[beagleboard] Problem enabling SPI and UARTs (4.5 kernel)

[Thomas Andrews]

I have just upgraded to a 4.5.0-rc4+ kernel that I built, and I'm having 
trouble getting SPI0 and UARTs 1 & 4 working again. I built the kernel 
with CONFIG_BONE_CAPEMGR=y

cat /sys/devices/platform/bone_capemgr/slots
0: PF -1 
1: PF -1 
2: PF -1 
3: PF -1 

Here is my problem:
echo 'BB-SPIDEV0' > /sys/devices/platform/bone_capemgr/slots
-bash: echo: write error: Invalid argument

What am I missing? Is there perhaps some kernel build option that I've 
missed?

This was an upgrade from 3.8.13-bone47, so I'm somewhat out of date..

Thanks!
Thomas

-- 
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: Problem enabling SPI and UARTs (4.5 kernel)

[DLF]

Hi 

follow William's blog it provides some insights for the 4.x kernels ... 
very useful
http://www.embeddedhobbyist.com/2015/09/beaglebone-black-updating-device-tree-files/
however.
there are some points I could not figure out with SPIDEV0
https://groups.google.com/forum/#!category-topic/beagleboard/gOynYr8fgns

good luck

On Thursday, 25 February 2016 09:59:58 UTC+1, Thomas Andrews wrote:
>
> I have just upgraded to a 4.5.0-rc4+ kernel that I built, and I'm having 
> trouble getting SPI0 and UARTs 1 & 4 working again. I built the kernel 
> with CONFIG_BONE_CAPEMGR=y
>
> cat /sys/devices/platform/bone_capemgr/slots
> 0: PF -1 
> 1: PF -1 
> 2: PF -1 
> 3: PF -1 
>
> Here is my problem:
> echo 'BB-SPIDEV0' > /sys/devices/platform/bone_capemgr/slots
> -bash: echo: write error: Invalid argument
>
> What am I missing? Is there perhaps some kernel build option that I've 
> missed?
>
> This was an upgrade from 3.8.13-bone47, so I'm somewhat out of date..
>
> Thanks!
> Thomas
>

-- 
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: Problem enabling SPI and UARTs (4.5 kernel)

[Thomas Andrews]

Some extra info - I get the messages below in dmesg after executing this -
echo 'BB-SPIDEV0' > /sys/devices/platform/bone_capemgr/slots

[ 9170.846742] bone_capemgr bone_capemgr: part_number 'BB-SPIDEV0', version 
'N/A'
[ 9170.846781] bone_capemgr bone_capemgr: slot #15: override
[ 9170.846797] bone_capemgr bone_capemgr: Using override eeprom data at 
slot 15
[ 9170.846814] bone_capemgr bone_capemgr: slot #15: 'Override Board 
Name,00A0,Override Manuf,BB-SPIDEV0'
[ 9170.847345] __of_adjust_tree_phandle_references: Could not find target 
property 'fixup' @/__local_fixups__
[ 9170.857775] bone_capemgr bone_capemgr: slot #15: Failed to resolve tree

-- 
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: Problem enabling SPI and UARTs (4.5 kernel)

[DLF]

I think you have the wrong (old) DTC version.  It has changed and should be 
something like Version: DTC 1.4.1xxx

On Thursday, 25 February 2016 10:40:28 UTC+1, Thomas Andrews wrote:
>
> Some extra info - I get the messages below in dmesg after executing this -
> echo 'BB-SPIDEV0' > /sys/devices/platform/bone_capemgr/slots
>
> [ 9170.846742] bone_capemgr bone_capemgr: part_number 'BB-SPIDEV0', 
> version 'N/A'
> [ 9170.846781] bone_capemgr bone_capemgr: slot #15: override
> [ 9170.846797] bone_capemgr bone_capemgr: Using override eeprom data at 
> slot 15
> [ 9170.846814] bone_capemgr bone_capemgr: slot #15: 'Override Board 
> Name,00A0,Override Manuf,BB-SPIDEV0'
> [ 9170.847345] __of_adjust_tree_phandle_references: Could not find target 
> property 'fixup' @/__local_fixups__
> [ 9170.857775] bone_capemgr bone_capemgr: slot #15: Failed to resolve tree
>
>

-- 
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] Re: Problem enabling SPI and UARTs (4.5 kernel)

[Thomas Andrews]

On 02/25/2016 11:50 AM, DLF wrote:
I think you have the wrong (old) DTC version.  It has changed and 
should be something like Version: DTC 1.4.1xxx


In /usr/src/kernel/linux-dev-master/KERNEL/scripts/dtc/ I have
Version: DTC 1.4.1-g5aaeb52e

However in /usr/bin/ I have
Version: DTC 1.4.0

So, ... I need to understand when dtc is actually called. When does 
(did?) it actually compile the dts files?


All of the dtbo files in /lib/firmware are over 2 years old. Is this 
where the problem is?


Many thanks!
Thomas

--
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: Problem enabling SPI and UARTs (4.5 kernel)

[DLF]

yes - it sounds like the problem...

from William's blog, I'd look at this part
 
$ sudo apt-get install git
$ git clone https://github.com/beagleboard/bb.org-overlays
$ cd bb.org-overlays/
$ ./dtc-overlay.sh
$ sudo ./install.sh

and then check that the overlays in /lib/firmware are current.

BTW, backup any data before following my comments

cheers





On Thursday, 25 February 2016 09:59:58 UTC+1, Thomas Andrews wrote:
>
> I have just upgraded to a 4.5.0-rc4+ kernel that I built, and I'm having 
> trouble getting SPI0 and UARTs 1 & 4 working again. I built the kernel 
> with CONFIG_BONE_CAPEMGR=y
>
> cat /sys/devices/platform/bone_capemgr/slots
> 0: PF -1 
> 1: PF -1 
> 2: PF -1 
> 3: PF -1 
>
> Here is my problem:
> echo 'BB-SPIDEV0' > /sys/devices/platform/bone_capemgr/slots
> -bash: echo: write error: Invalid argument
>
> What am I missing? Is there perhaps some kernel build option that I've 
> missed?
>
> This was an upgrade from 3.8.13-bone47, so I'm somewhat out of date..
>
> Thanks!
> Thomas
>

-- 
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] Re: Problem enabling SPI and UARTs (4.5 kernel)

[William Hermans]

>
> *All of the dtbo files in /lib/firmware are over 2 years old. Is this
> where the problem is?*
>

Very likely yes, that is where the problem is. The old binary files have
been compiled with the old device tree compiler, and will not work.
However, if you have old source files those stand a very good chance to be
compiled successfully with the new compiler. There are a few exceptions,
but very few from what I understand. I've actually yet to find a source
file that hadn't compiled properly yet.

On Thu, Feb 25, 2016 at 3:40 AM, DLF  wrote:

> yes - it sounds like the problem...
>
> from William's blog, I'd look at this part
>
> $ sudo apt-get install git
> $ git clone https://github.com/beagleboard/bb.org-overlays
> $ cd bb.org-overlays/
> $ ./dtc-overlay.sh
> $ sudo ./install.sh
>
> and then check that the overlays in /lib/firmware are current.
>
> BTW, backup any data before following my comments
>
> cheers
>
>
>
>
>
> On Thursday, 25 February 2016 09:59:58 UTC+1, Thomas Andrews wrote:
>
>> I have just upgraded to a 4.5.0-rc4+ kernel that I built, and I'm having
>> trouble getting SPI0 and UARTs 1 & 4 working again. I built the kernel
>> with CONFIG_BONE_CAPEMGR=y
>>
>> cat /sys/devices/platform/bone_capemgr/slots
>> 0: PF -1
>> 1: PF -1
>> 2: PF -1
>> 3: PF -1
>>
>> Here is my problem:
>> echo 'BB-SPIDEV0' > /sys/devices/platform/bone_capemgr/slots
>> -bash: echo: write error: Invalid argument
>>
>> What am I missing? Is there perhaps some kernel build option that I've
>> missed?
>>
>> This was an upgrade from 3.8.13-bone47, so I'm somewhat out of date..
>>
>> Thanks!
>> Thomas
>>
> --
> 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.
>

-- 
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] PRU - clear an event interrupt

[alexbattiston]

Hello,
I have problem with the interrupts.

With this command I check if there is an interrupt
QBBSBACK_LOOP, r31, 30

How can I clear the interrupt?
I have tried to find a solution via from am335xPruReferenceGuide.pdf
"6.2.2.5 Interrupt Status Clearing
For clearing the status of an interrupt, whose interrupt number is N, write 
a 1 to the Nth bit position in the system interrupt status enabled/clear 
registers (SECR1-SECR2). System interrupt N can also be cleared by writing 
the value N into the system interrupt status indexed clear register (SICR)."

How can I do in practice?




-- 
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: simple kernel module error

[amey11637]

Hi,
I'm getting same error for cross compiling LKM for ARM architecture. I am 
using Beaglebone Black(uname -r = 4.1.13-g8dc6617) and host machine (uname 
-r =3.19.0-49-generic)
LKM module for same host machine is working fine.
Any idea?
Thanks!

On Friday, June 15, 2012 at 12:35:57 AM UTC+5:30, Kamran wrote:
>
> Hi all. i made a simple hello world kernel module for beaglebone.
> after make command following is the output.
>
>
> root@beaglebone:~/project/modules/hello-world# make
> make -C /lib/modules/3.2.14/build 
> SUBDIRS=/home/root/project/modules/hello-world modules
> make[1]: Entering directory `/usr/src/linux-3.2.18'
>
>   WARNING: Symbol version dump /usr/src/linux-3.2.18/Module.symvers
>is missing; modules will have no dependencies and modversions.
>
>   CC [M]  /home/root/project/modules/hello-world/hello.o
> In file included from include/linux/gfp.h:4:0,
>  from include/linux/kmod.h:22,
>  from include/linux/module.h:13,
>  from /home/root/project/modules/hello-world/hello.c:1:
> include/linux/mmzone.h:18:30: fatal error: generated/bounds.h: No such 
> file or directory
> compilation terminated.
> make[2]: *** [/home/root/project/modules/hello-world/hello.o] Error 1
> make[1]: *** [_module_/home/root/project/modules/hello-world] Error 2
> make[1]: Leaving directory `/usr/src/linux-3.2.18'
> make: *** [default] Error 2
>
>
> can some one point out what wrong i have done.Thanks in advance.

-- 
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] Re: Problem enabling SPI and UARTs (4.5 kernel)

[Thomas Andrews]

On 02/25/2016 12:40 PM, DLF wrote:

$git clonehttps://github.com/beagleboard/bb.org-overlays
$cd bb.org-overlays/
$./dtc-overlay.sh
$sudo./install.sh


Thanks DLF and William, I followed this procedure (with some minor 
modifications to use my (already existing) dtc that came with the 
kernel), and it is working now.


Thanks again,
Thomas

--
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] Change dhclient log level on RobertCNelson 4.1.10 kernel?

[pbft]

dhclient is filling the daemon.log file with needless junk. I'd like to 
have only actual problems logged.

I'd like to change the dhclient log level, but I can't figure out where 
dhclient is invoked or where options could be specified.

Sample logfile entries:

Feb 25 06:57:28 vesta dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 
67 interval 10
Feb 25 06:57:38 vesta dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 
67 interval 10
Feb 25 06:57:48 vesta dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 
67 interval 15
Feb 25 06:57:54 vesta dhclient: DHCPREQUEST on eth0 to 192.168.1.10 port 67
Feb 25 06:57:54 vesta dhclient: DHCPACK from 192.168.1.10
Feb 25 06:57:54 vesta dhclient: bound to 192.168.1.179 -- renewal in 299 
seconds.
Feb 25 06:58:03 vesta dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 
67 interval 12

Don't know if this is BeagleBone-specific or just a systemd question, but 
help would be *really* 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PRU - clear an event interrupt

[alexbattiston]

.macro  MOV32
.mparam dst, src
MOV dst.w0, src & 0x
MOV dst.w2, src >> 16
.endm

#define SICR_OFFSET   0x24
#define CONST_PRUSSINTC C0
#define temp32reg r10

// clear interrupt
MOV32 temp32reg, (0x | 21)
SBCO  temp32reg, CONST_PRUSSINTC, SICR_OFFSET, 4


On Thursday, February 25, 2016 at 2:18:22 PM UTC+2, alexba...@gmail.com 
wrote:
>
> Hello,
> I have problem with the interrupts.
>
> With this command I check if there is an interrupt
> QBBSBACK_LOOP, r31, 30
>
> How can I clear the interrupt?
> I have tried to find a solution via from am335xPruReferenceGuide.pdf
> "6.2.2.5 Interrupt Status Clearing
> For clearing the status of an interrupt, whose interrupt number is N, 
> write a 1 to the Nth bit position in the system interrupt status 
> enabled/clear registers (SECR1-SECR2). System interrupt N can also be 
> cleared by writing the value N into the system interrupt status indexed 
> clear register (SICR)."
>
> How can I do in practice?
>
>
>
>
>

-- 
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: opencv videocapture on beaglebone black

[Wally Bkg]

I went through this a few months ago and got nowhere.  The problem seems to 
be in the uvc driver.  To troubleshoot outside of openCV I installed 
v4l-utils fswebcam gpicview guvcview and permuted available kernels and 
never could get image capture to work for more than one frame.  I posted a 
thread about it here at the time.  I gave up and got another RPi2 for this 
project instead.  I did have success with  Derek Molloy's examples on the 
old Angstrom image, but Angstrom is too old and has been abandoned, so I 
didn't want to use it. 



On Wednesday, February 17, 2016 at 6:29:50 PM UTC-6, joelk wrote:
>
> Has anybody managed to capture video from a usb webcam on a BBB with any 
> recent Linux distribution using OpenCV cv::VideoCapture functions?
>
> I'm using a Logitech C615 which works perfectly with OpenCV on x86 PCs and 
> on a Raspberry Pi 2 (a little slow but it works) running the latest 
> Raspbian Jessie image.
>
> But I haven't yet managed to get anything but completely black images 
> running the same program on my BBB.  I've tried it with a recent Arch Linux 
> image.  I've tried Ubuntu 14.04, Debian 7.9 and 8.3 (with a few different 
> kernels) from BeagleBoard.  Nothing!  No problems doing anything else in 
> OpenCV -- it can load and display individual images and videos from files, 
> just not from the camera.  And in all of these installations I can capture 
> video from the camera with other programs (using v4l2) -- just not with 
> OpenCV.
>
> I've seen Derek Molloy's videos demonstrating use of OpenCV on a BBB -- 
> but he was running it under Angstrom, and as far as I can see the last 
> Angstrom distro was at least 3 years ago.
>
> Any suggestions for something more recent?
>
> By the way, here's a sample of a program that's fails to capture any video 
> on the BBB (it displays the frame size and then just gives a series of 
> "select timeout" messages):
>
>
> #include 
>> #include 
>>
>> int main(int argc, char *argv[]) {
>>   cv::VideoCapture cap;
>>
>>   cap.open(0);
>>
>>   if(!cap.isOpened()) {
>> std::cout << "Did not connect to camera."  << std::endl;;
>> return -1;
>>   }
>>
>>   double dWidth = cap.get(CV_CAP_PROP_FRAME_WIDTH);
>>   double dHeight = cap.get(CV_CAP_PROP_FRAME_HEIGHT);
>>
>>   std::cout << "Frame size: " << dWidth << " x " << dHeight << std::endl;
>>   cv::namedWindow("MyVideo",CV_WINDOW_AUTOSIZE);  
>>
>>   while(1) {
>> cv::Mat frame;
>> bool bSuccess = cap.read(frame);
>> if(!bSuccess) {
>>   std::cout << "failed to read frame" << std::endl;
>>   break;
>> }
>> cv::imshow("MyVideo", frame);
>> if(cv::waitKey(30) >= 0) break;
>>   }
>> 
>>   return 0;
>> }
>>
>
> Can't get much simpler than that.
>

-- 
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] Newbie unable to run BoneScript

[sarunas . straigis]

Hello,

I have just received my BBB and am trying to set it up.

I launched some examples of blinking led by connecting to it via browser 
http://192.168.7.2 and it worked fine. 
Then I flashed newest Debian Jessie I found on beaglebone.org and now I am 
unable to blink user leds using the same method. 
I tried apt-get update, apt-get dist-upgrade but result is the same.  

Website says *Your board is connected!*
BeagleBone running BoneScript 0.2.5 at beaglebone.local
and examples return no error, but LED's do not blink. 

Also, i am unable to access cloud9 ide after flashing new image. It just 
fails to connect. 

Another stupid question - how do I run debian terminal in root mode? Or 
should I just always use sudo? 

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] debian testing: 2016-01-31 (Node-RED)

[Wally Bkg]

Sorry, but I've been away for awhile, but to answer your question, the main 
reason I'm thinking node-red and its bonescript nodes instead of "just 
programming in whatever" is basically two reasons:

1) My buddy has zero programming skills or experience, although he is 
expert in electronics having built several non-autonomous robots (RC 
controlled), and lives "off-grid" with a solar power system he's installed 
and maintains.  He's also 80+ miles away so my "hands-on" help is very 
intermittent at best.

