Nico, There are two prerequisites for your PRU firmware to be loaded by the remoteproc d river: 1. PRU firmware image must be in ELF format. Only TI's clpru and the unofficial G NU PRU toolchain support this. 2. PRU firmware must include a ".resource_table" ELF section containing a resourc e table.
You cannot use PASM with remoteproc because PASM cannot output ELF. Here is a GNU assembler example that can be loaded and executed by remoteproc: htt ps://github.com/dinuxbg/pru-gcc-examples/blob/master/blinking-led/pru/main1. S . Yo u should be able to write something similar for TI's clpru assembler. But as others have pointed, it is more sensible to start with C and optimize only the critical p arts of your program in assembly. Regards, Dimitar On Friday, February 19, 2016 at 9:04:30 PM UTC+2, Nicolas Dammin wrote: > > > Hi, > > I'm using the AM335X Starter Kit from TI with an AM3359 SoC and I use the > TI Processor SDK Linux version 02.00.01.07. I managed to get remoteproc > driver working, then I removed the Display module and used the flatflex > connector to breakout some GPIOs of PRU1 to hook up some LEDs. I wrote a > blink-led firmware in CCS v6 as described in the PRU HandsOn Lab and > successfully bootet the PRU1 to let my LEDs blink. > > Now I need to write a very fast code so I have to write it in Assembly > language. I would like to use the AM335x PRU-ICSS Reference Guide to write > my code and use the PASM compiler. > > Is it possible to write pure assembler code like with the PASM and make > the code work for the newer remoteproc? Or can I write assembly code in > CodeComposer Studio with the TI compiler? I couldn't figure out yet how I > can do that. Is there a Tutorial somewhere? > > I read that TI does not support PRU so good so this is why I ask here. > > Regards > Nico > -- 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]. For more options, visit https://groups.google.com/d/optout.
