[beagleboard] Re: MCP2515 via SPI0, CS0 on BeagleBone Black

[Sam Daleo]

Hi! Just wondering if you had any luck with the MCP2515 and your Beaglebone?

On Thursday, June 13, 2013 at 3:09:44 PM UTC-7, Michael Luxen wrote:
>
> Hello,
>  
> does anyone already have a working setup/howto for a MCP2515 activation on 
> SPI0 with CS0?
> To be clear, I've the internal DCAN0 and DCAN1 already up and running but 
> I'm interesting to have a further 3rd CAN channel via a MCP2515 enabled. 
> After some hours of trying and searching on the WWW I've still no working 
> MCP2515 SPI interface. I've used my MCP2515 SPI-Interface already with 
> success on the Raspberry Pi and adapted it to the GPIOs of the BeagleBone 
> Black.
>  
> To give more details my environment is:
> Angstrom distribution from 2013-05-27
>  
> P9.27,/* spi irq: gpio3_19 */
> P9.22,/* spi: spi0_sclk */
> P9.21,/* spi: spi0_d0 */
> P9.18,/* spi: spi0_d1 */
> P9.17,/* spi: spi0_cs0 */
>  
> extract of my spi0-00A0.dts file:
>  
> pinctrl-single,pins = <
>   0x150 0x10  /* spi0_sclk, OUTPUT_PULLUP | MODE0 */
>   0x154 0x30  /* spi0_d0, INPUT_PULLUP | MODE0 */
>   0x158 0x10  /* spi0_d1, OUTPUT_PULLUP | MODE0 */
>   0x15c 0x10  /* spi0_cs0, OUTPUT_PULLUP | MODE0 */
>   0x1a4 0x37 /* mcasp0_fsr.gpio3_19, RX_ENABLED | PULLUP | MODE7, IRQ */
> >;
> I'm unsure about the spi0_sclk Pin. Some websites describes it as output 
> as shown above and others as Input with "0x150 0x30". My setup doesn't work 
> with both of them.
> Any hints are welcome!
>  
> Regards
> Mike
>  
>  
>

-- 
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.

[beagleboard] CAN over SPI using MCP2515 and Beaglebone

[Sam Daleo]

Hey! Just like the title says, I'm interested in doing this. I know I can 
use the CAN bus on the Beaglebone, but I want to be able to do it over SPI. 
Anyone ever tried this before?

-- 
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.

[beagleboard] No output voltage on GPIO headers

[Sam Daleo]

I've messed around with device tree overlays a bit, and I'm wondering if I 
could have screwed something up to cause the 3.3 and 5v headers to not 
output voltage? Is there a way to fix this in /sys/ ?

Thanks!

-- 
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.

Re: [beagleboard] Trouble loading a custom DTO

[Sam Daleo]

Looking at dmesg for startup of the board it turns out that it does matter 
what you set the compatability field to in the DTO. I got it to apply.. 
Feels good! :D

On Thursday, January 14, 2016 at 11:25:07 AM UTC-8, Sam Daleo wrote:
>
> I'm seeing this now...
>
> [  820.596818] bone-capemgr bone_capemgr.9: slot #7: Incompatible with 
>>> baseboard for 'libpruio'
>>
>> [  820.605916] bone-capemgr bone_capemgr.9: slot #7: Failed verification
>>
>>
> Does it matter than I'm using a Beaglebone Green instead of Black? 
>
> On Thursday, January 7, 2016 at 11:49:09 AM UTC-8, RobertCNelson wrote:
>>
>>
>>
>> On Thu, Jan 7, 2016 at 1:32 PM, Sam Daleo <ssd...@gmail.com> wrote:
>>
>>> When I try that I get
>>>
>>> *sh: echo: I/O error*
>>>
>>
>> and what error does "dmesg | grep bone" show after that?
>>
>> Regard,
>>
>> -- 
>> Robert Nelson
>> https://rcn-ee.com/
>>
>

-- 
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.

Re: [beagleboard] Trouble loading a custom DTO

[Sam Daleo]

I'm seeing this now...

[  820.596818] bone-capemgr bone_capemgr.9: slot #7: Incompatible with 
>> baseboard for 'libpruio'
>
> [  820.605916] bone-capemgr bone_capemgr.9: slot #7: Failed verification
>
>
Does it matter than I'm using a Beaglebone Green instead of Black? 