2) There are multiple buildings and distributed solar power systems, all 
covered by WiFi.  While all his monitoring and  control  is pretty 
straightforward,  the network code for multiple controller interaction and 
status reporting would totally blow him away.  But node-red, and mqtt 
nicely offers a solution to this with "visual programming" (ever heard of 
LabView? I'm not a fan but it works well for scientists and engineers who 
aren't programmers).  It seems to me he *is* the person the authors of such 
systems had in mind.   Its just too bad that things aren't "smoother" out 
of the box.

While I don't see node-red and bonescript as particularly useful to me, if 
it "just worked" after installing an image (or better if it worked with the 
images shipped in the eMMC) it would be easy to recommend as a starting 
point or alternative to Arduino  (Arduino is a great starting point if one 
is motivated to learn programming but it falls down if you need networking).

Frankly all this /sys/class/ file read/write and device-tree overlay stuff 
is a nightmare and nobody seems to care if changes break anything 
(it especially breaks the documentation such as it is).  To expect/demand 
that a non-programmer  jump into it to be able to do anything is absurd.

I'm planning to down load the new 2016-02-21 image (or what follows by the 
time I actually get a chance to do it) and re-evaluate the situation, 
hopefully things are getting better.

--wally.


On Tuesday, February 2, 2016 at 5:31:50 PM UTC-6, William Hermans wrote:
>
> Wally, what was the original purpose of this post ? E.G. what was it your 
> buddy wanted to accomplish ? If it's just twiddle a couple of GPIO's and 
> read an ADC or two. That can be done fairly easily in Nodejs, without even 
> any plugins. So not need for Node-RED, or C/C++ if not wanted.
>
>>
>>

-- 
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] debian testing: 2016-01-31 (Node-RED)

[William Hermans]

>
> *Frankly all this /sys/class/ file read/write and device-tree overlay
> stuff is a nightmare and nobody seems to care if changes break anything
> (it especially breaks the documentation such as it is).  To expect/demand
> that a non-programmer  jump into it to be able to do anything is absurd.*
>

I do not know . . . I guess I will always view "solutions" that include
labview, or node-red( this type of thing ) as an excuse to not have to
learn how to write code. Which I view as an incredibly lame excuse . . .
because. This gives people who do not understand a system the ability to
build that system. Further, it keeps them from understanding the system
it's running on, unless they push themselves. Which I doubt most will do.

What will your friend do when he runs into a problem that is not easily
solved with, or is not solvable with this current solution ?

Anyway, with the above aside, I get why you are interested in node-red now.
I've a friend here who is a very good EE too, but does not like to code. So
perhaps this is something he would do too. If I did not write code for his
hardware projects that need it.




On Thu, Feb 25, 2016 at 12:40 PM, Wally Bkg  wrote:

> Sorry, but I've been away for awhile, but to answer your question, the
> main reason I'm thinking node-red and its bonescript nodes instead of "just
> programming in whatever" is basically two reasons:
>
> 1) My buddy has zero programming skills or experience, although he is
> expert in electronics having built several non-autonomous robots (RC
> controlled), and lives "off-grid" with a solar power system he's installed
> and maintains.  He's also 80+ miles away so my "hands-on" help is very
> intermittent at best.
>
> 2) There are multiple buildings and distributed solar power systems, all
> covered by WiFi.  While all his monitoring and  control  is pretty
> straightforward,  the network code for multiple controller interaction and
> status reporting would totally blow him away.  But node-red, and mqtt
> nicely offers a solution to this with "visual programming" (ever heard of
> LabView? I'm not a fan but it works well for scientists and engineers who
> aren't programmers).  It seems to me he *is* the person the authors of such
> systems had in mind.   Its just too bad that things aren't "smoother" out
> of the box.
>
> While I don't see node-red and bonescript as particularly useful to me, if
> it "just worked" after installing an image (or better if it worked with the
> images shipped in the eMMC) it would be easy to recommend as a starting
> point or alternative to Arduino  (Arduino is a great starting point if one
> is motivated to learn programming but it falls down if you need networking).
>
> Frankly all this /sys/class/ file read/write and device-tree overlay stuff
> is a nightmare and nobody seems to care if changes break anything
> (it especially breaks the documentation such as it is).  To expect/demand
> that a non-programmer  jump into it to be able to do anything is absurd.
>
> I'm planning to down load the new 2016-02-21 image (or what follows by the
> time I actually get a chance to do it) and re-evaluate the situation,
> hopefully things are getting better.
>
> --wally.
>
>
> On Tuesday, February 2, 2016 at 5:31:50 PM UTC-6, William Hermans wrote:
>>
>> Wally, what was the original purpose of this post ? E.G. what was it your
>> buddy wanted to accomplish ? If it's just twiddle a couple of GPIO's and
>> read an ADC or two. That can be done fairly easily in Nodejs, without even
>> any plugins. So not need for Node-RED, or C/C++ if not wanted.
>>
>>>
>>> --
> 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.
>

-- 
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: Newbie unable to run BoneScript

[sarunas . straigis]

I found the solution myself. The Kernel version 4.x.x.x included in newest 
image does not support BoneScript. I downgraded kernel to 3.8 and it works 
great. 

thanks alot for my day wasted "Quick start guide" :D

-- 
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] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[lajos]

Hello-

I have a BBB rev c with the Debian Jessie image on an SD card. I compiled 
the 4.4.2 bone rt kernel with RFKILL disabled, otherwise default settings 
built with github.com/RobertCNelson/bb-kernel. (Thanks for the great kernel 
builder!!!)

uname -a
Linux beagle 4.4.2-bone-rt-r5 #1 PREEMPT RT Thu Feb 25 11:36:52 EST 2016 
armv7l GNU/Linux

When I boot up the system I have several (8) systemd-udevd processes using 
up all the cpu, but they are killed after a while with this message in 
syslog:

Feb 25 19:46:54 beagle systemd-udevd[212]: worker [636] 
/devices/platform/ocp/4a30.pruss/uio/uio0 timeout; kill it
Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2259 
'/devices/platform/ocp/4a30.pruss/uio/uio0' killed
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [684] 
/devices/platform/ocp/4a30.pruss/uio/uio1 timeout; kill it
Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2260 
'/devices/platform/ocp/4a30.pruss/uio/uio1' killed
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [685] 
/devices/platform/ocp/4a30.pruss/uio/uio2 timeout; kill it
Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2261 
'/devices/platform/ocp/4a30.pruss/uio/uio2' killed
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [686] 
/devices/platform/ocp/4a30.pruss/uio/uio3 timeout; kill it
Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2262 
'/devices/platform/ocp/4a30.pruss/uio/uio3' killed
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [832] 
/devices/platform/ocp/4a30.pruss/uio/uio4 timeout; kill it
Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2263 
'/devices/platform/ocp/4a30.pruss/uio/uio4' killed
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [834] 
/devices/platform/ocp/4a30.pruss/uio/uio5 timeout; kill it
Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2264 
'/devices/platform/ocp/4a30.pruss/uio/uio5' killed
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [850] 
/devices/platform/ocp/4a30.pruss/uio/uio6 timeout; kill it
Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2265 
'/devices/platform/ocp/4a30.pruss/uio/uio6' killed
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [856] 
/devices/platform/ocp/4a30.pruss/uio/uio7 timeout; kill it
Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2266 
'/devices/platform/ocp/4a30.pruss/uio/uio7' killed
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [636] terminated by 
signal 9 (Killed)
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [684] terminated by 
signal 9 (Killed)
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [685] terminated by 
signal 9 (Killed)
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [686] terminated by 
signal 9 (Killed)
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [832] terminated by 
signal 9 (Killed)
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [834] terminated by 
signal 9 (Killed)
Feb 25 19:46:54 beagle systemd-udevd[212]: worker [850] terminated by 
signal 9 (Killed)

As I understand prus are supported with the *bone* kernels. Any ideas why 
they don't work? Maybe in conflict with something?

I have HDMI Audio/Video and eMMC turned off in uEnv.txt:

uname_r=4.4.2-bone-rt-r5
dtb=am335x-boneblack-overlay.dtb
cmdline=coherent_pool=1M quiet cape_universal=enable
 
And this is my lsmod:

Module  Size  Used by
c_can_platform  6560  0 
c_can   9531  1 c_can_platform
uio_pruss   4928  0 
can_dev11689  1 c_can
spidev  7481  0 
tieqep  8758  0 
pwm_tiecap  3652  0 
pwm_tiehrpwm4706  0 
usb_f_acm   7193  1 
u_serial   10716  3 usb_f_acm
usb_f_rndis22093  1 
g_multi 5441  0 
usb_f_mass_storage 41731  2 g_multi
u_ether11887  2 usb_f_rndis,g_multi
libcomposite   43393  4 
usb_f_acm,usb_f_rndis,g_multi,usb_f_mass_storage
ccm 6710  3 
arc42019  2 
rtl8192cu  52442  0 
rtl_usb 9579  1 rtl8192cu
rtl8192c_common37747  1 rtl8192cu
rtlwifi56114  3 rtl_usb,rtl8192c_common,rtl8192cu
mac80211  490892  3 rtl_usb,rtlwifi,rtl8192cu
cfg80211  419275  2 mac80211,rtlwifi
joydev  8336  0 
omap_aes   13637  0 
omap_sham  21619  0 
omap_rng4359  0 
rng_core7099  1 omap_rng
evdev  10516  1 
spi_omap2_mcspi8  0 
uio_pdrv_genirq 3661  0 
uio 8760  2 uio_pruss,uio_pdrv_genirq
leds_gpio   3420  0 


Any help would be appreciated!

Thanks-
Lajos


-- 
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://g

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[William Hermans]

>
> *As I understand prus are supported with the *bone* kernels. Any ideas why
> they don't work? Maybe in conflict with something?*
>

First, which device tree file are you using for the PRU's, and have you
loaded it ?

On Thu, Feb 25, 2016 at 2:46 PM, lajos  wrote:

> Hello-
>
> I have a BBB rev c with the Debian Jessie image on an SD card. I compiled
> the 4.4.2 bone rt kernel with RFKILL disabled, otherwise default settings
> built with github.com/RobertCNelson/bb-kernel. (Thanks for the great
> kernel builder!!!)
>
> uname -a
> Linux beagle 4.4.2-bone-rt-r5 #1 PREEMPT RT Thu Feb 25 11:36:52 EST 2016
> armv7l GNU/Linux
>
> When I boot up the system I have several (8) systemd-udevd processes using
> up all the cpu, but they are killed after a while with this message in
> syslog:
>
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [636]
> /devices/platform/ocp/4a30.pruss/uio/uio0 timeout; kill it
> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2259
> '/devices/platform/ocp/4a30.pruss/uio/uio0' killed
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [684]
> /devices/platform/ocp/4a30.pruss/uio/uio1 timeout; kill it
> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2260
> '/devices/platform/ocp/4a30.pruss/uio/uio1' killed
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [685]
> /devices/platform/ocp/4a30.pruss/uio/uio2 timeout; kill it
> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2261
> '/devices/platform/ocp/4a30.pruss/uio/uio2' killed
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [686]
> /devices/platform/ocp/4a30.pruss/uio/uio3 timeout; kill it
> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2262
> '/devices/platform/ocp/4a30.pruss/uio/uio3' killed
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [832]
> /devices/platform/ocp/4a30.pruss/uio/uio4 timeout; kill it
> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2263
> '/devices/platform/ocp/4a30.pruss/uio/uio4' killed
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [834]
> /devices/platform/ocp/4a30.pruss/uio/uio5 timeout; kill it
> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2264
> '/devices/platform/ocp/4a30.pruss/uio/uio5' killed
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [850]
> /devices/platform/ocp/4a30.pruss/uio/uio6 timeout; kill it
> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2265
> '/devices/platform/ocp/4a30.pruss/uio/uio6' killed
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [856]
> /devices/platform/ocp/4a30.pruss/uio/uio7 timeout; kill it
> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2266
> '/devices/platform/ocp/4a30.pruss/uio/uio7' killed
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [636] terminated by
> signal 9 (Killed)
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [684] terminated by
> signal 9 (Killed)
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [685] terminated by
> signal 9 (Killed)
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [686] terminated by
> signal 9 (Killed)
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [832] terminated by
> signal 9 (Killed)
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [834] terminated by
> signal 9 (Killed)
> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [850] terminated by
> signal 9 (Killed)
>
> As I understand prus are supported with the *bone* kernels. Any ideas why
> they don't work? Maybe in conflict with something?
>
> I have HDMI Audio/Video and eMMC turned off in uEnv.txt:
>
> uname_r=4.4.2-bone-rt-r5
> dtb=am335x-boneblack-overlay.dtb
> cmdline=coherent_pool=1M quiet cape_universal=enable
>
> And this is my lsmod:
>
> Module  Size  Used by
> c_can_platform  6560  0
> c_can   9531  1 c_can_platform
> uio_pruss   4928  0
> can_dev11689  1 c_can
> spidev  7481  0
> tieqep  8758  0
> pwm_tiecap  3652  0
> pwm_tiehrpwm4706  0
> usb_f_acm   7193  1
> u_serial   10716  3 usb_f_acm
> usb_f_rndis22093  1
> g_multi 5441  0
> usb_f_mass_storage 41731  2 g_multi
> u_ether11887  2 usb_f_rndis,g_multi
> libcomposite   43393  4
> usb_f_acm,usb_f_rndis,g_multi,usb_f_mass_storage
> ccm 6710  3
> arc42019  2
> rtl8192cu  52442  0
> rtl_usb 9579  1 rtl8192cu
> rtl8192c_common37747  1 rtl8192cu
> rtlwifi56114  3 rtl_usb,rtl8192c_common,rtl8192cu
> mac80211  490892  3 rtl_usb,rtlwifi,rtl8192cu
> cfg80211  419275  2 mac80211,rtlwifi
> joydev  8336  0
> omap_aes   13637  0
> omap_sham  21619  0
> omap_rng4359  0
> rng_core7099  1 omap_rng
> evdev  10516  1
> spi_omap2_mcspi8  0
> uio_pdrv_genirq 3661  0
> uio 8760  2 uio_p

[beagleboard] Problem with BB-UART1 overlay using P8 header pins

[Wally Bkg]

Running on a BBW.
~# cat /etc/dogtag
BeagleBoard.org Debian Image 2015-11-12

~# uname -a
Linux alarmbone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015 
armv7l GNU/Linux

~# 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,univ-all

I'm basically using all of the GPIO on the P8 Header.

I now want a UART or two, for some new functionality,  seems UART1 & UART2 
only use pins on P9 Header so in /boot/uEnv.txt so I added:
##Example v4.1.x
#cape_disable=bone_capemgr.disable_partno=
cape_enable=bone_capemgr.enable_partno=BB-UART1

After I reboot  the slot 4: becomes BB-UART1 
and a simple loopback test with minicom after jumpering P9_22 to P9_24 
 shows the UART /dev/ttyO1 is working.  But none of the P8 GPIO are 
exported. No problem as my
code exported them anyways, even though it seemed not required with 4.1.x 
kernels and the BBW "default" dtb, but seems P8_20 & P8_21 are now used for 
something else and my code
always reads them as low which messes everything up.  I was expecting an 
error when I did the export if there was a conflict, but didn't catch any 
in my code (assumed the open would fail if there was a problem).

I also tried
cape_enable=bone_capemgr.enable_partno=cape_universal,BB-UART1
with and without cape_universal=enable on the cmdline.
The slot 4: line disappears and a 5: line is added with BB-UART1
but no change, UART1 still works and p8 20&21 are still stuck at low.

Is my lib/firmware and/or kernel out of date, or somehow wrong? 

I thought UART1 was supposed to have rts & cts on P9 pins 19 & 20 according 
the tables in "Exploring Beaglebone" book with apparently no UART1 
functions on P8.

Is there an easy fix?  I'd prefer to have RTS/CTS available, although the 
device I'm ordering is supposed to support Xon/Xoff protocol as well.

I've been looking at 
https://github.com/cdsteinkuehler/beaglebone-universal-io and maybe using 
config-pin to enable uart1 but my /sys/devices/ paths aren't matching up 
very well with the docs  so I'm loathe to just stumble around with my very 
limited knowledge of pinmux and modes.

--wally.

-- 
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] uEnv.txt and Kernel 4.1 Device Overlays

[Emile Cormier]

Hello All,

I was attempting to configure uEnv.txt to enable the new Kernel 4.1 device 
overlays, using debian-8.3-console-armhf-2016-02-11. I mistakenly though 
that I had to rename /bbb-uEnv.txt to /uEnv.txt and make the changes there. 
Well, it turns out that it's /boot/uEnv.txt that you need to edit (in the 
/boot directory, not the root). The one under /boot has friendly, 
commented-out blocks that you can use to do things like disable HDMI, or 
enable a device overlay. I just though I'd share my silly mistake so that 
others don't repeat it and waste time.

For those who are not yet familiar with the new device overlays, check out 
the readme.md at https://github.com/RobertCNelson/bb.org-overlays. The new 
Debian images also come with a bunch of revised "canned" device overlay 
*.dtbo files that are ready to use. They are listed here 
.

Hope this helps someone,
Emile Cormier

-- 
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] uEnv.txt and Kernel 4.1 Device Overlays

[William Hermans]

Yes, that is because . . .

/uEnv.txt is the "real" uboot envoirnment file. You do not want to edit
this file unless you know absolutely what you're doing. Really though, this
file is not meant to be edited.

/boot/uEnv.txt is the second stage environment file, from which the first
stage file loads various variables for various configuration options.
Editing stuff in this file should not keep the board from booting. But it
is possible to configure this file in a way that will leave the board
unable to find it's proper kernel version.

On Thu, Feb 25, 2016 at 4:59 PM, Emile Cormier 
wrote:

