The ZephyrRTOS is a newer Open Source RTOS. It strives to deliver the best-in-class RTOS for connected resource-constrained devices, built to be secure and safe.

This add ZephyrRTOS entry point and define environment to build Bouffalo Lab low level peripheral drivers as hal_bouffalolab. Initially, bl602 is the target but can be extended to any other SoC series present in the bl_mcu_sdk.

The commit sequence try fix small issues found due to code isolation. The BFLB_USE_PLATFORM was necessary to be created to isolate low level drivers and Bouffalo Lab HAL, once Zephyr have their own.

The zephyr directory is completely isolated from bl_mcu_sdk and not interfere. This layout was created to allow add manufacturer repositories as external modules into ZephyrRTOS.

Currently there is a minimal attempt to enable Bouffalo Lab SoC at ZephyrRTOS at PR 37686

How to Build/Flash on a working zephyr environment:

1. Clone PR 37686
2. Read board/riscv/dt_bl10_devkit/doc/index.rst
3. west update
4. west build -b dt_bl10_devkit samples/hello_world
5. west flash

There does not seem to be much in the way of documentation for using JTAG with the BL808 chip. I have been trying to use a RV Debugger Plus with a Ox64 board but am not able to examine any of the cores.

Hi, I'm trying to flash the BL808 used on the Ox64 board (20221018 version) and I have many questions about it:

1. Do you provide any support for flashing it using JFlash (JLink)? I've been able to read the memory using JMem, working well, and I can even read registers (the cpu id one for example). But when trying to flash it doesn't work, I guess because it's QSPI and read-only when using memory-mapped access... So I'll be forced to use an Open FlashLoader binary if I want it to work, and I was wondering if you provide such things or workarounds...

2. When using BLDevCube with JLink mode, I can see/select the JLink port that is connected to the BL808 and click "Create & Download", and it doesn't go that far as you can see in the logs:

...
[17:18:26.264] - Write flash img
[17:18:26.266] - Image hash is b'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855'
[17:18:26.267] - Header crc: b'77f215f5'
[17:18:26.268] - Write flash img
[17:18:26.270] - Encrypt efuse data
[17:18:26.272] - ========= eflash loader config =========
[17:18:26.287] - Version: eflash_loader_v2.4.3
[17:18:26.288] - Program Start
[17:18:26.289] - ========= eflash loader cmd arguments =========
[17:18:26.289] - None
[17:18:26.289] - Config file: D:\Programmes\BLDevCube-1.8.1\chips\bl808\eflash_loader\eflash_loader_cfg.ini
[17:18:26.290] - serial port is 175001652
[17:18:26.290] - cpu_reset=False
[17:18:26.290] - chiptype: bl808
[17:18:26.290] - ========= Interface is JLink =========
[17:18:26.291] - Bootrom load
[17:18:26.291] - ========= get_boot_info =========
[17:18:26.291] - interface not fit
[17:18:26.291] - ErrorCode: 0050, ErrorMsg: BFLB IMG LOAD SHAKEHAND FAIL
[17:18:26.291] - Burn Retry
[17:18:26.291] - 0
[17:18:26.291] - Burn return with retry fail

3. When flashing using UART on BLDevCube (I push the boot button before powering on the chip), the handshake is successful, the image is built, but I get an error when it tries to enter xip mode (see logs below). It seems that flashing is successful, but when I use JMem (JLink) to read the flash at 0x58000000, it's filled with 0xFF, so I'm wondering if the flashing actually worked (maybe rollback?). Note that I'm playing with Rust and linker scripts (all based on your SDK), if you think that it comes from this I'll try on the sdk, but I'd be really surprised that my binary (manually verified to contain right startup instructions) would prevent flashing success.