On Thursday, January 7, 2016 at 11:49:09 AM UTC-8, RobertCNelson wrote:
>
>
>
> On Thu, Jan 7, 2016 at 1:32 PM, Sam Daleo <ssd...@gmail.com > 
> wrote:
>
>> When I try that I get
>>
>> *sh: echo: I/O error*
>>
>
> and what error does "dmesg | grep bone" show after that?
>
> Regard,
>
> -- 
> Robert Nelson
> https://rcn-ee.com/
>

-- 
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.

Re: [beagleboard] Trouble loading a custom DTO

[Sam Daleo]

Wanted to bump this in case anyone has seen anything like it. Instead of 
making my own DTO, I tried to load the DTO from the libpruio 

 repo. 
I don't get any error when I try to echo the cape to the cape manager slots 
path.. Here are the artifacts from my latest session...

> root@beaglebone:/home/libpruio/libpruio-0.2# sudo sh -c "echo libpruio >> 
>> /sys/devices/bone_capemgr.9/slots"
>
> root@beaglebone:/home/libpruio/libpruio-0.2# cat 
>> /sys/devices/bone_capemgr.9/slots
>
>  0: 54:PF---
>
>  1: 55:PF---
>
>  2: 56:PF---
>
>  3: 57:PF---
>
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>
> If I'm not mistaken it should appear under 4? I'm not getting any I/O 
> error like before, but it doesn't look like the cape is loading properly...
>

Has anyone else seen this?  

-- 
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.

[beagleboard] Re: About beaglebone_pru_adc to read just one ADC port

[Sam Daleo]

Just by looking at the readme, it looks as though it's using the 
multiplexor to read the different values from one pin? 

I could be wrong, but maybe you could look into this and see if you can 
disable it.

On Saturday, January 9, 2016 at 6:30:05 AM UTC-8, ThanapatMax wrote:
>
> From https://github.com/pgmmpk/beaglebone_pru_adc
>
> Im install and follow instruction to make it read ADC value
>
> But i cant read the value in single port it always read 8 ports (AIN 0-7)
>
> I want to just read AIN 0 in 0-4095 range.
>

-- 
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.

Re: [beagleboard] Trouble loading a custom DTO

[Sam Daleo]

sh: 1: cannot create /sys/devices/bone_capemgr.9/slotsdmesg: Directory 
nonexistent

This isn't true, I can definitely cd into that directory and it does exist. 
I have also given 777 permisions to that entire directory in case there was 
some weird permission thing going on...


On Thursday, January 7, 2016 at 11:49:09 AM UTC-8, RobertCNelson wrote:
>
>
>
> On Thu, Jan 7, 2016 at 1:32 PM, Sam Daleo <ssd...@gmail.com > 
> wrote:
>
>> When I try that I get
>>
>> *sh: echo: I/O error*
>>
>
> and what error does "dmesg | grep bone" show after that?
>
> Regard,
>
> -- 
> Robert Nelson
> https://rcn-ee.com/
>

-- 
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.

Re: [beagleboard] Trouble loading a custom DTO

[Sam Daleo]

When I try that I get

*sh: echo: I/O error*

On Thursday, January 7, 2016 at 11:24:37 AM UTC-8, RobertCNelson wrote:
>
>
>
> On Thu, Jan 7, 2016 at 1:21 PM, Sam Daleo <ssd...@gmail.com > 
> wrote:
>
>>
>> Hi,
>>
>> So I've been having issues loading a custom DTO on my Beaglebone Black 
>> (well, green, really..). Anyway..
>>
>> I've been following the book Exploring Beaglebone because there's a lot 
>> of good information here. I've made a custom .dtbo with pin settings that 
>> I'm interested in using because I want to interface with the PRU. I try to 
>> run the command
>>
>> 'echo PRU_cape > /sys/devices/bone_capemgr.9/slots'
>>
>> but every time I try to execute the command I get 
>>
>> 'echo: write error: Invalid argument'
>>
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Privileged_echo
>
>  
>
>>
>> So then I figured maybe I could just go into slots and edit the file to 
>> include the name (I'm thinking that the part number is the correct thing to 
>> add to this?) manually. When I try to edit /sys/.../slots and save it using 
>> nano, I get an error that the file doesn't exist.
>>
>> Anyone else have any trouble loading a DTO? Am I missing something?
>>
>> Any help would be much appreciated, thanks!
>>
>
>
> Regards,
>
> -- 
> Robert Nelson
> https://rcn-ee.com/
>