> Hello All,
>
> I was attempting to configure uEnv.txt to enable the new Kernel 4.1
> device overlays, using debian-8.3-console-armhf-2016-02-11. I mistakenly
> though that I had to rename /bbb-uEnv.txt to /uEnv.txt and make the
> changes there. Well, it turns out that it's /boot/uEnv.txt that you need
> to edit (in the /boot directory, not the root). The one under /boot has
> friendly, commented-out blocks that you can use to do things like disable
> HDMI, or enable a device overlay. I just though I'd share my silly mistake
> so that others don't repeat it and waste time.
>
> For those who are not yet familiar with the new device overlays, check out
> the readme.md at https://github.com/RobertCNelson/bb.org-overlays. The
> new Debian images also come with a bunch of revised "canned" device overlay
> *.dtbo files that are ready to use. They are listed here
> .
>
> Hope this helps someone,
> Emile Cormier
>
> --
> 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.
>

-- 
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] BBW Upgrading Jessie console image 2015-11-12 to current lxqt 2016-02-21 image?

[Wally Bkg]

I've been running bone-debian-8.2-tester-2gb-armhf-2015-11-12-2gb.img.xz 
since shortly after it was released with great success on my BBW.  I've 
kept reasonably current with apt-get update ; apt-get upgrade, although 
there are 73 packages to be upgraded with c9-core-installer held back when 
I looked a few minutes ago.  Its installed to an 8GB SD card so space is 
not an issue.   This system has been running 24/7 since mid December doing 
an essential job, but the system is evolving with new features added 
incrementally, so I'd like to "roll" with Jessie as things progress.

~# cat /etc/dogtag
BeagleBoard.org Debian Image 2015-11-12

~# uname -a
Linux alarmbone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015 
armv7l GNU/Linux

Before I do this much of an upgrade, I'll shut the system down and "clone" 
the sdcard so I can quickly go back, should something go wrong, but before 
I start I'd like to know if I'm leaving out some packages that I don't know 
the names of.   


This part seem obvious and reasonably well documented, update kernel and 
dtb files, but is this the "correct" kernel to be tracking these Jessie 
Testing images?:
git clone https://github.com/beagleboard/bb.org-overlays cd 
./bb.org-overlays
./dtc-overlay.sh
./install.sh
cd /opt/scripts/tools
git pull
sudo ./update_kernel.sh --lts-4_1 --ti-channel


Next I'd like to install the basic lxqt package so things like gedit would 
work over ssh -X
What packages are needed to upgrade the 2GB console image to the 4GB lxqt 
testing image?


I'm also concerned about the various "installer" packages I've seen 
mentioned in various threads, like:
bb-bonescript-installer-beta
bb-node-red-installer

What others might I be missing from my 2015-11-12 image?

Or is it not really a viable option to try and evolve with apt-get update ; 
apt-get upgrade?


Things don't seem right with Jessie updates.  I ended up with an unusable 
system (no ssh, no usb gadget) after trying apt-get update ; apt-get 
upgrade trying to move from 8.2 to 8.3.  back in early December, so I'm 
being more careful this time.

Doing something that should be relatively "safe" (as I'm not sure I'll 
really use it, so unless it does really bad things all I risk 
is wasting some SD card space) but it didtn't work:
~# apt-get install bb-node-red-installer
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following extra packages will be installed:
  bb-npm-installer
The following NEW packages will be installed:
  bb-node-red-installer bb-npm-installer
0 upgraded, 2 newly installed, 0 to remove and 74 not upgraded.
Need to get 6,884 B of archives.
After this operation, 78.8 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://repos.rcn-ee.com/debian/ jessie/main bb-npm-installer all 
3.7.5-0rcnee1~bpo80+20160224+1 [2,800 B]
Get:2 http://repos.rcn-ee.com/debian/ jessie/main bb-node-red-installer all 
0.13.2-0rcnee1~bpo80+20160222+1 [4,084 B]
Fetched 6,884 B in 0s (40.7 kB/s)   
Selecting previously unselected package bb-npm-installer.
(Reading database ... 33721 files and directories currently installed.)
Preparing to unpack 
.../bb-npm-installer_3.7.5-0rcnee1~bpo80+20160224+1_all.deb ...
Unpacking bb-npm-installer (3.7.5-0rcnee1~bpo80+20160224+1) ...
Setting up bb-npm-installer (3.7.5-0rcnee1~bpo80+20160224+1) ...
bb-npm-installer:npm: [1.4.21]
bb-npm-installer:node: [v0.10.41]
bb-npm-installer:Installing: npm-3.7.5 (for bb-npm-installer)
/usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
npm@3.7.5 /usr/local/lib/node_modules/npm
bb-npm-installer:Installed
Selecting previously unselected package bb-node-red-installer.
(Reading database ... 33723 files and directories currently installed.)
Preparing to unpack 
.../bb-node-red-installer_0.13.2-0rcnee1~bpo80+20160222+1_all.deb ...
Unpacking bb-node-red-installer (0.13.2-0rcnee1~bpo80+20160222+1) ...
Setting up bb-node-red-installer (0.13.2-0rcnee1~bpo80+20160222+1) ...
bb-node-red-installer:npm: [1.4.21]
bb-node-red-installer:node: [v0.10.41]
bb-node-red-installer:Installing: systemd-0.2.6 (for node-red)
systemd@0.2.6 /usr/local/lib/node_modules/systemd
bb-node-red-installer:Installing: node-red-0.13.2 (for node-red)
 
> bcrypt@0.8.5 install 
/usr/local/lib/node_modules/node-red/node_modules/bcrypt
> node-gyp rebuild

make: Entering directory 
'/usr/local/lib/node_modules/node-red/node_modules/bcrypt/build'
  CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
Killed
dpkg: error processing package bb-node-red-installer (--configure):
 subprocess installed post-installation script returned error exit status 
137
Errors were encountered while processing:
 bb-node-red-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any ideas as to what is wrong?
Do I need a kernel update first? or somet

Re: [beagleboard] BBW Upgrading Jessie console image 2015-11-12 to current lxqt 2016-02-21 image?

[William Hermans]

>
> *dpkg: error processing package bb-node-red-installer (--configure):*
>
* subprocess installed post-installation script returned error exit status
137*

My understanding is that exit status 137 == exit status 128 + n where n
here would seem to be 9. So . . . SIGKILL 9 . . .

Quite possibly this is the oomkiller killing your process because it
thinks, or knows it's using too much memory.


On Thu, Feb 25, 2016 at 5:42 PM, Wally Bkg  wrote:

> I've been running bone-debian-8.2-tester-2gb-armhf-2015-11-12-2gb.img.xz
> since shortly after it was released with great success on my BBW.  I've
> kept reasonably current with apt-get update ; apt-get upgrade, although
> there are 73 packages to be upgraded with c9-core-installer held back when
> I looked a few minutes ago.  Its installed to an 8GB SD card so space is
> not an issue.   This system has been running 24/7 since mid December doing
> an essential job, but the system is evolving with new features added
> incrementally, so I'd like to "roll" with Jessie as things progress.
>
> ~# cat /etc/dogtag
> BeagleBoard.org Debian Image 2015-11-12
>
> ~# uname -a
> Linux alarmbone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015
> armv7l GNU/Linux
>
> Before I do this much of an upgrade, I'll shut the system down and "clone"
> the sdcard so I can quickly go back, should something go wrong, but before
> I start I'd like to know if I'm leaving out some packages that I don't know
> the names of.
>
>
> This part seem obvious and reasonably well documented, update kernel and
> dtb files, but is this the "correct" kernel to be tracking these Jessie
> Testing images?:
> git clone https://github.com/beagleboard/bb.org-overlays cd
> ./bb.org-overlays
> ./dtc-overlay.sh
> ./install.sh
> cd /opt/scripts/tools
> git pull
> sudo ./update_kernel.sh --lts-4_1 --ti-channel
>
>
> Next I'd like to install the basic lxqt package so things like gedit would
> work over ssh -X
> What packages are needed to upgrade the 2GB console image to the 4GB lxqt
> testing image?
>
>
> I'm also concerned about the various "installer" packages I've seen
> mentioned in various threads, like:
> bb-bonescript-installer-beta
> bb-node-red-installer
>
> What others might I be missing from my 2015-11-12 image?
>
> Or is it not really a viable option to try and evolve with apt-get update
> ; apt-get upgrade?
>
>
> Things don't seem right with Jessie updates.  I ended up with an unusable
> system (no ssh, no usb gadget) after trying apt-get update ; apt-get
> upgrade trying to move from 8.2 to 8.3.  back in early December, so I'm
> being more careful this time.
>
> Doing something that should be relatively "safe" (as I'm not sure I'll
> really use it, so unless it does really bad things all I risk
> is wasting some SD card space) but it didtn't work:
> ~# apt-get install bb-node-red-installer
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following extra packages will be installed:
>   bb-npm-installer
> The following NEW packages will be installed:
>   bb-node-red-installer bb-npm-installer
> 0 upgraded, 2 newly installed, 0 to remove and 74 not upgraded.
> Need to get 6,884 B of archives.
> After this operation, 78.8 kB of additional disk space will be used.
> Do you want to continue? [Y/n] Y
> Get:1 http://repos.rcn-ee.com/debian/ jessie/main bb-npm-installer all
> 3.7.5-0rcnee1~bpo80+20160224+1 [2,800 B]
> Get:2 http://repos.rcn-ee.com/debian/ jessie/main bb-node-red-installer
> all 0.13.2-0rcnee1~bpo80+20160222+1 [4,084 B]
> Fetched 6,884 B in 0s (40.7 kB/s)
> Selecting previously unselected package bb-npm-installer.
> (Reading database ... 33721 files and directories currently installed.)
> Preparing to unpack
> .../bb-npm-installer_3.7.5-0rcnee1~bpo80+20160224+1_all.deb ...
> Unpacking bb-npm-installer (3.7.5-0rcnee1~bpo80+20160224+1) ...
> Setting up bb-npm-installer (3.7.5-0rcnee1~bpo80+20160224+1) ...
> bb-npm-installer:npm: [1.4.21]
> bb-npm-installer:node: [v0.10.41]
> bb-npm-installer:Installing: npm-3.7.5 (for bb-npm-installer)
> /usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
> npm@3.7.5 /usr/local/lib/node_modules/npm
> bb-npm-installer:Installed
> Selecting previously unselected package bb-node-red-installer.
> (Reading database ... 33723 files and directories currently installed.)
> Preparing to unpack
> .../bb-node-red-installer_0.13.2-0rcnee1~bpo80+20160222+1_all.deb ...
> Unpacking bb-node-red-installer (0.13.2-0rcnee1~bpo80+20160222+1) ...
> Setting up bb-node-red-installer (0.13.2-0rcnee1~bpo80+20160222+1) ...
> bb-node-red-installer:npm: [1.4.21]
> bb-node-red-installer:node: [v0.10.41]
> bb-node-red-installer:Installing: systemd-0.2.6 (for node-red)
> systemd@0.2.6 /usr/local/lib/node_modules/systemd
> bb-node-red-installer:Installing: node-red-0.13.2 (for node-red)
>
> > bcrypt@0.8.5 install
> /usr/local/lib/node_modules/node-red/node_modules/bcrypt
> > node-gyp rebuild
>
> make: Entering directory

Re: [beagleboard] BBW Upgrading Jessie console image 2015-11-12 to current lxqt 2016-02-21 image?

[Robert Nelson]

On Thu, Feb 25, 2016 at 6:42 PM, Wally Bkg  wrote:
> I've been running bone-debian-8.2-tester-2gb-armhf-2015-11-12-2gb.img.xz
> since shortly after it was released with great success on my BBW.  I've kept
> reasonably current with apt-get update ; apt-get upgrade, although there are
> 73 packages to be upgraded with c9-core-installer held back when I looked a
> few minutes ago.  Its installed to an 8GB SD card so space is not an issue.
> This system has been running 24/7 since mid December doing an essential job,
> but the system is evolving with new features added incrementally, so I'd
> like to "roll" with Jessie as things progress.
>
> ~# cat /etc/dogtag
> BeagleBoard.org Debian Image 2015-11-12
>
> ~# uname -a
> Linux alarmbone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015
> armv7l GNU/Linux
>
> Before I do this much of an upgrade, I'll shut the system down and "clone"
> the sdcard so I can quickly go back, should something go wrong, but before I
> start I'd like to know if I'm leaving out some packages that I don't know
> the names of.
>
>
> This part seem obvious and reasonably well documented, update kernel and dtb
> files, but is this the "correct" kernel to be tracking these Jessie Testing
> images?:
> git clone https://github.com/beagleboard/bb.org-overlays cd
> ./bb.org-overlays
> ./dtc-overlay.sh
> ./install.sh
> cd /opt/scripts/tools
> git pull
> sudo ./update_kernel.sh --lts-4_1 --ti-channel
>
>
> Next I'd like to install the basic lxqt package so things like gedit would
> work over ssh -X
> What packages are needed to upgrade the 2GB console image to the 4GB lxqt
> testing image?
>
>
> I'm also concerned about the various "installer" packages I've seen
> mentioned in various threads, like:
> bb-bonescript-installer-beta
> bb-node-red-installer
>
> What others might I be missing from my 2015-11-12 image?
>
> Or is it not really a viable option to try and evolve with apt-get update ;
> apt-get upgrade?
>
>
> Things don't seem right with Jessie updates.  I ended up with an unusable
> system (no ssh, no usb gadget) after trying apt-get update ; apt-get upgrade
> trying to move from 8.2 to 8.3.  back in early December, so I'm being more
> careful this time.
>
> Doing something that should be relatively "safe" (as I'm not sure I'll
> really use it, so unless it does really bad things all I risk is wasting
> some SD card space) but it didtn't work:
> ~# apt-get install bb-node-red-installer
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following extra packages will be installed:
>   bb-npm-installer
> The following NEW packages will be installed:
>   bb-node-red-installer bb-npm-installer
> 0 upgraded, 2 newly installed, 0 to remove and 74 not upgraded.

Well, bb-node-red-installer/bb-npm-installer is something i packaged
in the last couple of weeks..  So if you have '74' other updates
pending..

Yeah, that's not something i've tested for yet..

So let's see what happens with the base image:

bone-debian-8.2-tester-2gb-armhf-2015-11-12-2gb.img.xz

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] BBW Upgrading Jessie console image 2015-11-12 to current lxqt 2016-02-21 image?

[William Hermans]

Wally, so . . . I probably should have put this in my last post, but I just
now thought of it so . . .

You have two options here.

First, you can setup a swap disk using external media temporarily while
running the upgrade processes and see if that fixes it. This will only work
if in fact this is a problem with the oomkiller.

Second, you can run strace on your executable to see whats going on when it
erroneously exits. And you'll probably want to pipe the output to a file.
Such as *strace  > filename*

On Thu, Feb 25, 2016 at 5:52 PM, William Hermans  wrote:

> *dpkg: error processing package bb-node-red-installer (--configure):*
>>
> * subprocess installed post-installation script returned error exit status
> 137*
>
> My understanding is that exit status 137 == exit status 128 + n where n
> here would seem to be 9. So . . . SIGKILL 9 . . .
>
> Quite possibly this is the oomkiller killing your process because it
> thinks, or knows it's using too much memory.
>
>
> On Thu, Feb 25, 2016 at 5:42 PM, Wally Bkg  wrote:
>
>> I've been running bone-debian-8.2-tester-2gb-armhf-2015-11-12-2gb.img.xz
>> since shortly after it was released with great success on my BBW.  I've
>> kept reasonably current with apt-get update ; apt-get upgrade, although
>> there are 73 packages to be upgraded with c9-core-installer held back when
>> I looked a few minutes ago.  Its installed to an 8GB SD card so space is
>> not an issue.   This system has been running 24/7 since mid December doing
>> an essential job, but the system is evolving with new features added
>> incrementally, so I'd like to "roll" with Jessie as things progress.
>>
>> ~# cat /etc/dogtag
>> BeagleBoard.org Debian Image 2015-11-12
>>
>> ~# uname -a
>> Linux alarmbone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015
>> armv7l GNU/Linux
>>
>> Before I do this much of an upgrade, I'll shut the system down and
>> "clone" the sdcard so I can quickly go back, should something go wrong, but
>> before I start I'd like to know if I'm leaving out some packages that I
>> don't know the names of.
>>
>>
>> This part seem obvious and reasonably well documented, update kernel and
>> dtb files, but is this the "correct" kernel to be tracking these Jessie
>> Testing images?:
>> git clone https://github.com/beagleboard/bb.org-overlays cd
>> ./bb.org-overlays
>> ./dtc-overlay.sh
>> ./install.sh
>> cd /opt/scripts/tools
>> git pull
>> sudo ./update_kernel.sh --lts-4_1 --ti-channel
>>
>>
>> Next I'd like to install the basic lxqt package so things like gedit
>> would work over ssh -X
>> What packages are needed to upgrade the 2GB console image to the 4GB lxqt
>> testing image?
>>
>>
>> I'm also concerned about the various "installer" packages I've seen
>> mentioned in various threads, like:
>> bb-bonescript-installer-beta
>> bb-node-red-installer
>>
>> What others might I be missing from my 2015-11-12 image?
>>
>> Or is it not really a viable option to try and evolve with apt-get update
>> ; apt-get upgrade?
>>
>>
>> Things don't seem right with Jessie updates.  I ended up with an unusable
>> system (no ssh, no usb gadget) after trying apt-get update ; apt-get
>> upgrade trying to move from 8.2 to 8.3.  back in early December, so I'm
>> being more careful this time.
>>
>> Doing something that should be relatively "safe" (as I'm not sure I'll
>> really use it, so unless it does really bad things all I risk
>> is wasting some SD card space) but it didtn't work:
>> ~# apt-get install bb-node-red-installer
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> The following extra packages will be installed:
>>   bb-npm-installer
>> The following NEW packages will be installed:
>>   bb-node-red-installer bb-npm-installer
>> 0 upgraded, 2 newly installed, 0 to remove and 74 not upgraded.
>> Need to get 6,884 B of archives.
>> After this operation, 78.8 kB of additional disk space will be used.
>> Do you want to continue? [Y/n] Y
>> Get:1 http://repos.rcn-ee.com/debian/ jessie/main bb-npm-installer all
>> 3.7.5-0rcnee1~bpo80+20160224+1 [2,800 B]
>> Get:2 http://repos.rcn-ee.com/debian/ jessie/main bb-node-red-installer
>> all 0.13.2-0rcnee1~bpo80+20160222+1 [4,084 B]
>> Fetched 6,884 B in 0s (40.7 kB/s)
>> Selecting previously unselected package bb-npm-installer.
>> (Reading database ... 33721 files and directories currently installed.)
>> Preparing to unpack
>> .../bb-npm-installer_3.7.5-0rcnee1~bpo80+20160224+1_all.deb ...
>> Unpacking bb-npm-installer (3.7.5-0rcnee1~bpo80+20160224+1) ...
>> Setting up bb-npm-installer (3.7.5-0rcnee1~bpo80+20160224+1) ...
>> bb-npm-installer:npm: [1.4.21]
>> bb-npm-installer:node: [v0.10.41]
>> bb-npm-installer:Installing: npm-3.7.5 (for bb-npm-installer)
>> /usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
>> npm@3.7.5 /usr/local/lib/node_modules/npm
>> bb-npm-installer:Installed
>> Selecting previously unselected package bb-node-red-installer.
>> (Reading database ... 33723 files 

Re: [beagleboard] BBW Upgrading Jessie console image 2015-11-12 to current lxqt 2016-02-21 image?

[Robert Nelson]

On Thu, Feb 25, 2016 at 6:55 PM, Robert Nelson  wrote:
> On Thu, Feb 25, 2016 at 6:42 PM, Wally Bkg  wrote:
>> I've been running bone-debian-8.2-tester-2gb-armhf-2015-11-12-2gb.img.xz
>> since shortly after it was released with great success on my BBW.  I've kept
>> reasonably current with apt-get update ; apt-get upgrade, although there are
>> 73 packages to be upgraded with c9-core-installer held back when I looked a
>> few minutes ago.  Its installed to an 8GB SD card so space is not an issue.
>> This system has been running 24/7 since mid December doing an essential job,
>> but the system is evolving with new features added incrementally, so I'd
>> like to "roll" with Jessie as things progress.
>>
>> ~# cat /etc/dogtag
>> BeagleBoard.org Debian Image 2015-11-12
>>
>> ~# uname -a
>> Linux alarmbone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015
>> armv7l GNU/Linux
>>
>> Before I do this much of an upgrade, I'll shut the system down and "clone"
>> the sdcard so I can quickly go back, should something go wrong, but before I
>> start I'd like to know if I'm leaving out some packages that I don't know
>> the names of.
>>
>>
>> This part seem obvious and reasonably well documented, update kernel and dtb
>> files, but is this the "correct" kernel to be tracking these Jessie Testing
>> images?:
>> git clone https://github.com/beagleboard/bb.org-overlays cd
>> ./bb.org-overlays
>> ./dtc-overlay.sh
>> ./install.sh
>> cd /opt/scripts/tools
>> git pull
>> sudo ./update_kernel.sh --lts-4_1 --ti-channel
>>
>>
>> Next I'd like to install the basic lxqt package so things like gedit would
>> work over ssh -X
>> What packages are needed to upgrade the 2GB console image to the 4GB lxqt
>> testing image?
>>
>>
>> I'm also concerned about the various "installer" packages I've seen
>> mentioned in various threads, like:
>> bb-bonescript-installer-beta
>> bb-node-red-installer
>>
>> What others might I be missing from my 2015-11-12 image?
>>
>> Or is it not really a viable option to try and evolve with apt-get update ;
>> apt-get upgrade?
>>
>>
>> Things don't seem right with Jessie updates.  I ended up with an unusable
>> system (no ssh, no usb gadget) after trying apt-get update ; apt-get upgrade
>> trying to move from 8.2 to 8.3.  back in early December, so I'm being more
>> careful this time.
>>
>> Doing something that should be relatively "safe" (as I'm not sure I'll
>> really use it, so unless it does really bad things all I risk is wasting
>> some SD card space) but it didtn't work:
>> ~# apt-get install bb-node-red-installer
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> The following extra packages will be installed:
>>   bb-npm-installer
>> The following NEW packages will be installed:
>>   bb-node-red-installer bb-npm-installer
>> 0 upgraded, 2 newly installed, 0 to remove and 74 not upgraded.
>
> Well, bb-node-red-installer/bb-npm-installer is something i packaged
> in the last couple of weeks..  So if you have '74' other updates
> pending..
>
> Yeah, that's not something i've tested for yet..
>
> So let's see what happens with the base image:
>
> bone-debian-8.2-tester-2gb-armhf-2015-11-12-2gb.img.xz

eh it works fine:  (should add nodejs-v0.12.x as a depend of
bb-node-red-installer thou..)

debian@beaglebone:~$ sudo cat /etc/dogtag
BeagleBoard.org Debian Image 2015-11-12
debian@beaglebone:~$ sudo apt-get install bb-node-red-installer
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  bb-npm-installer
The following NEW packages will be installed:
  bb-node-red-installer bb-npm-installer
0 upgraded, 2 newly installed, 0 to remove and 88 not upgraded.
Need to get 6,884 B of archives.
After this operation, 78.8 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://repos.rcn-ee.com/debian/ jessie/main bb-npm-installer all
3.7.5-0rcnee1~bpo80+20160224+1 [2,800 B]
Get:2 http://repos.rcn-ee.com/debian/ jessie/main
bb-node-red-installer all 0.13.2-0rcnee1~bpo80+20160222+1 [4,084 B]
Fetched 6,884 B in 0s (29.6 kB/s)
Selecting previously unselected package bb-npm-installer.
(Reading database ... 33086 files and directories currently installed.)
Preparing to unpack
.../bb-npm-installer_3.7.5-0rcnee1~bpo80+20160224+1_all.deb ...
Unpacking bb-npm-installer (3.7.5-0rcnee1~bpo80+20160224+1) ...
Setting up bb-npm-installer (3.7.5-0rcnee1~bpo80+20160224+1) ...
bb-npm-installer:npm: [1.4.21]
bb-npm-installer:node: [v0.10.38]
bb-npm-installer:Installing: npm-3.7.5 (for bb-npm-installer)
/usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
npm@3.7.5 /usr/local/lib/node_modules/npm
bb-npm-installer:Installed
Selecting previously unselected package bb-node-red-installer.
(Reading database ... 33088 files and directories currently installed.)
Preparing to unpack
.../bb-node-red-installer_0.13.2-0rcnee1~bpo80+20160222+1_all.deb ...
Unpac

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[lajos kamocsay]

I used the info from a post you made in this thread:

https://groups.google.com/forum/m/#!category-topic/beagleboard/software/tdt1TTix7aE

It's your 3rd post from the top, sorry, couldn't figure out how to link to
it.

I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43 kernel.
Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed
myself, am I maybe missing some udev rules?


On Thu, Feb 25, 2016 at 4:57 PM, William Hermans  wrote:

> *As I understand prus are supported with the *bone* kernels. Any ideas why
>> they don't work? Maybe in conflict with something?*
>>
>
> First, which device tree file are you using for the PRU's, and have you
> loaded it ?
>
> On Thu, Feb 25, 2016 at 2:46 PM, lajos  wrote:
>
>> Hello-
>>
>> I have a BBB rev c with the Debian Jessie image on an SD card. I compiled
>> the 4.4.2 bone rt kernel with RFKILL disabled, otherwise default settings
>> built with github.com/RobertCNelson/bb-kernel. (Thanks for the great
>> kernel builder!!!)
>>
>> uname -a
>> Linux beagle 4.4.2-bone-rt-r5 #1 PREEMPT RT Thu Feb 25 11:36:52 EST 2016
>> armv7l GNU/Linux
>>
>> When I boot up the system I have several (8) systemd-udevd processes
>> using up all the cpu, but they are killed after a while with this message
>> in syslog:
>>
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [636]
>> /devices/platform/ocp/4a30.pruss/uio/uio0 timeout; kill it
>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2259
>> '/devices/platform/ocp/4a30.pruss/uio/uio0' killed
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [684]
>> /devices/platform/ocp/4a30.pruss/uio/uio1 timeout; kill it
>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2260
>> '/devices/platform/ocp/4a30.pruss/uio/uio1' killed
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [685]
>> /devices/platform/ocp/4a30.pruss/uio/uio2 timeout; kill it
>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2261
>> '/devices/platform/ocp/4a30.pruss/uio/uio2' killed
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [686]
>> /devices/platform/ocp/4a30.pruss/uio/uio3 timeout; kill it
>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2262
>> '/devices/platform/ocp/4a30.pruss/uio/uio3' killed
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [832]
>> /devices/platform/ocp/4a30.pruss/uio/uio4 timeout; kill it
>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2263
>> '/devices/platform/ocp/4a30.pruss/uio/uio4' killed
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [834]
>> /devices/platform/ocp/4a30.pruss/uio/uio5 timeout; kill it
>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2264
>> '/devices/platform/ocp/4a30.pruss/uio/uio5' killed
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [850]
>> /devices/platform/ocp/4a30.pruss/uio/uio6 timeout; kill it
>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2265
>> '/devices/platform/ocp/4a30.pruss/uio/uio6' killed
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [856]
>> /devices/platform/ocp/4a30.pruss/uio/uio7 timeout; kill it
>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2266
>> '/devices/platform/ocp/4a30.pruss/uio/uio7' killed
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [636] terminated by
>> signal 9 (Killed)
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [684] terminated by
>> signal 9 (Killed)
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [685] terminated by
>> signal 9 (Killed)
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [686] terminated by
>> signal 9 (Killed)
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [832] terminated by
>> signal 9 (Killed)
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [834] terminated by
>> signal 9 (Killed)
>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [850] terminated by
>> signal 9 (Killed)
>>
>> As I understand prus are supported with the *bone* kernels. Any ideas why
>> they don't work? Maybe in conflict with something?
>>
>> I have HDMI Audio/Video and eMMC turned off in uEnv.txt:
>>
>> uname_r=4.4.2-bone-rt-r5
>> dtb=am335x-boneblack-overlay.dtb
>> cmdline=coherent_pool=1M quiet cape_universal=enable
>>
>> And this is my lsmod:
>>
>> Module  Size  Used by
>> c_can_platform  6560  0
>> c_can   9531  1 c_can_platform
>> uio_pruss   4928  0
>> can_dev11689  1 c_can
>> spidev  7481  0
>> tieqep  8758  0
>> pwm_tiecap  3652  0
>> pwm_tiehrpwm4706  0
>> usb_f_acm   7193  1
>> u_serial   10716  3 usb_f_acm
>> usb_f_rndis22093  1
>> g_multi 5441  0
>> usb_f_mass_storage 41731  2 g_multi
>> u_ether11887  2 usb_f_rndis,g_multi
>> libcomposite   43393  4
>> usb_f_acm,usb_f_rndis,g_multi,usb_f_mass_storage
>> ccm 6710  3
>> arc42019  2
>> rtl8192cu  52442  0
>> rtl_usb 

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[William Hermans]

>
> *I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43 kernel.
> Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed
> myself, am I maybe missing some udev rules?*
>

If I were you, I would . . .

$ *apt-cache search linux-image-4 |grep bone-rt*
linux-image-4.0.6-bone-rt-r5 - Linux kernel, version 4.0.6-bone-rt-r5
linux-image-4.0.6-bone-rt-r6 - Linux kernel, version 4.0.6-bone-rt-r6
linux-image-4.0.7-bone-rt-r7 - Linux kernel, version 4.0.7-bone-rt-r7
linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16
linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16
linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16
linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16
linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17
linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17
linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17
linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16

Then pick the last one which would be: linux-image-4.1.9-bone-rt-r16 Here
is the problem. There are a couple kernel config options that must be
enabled / disabled in order for prussdrv to work properly. Passed that it
is entirely possible that 4.4* may break prussdrv *somehow*, and
unintentionally. Because no one who uses prussdrv has tested this kernel
yet.

Later, once you confirm that linux-image-4.1.9-bone-rt-r16 works. You can
always compare configs between the two to double check what you've missed.

On Thu, Feb 25, 2016 at 7:40 PM, lajos kamocsay 
wrote:

> I used the info from a post you made in this thread:
>
>
> https://groups.google.com/forum/m/#!category-topic/beagleboard/software/tdt1TTix7aE
>
> It's your 3rd post from the top, sorry, couldn't figure out how to link to
> it.
>
> I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43 kernel.
> Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed
> myself, am I maybe missing some udev rules?
>
>
> On Thu, Feb 25, 2016 at 4:57 PM, William Hermans 
> wrote:
>
>> *As I understand prus are supported with the *bone* kernels. Any ideas
>>> why they don't work? Maybe in conflict with something?*
>>>
>>
>> First, which device tree file are you using for the PRU's, and have you
>> loaded it ?
>>
>> On Thu, Feb 25, 2016 at 2:46 PM, lajos  wrote:
>>
>>> Hello-
>>>
>>> I have a BBB rev c with the Debian Jessie image on an SD card. I
>>> compiled the 4.4.2 bone rt kernel with RFKILL disabled, otherwise default
>>> settings built with github.com/RobertCNelson/bb-kernel. (Thanks for the
>>> great kernel builder!!!)
>>>
>>> uname -a
>>> Linux beagle 4.4.2-bone-rt-r5 #1 PREEMPT RT Thu Feb 25 11:36:52 EST 2016
>>> armv7l GNU/Linux
>>>
>>> When I boot up the system I have several (8) systemd-udevd processes
>>> using up all the cpu, but they are killed after a while with this message
>>> in syslog:
>>>
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [636]
>>> /devices/platform/ocp/4a30.pruss/uio/uio0 timeout; kill it
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2259
>>> '/devices/platform/ocp/4a30.pruss/uio/uio0' killed
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [684]
>>> /devices/platform/ocp/4a30.pruss/uio/uio1 timeout; kill it
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2260
>>> '/devices/platform/ocp/4a30.pruss/uio/uio1' killed
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [685]
>>> /devices/platform/ocp/4a30.pruss/uio/uio2 timeout; kill it
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2261
>>> '/devices/platform/ocp/4a30.pruss/uio/uio2' killed
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [686]
>>> /devices/platform/ocp/4a30.pruss/uio/uio3 timeout; kill it
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2262
>>> '/devices/platform/ocp/4a30.pruss/uio/uio3' killed
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [832]
>>> /devices/platform/ocp/4a30.pruss/uio/uio4 timeout; kill it
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2263
>>> '/devices/platform/ocp/4a30.pruss/uio/uio4' killed
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [834]
>>> /devices/platform/ocp/4a30.pruss/uio/uio5 timeout; kill it
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2264
>>> '/devices/platform/ocp/4a30.pruss/uio/uio5' killed
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: worker [850]
>>> /devices/platform/ocp/4a30.pruss/uio/uio6 timeout; kill it
>>> Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2265
>>> '/devices/platform

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[lajos kamocsay]

Thanks for the advice, I'll try a 4.1 bone kernel.
On Feb 25, 2016 10:04 PM, "William Hermans"  wrote:

> *I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43 kernel.
>> Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed
>> myself, am I maybe missing some udev rules?*
>>
>
> If I were you, I would . . .
>
> $ *apt-cache search linux-image-4 |grep bone-rt*
> linux-image-4.0.6-bone-rt-r5 - Linux kernel, version 4.0.6-bone-rt-r5
> linux-image-4.0.6-bone-rt-r6 - Linux kernel, version 4.0.6-bone-rt-r6
> linux-image-4.0.7-bone-rt-r7 - Linux kernel, version 4.0.7-bone-rt-r7
> linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
> linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16
> linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16
> linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16
> linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16
> linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17
> linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17
> linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17
> linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
> linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
> linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
> linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
> linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
>
> Then pick the last one which would be: linux-image-4.1.9-bone-rt-r16 Here
> is the problem. There are a couple kernel config options that must be
> enabled / disabled in order for prussdrv to work properly. Passed that it
> is entirely possible that 4.4* may break prussdrv *somehow*, and
> unintentionally. Because no one who uses prussdrv has tested this kernel
> yet.
>
> Later, once you confirm that linux-image-4.1.9-bone-rt-r16 works. You can
> always compare configs between the two to double check what you've missed.
>
> On Thu, Feb 25, 2016 at 7:40 PM, lajos kamocsay 
> wrote:
>
>> I used the info from a post you made in this thread:
>>
>>
>> https://groups.google.com/forum/m/#!category-topic/beagleboard/software/tdt1TTix7aE
>>
>> It's your 3rd post from the top, sorry, couldn't figure out how to link
>> to it.
>>
>> I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43 kernel.
>> Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed
>> myself, am I maybe missing some udev rules?
>>
>>
>> On Thu, Feb 25, 2016 at 4:57 PM, William Hermans 
>> wrote:
>>
>>> *As I understand prus are supported with the *bone* kernels. Any ideas
 why they don't work? Maybe in conflict with something?*

>>>
>>> First, which device tree file are you using for the PRU's, and have you
>>> loaded it ?
>>>
>>> On Thu, Feb 25, 2016 at 2:46 PM, lajos  wrote:
>>>
 Hello-

 I have a BBB rev c with the Debian Jessie image on an SD card. I
 compiled the 4.4.2 bone rt kernel with RFKILL disabled, otherwise default
 settings built with github.com/RobertCNelson/bb-kernel. (Thanks for
 the great kernel builder!!!)

 uname -a
 Linux beagle 4.4.2-bone-rt-r5 #1 PREEMPT RT Thu Feb 25 11:36:52 EST
 2016 armv7l GNU/Linux

 When I boot up the system I have several (8) systemd-udevd processes
 using up all the cpu, but they are killed after a while with this message
 in syslog:

 Feb 25 19:46:54 beagle systemd-udevd[212]: worker [636]
 /devices/platform/ocp/4a30.pruss/uio/uio0 timeout; kill it
 Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2259
 '/devices/platform/ocp/4a30.pruss/uio/uio0' killed
 Feb 25 19:46:54 beagle systemd-udevd[212]: worker [684]
 /devices/platform/ocp/4a30.pruss/uio/uio1 timeout; kill it
 Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2260
 '/devices/platform/ocp/4a30.pruss/uio/uio1' killed
 Feb 25 19:46:54 beagle systemd-udevd[212]: worker [685]
 /devices/platform/ocp/4a30.pruss/uio/uio2 timeout; kill it
 Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2261
 '/devices/platform/ocp/4a30.pruss/uio/uio2' killed
 Feb 25 19:46:54 beagle systemd-udevd[212]: worker [686]
 /devices/platform/ocp/4a30.pruss/uio/uio3 timeout; kill it
 Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2262
 '/devices/platform/ocp/4a30.pruss/uio/uio3' killed
 Feb 25 19:46:54 beagle systemd-udevd[212]: worker [832]
 /devices/platform/ocp/4a30.pruss/uio/uio4 timeout; kill it
 Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2263
 '/devices/platform/ocp/4a30.pruss/uio/uio4' killed
 Feb 25 19:46:54 beagle systemd-udevd[212]: worker [834]
 /devices/platform/ocp/4a30.pruss/uio/uio5 timeout; kill it
 Feb 25 19:46:54 beagle systemd-udevd[212]: seq 2264
 '/devices/platform/ocp/4a3000

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[William Hermans]

Heh, perfect example of why one need to update the APT cache .  . .

william@beaglebone:~$ *sudo apt-get update*
william@beaglebone:~$ *apt-cache search linux-image-4 |grep bone-rt*
linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16
linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16
linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16
linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16
linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17
linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17
linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17
linux-image-4.1.15-bone-rt-r18 - Linux kernel, version 4.1.15-bone-rt-r18
linux-image-4.1.16-bone-rt-r18 - Linux kernel, version 4.1.16-bone-rt-r18
linux-image-4.1.17-bone-rt-r18 - Linux kernel, version 4.1.17-bone-rt-r18
linux-image-4.1.17-bone-rt-r19 - Linux kernel, version 4.1.17-bone-rt-r19
linux-image-4.1.18-bone-rt-r19 - Linux kernel, version 4.1.18-bone-rt-r19
linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
linux-image-4.4.0-bone-rt-r1 - Linux kernel, version 4.4.0-bone-rt-r1
linux-image-4.4.0-bone-rt-r2 - Linux kernel, version 4.4.0-bone-rt-r2
linux-image-4.4.0-bone-rt-r3 - Linux kernel, version 4.4.0-bone-rt-r3
linux-image-4.4.0-rc8-bone-rt-r1 - Linux kernel, version
4.4.0-rc8-bone-rt-r1
linux-image-4.4.1-bone-rt-r4 - Linux kernel, version 4.4.1-bone-rt-r4
linux-image-4.4.1-bone-rt-r5 - Linux kernel, version 4.4.1-bone-rt-r5
*linux-image-4.4.2-bone-rt-r5 - Linux kernel, version 4.4.2-bone-rt-r5*


On Thu, Feb 25, 2016 at 8:04 PM, William Hermans  wrote:

> *I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43 kernel.
>> Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed
>> myself, am I maybe missing some udev rules?*
>>
>
> If I were you, I would . . .
>
> $ *apt-cache search linux-image-4 |grep bone-rt*
> linux-image-4.0.6-bone-rt-r5 - Linux kernel, version 4.0.6-bone-rt-r5
> linux-image-4.0.6-bone-rt-r6 - Linux kernel, version 4.0.6-bone-rt-r6
> linux-image-4.0.7-bone-rt-r7 - Linux kernel, version 4.0.7-bone-rt-r7
> linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
> linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16
> linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16
> linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16
> linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16
> linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17
> linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17
> linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17
> linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
> linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
> linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
> linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
> linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
>
> Then pick the last one which would be: linux-image-4.1.9-bone-rt-r16 Here
> is the problem. There are a couple kernel config options that must be
> enabled / disabled in order for prussdrv to work properly. Passed that it
> is entirely possible that 4.4* may break prussdrv *somehow*, and
> unintentionally. Because no one who uses prussdrv has tested this kernel
> yet.
>
> Later, once you confirm that linux-image-4.1.9-bone-rt-r16 works. You can
> always compare configs between the two to double check what you've missed.
>
> On Thu, Feb 25, 2016 at 7:40 PM, lajos kamocsay 
> wrote:
>
>> I used the info from a post you made in this thread:
>>
>>
>> https://groups.google.com/forum/m/#!category-topic/beagleboard/software/tdt1TTix7aE
>>
>> It's your 3rd post from the top, sorry, couldn't figure out how to link
>> to it.
>>
>> I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43 kernel.
>> Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed
>> myself, am I maybe missing some udev rules?
>>
>>
>> On Thu, Feb 25, 2016 at 4:57 PM, William Hermans 
>> wrote:
>>
>>> *As I understand prus are supported with the *bone* kernels. Any ideas
 why they don't work? Maybe in conflict with something?*

>>>
>>> First, which device tree file are you using for the PRU's, and have you
>>> loaded it ?
>>>
>>> On Thu, Feb 25, 2016 at 2:46 PM, lajos  wrote:
>>>
 Hello-

 I have a BBB rev c with the Debian Jessie i

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[Robert Nelson]

and i'm not sure anyone has actually tested the uio_pruss on v4.4.x..

It's the same patches forward ported from v4.1.x -> v4.2.x -> v4.3.x.. ;)

But, i wonder if it works on v4.4.x. ;)

