Hi Dennis,

Thanks for the reply. I forgot to mention that I get linker erros if i use 
printf() statements.

On Monday, 20 July 2020 14:53:10 UTC-4, Dennis Bieber wrote:
>
> On Mon, 20 Jul 2020 09:03:34 -0700 (PDT), in 
> gmane.comp.hardware.beagleboard.user 
> sreekodakkad-re5jqeeqqe8avxtiumw...@public.gmane.org <javascript:> wrote: 
>
> >Hi 
> > 
> >I am just trying to print some values to check if the condition meets the 
> >requirement in beagle bone AI board. But it is not happening when I 
> program 
> >PRUs. 
> > 
>
>         I'm actually surprised you don't get some link error if you are 
> using 
> printf() in a (C/C++) PRU program. The PRUs are not using an OS, so there 
> wouldn't be anything like STDOUT for a program running in a PRU. 
>
> >Do I have to configure UART in PRU to achieve this capability? 
>
> BB Black example at 
>
> http://exploringbeaglebone.com/chapter15/#High-Speed_Analog_to_Digital_Conversion_ADC_using_the_PRU-ICSS
>  
> appears to have the PRU write the data to shared RAM, and a program 
> running 
> in Linux reading the values for output. (NOTE: reference to "chapter 13" 
> applies to the first edition of the book -- it is chapter 15 in the 2nd) 
> (NOTE: Examples also seem to be using PRUSS driver, and not the newer 
> RemoteProc 
>
>
>
> https://processors.wiki.ti.com/index.php/PRU_Debugging#Place_.22printf.22_statements
>  
> Note that this also does not use printf() IN the PRU code, but rather in 
> whatever program was used to load/start the PRU, and it interfaces, again, 
> by monitoring shared memory into which the PRU has written. 
>
>
> -- 
> Dennis L Bieber 
>
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ccd0dab1-689b-48ba-a52a-051e253e9ca7o%40googlegroups.com.

Reply via email to