[17:08:59.756] - EFUSE_CFG
[17:08:59.757] - BOOTHEADER_GROUP0_CFG
[17:08:59.758] - BOOTHEADER_GROUP1_CFG
[17:08:59.779] - Create bootheader using D:\Programmes\BLDevCube-1.8.1\chips\bl808\img_create_mcu/efuse_bootheader_cfg.ini
[17:08:59.780] - Updating data according to <D:\Programmes\BLDevCube-1.8.1\chips\bl808\img_create_mcu/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP0_CFG]>
[17:08:59.784] - Created file len:352
[17:08:59.789] - Create bootheader using D:\Programmes\BLDevCube-1.8.1\chips\bl808\img_create_mcu/efuse_bootheader_cfg.ini
[17:08:59.790] - Updating data according to <D:\Programmes\BLDevCube-1.8.1\chips\bl808\img_create_mcu/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP1_CFG]>
[17:08:59.795] - Created file len:352
[17:08:59.798] - Create efuse using D:\Programmes\BLDevCube-1.8.1\chips\bl808\img_create_mcu/efuse_bootheader_cfg.ini
[17:08:59.799] - Updating data according to <D:\Programmes\BLDevCube-1.8.1\chips\bl808\img_create_mcu/efuse_bootheader_cfg.ini[EFUSE_CFG]>
[17:08:59.804] - Created file len:256
[17:08:59.811] - Image create path: D:\Programmes\BLDevCube-1.8.1\chips\bl808\img_create_mcu
[17:08:59.812] - Config file: D:\Programmes\BLDevCube-1.8.1\chips\bl808\img_create_mcu/img_create_cfg.ini
[17:08:59.814] - Image hash is b'4642d564bc85498d292f113851b9a92c9780a838f623766099bd8a30a06d6eff'
[17:08:59.830] - Header crc: b'121ba109'
[17:08:59.831] - Write flash img
[17:08:59.834] - Image hash is b'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855'
[17:08:59.835] - Header crc: b'77f215f5'
[17:08:59.835] - Write flash img
[17:08:59.837] - Encrypt efuse data
[17:08:59.839] - ========= eflash loader config =========
[17:08:59.854] - Version: eflash_loader_v2.4.3
[17:08:59.855] - Program Start
[17:08:59.856] - ========= eflash loader cmd arguments =========
[17:08:59.856] - None
[17:08:59.856] - Config file: D:\Programmes\BLDevCube-1.8.1\chips\bl808\eflash_loader\eflash_loader_cfg.ini
[17:08:59.858] - serial port is COM4
[17:08:59.858] - cpu_reset=False
[17:08:59.858] - chiptype: bl808
[17:08:59.858] - ========= Interface is uart =========
[17:08:59.859] - com speed: 115200
[17:08:59.859] - Bootrom load
[17:08:59.859] - ========= get_boot_info =========
[17:08:59.859] - ========= image get bootinfo =========
[17:09:00.196] - tx rx and power off, press the machine!
[17:09:00.197] - cutoff time is 0.05
[17:09:00.257] - power on tx and rx
[17:09:01.262] - reset cnt: 0, reset hold: 0.05, shake hand delay: 0.1
[17:09:01.263] - clean buf
[17:09:01.266] - send sync
[17:09:01.799] - ack is b'4f4b'
[17:09:01.847] - shake hand success
[17:09:02.355] - data read is b'01000808000000000b14c102e9f12bcf0eb455002ff4fb18'
[17:09:02.356] - ========= ChipID: b40ecf2bf1e9 =========
[17:09:02.356] - Get bootinfo time cost(ms): 2497.1748046875
[17:09:02.356] - clock para file: D:\Programmes\BLDevCube-1.8.1\chips/bl808/efuse_bootheader/clock_para.bin
[17:09:02.357] - change bdrate: 115200
[17:09:02.357] - Clock PLL set
[17:09:02.357] - clock para:
[17:09:02.357] - 504346470404000003010300010200020101000101010101c0c4e229
[17:09:02.362] - Set clock time cost(ms): 5.013427734375
[17:09:02.493] - Read mac addr
[17:09:02.498] - flash set para
[17:09:02.499] - get flash pin cfg from bootinfo: 0x04
[17:09:02.499] - set flash cfg: 14104
[17:09:02.499] - Set flash config
[17:09:02.504] - Set para time cost(ms): 4.98779296875
[17:09:02.505] - ========= flash read jedec ID =========
[17:09:02.509] - Read flash jedec ID
[17:09:02.509] - readdata:
[17:09:02.510] - b'ef601800'
[17:09:02.510] - Finished
[17:09:02.514] - Program operation
[17:09:02.515] - Dealing Index 0
[17:09:02.515] - ========= programming D:\dev\projects\bflb-rust-experiment\app.bin to 0x58000000
[17:09:02.519] - flash para file: D:\Programmes\BLDevCube-1.8.1\chips/bl808/efuse_bootheader/flash_para.bin
[17:09:02.519] - Set flash config
[17:09:02.533] - Set para time cost(ms): 13.519287109375
[17:09:02.533] - ========= flash load =========
[17:09:02.534] - ========= flash erase =========
[17:09:02.534] - Erase flash from 0x58000000 to 0x58000733
[17:09:02.540] - Erase time cost(ms): 6.013427734375
[17:09:02.706] - Load 1844/1844 {"progress":100}
[17:09:02.707] - Load 1844/1844 {"progress":100}
[17:09:02.707] - Write check
[17:09:02.713] - Flash load time cost(ms): 171.0556640625
[17:09:02.714] - Finished
[17:09:02.714] - Sha caled by host: a5a16e48a85b7f152a808103c63a3eeb34bc1b6ad8bf02932225b1498bd550fe
[17:09:02.714] - xip mode Verify
[17:09:04.724] - ack is b''
[17:09:04.725] - Not ack OK
[17:09:04.725] - Retry
[17:09:06.739] - ack is b''
[17:09:06.740] - Not ack OK
[17:09:06.740] - Retry
[17:09:08.752] - ack is b''
[17:09:08.753] - Not ack OK
[17:09:08.753] - Retry
[17:09:10.756] - ack is b''
[17:09:10.757] - Not ack OK
[17:09:10.757] - Read Fail
[17:09:12.758] - ack is b''
[17:09:12.759] - ErrorCode: 0039, ErrorMsg: BFLB FLASH XIP MODE ENTER FAIL
[17:09:12.759] - a bytes-like object is required, not 'NoneType'
Traceback (most recent call last):
File "libs\bflb_eflash_loader.py", line 3420, in efuse_flash_loader_do
File "libs\bflb_eflash_loader.py", line 2045, in flash_load_specified
File "libs\bflb_eflash_loader.py", line 1948, in flash_load_opt
TypeError: a bytes-like object is required, not 'NoneType'
[17:09:12.760] - Burn Retry
[17:09:12.760] - 0
[17:09:12.760] - Burn return with retry fail

