Here is what you need to understand about people on this list. There are no 
“developers" on this list. No one on this mailing list is paid by BeagleBoard. 
We are all volunteers, including Robert Nelson. If you have a problem with 
Documentation, then why don’t you create it so others can learn. If you need 
help with getting the info you need, we are all prepared to help. 

Regards,
John




> On Apr 5, 2016, at 9:57 AM, Wally Bkg <wb666gre...@gmail.com> wrote:
> 
> 
> I think the output of uname -a  for your kernel version is more helpful than 
> the Debian version which is running when it comes to overlays, modules, and 
> Beaglebone hardware specific issues.
> 
> I'm subscribing to this thread, as you are doing what I've planned to do in 
> the not too distant future, so I'm really interested in what the solutions 
> are to your problems here.
> 
> The Beaglebone development is fast and furious, which is good, but the 
> developers don't seem to give a hoot if changes break what little 
> documentation is out there, which IMHO makes the BB a rather poor choice for 
> newbies.   
> 
> I've posted a fair amount about Bonescript issues because I'm trying to help 
> a friend get started with an automation project for a solar powered, 
> off-grid, hydroponic green-house.  He needs some A/D or I'd have recommended 
> a Rasperry Pi2 from the start, but if things don't fall into place soon I'll 
> just buy him a Pi Hat that has A/D and give it to him along with one of my 
> RiP2 boards as the frustration factor is really turning me off.   Without me 
> helping him, he'd already have tossed the BB in the trash and did the best he 
> could with timers and relays, which he totally understands -- but he was 
> looking to get creative with some of his control ideas that he clearly sees 
> as difficult to do without a computer.
> 
> 
> 
> 
> 
> On Tuesday, April 5, 2016 at 10:22:36 AM UTC-5, Le Costaouec Vincent wrote:
> 
> I forgot to indicate the release on which I'm working on :  
> #  lsb_release -da
> 
> Distributor ID:    Debian
> Description:    Debian GNU/Linux 8.3 (jessie)
> Release:    8.3
> Codename:    jessie
> 
> Is anyone have already work on the PRU on this kernel version ?
> Thanks by advance.
> Regards.
> Vincent
> 
> 
> Le mardi 5 avril 2016 11:33:06 UTC+2, Le Costaouec Vincent a écrit :
> Hello, 
> 
> I'm currently trying to configure and use the PRU of the BBB.
> 
> So I've tried two different method to do so however, with none of them I get 
> succeed and I don't really 
> understand why.
> 
> 1) First method (from Derek Molloy book) :
> 
> http://exploringbeaglebone.com/chapter13/ 
> <http://exploringbeaglebone.com/chapter13/>
> So I have tried to do the PRU-based Clock Signal Generators, because this one 
> do not required any additional material except an oscilloscope.
> 
> So I had load the EBB-PRU-Example DTS overlay (provided in attachment), and I 
> have receive the following message : 
> # echo EBB-PRU-Example > $SLOTS
> [   51.417438] bone_capemgr bone_capemgr: part_number 'EBB-PRU-Example', 
> version 'N/A'
> [   51.425297] bone_capemgr bone_capemgr: slot #4: override
> [   51.430665] bone_capemgr bone_capemgr: Using override eeprom data at slot 4
> [   51.437772] bone_capemgr bone_capemgr: slot #4: 'Override Board 
> Name,00A0,Override Manuf,EBB-PRU-Example'
> [   52.526058] gpio-of-helper ocp:gpio_helper: ready
> [   52.531052] bone_capemgr bone_capemgr: slot #4: dtbo 
> 'EBB-PRU-Example-00A0.dtbo' loaded; overlay id #0
> 
> 
> 
> # cat $SLOTS
>  0: PF----  -1 
>  1: PF----  -1 
>  2: PF----  -1 
>  3: PF----  -1 
>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,EBB-PRU-Example
> 
> I have also check :
> # lsmod |grep uio
> uio_pruss               4590  0 
> uio_pdrv_genirq         3317  0 
> uio                     8319  2 uio_pruss,uio_pdrv_genirq
> 
> 
> root@beagle01:~/labs/exploringBB/chp13/fixedPRUClock# ./build 
> PRU Assembler Version 0.86
> Copyright (C) 2005-2013 by Texas Instruments Inc.
> Pass 2 : 0 Error(s), 0 Warning(s)
> Writing Code Image of 12 word(s)
> 
> # sudo ./fixedclock
> However, when I tried to monitor what append on pin P9_27 but I didn't 
> observed anything on this pins.
> 
> 
> 
> 
> 2) Second method (from the Beagle bone black cookbook written by Charles A 
> Hamilton) :
> 
> This time, I have use this DTS : BB-BONE-PRU-01 
> (https://github.com/jadonk/cape-firmware/blob/master/arch/arm/boot/dts/BB-BONE-PRU-01-00A0.dts
>  
> <https://github.com/jadonk/cape-firmware/blob/master/arch/arm/boot/dts/BB-BONE-PRU-01-00A0.dts>)
> In addition, I have tried to used this code :
> https://github.com/HudsonWerks/bbb-pru 
> <https://github.com/HudsonWerks/bbb-pru>
> 
> So first I tried to add the DTS, I received this message : 
> # echo EBB-PRU-Exampecho BB-BONE-PRU-01 > $SLOTS
> [59800.649273] bone_capemgr bone_capemgr: part_number 'BB-BONE-PRU-01', 
> version 'N/A'
> [59800.656947] bone_capemgr bone_capemgr: slot #12: override
> [59800.662528] bone_capemgr bone_capemgr: Using override eeprom data at slot 
> 12
> [59800.669680] bone_capemgr bone_capemgr: slot #12: 'Override Board 
> Name,00A0,Override Manuf,BB-BONE-PRU-01'
> [59800.699368] ------------[ cut here ]------------
> [59800.704089] WARNING: CPU: 0 PID: 619 at 
> arch/arm/mach-omap2/omap_hwmod.c:2087 _enable+0x201/0x210()
> [59800.713188] omap_hwmod: pruss: enabled state can only be entered from 
> initialized, idle, or disabled state
> [59800.722894] Modules linked in: uio_pruss usb_f_ecm g_ether usb_f_rndis 
> u_ether libcomposite pvrsrvkm(O) omap_sham omap_aes snd_soc_davinci_mcasp 
> snd_soc_edma snd_soc_omap omap_rng rng_core snd_soc_core snd_compress 
> snd_pcm_dmaengine snd_pcm snd_timer snd soundcore evdev spi_omap2_mcspi 
> uio_pdrv_genirq uio leds_gpio
> [59800.751252] CPU: 0 PID: 619 Comm: bash Tainted: G        W  O    
> 4.1.19-bone20 #1
> [59800.758778] Hardware name: Generic AM33XX (Flattened Device Tree)
> [59800.764974] [<c0012f39>] (unwind_backtrace) from [<c00110a9>] 
> (show_stack+0x11/0x14)
> [59800.772791] [<c00110a9>] (show_stack) from [<c002e5b7>] 
> (warn_slowpath_common+0x6b/0x8c)
> [59800.780948] [<c002e5b7>] (warn_slowpath_common) from [<c002e5fb>] 
> (warn_slowpath_fmt+0x23/0x2c)
> [59800.789714] [<c002e5fb>] (warn_slowpath_fmt) from [<c0022dfd>] 
> (_enable+0x201/0x210)
> [59800.797524] [<c0022dfd>] (_enable) from [<c00231fd>] 
> (omap_hwmod_enable+0x15/0x20)
> [59800.805158] [<c00231fd>] (omap_hwmod_enable) from [<c0023e05>] 
> (omap_device_enable+0x29/0x50)
> [59800.813751] [<c0023e05>] (omap_device_enable) from [<c0023e3d>] 
> (_od_runtime_resume+0x11/0x1c)
> [59800.822450]
> ...
> 
> -- 
> For more options, visit http://beagleboard.org/discuss 
> <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 
> <mailto:beagleboard+unsubscr...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout 
> <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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to