> > *(the PRUSS's can write anywhere in memory - they could be a significant > security risk - for example changing some bytes loaded at PRUSS startup > could be used to take over the BBB).*
Only if you're incompetent where system security is concerned. On Thu, Apr 23, 2015 at 9:18 AM, Bit Pusher <[email protected]> wrote: > We have been using the PRUSS's extensively on bone70; with mostly success, > but every so often, memory gets corrupted, and we have to reboot. This > behavior is aperiodic and we have not been able to track it down yet (the > PRUSS's can write anywhere in memory - they could be a significant security > risk - for example changing some bytes loaded at PRUSS startup could be > used to take over the BBB). That is until today (see my recent post), where > some input connections to the header that we want to use as PRUSS inputs is > causing the BBB to freeze at boot. Generally, however, the PRUSS's seem to > work as expected (make sure you assemble with -V2) > > On Friday, June 27, 2014 at 4:03:32 PM UTC-4, Sherman Boyd wrote: >> >> Hello. I'm trying to get PRUSS working with the new Debian beta image. >> I've got things working on Angstrom, but not on Debian. I'm using >> kernel 3.8.13-bone50, is anybody else using PRUSS on this kernel? >> > -- > 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. > -- 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.
