[beagleboard] Re: BeagleBoneBlack not booting with custom cape on

2016-05-27 Thread Greg 
Look at page 67 and 68 of the "Beaglebone Black System Reference Manual" 
regarding the "Boot Configuration".

Also this discussion:

https://groups.google.com/forum/#!category-topic/beagleboard/DdPYCIUB-Sg

Regards,
Greg


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/98c67195-bd32-49fb-a075-9cfb1d962078%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PRU RPMsg device file missing

2016-05-27 Thread Greg 
Here is the section of main.c which must be changed:

/*
 * Using the name 'rpmsg-client-sample' will probe the RPMsg sample driver
 * found at linux-x.y.z/samples/rpmsg/rpmsg_client_sample.c
 *
 * Using the name 'rpmsg-pru' will probe the rpmsg_pru driver found
 * at linux-x.y.z/drivers/rpmsg/rpmsg_pru.c
 */
//#define CHAN_NAME 
"rpmsg-client-sample"
#define CHAN_NAME   "rpmsg-pru"

The above is how it should be modified to get the virtual device file to 
appear.
I am using the exact same TI based kernel, lab 5 works and yields two-way 
PRU<->ARM messages.

Regards,
Greg

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/16bb3b8f-d444-4f70-b085-135d23c72d3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBone Black/Green SPI pins always low with 4.1.22 kernel

2016-05-27 Thread John Syne 
Hi Robert,

You are talking about the edma not being registered for the SPI when using 
overlays, right?

I’ve been working on adding DMA to the IIO ADC driver and I came across the 
same problem. It seems like prepare_unused_channel_list is only called the 
first time edma_alloc_channel is called. In prepare_unused_channel_list, it 
scans the device tree for “dmas” & “dma-cells” and sets up the 
edma_cc[0]->edma_unused. 

So similar to the problem you have with SPI, I had to add the ADC spec into the 
base devicetree because the overlay would not work. 

Regards,
John




> On May 27, 2016, at 6:34 AM, Robert Nelson  wrote:
> 
> 
> 
> On Fri, May 27, 2016 at 8:29 AM, Mattt C  > wrote:
> Hi, 
> 
> I got the exact same problem. I use the DTBO BB-SPIDEV0 with linux kernel 
> 4.1.15. The pinmux of SPI pins doesn't change when I load the SPI overlay. I 
> tried loading I2C1, pin P9_18 change its pinmux. When I load SPIDEV0, it 
> doesn't.
> 
> BB-SPIDEV0 needs to be loaded at bootup, not later, as it will fail if 
> manually loaded...
> 
> add it to /boot/uEnv.txt
> 
> cape_enable=bone_capemgr.enable_partno=BB-SPIDEV0
> 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 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYh%3DmV%2BPb48zEjy3Zqh2HN_kq_iCAZB2KCcfmdVhAWqUzA%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/AF448155-FF26-44DB-AC2E-AA7632AA82BD%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PRU RPMsg device file missing

2016-05-27 Thread Greg 
I may not be remembering this correctly.  In one of the labs, and it may be 
#5, you have to uncomment/comment some lines in the C file to cause the 
rpmsg driver to be "probed".

This will cause the virtual device file to appear in the /dev directory.
I have got it functioning correctly and I think I have the same version you 
are working with.

I'll double-check when I get home later this evening.

Regards,
Greg


>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/bf6d89c3-345b-4b99-8516-b7046d7e26a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBoneBlack not booting with custom cape on

2016-05-27 Thread Greg 
Be careful that your cape does not put a resistive load on those pins.  I 
had an LED switching network connected to Pin 8.44.
This causes the BBB to not boot.

I don't have my documentation with me, but there are several pins which 
have this property.

I added a series resistor, I think about 50kohm, which allows the LED 
switch circuit to work, but decreased the load enough for the boot process 
to proceed successfully.

I was using a BJT switching circuit.  A MOSFET switch with very high input 
resistance would not have caused this type of problem.

Regards,
Greg


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d60753d2-fa85-4435-924f-f2603b78a3da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Kernel Panic: NULL pointer dereference

2016-05-27 Thread Jan Meitner 
PROBLEM SOLVED:

Using the Pins 31 to 46 on P8 with external Pullups causes the BBB to 
change it's startupsequence! You can use them after boot is finished.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/09f222fc-af55-4d36-a4c4-2be01157eab0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Ethernet-over-USB: no IP assigned with latest images (Debian 7.9 2015-11-12, Debian 8.4 2016-05-13)

2016-05-27 Thread Andrey Somov 
No, it does not (eth2:avahi was added):

eth2  Link encap:Ethernet  HWaddr d0:5f:b8:a3:51:a5  
  inet6 addr: fe80::d25f:b8ff:fea3:51a5/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:38 errors:0 dropped:0 overruns:0 frame:0
  TX packets:243 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:7507 (7.5 KB)  TX bytes:64147 (64.1 KB)

eth2:avahi Link encap:Ethernet  HWaddr d0:5f:b8:a3:51:a5  
  inet addr:169.254.9.54  Bcast:169.254.255.255  Mask:255.255.0.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/83b70c1b-73aa-4c3d-9f30-1199c4aaf8bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Unable to ssh into Beaglebone Black from Arch Linux

2016-05-27 Thread Andrey Somov 
I have the same problem and I had to downgrade to fix it.
This image does not have the problem:
Debian 7.8 (BeagleBone, BeagleBone Black - 4GB SD) 2015-03-01 - more info - 
md5: c848627722b7a5f7bc89791cc8949e3b

