cjacker
commented
1 year ago After BLFlashCommand added and the commit [update][board] enable fw header for new flash tool . it result in:
- flashing with blisp and bflb-mcu-tool completely broken. it also broken all tutorials, howtos, etc...
- BLFlashCommand not works as expected, the error as below, report missing "eflash_loader_32m.bin".
- There is no source codes released for BLFlashCommand and various eflash_loader.elf, etc...
My Questions:
- Is it really good to commit so many binaries and break all known open-source solutions?
- Is 'bflb-mcu-tool' also official program tool? How is it different from 'BLFlashCommand'? which is maintained and supported by official in deed?
BLFlashCommand error output:
./BLFlashCommand --interface uart --port /dev/ttyACM0 --chipname bl702 --config ./flash_prog_cfg.ini
['./BLFlashCommand', '--interface', 'uart', '--port', '/dev/ttyACM0', '--chipname', 'bl702', '--config', './flash_prog_cfg.ini']
[10:27:10.357] - Serial port is /dev/ttyACM0
[10:27:10.357] - ==================================================
[10:27:10.359] - Program Start
[10:27:10.359] - ========= eflash loader cmd arguments =========
[10:27:10.360] - serial port is /dev/ttyACM0
[10:27:10.360] - chiptype: bl702
[10:27:10.360] - cpu_reset=False
[10:27:10.377] - ========= Interface is uart =========
[10:27:10.377] - Eflash load bin file: /home/cjacker/bouffalo_flash_cube/chips/bl702/eflash_loader/eflash_loader_32m.bin
[10:27:10.377] - ========= load eflash_loader.bin =========
[10:27:10.377] - Load eflash_loader.bin via uart
[10:27:10.377] - ========= image load =========
[10:27:10.389] - default set DTR high
[10:27:10.490] - usb serial port
[10:27:10.541] - clean buf
[10:27:10.542] - send sync
[10:27:10.753] - ack is b'4f4b464c0201'
[10:27:10.784] - shake hand success
[10:27:10.794] - get_boot_info
[10:27:10.798] - data read is b'0100020700000000931d000027000004000043575c4cb97c'
[10:27:10.798] - ========= ChipID: 000043575c4cb97c =========
[10:27:10.798] - last boot info: None
[10:27:10.798] - sign is 0 encrypt is 0
[10:27:10.798] - [Errno 2] No such file or directory: '/home/cjacker/bouffalo_flash_cube/chips/bl702/eflash_loader/eflash_loader_32m.bin'
Traceback (most recent call last):
File "libs/base/bflb_img_loader.py", line 941, in img_load_process
File "libs/base/bflb_img_loader.py", line 802, in img_load_main_process
FileNotFoundError: [Errno 2] No such file or directory: '/home/cjacker/bouffalo_flash_cube/chips/bl702/eflash_loader/eflash_loader_32m.bin'
[10:27:10.800] - Load helper bin time cost(ms): 422.57763671875
[10:27:10.800] - {"ErrorCode": "0003","ErrorMsg":"BFLB LOAD HELP BIN FAIL"}
[10:27:10.802] - Burn Retry
[10:27:10.802] - Burn return with retry fail
sakumisu
Fishwaldo
.
gamelaster
sakumisue
Abstract
For now we have these flashtools:
Devcube has mcu and iot, mcu is only used to flash firmware, iot is used to flash boot2/mfg/user bin/dts/toml, clock and flash config are set in devcube, and generates whole bin( firmware + bootheader) at last.
Flashcube is only used to flash bin with address, no other functions, and firmware must have bootheader, other bins no need.So it is very easier to use. How to write ini please see https://bl-mcu-sdk.readthedocs.io/zh_CN/latest/get_started/flash_prog.html.
Use
We should know that new firmware = old firmware (without bootheader) + bootheader = whole img bin generated by devcube
Old firmware (without bootheader)
Please do not use flashcube(gui or cmd), use devcube instead.
Old firmware (with bootheader)
You can use devcube or flashcube(gui or cmd), if you use bl808 multi groups , please use devcube
New firmware (with bootheader)
Use flashcube(gui or cmd)