On Wed, Feb 12, 2020 at 9:12 AM Stephan Böck <[email protected]> wrote:

> Hey,
>
> at the moment I try to port a program to the BB AI, which was developed
> for the BB Black.
>
> This program uses the PRUs and includes the headerfiles
> pruss_intc_mapping.h and prussdrv.h aswell as the libs (libprussdrv.a,
> libprussdrv.so, libprussdrvd.a and libprussdrvd.so) from the
> am335x_pru_package, which can be found in the beagleboard git repo
> https://github.com/beagleboard/am335x_pru_package
>
> Is there a chance that a pru package for the AM5729 is on the way?
>

What do you need out of the package first? I think we can tackle adding
some cross AM3/AM5 device support to this library incrementally.

Mark Yoder and I have been working on BeagleBone AI PRU examples at:

https://github.com/beagleboard/cloud9-examples/tree/v2020.01/BeagleBone/AI/pru



>
>
> Currently, I am facing segmentation faults. Which makes totally sense,
> since the base addresses changed.
>
> Stephan
>
> --
> 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/08c3aa1e-e013-4c3e-9214-1b238b5d3924%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/08c3aa1e-e013-4c3e-9214-1b238b5d3924%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
https://beagleboard.org/about - a 501c3 non-profit educating around open
hardware computing

-- 
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/CA%2BT6QP%3DXwFKmVDS-t%3D82wMj7En1AUCDw%2BHRRnkaFjUVo2TNUeQ%40mail.gmail.com.

Reply via email to