• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 22 subscribers
  • Views 872 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

How to jump somewhere in my firmware?

Bolus Deng

Hi,

I have finished concatenation boot loader and firmware codes. The boot loader can jump somewhere in firmware startup segment when I checked the signature passed in boot loader during the boot sequence.

The question is how do I debug the mechanism? [jump to firmware startup] Concatenation two different code is not supported by hardware.

Any suggestions will be fine. very thanks.

Parents
  • 0 in reply to ²erik malund

    Did you concatenate two separate stand-alone binaries, or did you let the compiler/linker create a single binary expected to contain two disjoint programs?

    More than one developer of boot loader mechanisms have managed to create binaries that shares a common set of functions, such as helper functions used by the compiler. In that case, they may test the boot sequence, and everything will look good. But at a later time, when they create a new version of the replaceable application, that application will have resulted in a move-around of the common routines, so the boot loader already in shipped units may fail after an upgrade.

    Obviously, the used test methods will differ, depending on how you merged your two applications.

Reply
  • 0 in reply to ²erik malund

    Did you concatenate two separate stand-alone binaries, or did you let the compiler/linker create a single binary expected to contain two disjoint programs?

    More than one developer of boot loader mechanisms have managed to create binaries that shares a common set of functions, such as helper functions used by the compiler. In that case, they may test the boot sequence, and everything will look good. But at a later time, when they create a new version of the replaceable application, that application will have resulted in a move-around of the common routines, so the boot loader already in shipped units may fail after an upgrade.

    Obviously, the used test methods will differ, depending on how you merged your two applications.

Children
  • 0 in reply to ImPer Westermark

    Hi Per,

    Thanks for your replied this discussion.
    I concatenate two separate stand-alone binaries[boot loader and test program like "Hello World" program]

    Our objective is to reuse OTP[one time programming] space. When I ship our boot loader in the OTP and the OTP has another enough of spaces to put our firmware code in it. My boot loader only capability is to check the newest firmware code to execute in OTP.

    Now I want to know how to test this mechanism without hardware supported.

    Thx