> > Jason: > I'm using gcc on the ARM and clpru on the PRU. Both are installed. > > What would you gain by using gcc on the PRU? > > --Mark >
Let me answer this for you Mark. You would gain nothing. The contributor of the pru gcc implementation hints that it's nothign more than a toy, and that code generated with it should be thought of nothign more than experimental. It says this right on the github project page readme.md. On Mon, Jul 11, 2016 at 6:39 PM, William Hermans <[email protected]> wrote: > Hi Mark, > > Well I do not know, what would be the simplest example that is close > enough to the traditional hello world app ? I was thinking perhaps blinking > a USR LED, since one would not have to add any additional hardware. But I > looked into that a while back, and doing this would not be a trivial matter > I think. Well actually . . . it depends on how remoteproc is implemented. > If remoteproc can gain direct access to CPU memory addressing as can be > done using uio_pruss. Then it should not be too much trouble. > > So maybe an external LED example? Which would work out very close to how > one would toggle a GPIO( LED ) on a bare metal platform. So anyone having > background experience with something like a TI Launchpad or Arduino should > be able to understand this very easily. > > Passed that . . some kind of communication example. I was thinking perhaps > usrspace to PRU core 1, to PRU core 2, then back to userspace. As a way for > people to get their feet wet, with something easily verifiable. Then > perhaps a shared memory example. > > > On Mon, Jul 11, 2016 at 6:14 PM, Mark A. Yoder <[email protected]> > wrote: > >> Greg: >> I tried removing the symbolic links and I get the following error when >> running make on a BeagleScope example. >> >> Invoking: PRU Compiler >> /usr/share/ti/cgt-pru/bin/clpru >> --include_path=/usr/share/ti/cgt-pru/include >> --include_path=../../../include --include_path=../../../include/am335x -v3 >> -O2 --display_error_number --endian=little --hardware_mac=on >> --obj_directory=gen --pp_directory=gen -ppd -ppa -fe >> gen/PRU_gpioToggle.object PRU_gpioToggle.c >> make: /usr/share/ti/cgt-pru/bin/clpru: Command not found >> Makefile:63: recipe for target 'gen/PRU_gpioToggle.object' failed >> >> The error goes away when I put the link back. Maybe the BeagleScope >> makefiles aren't set up right. >> >> --Mark >> >> On Monday, July 11, 2016 at 8:08:40 PM UTC-4, Greg wrote: >>> >>> One note on the compiler set-up: >>> >>> *ln -s `which lnkpru` .* >>> >>> I haven't found a reason to use the lnkpru command. The linking is done >>> with clpru with the -z option. >>> >>> Compile and link processes all done with a single command. The PRU >>> compiler manual explains the options reasonably thoroughly. >>> >>> Regards, >>> Greg >>> >> -- >> 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/6e34f332-77b5-4f0d-9267-3a5daca38616%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/6e34f332-77b5-4f0d-9267-3a5daca38616%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/CALHSORpsh5j72Bdp%3DgWYr6gngvxW2FuRL4yFDJAeRkGBiMoRXQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
