AM3352: AM335x Beaglebone - BBONE-GATEWAY-CAPE Installation Process Guidance

[chris....@gmail.com]

Beaglebone Friends and Family, Robert;

We would like assistance in getting the BBONE-GATEWAY-CAPE running properly. As is known, there were some design trade-offs on this particular cape that resulted in it not being granted 100% BeagleBoard.org support, but it is understood that the beagle community may have it working with recent images.

Several previous threads talk to this topic such as this one here:

Linux/BEAGLEBK: using beaglebone black with on board eMMC flash and element 14 wirelss cape
TI E2E Community


Still, the underlying question is : what exactly needs to be done to enable the wireless cape? The readme instructions are either not correct or not enough explanation for some users to make the changes needed to enable it. Following the steps in the Readme have not been able to enable it to get it up and running. First apparent problem is the root password. This is not accepted - says access denied. Users are still sometime able to get in by SSH/PuTTY and use the username Debian and password temppwd. Some have tried setting a root password with sudo but after a restart root still won't often work - therefore does the beagle community have the documentation reflecting the actual experience for this particular cape?

Comments welcomed and apprecicase? Thanks so much!

TY,
Chris

[Robert Nelson]

Hi Chris,

Sorry forgot to dig in my collection of capes at home, can you please
run this script:

sudo /opt/scripts/tools/version.sh

Then i'll dig for that cape tonight and see what it takes..

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

[drhun...@gmail.com]

Chris,

I've used the E14 cape on multiple customer projects. They have been both debian based and TI SDK based. From memory its just been a case of picking up the correct dtb file in u-boot. I've never touch the CC device on it though as I've just needed Wi-Fi and/or Bluetooth.

I can't imagine how the cape would affect the ability to log in. To me that would be an unrelated problem in the filesystem such as root being disabled.

Are there more details on cape related problems they are facing?

Iain

ia...@hunterembedded.co.uk

[Chris Yorkey]

Robert,

I thank you very much for any insight you can provide.  For now, here are some comments.

Thanks again,

Chris

-----

They can't apparently run the BB with the cape installed.  Once attached it fails to boot.  It is the WL1837MOD board.  There is also a mention that to run it, it must not run from the eMMC BB flash, it must be run from an SD card.  They have tried this also.  It also states that to force the BB to boot from the SD card , must press the S2 button on power up to force booting from SD and not eMMC.  However, it seems that whenever there is a SD present it boots to it (not 100% sure of this but think it's the case).  We just need to know how to edit the boot file. 

 

Comments are:

" set: 

 

disable_uboot_overlay_emmc=1

uboot_overlay_addr0=/lib/firmware/BB-GATEWAY-WL1837-00A0.dtbo

 

in /boot/uEnv.txt"

 

There is a line: "#disable_uboot_overlay_emmc=1"

Uncomment this line?  Seems like the step needed here.

Next, there is: "#uboot_overlay_addr0=/lib/firmware/<file0>.dtbo"

Uncomment and modify to be the above line?  This seems to be what to do here also.

Then boot to SD card while holding S2 after saving this?

Does the line enable_uboot_overlays=1 stay as is?

They will try this and get back either way. 

 

[Chris Yorkey]

Robert,

I spoke a little too soon; some progress being made...Chris.

-----

Currently booted with cape in place!  Here are the results of the version.sh…

 

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh

[sudo] password for debian:

git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]

eeprom:[A335BNLT00C04718BBBK0AC1]

model:[TI_AM335x_BeagleBone_Black]

dogtag:[BeagleBoard.org Debian Image 2018-10-07]

bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.09-00002-g0b54a51eee]:[location: dd MBR]

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.09-00002-g0b54a51eee]:[location: dd MBR]

kernel:[4.14.71-ti-r80]

nodejs:[v6.14.4]

pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]

pkg:[bb-cape-overlays]:[4.4.20180928.0-0rcnee0~stretch+20180928]

pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]

pkg:[kmod]:[23-2rcnee1~stretch+20171005]

pkg:[librobotcontrol]:[1.0.3-git20181005.0-0rcnee0~stretch+20181005]

pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]

groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep admin spi tisdk weston-launch xenomai]

cmdline:[console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet]

dmesg | grep pinctrl-single

[    1.027032] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568

dmesg | grep gpio-of-helper

[    1.028615] gpio-of-helper ocp:cape-universal: ready

END

 

When they follow the next step of commands in the BB-Gateway-cape readme the tether wifi disable results in:

 

