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

Adding bootloader binary to C project

Ian Mellor

Hi all,

I see this is a common problem, I am using uVision 4 with an ARM 7.

I have a bootloader at location 0x0 and application code that is located at 0x800.
I currently use HEX2BIN and BIN2HEX to merge the files before I can downloaded them to the target.
However to I would like to debug the application with the bootloader included as a binary.
Is there a way the linker can add the bootloader binary (or HEX file) during the build?
I would like to keep the two projects separate.
I'm looking at using bin2c.exe to create a header file with the bootloader as a const array, but this seems silly when it's the linkers job to combine object and library files together, why not also link an external hex or bin file.

Any ideas please.

Thanks,

Ian

Parents
  • 0 in reply to Ian Mellor

    The thing you're overlooked so far is that you can do much more than just loading the application when you start a debug session. That's what the debugger has an "init script" for.

    One of many things you can do in there is load additional data (e.g. your bootloader) into the target, before you start the program. You could even go one step further and load the debuggable image of the bootloader, so you would have symbols of both your bootloader and your application available in the same debug session.

Reply
  • 0 in reply to Ian Mellor

    The thing you're overlooked so far is that you can do much more than just loading the application when you start a debug session. That's what the debugger has an "init script" for.

    One of many things you can do in there is load additional data (e.g. your bootloader) into the target, before you start the program. You could even go one step further and load the debuggable image of the bootloader, so you would have symbols of both your bootloader and your application available in the same debug session.

Children
No data