> > *until now I used the compiler of TI: clpru. I thought this is the > compiler of TI for the PRUs. That I can use the gnueabi I didn't know. The > Cores/ Prus should use hard float, so I could use gnueabihf compiler too? > (1)* > *I get the table of the sizes too (which is explained in your link). Can I > use them to get the code parts of the parts in the program?* >
So, you probably can not use the arm-none-eabi-gcc executable without heavy modification to compile executables for the PRU's, but the size executable might still work. It depends on the binary file type. You have elf, and if I recall correctly something refereed to as ihex( or intel hex files ) HOWEVER, you need to read the documentation that comes with clpru, and check out the other executable that comes with it. run clpru --help to get all the usage cmd switches etc, and it may even tell you the proper code and data sections(sizes ) its self. I can create a pointer at the 0x0000 address of my program and start > reading until 0x2000 and get the Flash bytes. After that I read the dram > bytes for the Pru0, after that for the PRu1 and so on. > Am I correct? Or is there another way of reading the data out of the > program? > I have no idea what you're asking me. If you're asking about being able to read from various addresses in memory. Yes you can. How, or why is up to you. On Sun, Jul 3, 2016 at 2:52 PM, Fabian <[email protected]> wrote: > until now I used the compiler of TI: clpru. I thought this is the compiler > of TI for the PRUs. That I can use the gnueabi I didn't know. The Cores/ > Prus should use hard float, so I could use gnueabihf compiler too? (1) > I get the table of the sizes too (which is explained in your link). Can I > use them to get the code parts of the parts in the program? > For example I got this: > > PAGE 0: > PRU_IMEM 00000000 00002000 00000098 00001f68 RWIX > > PAGE 1: > PRU_DMEM_0_1 00000000 00002000 00000100 00001f00 RWIX > PRU_DMEM_1_0 00002000 00002000 00000000 00002000 RWIX > > PAGE 2: > PRU_SHAREDMEM 00010000 00003000 00000000 00003000 RWIX > PRU_INTC 00020000 00001504 00000000 00001504 RWIX > PRU_CFG 00026000 00000044 00000044 00000000 RWIX > PRU_UART 00028000 00000038 00000000 00000038 RWIX > PRU_IEP 0002e000 0000031c 00000000 0000031c RWIX > PRU_ECAP 00030000 00000060 00000000 00000060 RWIX > RSVD27 00032000 00000100 00000000 00000100 RWIX > RSVD21 00032400 00000100 00000000 00000100 RWIX > > .... > > I can create a pointer at the 0x0000 address of my program and start > reading until 0x2000 and get the Flash bytes. After that I read the dram > bytes for the Pru0, after that for the PRu1 and so on. > Am I correct? Or is there another way of reading the data out of the > program? > > > Thanks for your help and taking your time for answering > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/ae898a55-cc2c-4bfd-b406-7013bb19162c%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/ae898a55-cc2c-4bfd-b406-7013bb19162c%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORpando%2BGNaFJ4S4yVsK2XD-Tvjh%2Bo0e5fni6ZoBh4nizA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
