topic Re: File of addresses of all labels in project in LPCXpresso IDE

File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:16 GMT

Content originally posted in LPCWare by cwpjr on Mon Feb 04 19:05:53 MST 2013
After a forum search for "link map" I didn't get what I was looking for. The .map file created normally is a good outline of sections.
I don't know the term for an output that gives addresses of all the labels in the various section....

I need a file that shows me the addresses of all the labels in my downloaded code to aid in debugging.

I ask for this because in the debugger I see no info on the addresses, which would be a 'dynamic' version of what I am requesting. Either an output file or better the dynamic info in the debug session I really need.

I am making progress in assembly but am hindered by no visibility of this info.

Thanks in advance!

Clyde

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:17 GMT

Content originally posted in LPCWare by MikeSimmonds on Mon Feb 04 23:13:13 MST 2013
[FONT=Trebuchet MS][SIZE=1]Try the readelf command line utility.
Redirect the output to a file as there is usually a lot.

E.g. readelf -s MyProg.elf > symlist.txt
You may want to add -wp for 'public' names.
readelf -s -wp MyProg.elf > myList.txt

If you are into scripting languages (I am not) then
I am sure you can sort, filter, reformat etc.

readelf with no args prints a usage and is documented
(I think) with binutils. It is definitely a GNU utility.

This may not be absolutely all labels, but it is certainly of interrest.

Cheers, Mike

[/SIZE][/FONT]

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:18 GMT

Content originally posted in LPCWare by MikeSimmonds on Mon Feb 04 23:16:05 MST 2013
[FONT=Verdana][SIZE=1]

Quote:
I ask for this because in the debugger I see no info on the addresses, which would be a 'dynamic' version of what I am requesting. Either an output file or better the dynamic info in the debug session I really need.

Shocking omission, most other debuggers I have used have a symbol table command.

Mike
[/SIZE][/FONT]

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:18 GMT

Content originally posted in LPCWare by wrighflyer on Tue Feb 05 06:04:49 MST 2013
readelf is a pretty "raw" way to do this. The GNU binutils tool for examining symbolic information is nm:

C:\Documents and Settings\asl\My Documents\LPCXpresso\workspace\lpc8test1\Debug>\nxp\LPCXpresso_5.0.14_1109\lpcxpresso\t
ools\bin\arm-none-eabi-nm.exe lpc8test1.axf
00000150 W BOD_IRQHandler
00000150 W CMP_IRQHandler
000002fc T CRP_WORD
0000058c T GPIOInit
000005c8 T GPIOSetBitValue
00000610 T GPIOSetDir
000000d8 W HardFault_Handler
00000150 W I2C_IRQHandler
00000150 W IntDefaultHandler
00000150 W MRT_IRQHandler
000000d4 W NMI_Handler
000000dc W PendSV_Handler
00000108 T ResetISR
00000150 W SCT_IRQHandler
00000150 W SPI0_IRQHandler
00000150 W SPI1_IRQHandler
         w SVC_Handler
0000014c T SVCall_Handler
00000300 T SwitchMatrix_Init
000000e0 W SysTick_Handler
000004ec T SystemInit
00000150 W UART0_IRQHandler
00000150 W UART1_IRQHandler
00000150 W UART2_IRQHandler
00000150 W WDT_IRQHandler
00000150 W WKT_IRQHandler
00000300 T __CRP_WORD_END__
000002fc T __CRP_WORD_START__
000000cc T __bss_section_table
000000d4 T __bss_section_table_end
000000c0 T __data_section_table
000000cc T __data_section_table_end
000006e0 A __exidx_end
000006e0 A __exidx_start
00000670 W __main
000000d4 T __section_table_end
000000c0 T __section_table_start
00004000 A __top_MFlash16
10001000 A __top_RamLoc4
00000670 T __weak_main
10000000 B _bss
10000000 T _data
1000000c B _ebss
10000000 T _edata
1000000c N _end_noinit
10000000 N _end_uninit_RESERVED
000006e0 A _etext
1000000c N _noinit
10001000 A _vStackTop
000000f6 T bss_init
000000e4 T data_init
00000000 T g_pfnVectors
10000000 b i.4421
10000008 b j.4422
10000004 b k.4423
00000378 T main
00000344 T readComparator
00000678 T strncpy

the --size-sort option is particularly useful when you are trying to find all the "bloat"

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:19 GMT