-- 
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.

Re: [beagleboard] Trouble loading a custom DTO

[Sam Daleo]

>
> Also, just in case you're interested...
>

 root@beaglebone:~# uname -a
Linux beaglebone 3.8.13-bone79 #1 SMP Tue Oct 13 20:44:56 UTC 2015 armv7l 
GNU/Linux

-- 
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.

[beagleboard] Re: How to disable mcasp0

[Sam Daleo]

Hey, 

I just want to make sure I'm reading this right. Did you just delete the 
two mcasp sections in the .dtb file entirely? These two? 


On Tuesday, July 1, 2014 at 5:05:07 PM UTC-7, Spaced Cowboy wrote:
>
> Well, following up on my own post in case anyone finds this useful...
>
> I just tried deleting all references to mcasp{0,1} in 
> /boot/am335x-boneblack.dts and on reboot, the pins that I wanted free are 
> indeed free. This gives me
>
> P8:
>
> name pin mode 6 mode 5
>
>
> P8_11 13 out:0:r30:15
>
> P8_12 12 out:0:r30:14
>
> P8_15 15 in:0:r31:15
>
> P8_16 14 in:0:r31:14
>
>
> P9:
>
> P9_24 97 in:0:r31:16
>
> P9_26 96 in:1:r31:16
>
> P9_27 105 in:0:r31:5 out:0:r30:5
>
> P9_30 102 in:0:r31:2 out:0:r30:2
>
> P9_41 106 in:0:r31:6 out:0:r30:6
>
>
> P9_25 107 in:0:r31:7 out:0:r30:7
>
> P9_28 103 in:0:r31:3 out:0:r30:3
>
> P9_29 101 in:0:r31:1 out:0:r30:1
>
> P9_31 100 in:0:r31:0 out:0:r30:0
>
> P9_42 104 in:0:r31:4 out:0:r30:4
>
> giving the following pin configuration:
>
> in: PRU0: 0,1,2,3,4,5,6,7,14,15,16
>
> PRU1: 16
>
> out: PRU0: 14,15
>
> ... with the latter set of P9 pins being the ones released by not using 
> mcasp.  I can therefore set up two synchronous-data channels, one dedicated 
> output (2-pin, clock and data) and one dedicated input (9-pin, clock and 
> byte-wide data). If I can clock the input pins at ~20MHz, I have my 20 
> MBytes/sec. I even have a couple of input pins left over spare :)
>
> My data needs are highly asymmetric (massive input, small output) so this 
> suits me, and it stops me from needing to switch over the input/output 
> configuration to get bi-directionality. 
>
> Hope this helps someone. I'm sure there's a better way to disable the 
> mcasp device, but I couldn't find it...
>
> Simon
>

-- 
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.

Re: [beagleboard] /sys/device/bone_capemgr* doesn't exist on fresh image

[Sam Daleo]

I just realized I never responded to your post.
Thanks for your link! I didn't really get a chance to break down what he 
was doing in that code, so I'll do so. I think part of the problem with 
approaching Google is that I'm not familiar enough with the nomenclature 
and I feel you have to be specific enough with Google to get what you're 
looking for.


