Missing referenced firmware in Readme.md

[btashton]

Steps 3 and 4 refer to firmware for the e907 and the bl702, but this firmware does not appear to be built from this repo. Are these binaries or instructions to build them somewhere else?

[btashton]

Appears to be:

• https://dl.sipeed.com/shareURL/MAIX/M1s/M1s_Dock/7_Firmware
• https://dl.sipeed.com/shareURL/Accessories/RV-Debugger%20Plus

Based on the documentation here: https://wiki.sipeed.com/hardware/zh/maix/m1s/other/get_key.html

Should we update the documentation here? Is there source for the firmware_m1sdock_221109.bin?

[btashton]

Firmware can simply be built by running:

M1s_BL808_example/e907_app on  main
❯ ./build.sh firmware

and using the firmware.bin in the build_out folder

[taorye]

Thanks.

[x893]

Hello, i try all instruction to flash M1sDock but all without success. I try both COM ports, with and without BOOT+RST

d0fw.bin if lvgl_example

May be you can help with right direction ? Thanks Mitek

[12:29:50.353] - ========= Interface is Uart ========= [12:29:50.366] - eflash loader bin is eflash_loader_auto.bin [12:29:50.371] - ========= chip flash id: ef4016 ========= [12:29:50.401] - create partition.bin, pt_new is True [12:29:50.449] - Create bootheader using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:50.450] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP0_CFG]> [12:29:50.466] - Created file len:352 [12:29:50.480] - Create bootheader using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:50.481] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP1_CFG]> [12:29:50.498] - Created file len:352 [12:29:50.505] - Create efuse using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:50.508] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[EFUSE_CFG]> [12:29:50.525] - Created file len:256 [12:29:50.527] - ef_sw_usage_0 not exist [12:29:50.528] - ef_sw_usage_1 not exist [12:29:50.547] - ========= sp image create ========= [12:29:50.561] - Image hash is b'a42b69b01e69c2cbb2643612895522affa7309fbc8c6a6fe122b1ad5586efab2' [12:29:50.615] - Hash ignored [12:29:50.621] - Header crc ignored [12:29:50.621] - Write flash img [12:29:50.705] - Create bootheader using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:50.706] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP0_CFG]> [12:29:50.720] - Created file len:352 [12:29:50.738] - Create bootheader using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:50.738] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP1_CFG]> [12:29:50.752] - Created file len:352 [12:29:50.762] - Create efuse using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:50.766] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[EFUSE_CFG]> [12:29:50.778] - Created file len:256 [12:29:50.779] - ef_sw_usage_0 not exist [12:29:50.781] - ef_sw_usage_1 not exist [12:29:50.801] - ========= sp image create ========= [12:29:50.897] - Image hash is b'dcb8e025c9de669bc3caa21d5a39ee3d25076fe77a22fe45968474c93df8b2e1' [12:29:50.952] - Hash ignored [12:29:50.953] - Header crc ignored [12:29:50.954] - Write flash img [12:29:50.978] - FW Header is 1620, 2476 still needed [12:29:50.982] - FW OTA bin header is Done. Len is 4096 [12:29:51.123] - BL60X_OTA_Ver1.0 [12:29:51.277] - FW OTA bin is Done. Len is 496832 [12:29:51.996] - OTA XZ file len = 286748 [12:29:51.998] - Partiton len = 0 [12:29:52.000] - Warn: fw1 xz bin size is overflow with partition table, don't create ota bin [12:29:52.001] - Remove OTA directory due to xz image fail [12:29:52.012] - FW OTA xz is Done [12:29:52.063] - Create bootheader using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:52.066] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP0_CFG]> [12:29:52.079] - Created file len:352 [12:29:52.096] - Create bootheader using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:52.097] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP1_CFG]> [12:29:52.110] - Created file len:352 [12:29:52.119] - Create efuse using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:52.125] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[EFUSE_CFG]> [12:29:52.138] - Created file len:256 [12:29:52.142] - ef_sw_usage_0 not exist [12:29:52.144] - ef_sw_usage_1 not exist [12:29:52.164] - ========= sp image create ========= [12:29:52.266] - Image hash is b'8cd3c67189c44e3628251f4bf99d332545588e194854794a7a64cef9f8dcf85f' [12:29:52.317] - Hash ignored [12:29:52.317] - Header crc ignored [12:29:52.318] - Write flash img [12:29:52.342] - Warning: factory file is not programed to flash [12:29:52.343] - ========= eflash loader config ========= [12:29:52.925] - Version: eflash_loader_v2.4.2 [12:29:52.925] - Program Start [12:29:52.926] - ========= eflash loader cmd arguments ========= [12:29:52.926] - F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\eflash_loader/eflash_loader_cfg.ini [12:29:52.926] - Config file: F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\eflash_loader/eflash_loader_cfg.ini [12:29:52.930] - serial port is COM19 [12:29:52.933] - cpu_reset=False [12:29:52.934] - chiptype: bl808 [12:29:52.937] - ========= Interface is uart ========= [12:29:52.940] - com speed: 2000000 [12:29:52.941] - Bootrom load [12:29:52.941] - ========= get_boot_info ========= [12:29:52.941] - ========= image get bootinfo ========= [12:29:53.256] - tx rx and power off, press the machine! [12:29:53.258] - cutoff time is 0.05 [12:29:53.317] - power on tx and rx [12:29:54.312] - reset cnt: 0, reset hold: 0.05, shake hand delay: 0.1 [12:29:54.313] - clean buf [12:29:54.328] - send sync [12:29:54.746] - ack is b'' [12:29:54.747] - retry [12:29:55.029] - tx rx and power off, press the machine! [12:29:55.029] - cutoff time is 0.05 [12:29:55.091] - power on tx and rx [12:29:56.087] - reset cnt: 0, reset hold: 0.05, shake hand delay: 0.1 [12:29:56.087] - clean buf [12:29:56.103] - send sync [12:29:56.524] - ack is b'' [12:29:56.525] - retry [12:29:56.807] - tx rx and power off, press the machine! [12:29:56.809] - cutoff time is 0.05 [12:29:56.870] - power on tx and rx [12:29:57.869] - reset cnt: 0, reset hold: 0.05, shake hand delay: 0.1 [12:29:57.871] - clean buf [12:29:57.883] - send sync [12:29:58.305] - ack is b'' [12:29:58.306] - retry [12:29:58.314] - shake hand fail [12:29:58.316] - ######################################################################## [12:29:58.316] - 请按照以下描述排查问题： [12:29:58.316] - Boot pin是否上拉到板子自身的3.3V，而不是外部的3.3V [12:29:58.317] - UART RX是否连接到USB转串口的TX引脚 [12:29:58.317] - UART TX是否连接到USB转串口的RX引脚 [12:29:58.317] - 在使用烧录软件进行烧录前，是否在Boot pin拉高的情况下，使用Reset/Chip_En复位了芯片 [12:29:58.318] - 烧录软件所选择的COM口，是否是连接芯片的串口 [12:29:58.318] - 烧录软件上选择的波特率是否是USB转串口支持的波特率 [12:29:58.318] - 3.3V供电是否正常 [12:29:58.318] - 板子供电电流是否正常(烧录模式下，芯片耗电电流5-7mA) [12:29:58.319] - ######################################################################## [12:29:58.319] - shake hand fail [12:29:58.430] - {"ErrorCode": "0050","ErrorMsg":"BFLB IMG LOAD SHAKEHAND FAIL"} [12:29:58.431] - Burn Retry [12:29:58.433] - 0 [12:29:58.434] - Burn return with retry fail

