BeagleBoard/GSoC/2023 Proposal/AyushSingh

Proposal: Replace GBridge

About Student: Ayush Singh
Mentors: Jason Kridner, Vaishnav
Wiki: BeagleConnect
GSoC: TBD

Status

This project is currently just a proposal.

Proposal

• Completed All the requirements listed on the ideas page.
• The PR request for cross-compilation task: #170

About you

IRC: @ayush1325:matrix.org
Github: Ayush1325
Blog: Programmer's Hideaway
Slack: Ayush1325
Gitlab: ayush1325
Discourse: ayush1325
School: Indian Institute of Technology (ISM), Dhanbad
Country: India
Primary language: English, Hindi
Typical work hours: 12PM - 01AM Indian Standard Time<be>

Previous GSoC participation: I have previously participated in GSoC 2022 for Tianocore Organization. I have been quite interested in working on the Linux Kernel, the biggest Open-Source project in the world, for a long time. While I have worked on low-level stuff like UEFI, I still haven’t contributed to upstream Linux. Initially, the barrier of entry was simply too high for me. After completing the GSoC 2022 project, I was more confident about working on upstream Linux. However, I couldn’t find strong enough motivation to drop my other open-source projects to work on Linux Kernel. With this project, I hope to change this and start contributing to upstream Linux. I am also quite interested in BeagleConnect and its implications in the Internet of Things applications. Thus I would like to help improve it.

About your project

Project name: Replace GBridge

Description

Overview

The goal of the project is to eliminate the need for GBridge completely and simplify the architecture of BeagleConnect. The current architecture is as follows:

Greybus <--Netlink--> GBridge <--wpanusb--> cc1532 <--6lowpan--> BeagleConnect

The new architecture will look as follows:

Greybus <--Platform Driver--> cc1532 <--6lowpan--> BeagleConnect

I have also created a Flow Chart for better visualization.

The subtasks I have identified are the following:

1. Allow the Greybus Linux driver to directly communicate with cc1352
2. Move SVC and APBridge roles into cc1352
3. Eliminate the need for GBridge

GBridge Overview

To eliminate GBridge, we must first understand it's different parts. Thus I will discuss each part here in brief.

SVC

It is in charge of module hot plug / hot unplug detection, create / destroy connections, etc.

Netlink

GBridge is using netlink to communicate with Greybus.

Controller

The controller is actually the link between the SVC, netlink and all the modules. There are 4 main controllers present in GBridge currently:

1. Bluetooth Controller: It scans continuously to detect new bluetooth module. When a Bluetooth module with the "GREYBUS" string in its name show up, the controller will generate an hotplug event and create a connection.
2. TCP/IP: It use avahi to detect a new module.
3. GBSHIM: It provides a way to test quickly and easily Greybus, Greybus netlink and gbridge.
4. UART: This does not seem to be in the README, but is being registered if a `p` option is supplied.

Greybus Serdev Driver

This new driver will be responsible for communication between Greybus and cc1352. This will be a Serial Device Bus Driver (serdev) driver with the following structure:

struct serdev_device_driver {
	struct device_driver driver;
	int	(*probe)(struct serdev_device *);
	void	(*remove)(struct serdev_device *);
};