On Tuesday, December 15, 2015 at 2:22:24 AM UTC-8, William Hermans wrote:
>
> https://github.com/boxysean/am335x_pru_package
>
> This one is different from the "stock" repo as he's added 3 examples all 
> related to blinking LEDs. LEDs which are tied to GPIO pins . . .After that, 
> google has lots to read.
>
> On Mon, Dec 14, 2015 at 8:47 PM, Sam Daleo <ssd...@gmail.com 
> > wrote:
>
>> Hey, since I've got you here. Do you have anything good to read on using 
>> the PRU with the GPIOs on the board?
>>
>> On Monday, December 14, 2015 at 7:18:10 PM UTC-8, RobertCNelson wrote:
>>>
>>> On Mon, Dec 14, 2015 at 9:15 PM, Sam Daleo <ssd...@gmail.com> wrote: 
>>> > Oh, cool. Should I install the 8.2 image from the website, install 
>>> > linux-image-4.1.14-bone-rt-r17  using apt-get and then update the 
>>> kernel? 
>>>
>>> Either or.. they both do the same thing.. the "update_kernel.sh" 
>>> always get's the latest.. So in a month's time, when this email 
>>> exchange is old, "bone17" will be long replaced. ;) 
>>>
>>> Regards, 
>>>
>>> -- 
>>> Robert Nelson 
>>> https://rcn-ee.com/ 
>>>
>> -- 
>> 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...@googlegroups.com .
>> For more options, visit 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.

Re: [beagleboard] /sys/device/bone_capemgr* doesn't exist on fresh image

[Sam Daleo]

When I downgrade to this image all four of my LEDs are illuminated upon 
reboot and stay this way for a long time. Is this normal?

On Monday, December 29, 2014 at 6:22:03 AM UTC-8, RobertCNelson wrote:
>
> On Mon, Dec 29, 2014 at 1:28 AM,   wrote: 
> > Sorry for the super newbie question.  What do I need to install in order 
> to 
> > have the /sys/devices/bone_capemgr* directory show up on a fresh Ubuntu 
> > image?  My software uses this to configure the device tree for PWM 
> slots. 
> > 
> > Background: I was operating fine using the default Debian image that 
> came on 
> > the BBB Rev C, but for various reasons I decided to switch to Ubuntu 
> > (Trusty).  I used the image located here and all seemed to go well.  I 
> can 
> > list the GPIOs at /sys/class/gpio, but there is no bone* under 
> /sys/devices 
> > like there used to be with the Debian (Wheezy) image. 
> > 
> > Any pointers would be appreciated. 
>
> Down grade to v3.8.x: 
>
> sudo apt-get update 
> sudo apt-get install linux-image-3.8.13-bone68 
> sudo reboot 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

-- 
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.

Re: [beagleboard] /sys/device/bone_capemgr* doesn't exist on fresh image

[Sam Daleo]

I just used Debian 8.2 from the website.

On Monday, December 14, 2015 at 5:40:12 PM UTC-8, RobertCNelson wrote:
>
> On Mon, Dec 14, 2015 at 7:26 PM, Sam Daleo <ssd...@gmail.com > 
> wrote: 
> > When I downgrade to this image all four of my LEDs are illuminated upon 
> > reboot and stay this way for a long time. Is this normal? 
>
> Nope... 
>
> Considering this specific thread went back a year ago... 
>
> What image did you start with? Before you down-graded? 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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.

Re: [beagleboard] /sys/device/bone_capemgr* doesn't exist on fresh image

[Sam Daleo]

Ah, thank you for the help! I'll give that a try.

Yeah, doing a quick google search I found this thread and was running into 
an issue with trying to use the PRU so I figured I'd give this a try.

On Monday, December 14, 2015 at 6:27:10 PM UTC-8, RobertCNelson wrote:
>
> On Mon, Dec 14, 2015 at 8:20 PM, Sam Daleo <ssd...@gmail.com > 
> wrote: 
> > I just used Debian 8.2 from the website. 
>
> Well, bone68 was over a year ago.. so yeah, probally broken.. 
>
> Today, 3.8.13-bone79 is the latest: 
>
> http://repos.rcn-ee.com/latest/jessie-armhf/LATEST-omap-psp 
>
> So you should have done: 
>
> sudo apt-get update ; sudo apt-get install linux-image-3.8.13-bone79 ; 
> sudo reboot 
>
> Or you could have used the script listed here: 
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Kernel_Options 
>
> or here: 
>
> http://elinux.org/BeagleBoardDebian#Install_Latest_Kernel_Image 
>
> Lesson, don't follow directions more then a year old.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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.

Re: [beagleboard] /sys/device/bone_capemgr* doesn't exist on fresh image

[Sam Daleo]

^^ don't mind that second line, didn't realize I started typing in the 
box.. was meant for a different window :)

