Ok here is a an update.  I had to change uEnV.txt file in /boot and that 
seems to load device tree without any issues and i made changes to the 
following lines:
##Example v4.1.x
cape_disable=bone_capemgr.disable_partno=cape-universaln
cape_enable=bone_capemgr.enable_partno=uio_pruss_enable,PRU-GPIO-EXAMPLE

while as before those lines did not have anything to the right of the = 
sign and th lines were commented out.
I am now trying to use the same device tree as used by 
http://credentiality2.blogspot.com/2015/09/beaglebone-pru-gpio-example.html
Once I boot up with the device tree I can see the new pins that I got from 
the device tree:
debian@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
 0: PF----  -1 
 1: PF----  -1 
 2: PF----  -1 
 3: PF----  -1 
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,uio_pruss_enable
 5: P-O-L-   1 Override Board Name,00A0,Override Manuf,PRU-GPIO-EXAMPLE

But when I go to the run the program as he instructed I run into the 
following error:
debian@beaglebone:~$ sudo ./pru_loader pru_egp_output.bin
prussdrv_open() failed

I don't know what is causing that error now?  Some guidance would be great 
(I can move this to another location if necessary)
Also I would like to know why I have to place the binary into the uEnv.txt 
file and just be able to change it on the fly? Is this requirement true of 
all linux systems?

On Sunday, January 22, 2017 at 4:31:25 PM UTC-8, Ashwini Bhat wrote:
>
>
> Hey Guys,
>   I need some help in trying to configure my device tree.  The goal is to 
> make it possible to so that I can use PRUs.  I keep getting stuck getting 
> the device trees loaded.  Help would be greatly appreciated.  To start off 
> here is some info about the machine:
> debian@beaglebone:/lib/firmware$ uname -a
> Linux beaglebone 4.4.43-ti-r84 #1 SMP Fri Jan 20 16:28:53 UTC 2017 armv7l 
> GNU/Linux
> debian@beaglebone:/lib/firmware$ lsb_release -a
> No LSB modules are available.
> Distributor ID:    Debian
> Description:    Debian GNU/Linux 8.6 (jessie)
> Release:    8.6
> Codename:    jessie
>
> *The text below shows you what happens when I try to load the UART1 device 
> tree*
>
> debian@beaglebone:/lib/firmware$ sudo sh -c "echo 'BB-UART1' > 
> /sys/devices/platform/bone_capemgr/slots"
> sh: echo: I/O error
> debian@beaglebone:/lib/firmware$ dmesg | tail
> [  780.776674] bone_capemgr bone_capemgr: Using override eeprom data at 
> slot 5
> [  780.776706] bone_capemgr bone_capemgr: slot #5: 'Override Board 
> Name,00A0,Override Manuf,PRU-GPIO-EXAMPLE'
> [  780.796089] bone_capemgr bone_capemgr: slot #5: PRU-GPIO-EXAMPLE 
> conflict P8.11 (#4:cape-universaln)
> [  780.805395] bone_capemgr bone_capemgr: slot #5: Failed verification
> [  810.309452] bone_capemgr bone_capemgr: part_number 'BB-UART1', version 
> 'N/A'
> [  810.309506] bone_capemgr bone_capemgr: slot #6: override
> [  810.315043] bone_capemgr bone_capemgr: Using override eeprom data at 
> slot 6
> [  810.315074] bone_capemgr bone_capemgr: slot #6: 'Override Board 
> Name,00A0,Override Manuf,BB-UART1'
> [  810.353761] bone_capemgr bone_capemgr: slot #6: BB-UART1 conflict P9.24 
> (#4:cape-universaln)
> [  810.362487] bone_capemgr bone_capemgr: slot #6: Failed verification
>  
> *This is what my slots file looks like:*
> debian@beaglebone:/lib/firmware$ cat 
> /sys/devices/platform/bone_capemgr/slots
>  0: PF----  -1 
>  1: PF----  -1 
>  2: PF----  -1 
>  3: PF----  -1 
>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,cape-universaln
>
>
> *I know the pruss is loaded because is see it in lsmod*
> debian@beaglebone:/lib/firmware$ lsmod | grep pruss
> uio_pruss               5504  0 
> uio                    10524  2 uio_pruss,uio_pdrv_genirq
>
> Since this basic device tree is not working I don't know what to do. I 
> want get to eventually using PRU, but I keep getting stuck on the damn 
> device trees.  I have gone through Derek Molloy's tutorial, I can get that 
> to work on a different, and older beaglebone black.  What I am concerned 
> with is, I am unable to debug what is happening when the device trees stops 
> working.  I don't want to just copy and paste because then I don't 
> understand what is going on. Any help will be greatly appreciated. 
>

-- 
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/db6ac552-ef52-4caf-be52-fc0b2cab905e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to