BouffaloSDK is the IOT and MCU software development kit provided by the Bouffalo Lab Team, supports all the series of Bouffalo chips. Also it is the combination of bl_mcu_sdk and bl_iot_sdk 。
Name | Description |
---|---|
bsp/board | clock, pinmux, memoryheap and console init |
bsp/common | bsp common driver |
components | components |
docs | quick start、 api、demo doc |
drivers/lhal | bouffalo common peripherals drivers which support all the chips |
drivers/soc | bouffalo non-generic peripherals drivers |
drivers/rfparam | rf param |
examples | official samples |
tools | tools |
LHAL is a low level hal driver for common peripherals designed by Bouffalo Lab, in order to support all the Bouffalo chips with the same api . Also it is convenient for users to use and port to other platforms.
Note:√ means supported ; × means not supported; ○ means supported but not tested ; - means no such peripheral.
Peripheral | BL602/BL604 | BL702/BL704/BL706 | BL616/BL618 | BL808 |
---|---|---|---|---|
ADC | ○ | √ | √ | ○ |
CAM | - | √ | √ | √ |
CKS | ○ | √ | √ | ○ |
CSI | - | - | - | √ |
DAC | ○ | √ | √ | ○ |
DMA | ○ | √ | √ | √ |
EFUSE | × | × | × | × |
EMAC | - | √ | √ | √ |
FLASH | √ | √ | √ | √ |
GPIO | ○ | √ | √ | √ |
I2C | ○ | √ | √ | ○ |
I2S | ○ | ○ | √ | ○ |
IR | ○ | √ | √ | ○ |
MJPEG | × | × | √ | √ |
PWM_v1 | ○ | √ | - | - |
PWM_v2 | - | - | √ | √ |
RTC | ○ | √ | √ | √ |
SEC_AES | ○ | √ | √ | √ |
SEC_SHA | ○ | √ | √ | √ |
SEC_TRNG | ○ | √ | √ | √ |
SEC_PKA | ○ | √ | √ | √ |
SPI | ○ | √ | √ | √ |
TIMER | ○ | √ | √ | √ |
UART | √ | √ | √ | √ |
USB_v1 | - | √ | - | - |
USB_v2 | - | - | √ | √ |
WDG | ○ | √ | √ | ○ |
Peripheral | BL602/BL604 | BL702/BL704/BL706 | BL616/BL618 | BL808 |
---|---|---|---|---|
WIFI4 | × | - | - | × |
WIFI6 | - | - | √ | - |
BT | - | - | √ | × |
BLE | × | × | √ | × |
ZIGBEE | - | × | × | × |
Note:√ means supported ; × means not supported; ○ means supported but not tested ; - means no such peripheral.
- riscv64-unknown-elf-gcc toolchain used in windows.
- riscv64-unknown-elf-gcc toolchain used in linux.
- T-HEAD official does not provide macos toolchain, so you should build by yourself, refer to build_toolchain_macos.
- linux-riscv64-linux-gcc toolchain used for compiling linux code.
Before compiling with the command line, you need to select the corresponding toolchain according to your operating system, configure it to the system environment variables, and install the make or ninja, then you can do the following. For the details, you can visit BouffaloSDK Environment Setup.
- Go to the demo directory where you want to compile and there are
main.c
andMakefile
files in that directory - Just execute the following command, take BL616 as an example
cd examples/helloworld
make CHIP=bl616 BOARD=bl616dk
- If you use BL808 or BL606P, you need to add CPU_ID with m0 or d0.
If you want to use ninja, you can try:
cd examples/helloworld
make ninja CHIP=bl616 BOARD=bl616dk
cd examples/helloworld
make ninja CHIP=bl808 BOARD=bl808dk CPU_ID=m0
TODO
Only supports debug with CKLink currently. See BouffaloSDK Debug Guide.
Note that if you are using linux, linux will deny access to the serial device due to permission issues, so add your own username to dialout
for easy to use, restart your linux and then take effect. Or add sudo
before command.
usermod -aG dialout xxx # xxx is your own name
cd examples/helloworld
make flash CHIP=chip_name COMX=xxx # chip_name should be bl602/bl702/bl616/bl808/bl606p, COMX in Windows, /dev/ttyxxx in Linux
- If you use BL808 or BL606P, you need to add CPU_ID with m0 or d0.
cd examples/helloworld
make flash CHIP=chip_name CPU_ID=m0 COMX=xxx # chip_name should be bl602/bl702/bl616/bl808/bl606p, COMX in Windows, /dev/ttyxxx in Linux
If flash using serial port rather than USB, different USB2TTL chips support different max baudrates, need to pay attention to when flashing.
chip | baudrate |
---|---|
ch340 | <= 500K |
cp2102 | <= 2M |
ft232 | <= 2M |
bl702 | <= 8M |
bl616 | <= 10M |
Chip Reference Manual and Chip Data Manual are listed on document
To get more BouffaloSDK documentation tutorial, like api manual or peripheral demo and so on, please visit:
TODO
Bouffalolab Developer Forum: https://bbs.bouffalolab.com/