On Monday, December 14, 2015 at 7:15:40 PM UTC-8, Sam Daleo wrote:
>
> Oh, cool. Should I install the 8.2 image from the website, 
> install linux-image-4.1.14-bone-rt-r17  using apt-get and then update the 
> kernel?
>
> Hey, quick question. Trying to 
>
> On Monday, December 14, 2015 at 6:45:05 PM UTC-8, RobertCNelson wrote:
>>
>> On Mon, Dec 14, 2015 at 8:32 PM, Sam Daleo <ssd...@gmail.com> wrote: 
>> > Ah, thank you for the help! I'll give that a try. 
>> > 
>> > Yeah, doing a quick google search I found this thread and was running 
>> into 
>> > an issue with trying to use the PRU so I figured I'd give this a try. 
>>
>> For the pru, compatible with 3.8 you can use: 
>>
>> 4.1.x-bone 
>>
>> linux-image-4.1.14-bone17 
>>
>> or the real time version: 
>>
>> linux-image-4.1.14-bone-rt-r17 
>>
>> With the magic script: 
>>
>> cd /opt/scripts/tools/ 
>> git pull 
>>
>> sudo ./update_kernel.sh --bone-kernel --lts 
>>
>> or 
>>
>> sudo ./update_kernel.sh --bone-rt-kernel --lts 
>>
>> Regards, 
>>
>> -- 
>> Robert Nelson 
>> https://rcn-ee.com/ 
>>
>

-- 
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.

Re: [beagleboard] /sys/device/bone_capemgr* doesn't exist on fresh image

[Sam Daleo]

Awesome, thanks for the help!

On Monday, December 14, 2015 at 7:18:10 PM UTC-8, RobertCNelson wrote:
>
> On Mon, Dec 14, 2015 at 9:15 PM, Sam Daleo <ssd...@gmail.com > 
> wrote: 
> > Oh, cool. Should I install the 8.2 image from the website, install 
> > linux-image-4.1.14-bone-rt-r17  using apt-get and then update the 
> kernel? 
>
> Either or.. they both do the same thing.. the "update_kernel.sh" 
> always get's the latest.. So in a month's time, when this email 
> exchange is old, "bone17" will be long replaced. ;) 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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.

Re: [beagleboard] /sys/device/bone_capemgr* doesn't exist on fresh image

[Sam Daleo]

Hey, since I've got you here. Do you have anything good to read on using 
the PRU with the GPIOs on the board?

On Monday, December 14, 2015 at 7:18:10 PM UTC-8, RobertCNelson wrote:
>
> On Mon, Dec 14, 2015 at 9:15 PM, Sam Daleo <ssd...@gmail.com > 
> wrote: 
> > Oh, cool. Should I install the 8.2 image from the website, install 
> > linux-image-4.1.14-bone-rt-r17  using apt-get and then update the 
> kernel? 
>
> Either or.. they both do the same thing.. the "update_kernel.sh" 
> always get's the latest.. So in a month's time, when this email 
> exchange is old, "bone17" will be long replaced. ;) 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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.

Re: [beagleboard] /sys/device/bone_capemgr* doesn't exist on fresh image

[Sam Daleo]

Oh, cool. Should I install the 8.2 image from the website, 
install linux-image-4.1.14-bone-rt-r17  using apt-get and then update the 
kernel?

Hey, quick question. Trying to 

On Monday, December 14, 2015 at 6:45:05 PM UTC-8, RobertCNelson wrote:
>
> On Mon, Dec 14, 2015 at 8:32 PM, Sam Daleo <ssd...@gmail.com > 
> wrote: 
> > Ah, thank you for the help! I'll give that a try. 
> > 
> > Yeah, doing a quick google search I found this thread and was running 
> into 
> > an issue with trying to use the PRU so I figured I'd give this a try. 
>
> For the pru, compatible with 3.8 you can use: 
>
> 4.1.x-bone 
>
> linux-image-4.1.14-bone17 
>
> or the real time version: 
>
> linux-image-4.1.14-bone-rt-r17 
>
> With the magic script: 
>
> cd /opt/scripts/tools/ 
> git pull 
>
> sudo ./update_kernel.sh --bone-kernel --lts 
>
> or 
>
> sudo ./update_kernel.sh --bone-rt-kernel --lts 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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.