bouffalo_sdk VS pbbr

I bought a bunch of the 16Mbit flash variant for an embedded project but sadly it looks like the firmware always gets corrupted on write, and have gotten no reply from Bouffalo

https://github.com/bouffalolab/bouffalo_sdk/issues/92

I tried looking through the source code of the SDK to get somewhat of an understanding, but it's taking too long for me to understand, so I'll leave it in your hands. gpio.h gpio.c gpio_reg.h

BouffaloLab has recently started bringing order to the chaos. They have created a new bouffalo_sdk where they're merging bl_mcu_sdk and bl_iot_sdk, the latter being the one to use for wireless. The README file lists which peripherals are currently supported. There's still work to be done, but it's good news they engaged into this endeavour.

The chip has complete-ish sdk here(https://github.com/bouffalolab/bouffalo_sdk) we use as "documentation". Datasheet and the reference manual are incomplete.

I don't think there is a "common solution". From my point of view, the Bouffalo Labs chipsets are not yet widely in use, at least not outside of china. However - as far as I can see, the USB host example code from the SDK interfaces the USB HID parts of the stack, too: https://github.com/bouffalolab/bl_mcu_sdk/blob/master/examples/peripherals/usbhost/usb_host.c

I just scoured the current main branch of https://github.com/bouffalolab/bl_mcu_sdk and can see the current HAL supports DMA, EMAC, flash, GPIO, MJPEG, PWM, RTC, encryption, timers, UART and USB. DAC and ADC's (audio) are implemented but not tested. I can also see there are BSPs for the LP core if you wanted to take advantage of it, with helloworld examples for all three, and finally there are some examples of using TensorFlowLite in the examples directory that you could build and try too.

Wifi/RF on bl616 is the same state as bl808. We are waiting for bouffalo to release support for it in bl_mcu_sdk: https://github.com/bouffalolab/bl_mcu_sdk/issues/85

Perhaps you can work on the new promising Shortest Path Bridging (SPB) in the Linux kernel that has not been very popular as it should be [1],[2],[3].

[1] 802.1Q-2018 - IEEE Standard for Local and Metropolitan Area Network--Bridges and Bridged Networks:

https://ieeexplore.ieee.org/document/8403927

[2] Provider Backbone Bridging for Linux:

https://github.com/openss7/pbbr

[3] Are there inherent problems with 802.1aq preventing wider adoption?

https://www.reddit.com/r/networking/comments/8gez0r/are_ther...