Why is there a missing block in the .lst file?

[Matro]

Hi everybody,

A strange thing happens when I compile my code.
The whole ASM code corresponding to the "write_program_memory()" function doesn't appear in the ".lst" file.
The memory area seems to be reserved but nowhere is the generated ASM.
The code seems present in the hex file too.
It's really a problem to look for bugs.

Is that normal? Or a bug of the compiler? Or something else?...

I use CCS 4.069.

Thanks for your answers.
Matro.

[Ttelmah]

At the top of the include file for your processor, there will be a line '#nolist'. Simply remove this line, or use // to 'remark' it out.
With this present, assembler will not be shown for any of the internal functions (arithmetic, I/O etc.).
It makes it simpler to see the assembler for _your_ code, but leaves these odd 'holes'.

Best Wishes

[Matro]

Hi Ttelmah,
Once again your help is very appreciated because accuracy & efficiency. ;-)
Simply what I need. Exactly!

Thanks a lot. And maybe see you soon. :-D
Matro.

[Matro]

Actually I've another question following the last one.
My problem is that I need to place a bootloader in a specific memory area.
This part is OK.
And the bootloader uses of course the built-in "write_program_memory()".
Here comes the problem. This built-in function uses itself a function that it calls. But this sub-function is placed anywhere in memory by the compiler. And of course at a location where the bootloader overwrite it.
The #ORG of the bootloader function seems not to be sufficient and I can't find nowhere a way for "forcing" the memory location of this sub-function.

Is there a way to do so?
Hoping the explanation was OK.
Thanks in advance,
Matro.

[Ttelmah]

Look at the keyword 'default' for the #org statement.
Without this, the defined range will only be used for your code, not the cmpiler 'default' functions.

Best Wishes

[Matro]

Hi Ttelmah,
your tip sounded ok but I tried it and unfortunately it didn't solve the problem.
This behavior of the compiler is very embarrassing.

Thanks again for your help.
Matro.

[Ttelmah]

What syntax are you using?.
You do realise, you have to declare the memory area you want to use, and add the 'default' to the same statement?.
The way it works:

#org start,end

Puts the next routine into the specified area.

#org start,end DEFAULT

Puts the next routine _including internal compiler routines_, into the specified range.

#org DEFAULT

Turns this off.
The version with default included, definately works.

Best Wishes

[Matro]

I did so,but it didn't work.
I will try to provide a sample code for demonstrating.
Matro.

[Matro]

The following code demonstrates the problem:

[Ttelmah]

Feature.....
You are declaring 'bootloader', before you change the default declarations. Though 'bootloader' itself will go 'inline', and therefore be inside the declared area, anything it calls, won't be put in the area. If you want the bootloader functions to be at a specific address, _it_ needs to have a default declaration before it.
You can (for instance), declare a different memory area, with the default option, and still declare bootloader as 'inline'. Bootloader will be put in the second declared area as 'inline', while the system calls it makes wil be put in the area declared before the bootloader.

Best Wishes

[Matro]

OK. Thanks for that.
The problem has actually been solved by writing my own "write_program_memory()" and it save a lot of space because I adapted it to my needs. ;-)
Thanks for all tips and advices.
See you.
Matro.