On 5/9/2014 1:57 PM, foreverska wrote: > I'm trying to get the hang of the pru and all the examples segfault out of > the gate. So I grabbed TI's skeleton code and tried compiling and running > that, segfault. I reduced it down to the first line, fine. First 3, > segfault. Comment out prussdrv_open, fine. Thow -g at the compiler and > run it under gdb and that really narrows it down: > "Program received signal SIGSEGV, Segmentation fault. > 0xb6fc9eec in __pruss_detect_hw_version () from /usr/lib/libprussdrv.so" > gdb doesn't really have a reference once it gets into that library so I > can't see my surroundings. There are zero results for this in google. Has > anyone seen this before? I must be missing something pretty simple.
Did you load one of the PRU device tree overlays? Most of the hardware on the SoC defaults to "off" (powered down with no clock signal) until you explicitly enable it via loading it's driver. Trying to access the hardware before it is enabled typically results in hardware bus faults, which are likely showing up as segment faults in the debugger. -- Charles Steinkuehler [email protected] -- 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.
