PT Check Fail

[9nut]

I'm using BLDevCube 1.8.3 on Ubuntu 22.04, and the most recent firmware I downloaded from here. When trying to upload the firmware in the MCU section, I get the error below. For comparison, it succeeds in downloading bl808-firmware.bin in the IOT section. Although I don't think it is related to UART, I tried several different USB-UART (CH340G , PiPico/Picoprobe and STM32 BluePill/Blackmagic), all with the same result.

[00:58:48.846] - EFUSE_CFG
[00:58:48.848] - BOOTHEADER_GROUP0_CFG
[00:58:48.849] - BOOTHEADER_GROUP1_CFG
[00:58:48.864] - Create bootheader using /home/xxx/BL808/chips/bl808/img_create_mcu/efuse_bootheader_cfg.ini
[00:58:48.865] - Updating data according to </home/xxx/BL808/chips/bl808/img_create_mcu/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP0_CFG]>
[00:58:48.871] - Created file len:352
[00:58:48.875] - Create bootheader using /home/xxx/BL808/chips/bl808/img_create_mcu/efuse_bootheader_cfg.ini
[00:58:48.876] - Updating data according to </home/xxx/BL808/chips/bl808/img_create_mcu/efuse_bootheader_cfg.ini[BOOTHEADER_GROUP1_CFG]>
[00:58:48.881] - Created file len:352
[00:58:48.885] - Create efuse using /home/xxx/BL808/chips/bl808/img_create_mcu/efuse_bootheader_cfg.ini
[00:58:48.888] - Updating data according to </home/xxx/BL808/chips/bl808/img_create_mcu/efuse_bootheader_cfg.ini[EFUSE_CFG]>
[00:58:48.893] - Created file len:256
[00:58:48.900] - Image create path: /home/xxx/BL808/chips/bl808/img_create_mcu
[00:58:48.901] - Config file: /home/xxx/BL808/chips/bl808/img_create_mcu/img_create_cfg.ini
[00:58:48.908] - img already have bootheader
[00:58:48.908] - Write flash img direct
[00:58:48.914] - img already have bootheader
[00:58:48.915] - Write flash img direct
[00:58:48.917] - ========= eflash loader config =========
[00:58:48.927] - pt check fail, chips/bl808/img_create_mcu/bootinfo_group1.bin is overlayed with chips/bl808/img_create_mcu/img_group0.bin in flash layout, please check your partition table to fix this issue
[00:58:48.928] - PT Check Fail

[eeucalyptus]

I think you might have set one of the firmware binaries to group 1, at least that's what your log says. As said in the README instructions, they both have to be set to group0.

[9nut]

Thank you! That was it. I should not try things so late at night :(