That sounds like a perfect justification to spend $90 on jtag Sent from Yahoo Mail on Android On Tue, Aug 8, 2017 at 3:35 PM, Clark Sann<[email protected]> wrote: Thanks, Charles, for the great ideas.
I definitely agree with you that debugging on the PRU is hard. I’ve been working on a problem on and off for weeks. I’ve solved it now but had decent debugging tools it would have only taken a few minutes. (Or if I knew C better!) It’s like trying to play tennis with a bag over my head. Lucky for me, I don’t get paid for this stuff. Today I got RPMsg working. I’m now using it to send commands to the PRU and to retrieve rudimentary diagnostic data. So I hope to pick up the pace a little bit. The PRU certainly has a steep learning curve! I’ll also look into your suggestions. Thanks again! Clark > On Aug 8, 2017, at 11:08 AM, Charles Steinkuehler <[email protected]> > wrote: > > On 8/8/2017 10:11 AM, Clark Sann wrote: >> >> But why did TI blather on and on about the printf_support switch and the >> high >> and low level IO drivers in the PRU C Compiler manual? > > Because you can get printf working if you add a UART or other means to > get data out of the system. > >> What do you do to get diagnostic info while debugging PRU firmware? > > My typical methods: > > * "Twiddle" pru output pins at various points in the code. Note that > if you've got a good 'scope or logic analyzer (I'm typically using an > Agilent MSO with 16 digital channels), you can shift out data values > with a single pin, so it can be more useful than just "LED" style > debugging. > > * Dump data into a chunk of shared memory (typically one of the PRU > data RAMs) and examine it from the ARM side. > > * Use a debugger to single-step the PRU code. I typically use the HAL > based one provided with Machinekit but there are now several others > available. > > Regardless, debugging on the PRU is much harder than debugging code on > the ARM side. > > -- > Charles Steinkuehler > [email protected] > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the Google > Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/hM0UojPprcY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/e5397db0-ee22-e884-a2d5-893936dea0df%40steinkuehler.net. > 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/0F280D4F-A9C9-4A8E-922A-DCCAC6034C1D%40icloud.com. 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/1351920125.2597834.1502229364128%40mail.yahoo.com. For more options, visit https://groups.google.com/d/optout.