Content originally posted in LPCWare by cwpjr on Thu Feb 07 17:03:09 MST 2013
Thanks for the 2 binutil suggestions. I also thought there might be option flags for the linker. I can research these items.

So now what searches or docs would get me info on adding say the 2 binutils commands to the build, and how to change the linker flags in the build?

Cheers, Clyde

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:20 GMT

Content originally posted in LPCWare by TheFallGuy on Fri Feb 08 00:49:53 MST 2013
Try the help shipped with the product. All compiler and binutils docs are provided.

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:20 GMT

Content originally posted in LPCWare by cwpjr on Fri Feb 08 17:14:04 MST 2013

Quote: TheFallGuy
Try the help shipped with the product. All compiler and binutils docs are provided.

I was hoping for some relevant search terms. I mean that I can search and find the compiler and binutils docs with their command line arguments, but my searches for how to change the IDE settings that issue the command line(s) invoking the build have not told me about the eclipse side where the command line invocations are encapsulated in LPCXepresso IDE.

I hope this is not an "Eclipse" conceptualization domain error on my part but if it's so just let me know, k? :)

Clyde

P.S. RE the underlying makefiles which are visible in the Dev Env Filesystem, would the IDE barf if I modify any of these files it runs against? How does LPCx run against the files? Are these supported question? vs Eclipse stuff? I suspect the suspenders are scripts that act like a *nix guy and invoke whats needed to complete a task. Like the task we all click as a button "Build Projectx".

So I'd think an IDE would have menu items like "construct command line to add to the build" / "Modify command lines in the (xcurrent) build"

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:21 GMT

Content originally posted in LPCWare by Ex-Zero on Fri Feb 08 18:22:11 MST 2013
Just add nm command to your Post-Processing :eek:

See: http://www.support.code-red-tech.com/CodeRedWiki/PostProcessApp

like:

Quote:

arm-none-eabi-size "${BuildArtifactFileName}"; arm-none-eabi-objcopy -O binary "${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin" ; checksum -p ${TargetChip} -d "${BuildArtifactFileBaseName}.bin";[COLOR=Red] arm-none-eabi-nm "${BuildArtifactFileBaseName}.axf" >"${BuildArtifactFileBaseName}.sym";
[/COLOR]

[COLOR=Red]
[/COLOR]

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:21 GMT

Content originally posted in LPCWare by cwpjr on Fri Feb 08 18:26:58 MST 2013
Title is in case it helps others.
Thanks, Zero, A significant link in my query chain.

I'll see if I can educate myself on how i would search for this page.

Clyde

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:22 GMT

Content originally posted in LPCWare by cwpjr on Fri Feb 08 18:34:46 MST 2013
I haven't seen this for a bit. I saw this a fair bit after initial installation.

Boot LPCxpresso IDE. Open help from the menus. Do a search. Next search entered in the help window closes the help window, if not the full LPCxpresso IDE.

I had done a first search of BUILD.

Action outlined above happened when I appended search line txt box input with POST PRECESSING.

This is the same in new release as in previous. Both V5, 010 vs 100

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:23 GMT

Content originally posted in LPCWare by cwpjr on Fri Feb 08 19:05:50 MST 2013
I followed app note on how to add a executable line to BUILD -> Post Processing...
So I appended my command line after the ; in dialog box.
Looked good but did nothing...
Line is the readelf one.. The original size, objcopy, checksum all work fine still.
yES I bypassed verification that I could run this command thru my CLI but I expect the IDE to say this particular thing had a problem.

make --no-print-directory post-build
Performing post-build steps
arm-none-eabi-size "lpcm0asm.axf"; # arm-none-eabi-objcopy -O binary "lpcm0asm.axf" "lpcm0asm.bin" ; checksum -p LPC1114_302 -d "lpcm0asm.bin"; readelf -s -wp lpcm0asm.elf > myList.txt
text data bss dec hex filename
9560 0 1920 11480 2cd8 lpcm0asm.axf

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:24 GMT

Content originally posted in LPCWare by cwpjr on Fri Feb 08 19:09:13 MST 2013
This is a case where I should say I have no elf output file in my build. I thought I did, or should, and would, but I see I have .axf.
And after further examination of .../bin there is no readelf. only nm.

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:24 GMT