The actual types that are used in communication can be found at include/linux/greybus/greybus_protocols.h` in upstream Linux kernel.

The driver will run on BeaglePlay's AM62 processor, although it should be possible on any Linux host.

The two main functions of this driver are as follows:

probe

This step will involve the following:

• Initialize stuff: This includes Work Queue, spin locks and allocate read/write buffers.
• Open the serial device. Set parameters such as the baudrate. Mostly copy the configuration from bcfserial.
• Create gb_host_device.

Since we only want to use a single static UART (between AM62 and CC1352), we can optimize the driver probe.

remove

• Flush the contents of the work queue.
• Close the serdev device

cc1352 Firmware

Most of the heavy lifting will be done by the cc1352 firmware. It now needs to take care of both the SVC and APBridge roles. This will be running on BeaglePlay's CC1352 processor.

This will be running ZephyrRTOS. The functionality will be implemented as a Zephyr Module.

While I am writing about SVC Role and APBridge Role separately, the implementation would not really have any rigid separation. The SVC and AP terminology is from the Project Ara days when these used to be physically separate entities.

SVC Role

The cc1352 firmware will need to detect the hotplug and removal of modules. In the current architecture, each controller runs an event_loop in a pthread to carry out its functionality. The approach I am currently thinking of is as follows:

1. Run a loop in a separate thread that polls for `_greybus._tcp`.
2. Maintain a table of nodes.
3. Compare the polled devices against the table for new/removed nodes.
4. Handle new devices and free removed device resources.

Initially, I plan on implementing a basic version using threads. However, if I have time, I will try to write a more efficient implementation using the Polling API.

APBridge Role

The cc1352 firmware will now also be responsible for the APBridge role, which is currently handled by GBridge. This role involves a variety of tasks:

• Reading/Writing Greybus messages over 6lowpan and generating messages to send to host.
• Installing/Uninstalling greybus interfaces on insertion/removal after receiving an event from SVC.
• Get Device manifest on insertion.
• Sending events to register drivers, etc

The actual communication between Host and BeagleConnect can be implemented using Message Queues + Events.

Using Message Queues might be better than pipes and/or directly sending messages from the controller since the asynchronous operation of Message Queues in a multi-controller architecture might be more efficient.

Timeline

Date	Status	Details
May 4 - May 28	Community Bonding	I will be having exams till May 10th, so I will start being active after that. Introduction Video. Required hardware will be available to me. Setup BeaglePlay and BeagleConnect Freedom.
May 28	Milestone #1	Run some samples on the two boards. Write a Hello World Linux Driver for BeaglePlay. Setup workflow to deploy to driver from Linux host.
June 4th	Milestone #2	Start work on serdev Linux Driver. Start work on Zephyr Module For CC1352.
June 11th	Milestone #3	Start testing communication between serdev driver running on AM62 with Zephyr Module on CC1352. The communication will just be simple messages (not Greybus stuff)
June 18th	Milestone #4	Start implementing greybus stuff. This will involve creating gb host device, sending/reciveing greybus messages, cleaning up greybus stuff on remove, etc. This involves implementing async processing of greybus requests and responses over the socket. Also add parsing for greybus manifest.
June 25th	Milestone #5	Implement a table to keep track of all nodes and their cports. Implement the SVC role for cc1352. This involves implementing all control operations.
July 2nd	Milestone #6	Implement APBridge role for cc1352. Use HDLC for UART communication. Also implement MCUmgr over HDLC
July 9th	Milestone #7	Write some tests for SVC Role. Also run the tests in CI.
July 14th	Milestone #8 (Mid-term Evaluation)	Write tests that APBridge role is working as intended. Also run the tests in CI.
July 23th	Milestone #9	Start testing all the 3 components (Greybus Linux driver, cc1352 and BeagleConnect) together. Iron out bugs.
July 30th	Milestone #10	Submit upstream PR for the new Platform Driver.
August 6th	Milestone #11	Test the completed setup and make some performance optimizations.
August 13th	Milestone #12	Make any suggested changes to different PRs.
August 21th to 28th	Final Week	Submit final work product and final mentor evaluation Complete YouTube video
August 28 to September 4	End of competition	Mentors submit final student evaluations

Experience and approach

I have a very good knowledge of Rust programming language in firmware development. I work a lot on `no_std` environments, i.e. environments where Rust standard library is not available due to some reason. I also have experience with Rust FFI for things like UEFI specification. I have some experience with C and C++ as well. Some of my previous projects include

1. Rust UEFI std: PR for implementation of Rust std for UEFI. This project was initially done as a part of the Google Summer of Code 2022. However, at this point it has evolved into its own thing and I am still actively working on it.
2. r-efi: UEFI Reference Specification Protocol Constants and Definitions in Rust. I am just one of the frequent contributors. This project requires deep knowledge of Rust FFI.
3. kconfig-rs: Rust bindings for KConfig KDE Framework. This project was done as a part of the Season of KDE 2022.
4. Qmetaobject: I am one of the collaborators in this project. It allows the creation of Qt applications in Rust.

I also regularly contribute to other open-source projects I am using at the time.

Contingency

If I get stuck on my project and my mentor isn’t around, I will use the following resources:

• Current Github Repos
  • Greybus
  • GBridge
  • BeagleConnect Freedom
• Linux Kernel mailing list (especially Greybus Subsystem)
• BeagleConnect Documentation
• Zeroconf

Benefit

The completed project would allow using BeagleConnect without requiring an intermediary (GBridge). Also, due to the presence of GBridge, the upstream Greybus drivers need to be patched for netlink support, which will be eliminated by this project. Thus, it will eventually be possible to just use mainline Linux kernel for BeagleConnect. This should help increase the adoption of BeagleConnect as an industry standard.