topic S-Record output size in CodeWarrior for MCU

S-Record output size

ahmedfouda — Tue, 29 Jun 2010 19:03:54 GMT

Hi,

I'm trying to build my application using CodeWarrior.

I don't have an entry function to my software so that I set INIT to entry in my prm file, where entry is an empty function.

When I do this, the resulting map file doesn't contain any of the functions in my software.

I searched for this problem and I used the NAME .. END option in the prm file to include all objects in my *.o files.

Now the generated map file includes all functions, but the .sx file is very small to include the code of the functions. (It's just one line of HEX)

Do you have any solution for this.??

Re: S-Record output size

Lundin — Tue, 29 Jun 2010 20:29:22 GMT

> I don't have an entry function to my software

You must have one, obviously, or the program wouldn't make any sense.

By default in CW, the entry function is main() for C programs. If you write assembler you must use the INIT syntax as you describe. Alternatively you can also define one of your own by writing your own reset ISR if you wish.

> so that I set INIT to entry in my prm file, where entry is an empty function.

Why would you use an empty function for? Don't you want your program to do anything?

NAMES... END shouldn't be necessary. If you want to force linking of your functions or variables, their names should be placed inside ENTRIES... END.

Re: S-Record output size

ahmedfouda — Tue, 29 Jun 2010 21:18:15 GMT

Hi,

I don't need an entry function because I compile this code just to get the HEx output and then put this hex output in memory and access it by pointers.

So I'm sure that i don't need entry.

I tried to use ENTRIES .. END, but the resulting .sx file doesn't contain any code.

Re: S-Record output size

CompilerGuru — Tue, 29 Jun 2010 22:00:23 GMT

The linker only actually allocates functions which are referred, typically by starting at _Startup and then main.

So everything called by main gets allocated. If your main/_Startup do not actually use your objects, then they do not get allocated.

I guess you have some vector table which contains function pointer to all interrupt handlers (or some other kind of how your code/data gets referred to). Add that object into a ENTRIES XXX END block so it becomes an additional root for the linker.

Daniel

Re: S-Record output size

CompilerGuru — Tue, 29 Jun 2010 22:03:34 GMT

According to the map file, are your functions linked or not (do they have an address?)?

If not, then I would still think ENTRIES is the way to go.

If they are linked, check how the srecord gets generated. And that you look at the right srecord file.

Daniel

Re: S-Record output size

ahmedfouda — Tue, 29 Jun 2010 22:16:25 GMT

Hi,

Thanks, It's working now usint ENTRIES XXX END