William: I'm not sure how far I will get. It depends on how easy it is to find the information I need.
I'd like to build a framework for simple devices. For example make it easy to add another eQEP, PWM, or I2C device via the PRU. What sort of examples would make good starting points? --Mark On Monday, July 11, 2016 at 4:15:27 PM UTC-4, William Hermans wrote: > > Mark, > > Excellent ! I look forward to looking over your course material. Do you > plan on giving a deep dive into communications between both sides. Host, > and PRU ? Not sure if that fits into your course plans or not but I know I > would to learn this myself. Also the PRU config files, hex files . . . not > sure I'm remembering that correctly or not. But it's the config files that > seem to layout stuff like .bss .data, etc . . . No idea if you plan on > covering that either. But someone needs to. > > On Mon, Jul 11, 2016 at 1:10 PM, Mark A. Yoder <[email protected] > <javascript:>> wrote: > >> gcc. My students are running Linux on their host and gcc is already >> there. >> >> --Mark >> >> On Monday, July 11, 2016 at 3:47:06 PM UTC-4, William Hermans wrote: >>> >>> Hi Mark, >>> >>> Are you using CCS or GCC tools ? >>> >>> On Mon, Jul 11, 2016 at 11:58 AM, Mark A. Yoder <[email protected]> >>> wrote: >>> >>>> It looks like the new way to talk to the PRUs is via remoteproc and >>>> RPMsg. >>>> >>>> Does anyone have pointers to some good tutorials? Or some good >>>> debuggers? >>>> >>>> ZeekHuge has a Google Summer of Code project (2016) >>>> <https://github.com/ZeekHuge/BeagleScope>that has some nice remoteproc >>>> examples, and he >>>> built some nice tools. >>>> >>>> I'm putting together a wiki >>>> <http://elinux.org/EBC_Exercise_30_PRU_via_remoteproc_and_RPMsg> that >>>> shows how to setup your Bone to run his examples. ( >>>> http://elinux.org/EBC_Exercise_30_PRU_via_remoteproc_and_RPMsg). >>>> I'm open for additions/corrections so we can have a one stop place for >>>> those using the PRUs with remoteproc. >>>> >>>> --Mark >>>> >>>> >>>> >>>> -- >>>> 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/70e1498f-3f86-4a06-b319-a66264e9ce7f%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/beagleboard/70e1498f-3f86-4a06-b319-a66264e9ce7f%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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/2e60f2f2-d5d0-4394-b854-d5d4090ac3d0%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beagleboard/2e60f2f2-d5d0-4394-b854-d5d4090ac3d0%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/9a2e62d9-4c39-45cb-b84c-3c9fae698316%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