Cheers,
Andrey

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4fb34620-904e-403b-a3d8-114a379c3af0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Ethernet-over-USB: no IP assigned with latest images (Debian 7.9 2015-11-12, Debian 8.4 2016-05-13)

2016-05-27 Thread Robert Nelson 
On Fri, May 27, 2016 at 10:57 AM, Andrey Somov 
wrote:

> I tried the image
> Debian 7.9 (BeagleBone, BeagleBone Black, SeeedStudio BeagleBone Green -
> 4GB SD) 2015-11-12
> sha256sum: f6e67ba01ff69d20f2c655f5e429c3e6c2398123bcd3d8d548460c597275d277
>
> The IP address is assigned randomly. I could not clearly see the pattern.
> I think it works better if the power is given pluging in the USB cable then
> when pressing the POWER button on BBB
>
> This is the 'ifconfig -a':
> ==
> br-4270761bdbf4 Link encap:Ethernet  HWaddr 02:42:60:c0:ef:5a
>   inet addr:172.23.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> br-4e56a19f7872 Link encap:Ethernet  HWaddr 02:42:7d:ab:f3:4b
>   inet addr:172.19.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> br-5f853dc6d996 Link encap:Ethernet  HWaddr 02:42:e4:6d:0a:f0
>   inet addr:172.22.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> br-6ef8d2001e87 Link encap:Ethernet  HWaddr 02:42:4c:49:1c:88
>   inet addr:172.21.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> br-89dd64f3e0c7 Link encap:Ethernet  HWaddr 02:42:95:bf:54:c8
>   inet addr:172.20.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> br-c734abfd4862 Link encap:Ethernet  HWaddr 02:42:26:28:03:b2
>   inet addr:172.18.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> docker0   Link encap:Ethernet  HWaddr 02:42:aa:81:55:e2
>   inet addr:172.17.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> eth0  Link encap:Ethernet  HWaddr 28:d2:44:96:fb:15
>   inet addr:10.10.15.39  Bcast:10.10.255.255  Mask:255.255.0.0
>   inet6 addr: fe80::2ad2:44ff:fe96:fb15/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:12334 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:3538 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:4939001 (4.9 MB)  TX bytes:355314 (355.3 KB)
>
> eth2  Link encap:Ethernet  HWaddr d0:5f:b8:a3:51:a5
>   inet6 addr: fe80::d25f:b8ff:fea3:51a5/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:40 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:7659 (7.6 KB)  TX bytes:34695 (34.6 KB)
>


Does it grab an ip with :

sudo dhclient eth2

?

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYiF8M81J%2BOZBEXKGKhsBL_hstNGm4barRbsgRdF0jYvSQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Ethernet-over-USB: no IP assigned with latest images (Debian 7.9 2015-11-12, Debian 8.4 2016-05-13)

2016-05-27 Thread Andrey Somov 
I tried the image 
Debian 7.9 (BeagleBone, BeagleBone Black, SeeedStudio BeagleBone Green - 
4GB SD) 2015-11-12 
sha256sum: f6e67ba01ff69d20f2c655f5e429c3e6c2398123bcd3d8d548460c597275d277

The IP address is assigned randomly. I could not clearly see the pattern. I 
think it works better if the power is given pluging in the USB cable then 
when pressing the POWER button on BBB

This is the 'ifconfig -a':
==
br-4270761bdbf4 Link encap:Ethernet  HWaddr 02:42:60:c0:ef:5a  
  inet addr:172.23.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

br-4e56a19f7872 Link encap:Ethernet  HWaddr 02:42:7d:ab:f3:4b  
  inet addr:172.19.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

br-5f853dc6d996 Link encap:Ethernet  HWaddr 02:42:e4:6d:0a:f0  
  inet addr:172.22.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

br-6ef8d2001e87 Link encap:Ethernet  HWaddr 02:42:4c:49:1c:88  
  inet addr:172.21.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

br-89dd64f3e0c7 Link encap:Ethernet  HWaddr 02:42:95:bf:54:c8  
  inet addr:172.20.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

br-c734abfd4862 Link encap:Ethernet  HWaddr 02:42:26:28:03:b2  
  inet addr:172.18.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

docker0   Link encap:Ethernet  HWaddr 02:42:aa:81:55:e2  
  inet addr:172.17.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0  Link encap:Ethernet  HWaddr 28:d2:44:96:fb:15  
  inet addr:10.10.15.39  Bcast:10.10.255.255  Mask:255.255.0.0
  inet6 addr: fe80::2ad2:44ff:fe96:fb15/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:12334 errors:0 dropped:0 overruns:0 frame:0
  TX packets:3538 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:4939001 (4.9 MB)  TX bytes:355314 (355.3 KB)

eth2  Link encap:Ethernet  HWaddr d0:5f:b8:a3:51:a5  
  inet6 addr: fe80::d25f:b8ff:fea3:51a5/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:40 errors:0 dropped:0 overruns:0 frame:0
  TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:7659 (7.6 KB)  TX bytes:34695 (34.6 KB)

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:888 errors:0 dropped:0 overruns:0 frame:0
  TX packets:888 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 
  RX bytes:333933 (333.9 KB)  TX bytes:333933 (333.9 KB)

wlan0 Link encap:Ethernet  HWaddr b8:ee:65:e9:d0:55  
  inet addr:10.12.1.7  Bcast:10.12.3.255  Mask:255.255.252.0
  inet6 addr: fe80::baee:65ff:fee9:d055/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:905 errors:0 dropped:0 overruns:0 frame:0
  TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:123679 (123.6 KB)  TX bytes:35621 (35.6 KB)
