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!

On Mon, Jan 28, 2019, 5:12 PM Chris Yorkey <[email protected] wrote:

> 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.
>
>
>
> On Mon, Jan 28, 2019, 2:18 PM Robert Nelson <[email protected]
> wrote:
>
>> On Mon, Jan 28, 2019 at 7:05 AM <[email protected]> wrote:
>> >
>> > 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
>>
>> 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/
>>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOA2q1fXnKB-PykUJpj5qWxSeUBJiQ49nAu4gkNFn9sKF-TB0g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to