debian@beaglebone:~$ sudo connmanctl

connmanctl>

connmanctl> tether wifi disable

Error disabling wifi tethering: Method "SetProperty" with signature "sv" on interface "net.connman.Technology" doesn't exist

 

Thanks again for any help!

[Robert Nelson]

On Tue, Jan 29, 2019 at 2:28 PM Chris Yorkey <chris....@gmail.com> wrote:
>
> Robert and BB Community,
>
> While some ignition has been started (Currently booted with cape in place) they still cannot successfully tether/run wifi.
>
> Any additional guidance or comments would be most appreciated!

Sorry i had no luck finding my board last night, it's somewhere in my
boxes of parts.

I did find an old email thou, for the moment let's disable all the
external overlays, in /boot/uEnv.txt set these 4 options:

disable_uboot_overlay_emmc=1
disable_uboot_overlay_video=1
#enable_uboot_cape_universal=1
uboot_overlay_addr0=/lib/firmware/BB-GATEWAY-WL1837-00A0.dtbo

[Robert Nelson]

On Tue, Jan 29, 2019 at 4:04 PM Chris Yorkey <chris....@gmail.com> wrote:
>
> Boots, but when they try to do the connmanctl> tether wifi disable command they get the same error message as before.
>
> Is there something else they should try instead of that?

We haven't had tether enabled thru connman for awhile now.

dmesg | grep wl
journalctl | grep wl18

Then in connmanctl

connmanctl> enable wifi
connmanctl> scan wifi
connmanctl> services

[Chris Yorkey]

Robert and BB Community,

While some ignition has been started (Currently booted with cape in place) they still cannot successfully tether/run wifi.

Any additional guidance or comments would be most appreciated!

Thank you,
Chris

[Chris Yorkey]

Boots, but when they try to do the connmanctl> tether wifi disable command they get the same error message as before.

 

Is there something else they should try instead of that?

 

Thanks

 

[Chris Yorkey]

Robert,

Thank you.  Bit by bit progress being made but here is the latest update:

Here are the results:

 

dmesg | grep wl
journalctl | grep wl18

Then in connmanctl

connmanctl> enable wifi

 

They get:

 

Error wifi: Method "SetProperty" with signature "sv" on interfaces "net.connman.Technology" doesn't exist

Thanks for your continued guidance.

Regards,

Chris

[chicag...@gmail.com]

Anyone ever get the  BBONE-GATEWAY-CAPE to work ?

I am having much the same uphill fight with no results. 

On Thursday, January 31, 2019 at 4:37:19 PM UTC-6, Chris Yorkey wrote:

Robert,

Thank you.  Bit by bit progress being made but here is the latest update:

Here are the results:

 

dmesg | grep wl
journalctl | grep wl18

Then in connmanctl

connmanctl> enable wifi

 

They get:

 

Error wifi: Method "SetProperty" with signature "sv" on interfaces "net.connman.Technology" doesn't exist

Thanks for your continued guidance.

Regards,

Chris

On Tue, Jan 29, 2019 at 5:09 PM Robert Nelson <robert...@gmail.com> wrote:

[ano T]

This is what happens when the cape seems to be working

Anyone know what this means? Seems like the CPU is deadlocked. 

 

[   53.603501] INFO: rcu_preempt detected stalls on CP

Us/tasks:

[   53.609223]  (detected by 0, t=5252 jiffies, g=3312, c=3311, q=0)

[   53.615356] All QSes seen, last rcu_preempt kthread activity 5251 (-61599--66

850), jiffies_till_next_fqs=1, root ->qsmask 0x0

[   53.627625] rcu_preempt kthread starved for 5251 jiffies! g3312 c3311 f0x2 RC

U_GP_WAIT_FQS(3) ->state=0x0 ->cpu=0

[  116.623503] INFO: rcu_preempt detected stalls on CPUs/tasks:

[  116.629223]  (detected by 0, t=21007 jiffies, g=3312, c=3311, q=0)

[  116.635442] All QSes seen, last rcu_preempt kthread activity 21006 (-45844--6

6850), jiffies_till_next_fqs=1, root ->qsmask 0x0

[  116.647950] rcu_preempt kthread starved for 21006 jiffies! g3312 c3311 f0x2 R

CU_GP_WAIT_FQS(3) ->state=0x0 ->cpu=0

--
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/wJEfFX20liA/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/cd7d9e75-dd99-4893-ae35-4cecc4032df3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.