Bug, or conflict with kernels 4.x and universal IO

118 views
Skip to first unread message

William Hermans

unread,
Jan 9, 2017, 5:05:05 PM1/9/17
to BeagleBoard
So this is probably more of an oversight than a bug. But when loading *some* overlays via config-pin overlay <overlay>, *AFTER* already having loaded an overlay through /boot/uEnv.txt. At least one pin will still continue function correctly( electrically ) but the file that indicates the actual value of the pin will not update correctly. As an GPI( input ). Which has nothing to do with a conflict in overlays, as I have a custom overlay that initializes several GPIO pins, as well as a few PWM pins. Plus I am loading  BB-ADC-00A0.dtbo, and BB-W1-P8.26-00A0.dtbo, Where BB-W1-P8.26-00A0.dtbo is an adaption of the stock overlay BB-W1-P9.12-00A0.dtbo.

None of the above overlays describe, or use any of the same pins. So there can not be a conflict between overlays in that regard.

The fix I found for this problem, was to load all the overlays through /boot/uEnv.txt. Through cape_enable=bone_capemgr.enable_partno=

The pin in question that we're having issues with is P8.16. Which if memory serves me correctly is also tied to another processor pad/pin through a zero ohm resistor.

Before, all the GPI's would read correctly through the value file using a shell script. While this one pin would always read 0. Now, the pin value file works correctly.

@Robert,

Has the ability to load  multiple overlays through uboot been implemented yet ?

William Hermans

unread,
Jan 9, 2017, 5:09:25 PM1/9/17
to beagl...@googlegroups.com
I should also add, that I have only tested this "fix" on a beaglebone green. I seem to recall that this problem does not exist when using a beaglebone black.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/0dc4c9de-50d2-4d76-aacd-0bb3943ea467%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Robert Nelson

unread,
Jan 9, 2017, 5:13:12 PM1/9/17
to Beagle Board
Use this in /boot/uEnv.txt

enable_uboot_overlays=1
uboot_overlay_addr0=/lib/firmware/BB-CAPE-1-00A0.dtbo
uboot_overlay_addr1=/lib/firmware/BB-CAPE-2-00A0.dtbo
uboot_overlay_addr2=/lib/firmware/BB-CAPE-3-00A0.dtbo
uboot_overlay_addr3=/lib/firmware/BB-CAPE-4-00A0.dtbo
dtb_overlay=/lib/firmware/BB-CAPE-5-00A0.dtbo

Regards,

--
Robert Nelson
https://rcn-ee.com/

William Hermans

unread,
Jan 9, 2017, 5:17:43 PM1/9/17
to beagl...@googlegroups.com

On Mon, Jan 9, 2017 at 3:12 PM, Robert Nelson <robert...@gmail.com> wrote:

Use this in /boot/uEnv.txt

enable_uboot_overlays=1
uboot_overlay_addr0=/lib/firmware/BB-CAPE-1-00A0.dtbo
uboot_overlay_addr1=/lib/firmware/BB-CAPE-2-00A0.dtbo
uboot_overlay_addr2=/lib/firmware/BB-CAPE-3-00A0.dtbo
uboot_overlay_addr3=/lib/firmware/BB-CAPE-4-00A0.dtbo
dtb_overlay=/lib/firmware/BB-CAPE-5-00A0.dtbo

Regards,

--
Robert Nelson
https://rcn-ee.com/


Awesome, thanks Robert.

aroc...@yahoo.com

unread,
Jan 10, 2017, 12:13:21 PM1/10/17
to beagl...@googlegroups.com

--------------------------------------------
On Tue, 1/10/17, William Hermans <yyr...@gmail.com> wrote:

Subject: Re: [beagleboard] Bug, or conflict with kernels 4.x and universal IO
To: beagl...@googlegroups.com
Date: Tuesday, January 10, 2017, 12:17 AM
--

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/CALHSORoHce1zAVdy-HO5ErvxPQhcLcYz%2BZCeSd87P3VJ7irKkg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.
ultura de mase. Trasaturi generale. Din punct de vedere cultural perioada din istoria Romaniei care debuteaza dupa infaptuirea Marii Uniri din 1918 si se incheie o data cu instalarea regimului comunist a reprezentat un apogeu pregatit de desfasurarile anterioare din intreaga epoca moderna. Desigur generatia marilor clasici Eminescu Creanga Caragiale isi incheiase activitatea dar acum ia nastere un veritabil al doilea clasicism demn de acest nume prin caracterul stabil durabil al valorilor spirituale pe care Ie-a generat nicidecum insa prin optiunea stilistica deloc omogena cateodata de-a dreptul modernista. Totusi chiar daca in constiinta publica se incetatenesc cu precadere valorile de varf aceasta perioada istorica poate fi in mod la fel de justificat caracterizata ca momentul de explozie a culturii de difuzare a ei in toate mediile sociale in care societatea romaneasca isi edifica - fara sa o numeasca astfel si fara nici o nuanta propagandistica - o adevarata cultura de mase care stimuleaza si antreneaza forte creatoare de diverse marimi nu doar superlativele care constituie partea vizibila a icebergului cultural romanesc. Aparitia acestui fenomen isi afla suficiente argumente in plan istoric dar si in domeniul psihologiei sociale. Istoric el a fost pregatit de perioada precedenta in care notam obligativitatea invatamantului primar miscarea culturala la sate avandu-i ca principali agenti pe invatatorii din mediul rural stimulati de initiativele lui Spiru Haret iar in Transilvania activitatea Astrei care de asemenea viza totalitatea romanilor indiferent de provenienta sociala sau gradul de instructie. Deloc neglijabila in generarea acestui fenomen de patrundere a culturii in toate straturile societatii cu forme specifice este si activitatea unui mare numar de asociatii si societati culturale cauza dar in acelasi timp si efect al tot mai largului interes pentru cultura. Abundenta presei de tot felul de la efemere aparitii de gazete locale uneori doar cu caracter ocazional pana la marile cotidiene citite in intreaga tara.

