On Sat, Feb 20, 2016 at 2:45 PM, William Hermans <[email protected]> wrote: > Is it really so much to ask for example code to demonstrate how to interact > with the on die hardware ? Without having to download 1GB of pretty much > useless library . . .
William, I must be missing something, because I see remoteproc as a communication and management mechanism for code on CPUs other than the main processor. The actual code that you are running on those subsidiary processors does not depend on the mechanism you use for talking to it (other than the parts that do the talking, of course). In particular, running ADC, I2C or GPIO should be the same, regardless whether you use remoteproc or not---what changes is how you tell this code what to do. Does it make sense to you? -- 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.