On Thu, Feb 25, 2016 at 9:10 PM, William Hermans  wrote:
> Heh, perfect example of why one need to update the APT cache .  . .
>
> william@beaglebone:~$ sudo apt-get update
> william@beaglebone:~$ apt-cache search linux-image-4 |grep bone-rt
> linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
> linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16
> linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16
> linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16
> linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16
> linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17
> linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17
> linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17
> linux-image-4.1.15-bone-rt-r18 - Linux kernel, version 4.1.15-bone-rt-r18
> linux-image-4.1.16-bone-rt-r18 - Linux kernel, version 4.1.16-bone-rt-r18
> linux-image-4.1.17-bone-rt-r18 - Linux kernel, version 4.1.17-bone-rt-r18
> linux-image-4.1.17-bone-rt-r19 - Linux kernel, version 4.1.17-bone-rt-r19
> linux-image-4.1.18-bone-rt-r19 - Linux kernel, version 4.1.18-bone-rt-r19
> linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
> linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
> linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
> linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
> linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
> linux-image-4.4.0-bone-rt-r1 - Linux kernel, version 4.4.0-bone-rt-r1
> linux-image-4.4.0-bone-rt-r2 - Linux kernel, version 4.4.0-bone-rt-r2
> linux-image-4.4.0-bone-rt-r3 - Linux kernel, version 4.4.0-bone-rt-r3
> linux-image-4.4.0-rc8-bone-rt-r1 - Linux kernel, version
> 4.4.0-rc8-bone-rt-r1
> linux-image-4.4.1-bone-rt-r4 - Linux kernel, version 4.4.1-bone-rt-r4
> linux-image-4.4.1-bone-rt-r5 - Linux kernel, version 4.4.1-bone-rt-r5
> linux-image-4.4.2-bone-rt-r5 - Linux kernel, version 4.4.2-bone-rt-r5
>
>
> On Thu, Feb 25, 2016 at 8:04 PM, William Hermans  wrote:
>>>
>>> I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43 kernel.
>>> Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed myself,
>>> am I maybe missing some udev rules?
>>
>>
>> If I were you, I would . . .
>>
>> $ apt-cache search linux-image-4 |grep bone-rt
>> linux-image-4.0.6-bone-rt-r5 - Linux kernel, version 4.0.6-bone-rt-r5
>> linux-image-4.0.6-bone-rt-r6 - Linux kernel, version 4.0.6-bone-rt-r6
>> linux-image-4.0.7-bone-rt-r7 - Linux kernel, version 4.0.7-bone-rt-r7
>> linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
>> linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16
>> linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16
>> linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16
>> linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16
>> linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17
>> linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17
>> linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17
>> linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
>> linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
>> linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
>> linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
>> linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
>>
>> Then pick the last one which would be: linux-image-4.1.9-bone-rt-r16 Here
>> is the problem. There are a couple kernel config options that must be
>> enabled / disabled in order for prussdrv to work properly. Passed that it is
>> entirely possible that 4.4* may break prussdrv *somehow*, and
>> unintentionally. Because no one who uses prussdrv has tested this kernel
>> yet.
>>
>> Later, once you confirm that linux-image-4.1.9-bone-rt-r16 works. You can
>> always compare configs between the two to double check what you've missed.
>>
>> On Thu, Feb 25, 2016 at 7:40 PM, lajos kamocsay 
>> wrote:
>>>
>>> I used the info from a post you made in this thread:
>>>
>>>
>>> https://groups.google.com/forum/m/#!category-topic/beagleboard/software/tdt1TTix7aE
>>>
>>> It's your 3rd post from the top, sorry, couldn't figure out how to link
>>> to it.
>>>
>>> I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43 kernel.
>>> Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed myself,
>>> am I maybe missing some udev rules?
>>>
>>>
>>> On Thu, Feb 25, 2016 at 4:57 PM, William Hermans 
>>> wrote:
>

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[William Hermans]

>
> *and i'm not sure anyone has actually tested the uio_pruss on v4.4.x..*
>
> * It's the same patches forward ported from v4.1.x -> v4.2.x -> v4.3.x..
> ;)*
>
> * But, i wonder if it works on v4.4.x. ;)*


I'm testing now. The kernel modules are not automatically loaded when
enabling the pru's through a device tree. So something has changed, and I'm
not sure what it is. however . . .

william@beaglebone:~$ sudo modprobe uio_pruss
william@beaglebone:~$ lsmod
Module  Size  Used by
uio_pruss   4436  0
uio 8247  1 uio_pruss
rfcomm 53016  0
bluetooth 406428  9 rfcomm
nfsd  223727  2


This does not seem right. Which may be my own fault, but let me double
check.

On Thu, Feb 25, 2016 at 8:17 PM, Robert Nelson 
wrote:

> and i'm not sure anyone has actually tested the uio_pruss on v4.4.x..
>
> It's the same patches forward ported from v4.1.x -> v4.2.x -> v4.3.x.. ;)
>
> But, i wonder if it works on v4.4.x. ;)
>
> On Thu, Feb 25, 2016 at 9:10 PM, William Hermans 
> wrote:
> > Heh, perfect example of why one need to update the APT cache .  . .
> >
> > william@beaglebone:~$ sudo apt-get update
> > william@beaglebone:~$ apt-cache search linux-image-4 |grep bone-rt
> > linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
> > linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16
> > linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16
> > linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16
> > linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16
> > linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17
> > linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17
> > linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17
> > linux-image-4.1.15-bone-rt-r18 - Linux kernel, version 4.1.15-bone-rt-r18
> > linux-image-4.1.16-bone-rt-r18 - Linux kernel, version 4.1.16-bone-rt-r18
> > linux-image-4.1.17-bone-rt-r18 - Linux kernel, version 4.1.17-bone-rt-r18
> > linux-image-4.1.17-bone-rt-r19 - Linux kernel, version 4.1.17-bone-rt-r19
> > linux-image-4.1.18-bone-rt-r19 - Linux kernel, version 4.1.18-bone-rt-r19
> > linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
> > linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
> > linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
> > linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
> > linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
> > linux-image-4.4.0-bone-rt-r1 - Linux kernel, version 4.4.0-bone-rt-r1
> > linux-image-4.4.0-bone-rt-r2 - Linux kernel, version 4.4.0-bone-rt-r2
> > linux-image-4.4.0-bone-rt-r3 - Linux kernel, version 4.4.0-bone-rt-r3
> > linux-image-4.4.0-rc8-bone-rt-r1 - Linux kernel, version
> > 4.4.0-rc8-bone-rt-r1
> > linux-image-4.4.1-bone-rt-r4 - Linux kernel, version 4.4.1-bone-rt-r4
> > linux-image-4.4.1-bone-rt-r5 - Linux kernel, version 4.4.1-bone-rt-r5
> > linux-image-4.4.2-bone-rt-r5 - Linux kernel, version 4.4.2-bone-rt-r5
> >
> >
> > On Thu, Feb 25, 2016 at 8:04 PM, William Hermans 
> wrote:
> >>>
> >>> I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43
> kernel.
> >>> Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed
> myself,
> >>> am I maybe missing some udev rules?
> >>
> >>
> >> If I were you, I would . . .
> >>
> >> $ apt-cache search linux-image-4 |grep bone-rt
> >> linux-image-4.0.6-bone-rt-r5 - Linux kernel, version 4.0.6-bone-rt-r5
> >> linux-image-4.0.6-bone-rt-r6 - Linux kernel, version 4.0.6-bone-rt-r6
> >> linux-image-4.0.7-bone-rt-r7 - Linux kernel, version 4.0.7-bone-rt-r7
> >> linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
> >> linux-image-4.1.10-bone-rt-r16 - Linux kernel, version
> 4.1.10-bone-rt-r16
> >> linux-image-4.1.11-bone-rt-r16 - Linux kernel, version
> 4.1.11-bone-rt-r16
> >> linux-image-4.1.12-bone-rt-r16 - Linux kernel, version
> 4.1.12-bone-rt-r16
> >> linux-image-4.1.13-bone-rt-r16 - Linux kernel, version
> 4.1.13-bone-rt-r16
> >> linux-image-4.1.13-bone-rt-r17 - Linux kernel, version
> 4.1.13-bone-rt-r17
> >> linux-image-4.1.14-bone-rt-r17 - Linux kernel, version
> 4.1.14-bone-rt-r17
> >> linux-image-4.1.15-bone-rt-r17 - Linux kernel, version
> 4.1.15-bone-rt-r17
> >> linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
> >> linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
> >> linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
> >> linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
> >> linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
> >>
> >> Then pick the last one which would be: linux-image-4.1.9-bone-rt-r16
> Here
> >> is the problem. There are a couple kernel config options that must be
> >> enabled 

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[William Hermans]

@Robert, Yeah I do not know what's going on. Perhaps you know ? Fresh
reboot with all blocked modules, unblocked.

william@beaglebone:~$ *sudo sh -c "echo 'pru_enable' >
/sys/devices/platform/bone_capemgr/slots"*
william@beaglebone:~$ *dmesg | grep pru*
[   38.594211] bone_capemgr bone_capemgr: part_number 'pru_enable', version
'N/A'
[   38.614582] bone_capemgr bone_capemgr: slot #4: 'Override Board
Name,00A0,Override Manuf,pru_enable'
[   38.627556] bone_capemgr bone_capemgr: slot #4: dtbo
'pru_enable-00A0.dtbo' loaded; overlay id #0
william@beaglebone:~$ *lsmod |grep pru*
william@beaglebone:~$ *dmesg | tail*
[   20.286438] Bluetooth: RFCOMM TTY layer initialized
[   20.286463] Bluetooth: RFCOMM socket layer initialized
[   20.286501] Bluetooth: RFCOMM ver 1.11
[   20.330738] Bluetooth: BNEP socket layer initialized
[   38.594211] bone_capemgr bone_capemgr: part_number 'pru_enable', version
'N/A'
[   38.601622] bone_capemgr bone_capemgr: slot #4: override
[   38.607563] bone_capemgr bone_capemgr: Using override eeprom data at
slot 4
[   38.614582] bone_capemgr bone_capemgr: slot #4: 'Override Board
Name,00A0,Override Manuf,pru_enable'
[   38.627556] bone_capemgr bone_capemgr: slot #4: dtbo
'pru_enable-00A0.dtbo' loaded; overlay id #0
[   62.258491] random: nonblocking pool is initialized
william@beaglebone:~$ *lsmod*
Module  Size  Used by
bnep   12921  2
rfcomm 53016  0
bluetooth 406428  10 bnep,rfcomm
nfsd  223727  2


On Thu, Feb 25, 2016 at 8:31 PM, William Hermans  wrote:

