logo elektroda
logo elektroda
X
logo elektroda

CB2S BK7231N failed to flash Easy UART Flasher - failed with serial.BytesToRead 0 (expected 15)

MSP_Tech 39 0
ADVERTISEMENT
  • #1 21640821
    MSP_Tech
    Level 1  
    HI, I've just tried to flash OpenBK firmware on CB2S module with BK7231N chip by Easy Uart Flasher, but unfortunately it failed.
    I used Easy Uart Flasher v50 and OpenBK7231N_QIO_1.18.156 firmware.
    Photo
    Spoiler:

    CB2S BK7231N failed to flash Easy UART Flasher - failed with serial.BytesToRead 0 (expected 15)

    I managed to do backup flash, and I think it was read properly as program managed to extract OBK. But when I clicked write, program start to flash firmware and failed at address0xE3000:
    Easy Uart Flasher wrote:
    Writing sector 0xE0000... ok! failed with serial.BytesToRead 0 (expected 15)
    The beginning of buffer in UART contains data.
    Writing sector 0xE1000... Writing sector 921600 failed!
    Writing file data to chip failed.

    Log
    Spoiler:
    Getting bus success!
    Going to set baud rate setting (921600)!
    Will try to read device flash MID (for unprotect N):
    Flash MID loaded: 1560EB
    Will now search for Flash def in out database...
    Flash def found! For: 1560EB
    Flash information: mid: 1560EB, icName: TH25Q16HB, manufacturer: TH, szMem: 1000000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-FF-FF-FF
    Entering SetProtectState(True)...
    sr: 80
    sr: 680
    final sr: 680
    msk: 407c
    cw: 0, sb: 2, lb: 5
    bfd: 0
    SetProtectState(True) success!
    Going to read encryption key...
    Encryption key read done!
    Encryption key: 510fb093 a3cbeadc 5993a17e c7adeb03
    Reading file firmwares/OpenBK7231N_QIO_1.18.156.bin...
    Loaded 1220464 bytes from firmwares/OpenBK7231N_QIO_1.18.156.bin...
    Using hack to write QIO - just skip bootloader...
    ... so bootloader will not be overwritten!
    Preparing to write data file to chip - resetting bus and baud...
    Getting bus... (now, please do reboot by CEN or by power off/on)
    Getting bus success!
    Going to set baud rate setting (921600)!
    Will try to read device flash MID (for unprotect N):
    Flash MID loaded: 1560EB
    Will now search for Flash def in out database...
    Flash def found! For: 1560EB
    Flash information: mid: 1560EB, icName: TH25Q16HB, manufacturer: TH, szMem: 1000000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-FF-FF-FF
    Entering SetProtectState(True)...
    sr: 80
    sr: 680
    final sr: 680
    msk: 407c
    cw: 0, sb: 2, lb: 5
    bfd: 0
    SetProtectState(True) success!
    Going to do erase, start 69632, sec count 281!
    Erasing sector 69632... ok! Erasing sector 73728... ok! Erasing sector 77824... ok! Erasing sector 81920... ok! Erasing sector 86016... ok! Erasing sector 90112... ok! Erasing ....
    All selected sectors erased!
    Writing sector 0x11000... ok! Writing sector 0x12000... ok! Writing sector 0x13000... ok! Writing sector 0x14000... ok! Writing sector 0x15000... ok!
    ...
    Writing sector 0xDD000... ok! Writing sector 0xDE000... ok! Writing sector 0xDF000... ok! Writing sector 0xE0000... ok! failed with serial.BytesToRead 0 (expected 15)
    The beginning of buffer in UART contains data.
    Writing sector 0xE1000... Writing sector 921600 failed!
    Writing file data to chip failed.

    After that I tried to rollback, python tool, change speeds or skip key check, but no lack. It simply fails writing at some but specific to selected file address.
    Is there any way to fix this, or unit can be considered as dead?
    AI: Can you provide details about your UART wiring setup—specifically, which USB-to-serial adapter you're using, how you've connected it to the CB2S module (including voltage levels), and whether you've confirmed the connections are correct?
    UART: FTDI FT232RL adapter with 3.3V level. Connected to TX,RX of the module.
    AI: What operating system and version are you running Easy UART Flasher on, and have you installed any specific drivers or made any changes to your system environment for the flashing process?
    System: Win11, no special drivers were installed.
  • ADVERTISEMENT
ADVERTISEMENT