realppae

Hello, Are you asking me how to know the start memory address and their size for each CODE/DATA/MEASUREMENT? Simple answer : Please check such memory area with XCP integrator. Detailed answer : Actually such information is coming from 1) MCU type, 2) SW developers decide it. For example, if you use Tricore, usually Measurement area start from 0x7000_0000 or 0x6000_0000, or even 0x5000_0000. It's exact available size is written from Tricore's User Guide PDF file. In case of MPC5777C, maybe 0x4000_0000~0x4007_FFFF....

Hi, I haven't shared source code of AutoExtractGui - actually it's not ready to share with others. But ProF Builder is somehow better, so I uploaded it's source code. The AutoExtractGui does not read existing A2L, but it reads ELF because it always create NEW a2l. If you are having trouble of creating new A2L then please send me the ELF with AEC file (memory segment, XCP config, ... configuration) so that I reproduce the same issues you are having and try to solve / improve.

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...

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

Hi, 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. 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....

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.