> *and i'm not sure anyone has actually tested the uio_pruss on v4.4.x..*
>>
>> * It's the same patches forward ported from v4.1.x -> v4.2.x -> v4.3.x..
>> ;)*
>>
>> * But, i wonder if it works on v4.4.x. ;)*
>
>
> I'm testing now. The kernel modules are not automatically loaded when
> enabling the pru's through a device tree. So something has changed, and I'm
> not sure what it is. however . . .
>
> william@beaglebone:~$ sudo modprobe uio_pruss
> william@beaglebone:~$ lsmod
> Module  Size  Used by
> uio_pruss   4436  0
> uio 8247  1 uio_pruss
> rfcomm 53016  0
> bluetooth 406428  9 rfcomm
> nfsd  223727  2
>
>
> This does not seem right. Which may be my own fault, but let me double
> check.
>
> On Thu, Feb 25, 2016 at 8:17 PM, Robert Nelson 
> wrote:
>
>> and i'm not sure anyone has actually tested the uio_pruss on v4.4.x..
>>
>> It's the same patches forward ported from v4.1.x -> v4.2.x -> v4.3.x.. ;)
>>
>> But, i wonder if it works on v4.4.x. ;)
>>
>> On Thu, Feb 25, 2016 at 9:10 PM, William Hermans 
>> wrote:
>> > Heh, perfect example of why one need to update the APT cache .  . .
>> >
>> > william@beaglebone:~$ sudo apt-get update
>> > william@beaglebone:~$ apt-cache search linux-image-4 |grep bone-rt
>> > linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
>> > linux-image-4.1.10-bone-rt-r16 - Linux kernel, version
>> 4.1.10-bone-rt-r16
>> > linux-image-4.1.11-bone-rt-r16 - Linux kernel, version
>> 4.1.11-bone-rt-r16
>> > linux-image-4.1.12-bone-rt-r16 - Linux kernel, version
>> 4.1.12-bone-rt-r16
>> > linux-image-4.1.13-bone-rt-r16 - Linux kernel, version
>> 4.1.13-bone-rt-r16
>> > linux-image-4.1.13-bone-rt-r17 - Linux kernel, version
>> 4.1.13-bone-rt-r17
>> > linux-image-4.1.14-bone-rt-r17 - Linux kernel, version
>> 4.1.14-bone-rt-r17
>> > linux-image-4.1.15-bone-rt-r17 - Linux kernel, version
>> 4.1.15-bone-rt-r17
>> > linux-image-4.1.15-bone-rt-r18 - Linux kernel, version
>> 4.1.15-bone-rt-r18
>> > linux-image-4.1.16-bone-rt-r18 - Linux kernel, version
>> 4.1.16-bone-rt-r18
>> > linux-image-4.1.17-bone-rt-r18 - Linux kernel, version
>> 4.1.17-bone-rt-r18
>> > linux-image-4.1.17-bone-rt-r19 - Linux kernel, version
>> 4.1.17-bone-rt-r19
>> > linux-image-4.1.18-bone-rt-r19 - Linux kernel, version
>> 4.1.18-bone-rt-r19
>> > linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
>> > linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
>> > linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
>> > linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
>> > linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
>> > linux-image-4.4.0-bone-rt-r1 - Linux kernel, version 4.4.0-bone-rt-r1
>> > linux-image-4.4.0-bone-rt-r2 - Linux kernel, version 4.4.0-bone-rt-r2
>> > linux-image-4.4.0-bone-rt-r3 - Linux kernel, version 4.4.0-bone-rt-r3
>> > linux-image-4.4.0-rc8-bone-rt-r1 - Linux kernel, version
>> > 4.4.0-rc8-bone-rt-r1
>> > linux-image-4.4.1-bone-rt-r4 - Linux kernel, version 4.4.1-bone-rt-r4
>> > linux-image-4.4.1-bone-rt-r5 - Linux kernel, version 4.4.1-bone-rt-r5
>> > linux-image-4.4.2-bone-rt-r5 - Linux kernel, version 4.4.2-bone-rt-r5
>> >
>> >
>> > On Thu, Feb 25, 2016 at 8:04 PM, William Hermans 
>> wrote:
>> >>>
>> >>> I started from the Jessie BBB i

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[William Hermans]

BY the way . . . my workflow . . .

william@beaglebone:~$ uname -r
4.1.12-bone-rt-r16
william@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2015-03-01
( Wheezy 7.8 )

william@beaglebone:~$ sudo apt-get update
william@beaglebone:~$ apt-cache search linux-image-4 |grep bone-rt
linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16
linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16
linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16
linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16
linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17
linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17
linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17
linux-image-4.1.15-bone-rt-r18 - Linux kernel, version 4.1.15-bone-rt-r18
linux-image-4.1.16-bone-rt-r18 - Linux kernel, version 4.1.16-bone-rt-r18
linux-image-4.1.17-bone-rt-r18 - Linux kernel, version 4.1.17-bone-rt-r18
linux-image-4.1.17-bone-rt-r19 - Linux kernel, version 4.1.17-bone-rt-r19
linux-image-4.1.18-bone-rt-r19 - Linux kernel, version 4.1.18-bone-rt-r19
linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
linux-image-4.4.0-bone-rt-r1 - Linux kernel, version 4.4.0-bone-rt-r1
linux-image-4.4.0-bone-rt-r2 - Linux kernel, version 4.4.0-bone-rt-r2
linux-image-4.4.0-bone-rt-r3 - Linux kernel, version 4.4.0-bone-rt-r3
linux-image-4.4.0-rc8-bone-rt-r1 - Linux kernel, version
4.4.0-rc8-bone-rt-r1
linux-image-4.4.1-bone-rt-r4 - Linux kernel, version 4.4.1-bone-rt-r4
linux-image-4.4.1-bone-rt-r5 - Linux kernel, version 4.4.1-bone-rt-r5
linux-image-4.4.2-bone-rt-r5 - Linux kernel, version 4.4.2-bone-rt-r5

william@beaglebone:~$ sudo apt-get install linux-image-4.4.2-bone-rt-r5
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  linux-firmware-image-4.4.2-bone-rt-r5
The following NEW packages will be installed:
  linux-image-4.4.2-bone-rt-r5
0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded.
Need to get 27.6 MB of archives.
After this operation, 70.4 MB of additional disk space will be used.

. . .

Unpacking linux-image-4.4.2-bone-rt-r5 (from
.../linux-image-4.4.2-bone-rt-r5_1wheezy_armhf.deb) ...
Setting up linux-image-4.4.2-bone-rt-r5 (1wheezy) ...
update-initramfs: Generating /boot/initrd.img-4.4.2-bone-rt-r5
zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.4.2-bone-rt-r5]

william@beaglebone:~$ sudo reboot

Broadcast message from root@beaglebone (pts/0) (Thu Feb 25 20:20:41 2016):
The system is going down for reboot NOW!
william@beaglebone:~$ Connection to 192.168.xxx.xxx closed by remote host.
Connection to 192.168.xxx.xxx closed.

william@eee-pc:~$ ssh will...@192.168.xxx.xxx
Debian GNU/Linux 7

BeagleBoard.org Debian Image 2015-03-01

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

will...@192.168.xxx.xxx's password:
Last login: Mon Feb 22 12:59:23 2016 from 192.168.xxx.xxx

william@beaglebone:~$ uname -r
4.4.2-bone-rt-r5

On Thu, Feb 25, 2016 at 8:39 PM, William Hermans  wrote:

> @Robert, Yeah I do not know what's going on. Perhaps you know ? Fresh
> reboot with all blocked modules, unblocked.
>
> william@beaglebone:~$ *sudo sh -c "echo 'pru_enable' >
> /sys/devices/platform/bone_capemgr/slots"*
> william@beaglebone:~$ *dmesg | grep pru*
> [   38.594211] bone_capemgr bone_capemgr: part_number 'pru_enable',
> version 'N/A'
> [   38.614582] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A0,Override Manuf,pru_enable'
> [   38.627556] bone_capemgr bone_capemgr: slot #4: dtbo
> 'pru_enable-00A0.dtbo' loaded; overlay id #0
> william@beaglebone:~$ *lsmod |grep pru*
> william@beaglebone:~$ *dmesg | tail*
> [   20.286438] Bluetooth: RFCOMM TTY layer initialized
> [   20.286463] Bluetooth: RFCOMM socket layer initialized
> [   20.286501] Bluetooth: RFCOMM ver 1.11
> [   20.330738] Bluetooth: BNEP socket layer initialized
> [   38.594211] bone_capemgr bone_capemgr: part_number 'pru_enable',
> version 'N/A'
> [   38.601622] bone_capemgr bone_capemgr: slot #4: override
> [   38.607563] bone_capemgr bone_capemgr: Using override eeprom data at
> slot 4
> [   38.614582] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A0,Override Manuf,pru_enable'
> [   38.627556] bone_capemgr bone_capemgr: slot #4: dtbo
> 'pru_enable-00A0.dtbo' loaded; overlay id #0
> [   62.258491] random: nonblocking pool is initialized
> william@beaglebone:~$ *lsmod*
> Module  Size  Used by
> bnep   

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[Robert Nelson]

On Thu, Feb 25, 2016 at 9:42 PM, William Hermans  wrote:

> BY the way . . . my workflow . . .
>
> william@beaglebone:~$ uname -r
> 4.1.12-bone-rt-r16
> william@beaglebone:~$ cat /etc/dogtag
> BeagleBoard.org Debian Image 2015-03-01
> ( Wheezy 7.8 )
>
>
> william@beaglebone:~$ sudo apt-get update
> william@beaglebone:~$ apt-cache search linux-image-4 |grep bone-rt
> linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
> linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16
> linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16
> linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16
> linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16
> linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17
> linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17
> linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17
> linux-image-4.1.15-bone-rt-r18 - Linux kernel, version 4.1.15-bone-rt-r18
> linux-image-4.1.16-bone-rt-r18 - Linux kernel, version 4.1.16-bone-rt-r18
> linux-image-4.1.17-bone-rt-r18 - Linux kernel, version 4.1.17-bone-rt-r18
> linux-image-4.1.17-bone-rt-r19 - Linux kernel, version 4.1.17-bone-rt-r19
> linux-image-4.1.18-bone-rt-r19 - Linux kernel, version 4.1.18-bone-rt-r19
> linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
> linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
> linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
> linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
> linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
> linux-image-4.4.0-bone-rt-r1 - Linux kernel, version 4.4.0-bone-rt-r1
> linux-image-4.4.0-bone-rt-r2 - Linux kernel, version 4.4.0-bone-rt-r2
> linux-image-4.4.0-bone-rt-r3 - Linux kernel, version 4.4.0-bone-rt-r3
> linux-image-4.4.0-rc8-bone-rt-r1 - Linux kernel, version
> 4.4.0-rc8-bone-rt-r1
> linux-image-4.4.1-bone-rt-r4 - Linux kernel, version 4.4.1-bone-rt-r4
> linux-image-4.4.1-bone-rt-r5 - Linux kernel, version 4.4.1-bone-rt-r5
> linux-image-4.4.2-bone-rt-r5 - Linux kernel, version 4.4.2-bone-rt-r5
>
> william@beaglebone:~$ sudo apt-get install linux-image-4.4.2-bone-rt-r5
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Suggested packages:
>   linux-firmware-image-4.4.2-bone-rt-r5
> The following NEW packages will be installed:
>   linux-image-4.4.2-bone-rt-r5
> 0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded.
> Need to get 27.6 MB of archives.
> After this operation, 70.4 MB of additional disk space will be used.
>
> . . .
>
> Unpacking linux-image-4.4.2-bone-rt-r5 (from
> .../linux-image-4.4.2-bone-rt-r5_1wheezy_armhf.deb) ...
> Setting up linux-image-4.4.2-bone-rt-r5 (1wheezy) ...
> update-initramfs: Generating /boot/initrd.img-4.4.2-bone-rt-r5
> zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.4.2-bone-rt-r5]
>
> william@beaglebone:~$ sudo reboot
>
> Broadcast message from root@beaglebone (pts/0) (Thu Feb 25 20:20:41 2016):
> The system is going down for reboot NOW!
> william@beaglebone:~$ Connection to 192.168.xxx.xxx closed by remote host.
> Connection to 192.168.xxx.xxx closed.
>
> william@eee-pc:~$ ssh will...@192.168.xxx.xxx
> Debian GNU/Linux 7
>
> BeagleBoard.org Debian Image 2015-03-01
>
> Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
>
> default username:password is [debian:temppwd]
>
> will...@192.168.xxx.xxx's password:
> Last login: Mon Feb 22 12:59:23 2016 from 192.168.xxx.xxx
>
> william@beaglebone:~$ uname -r
> 4.4.2-bone-rt-r5
>


Yeap, that looks right...  Yuck, something broke..

Does it work with either of these? (last 4.3.x & last 4.2.x)

linux-image-4.3.6-bone5
linux-image-4.2.5-bone2

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] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[William Hermans]

GIve me a few, I'll test both.

On Thu, Feb 25, 2016 at 8:48 PM, Robert Nelson 
wrote:

>
>
> On Thu, Feb 25, 2016 at 9:42 PM, William Hermans 
> wrote:
>
>> BY the way . . . my workflow . . .
>>
>> william@beaglebone:~$ uname -r
>> 4.1.12-bone-rt-r16
>> william@beaglebone:~$ cat /etc/dogtag
>> BeagleBoard.org Debian Image 2015-03-01
>> ( Wheezy 7.8 )
>>
>>
>> william@beaglebone:~$ sudo apt-get update
>> william@beaglebone:~$ apt-cache search linux-image-4 |grep bone-rt
>> linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
>> linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16
>> linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16
>> linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16
>> linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16
>> linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17
>> linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17
>> linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17
>> linux-image-4.1.15-bone-rt-r18 - Linux kernel, version 4.1.15-bone-rt-r18
>> linux-image-4.1.16-bone-rt-r18 - Linux kernel, version 4.1.16-bone-rt-r18
>> linux-image-4.1.17-bone-rt-r18 - Linux kernel, version 4.1.17-bone-rt-r18
>> linux-image-4.1.17-bone-rt-r19 - Linux kernel, version 4.1.17-bone-rt-r19
>> linux-image-4.1.18-bone-rt-r19 - Linux kernel, version 4.1.18-bone-rt-r19
>> linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
>> linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
>> linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
>> linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
>> linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
>> linux-image-4.4.0-bone-rt-r1 - Linux kernel, version 4.4.0-bone-rt-r1
>> linux-image-4.4.0-bone-rt-r2 - Linux kernel, version 4.4.0-bone-rt-r2
>> linux-image-4.4.0-bone-rt-r3 - Linux kernel, version 4.4.0-bone-rt-r3
>> linux-image-4.4.0-rc8-bone-rt-r1 - Linux kernel, version
>> 4.4.0-rc8-bone-rt-r1
>> linux-image-4.4.1-bone-rt-r4 - Linux kernel, version 4.4.1-bone-rt-r4
>> linux-image-4.4.1-bone-rt-r5 - Linux kernel, version 4.4.1-bone-rt-r5
>> linux-image-4.4.2-bone-rt-r5 - Linux kernel, version 4.4.2-bone-rt-r5
>>
>> william@beaglebone:~$ sudo apt-get install linux-image-4.4.2-bone-rt-r5
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Suggested packages:
>>   linux-firmware-image-4.4.2-bone-rt-r5
>> The following NEW packages will be installed:
>>   linux-image-4.4.2-bone-rt-r5
>> 0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded.
>> Need to get 27.6 MB of archives.
>> After this operation, 70.4 MB of additional disk space will be used.
>>
>> . . .
>>
>> Unpacking linux-image-4.4.2-bone-rt-r5 (from
>> .../linux-image-4.4.2-bone-rt-r5_1wheezy_armhf.deb) ...
>> Setting up linux-image-4.4.2-bone-rt-r5 (1wheezy) ...
>> update-initramfs: Generating /boot/initrd.img-4.4.2-bone-rt-r5
>> zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.4.2-bone-rt-r5]
>>
>> william@beaglebone:~$ sudo reboot
>>
>> Broadcast message from root@beaglebone (pts/0) (Thu Feb 25 20:20:41
>> 2016):
>> The system is going down for reboot NOW!
>> william@beaglebone:~$ Connection to 192.168.xxx.xxx closed by remote
>> host.
>> Connection to 192.168.xxx.xxx closed.
>>
>> william@eee-pc:~$ ssh will...@192.168.xxx.xxx
>> Debian GNU/Linux 7
>>
>> BeagleBoard.org Debian Image 2015-03-01
>>
>> Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
>>
>> default username:password is [debian:temppwd]
>>
>> will...@192.168.xxx.xxx's password:
>> Last login: Mon Feb 22 12:59:23 2016 from 192.168.xxx.xxx
>>
>> william@beaglebone:~$ uname -r
>> 4.4.2-bone-rt-r5
>>
>
>
> Yeap, that looks right...  Yuck, something broke..
>
> Does it work with either of these? (last 4.3.x & last 4.2.x)
>
> linux-image-4.3.6-bone5
> linux-image-4.2.5-bone2
>
> 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.
>

-- 
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] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[William Hermans]

linux-image-4.2.5-bone2 -> Functional

william@beaglebone:~$ sudo apt-get install linux-image-4.2.5-bone2
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  linux-firmware-image-4.2.5-bone2
The following NEW packages will be installed:
  linux-image-4.2.5-bone2