[taorye]

Hello, i try all instruction to flash M1sDock but all without success. I try both COM ports, with and without BOOT+RST

d0fw.bin if lvgl_example

May be you can help with right direction ? Thanks Mitek

[12:29:50.353] - ========= Interface is Uart ========= [12:29:50.366] - eflash loader bin is eflash_loader_auto.bin [12:29:50.371] - ========= chip flash id: ef4016 ========= [12:29:50.401] - create partition.bin, pt_new is True [12:29:50.449] - Create bootheader using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:50.450] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP0_CFG]> [12:29:50.466] - Created file len:352 [12:29:50.480] - Create bootheader using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:50.481] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP1_CFG]> [12:29:50.498] - Created file len:352 [12:29:50.505] - Create efuse using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:50.508] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[EFUSE_CFG]> [12:29:50.525] - Created file len:256 [12:29:50.527] - ef_sw_usage_0 not exist [12:29:50.528] - ef_sw_usage_1 not exist [12:29:50.547] - ========= sp image create ========= [12:29:50.561] - Image hash is b'a42b69b01e69c2cbb2643612895522affa7309fbc8c6a6fe122b1ad5586efab2' [12:29:50.615] - Hash ignored [12:29:50.621] - Header crc ignored [12:29:50.621] - Write flash img [12:29:50.705] - Create bootheader using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:50.706] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP0_CFG]> [12:29:50.720] - Created file len:352 [12:29:50.738] - Create bootheader using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:50.738] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP1_CFG]> [12:29:50.752] - Created file len:352 [12:29:50.762] - Create efuse using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:50.766] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[EFUSE_CFG]> [12:29:50.778] - Created file len:256 [12:29:50.779] - ef_sw_usage_0 not exist [12:29:50.781] - ef_sw_usage_1 not exist [12:29:50.801] - ========= sp image create ========= [12:29:50.897] - Image hash is b'dcb8e025c9de669bc3caa21d5a39ee3d25076fe77a22fe45968474c93df8b2e1' [12:29:50.952] - Hash ignored [12:29:50.953] - Header crc ignored [12:29:50.954] - Write flash img [12:29:50.978] - FW Header is 1620, 2476 still needed [12:29:50.982] - FW OTA bin header is Done. Len is 4096 [12:29:51.123] - BL60X_OTA_Ver1.0 [12:29:51.277] - FW OTA bin is Done. Len is 496832 [12:29:51.996] - OTA XZ file len = 286748 [12:29:51.998] - Partiton len = 0 [12:29:52.000] - Warn: fw1 xz bin size is overflow with partition table, don't create ota bin [12:29:52.001] - Remove OTA directory due to xz image fail [12:29:52.012] - FW OTA xz is Done [12:29:52.063] - Create bootheader using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:52.066] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP0_CFG]> [12:29:52.079] - Created file len:352 [12:29:52.096] - Create bootheader using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:52.097] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP1_CFG]> [12:29:52.110] - Created file len:352 [12:29:52.119] - Create efuse using F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini [12:29:52.125] - Updating data according to <F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\img_create_iot/efuse_bootheader_cfg.ini[EFUSE_CFG]> [12:29:52.138] - Created file len:256 [12:29:52.142] - ef_sw_usage_0 not exist [12:29:52.144] - ef_sw_usage_1 not exist [12:29:52.164] - ========= sp image create ========= [12:29:52.266] - Image hash is b'8cd3c67189c44e3628251f4bf99d332545588e194854794a7a64cef9f8dcf85f' [12:29:52.317] - Hash ignored [12:29:52.317] - Header crc ignored [12:29:52.318] - Write flash img [12:29:52.342] - Warning: factory file is not programed to flash [12:29:52.343] - ========= eflash loader config ========= [12:29:52.925] - Version: eflash_loader_v2.4.2 [12:29:52.925] - Program Start [12:29:52.926] - ========= eflash loader cmd arguments ========= [12:29:52.926] - F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\eflash_loader/eflash_loader_cfg.ini [12:29:52.926] - Config file: F:\Downloads\Sipeed\bl_iot_sdk\tools\flash_tool\chips\bl808\eflash_loader/eflash_loader_cfg.ini [12:29:52.930] - serial port is COM19 [12:29:52.933] - cpu_reset=False [12:29:52.934] - chiptype: bl808 [12:29:52.937] - ========= Interface is uart ========= [12:29:52.940] - com speed: 2000000 [12:29:52.941] - Bootrom load [12:29:52.941] - ========= get_boot_info ========= [12:29:52.941] - ========= image get bootinfo ========= [12:29:53.256] - tx rx and power off, press the machine! [12:29:53.258] - cutoff time is 0.05 [12:29:53.317] - power on tx and rx [12:29:54.312] - reset cnt: 0, reset hold: 0.05, shake hand delay: 0.1 [12:29:54.313] - clean buf [12:29:54.328] - send sync [12:29:54.746] - ack is b'' [12:29:54.747] - retry [12:29:55.029] - tx rx and power off, press the machine! [12:29:55.029] - cutoff time is 0.05 [12:29:55.091] - power on tx and rx [12:29:56.087] - reset cnt: 0, reset hold: 0.05, shake hand delay: 0.1 [12:29:56.087] - clean buf [12:29:56.103] - send sync [12:29:56.524] - ack is b'' [12:29:56.525] - retry [12:29:56.807] - tx rx and power off, press the machine! [12:29:56.809] - cutoff time is 0.05 [12:29:56.870] - power on tx and rx [12:29:57.869] - reset cnt: 0, reset hold: 0.05, shake hand delay: 0.1 [12:29:57.871] - clean buf [12:29:57.883] - send sync [12:29:58.305] - ack is b'' [12:29:58.306] - retry [12:29:58.314] - shake hand fail [12:29:58.316] - ######################################################################## [12:29:58.316] - 请按照以下描述排查问题： [12:29:58.316] - Boot pin是否上拉到板子自身的3.3V，而不是外部的3.3V [12:29:58.317] - UART RX是否连接到USB转串口的TX引脚 [12:29:58.317] - UART TX是否连接到USB转串口的RX引脚 [12:29:58.317] - 在使用烧录软件进行烧录前，是否在Boot pin拉高的情况下，使用Reset/Chip_En复位了芯片 [12:29:58.318] - 烧录软件所选择的COM口，是否是连接芯片的串口 [12:29:58.318] - 烧录软件上选择的波特率是否是USB转串口支持的波特率 [12:29:58.318] - 3.3V供电是否正常 [12:29:58.318] - 板子供电电流是否正常(烧录模式下，芯片耗电电流5-7mA) [12:29:58.319] - ######################################################################## [12:29:58.319] - shake hand fail [12:29:58.430] - {"ErrorCode": "0050","ErrorMsg":"BFLB IMG LOAD SHAKEHAND FAIL"} [12:29:58.431] - Burn Retry [12:29:58.433] - 0 [12:29:58.434] - Burn return with retry fail