Thank you!

I have BL70X IoT DVK-MB-V1.1, which have BL706 with no internal FLASH or RAM, everything is external. It have Winbond 25Q32JVS1Q and 1604M-3SQR.

Unfortunately, I can't get this flashed with bflb_mcu_tool or Bouffalo Lab Dev Cube, it all ends on Flash load shake hand. I tried to change flash_id = ef8016 (which is flash config for W25Q32JW_ef8016.conf), although, the eflash_loader still can't load the SPI flash. Also I tried to change boot headers with SPI configuration for that same Winbond, still no success. Any ideas?

Thanks

Hi, I"m trying to get a JLINK programmer running with the ox64.

First issue I see is - the JTAG pins on the ox64 are also the same pins used for UART0 and UART1.

Is there a way to remap the JTAG pins to another GPIO (maybe via efuse?)

2nd - even with a empty flash - I can't get JTAG working. (tried both in Bootloader mode, and normal mode with empty flash - which wouldn't make sense as those pins are used for flashing)

(I see this in the board BSP - https://github.com/bouffalolab/bl_mcu_sdk/blob/16d3a819c86dab25e3c20155a3563c2dc9bc7220/bsp/board/bl808dk/board.h#L6 but there is no actual function in the SDK)

Hi!

I feel like there is a little asymmetry in the level of documentation between Reference Manual and SDK, regarding interactions between Camera, MJPEG and H265 modules.

For example, the module that seems responsible for accepting CSI in DVP module (using the CAM_FRONT registers) is not documented, while CAM registers are. In general these modules are implemented and partially documented but lacks of information about interactions between all of them, especially CSI/CAM, CAM/MJPEG with hardware mode. It would be really helpful if these fields were more documented.

Thank you anyway, this is hard but good learning for me :)

Hi, I'm wondering where to find documentation about all the network subsystem in details, I cannot find any information about Wifi/Zigbee/BT either in the reference manual or the datasheet, they are only mentioned but no register/IRQ description is available.

It seems intentional, so am I missing something in another doc?

bl-mcu-iot I can't find how to use the wifi feature, is there not yet a wifi SDK feature for BL602 in this SDK? Is there a bouffalolab team that can help?

