Unable to flash firmware due to write_firmware step failing on bootloader.

[Ajay K]

The CRC errors or gone. I had to fix a line of code and I recompiled the application. Used the Multitool to generate the crc for the compiled file and I get the following error now when flashing the firmware either offline/online compilations. Any ideas as to why I am getting this error now? Again I am using dot library 4.0.1 and mbed os 6.1.0.

bootloader :> upgrade ymodem
[INFO] Starting upgrade
[INFO] Starting YMODEM file transfer
[INFO] YMODEM file transfer succeeded
[INFO] appended crc: 408270576
[INFO] calculated crc: 408270576
[ERROR] write_firmware: lseek failed
[ERROR] Flashing new firmware failed

Thanks,
Ajay.

[Ajay K]

If I power cycle the mdot, it sits in a loop and keeps printing out the following error.

[INFO] 0X7E000 bytes remaining
[INFO] 0X7C000 bytes remaining
[INFO] 0X7A000 bytes remaining
[INFO] 0X78000 bytes remaining
[INFO] 0X76000 bytes remaining
[INFO] 0X74000 bytes remaining
[INFO] 0X72000 bytes remaining
[INFO] 0X70000 bytes remaining
[INFO] 0X6E000 bytes remaining
[INFO] 0X6C000 bytes remaining
[INFO] 0X6A000 bytes remaining
[INFO] 0X68000 bytes remaining
[INFO] 0X66000 bytes remaining
[INFO] 0X64000 bytes remaining
[INFO] 0X62000 bytes remaining
[INFO] 0X60000 bytes remaining
[INFO] 0X5E000 bytes remaining
[INFO] 0X5C000 bytes remaining
[INFO] 0X5A000 bytes remaining
[INFO] 0X58000 bytes remaining
[INFO] 0X56000 bytes remaining
[INFO] 0X54000 bytes remaining
[INFO] 0X52000 bytes remaining
[INFO] 0X50000 bytes remaining
[INFO] 0X4E000 bytes remaining
[INFO] 0X4C000 bytes remaining
[INFO] 0X4A000 bytes remaining
[INFO] 0X48000 bytes remaining
[INFO] 0X46000 bytes remaining
[INFO] 0X44000 bytes remaining
[INFO] 0X42000 bytes remaining
[INFO] 0X40000 bytes remaining
[INFO] 0X3E000 bytes remaining
[INFO] 0X3C000 bytes remaining
[INFO] 0X3A000 bytes remaining
[INFO] 0X38000 bytes remaining
[INFO] 0X36000 bytes remaining
[INFO] 0X34000 bytes remaining
[INFO] 0X32000 bytes remaining
[INFO] 0X30000 bytes remaining
[INFO] 0X2E000 bytes remaining
[INFO] 0X2C000 bytes remaining
[INFO] 0X2A000 bytes remaining
[INFO] 0X28000 bytes remaining
[INFO] 0X26000 bytes remaining
[INFO] 0X24000 bytes remaining
[INFO] 0X22000 bytes remaining
[INFO] 0X20000 bytes remaining
[INFO] 0X1E000 bytes remaining
[INFO] 0X1C000 bytes remaining
[INFO] 0X1A000 bytes remaining
[INFO] 0X18000 bytes remaining
[INFO] 0X16000 bytes remaining
[INFO] 0X14000 bytes remaining
[INFO] 0X12000 bytes remaining
[INFO] 0X10000 bytes remaining
[INFO] 0XE000 bytes remaining
[INFO] 0XC000 bytes remaining
[INFO] 0XA000 bytes remaining
[INFO] 0X8000 bytes remaining
[INFO] 0X6000 bytes remaining
[INFO] 0X4000 bytes remaining
[INFO] 0X2000 bytes remaining
[INFO] 0 bytes remaining
[INFO] Flashing new firmware
[ERROR] write_firmware: lseek failed
[ERROR] update_firmware: Failed to flash new firmware
[INFO] Flashing backup firmware
[ERROR] write_firmware: open failed
[ERROR] update_firmware: Failed to flash old firmwareÿ[INFO] Backing up current firmware

[Ajay K]

Any thoughts on why this issue is occurring and how this can be resolved?

Thanks,
Ajay

[Taylor Heck]

What is the bootloader’s version?

Are you able to program the module with a dev kit instead of YMODEM?

[Ajay K]

Hi Taylor,

Thanks again for taking the time to respond. The bootloader version is mentioned below:

bootloader version v0.1.6-5-g4e0ca29

I have try with a development kit. However since we have had this custom board with us for over 2 years now, this is the first time I am seeing so many issues with the bootloader and inability to flash the firmware. I am not sure if this is anything to do with the 4.0.1 dot library or the multitool firmware o/p, which is appending the CRC

Thanks,
Ajay

[Ajay K]

Any ideas as to how this can be resolved. Also if I power-up the mDot it just stays infinitely in a loop, printing debug o/p on the COM Ports as described earlier in the thread. This has completely blocked us, even though we are also tracking a ticket on this issue, it would be great if we can be unblocked at the earliest.

Thanks,
Ajay.

[Ajay K]

This is resolved for now. Needed to upgrade the MDot bootloader to version 1.0.0 for it to work. Thanks to your support team to help us resolve this.

Thanks,
Ajay

[Author]

Posts