roberts...@yahoo.com

unread,
Jan 10, 2017, 2:03:27 PM1/10/17
to beagl...@googlegroups.com

--------------------------------------------
On Tue, 1/10/17, arochagus via BeagleBoard <beagl...@googlegroups.com> wrote:

Subject: Re: [beagleboard] Bug, or conflict with kernels 4.x and universal IO
To: beagl...@googlegroups.com
Date: Tuesday, January 10, 2017, 6:15 PM
https://groups.google.com/d/msgid/beagleboard/1359003576.348641.1484064945791%40mail.yahoo.com.
For more options, visit
https://groups.google.com/d/optout.selor lor politice. Pentru imbunatatirea situatiei taranimii conservatorii

caseyro...@yahoo.com

unread,
Jan 10, 2017, 8:33:14 PM1/10/17
to beagl...@googlegroups.com

--------------------------------------------
On Tue, 1/10/17, robertsmaria934 via BeagleBoard <beagl...@googlegroups.com> wrote:

Subject: Re: [beagleboard] Bug, or conflict with kernels 4.x and universal IO
To: beagl...@googlegroups.com
Date: Tuesday, January 10, 2017, 9:03 PM
https://groups.google.com/d/msgid/beagleboard/1864479383.497229.1484074999311%40mail.yahoo.com.
For more options, visit
https://groups.google.com/d/optout. vasta activitate politica s-a desfasurat in jurul modificam Constitutiei din '6 in 1884 desi numarul colegiilor electorale a fost redus la trei s-a mentinut ii cenzitar in acelasi an s-a votat legea Domeniilor Regale prin care regele imilia sa au fost inzestrati cu 12 proprietati care aveau suprafata de 118 286 tare teren arabil si paduri in 1885 Biserica Ortodoxa Romana si-a proclamat ocefalia fata de Patriarhia ecumenica de la Constantinopol fapt cu implicatii itive asupra suveranitatii nationale

Ross Morrison

unread,
Jan 11, 2017, 4:15:51 PM1/11/17
to beagl...@googlegroups.com
Hello all,

Simple question, hope there is a simple answer. After some googling,
I've been unable to discover how and when the ipv4 address for
interface SoftAp0 is set. I would like to change the address from
192.168.8.1 to some other private ipv4 address, ie 192.168.200.1 or
whatever, just something other than 8.1. Part two of that question is
what would break if the change is made?

I know how to keep /etc/dnsmasq.d/SoftAp0 static and modify
the ip values for issuing to clients, just need to know how to get
SoftAp0's base ip changed.

Beaglebone Green Wireless with image:
BeagleBoard.org Debian Image 2017-01-08

Thanks,
Ross

Ross Morrison

unread,
Jan 11, 2017, 4:18:40 PM1/11/17
to beagl...@googlegroups.com
Oops, forgot the subject...

Laurel Watts - NOAA Affiliate

unread,
Jan 11, 2017, 4:21:03 PM1/11/17
to beagl...@googlegroups.com
It is very easy, just edit /etc/network/interfaces.

Laurel

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/20170111131537.280b61b5%40kubuntu-14-04.

Robert Nelson

unread,
Jan 11, 2017, 4:24:16 PM1/11/17
to Beagle Board, ro...@buy-ei.com
On Wed, Jan 11, 2017 at 3:18 PM, Ross Morrison <ro...@buy-ei.com> wrote:
> On Wed, 11 Jan 2017 13:15:37 -0800
> Ross Morrison <ro...@buy-ei.com> wrote:
>
>> Hello all,
>>
>> Simple question, hope there is a simple answer. After some googling,
>> I've been unable to discover how and when the ipv4 address for
>> interface SoftAp0 is set. I would like to change the address from
>> 192.168.8.1 to some other private ipv4 address, ie 192.168.200.1 or
>> whatever, just something other than 8.1. Part two of that question is
>> what would break if the change is made?

