Ok, so the PRU's are basically Cortex M3's. Which means they would probably use the arm-none-eabi toolchain . . . or arm-none-eabi-size as the executable. This tool is the correct way to get to code and data sizes. Explained somewhat here: https://mcuoneclipse.com/2013/04/14/text-data-and-bss-code-and-data-size-explained/
*Do you mean by gcc tool the compiler itself?* > No, when someone refers to "the toolchain" or a tool *of* "the toolchain" they're talking about the gnu compiler collection ( gcc ) not the gcc C compiler . . . Anyway, the gcc toolchain is a set of executable all used for the purpose of programing a specific hardware architecture(s). gcc, g++, object-copy, size, gdb, etc are all tools in the gcc toolchain( and there are more ). For instance the following is the gcc toolchain for the MSP430: 02/27/2014 01:39 PM 581,646 msp430-addr2line.exe 02/27/2014 01:39 PM 601,614 msp430-ar.exe 02/27/2014 01:39 PM 797,198 msp430-as.exe 02/27/2014 01:39 PM 299,022 msp430-c++.exe 02/27/2014 01:39 PM 580,622 msp430-c++filt.exe 02/27/2014 01:39 PM 297,486 msp430-cpp.exe 02/27/2014 01:39 PM 51,726 msp430-elfedit.exe 02/27/2014 01:39 PM 924,062 msp430-g++.exe 02/27/2014 01:39 PM 898,317 msp430-gcc-4.6.3.exe 02/27/2014 01:39 PM 898,317 msp430-gcc.exe 02/27/2014 01:39 PM 55,822 msp430-gcov.exe 02/27/2014 01:39 PM 4,091,918 msp430-gdb.exe 02/27/2014 01:39 PM 647,694 msp430-gprof.exe 02/27/2014 01:39 PM 789,518 msp430-ld.bfd.exe 02/27/2014 01:39 PM 789,518 msp430-ld.exe 02/27/2014 01:39 PM 592,398 msp430-nm.exe 02/27/2014 01:39 PM 749,582 msp430-objcopy.exe 02/27/2014 01:39 PM 826,382 msp430-objdump.exe 02/27/2014 01:39 PM 601,614 msp430-ranlib.exe 02/27/2014 01:39 PM 351,758 msp430-readelf.exe 02/27/2014 01:39 PM 565,774 msp430-run.exe 02/27/2014 01:39 PM 583,694 msp430-size.exe 02/27/2014 01:39 PM 582,670 msp430-strings.exe 02/27/2014 01:39 PM 749,582 msp430-strip.exe 02/27/2014 01:39 PM 906 msp430mcu-config On Sun, Jul 3, 2016 at 2:17 PM, Fabian <xy6...@gmail.com> wrote: > what would be the correct one? I took the one of filesystem. > Do you mean by gcc tool the compiler itself? Because after compiling I > don't get any information about compiled bytes or something like it. > Can I take the table of the AM335x.cmd and read the bytes of this > addresses into the pru? So at 0x0 to 0x2000 the program, after that the > DRAM etc.? > Or do I have to watch out? I get the feeling I walk more and more into the > wrong direction. > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/cfcd5e86-9654-4898-b825-3f001fe7ccc4%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/cfcd5e86-9654-4898-b825-3f001fe7ccc4%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORrHgExjmE1jhkj3fThZAhQ2Zq0BdQmEq_aaBmS1hDTQNg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
