bug #28
closed
Slave Display failing on firmware programming
Added by dishant nalwaya 3 months ago.
Updated 3 months ago.
Description
After successful handshake when the firmware programming starts it is failing for slave display
Slave display is part of bootloader version 1.2
- Assignee changed from dishant nalwaya to Shuchi Tailor
The Slave Bootloader V1.02 is developed similar to Display Bootloader V1.02
Slave bootloader had been tested before (Feb 2026) with successful uploading of Slave V11_04 and V11_05 Binfiles on slave displays. The same display had also been tested with the master hardware setup. the logs of the same can be found on the Bootloader Server.
Currently, firmware programming of any Slave Bin file is failing from the SBC, including the older tested binfiles from server as well as new generated binfiles. But on the other hand same binfiles are successfully getting uploaded from direct commands from Command Prompt from the local PC locations.
There are a multiple possibilities for this problem:
- Binfile is getting corrupted on the server
- Slave Bootloader Project is getting corrupted
- Multiple files are getting overlapped on server
- Microcontroller memory is getting overlapped
All of the above possibilities needs to be studied and discussed thoroughly.
- % Done changed from 0 to 100
There are two delays from the bootloader application side
- 4 seconds delay before sending the 512 enc bytes packet from bootloader to display
- 5 seconds delay before the actual programming starts
So from Bootloader application side 2nd Delay is changed from 5 sec to 6 sec and the programming section where it was failing was successful the moment it is again changed to 5 sec it fails.
As of now programming is successful for Slave bootloader and Slave Binfile.
- Status changed from ongoing to done
Also available in: Atom
PDF