• State Not Answered
  • Locked Locked
  • Replies 17 replies
  • Subscribers 22 subscribers
  • Views 3649 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Reset after success remote update

Kobi Hayun

Hi All,

I managed to update my FW, but the new FW is not start to work.

I checked that the new FW is burn correctly (I verify it with uVision3 with the verify option at the utility settings).

Please advice Kobi

Parents
  • 0 in reply to Kobi Hayun

    Hi,

    As I wrote before, I managed to burn my new FW instead of the old one, but the new FW is not restarts.
    I checked That the new FW is correct (Validate it with ULINK2). As far as I understand, the bootloader checks if the program signature is valid.
    My new FW is stuck at the LPC bootloader and do not run the new FW(probably because the program signature is wrong).

    Is the program signature is included with the INTEL hex file?
    If no, how do I updates it?

    Please advice Kobi

Reply
  • 0 in reply to Kobi Hayun

    Hi,

    As I wrote before, I managed to burn my new FW instead of the old one, but the new FW is not restarts.
    I checked That the new FW is correct (Validate it with ULINK2). As far as I understand, the bootloader checks if the program signature is valid.
    My new FW is stuck at the LPC bootloader and do not run the new FW(probably because the program signature is wrong).

    Is the program signature is included with the INTEL hex file?
    If no, how do I updates it?

    Please advice Kobi

Children
  • 0 in reply to Kobi Hayun

    The Keil tools will automagically create a checksum for the interrupt vector table. As long as you download that address range, the NXP boot loader should be able to sum all vectors and get a total of zero. This indicates that there is an application loaded, and the NXP boot loader will then start your firmware.

    If your download doesn't contain the interrupt vector table - or downloads it to the wrong address - the NXP boot loader will (as intended) wait in an infinite loop for anyone to connect on the monitor port and feed it a new firmware.