Content originally posted in LPCWare by MikeSimmonds on Fri Feb 08 21:36:32 MST 2013
[FONT=Palatino Linotype][SIZE=1]readelf is in the same place as all the other gnu tools:
<install dir>\lpcxpresso\tools\bin
as "arm-none-eabi-readelf.exe"

The post-processing line 'stops' at the hash '#' which
comments out anything after it. ';' separates commands.

axf [I]is[/I] elf just renamed (why, why, why).
I think this got 'inherited' from ARM (the company) / Keil terminology.
I smells a lot like "Not Invented Here" to me; but Hey! what do I know.

In the build properties, you can tell the IDE that you don't want it to
generate a makefile and/or linker scripts.
Of course you have to provide your own (and tell it where to find them).
Then, the executable extension (and other extensions) stays at what your
makefile build line says.
Also you can put whatever pre- and post-processing commands you
want directly into the makefile.

You can't do this with IDE managed makefiles because they get regenerated
at the drop of a rat (I mean [I]hat[/I])

I [I]always[/I] use this method, partly because I don't like the way the generated
makefile and linker scripts are split into multiple files, but mostly so that I
can guarantee that I can build the [I]same[/I] executable that was installed into
a customer site (maybe) 10 years earlier no matter how many releases of the
IDE there may have been since. [I archive the 'tools' directory of course.]
(I could archive the entire IDE also, but have you seen the size of the Java bloat,
and support for really old versions should not be looked for.)
Also, I want a lot more control over the link process than the managed link
will provide.

Well, here are a few things to think about (and for me to be flamed about
I expect). As always, read everything, but your own judgement is final.

Mike.

[/SIZE][/FONT]

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:25 GMT

Content originally posted in LPCWare by MikeSimmonds on Fri Feb 08 21:44:09 MST 2013
[FONT=Tahoma][SIZE=1]

Quote: cwpjr
I haven't seen this for a bit. I saw this a fair bit after initial installation.

Boot LPCxpresso IDE. Open help from the menus. Do a search. Next search entered in the help window closes the help window, if not the full LPCxpresso IDE.

[/SIZE][/FONT]

Quote: cwpjr
[FONT=Tahoma][SIZE=1]

I had done a first search of BUILD.[/SIZE][/FONT] [FONT=Tahoma][SIZE=1]

Action outlined above happened when I appended search line txt box input with POST PRECESSING.[/SIZE][/FONT] [FONT=Tahoma][SIZE=1]

This is the same in new release as in previous. Both V5, 010 vs 100[/SIZE][/FONT]

[FONT=Tahoma][SIZE=1]

[/SIZE][/FONT][FONT=Tahoma][SIZE=1]I suggest you start a new thread about this; the issue is easy to miss on the second page of a thread that started out as something quite different and not IDE related.
[/SIZE][/FONT][FONT=Tahoma][SIZE=1]

[/SIZE][/FONT]

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:25 GMT

Content originally posted in LPCWare by Ex-Zero on Sat Feb 09 01:55:46 MST 2013

Quote: cwpjr
I followed app note on how to add a executable line to BUILD -> Post Processing...
So I appended my command line after the ; in dialog box.
Looked good but did nothing...
Line is the readelf one.. The original size, [COLOR=Red]objcopy, checksum all work fine still.[/COLOR]
yES I bypassed verification that I could run this command thru my CLI but I expect the IDE to say this particular thing had a problem.

make --no-print-directory post-build
Performing post-build steps
arm-none-eabi-size "lpcm0asm.axf"; [COLOR=Red]# arm-none-eabi-objcopy -O binary "lpcm0asm.axf" "lpcm0asm.bin" ; checksum -p L[/COLOR]PC1114_302 -d "lpcm0asm.bin"; readelf -s -wp lpcm0asm.elf > myList.txt
text data bss dec hex filename
9560 0 1920 11480 2cd8 lpcm0asm.axf

I don't think so :confused:

http://www.support.code-red-tech.com/CodeRedWiki/PostProcessApp

Quote:

Additional commands may also be listed (for example to create a binary and to run a checksum command), [COLOR=Red]but be commented out (and hence not executed) by use of a # character. [/COLOR]

[SIZE=4]I've posted a working command above, which can be copied in [B][COLOR=Red]every new project without changing names[/COLOR][/B]. Is that too difficult [/SIZE]:confused:

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:26 GMT

Content originally posted in LPCWare by wrighflyer on Sat Feb 09 11:03:56 MST 2013