Is the boot btn keepping pressed when you click the rest btn? It shows that you may have not made it to the download mode. So failed in communication with the bootrom firmware.

[x893]

Hello, i connect both OTG and UART cables, press both side buttons and RST. See USB Mass Storage device in Device Manager (Windows 10 22H2) with yellow mark and message on terminal

[taorye]

Hello, i connect both OTG and UART cables, press both side buttons and RST. See USB Mass Storage device in Device Manager (Windows 10 22H2) with yellow mark and message on terminal

To use bl_dev_cube, you need make the chip into the boot mode by keepping boot btn pressed followed by clicking the reset btn. They are all on the top side, near the usb port.

The combination of both side buttons and the reset button will make chip boot 'normally', into the custom bootloader provided by Sipeed to let everybody can avoid downloading the additional software just for flashing and can upload your firmware easily by drag-n-drop.

[x893]

Of course I try BOOT+RST and try download via UART. You can see error screen above (black text on red - BFLB SET CLOCK PLL)FAIL)

[x893]

I try U-disk under linux and i see ` [ 100.203204] usb 1-1.3: new high-speed USB device number 3 using xhci_hcd [ 100.333861] usb 1-1.3: New USB device found, idVendor=ffff, idProduct=ffff, bcdDevice= 0.01 [ 100.333884] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 100.333897] usb 1-1.3: Product: Mass Storage [ 100.333909] usb 1-1.3: Manufacturer: Sipeed [ 100.333921] usb 1-1.3: SerialNumber: 20221014 [ 100.344800] usb-storage 1-1.3:1.0: USB Mass Storage device detected [ 100.351418] scsi host0: usb-storage 1-1.3:1.0 [ 101.393425] scsi 0:0:0:0: Direct-Access Bouffalo Product 0.01 PQ: 0 ANSI: 2 [ 101.394989] sd 0:0:0:0: [sda] 11718 512-byte logical blocks: (6.00 MB/5.72 MiB) [ 101.395432] sd 0:0:0:0: [sda] Write Protect is off [ 101.395451] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 [ 101.395746] sd 0:0:0:0: [sda] No Caching mode page found [ 101.395762] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 101.399430] sda: sda1 [ 101.401143] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 101.430483] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 125.070819] w1_master_driver w1_bus_master1: Attaching one wire slave 00.400000000000 crc 46 [ 125.078696] w1_master_driver w1_bus_master1: Family 0 for 00.400000000000.46 is not registered.

sudo mount /dev/sda1 /tmp/m1s/

ls -la /tmp/m1s/ total 20 drwxr-xr-x 2 root root 16384 Jan 1 1970 . drwxrwxrwt 11 root root 4096 Dec 19 18:15 ..

`

[x893]

I reveiew and think that problem in ` static bool usbd_get_descriptor(uint16_t type_index, uint8_t *data, uint32_t len)

...

USB_LOG_ERR("descriptor <type:%x,index:%x> not found!\r\n", type, index);

...

` under Win10 22H2 (or may be early)

USB_DESCRIPTOR_TYPE_DEVICE_QUALIFIER not supported in static bool usbd_get_descriptor(uint16_t type_index, uint8_t *data, uint32_t len)

[x893]

No fix yet ?

[sakumisu]

Of course I try BOOT+RST and try download via UART. You can see error screen above (black text on red - BFLB SET CLOCK PLL)FAIL)

If flashed fail, just try again. This means your bootrom is not ok, please boot+rst again.

[x893]

If flashed fail, just try again. This means your bootrom is not ok, please boot+rst again.

Message SET CLOCK PLL FAIL

[sakumisu]

I know, only try again. Or your uart port is poor then uart data is incorrect.

[x893]

I know, only try again. Or your uart port is poor then uart data is incorrect.

I use M1s Dock with integrated USB-UART

[xb1g]

i also have the same problem, sometimes it just froze at shake hand success. both cli and gui