I have received a BBBW yesterday. I booted from a SD Card (which has image bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb) previously used on a BBB rev C. Everything functions the same on the BBBW as on the BBB except the network (wired) (the only item listed in connman gui) is not functioning (fair enough). When I run connmanctl> enable wifi BBBW I have error message:“Method “SetProperty” with signature “sv” on interface “net.connman.Technology” doesn’t exist”.
Is there a solution for this please?
Kevin.
Just grab this build:
https://rcn-ee.net/rootfs/bb.org/testing/2017-01-04/lxqt-4gb/
The initial "connman/tether" setup I setup for out of the box was
sub-optimal for the BBBW..
(it assumes your making a wifi access point)..
flash the newest lxqt-4gb image from yesterday
Out of the new image, you can ssh into the wifi access point
(BeagleBone-WXYZ) and use connmanctl to connect to a 2nd access point
(while still connected to the BBBW thru wifi)..
Regards,
Thank you Robert for your reply. I downloaded bone-debian-8.6-lxqt-4gb-armhf-2017-01-04-4gb.img.xz which I hope is the correct selection.
I now have the BBBW booting from the new image, configuring the 4DCAPE-70T display from its eeprom, with keyboard and mouse. #ifconfig -a // providing 192.168.8.1
coomanctl // Error getting VPN connections…
enable wifi // already enabled
scan wifi //Scan completed for wifi
services // found my wireless network: KGNETGEAR
agent on //Agent registered
connect wifi_506583d…// Error /net/connman/service…Method “Connect” with signature “” on interface…doesn’t exist
I also have a Debian pc wired to wireless router KGNETGEAR #ifconfig -a // 192.168.1.4
Please advise next step.
Many thanks,
Kevin.
I carried out:
"I now have the BBBW booting from the new image (debian-8.6-lxqt-4gb-armhf-2017-01-04-4gb), configuring the 4DCAPE-70T display from its eeprom, with keyboard and mouse.
#ifconfig -a // providing 192.168.8.1 (on the BBBW)
coomanctl // Error getting VPN connections… (on the BBBW)
enable wifi // already enabled
scan wifi //Scan completed for wifi
services // found my wireless network: KGNETGEAR
agent on //Agent registered
connect wifi_506583d…// Error /net/connman/service…Method “Connect” with signature “” on interface…doesn’t exist
I also have a Debian pc wired to wireless router KGNETGEAR #ifconfig -a // 192.168.1.4"
Have I misunderstood:
“Out of the new image, you can ssh into the wifi access point
(BeagleBone-WXYZ) and use connmanctl to connect to a 2nd access point
(while still connected to the BBBW thru wifi)…”
Does this mean ssh out of the BBBW?
Regards,
Kevin.
I carried out:
"I now have the BBBW booting from the new image
(debian-8.6-lxqt-4gb-armhf-2017-01-04-4gb), configuring the 4DCAPE-70T
display from its eeprom, with keyboard and mouse.
#ifconfig -a // providing 192.168.8.1 (on the BBBW)
# coomanctl // Error getting VPN connections... (on the BBBW)
> enable wifi // already enabled
> scan wifi //Scan completed for wifi
> services // found my wireless network: KGNETGEAR
> agent on //Agent registered
> connect wifi_506583d........// Error
/net/connman/service....Method "Connect" with signature "" on
interface......doesn't existI also have a Debian pc wired to wireless router KGNETGEAR #ifconfig -a //
192.168.1.4"Have I misunderstood:
"Out of the new image, you can ssh into the wifi access point
(BeagleBone-WXYZ) and use connmanctl to connect to a 2nd access point
(while still connected to the BBBW thru wifi).."
Does this mean ssh out of the BBBW?
It just means, when your run "sudo ifconfig -a"
You'll see two wlan's..
SoftAp0 = the WiFi AP connection for a 2nd PC to connect directly to
the BeagleBone.. (192.168.8.x ip range)
wlan0 = you are free to use this connection to connect to any other
Wireless AP on your network..
Looking at your log:
> connect wifi_506583d........// Error
/net/connman/service....Method "Connect" with signature "" on
interface......doesn't exist
connman died on something else, double check via:
journalctl | grep connman
(it might even be fixed on connman master, we are currently using 1.33)
Regards,
Thank you Robert for your reply. I am sending this message from my BBBW. I have attached a file showing my configuration. At the beginning of the file I have a typing error as I missed the last letter in the connection string .psk
I was unable to use journalctl | grep connman (Error:bash :connman: command not found
Many thanks,
Kevin
http://www.rescuerobot.org/drupal/?q=content/beaglebone-black-bbb-and-debugging-eclipse
connman.txt (3.92 KB)
Hi robert. I have the same problem. I download latest image for bbbw from beagle site(debian 9.1 2017.10.10). When i try to enable wifi by connmanctl, i recieved below error.
Error wifi : methode "set property" with signature "sv" on interface "net.connman.technologies" doesn't exist.
What is the reason?
Hi Robert,
Same problem as Mostafa Bahrami on my side too. I’ve downloaded the other version of stretch. The file I’ve downloaded is → “bone-debian-9.1-lxqt-armhf-2017-08-31-4gb.img”
I can’t see even a wlan0 device when I do ifconfig though, that seems weird to me. I see the following main devices:
eth0 (there’s no ethernet on-board though…)
lo (I guess this is the loopback?)
usb0 → 192.168.7.2
usb1 → 192.168.6.2
Do you have any ideas as to what might be the problem?
Burak
Run this command and share it's output with us to help you debug:
sudo /opt/scripts/tools/version.sh
Regards,
Hi Robert,
Thanks for the quick answer! Here’s the output:
git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]
eeprom:[A335BNLT*]
dogtag:[BeagleBoard.org Debian Image 2017-08-31]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.09-rc2-00002-g7c9353]
kernel:[4.9.45-ti-r57]
nodejs:[v6.11.2]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
Burak
Hi Robert,
Thanks for the quick answer! Here's the output:
git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]
eeprom:[A335BNLT*]
Another case of eeprom mis-programmed:
GND TP1 then run as root:
dd if=/opt/scripts/device/bone/bbbw-eeprom.dump
of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom
reboot and everything will be okay..
dogtag:[BeagleBoard.org Debian Image 2017-08-31]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2017.09-rc2-00002-g7c9353]
kernel:[4.9.45-ti-r57]
nodejs:[v6.11.2]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
Regards,
Hi Robert,
I’ve grounded TP1 (something like a via I suppose so I stuck a jumper in and connected the other end to P9-1). I checked with a thin tip multimeter touching the golden part of the via (not the jumper) and verified they’re connected. I logged in as root and entered the following commands with the outputs beneath them (I’ve added separators here to make them clear, didn’t press enter twice)
root@beaglebone:~# dd if=/opt/scripts/device/bone/bbbw-eeprom.dump
▒U3▒A335BNLTBWA50000BBWG00000+1 records in
0+1 records out
28 bytes copied, 0.00245283 s, 11.4 kB/s
root@beaglebone:~# of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom
After disconnecting the TP1 GND connection I rebooted the device, typed ifconfig and didn’t see wlan0 again, I tried connmanctl and then enable wifi there, same error as earlier. The output of the version.sh didn’t change either:
root@beaglebone:~# sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]
eeprom:[A335BNLT*]
dogtag:[BeagleBoard.org Debian Image 2017-08-31]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.09-rc2-00002-g7c9353]
kernel:[4.9.45-ti-r57]
nodejs:[v6.11.2]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
Is there a problem with what I’m doing or could this be about something else?
Thanks for the help!
Burak
That ^ should be one line, email word wraps it:
dd if=/opt/scripts/device/bone/bbbw-eeprom.dump
of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom
Regards,
Ok should’ve guessed that, it works now.
Thanks for the help Robert!
Burak
Sorry, what was the final solution to this?
If I ground this pin everything will work?
Run this command and share it's output with us to help you debug:
sudo /opt/scripts/tools/version.sh
and then tell us what board it should be..
Regards,
here are the results - it should be a BeagleBone Black - Wireless.
Something about the wlan0 not coming up too?
git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
]eprom:[A335BNLT▒O
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.09-00002-g0b54a51eee]:[l ocation: dd MBR]
kernel:[4.14.71-ti-r80]
nodejs:[v6.14.4]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI- 00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade ]
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 us ers systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/m mcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet]
dmesg | grep pinctrl-single
[ 1.107598] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[ 1.119419] gpio-of-helper ocp:cape-universal: ready
END
Congrat's you have a corrupt eeprom, it's easy to fix..
GND TP1 then run as root:
dd if=/opt/scripts/device/bone/bbbw-eeprom.dump
of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom
(that dd line is "1" line not two..)
reboot and everything will be okay..
Regards,
Thank you for your assistance Robert.
Unfortunately after following those steps the wlan0 and connman services still could not enable the wifi. Was there another step after executing “dd”
dd if=/opt/scripts/device/bone/bbbw-eeprom.dump
▒U3▒A335BNLTBWA50000BBWG00000+1 records in
0+1 records out
28 bytes copied, 0.00322917 s, 8.7 kB/s