compatible elf format?

[Guoliang Zhang]

hi, i'm trying to generate an elf from DS32 gnu compiler for the 5777c but the elf is not recognized by the converter by stating missing .debug_abbrev section. i wonder what is the elf settings need to be setup before using this tool?

thanks
gz

[realppae]

So far I tested Windriver compiler for MPC5777C, and also Tasking/Hitek/Greenhills/ARM-GCC for Infineon/NXP/ARM MCUs.

I haven't heard anything regarding DS32 - if this AutoEx. tool does not support then I need to do some adaptation, and for such task I need the ELF file to 1) analyze, 2) do adaptation, 3) actually test with ELF.

[Guoliang Zhang]

sorry for the sooo late reply.. forgot to subsribe the topic so didn't receive the email.

i've included one from my project - the S32 is basically using the gcc compiler for power architecture. i tried the latest version it seems to accept the elf. but now the question is how to get the symbols in the elf to list in the A2L? i tried the sample file it does not generate other than the ones described in the mem sections configuration. the ultimate goal is to run xcp on the 5777c.

thank you for your generous work!
regards
gz

[realppae]

Hi,

1. Version 1.0.24 has a serious bug - it doesn't normally describe variables under some conditions, so I deleted and uploaded the fixed version 1.0.25, please use it.

2. When this tool reads ELF, basically it can see many variables with their size, type, address, ...

However the tool cannot figure out whether each of them are Measurement, Calibration or out of interest. In technical aspect, there must be decision maker to describe each single variables to /begin MEASUREMENT or /begin CHARACTERISTIC. That decision making routine mandatorily needs MEMORY_SEGMENT.

If a variable "ABC" is within measurement area, it's measurement variable.
If a variable "ABC" is within calibration area, it's calibration variable.
If a variable "ABC" is within code area, it will be ignored.
If a variable "ABC" is not within any given area, it will be ignored.

I performed the tool and the attached file is the result - based on;
code address 0x0 with size 0x10000000
var address 0x40000000 with size 0x20000000

If you need cal variables, shrink code address and add cal area within the actual FLASH area of MPC5777C.

1. To see how this tool works, please go to the menu of SW.

HELP > HOW DOES THIL TOOL BUILD A2L FROM ELF?

You can read some slides that will help your understanding.

[Guoliang Zhang]

hi, thank you very much for the help.

i tried to follow the instruction here to extract variables in this section by puting it to the mem configuration

cal_ram_wp 0x40000000 0x00002000

after recreating the filter i see it was able to get all 12 vars in there. then i clicked generate a2l button. but the a2l only contains 3 out of the 12 vars.

to facilitate the process. i've enclosed the generated files and the map file.

another question. is it allowed to change the variable type? some floating point vars are generated as ULONG, can i change it in the program?

a third question, in the last reply the included a2l has an online section, does it come with some option checked or automatic? i didn't see it in my generated a2l.

i was using asap2demo sw to inspect the a2l.

thanks
gz

[realppae]

Hi,

Looks like I should investigate the output files with elf - however I can find some chances after 1-2 weeks due to my personal reason (lunar new year holiday)

I will check when I am ready

Are they from the same elf file or did you used different elf? Maybe I need to check how my SW parses the elf and why those variables are missing

[realppae]

Hi,

Maybe you used different ELF to build the "ABC.A2L" - then I cannot do debugging since I don't have the ELF.

If you feel your issue is really important or severe then please attach the ELF here or at least email me (autoextractdeveloper@gmail.com) so that I check the internal parser of this AutoExtract SW.

Regarding "some floating point vars are generated as ULONG, can i change it in the program?",
Actually the parser always describe variable AS-IT-IS. This means the parser think those variables are ULONG but actually you did coding as "float"... this also means the parser should be checked and maybe improved to successfully read such ELF type. Maybe the compiler you are using is new to this AutoExtract SW, still it cannot normally read it's internal contents.

[Guoliang Zhang]

Hi, Thanks for the support. and happy new year~

i will regenerate a set of files tomorrow and send to you.

BR
gz