So, you can define this in:

ip_prefix="192.168.8"

/usr/bin/bb-wl18xx-tether

https://github.com/rcn-ee/repos/blob/master/bb-wl18xx-firmware/suite/jessie/debian/bb-wl18xx-tether#L26

But i really should move this to:

/etc/default/bb-wl18xx

Careful around:

https://github.com/rcn-ee/repos/blob/0161650aa1e1da854425144c9d50d2d774a6f6e6/bb-wl18xx-firmware/suite/jessie/debian/bb-wl18xx-tether#L286-L291

as i hard-coded that to 192.168.8.x

I'll fix those both up right now..

Ross Morrison

unread,
Jan 11, 2017, 4:32:25 PM1/11/17
to beagl...@googlegroups.com
That works, thanks Robert....

Ross

Robert Nelson

unread,
Jan 11, 2017, 4:35:27 PM1/11/17
to Beagle Board
Pushed out:

https://github.com/rcn-ee/repos/commit/d8253954216fe6aa3baf43cb4580ca4542bded55

It's now building, should hit apt repo in a half hour or so...

William Hermans

unread,
Jan 16, 2017, 5:47:51 AM1/16/17
to beagl...@googlegroups.com
Robert,

So, I got around to updating to the latest bootloader this morning, and, well something went wrong. not sure exactly what yet. But here is the serial debug output. For some reason it can't seem to find a valid boot partition ?

http://pastebin.com/tUqkDvef

Robert Nelson

unread,
Jan 16, 2017, 12:07:08 PM1/16/17
to Beagle Board
On Mon, Jan 16, 2017 at 4:47 AM, William Hermans <yyr...@gmail.com> wrote:
> Robert,
>
> So, I got around to updating to the latest bootloader this morning, and,
> well something went wrong. not sure exactly what yet. But here is the serial
> debug output. For some reason it can't seem to find a valid boot partition ?
>
> http://pastebin.com/tUqkDvef

the issue is 4.4.9-bone-rt-r10...

grab 4.4.39-bone-rt-r16 or later, which includes a dtc resync:

https://github.com/RobertCNelson/bb-kernel/blob/722d8ee587bc6573c01136ef18dc14d0de903f46/patches/dtc/0001-scripts-dtc-Update-to-upstream-version-overlays.patch

as that fixes:
libfdt fdt_check_header(): FDT_ERR_BADMAGIC

and:
debug: [bootz 0x82000000 0x88080000:48b75f 88000000] ...
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree

William Hermans

unread,
Jan 16, 2017, 2:20:06 PM1/16/17
to beagl...@googlegroups.com

On Mon, Jan 16, 2017 at 10:06 AM, Robert Nelson <robert...@gmail.com> wrote:
the issue is 4.4.9-bone-rt-r10...

grab 4.4.39-bone-rt-r16 or later, which includes a dtc resync:

https://github.com/RobertCNelson/bb-kernel/blob/722d8ee587bc6573c01136ef18dc14d0de903f46/patches/dtc/0001-scripts-dtc-Update-to-upstream-version-overlays.patch

as that fixes:
libfdt fdt_check_header(): FDT_ERR_BADMAGIC

and:
debug: [bootz 0x82000000 0x88080000:48b75f 88000000] ...
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree

Regards,

--
Robert Nelson
https://rcn-ee.com/


D'oh . . .Ok, was sure it was my fault, and it was. Way too early of a kernel, and I did not even think about that.

After an apt-get update . . .
root@beaglebone:~# apt-cache search linux-image |grep 4.4.39-bone
linux-image-4.4.39-bone-rt-r14 - Linux kernel, version 4.4.39-bone-rt-r14
linux-image-4.4.39-bone-rt-r15 - Linux kernel, version 4.4.39-bone-rt-r15
linux-image-4.4.39-bone14 - Linux kernel, version 4.4.39-bone14
linux-image-4.4.39-bone15 - Linux kernel, version 4.4.39-bone15


What am I missing ?

Robert Nelson

unread,
Jan 16, 2017, 2:47:01 PM1/16/17
to Beagle Board
of course my dtc update alone wasn't built-able..

Grab the next release, where i fixed the dtc build errors...

linux-image-4.4.41-bone-rt-r16

William Hermans

unread,
Jan 16, 2017, 3:59:29 PM1/16/17
to beagl...@googlegroups.com
Thanks Robert. The odd thing, when I do a std apt-cache search linux-image |grep bone. I don't see those versions, or they're ordered out of sequence, and I just look in the wrong place I guess. So in context of 4.4.x, the kernel I pulled in "seemed" to be the newest. *shrug*

--
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+unsubscribe@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages