Student: Dhruva Gole
Mentors: Jason Kridner
GSoC: GSoC entry
This project is currently just a proposal.
School: Veermata Jijabai Technological Inst.
Primary language : English, Marathi, Hindi
Typical work hours: 10AM - 7PM Indian Standard Time
Previous GSoC participation: I find embedded and IOT pretty interesting, given I have experience with ESP32, SIMCOM, ESP8266, Arduino UNO I think I will be able to excel in this project. This is the first time i am participating in GSoC.
About your project
Project name: librobotcontrol support for BeagleBone AI
BeagleBone gets used a lot in automation tasks, be they in industrial, building, home or otherwise. Software that helps enable individual hobbyists, but can bridge into professional automation tasks, is strongly desired.
The Robot Control Library package contains the C library and example/testing programs for the Robot Control project. This project began as a hardware interface for the Robotics Cape and later the BeagleBone Blue and was originally called Robotics_Cape_Installer. It grew to include an extensive math library for discrete time feedback control, as well as a plethora of POSIX-compliant functions for timing, threads, program flow, and lots more, all aimed at developing robot control software on embedded computers.
- This project will enable the control of the Beaglebone's PRUs using remoteproc and rpmsg driver rather than using uio drivers. The PRU is a dual core micro-controller system present on the AM335x SoC which powers the BeagleBone. It is meant to be used for high speed jitter free IO control. Being independent from the linux scheduler and having direct access to the IO pins of the BeagleBone Black, the PRU is ideal for offloading IO intensive tasks.
The library and example programs are primarily written in C, and has been well tested on the BeagleBone Blue.
- Why to port it to the BeagleBone AI?
- Built on the proven BeagleBoard.org® open source Linux approach, BeagleBone® AI fills the gap between small SBCs and more powerful industrial computers. Based on the Texas Instruments AM5729, developers have access to the powerful SoC with the ease of BeagleBone® Black header and mechanical compatibility. BeagleBone® AI makes it easy to explore how artificial intelligence (AI) can be used in everyday life via the TI C66x digital-signal-processor (DSP) cores and embedded-vision-engine (EVE) cores supported through an optimized TIDL machine learning OpenCL API with pre-installed tools. Focused on everyday automation in industrial, commercial and home applications.
- It uses the Dual Arm® Cortex®-A15 microprocessor subsystem and further specs can be found on the official website
What I like most about librobotcontrol, is that it allows new users to get a very intuitive hardware interface for the board it is being used on. Currently it only supports Robotics Cape and the BeagleBone Blue and Black. But with the evolution of AI on the edge, porting this library to be used onboard the BeagleBone® AI will prove to be very useful to a lot of hardware enthusiasts, AI/ML developers and hobbyists to deploy edge computing solutions along with easy to program hardware.
- Features to be implemented
- Port this package to support the BeagleBone® AI.
- Port all the existing examples to run on BeagleBone® AI.
- Fill out the TODOs on the official System Reference Manual of the beaglebone AI
- Add the necessary docs on librobotcontrol website .
Details of implementation
- The Robotics Cape
The Robotics Cape brings the power of the BeagleBone Black to your robotics project with almost no setup time. Built by engineers for engineers, the Robotics Cape is loaded with innovative features and a library designed to effortlessly take your robotics concepts from design to reality. (source)
It has the following Technical Specifications :-
- 2 Cell Lipo Charging, Balancing, and Protection
- Battery Charge Inidcator LEDs
- 4 H-Bridge DC Motors Controllers 1.2A each
- 8-Channel Servo/ESC Output Enabled by PRU
- 6V 4A Regulated Power Supply to Protect Servos
- 9-Axis IMU: Invensense MPU-9250, and many more on-board peripherals that any robotic enthusiast or developer can want!
The above cape needs the Robot Control Library (ref documentation) to function. Currently, this is only available for the BeagleBone Blue and Black.
However, the BeagleBone® Blue lacks TI C66x digital-signal-processor (DSP) cores and embedded-vision-engine (EVE) cores which the AI board has. This enables machine learning tools to be integrted with a device capable of programmable hardware IOs. However it still lacks a proper hardware interface which is where the need to provide librobotcontrol support comes in.
The beaglebone AI has many programmable PRU General-Purpose Output and Input pins as give on device docs page
Implement all libraries under Robot Control Library (repo here to simplify tasks like writing to a pin, reading from a pin, delay, motor control, etc.
- Reimplement stock examples in librobotcontrol repository
I intend to port as many examples as the board can support using it's hardware to the examples directory.
- The How
Inorder to accomplish the above tasks, I will go through the pins of the beagle AI and accordingly make changes in the header files. For this, I have familiarized myself with the device tree for BeagleBone® AI. Also, I will be using the SRM(System Ref. Manual) which is given on this page and the BeagleBone cape interface spec is here. This is a list of symlink interfaces based on BeagleBone Cape header pins.
- LEDs: The compatibility layer comes with simple reference nodes for attaching LEDs to any gpio pin. (see here. For example, in the BBBWL/BBB, /sys/class/leds/led_P8_03 links to gpio1_6 whereas in the BBAI it is linked to gpio1_24. Pins gpio3_18,19,20 that are there in BBBWL/BBB are simply non existent in the BBAI.
- I2C: Compatibility layer provides simple I2C bone bus nodes for creating compatible overlays for BBBWL, BBB, & BBAI.
- SPI: SPI bone bus nodes allow creating compatible overlays for BBBWl, BBB, & BBAI.
- UART: UART bone bus nodes allow creating compatible overlays for BBBWl, BBB, & BBAI.
and many more like ADC, PWM, eCAP, LCD, etc. have differences in the way that their Header Pins are linked in the system. This can cause massive issues while using the current version of Robot Control Library, as it takes into account only the BBBWL/BBB pins.
|May 17||Proposal accepted or rejected|
|Jun 07||Pre-work complete||Coding officially begins!|
|June 17||Milestone #1|
|June 24||Milestone #2||
|June 30||Milestone #3||
|July 12 -July 16 18:00 UTC||Milestone #4 (Phase 1 evaluations)||
|July 23||Milestone #5||
|July 30||Milestone #6||
|Aug 06||Milestone #7||
|August 10 August 16 - 26 18:00 UTC||Milestone #8 (Phase 2 evaluations)||
|August 23 - 30 18:00 UTC||Mentors submit final student evaluations|
Experience and approach
I have used C++, C and Python programming languages over the past 3 years in a variety of projects involving embedded systems using the ESP32, Arduino UNO, ESP8266 and am also well-versed with freeRTOS.
I have an aptitude for writing good reports and blogs, and have written a small blog on how to use a debugger.
I recently did a project using ESP32, in which I used the DHT11 sensor to display humidity and temperature on a local HTML server . Other than that I have developed firmware for a 3 DOF arm based on an ESP32 custom board. I also interned at an embedded device startup where I
- Interfaced ADS1115 ADC with the ESP32 and used it to read battery voltage.
- Used UART for ESP32 and SIMCOM SIM 7600IE communication to gain LTE support.
- Published local sensor data to the cloud via LTE.
I actively contribute to open source and do a lot of mini projects throughout the year, you can find my several more interesting projects at my github page
I believe that if I get stuck on my project and my mentor isn’t around, I will use the resources that are available to me. this includes looking on online forums for support, trying approaches that have worked from previous experience and also getting in touch with professionals via IRC/other media for support.
librobotcontrol uses specific GPIO, I2C, SPI ports and the indexes all need to be updated to use the Cape Compatibility layer in a way that causes old BeagleBone Black + RC and BeagleBone Blue without the Cape Compatibility layer not to break.
- -Jason Kridner