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

GoogleGroups
1

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

2

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,

3

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

iain@hunterembedded.co.uk

4

Robert,

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

Thanks again,

Chris

5

Robert,

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

6

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

7

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

Regards,

8

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

9

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

enable wifi
scan wifi
services

Regards,

10

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

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

11

Anyone ever get the BBONE-GATEWAY-CAPE to work ?
I am having much the same uphill fight with no results.

12

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