0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded.
Need to get 26.2 MB of archives.
After this operation, 65.5 MB of additional disk space will be used.
. . .
Unpacking linux-image-4.2.5-bone2 (from
.../linux-image-4.2.5-bone2_1wheezy_armhf.deb) ...
Setting up linux-image-4.2.5-bone2 (1wheezy) ...
update-initramfs: Generating /boot/initrd.img-4.2.5-bone2
zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.2.5-bone2]

william@beaglebone:~$ sudo reboot

william@beaglebone:~$ uname -r
4.2.5-bone2
william@beaglebone:~$ sudo sh -c "echo 'pru_enable' >
/sys/devices/platform/bone_capemgr/slots"
william@beaglebone:~$ dmesg | grep pru
[   56.250528] bone_capemgr bone_capemgr: part_number 'pru_enable', version
'N/A'
[   56.270616] bone_capemgr bone_capemgr: slot #4: 'Override Board
Name,00A0,Override Manuf,pru_enable'
[   56.293224] bone_capemgr bone_capemgr: slot #4: dtbo
'pru_enable-00A0.dtbo' loaded; overlay id #1
[   56.304965] pruss_uio 4a30.pruss: pins are not configured from the
driver
william@beaglebone:~$ lsmod |grep pru
uio_pruss   4244  0
uio 8146  2 uio_pruss,uio_pdrv_genirq

On Thu, Feb 25, 2016 at 9:02 PM, William Hermans  wrote:

> GIve me a few, I'll test both.
>
> On Thu, Feb 25, 2016 at 8:48 PM, Robert Nelson 
> wrote:
>
>>
>>
>> On Thu, Feb 25, 2016 at 9:42 PM, William Hermans 
>> wrote:
>>
>>> BY the way . . . my workflow . . .
>>>
>>> william@beaglebone:~$ uname -r
>>> 4.1.12-bone-rt-r16
>>> william@beaglebone:~$ cat /etc/dogtag
>>> BeagleBoard.org Debian Image 2015-03-01
>>> ( Wheezy 7.8 )
>>>
>>>
>>> william@beaglebone:~$ sudo apt-get update
>>> william@beaglebone:~$ apt-cache search linux-image-4 |grep bone-rt
>>> linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
>>> linux-image-4.1.10-bone-rt-r16 - Linux kernel, version 4.1.10-bone-rt-r16
>>> linux-image-4.1.11-bone-rt-r16 - Linux kernel, version 4.1.11-bone-rt-r16
>>> linux-image-4.1.12-bone-rt-r16 - Linux kernel, version 4.1.12-bone-rt-r16
>>> linux-image-4.1.13-bone-rt-r16 - Linux kernel, version 4.1.13-bone-rt-r16
>>> linux-image-4.1.13-bone-rt-r17 - Linux kernel, version 4.1.13-bone-rt-r17
>>> linux-image-4.1.14-bone-rt-r17 - Linux kernel, version 4.1.14-bone-rt-r17
>>> linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17
>>> linux-image-4.1.15-bone-rt-r18 - Linux kernel, version 4.1.15-bone-rt-r18
>>> linux-image-4.1.16-bone-rt-r18 - Linux kernel, version 4.1.16-bone-rt-r18
>>> linux-image-4.1.17-bone-rt-r18 - Linux kernel, version 4.1.17-bone-rt-r18
>>> linux-image-4.1.17-bone-rt-r19 - Linux kernel, version 4.1.17-bone-rt-r19
>>> linux-image-4.1.18-bone-rt-r19 - Linux kernel, version 4.1.18-bone-rt-r19
>>> linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
>>> linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
>>> linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
>>> linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
>>> linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
>>> linux-image-4.4.0-bone-rt-r1 - Linux kernel, version 4.4.0-bone-rt-r1
>>> linux-image-4.4.0-bone-rt-r2 - Linux kernel, version 4.4.0-bone-rt-r2
>>> linux-image-4.4.0-bone-rt-r3 - Linux kernel, version 4.4.0-bone-rt-r3
>>> linux-image-4.4.0-rc8-bone-rt-r1 - Linux kernel, version
>>> 4.4.0-rc8-bone-rt-r1
>>> linux-image-4.4.1-bone-rt-r4 - Linux kernel, version 4.4.1-bone-rt-r4
>>> linux-image-4.4.1-bone-rt-r5 - Linux kernel, version 4.4.1-bone-rt-r5
>>> linux-image-4.4.2-bone-rt-r5 - Linux kernel, version 4.4.2-bone-rt-r5
>>>
>>> william@beaglebone:~$ sudo apt-get install linux-image-4.4.2-bone-rt-r5
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> Suggested packages:
>>>   linux-firmware-image-4.4.2-bone-rt-r5
>>> The following NEW packages will be installed:
>>>   linux-image-4.4.2-bone-rt-r5
>>> 0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded.
>>> Need to get 27.6 MB of archives.
>>> After this operation, 70.4 MB of additional disk space will be used.
>>>
>>> . . .
>>>
>>> Unpacking linux-image-4.4.2-bone-rt-r5 (from
>>> .../linux-image-4.4.2-bone-rt-r5_1wheezy_armhf.deb) ...
>>> Setting up linux-image-4.4.2-bone-rt-r5 (1wheezy) ...
>>> update-initramfs: Generating /boot/initrd.img-4.4.2-bone-rt-r5
>>> zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.4.2-bone-rt-r5]
>>>
>>> william@beaglebone:~$ sudo reboot
>>>
>>> Broadcast message from root@beaglebone (pts/0) (Thu Feb 25 20:20:41
>>> 2016):
>>> The system is going down for reboot NOW!
>>> william@beaglebone:~$ Connection to 192.168.xxx.xx

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[William Hermans]

linux-image-4.3.6-bone5 -> Non functional. Notice that the output of dmesg
mentions nothing of "bad pin configuration" such as output in working
kernels. e.g.
[   56.304965] pruss_uio 4a30.pruss: pins are not configured from the
driver

Workflow:
william@beaglebone:~$ sudo apt-get install linux-image-4.3.6-bone5
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  linux-firmware-image-4.3.6-bone5
The following NEW packages will be installed:
  linux-image-4.3.6-bone5
0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded.
Need to get 26.7 MB of archives.
After this operation, 66.8 MB of additional disk space will be used.
. . .
Unpacking linux-image-4.3.6-bone5 (from
.../linux-image-4.3.6-bone5_1wheezy_armhf.deb) ...
Setting up linux-image-4.3.6-bone5 (1wheezy) ...
update-initramfs: Generating /boot/initrd.img-4.3.6-bone5
zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.3.6-bone5]

william@beaglebone:~$ sudo reboot

william@beaglebone:~$ uname -r
4.3.6-bone5
william@beaglebone:~$ sudo sh -c "echo 'pru_enable' >
/sys/devices/platform/bone_capemgr/slots"
william@beaglebone:~$ dmesg | grep pru
[  113.299845] bone_capemgr bone_capemgr: part_number 'pru_enable', version
'N/A'
[  113.319610] bone_capemgr bone_capemgr: slot #4: 'Override Board
Name,00A0,Override Manuf,pru_enable'
[  113.332465] bone_capemgr bone_capemgr: slot #4: dtbo
'pru_enable-00A0.dtbo' loaded; overlay id #0
william@beaglebone:~$ lsmod |grep pru
william@beaglebone:~$ lsmod
Module  Size  Used by
bnep   12909  2
rfcomm 52472  0
bluetooth 399731  10 bnep,rfcomm
nfsd  217981  2

On Thu, Feb 25, 2016 at 9:11 PM, William Hermans  wrote:

> linux-image-4.2.5-bone2 -> Functional
>
> william@beaglebone:~$ sudo apt-get install linux-image-4.2.5-bone2
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Suggested packages:
>   linux-firmware-image-4.2.5-bone2
> The following NEW packages will be installed:
>   linux-image-4.2.5-bone2
> 0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded.
> Need to get 26.2 MB of archives.
> After this operation, 65.5 MB of additional disk space will be used.
> . . .
> Unpacking linux-image-4.2.5-bone2 (from
> .../linux-image-4.2.5-bone2_1wheezy_armhf.deb) ...
> Setting up linux-image-4.2.5-bone2 (1wheezy) ...
> update-initramfs: Generating /boot/initrd.img-4.2.5-bone2
> zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.2.5-bone2]
>
> william@beaglebone:~$ sudo reboot
>
> william@beaglebone:~$ uname -r
> 4.2.5-bone2
> william@beaglebone:~$ sudo sh -c "echo 'pru_enable' >
> /sys/devices/platform/bone_capemgr/slots"
> william@beaglebone:~$ dmesg | grep pru
> [   56.250528] bone_capemgr bone_capemgr: part_number 'pru_enable',
> version 'N/A'
> [   56.270616] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A0,Override Manuf,pru_enable'
> [   56.293224] bone_capemgr bone_capemgr: slot #4: dtbo
> 'pru_enable-00A0.dtbo' loaded; overlay id #1
> [   56.304965] pruss_uio 4a30.pruss: pins are not configured from the
> driver
> william@beaglebone:~$ lsmod |grep pru
> uio_pruss   4244  0
> uio 8146  2 uio_pruss,uio_pdrv_genirq
>
> On Thu, Feb 25, 2016 at 9:02 PM, William Hermans 
> wrote:
>
>> GIve me a few, I'll test both.
>>
>> On Thu, Feb 25, 2016 at 8:48 PM, Robert Nelson 
>> wrote:
>>
>>>
>>>
>>> On Thu, Feb 25, 2016 at 9:42 PM, William Hermans 
>>> wrote:
>>>
 BY the way . . . my workflow . . .

 william@beaglebone:~$ uname -r
 4.1.12-bone-rt-r16
 william@beaglebone:~$ cat /etc/dogtag
 BeagleBoard.org Debian Image 2015-03-01
 ( Wheezy 7.8 )


 william@beaglebone:~$ sudo apt-get update
 william@beaglebone:~$ apt-cache search linux-image-4 |grep bone-rt
 linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
 linux-image-4.1.10-bone-rt-r16 - Linux kernel, version
 4.1.10-bone-rt-r16
 linux-image-4.1.11-bone-rt-r16 - Linux kernel, version
 4.1.11-bone-rt-r16
 linux-image-4.1.12-bone-rt-r16 - Linux kernel, version
 4.1.12-bone-rt-r16
 linux-image-4.1.13-bone-rt-r16 - Linux kernel, version
 4.1.13-bone-rt-r16
 linux-image-4.1.13-bone-rt-r17 - Linux kernel, version
 4.1.13-bone-rt-r17
 linux-image-4.1.14-bone-rt-r17 - Linux kernel, version
 4.1.14-bone-rt-r17
 linux-image-4.1.15-bone-rt-r17 - Linux kernel, version
 4.1.15-bone-rt-r17
 linux-image-4.1.15-bone-rt-r18 - Linux kernel, version
 4.1.15-bone-rt-r18
 linux-image-4.1.16-bone-rt-r18 - Linux kernel, version
 4.1.16-bone-rt-r18
 linux-image-4.1.17-bone-rt-r18 - Linux kernel, version
 4.1.17-bone-rt-r18
 linux-image-4.1.17-bone-rt-r19 - Linux kernel, version
 4.1.17-bone-rt-r19
 linux-image-4.1.18-bone-rt-r19 - Linux kernel, version
 4.1.18-bone-rt-r19
 linux-image-4.1.3-bone-r

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[William Hermans]

One other thing on the last kernel version. The USR LEDs do not seem
configured either. At least they do not blink at boot up, and confused me
into thinking the image was not booting . . .

On Thu, Feb 25, 2016 at 9:22 PM, William Hermans  wrote:

> linux-image-4.3.6-bone5 -> Non functional. Notice that the output of
> dmesg mentions nothing of "bad pin configuration" such as output in working
> kernels. e.g.
> [   56.304965] pruss_uio 4a30.pruss: pins are not configured from the
> driver
>
> Workflow:
> william@beaglebone:~$ sudo apt-get install linux-image-4.3.6-bone5
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Suggested packages:
>   linux-firmware-image-4.3.6-bone5
> The following NEW packages will be installed:
>   linux-image-4.3.6-bone5
> 0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded.
> Need to get 26.7 MB of archives.
> After this operation, 66.8 MB of additional disk space will be used.
> . . .
> Unpacking linux-image-4.3.6-bone5 (from
> .../linux-image-4.3.6-bone5_1wheezy_armhf.deb) ...
> Setting up linux-image-4.3.6-bone5 (1wheezy) ...
> update-initramfs: Generating /boot/initrd.img-4.3.6-bone5
> zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.3.6-bone5]
>
> william@beaglebone:~$ sudo reboot
>
> william@beaglebone:~$ uname -r
> 4.3.6-bone5
> william@beaglebone:~$ sudo sh -c "echo 'pru_enable' >
> /sys/devices/platform/bone_capemgr/slots"
> william@beaglebone:~$ dmesg | grep pru
> [  113.299845] bone_capemgr bone_capemgr: part_number 'pru_enable',
> version 'N/A'
> [  113.319610] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A0,Override Manuf,pru_enable'
> [  113.332465] bone_capemgr bone_capemgr: slot #4: dtbo
> 'pru_enable-00A0.dtbo' loaded; overlay id #0
> william@beaglebone:~$ lsmod |grep pru
> william@beaglebone:~$ lsmod
> Module  Size  Used by
> bnep   12909  2
> rfcomm 52472  0
> bluetooth 399731  10 bnep,rfcomm
> nfsd  217981  2
>
> On Thu, Feb 25, 2016 at 9:11 PM, William Hermans 
> wrote:
>
>> linux-image-4.2.5-bone2 -> Functional
>>
>> william@beaglebone:~$ sudo apt-get install linux-image-4.2.5-bone2
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Suggested packages:
>>   linux-firmware-image-4.2.5-bone2
>> The following NEW packages will be installed:
>>   linux-image-4.2.5-bone2
>> 0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded.
>> Need to get 26.2 MB of archives.
>> After this operation, 65.5 MB of additional disk space will be used.
>> . . .
>> Unpacking linux-image-4.2.5-bone2 (from
>> .../linux-image-4.2.5-bone2_1wheezy_armhf.deb) ...
>> Setting up linux-image-4.2.5-bone2 (1wheezy) ...
>> update-initramfs: Generating /boot/initrd.img-4.2.5-bone2
>> zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.2.5-bone2]
>>
>> william@beaglebone:~$ sudo reboot
>>
>> william@beaglebone:~$ uname -r
>> 4.2.5-bone2
>> william@beaglebone:~$ sudo sh -c "echo 'pru_enable' >
>> /sys/devices/platform/bone_capemgr/slots"
>> william@beaglebone:~$ dmesg | grep pru
>> [   56.250528] bone_capemgr bone_capemgr: part_number 'pru_enable',
>> version 'N/A'
>> [   56.270616] bone_capemgr bone_capemgr: slot #4: 'Override Board
>> Name,00A0,Override Manuf,pru_enable'
>> [   56.293224] bone_capemgr bone_capemgr: slot #4: dtbo
>> 'pru_enable-00A0.dtbo' loaded; overlay id #1
>> [   56.304965] pruss_uio 4a30.pruss: pins are not configured from the
>> driver
>> william@beaglebone:~$ lsmod |grep pru
>> uio_pruss   4244  0
>> uio 8146  2 uio_pruss,uio_pdrv_genirq
>>
>> On Thu, Feb 25, 2016 at 9:02 PM, William Hermans 
>> wrote:
>>
>>> GIve me a few, I'll test both.
>>>
>>> On Thu, Feb 25, 2016 at 8:48 PM, Robert Nelson 
>>> wrote:
>>>


 On Thu, Feb 25, 2016 at 9:42 PM, William Hermans 
 wrote:

> BY the way . . . my workflow . . .
>
> william@beaglebone:~$ uname -r
> 4.1.12-bone-rt-r16
> william@beaglebone:~$ cat /etc/dogtag
> BeagleBoard.org Debian Image 2015-03-01
> ( Wheezy 7.8 )
>
>
> william@beaglebone:~$ sudo apt-get update
> william@beaglebone:~$ apt-cache search linux-image-4 |grep bone-rt
> linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
> linux-image-4.1.10-bone-rt-r16 - Linux kernel, version
> 4.1.10-bone-rt-r16
> linux-image-4.1.11-bone-rt-r16 - Linux kernel, version
> 4.1.11-bone-rt-r16
> linux-image-4.1.12-bone-rt-r16 - Linux kernel, version
> 4.1.12-bone-rt-r16
> linux-image-4.1.13-bone-rt-r16 - Linux kernel, version
> 4.1.13-bone-rt-r16
> linux-image-4.1.13-bone-rt-r17 - Linux kernel, version
> 4.1.13-bone-rt-r17
> linux-image-4.1.14-bone-rt-r17 - Linux kernel, version
> 4.1.14-bone-rt-r17
> linux-image-4.1.15-bone-rt-r17 - Linux kernel, version
> 4.1.15-bone-rt-r17
> linux-image-4.1.15-bone-

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[William Hermans]

How to Revert:

william@beaglebone:~$ sudo nano /boot/uEnv.txt

Change: uname_r=4.3.6-bone5 to uname_r=4.1.12-bone-rt-r16

william@beaglebone:~$ sudo reboot

william@beaglebone:~$ uname -r
4.1.12-bone-rt-r16

