This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

enclose bootloader code in project

Other Parts Discussed in Thread: TMS320F28377S

Hi, 

i have written a custom bootloader for a tms320f28377s project. It is developed as a stand alone project.

I was wondering if it is possible to embed this bootloader .out file in another project ? So when i am developping the new project (and want to have the bootloader available) and debug it, the bootloader (uses Flash A) gets flashed to the target together with the new project code (uses anything but flash A). 

Thanks 

Jan

  • Jan,

    You can keep the two projects seperate and still do what you want. First, load each program seperately. For bootloader, you have the loader only erase flash sector A, and for your main app you have the loader (e.g., CCS) erase all the sectors except sector A. then when you're debugging, you can use Program->Load_Symbols with the .out file you need to debug. You can switch back and forth between debugging the two projects this way without actually changing the flash contents.

    - David
  • thank you for your answer David.
    So i suppose combining the 2 isn't possible ? It would be handy in some cases but it is not really necessary...
  • I don't think you can directly combine two .out file. Not sure why you would want to. You went through the trouble of making the bootloader and main app two seperate projects. You could always create a single project if you wanted to and build it.

    Besides "Load symbols" as I described, you can also do "Add symbols" (i.e., load the first project symbols, add the second project symbols). This will keep both sets of symbols in the debugger for your session.

    Regards,
    David
  • Couldn't you just incorporate the bootloader code into your application?

  • yes off course. I was trying to keep the two separate so the bootloader has no influence what so ever on the main application (memory space, stack, heap etc...). If i combine the two then there is one initialization (_c_int00) routine for the bootloader and the main application.
    It seemed nice to be able to combine the two because not erasing flash sector A is a setting in code composer. So i expect to get at least some telephone call's "Why isn't your bootloader working ?" "did you erase it ?" But ok, this isn't worth too much hassle...
    Thanks again for the help.
    Jan