• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 401 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

multiple hex files

Tebogo Thebe
Prodigy 80 points

Other Parts Discussed in Thread: CC2430

I'm trying to achieve the following:

1. Write multiple source code files. (*.c)

2. Compile each source code file and produce a hex file for each.

3. Program as SoC (e.g CC2430) with all the hex files.

Each source file (and consequently each hex file) will define various functions which will be used by the application (the last hex file to be programmed onto the SoC).  I don't know if this is possible.

  • 0
    Expert 1535 points

    Hi,

    if you have seperate link files for each c module, this would be possible. But the main c module have to know the entry points of the functions located in the other modules. Much work, but possible.

    But why not linking everything together into one binary?

    regards

    spachner

  • 0 in reply to spachner
    Prodigy 80 points

    The trouble is, I'm developing a an application to run on the CC2430 using a trial version of Keil IDE.  The IDE has a limit to the size of object code and hex file it can emit so I'm trying to break up the code into segments and append these segments to the chip.  I'm not trying to be miserly but I haven't much time to complete the whole thing and obtaining a full version of Keil (which is expensive) will take a while (too many administrative layers to go through).

    Is there any reading material you can recommend to help understand what it would take to achieve this feat?

    Thanks in advance

  • 0 in reply to Tebogo Thebe
    Expert 1535 points

    Hi,

    if I were you I would spent the time going through the hierachy and buy a full featured compiler. Splitting the application into several parts needs deep knowledge of the used compiler/linked and debugging is not easier, too. All this will costs a considerable amount of extra time and It seems you are in hurry to get to a running system.

    I do not know about any material to read except the compiler and linker manuals you probably already have.

    I did this to a small extend and split-up my application into just two parts: a bootloader and an application. But these two parts are not running in parallel as you would like to do, my bootloader is just starting the application and despite of this I had much to do because of the interrupt vectors which are located at fixed places as you can see in this thread below, where I described the basic concepts for writing a bootloader with an 8051 core.

    http://e2e.ti.com/forums/p/4780/18150.aspx#18150

    Probably your application does not need any interrup, then It would be easier, but which application on a SOC is not using interrupts?

    regards

    spachner