pins conflict?

GoogleGroups
1

Hi,

I use custom hat board with my old BBB on P9 headers.

I would like use the same hat board with my new BBGW.
However i see in the dmesg pins conflict:

`

[ 2.131373] pinctrl-single 44e10800.pinmux: pin PIN109 already requested by 44e10800.pinmux; cannot claim for ocp:P9_41_pinmux
[ 2.714948] pinctrl-single 44e10800.pinmux: pin PIN86 already requested by ocp:P9_18_pinmux; cannot claim for 4802a000.i2c
[ 63.810571] pinctrl-single 44e10800.pinmux: pin PIN106 already requested by ocp:P9_91_pinmux; cannot claim for 48038000.mcasp
[ 67.662623] pinctrl-single 44e10800.pinmux: pin PIN18 already requested by ocp:P9_14_pinmux; cannot claim for sound

`

It seems like BBB and BBGW pinout is not compatible. I suspect that maybe two Grove connectors (I2C and UART) occupy the old pins?
If so how could I switch off these Grove connectors so BBGW pinout would be the same as BBB?

Regards,

2

Today all images boot with cape-univeral enabled, so if your overlay
needs specific pins, you need to tell it to disable them..

Or jsut disable:

enable_uboot_cape_universal=1

in /boot/uEnv.txt

If that still doesn't fix your problem, please run this script and
report it's output so we can help debug..

sudo /opt/scripts/tools/version.sh

Regards,

3

Thanks for prompt replay.
I’ve commented out the line ‘enable_uboot_cape_universal=1’ in /boot/uEnv.txt
and after reboot the old hat board works with BBGW.
However on-board wifi stops working.
How to enable wifi?
see details (dmesg and output of script):
https://paste.ubuntu.com/p/c7DHbwphDC/

Regards,

W dniu środa, 24 czerwca 2020 22:23:23 UTC+2 użytkownik RobertCNelson napisał:

4

Hi,
Is there any way to enable BBGW’s onboard wifi with disable uboot cape universal (with commented line ‘#enable_uboot_cape_universal=1’ in /boot/uEnv.txt )?