==

[beagleboard] Re: Kernel Panic: NULL pointer dereference

2016-05-27 Thread Jan Meitner 
This might be the Problem:

https://groups.google.com/forum/#!topic/beagleboard/PGB6S3aImmc

Accessing Pins that are responsible for the boot order.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0e7ac88f-828f-4b92-b1d8-0fff9a550d6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBoneBlack not booting with custom cape on

2016-05-27 Thread Gerald Coley 
If it were the reserved pins that were at fault, you would not be getting a
printout from the serial port as the board would never boot anything.

Gerald


On Fri, May 27, 2016 at 8:15 AM,  wrote:

> Hello,
>
> I am using the BeagleBoneBlack (BBB) in the educational sector. For a
> project I designed a cape. It all works very nice, if I plug in the cape
> one the BBB is started. My OS is on the eMMC and I use the SD-Card rarely
> for storing files.
>
> If I boot the BBB with the cape, it won't work. I suspect it has something
> to do with my using reserved pins for the HDMI, although I do disable them
> in the uEnv.txt.
> Booting with only the Cape connected to P9 works fine.
>
> On P8 is use the Pins: 11,14,15,16,17,19,31,32,33,34,35,7,38,45.
> In Derek Molloys Chart they are marked as reserved for hdmi.
>
> For a dump of uboot see below.
>
> Do you have an idea how what the problem is and how I can solve it?
>
> Thank you very much in advance!
>
> Kind regards,
>
> Jan
>
> --- uboot dump ---
>
>> =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2016.05.27 14:28:54
>> =~=~=~=~=~=~=~=~=~=~=~=
>> @uiP#!…W%ZDŒ XFPF©U
>>
>>
>> ü
>>
>> U-Boot 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06), Build:
>> jenkins-github_Bootloader-Builder-105
>>
>>Watchdog enabled
>> I2C:   ready
>> DRAM:  512 MiB
>> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
>> Using default environment
>>
>> Net:not set. Validating first E-fuse MAC
>>
>>
>> cpsw
>> Hit any key to stop autoboot:  1 0
>> gpio: pin 53 (gpio 53) value is 1
>> Card did not respond to voltage select!
>> Card did not respond to voltage select!
>> gpio: pin 56 (gpio 56) value is 0
>> gpio: pin 55 (gpio 55) value is 0
>> gpio: pin 54 (gpio 54) value is 0
>> switch to partitions #0, OK
>> mmc1(part 0) is current device
>> gpio: pin 54 (gpio 54) value is 1
>> Checking for: /uEnv.txt ...
>> Checking for: /boot.scr ...
>> Checking for: /boot/boot.scr ...
>> Checking for: /boot/uEnv.txt ...
>> gpio: pin 55 (gpio 55) value is 1
>> 829 bytes read in 15 ms (53.7 KiB/s)
>> Loaded environment from /boot/uEnv.txt
>> Checking if uname_r is set in /boot/uEnv.txt...
>> gpio: pin 56 (gpio 56) value is 1
>> Running uname_boot ...
>> loading /boot/vmlinuz-3.8.13-xenomai-r72 ...
>> 5741824 bytes read in 336 ms (16.3 MiB/s)
>> loading /boot/dtbs/3.8.13-xenomai-r72/am335x-boneblack.dtb ...
>> 26098 bytes read in 33 ms (771.5 KiB/s)
>> loading /boot/initrd.img-3.8.13-xenomai-r72 ...
>> 2286742 bytes read in 148 ms (14.7 MiB/s)
>> debug: [console=ttyO0,115200n8
>> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>> root=UUID=cf28a3f6-fcae-4d49-9887-f565a8bfbfaf ro rootfstype=ext4 rootwait
>> fixrtc quiet init=/lib/systemd/systemd] ...
>> debug: [bootz 0x8200 0x8808:22e496 0x8800] ...
>> Kernel image @ 0x8200 [ 0x00 - 0x579d00 ]
>> ## Flattened Device Tree blob at 8800
>>Booting using the fdt blob at 0x8800
>>Loading Ramdisk to 8fdd1000, end 8496 ... OK
>>Loading Device Tree to 8fdc7000, end 8fdd05f1 ... OK
>>
>> Starting kernel ...
>>
>> Uncompressing Linux... done, booting the kernel.
>> [0.359272] omap2_mbox_probe: platform not supported
>> [0.565509] tps65217-bl tps65217-bl: no platform data provided
>> [0.631529] bone-capemgr bone_capemgr.9: slot #0: No cape found
>> [0.84] bone-capemgr bone_capemgr.9: slot #1: No cape found
>> [0.701838] bone-capemgr bone_capemgr.9: slot #2: No cape found
>> [0.736994] bone-capemgr bone_capemgr.9: slot #3: No cape found
>> [0.757699] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset'
>> failed
>> [0.821243] pinctrl-single 44e10800.pinmux: pin 44e10854 already
>> requested by 44e10800.pinmux; cannot claim for gpio-leds.8
>> [0.835783] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8)
>> status -22
>> [0.844867] pinctrl-single 44e10800.pinmux: could not request pin 21
>> on device pinctrl-single
>> [0.929572] Unable to handle kernel NULL pointer dereference at
>> virtual address 006c
>> [0.940154] pgd = c0004000, hw pgd = de198000
>> [0.945818] [006c] *pgd=
>> [0.950483] Internal error: Oops: 5 [#1] THUMB2
>> [0.956352] Modules linked in:
>> [0.960314] CPU: 0Not tainted  (3.8.13-xenomai-r72 #1)
>> [0.967446] PC is at inode_sb_list_add+0x14/0x34
>> [0.973431] LR is at inode_sb_list_add+0xd/0x34
>> [0.979305] pc : []lr : []psr: 6033
>> [0.979305] sp : df06fec8  ip : c09c63c0  fp : 
>> [0.994192] r10: c087f6dc  r9 :   r8 : 
>> [1.000964] r7 : de99ac68  r6 : 41ed  r5 : c08caf2c  r4 : de99aad0
>> [1.009428] r3 :   r2 :   r1 : de99ab90  r0 : c08caf2c
>> [1.017892] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb
>> Segment kernel
>> [1.027594] Control: 50c5387d  Table: 9e198019  DAC: 0015
>> [1.035042] Process swapper (pid: 1, stack limit = 0xdf06e238)
>> [1.042605] Stack: (0xdf06fec8 to 0xdf07)
>> [1.048253] fec0

Re: [beagleboard] Vdds_ddr decoupling caps in am3358

2016-05-27 Thread larbi . joubala 
ok thank you for the reply.

Le jeudi 26 mai 2016 21:08:19 UTC+2, john3909 a écrit :
>
> There are several other factors that affect decoupling:
>
> PCB Layout (smaller is better)
> Ground planes size, distance between ground planes and dielectric material 
> used
> Decoupling cap ESR
> Proximity of the decoupling caps to the power pins
> Number and size of vias connected to power pins (think of vias as a small 
> inductor)
> Copper pour profile used to connect power pins to power rail
>
> Clearly the BBB layout is optimal and that is why they managed to make the 
> board work with fewer decoupling caps.
>
> Regards,
> John
>
>
>
>
> On May 26, 2016, at 8:52 AM, Gerald Coley  > wrote:
>
> Same answer as before.
>
> BeagleBone came first. 
> Smaller board size.
> Lower cost
> And it works.
>
> Gerald
>
> On Thu, May 26, 2016 at 10:46 AM, > 
> wrote:
>
>> I see difference between last schematic of beaglebone black and am3358 
>> starter kit board concerning vdds_ddr  decoupling cap. Am3358 sk board has 
>> 21 decoupling cap and beaglebone black uses 9 decoupling caps. The am3358 
>> datasheet specifies tu use min 20 decoupling caps. Why this difference?
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/b282b991-9043-4f98-8626-44bc5acb4de6%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Gerald
>  
> ger...@beagleboard.org 
> http://beagleboard.org/
> gco...@emprodesign.com 
>
>
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/CAHK_S%2BcKFuME82TcQfgtafO-63ZXVDNERAAcs8qmGs1q-doWqQ%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/fb25881a-ac4d-4cf8-a0fd-d9b88294765e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BeagleBoneBlack not booting with custom cape on

2016-05-27 Thread comondrew 
Hello,

I am using the BeagleBoneBlack (BBB) in the educational sector. For a 
project I designed a cape. It all works very nice, if I plug in the cape 
one the BBB is started. My OS is on the eMMC and I use the SD-Card rarely 
for storing files.

If I boot the BBB with the cape, it won't work. I suspect it has something 
to do with my using reserved pins for the HDMI, although I do disable them 
in the uEnv.txt.
Booting with only the Cape connected to P9 works fine.

On P8 is use the Pins: 11,14,15,16,17,19,31,32,33,34,35,7,38,45.
In Derek Molloys Chart they are marked as reserved for hdmi.

For a dump of uboot see below.

Do you have an idea how what the problem is and how I can solve it?

Thank you very much in advance!

Kind regards,

Jan

--- uboot dump ---

> =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2016.05.27 14:28:54 
> =~=~=~=~=~=~=~=~=~=~=~=
> @uiP#!…W%ZDŒ XFPF©U
>
>
> ü
>
> U-Boot 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06), Build: 
> jenkins-github_Bootloader-Builder-105
>
>Watchdog enabled
> I2C:   ready
> DRAM:  512 MiB
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Using default environment
>
> Net:not set. Validating first E-fuse MAC
>
>
> cpsw
> Hit any key to stop autoboot:  1 0 
> gpio: pin 53 (gpio 53) value is 1
> Card did not respond to voltage select!
> Card did not respond to voltage select!
> gpio: pin 56 (gpio 56) value is 0
> gpio: pin 55 (gpio 55) value is 0
> gpio: pin 54 (gpio 54) value is 0
> switch to partitions #0, OK
> mmc1(part 0) is current device
> gpio: pin 54 (gpio 54) value is 1
> Checking for: /uEnv.txt ...
> Checking for: /boot.scr ...
> Checking for: /boot/boot.scr ...
> Checking for: /boot/uEnv.txt ...
> gpio: pin 55 (gpio 55) value is 1
> 829 bytes read in 15 ms (53.7 KiB/s)
> Loaded environment from /boot/uEnv.txt
> Checking if uname_r is set in /boot/uEnv.txt...
> gpio: pin 56 (gpio 56) value is 1
> Running uname_boot ...
> loading /boot/vmlinuz-3.8.13-xenomai-r72 ...
> 5741824 bytes read in 336 ms (16.3 MiB/s)
> loading /boot/dtbs/3.8.13-xenomai-r72/am335x-boneblack.dtb ...
> 26098 bytes read in 33 ms (771.5 KiB/s)
> loading /boot/initrd.img-3.8.13-xenomai-r72 ...
> 2286742 bytes read in 148 ms (14.7 MiB/s)
> debug: [console=ttyO0,115200n8 
> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN 
> root=UUID=cf28a3f6-fcae-4d49-9887-f565a8bfbfaf ro rootfstype=ext4 rootwait 
> fixrtc quiet init=/lib/systemd/systemd] ...
> debug: [bootz 0x8200 0x8808:22e496 0x8800] ...
> Kernel image @ 0x8200 [ 0x00 - 0x579d00 ]
> ## Flattened Device Tree blob at 8800
>Booting using the fdt blob at 0x8800
>Loading Ramdisk to 8fdd1000, end 8496 ... OK
>Loading Device Tree to 8fdc7000, end 8fdd05f1 ... OK
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
> [0.359272] omap2_mbox_probe: platform not supported
> [0.565509] tps65217-bl tps65217-bl: no platform data provided
> [0.631529] bone-capemgr bone_capemgr.9: slot #0: No cape found
> [0.84] bone-capemgr bone_capemgr.9: slot #1: No cape found
> [0.701838] bone-capemgr bone_capemgr.9: slot #2: No cape found
> [0.736994] bone-capemgr bone_capemgr.9: slot #3: No cape found
> [0.757699] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' 
> failed
> [0.821243] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
> requested by 44e10800.pinmux; cannot claim for gpio-leds.8
> [0.835783] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status 
> -22
> [0.844867] pinctrl-single 44e10800.pinmux: could not request pin 21 on 
> device pinctrl-single
> [0.929572] Unable to handle kernel NULL pointer dereference at virtual 
> address 006c
> [0.940154] pgd = c0004000, hw pgd = de198000
> [0.945818] [006c] *pgd=
> [0.950483] Internal error: Oops: 5 [#1] THUMB2
> [0.956352] Modules linked in:
> [0.960314] CPU: 0Not tainted  (3.8.13-xenomai-r72 #1)
> [0.967446] PC is at inode_sb_list_add+0x14/0x34
> [0.973431] LR is at inode_sb_list_add+0xd/0x34
> [0.979305] pc : []lr : []psr: 6033
> [0.979305] sp : df06fec8  ip : c09c63c0  fp : 
> [0.994192] r10: c087f6dc  r9 :   r8 : 
> [1.000964] r7 : de99ac68  r6 : 41ed  r5 : c08caf2c  r4 : de99aad0
> [1.009428] r3 :   r2 :   r1 : de99ab90  r0 : c08caf2c
> [1.017892] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  
> Segment kernel
> [1.027594] Control: 50c5387d  Table: 9e198019  DAC: 0015
> [1.035042] Process swapper (pid: 1, stack limit = 0xdf06e238)
> [1.042605] Stack: (0xdf06fec8 to 0xdf07)
> [1.048253] fec0:    de99aad0 de999e30 c0109f7b 
> de999e30 c01d865b
> [1.058861] fee0: ac677448 0007 de996250 de999e30 01ed de99ac68 
>  0105
> [1.069470] ff00: c087f6dc c01d87d7    df06e000 
> c090bdc0 
> [1.080078] ff20: c0864531 c01d88a1

Re: [beagleboard] Re: Kernel Panic: NULL pointer dereference

2016-05-27 Thread Jan Meitner 
Sorry I cannot supply the schematic.

But I can give you the function of the Pins.
As P9 is working fine, I'll give you P8:

11: Input, theres a Button attached
14: Input, LM339 attached.
15: "
16: "
17: "
19: Output
31: Input, LM339 attached
32: Input, LM339 attached
33: Input, LM339 attached
34: Output
35: Input, LM339 attached
37: Serial Device attached
38: Serial Device attached
45: Output

Am Freitag, 27. Mai 2016 16:11:59 UTC+2 schrieb Chris Morgan:

> Can you provide a schematic for your cape?
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d7983ec5-1bf3-48c3-bb8f-a1a2b918c8a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Customize BBB-Board and add wifi module

2016-05-27 Thread DLF 
Hello

I played with this a while ago.  A lot depends on which firmware you are 
running.

http://dumb-looks-free.blogspot.fr/2015/12/beaglebone-black-bbb-uart2-with-esp8266.html

should be some other examples via google - it is not real specific to BBB 
(maybe some raspberry pi examples that could be used)

good luck

On Friday, 27 May 2016 15:12:48 UTC+2, El Smiedro wrote:
>
> Hy everyone,
>
> I would like to customize the board of the BBB and add a wifi module (f.e. 
> the esp8266) to it. Maybe someone could give me a little advice how to do 
> it or know some link to a little tutorial.
> Thank you very much for your help.
>
> best regards
> Eric
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1fb954be-6381-420a-a877-af16c3df0f77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Kernel Panic: NULL pointer dereference

2016-05-27 Thread Chris Morgan 
Can you provide a schematic for your cape?

On Fri, May 27, 2016 at 9:59 AM, Jan Meitner  wrote:

> UPDATE: Once it is started, I can reboot without a problem, as long as
> power is not cut.
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/9b14ac15-7066-4f62-9d9e-4e4f57f4e0fc%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAAPegz1igBJW3TUa%2B77d5jfdHZn1S_hT94-3LkU%3DCNywQzCtQA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Kernel Panic: NULL pointer dereference

2016-05-27 Thread Jan Meitner 
UPDATE: Once it is started, I can reboot without a problem, as long as 
power is not cut.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9b14ac15-7066-4f62-9d9e-4e4f57f4e0fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Creating an image of the debian OS with all the data that is stored in it.

2016-05-27 Thread Jan Meitner 
 *http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents* 


>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a3a9df99-0726-4aec-9d25-4a3d504304ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Creating an image of the debian OS with all the data that is stored in it.

2016-05-27 Thread Akash Gajeshwar 
Hello Everyone,

I have Debian OS running on my beaglebone with lot of scripts in it. 
What I want to do is create an image of this Debian OS  and flash it on 
other beaglebones so that they will also have same set of files.  Can 
someone please help me with this?

Thanks,
Akash 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a19098a4-e23e-4360-855d-78c055594eb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBone Black/Green SPI pins always low with 4.1.22 kernel

2016-05-27 Thread Robert Nelson 
On Fri, May 27, 2016 at 8:29 AM, Mattt C  wrote:

> Hi,
>
> I got the exact same problem. I use the DTBO BB-SPIDEV0 with linux kernel
> 4.1.15. The pinmux of SPI pins doesn't change when I load the SPI overlay.
> I tried loading I2C1, pin P9_18 change its pinmux. When I load SPIDEV0, it
> doesn't.
>

BB-SPIDEV0 needs to be loaded at bootup, not later, as it will fail if
manually loaded...

add it to /boot/uEnv.txt

cape_enable=bone_capemgr.enable_partno=BB-SPIDEV0

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYh%3DmV%2BPb48zEjy3Zqh2HN_kq_iCAZB2KCcfmdVhAWqUzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBone Black/Green SPI pins always low with 4.1.22 kernel

2016-05-27 Thread Mattt C 
Hi, 

I got the exact same problem. I use the DTBO BB-SPIDEV0 with linux kernel 
4.1.15. The pinmux of SPI pins doesn't change when I load the SPI overlay. 
I tried loading I2C1, pin P9_18 change its pinmux. When I load SPIDEV0, it 
doesn't.

Best regards.

Le vendredi 29 avril 2016 19:40:55 UTC+2, Grzesiek Stawik a écrit :
>
> Thanks, for the responses, let me clarify the problem.
>
> In 4.1.1 i have been using overlays from "
> https://github.com/RobertCNelson/bb.org-overlays"; and everything was 
> working fine for the last year or so except the power button ( i gave up on 
> this and don't remember the details, but issue was something about the 
> power button device in /dev/ or /sys missing, and acpid not receiving any 
> signal from the button )
>
> so i have working system with 4.1.1 ( except the power button, which is a 
> minor issue ).
>
>
>
> i have recently upgraded, ONLY the kernel ( and modules, and firmware ) to 
> 4.1.22, ( also later updated overlays from bb.org-overlays ) and now the 
> power button works fine, but /dev/spidevX.X is dead.
>
> *if i simply boot the old kernel, spidev comes back to life*.
>
> again, from the system's point of view, on 4.1.22 everything is fine, 
> spidev exists and i can use it, however no electrons are present on the 
> physical spi pins.
>
>
> Other overlays from bb.org-overlays are working fine on 4.1.22
>
>
> Best Regards.
>
>
>
>
> 2016-04-29 18:40 GMT+02:00 Robert Nelson  >:
>
>>
>>
>> On Fri, Apr 29, 2016 at 11:08 AM, Grzesiek Stawik > > wrote:
>>
>>> So i had this other issue where the power button would not trigger 
>>> poweroff, and from time to time i try new kernel versions to see if it 
>>> works, and i have recently switched to 4.1.22 because it does work there.
>>>
>>> But.
>>>
>>> Strange things happen with SPI in 4.1.22, spidev is now created as 
>>> /dev/spidev2.X instead /dev/spidev1.X, or, when using "cape-universal" 
>>> overlay, i get both /dev/spidev1.X and /dev/spidev2.X but none of them are 
>>> working.
>>>
>>
>> "cape-universal" just enables the peripheral out of the box..
>>
>> When using it, you need to use "config-pin" to mux the pin's utilized..
>>
>> Here is the readme:
>>
>>
>> https://github.com/cdsteinkuehler/beaglebone-universal-io/blob/master/README.md
>>
>> the 'overlay' is already loaded by default.. you just need to use 
>> config-pin to setup the spidev pin's..
>>
>> Regards,
>>
>> -- 
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/beagleboard/QiFPB9HjL4Y/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> beagleboard...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYjrj9NUz7bD%3D6ASAy%2BUvijyRbRbjadeY0P0Xmq34TL4-g%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/87eb3257-e14a-4e2e-9bee-c7bd9ad22a3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Kernel Panic: NULL pointer dereference

2016-05-27 Thread comondrew 
Hello,

I do have a Problem booting my BeagleBone with a custom cape on. I already 
double checked my layout, i did not use any pins marked with mmc1 in the 
pintables of the system reference manual.

It will not boot if the cape is on. If I just plug in P9-Capeheader, it 
does boot. If I plug in the cape when the bone is up, it works.

For my PinOut I used 
http://exploringbeaglebone.com/wp-content/uploads/resources/BBBP8Header.pdf  
from Derek Molloy and I didn't touch any of the marked pins but those 
"allocated for HDMI". I suppose the Problem might be there, though I 
disable the HDMI in the uEnv.txt.

On P8 I use the following Pins:
11,14,15,16,17,19,31,32,33,34,35,37,38,45

Here's the dump of a Startup with the cape on:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2016.05.27 14:28:54 
> =~=~=~=~=~=~=~=~=~=~=~=
> @uiP#!…W%ZDŒ XFPF©U
>
>
> ü
>
> U-Boot 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06), Build: 
> jenkins-github_Bootloader-Builder-105
>
>Watchdog enabled
> I2C:   ready
> DRAM:  512 MiB
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Using default environment
>
> Net:not set. Validating first E-fuse MAC
>
>
> cpsw
> Hit any key to stop autoboot:  1 0 
> gpio: pin 53 (gpio 53) value is 1
> Card did not respond to voltage select!
> Card did not respond to voltage select!
> gpio: pin 56 (gpio 56) value is 0
> gpio: pin 55 (gpio 55) value is 0
> gpio: pin 54 (gpio 54) value is 0
> switch to partitions #0, OK
> mmc1(part 0) is current device
> gpio: pin 54 (gpio 54) value is 1
> Checking for: /uEnv.txt ...
> Checking for: /boot.scr ...
> Checking for: /boot/boot.scr ...
> Checking for: /boot/uEnv.txt ...
> gpio: pin 55 (gpio 55) value is 1
> 829 bytes read in 15 ms (53.7 KiB/s)
> Loaded environment from /boot/uEnv.txt
> Checking if uname_r is set in /boot/uEnv.txt...
> gpio: pin 56 (gpio 56) value is 1
> Running uname_boot ...
> loading /boot/vmlinuz-3.8.13-xenomai-r72 ...
> 5741824 bytes read in 336 ms (16.3 MiB/s)
> loading /boot/dtbs/3.8.13-xenomai-r72/am335x-boneblack.dtb ...
> 26098 bytes read in 33 ms (771.5 KiB/s)
> loading /boot/initrd.img-3.8.13-xenomai-r72 ...
> 2286742 bytes read in 148 ms (14.7 MiB/s)
> debug: [console=ttyO0,115200n8 
> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN 
> root=UUID=cf28a3f6-fcae-4d49-9887-f565a8bfbfaf ro rootfstype=ext4 rootwait 
> fixrtc quiet init=/lib/systemd/systemd] ...
> debug: [bootz 0x8200 0x8808:22e496 0x8800] ...
> Kernel image @ 0x8200 [ 0x00 - 0x579d00 ]
> ## Flattened Device Tree blob at 8800
>Booting using the fdt blob at 0x8800
>Loading Ramdisk to 8fdd1000, end 8496 ... OK
>Loading Device Tree to 8fdc7000, end 8fdd05f1 ... OK
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
> [0.359272] omap2_mbox_probe: platform not supported
> [0.565509] tps65217-bl tps65217-bl: no platform data provided
> [0.631529] bone-capemgr bone_capemgr.9: slot #0: No cape found
> [0.84] bone-capemgr bone_capemgr.9: slot #1: No cape found
> [0.701838] bone-capemgr bone_capemgr.9: slot #2: No cape found
> [0.736994] bone-capemgr bone_capemgr.9: slot #3: No cape found
> [0.757699] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' 
> failed
> [0.821243] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
> requested by 44e10800.pinmux; cannot claim for gpio-leds.8
> [0.835783] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status 
> -22
> [0.844867] pinctrl-single 44e10800.pinmux: could not request pin 21 on 
> device pinctrl-single
> [0.929572] Unable to handle kernel NULL pointer dereference at virtual 
> address 006c
> [0.940154] pgd = c0004000, hw pgd = de198000
> [0.945818] [006c] *pgd=
> [0.950483] Internal error: Oops: 5 [#1] THUMB2
> [0.956352] Modules linked in:
> [0.960314] CPU: 0Not tainted  (3.8.13-xenomai-r72 #1)
> [0.967446] PC is at inode_sb_list_add+0x14/0x34
> [0.973431] LR is at inode_sb_list_add+0xd/0x34
> [0.979305] pc : []lr : []psr: 6033
> [0.979305] sp : df06fec8  ip : c09c63c0  fp : 
> [0.994192] r10: c087f6dc  r9 :   r8 : 
> [1.000964] r7 : de99ac68  r6 : 41ed  r5 : c08caf2c  r4 : de99aad0
> [1.009428] r3 :   r2 :   r1 : de99ab90  r0 : c08caf2c
> [1.017892] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  
> Segment kernel
> [1.027594] Control: 50c5387d  Table: 9e198019  DAC: 0015
> [1.035042] Process swapper (pid: 1, stack limit = 0xdf06e238)
> [1.042605] Stack: (0xdf06fec8 to 0xdf07)
> [1.048253] fec0:    de99aad0 de999e30 c0109f7b 
> de999e30 c01d865b
> [1.058861] fee0: ac677448 0007 de996250 de999e30 01ed de99ac68 
>  0105
> [1.069470] ff00: c087f6dc c01d87d7    df06e000 
> c090bdc0 
> [1.080078] ff20: c0864531 c01d88a1  c09d38b0 c09d38b0 c0864549 
>

[beagleboard] Customize BBB-Board and add wifi module

2016-05-27 Thread ericschmieder87 via BeagleBoard 
Hy everyone,

I would like to customize the board of the BBB and add a wifi module (f.e. 
the esp8266) to it. Maybe someone could give me a little advice how to do 
it or know some link to a little tutorial.
Thank you very much for your help.

best regards
Eric

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/79d85818-1767-4940-82a9-7d5b9f8b9005%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Unable to ssh into Beaglebone Black from Arch Linux

2016-05-27 Thread vmt . eiz 


I have a Beaglebone Black (running on Debian) which I'm connecting to my 
laptop (running on Arch Linux) through usb. The laptop is able to read 
Beaglebone as a storage device. However, I am unable to connect to 
Beaglebone through the browser/ssh by accessing the following ip - 
192.168.7.2. 


ifconfig -a gives the following output-


enp0s20u2: flags=4098  mtu 1500
ether 54:4a:16:c1:f1:53  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp1s0: flags=4163  mtu 1500
inet 192.168.3.204  netmask 255.255.255.0  broadcast 192.168.3.255
inet6 fe80::2ad2:44ff:fe8e:bd61  prefixlen 64  scopeid 0x20
ether 28:d2:44:8e:bd:61  txqueuelen 1000  (Ethernet)
RX packets 40024  bytes 35440467 (33.7 MiB)
RX errors 0  dropped 30  overruns 0  frame 0
TX packets 17546  bytes 2112866 (2.0 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 0  (Local Loopback)
RX packets 2137  bytes 479657 (468.4 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2137  bytes 479657 (468.4 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp2s0: flags=4163  mtu 1500
inet 10.10.5.86  netmask 255.255.252.0  broadcast 10.10.7.255
ether b8:ee:65:ac:7c:65  txqueuelen 1000  (Ethernet)
RX packets 19264  bytes 18721516 (17.8 MiB)
RX errors 0  dropped 4  overruns 0  frame 0
TX packets 17238  bytes 2273813 (2.1 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



enp0s20u2 is the interface of Beaglebone and has no ip allotted to it (as 
per the documentation, its ip should be 192.168.7.2) and thus I am unable 
to ssh or browse into it.


Kindly help.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e6e5ff09-9ff5-4b7c-b79a-dfc449f4bb2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Board-customization

2016-05-27 Thread 'El Smiedro' via BeagleBoard 
  Hello everyone,

I would like to customize the board of the BBB to add a wifi module (f.e. 
the esp8622). Did someone know a little tutorial or could give a little 
advice how to do that?
Thanks very much for your help.

best regards
Eric

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2e590f4c-4d28-40d5-9cd3-2f0691e2bc69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBB, how to install chipsee 7inch screen and gfx driver with lastet debian image?

2016-05-27 Thread yolcopc 
Taking advantage of the thread, I would like to make a question in 
reference to both, Chipsee TFT & BBB.

@Damian, does your system work fine just installed? 
I have followed the instructions wrote here (except the SGX ones, by the 
moment I'm not going further), but the touch panel does not work well even 
after calibration. It only works in a half-part of the screen.
What kernel are you working with? How did you calibrate the screen? Could 
you share the calibration file (/etc/pointercal.xinput.EP0790M09), please?

* Also, does the speaker works for you? This is another issue I have, audio 
works well through headphones, but the speaker.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ef062d71-4692-48a7-86ac-081f37911f35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone Debian OS

2016-05-27 Thread Andrey Somov 
I had the same problem with the latest builds.

This did not work either: "serial cable hooked to the serial command line 
port" 

Just downgrade to  Debian 7.8 (BeagleBone, BeagleBone Black - 4GB SD) 
2015-03-01 - more info - md5: c848627722b7a5f7bc89791cc8949e3b 
It works like a charm...
(https://debian.beagleboard.org/images/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz)

Cheers,
Andrey


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/117c1dd6-7387-46b0-b9c2-bc3ff9c7c937%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Unable to ssh into Beaglebone Black from Arch Linux

2016-05-27 Thread Akshat Tripathi 
I have a Beaglebone Black (running on Debian) which I'm connecting to my 
laptop (running on Arch Linux) through usb. The laptop is able to read 
Beaglebone as a storage device. However, I am unable to connect to 
Beaglebone through the browser/ssh by accessing the following ip - 
192.168.7.2. ifconfig -a gives the following output-

enp0s20u2: flags=4163  mtu 1500
inet6 fe80::564a:16ff:fec1:f153  prefixlen 64  scopeid 0x20
ether 54:4a:16:c1:f1:53  txqueuelen 1000  (Ethernet)
RX packets 23  bytes 4576 (4.4 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 8  bytes 1000 (1000.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp1s0: flags=4163  mtu 1500
inet 192.168.3.204  netmask 255.255.255.0  broadcast 192.168.3.255
inet6 fe80::2ad2:44ff:fe8e:bd61  prefixlen 64  scopeid 0x20
ether 28:d2:44:8e:bd:61  txqueuelen 1000  (Ethernet)
RX packets 51924  bytes 41955346 (40.0 MiB)
RX errors 0  dropped 30  overruns 0  frame 0
TX packets 23194  bytes 2903139 (2.7 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 0  (Local Loopback)
RX packets 2360  bytes 554625 (541.6 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2360  bytes 554625 (541.6 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp2s0: flags=4163  mtu 1500
inet 10.10.5.86  netmask 255.255.252.0  broadcast 10.10.7.255
ether b8:ee:65:ac:7c:65  txqueuelen 1000  (Ethernet)
RX packets 19289  bytes 18724799 (17.8 MiB)
RX errors 0  dropped 20  overruns 0  frame 0
TX packets 17241  bytes 2274086 (2.1 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp0s20u2 is the interface of Beaglebone and has no ip allotted to it (as 
per the documentation, its ip should be 192.168.7.2) and thus I am unable 
to ssh or browse into it.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/856632ed-7050-473a-9384-34bc7d3842ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] dd between boards

2016-05-27 Thread Antoine Rennuit 
Your link was an interesting reading, 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/cf01c40f-69fa-43c3-9710-03bac9c4a19d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.