PRU with 4.1.12-bone-rt-r16

GoogleGroups
1

Hi All

I have to use kernel image 4.1.12-bone-rt-r16 with PRU

I got error when i call
root@beaglebone:/home/amr/chp13/PRUclock# echo EBB-PRU-Example > /sys/devices/platform/bone_capemgr/slots
-bash: echo: write error: Invalid argument

in dmesg it shows

[ 375.463548] bone_capemgr bone_capemgr: part_number ‘EBB-PRU-Example’, version ‘N/A’
[ 375.463611] bone_capemgr bone_capemgr: slot #8: override
[ 375.463650] bone_capemgr bone_capemgr: Using override eeprom data at slot 8
[ 375.463693] bone_capemgr bone_capemgr: slot #8: ‘Override Board Name,00A0,Override Manuf,EBB-PRU-Example’
[ 375.464715] __of_adjust_tree_phandle_references: Could not find target property ‘fixup’ @/local_fixups
[ 375.474644] bone_capemgr bone_capemgr: slot #8: Failed to resolve tree

I got the same error when i tried to run other examples from exploring BBB book.

What do you think ?

Thanks a lot

2

Can you use Universal IO instead? I’ve been working on a PRU project and found it saved me a lot of trouble tweaking the Device Tree.

https://github.com/cdsteinkuehler/beaglebone-universal-io

I started using this rather than editing the Device Tree, and found it managed the PRU pins adequately.
So I had the intention of returning to this problem and building a custom DT.
The Beaglebones have plenty of resources to handle this, so why not use it permanently?
Perhaps if you are using a cape type plug-in with stored configuration a custom DT would be mandatory.

Note that you can put all of your pin configurations in a text file and load them with the config-pin -f option.
Put this in whatever start-up configuration you use and you are good to go.

Greg