https://github.com/bouffalolab/bl_mcu_sdk/blob/16d3a819c86dab25e3c20155a3563c2dc9bc7220/bsp/board/bl808dk/bl808_flash_d0.ld#L25-L30

https://github.com/bouffalolab/bl_mcu_sdk/blob/16d3a819c86dab25e3c20155a3563c2dc9bc7220/bsp/board/bl808dk/bl808_flash_m0.ld#L25-L30

These lines of the BL808 linker script doesn't correspond at all to the datasheet (page 12-13, at https://raw.githubusercontent.com/bouffalolab/bl_docs/main/BL808_DS/en/BL808_DS_1.2_en.pdf):

Could you explain why some of these values are correct (XIP, XRAM), the most annoying values are for D0 RAM, where it is set to 0x3EFF8000 in linker script, but 0x3EF80000 (notice the shift) in datasheet, values for M0 are correct. I'm also wondering where TCM is specified in the memory mapping tables?

Note: I'm posting this issue here, but this is related to https://github.com/bouffalolab/bl_docs, but there is not much activity there.

When building any of the example programs with make CHIP=bl702 BOARD=bl702dk, the following error occurs:

/home/tony/bl_mcu_sdk/drivers/lhal/config/bl702/device_table.c:205:19: error: 'BFLB_DEVICE_TYPE_KYS' undeclared here (not in a function); did you mean 'BFLB_DEVICE_TYPE_AES'?
  205 |       .dev_type = BFLB_DEVICE_TYPE_KYS,
      |                   ^~~~~~~~~~~~~~~~~~~~
      |                   BFLB_DEVICE_TYPE_AES
make[3]: *** [build_out/drivers/lhal/CMakeFiles/lhal.dir/build.make:368: build_out/drivers/lhal/CMakeFiles/lhal.dir/config/bl702/device_table.c.obj] Error 1
make[2]: *** [CMakeFiles/Makefile2:351: build_out/drivers/lhal/CMakeFiles/lhal.dir/all] Error 2

This error does not occur for any other target (BL602/BL616/BL808).

The front page marks cameras as not supported. There are several low cost boards with MIPI camera interface, e.g. Sipeed M1s Dock: https://wiki.sipeed.com/hardware/en/maix/m1s/m1s_dock.html.

Is there any chance to get cameras supported on BL808?

Hi, Just wondering why we are only allocating 64K DRAM in the D0 linker script when we have 512K?

https://github.com/bouffalolab/bl_mcu_sdk/blob/a574195a4b3399341794971a2ab4b8b17f4b70d7/bsp/board/bl808dk/bl808_flash_d0.ld#L29

Hi, I see UART3 is missing from the hal driver. Any plans to update it?

Can you share the "magic" to get both TX/RX on D0 running with UART3?

(I see in the board.c only TX is setup, does this commented out line turn on RX? - https://github.com/bouffalolab/bl_mcu_sdk/blob/a574195a4b3399341794971a2ab4b8b17f4b70d7/bsp/board/bl808dk/board.c#L215)

Hi, we have the header bl808_ipc.h present, but the source for IPC is missing. I found a copy in the bl_linux repo, but wondering if it could be added to this repo?

https://github.com/bouffalolab/bl808_linux/blob/main/bl_mcu_sdk_bl808/drivers/bl808_driver/std_drv/src/bl808_ipc.c

Hi there,

Are there any plans to support BLE and WiFi like version 1.4.5 and earlier did? I'm specifically interested in both BL702 and BL808. I see that BL808 is only supported in 2.0, so is there no official way to develop BLE/WiFi firmware for BL808?

Thanks, Tony

SPI BL702 - no "Byte-inverse signal for FIFO" option? SPI_BYTE_MSB https://github.com/bouffalolab/bl_mcu_sdk/blob/master/drivers/lhal/include/bflb_spi.h#L66

BL702/704/706 Reference Manual:

spi_config: 
Address：0x4000a200
bit7 - Byte-inverse signal for each FIFO entry data
0: Byte[0] is sent out first
1: Byte[3] is sent out first

With SPI_BYTE_MSB is set, SPI works correctly on the test board with BL702C10.

The readme says : " Chip Reference Manual and Chip Data Manual are listed on document "

When I go to the page, and then click a datasheet download link, it says "Sorry, the page is not found"