Quote: cwpjr
also thought there might be option flags for the linker. I can research these items.

Well there's already -Wl,-Map=foo.map that is creating a .map file. You may want to add --cref to that or just do it separately as a -Wl,--cref.

I know what you mean about Eclipse. Knowing the GNU option is "--cref" you now have a heck of a game trying to find out where in the IDE there is a tick box to say "i'll have one of those please". But like so many IDEs there's usually free entry text boxes called something like "Miscellaneous" that allow you to enter anything the IDE designers forgot.

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:27 GMT

Content originally posted in LPCWare by cwpjr on Tue Feb 12 17:23:39 MST 2013

Quote: Zero
I don't think so :confused:

http://www.support.code-red-tech.com/CodeRedWiki/PostProcessApp

[SIZE=4]I've posted a working command above, which can be copied in [B][COLOR=Red]every new project without changing names[/COLOR][/B]. Is that too difficult [/SIZE]:confused:

If you are saying ; equals # (don't execute) you still are not clear.

If it helps you deal with the frustration of people like me keep posting comments like the above with no explanation or links to what you are &^*&^ about.

I hope after that you will respond to your users/customers.

No malice meant. Clyde

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:28 GMT

Content originally posted in LPCWare by cwpjr on Tue Feb 12 17:30:04 MST 2013

arm-none-eabi-size "${BuildArtifactFileName}"; # arm-none-eabi-objcopy -O binary "${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin" ; checksum -p ${TargetChip} -d "${BuildArtifactFileBaseName}.bin"; nm lpcm0asm.axf

Tell me where in this line I have # commenting out my appended command.

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:28 GMT

Content originally posted in LPCWare by cwpjr on Tue Feb 12 17:42:06 MST 2013

Quote: MikeSimmonds
[FONT=Palatino Linotype][SIZE=1]readelf is in the same place as all the other gnu tools:
<install dir>\lpcxpresso\tools\bin
as "arm-none-eabi-readelf.exe"

The post-processing line 'stops' at the hash '#' which
comments out anything after it. ';' separates commands.

axf [I]is[/I] elf just renamed (why, why, why).
I think this got 'inherited' from ARM (the company) / Keil terminology.
I smells a lot like "Not Invented Here" to me; but Hey! what do I know.

In the build properties, you can tell the IDE that you don't want it to
generate a makefile and/or linker scripts.
Of course you have to provide your own (and tell it where to find them).
Then, the executable extension (and other extensions) stays at what your
makefile build line says.
Also you can put whatever pre- and post-processing commands you
want directly into the makefile.

You can't do this with IDE managed makefiles because they get regenerated
at the drop of a rat (I mean [I]hat[/I])

I [I]always[/I] use this method, partly because I don't like the way the generated
makefile and linker scripts are split into multiple files, but mostly so that I
can guarantee that I can build the [I]same[/I] executable that was installed into
a customer site (maybe) 10 years earlier no matter how many releases of the
IDE there may have been since. [I archive the 'tools' directory of course.]
(I could archive the entire IDE also, but have you seen the size of the Java bloat,
and support for really old versions should not be looked for.)
Also, I want a lot more control over the link process than the managed link
will provide.

Well, here are a few things to think about (and for me to be flamed about
I expect). As always, read everything, but your own judgement is final.

Mike.

[/SIZE][/FONT]

Mike, Thank you for your kind consideration. The lil flame on me about # by another was as helpful as a test that doesn't tell you the # affected every and anything following it vs just that section, or all sorts of appended stuff.

It would have been more universal to say put anything you want executed before any given thing you want to comment out.

Is that so hard. For some mindset's the answer is yes.

Thanks again, Cheers, Clyde

Re: File of addresses of all labels in project

lpcware — Wed, 15 Jun 2016 21:39:29 GMT

Content originally posted in LPCWare by ex-kayoda on Tue Feb 12 17:48:58 MST 2013
:confused:

Quote: cwpjr
arm-none-eabi-size "${BuildArtifactFileName}";[SIZE=6][COLOR=Red] [B]# [/B][/COLOR][/SIZE]arm-none-eabi-objcopy -O binary "${BuildArtifactFileName}" "${BuildArtifactFileBaseName}.bin" ; checksum -p ${TargetChip} -d "${BuildArtifactFileBaseName}.bin"; nm lpcm0asm.axf

Tell me where in this line I have # commenting out my appended command.