william@beaglebone:~$ sudo apt-get remove --purge linux-image-4.3.6-bone5
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  linux-image-4.3.6-bone5*
0 upgraded, 0 newly installed, 1 to remove and 45 not upgraded.
After this operation, 66.8 MB disk space will be freed.
. . .
update-initramfs: Deleting /boot/initrd.img-4.3.6-bone5
Purging configuration files for linux-image-4.3.6-bone5 ...
dpkg: warning: while removing linux-image-4.3.6-bone5, directory
'/lib/modules/4.3.6-bone5' not empty so not removed
william@beaglebone:~$ sudo rm -rf /lib/modules/4.3.6-bone5

william@beaglebone:~$ sudo apt-get remove --purge linux-image-4.2.5-bone2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  linux-image-4.2.5-bone2*
0 upgraded, 0 newly installed, 1 to remove and 45 not upgraded.
After this operation, 65.5 MB disk space will be freed.
. . .
update-initramfs: Deleting /boot/initrd.img-4.2.5-bone2
Purging configuration files for linux-image-4.2.5-bone2 ...
dpkg: warning: while removing linux-image-4.2.5-bone2, directory
'/lib/modules/4.2.5-bone2' not empty so not removed
william@beaglebone:~$ sudo rm -rf /lib/modules/4.2.5-bone2

william@beaglebone:~$ sudo apt-get remove --purge
linux-image-4.4.2-bone-rt-r5
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  linux-image-4.4.2-bone-rt-r5*
0 upgraded, 0 newly installed, 1 to remove and 45 not upgraded.
After this operation, 70.4 MB disk space will be freed.
. . .
Removing linux-image-4.4.2-bone-rt-r5 ...
update-initramfs: Deleting /boot/initrd.img-4.4.2-bone-rt-r5
Purging configuration files for linux-image-4.4.2-bone-rt-r5 ...
dpkg: warning: while removing linux-image-4.4.2-bone-rt-r5, directory
'/lib/modules/4.4.2-bone-rt-r5' not empty so not removed

william@beaglebone:~$ sudo rm -rf /lib/modules/4.4.2-bone-rt-r5

On Thu, Feb 25, 2016 at 9:26 PM, William Hermans  wrote:

> One other thing on the last kernel version. The USR LEDs do not seem
> configured either. At least they do not blink at boot up, and confused me
> into thinking the image was not booting . . .
>
> On Thu, Feb 25, 2016 at 9:22 PM, William Hermans 
> wrote:
>
>> linux-image-4.3.6-bone5 -> Non functional. Notice that the output of
>> dmesg mentions nothing of "bad pin configuration" such as output in working
>> kernels. e.g.
>> [   56.304965] pruss_uio 4a30.pruss: pins are not configured from the
>> driver
>>
>> Workflow:
>> william@beaglebone:~$ sudo apt-get install linux-image-4.3.6-bone5
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Suggested packages:
>>   linux-firmware-image-4.3.6-bone5
>> The following NEW packages will be installed:
>>   linux-image-4.3.6-bone5
>> 0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded.
>> Need to get 26.7 MB of archives.
>> After this operation, 66.8 MB of additional disk space will be used.
>> . . .
>> Unpacking linux-image-4.3.6-bone5 (from
>> .../linux-image-4.3.6-bone5_1wheezy_armhf.deb) ...
>> Setting up linux-image-4.3.6-bone5 (1wheezy) ...
>> update-initramfs: Generating /boot/initrd.img-4.3.6-bone5
>> zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.3.6-bone5]
>>
>> william@beaglebone:~$ sudo reboot
>>
>> william@beaglebone:~$ uname -r
>> 4.3.6-bone5
>> william@beaglebone:~$ sudo sh -c "echo 'pru_enable' >
>> /sys/devices/platform/bone_capemgr/slots"
>> william@beaglebone:~$ dmesg | grep pru
>> [  113.299845] bone_capemgr bone_capemgr: part_number 'pru_enable',
>> version 'N/A'
>> [  113.319610] bone_capemgr bone_capemgr: slot #4: 'Override Board
>> Name,00A0,Override Manuf,pru_enable'
>> [  113.332465] bone_capemgr bone_capemgr: slot #4: dtbo
>> 'pru_enable-00A0.dtbo' loaded; overlay id #0
>> william@beaglebone:~$ lsmod |grep pru
>> william@beaglebone:~$ lsmod
>> Module  Size  Used by
>> bnep   12909  2
>> rfcomm 52472  0
>> bluetooth 399731  10 bnep,rfcomm
>> nfsd  217981  2
>>
>> On Thu, Feb 25, 2016 at 9:11 PM, William Hermans 
>> wrote:
>>
>>> linux-image-4.2.5-bone2 -> Functional
>>>
>>> william@beaglebone:~$ sudo apt-get install linux-image-4.2.5-bone2
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> Suggested packages:
>>>   linux-firmware-image-4.2.5-bone2
>>> The following NEW packages will be installed:
>>>   linux-image-4.2.5-bone2
>>> 0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded.
>>> Need to get 26.2 MB of archives.
>>> After this operation, 65.5 MB of additional disk space will be used

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[William Hermans]

>
> *Change: uname_r=4.3.6-bone5 to uname_r=4.1.12-bone-rt-r16*
>

If you're not using the same kernel version I'm using the above is wrong.
So ask before rendering your system non bootable.

On Thu, Feb 25, 2016 at 9:35 PM, William Hermans  wrote:

> How to Revert:
>
> william@beaglebone:~$ sudo nano /boot/uEnv.txt
>
> Change: uname_r=4.3.6-bone5 to uname_r=4.1.12-bone-rt-r16
>
> william@beaglebone:~$ sudo reboot
>
> william@beaglebone:~$ uname -r
> 4.1.12-bone-rt-r16
>
> william@beaglebone:~$ sudo apt-get remove --purge linux-image-4.3.6-bone5
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be REMOVED:
>   linux-image-4.3.6-bone5*
> 0 upgraded, 0 newly installed, 1 to remove and 45 not upgraded.
> After this operation, 66.8 MB disk space will be freed.
> . . .
> update-initramfs: Deleting /boot/initrd.img-4.3.6-bone5
> Purging configuration files for linux-image-4.3.6-bone5 ...
> dpkg: warning: while removing linux-image-4.3.6-bone5, directory
> '/lib/modules/4.3.6-bone5' not empty so not removed
> william@beaglebone:~$ sudo rm -rf /lib/modules/4.3.6-bone5
>
> william@beaglebone:~$ sudo apt-get remove --purge linux-image-4.2.5-bone2
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be REMOVED:
>   linux-image-4.2.5-bone2*
> 0 upgraded, 0 newly installed, 1 to remove and 45 not upgraded.
> After this operation, 65.5 MB disk space will be freed.
> . . .
> update-initramfs: Deleting /boot/initrd.img-4.2.5-bone2
> Purging configuration files for linux-image-4.2.5-bone2 ...
> dpkg: warning: while removing linux-image-4.2.5-bone2, directory
> '/lib/modules/4.2.5-bone2' not empty so not removed
> william@beaglebone:~$ sudo rm -rf /lib/modules/4.2.5-bone2
>
> william@beaglebone:~$ sudo apt-get remove --purge
> linux-image-4.4.2-bone-rt-r5
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be REMOVED:
>   linux-image-4.4.2-bone-rt-r5*
> 0 upgraded, 0 newly installed, 1 to remove and 45 not upgraded.
> After this operation, 70.4 MB disk space will be freed.
> . . .
> Removing linux-image-4.4.2-bone-rt-r5 ...
> update-initramfs: Deleting /boot/initrd.img-4.4.2-bone-rt-r5
> Purging configuration files for linux-image-4.4.2-bone-rt-r5 ...
> dpkg: warning: while removing linux-image-4.4.2-bone-rt-r5, directory
> '/lib/modules/4.4.2-bone-rt-r5' not empty so not removed
>
> william@beaglebone:~$ sudo rm -rf /lib/modules/4.4.2-bone-rt-r5
>
> On Thu, Feb 25, 2016 at 9:26 PM, William Hermans 
> wrote:
>
>> One other thing on the last kernel version. The USR LEDs do not seem
>> configured either. At least they do not blink at boot up, and confused me
>> into thinking the image was not booting . . .
>>
>> On Thu, Feb 25, 2016 at 9:22 PM, William Hermans 
>> wrote:
>>
>>> linux-image-4.3.6-bone5 -> Non functional. Notice that the output of
>>> dmesg mentions nothing of "bad pin configuration" such as output in working
>>> kernels. e.g.
>>> [   56.304965] pruss_uio 4a30.pruss: pins are not configured from
>>> the driver
>>>
>>> Workflow:
>>> william@beaglebone:~$ sudo apt-get install linux-image-4.3.6-bone5
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> Suggested packages:
>>>   linux-firmware-image-4.3.6-bone5
>>> The following NEW packages will be installed:
>>>   linux-image-4.3.6-bone5
>>> 0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded.
>>> Need to get 26.7 MB of archives.
>>> After this operation, 66.8 MB of additional disk space will be used.
>>> . . .
>>> Unpacking linux-image-4.3.6-bone5 (from
>>> .../linux-image-4.3.6-bone5_1wheezy_armhf.deb) ...
>>> Setting up linux-image-4.3.6-bone5 (1wheezy) ...
>>> update-initramfs: Generating /boot/initrd.img-4.3.6-bone5
>>> zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.3.6-bone5]
>>>
>>> william@beaglebone:~$ sudo reboot
>>>
>>> william@beaglebone:~$ uname -r
>>> 4.3.6-bone5
>>> william@beaglebone:~$ sudo sh -c "echo 'pru_enable' >
>>> /sys/devices/platform/bone_capemgr/slots"
>>> william@beaglebone:~$ dmesg | grep pru
>>> [  113.299845] bone_capemgr bone_capemgr: part_number 'pru_enable',
>>> version 'N/A'
>>> [  113.319610] bone_capemgr bone_capemgr: slot #4: 'Override Board
>>> Name,00A0,Override Manuf,pru_enable'
>>> [  113.332465] bone_capemgr bone_capemgr: slot #4: dtbo
>>> 'pru_enable-00A0.dtbo' loaded; overlay id #0
>>> william@beaglebone:~$ lsmod |grep pru
>>> william@beaglebone:~$ lsmod
>>> Module  Size  Used by
>>> bnep   12909  2
>>> rfcomm 52472  0
>>> bluetooth 399731  10 bnep,rfcomm
>>> nfsd  217981  2
>>>
>>> On Thu, Feb 25, 2016 at 9:11 PM, William Hermans 
>>> wrote:
>>>
 linux-image-4.2.5-bone2 -> Functional

 william@beaglebone:~$ sudo apt-get install linux-image-4.2.5-bon

Re: [beagleboard] pru issues on BBB, jessie 4.4.2-bone-rt-rt5 kernel

[lajos kamocsay]

I do get uio_pruss automatically loaded with or without the device tree
file. But the systemd-udevd processes hog the cpu on boot until they get
killed eventually after a minute or two.

I tried to build a 4.1 kernel, but there are some i386 dependencies for the
build process that I can't install on my debian jessie machine. I'll try
tomorrow from a ubuntu vm.
On Feb 25, 2016 10:31 PM, "William Hermans"  wrote:

> *and i'm not sure anyone has actually tested the uio_pruss on v4.4.x..*
>>
>> * It's the same patches forward ported from v4.1.x -> v4.2.x -> v4.3.x..
>> ;)*
>>
>> * But, i wonder if it works on v4.4.x. ;)*
>
>
> I'm testing now. The kernel modules are not automatically loaded when
> enabling the pru's through a device tree. So something has changed, and I'm
> not sure what it is. however . . .
>
> william@beaglebone:~$ sudo modprobe uio_pruss
> william@beaglebone:~$ lsmod
> Module  Size  Used by
> uio_pruss   4436  0
> uio 8247  1 uio_pruss
> rfcomm 53016  0
> bluetooth 406428  9 rfcomm
> nfsd  223727  2
>
>
> This does not seem right. Which may be my own fault, but let me double
> check.
>
> On Thu, Feb 25, 2016 at 8:17 PM, Robert Nelson 
> wrote:
>
>> and i'm not sure anyone has actually tested the uio_pruss on v4.4.x..
>>
>> It's the same patches forward ported from v4.1.x -> v4.2.x -> v4.3.x.. ;)
>>
>> But, i wonder if it works on v4.4.x. ;)
>>
>> On Thu, Feb 25, 2016 at 9:10 PM, William Hermans 
>> wrote:
>> > Heh, perfect example of why one need to update the APT cache .  . .
>> >
>> > william@beaglebone:~$ sudo apt-get update
>> > william@beaglebone:~$ apt-cache search linux-image-4 |grep bone-rt
>> > linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
>> > linux-image-4.1.10-bone-rt-r16 - Linux kernel, version
>> 4.1.10-bone-rt-r16
>> > linux-image-4.1.11-bone-rt-r16 - Linux kernel, version
>> 4.1.11-bone-rt-r16
>> > linux-image-4.1.12-bone-rt-r16 - Linux kernel, version
>> 4.1.12-bone-rt-r16
>> > linux-image-4.1.13-bone-rt-r16 - Linux kernel, version
>> 4.1.13-bone-rt-r16
>> > linux-image-4.1.13-bone-rt-r17 - Linux kernel, version
>> 4.1.13-bone-rt-r17
>> > linux-image-4.1.14-bone-rt-r17 - Linux kernel, version
>> 4.1.14-bone-rt-r17
>> > linux-image-4.1.15-bone-rt-r17 - Linux kernel, version
>> 4.1.15-bone-rt-r17
>> > linux-image-4.1.15-bone-rt-r18 - Linux kernel, version
>> 4.1.15-bone-rt-r18
>> > linux-image-4.1.16-bone-rt-r18 - Linux kernel, version
>> 4.1.16-bone-rt-r18
>> > linux-image-4.1.17-bone-rt-r18 - Linux kernel, version
>> 4.1.17-bone-rt-r18
>> > linux-image-4.1.17-bone-rt-r19 - Linux kernel, version
>> 4.1.17-bone-rt-r19
>> > linux-image-4.1.18-bone-rt-r19 - Linux kernel, version
>> 4.1.18-bone-rt-r19
>> > linux-image-4.1.3-bone-rt-r15 - Linux kernel, version 4.1.3-bone-rt-r15
>> > linux-image-4.1.5-bone-rt-r15 - Linux kernel, version 4.1.5-bone-rt-r15
>> > linux-image-4.1.7-bone-rt-r16 - Linux kernel, version 4.1.7-bone-rt-r16
>> > linux-image-4.1.8-bone-rt-r16 - Linux kernel, version 4.1.8-bone-rt-r16
>> > linux-image-4.1.9-bone-rt-r16 - Linux kernel, version 4.1.9-bone-rt-r16
>> > linux-image-4.4.0-bone-rt-r1 - Linux kernel, version 4.4.0-bone-rt-r1
>> > linux-image-4.4.0-bone-rt-r2 - Linux kernel, version 4.4.0-bone-rt-r2
>> > linux-image-4.4.0-bone-rt-r3 - Linux kernel, version 4.4.0-bone-rt-r3
>> > linux-image-4.4.0-rc8-bone-rt-r1 - Linux kernel, version
>> > 4.4.0-rc8-bone-rt-r1
>> > linux-image-4.4.1-bone-rt-r4 - Linux kernel, version 4.4.1-bone-rt-r4
>> > linux-image-4.4.1-bone-rt-r5 - Linux kernel, version 4.4.1-bone-rt-r5
>> > linux-image-4.4.2-bone-rt-r5 - Linux kernel, version 4.4.2-bone-rt-r5
>> >
>> >
>> > On Thu, Feb 25, 2016 at 8:04 PM, William Hermans 
>> wrote:
>> >>>
>> >>> I started from the Jessie BBB image that had the 4.1.15-ti-rt-r43
>> kernel.
>> >>> Now I have the 4.4.2-bone-rt-r5 kernel that I compiled and installed
>> myself,
>> >>> am I maybe missing some udev rules?
>> >>
>> >>
>> >> If I were you, I would . . .
>> >>
>> >> $ apt-cache search linux-image-4 |grep bone-rt
>> >> linux-image-4.0.6-bone-rt-r5 - Linux kernel, version 4.0.6-bone-rt-r5
>> >> linux-image-4.0.6-bone-rt-r6 - Linux kernel, version 4.0.6-bone-rt-r6
>> >> linux-image-4.0.7-bone-rt-r7 - Linux kernel, version 4.0.7-bone-rt-r7
>> >> linux-image-4.0.8-bone-rt-r8 - Linux kernel, version 4.0.8-bone-rt-r8
>> >> linux-image-4.1.10-bone-rt-r16 - Linux kernel, version
>> 4.1.10-bone-rt-r16
>> >> linux-image-4.1.11-bone-rt-r16 - Linux kernel, version
>> 4.1.11-bone-rt-r16
>> >> linux-image-4.1.12-bone-rt-r16 - Linux kernel, version
>> 4.1.12-bone-rt-r16
>> >> linux-image-4.1.13-bone-rt-r16 - Linux kernel, version
>> 4.1.13-bone-rt-r16
>> >> linux-image-4.1.13-bone-rt-r17 - Linux kernel, version
>> 4.1.13-bone-rt-r17
>> >> linux-image-4.1.14-bone-rt-r17 - Linux kernel, version
>> 4.1.14-bone-rt-r17
>> >> linux-image-4.1.15-bone-rt-r17 - Linux kernel, version
>> 4.1.15-bone-rt-