[beagleboard] Re: BBB wireless won't reboot

[maxmike]

The file shows a line :* driver ecap already registered - aborting **what 
is that please?*

On Thursday, January 4, 2018 at 5:40:29 PM UTC-8, maxmike wrote:
>
> The problem is here:
>
> wlan0 Link encap:Ethernet  HWaddr 50:65:83:d1:aa:fa
>   UP BROADCAST MULTICAST DYNAMIC  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> Looks like connman won't load wlan0.
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d99aab4d-0f1d-4c05-9c9f-9e17e3325721%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] ti_am335x_tsc.c driver

[bigguiness]

Hi Robert,

That appears to work.

With the 4.4.91-ti-r133 kernel I had to do this to run the libts-bin 
utilities:

$ sudo TSLIB_TSDEVICE=/dev/input/event2 ts_calibrate
$ sudo TSLIB_TSDEVICE=/dev/input/event2 ts_test

With the 4.4.91-ti-r141.1 kernel the utilities now work with just:

$ sudo ts_calibrate
$ sudo ts_test

Thanks!

Unfortunately, this didn't fix the problems I see with SDL1.2 and pygame.

It appears the 1.2.15+dfsg1-4 version of libsdl1.2debian has support for 
tslib
removed since that package is not available in the "normal" jessie repos.

It looks like you are providing tslib from you repos:

$ dpkg -l | grep libts
ii  libts-bin 1.14-1rcnee0~stretch+20171122
 armhftouch screen library utilities
ii  libts0:armhf  1.14-1rcnee0~stretch+20171122
 armhftouch screen library

Any chance you could provide a libsdl1.2debian package that works with 
tslib?

I can go back to a wheezy image but I would rather use a newer one.

Thanks,
Hartley

On Wednesday, January 3, 2018 at 8:30:42 PM UTC-7, RobertCNelson wrote:
>
> On Wed, Jan 3, 2018 at 5:34 PM,   
> wrote: 
> > Hello all, 
> > 
> > The TI touch screen driver does not work _right_ with the libts-bin 
> package 
> > in the jessie image. 
> > 
> > $ cat /etc/dogtag 
> > BeagleBoard.org Debian Image 2018-01-01 
> > 
> > $ lsb_release -a 
> > No LSB modules are available. 
> > Distributor ID: Debian 
> > Description:Debian GNU/Linux 8.10 (jessie) 
> > Release:8.10 
> > Codename:   jessie 
> > 
> > $ dpkg -l | grep  libts-bin 
> > ii  libts-bin 1.14-1rcnee0~jessie+20171122 
> > armhftouch screen library utilities 
> > 
> > $ sudo ts_calibrate 
> > ts_setup: No such file or directory 
> > 
> > It is possible to make it work by setting the TSLIB_TSDEVICE environment 
> > variable: 
> > 
> > $ sudo su 
> > # export TSLIB_TSDEVICE=/dev/input/event2 
> > # ts_calibrate 
> > 
> > But, that's a bit of a pain since the environment variable always needs 
> to 
> > be set in order to use the touchscreen. 
> > 
> > It appears that this version of the utilities uses the INPUT_PROP_DIRECT 
> > propbit to automatically detect which /dev/input/event device is the 
> > touchscreen. 
> > 
> > It looks like the following is the only change needed to make it work. 
> > 
> > Unfortunately, I don't have currently have a way to build a custom 
> kernel 
> > for the BeagleBone in order to test it. If there is anyone that could I 
> > would 
> > appreciate it. 
>
>
> Give this a test: 
>
> wget 
> http://rcn-ee.online/builds/linux-image-4.4.91-ti-r141.1_1cross_armhf.deb 
>
> sudo dpkg -i linux-image-4.4.91-ti-r141.1_1cross_armhf.deb 
>
> src: 
>
> https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/39cf0016bff73697ee59783e5747b49f128fea5b
>  
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/97cecace-db12-44c8-94b0-d4a85ce73ebf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB wireless won't reboot

[maxmike]

The problem is here:

wlan0 Link encap:Ethernet  HWaddr 50:65:83:d1:aa:fa
  UP BROADCAST MULTICAST DYNAMIC  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Looks like connman won't load wlan0.

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/05e43bf7-898a-41f4--7fc90970ac02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB wireless won't reboot

[maxmike]

I have a flasher image for a BBBW that loads just fine and works, but when 
I reboot,
 the network will no longer see the board. Comes back with "unreachable 
host".
Can someone please point me at any particular file/setup I should look at?
 I'm really in a bind on this one. Serial log attached.

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/b6f84233-32e4-4ee9-ba96-dc12cb768c4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
U-Boot SPL 2017.03-2-gd12b1519b4 (Mar 14 2017 - 10:28:26)
Trying to boot from MMC2


U-Boot 2017.03-2-gd12b1519b4 (Mar 14 2017 - 10:28:26 -0500), Build: 
jenkins-github_Bootloader-Builder-532

CPU  : AM335X-GP rev 2.1
I2C:   ready
DRAM:  512 MiB
Reset Source: Global external warm reset has occurred.
Reset Source: Global warm SW reset has occurred.
Reset Source: Power-on reset has occurred.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

 not set. Validating first E-fuse MAC
BeagleBone Black:
Model: BeagleBoard.org BeagleBone Black Wireless:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net:   eth0: MII MODE
Could not get PHY for cpsw: addr 0
cpsw
Press SPACE to abort autoboot in 2 seconds
board_name=[BBBW] ...
Card did not respond to voltage select!
mmc_init: -95, time 13
Card did not respond to voltage select!
mmc_init: -95, time 13
Card did not respond to voltage select!
mmc_init: -95, time 13
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
Card did not respond to voltage select!
mmc_init: -95, time 12
Card did not respond to voltage select!
mmc_init: -95, time 13
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
gpio: pin 55 (gpio 55) value is 1
2207 bytes read in 21 ms (102.5 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
gpio: pin 56 (gpio 56) value is 1
Running uname_boot ...
loading /boot/vmlinuz-4.4.68-ti-r110 ...
8806088 bytes read in 578 ms (14.5 MiB/s)
loading /boot/dtbs/4.4.68-ti-r110/am335x-boneblack-wireless.dtb ...
59486 bytes read in 49 ms (1.2 MiB/s)
uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to enable...
loading /boot/initrd.img-4.4.68-ti-r110 ...
5300197 bytes read in 351 ms (14.4 MiB/s)
debug: [console=ttyO0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait 
coherent_pool=1M net.ifnames=0 quiet cape_universal=enable] ...
debug: [bootz 0x8200 0x8808:50dfe5 0x8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Loading Ramdisk to 8faf2000, end 8fe5 ... OK
   Loading Device Tree to 8fae, end 8faf185d ... OK

Starting kernel ...

[0.001091] clocksource_probe: no matching clocksources found
[2.081500] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[2.319951] omap_voltage_late_init: Voltage driver support not added
[2.327953] PM: Cannot get wkup_m3_ipc handle
Loading, please wait...
[4.834014]  remoteproc1: failed to load am335x-pru0-fw
[4.875999]  remoteproc1: request_firmware failed: -2
[4.881207] pru-rproc 4a334000.pru0: rproc_boot failed
[4.975916]  remoteproc1: failed to load am335x-pru1-fw
[4.985641]  remoteproc1: request_firmware failed: -2
[4.990874] pru-rproc 4a338000.pru1: rproc_boot failed
rootfs: recovering journal
rootfs: clean, 79877/233392 files, 478182/932864 blocks

Debian GNU/Linux 8 beaglebone ttyS0

BeagleBoard.org Debian Image 2017-03-19

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

beaglebone login: [   40.738802] Error: Driver 'ecap' is already registered, 
aborting...

Debian GNU/Linux 8 beaglebone ttyS0

BeagleBoard.org Debian Image 2017-03-19

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

beaglebone login:
Debian GNU/Linux 8 beaglebone ttyS0

BeagleBoard.org Debian Image 2017-03-19

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

Re: [beagleboard] bbio segmentation fault on brand new BBB

['Roberts Maria' via BeagleBoard]

On Fri, 1/5/18, Robert Nelson  wrote:

 Subject: Re: [beagleboard] bbio segmentation fault on brand new BBB
 To: "Ivan Zhidov" 
 Cc: "Beagle Board" 
 Date: Friday, January 5, 2018, 1:00 AM
 
 On Thu, Jan 4, 2018 at 3:56 PM,
 Ivan Zhidov 
 wrote:
 > Thank you!
 >
 > I will switch to
 using an alternative library then but BBB should stop
 > including BBIO examples.
 
 They were officially nuked on:
 May 30, 2017
 
 
https://github.com/jadonk/bone101/commit/fb8ce9a2f8a1b90fe6eabd3dab10c3ea5df86ae4
 
 The latest images page:
 
 https://beagleboard.org/latest-images
 
 lists "3" updated
 image releases since then..
 
 aka you have a really-really-really old
 image..
 
 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 beagleboard+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjmRLYY_-A1uuVEjOjKXsN1VO2x-1sSMVrB-OyYrZ4T7A%40mail.gmail.com.
 For
 more options, visit https://groups.google.com/d/optout.
  agresiunea si teritoriul  ar fi insemnat un pas inainte pe calea consolidarii

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1577106603.699134.1515108112992%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] bbio segmentation fault on brand new BBB

[Robert Nelson]

On Thu, Jan 4, 2018 at 4:14 PM, Ivan Zhidov  wrote:
> I just purchased this board from Newark a week ago. It still has PyBBIO
> examples in it. Its OS is Linux beaglebone 4.1.15-ti-rt-r43 #1 SMP PREEMPT
> RT Thu Jan 21 20:13:58 UTC 2016 armv7l GNU/Linux
>
> I did install latest Debian image on another BB prior to getting this one
> and that one dind't have PyBBIO.

Just reflash it, must have just sat on a shelf for awhile at Newark..

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYio9BgifzzgmHHgr7QcLNnL_bZDhdHiZTpUiMQ%2B_rEd%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] bbio segmentation fault on brand new BBB

[Ivan Zhidov]

I just purchased this board from Newark a week ago. It still has PyBBIO
examples in it. Its OS is Linux beaglebone 4.1.15-ti-rt-r43 #1 SMP PREEMPT
RT Thu Jan 21 20:13:58 UTC 2016 armv7l GNU/Linux

I did install latest Debian image on another BB prior to getting this one
and that one dind't have PyBBIO.

On Thu, Jan 4, 2018 at 4:00 PM, Robert Nelson 
wrote:

> On Thu, Jan 4, 2018 at 3:56 PM, Ivan Zhidov  wrote:
> > Thank you!
> >
> > I will switch to using an alternative library then but BBB should stop
> > including BBIO examples.
>
> They were officially nuked on: May 30, 2017
>
> https://github.com/jadonk/bone101/commit/fb8ce9a2f8a1b90fe6eabd3dab10c3
> ea5df86ae4
>
> The latest images page:
>
> https://beagleboard.org/latest-images
>
> lists "3" updated image releases since then..
>
> aka you have a really-really-really old image..
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAAxQk8nxK-FJ%3D1aVvSzgkyhUGdbJp1Nap9ySOhTwb-siMXs%2BtA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] bbio segmentation fault on brand new BBB

[Robert Nelson]

On Thu, Jan 4, 2018 at 3:56 PM, Ivan Zhidov  wrote:
> Thank you!
>
> I will switch to using an alternative library then but BBB should stop
> including BBIO examples.

They were officially nuked on: May 30, 2017

https://github.com/jadonk/bone101/commit/fb8ce9a2f8a1b90fe6eabd3dab10c3ea5df86ae4

The latest images page:

https://beagleboard.org/latest-images

lists "3" updated image releases since then..

aka you have a really-really-really old image..

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjmRLYY_-A1uuVEjOjKXsN1VO2x-1sSMVrB-OyYrZ4T7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] bbio segmentation fault on brand new BBB

[Ivan Zhidov]

Thank you!

I will switch to using an alternative library then but BBB should stop
including BBIO examples.

On Thu, Jan 4, 2018 at 3:42 PM, Robert Nelson 
wrote:

> On Thu, Jan 4, 2018 at 12:31 PM, Ivan Zhidov  wrote:
> > Linux beaglebone 4.1.15-ti-rt-r43 #1 SMP PREEMPT RT Thu Jan 21 20:13:58
> UTC
> > 2016 armv7l GNU/Linux
> >
> > Failed to execute BBIO examples, shows segmentation fault on import
> bbio, I
> > updated to the latest and updated bbio as well, still didn't help
> >
> > bash: line 1: 16630 Segmentation fault  "python2"
> > "/var/lib/cloud9/bone101/examples/PyBBIO/blink.py"
> >
> > There was an older thread about a similar issue on kernel >4.x but
> Ithought
> > this was already fixed. Again this is a brand new BBB out of the box.
>
> The "PyBBIO" examples only work on older 3.8.x kernels.
>
> Thus they are no-longer installed by default in the default images.
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAAxQk8npUbhO_%2Bq27skPsUkyt_9ScOCNakppFxm3fBh7mn2Szg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] bbio segmentation fault on brand new BBB

[Robert Nelson]

On Thu, Jan 4, 2018 at 12:31 PM, Ivan Zhidov  wrote:
> Linux beaglebone 4.1.15-ti-rt-r43 #1 SMP PREEMPT RT Thu Jan 21 20:13:58 UTC
> 2016 armv7l GNU/Linux
>
> Failed to execute BBIO examples, shows segmentation fault on import bbio, I
> updated to the latest and updated bbio as well, still didn't help
>
> bash: line 1: 16630 Segmentation fault  "python2"
> "/var/lib/cloud9/bone101/examples/PyBBIO/blink.py"
>
> There was an older thread about a similar issue on kernel >4.x but Ithought
> this was already fixed. Again this is a brand new BBB out of the box.

The "PyBBIO" examples only work on older 3.8.x kernels.

Thus they are no-longer installed by default in the default images.

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYig5m2CHP%3D8aUSbKi7JYDzwug0UPNkJyTibmSfXfKy8yA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] bbio segmentation fault on brand new BBB

[Ivan Zhidov]

Linux beaglebone 4.1.15-ti-rt-r43 #1 SMP PREEMPT RT Thu Jan 21 20:13:58 UTC 
2016 armv7l GNU/Linux

Failed to execute BBIO examples, shows segmentation fault on import bbio, I 
updated to the latest and updated bbio as well, still didn't help

bash: line 1: 16630 Segmentation fault  "python2" 
"/var/lib/cloud9/bone101/examples/PyBBIO/blink.py"

There was an older thread about a similar issue on kernel >4.x but Ithought 
this was already fixed. Again this is a brand new BBB out of the box.

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/65cec36e-a9ed-4462-8c37-f9510d05ddc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone Isn't Reading I2C Values from HMC5883L.

[Tomas Medina]

Thanks for your advice!
I added the parameter 2 to lines 7 and 15 and now it's reading.
def __init__(self):
self.hmc = Adafruit_I2C(0x1E,2)
self.debug = False
self.address = 0x1E

self.readingList = [0, 0, 0]
self.maxList = [0, 0, 0]
self.minList = [0, 0, 0]

self.mpu = Adafruit_I2C(0x68,2)



On Thursday, January 4, 2018 at 9:42:58 AM UTC-5, Graham wrote:
>
> I meant, go look at the AdaFruit I2C code.
> I think you need to override the bus number to get it talking to bus 2.
>
> --- Graham
>
> ==
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/b8321aef-db4e-4d31-8608-1695ebd53fa6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Using Connman for WiFi AP/tether...

[Robert Nelson]

On Thu, Jan 4, 2018 at 8:27 AM,   wrote:
> Dear all,
>
> I have to warm up this post again as I'm dealing with a minor problem when
> setting my boards in AP mode:
>
> I have two BBBs: 1 BBBW and one BBB rev. C
>
> On BBBW (4.4.30-ti-r64) the AP is started automatically, I can use
> /var/lib/connman/settings file to set the SSID and the passphrase, and I can
> connect to this board and get an IP in the range of 192.168.0.X
>
> On BBB with a TP-Link TL-WN722N (4.4.91-ti-r133) I try to do the same.
> Therefore, I uncommented to connman line in /etc/network/interfaces and
> edited the /var/lib/connman/settings (same setting as above). When I restart
> the board I can see the SSID and even connect (from Windows) but I don't get
> an IP. --> So I think I have to change another small thing to get it working
> 100% (a problem with the DHCP?). Can you please point me towards the right
> direction??? Would be great!

Give this a shot:

sudo connmanctl tether wifi on ${wifi_ssid} ${wifi_password}

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgzCAv1M-csQYs_k-_%2BtR-B7AdmJxdpz87ws4eTqaeOFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Using Connman for WiFi AP/tether...

[marco . st1987]

Dear all,

I have to warm up this post again as I'm dealing with a minor problem when 
setting my boards in AP mode:

I have two BBBs: 1 BBBW and one BBB rev. C

On BBBW (4.4.30-ti-r64) the AP is started automatically, I can use 
/var/lib/connman/settings file to set the SSID and the passphrase, and I 
can connect to this board and get an IP in the range of 192.168.0.X

On BBB with a TP-Link TL-WN722N (4.4.91-ti-r133) I try to do the same. 
Therefore, I uncommented to connman line in /etc/network/interfaces and 
edited the /var/lib/connman/settings (same setting as above). When I 
restart the board I can see the SSID and even connect (from Windows) but I 
don't get an IP. --> So I think I have to change another small thing to get 
it working 100% (a problem with the DHCP?). Can you please point me towards 
the right direction??? Would be great!

Best regards,
Marco


-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/6b32d111-50db-4f77-9ad6-1de430d59df9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: TI BSP failed to build kernel

[Jeff Andich]

Ok, so if I understand correctly, if I git the kernel and checkout the 
4.4.y or 4.9.y branches and then build the kernel using build_kernel.sh 
with FULL_REBUILD defined, any updates to the mainline or the patchset 
could affect my build or functionality, right?

What is the best way to get updated when either the kernel and/or patch 
set(s) change?  What mailing lists do we need to join?

Thanks!!

jeff  

On Tuesday, January 2, 2018 at 8:48:10 AM UTC-6, RobertCNelson wrote:
>
> On Tue, Jan 2, 2018 at 8:41 AM, Jeff Andich  > wrote: 
> > 
> > FYI, I THINK I ran into something similar over the holidays when I tried 
> to 
> > fetch and build the 4.4.y and 4.9.y kernels using eewiki.  I tried both 
> BBB 
> > and BB-X15.  I ran into an issue with a build error in an assembly file 
> > which apparently had to do with some kind of networking package.  The 
> kernel 
> > built again, when this package was de-selected in makemenuconfig.  I was 
> > getting ready to post something on this, but then some time after 
> Christmas, 
> > I re-fetched everything using the instructions on eewiki and everything 
> > built again 
> > 
> > 
> > Regards and happy new year! 
>
> for 4.9.x it was me last week, i fubared up the pocketbeagle 
> simplegaming device tree binary. 
>
> also the wireguard patchset merge the last few weeks had some issues with 
> thumb2 
>
> But Wireguard + https://github.com/StreisandEffect/streisand + linode 
> (or any of the other supported ones) has been working awesome for me. 
> ;) 
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/25803f4d-5d82-40b7-a040-fcfd60b2e152%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone Isn't Reading I2C Values from HMC5883L.

[Graham]

I meant, go look at the AdaFruit I2C code.
I think you need to override the bus number to get it talking to bus 2.

--- Graham

==

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f15045fc-95f1-4205-bced-10e86bd4f9e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone Isn't Reading I2C Values from HMC5883L.

[Graham]

On Thursday, January 4, 2018 at 8:37:33 AM UTC-6, Graham wrote:
>
> I suspect your code is looking for it on the wrong bus number.
>
> You did not include your driver code.
>
> Look there.
>
> The part is obviously sitting on Bus 2.
>
> I have seen drivers that default to bus 1, unless overridden.
>
> --- Graham
>
> ==
>
> On Wednesday, January 3, 2018 at 10:13:43 PM UTC-6, Tomas Medina wrote:
>>
>> I believe it's 2
>>
>> On Wednesday, January 3, 2018 at 10:07:29 PM UTC-5, RobertCNelson wrote:
>>>
>>>
>>>
>>> On Wed, Jan 3, 2018 at 8:54 PM, Tomas Medina  wrote:
>>>

 I am trying to use a Beaglebone Wireless (debian image 2017-07-01) to 
 read values from an HMC5883L Magnetometer. 
 The device is connected through I2C2 (pins P9_19 and P9_20). The 
 address for the device is 0x68. 

 I know the device is connected since I can see it by using i2cdetect as 
 shown below:

 However, whenever I run my python code to read the values, I get 
 messages that the bone is having errors accessing the adresses.
 As with most of my problems with the BBBW, the code works fine on an 
 older bone (debian image 2015-11-12).
 My faith in Beagleboard dwindles by the minute.

 Here is the python code, first is my main file:
 from time import sleep
 import os
 import hmcCl 

 sensor = hmcCl.hmc()
 sensor.setConfig()

 count = 0
 while True:

 count += 1
 x = 0
 y = 0
 z = 0
 he = 0
 
 os.system("clear")

 x, y, z = sensor.getAvgRead(5)
 
 print("X: {} Y: {} Z: {} Count: {}".format(x,y,z, count
 ))
 
 print(sensor.getDirection())
 sleep(.2)

 Next is the object file (hmcCl.py):
 from Adafruit_I2C import Adafruit_I2C
 import math

 class hmc:

 def __init__(self):
 self.hmc = Adafruit_I2C(0x1E)
 self.debug = False
 self.address = 0x1E

>>>
>>>
>>> busnum?
>>>
>>> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/56566293-9fed-4c9f-9109-954af352d230%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone Isn't Reading I2C Values from HMC5883L.

[Graham]

I suspect your code is looking for it on the wrong bus number.

You did not include your driver code.

Look there.

The part is obviously sitting on Bus 2.

I have seen drivers that default to bus 1, unless overridden.

--- Graham

==

On Wednesday, January 3, 2018 at 10:13:43 PM UTC-6, Tomas Medina wrote:
>
> I believe it's 2
>
> On Wednesday, January 3, 2018 at 10:07:29 PM UTC-5, RobertCNelson wrote:
>>
>>
>>
>> On Wed, Jan 3, 2018 at 8:54 PM, Tomas Medina  wrote:
>>
>>>
>>> I am trying to use a Beaglebone Wireless (debian image 2017-07-01) to 
>>> read values from an HMC5883L Magnetometer. 
>>> The device is connected through I2C2 (pins P9_19 and P9_20). The address 
>>> for the device is 0x68. 
>>>
>>> I know the device is connected since I can see it by using i2cdetect as 
>>> shown below:
>>>
>>> However, whenever I run my python code to read the values, I get 
>>> messages that the bone is having errors accessing the adresses.
>>> As with most of my problems with the BBBW, the code works fine on an 
>>> older bone (debian image 2015-11-12).
>>> My faith in Beagleboard dwindles by the minute.
>>>
>>> Here is the python code, first is my main file:
>>> from time import sleep
>>> import os
>>> import hmcCl 
>>>
>>> sensor = hmcCl.hmc()
>>> sensor.setConfig()
>>>
>>> count = 0
>>> while True:
>>>
>>> count += 1
>>> x = 0
>>> y = 0
>>> z = 0
>>> he = 0
>>> 
>>> os.system("clear")
>>>
>>> x, y, z = sensor.getAvgRead(5)
>>> 
>>> print("X: {} Y: {} Z: {} Count: {}".format(x,y,z, count
>>> ))
>>> 
>>> print(sensor.getDirection())
>>> sleep(.2)
>>>
>>> Next is the object file (hmcCl.py):
>>> from Adafruit_I2C import Adafruit_I2C
>>> import math
>>>
>>> class hmc:
>>>
>>> def __init__(self):
>>> self.hmc = Adafruit_I2C(0x1E)
>>> self.debug = False
>>> self.address = 0x1E
>>>
>>
>>
>> busnum?
>>
>> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/774679da-c32d-4964-97f3-0a3fdab3f09e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beaglebone Blue crashes furing updates/downloads and subsequent root file system failures

[George Terzakis]

Hello everyone,

I have been using the Beaglebone Blue for over 3 months now without any 
problems until now. The board typically boots off the SD card, primarily 
because I needed the extra space for a ROS installation. I originallyt used 
the latest Debian Jessie image for a couple of months and then created a 
new SD card (early December 2017) with the new Debian stretch image and 
then setup ROS (from source).

EMMC does not boot anymore
 
I recently noticed that when the SD card is removed, the board will not 
boot from the EMMC for some reason. This was clearly not the case about a 
month ago when I moved on to stretch, so whatever caused this must have 
happened recently. I typically power the board from the USB and 
occasionally from an external 12V DC source. In terms of devices, I am 
using the IMU and the UART to talk to a motor controller (Roboteq in 
particular), but during the last month the controller was not connected, so 
the board was practically running with no external devices connected to it. 
I once or twice briefly used different SD cards on it. 

Other (potentially) Related Issues
--
In addition to not booting from the EMMC, I noticed occasional hangs during 
updates and/or prolonged downloads. In some cases, the crashed 
download/update process can be interrupted by Ctrl-C and in others not. 
Regardless, the Beaglebone does not work properly, as many subsequent 
commands (for instance, "ps") will crash and the only way to recover is by 
hard reset. However, in many occasions after the reset, the root file 
system is corrupted and we have to repair it using fsck.

Consistency
--
I originally believed that the stretch installation was the source of the 
crash problem (did not think it was related to the EMMC not booting up), so 
I re-installed Debian Jessie and stretch multiple times to realize that the 
crashing-during-updates problem was consistently re-appearing regardless of 
Debian version at various stages. Thus, I was led to believe that this a 
board issue rather than something that has to do with the Debian and most 
probably, not being able to boot from the EMMC is a symptom of the same 
problem. In my last attempt, I burned the stretch image into the SD card 
and the Debian could not update right off the bat (it gave a root file 
system error : 

E: List directory /var/lib/apt/lists/partial is missing. - Acquire (30: 
Read-only file system)

Note that the Beaglebone Blue board appears to be in working order 
otherwise (i.e., wireless appears to work, cloud page, etc.).

I would very much appreciate your help in troubleshooting this problem and 
most importantly, finding out its cause.

Regards


George

 


-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4c44ad76-9b6d-4ac5-8e75-a560d18e4927%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone black doesn´t start (only power led is on)

[danilodene]

Follow this tutorial: https://elinux.org/Beagleboard:Updating_The_Software 
works great for me 

Other 
informations: 
http://wiki.beyondlogic.org/index.php?title=BeagleBoneBlack_Upgrading_uBoot




f the boot switch (S2) is held down during power-up, the ROM will boot from 
the SPI0 Interface first, followed by MMC0 (external uSD), USB0 and UART0. 
This allows the BeagleBone Black to bypass the onboard eMMC and boot from 
the removable uSD (provided no valid boot device is found on SPI0.) *This 
can be used to recover from a corrupted onboard eMMC/U-Boot.*



Em quarta-feira, 17 de fevereiro de 2016 12:39:12 UTC-2, Jecika escreveu:
>
> Hello everyone, 
>
>  
>
> I have the same problem . I bought a BBB and tested it: at start up, the 
> USERS leds blinks.  I have followed the instructions in the site 
> Beagleboard:Updating 
> The Software - eLinux.org. 
> 
>
> I unplagged the power supply and I keep pressed the S2 button (boot) (at 
> least 1 minute), I Applied the power to the board by plugging in the cable 
> (external power supply 5 V, 3 A). Only power led is on.
>
> When I pressed the power button for at least 8 seconds, the power led is 
> turned off then after  3-4 seconds it is turned on.
>
>  
> Could you please help me
>
> Le dimanche 18 août 2013 15:10:31 UTC+1, Gerald a écrit :
>>
>> Try here:
>>
>> http://circuitco.com/support/index.php?title=BeagleBoneBlack
>>
>> and
>>
>> http://circuitco.com/support/index.php?title=Updating_The_Software
>>
>> Gerald
>>
>>
>> On Sat, Aug 17, 2013 at 10:52 PM, Carlos Eduardo Giuliani Baú <
>> contato@gmail.com> wrote:
>>
>>> Hello!
>>>
>>> After trying to boot with the power suply by USB, my beaglebone board 
>>> doesn´t lit any led, only the power led. I already tried press the reset 
>>> button for a few seconds and nothing work.
>>> Any idea of how to fix it? 
>>>
>>> -- 
>>> 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 beagleboard...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9b24b4fa-854d-44d5-9524-44c517a6acd7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB MMC bare metal demo program

[mike . maikaefer]

Have you tried to submit a patch? The project itself seems to be alive, 
last change was done only one month 
ago: https://sourceforge.net/p/starterwarefree/code/ci/master/tree/

And this seems to be the maintainer of the 
project: https://sourceforge.net/u/openapcjim/profile/



On Thursday, January 4, 2018 at 11:42:59 AM UTC+1, dd wrote:
>
> Hi Mike.  It is not related to the sourceforge starterware project, but 
> they are free to rip it.  
> I had a look at them, i did not see anyone spearheading the project.  
> It would be great to have a collaboration of contributors, this is a huge 
> undertaking.  
> we really need a real-time library that we can build on.   
>
> hack on brothersdd
>
> On Wednesday, January 3, 2018 at 10:47:41 AM UTC+2, mike.ma...@gmail.com 
> wrote:
>>
>> Is this somehow related to the free StarterWare project at Sourceforge? 
>> If no: any chance it will be integrated there?
>>
>> On Monday, January 1, 2018 at 2:22:34 PM UTC+1, dd wrote:
>>>
>>> Hi 2 all 'bone programmers.  
>>> The starterware MMC port is finally finished.  
>>> This is a great opportunity to learn MMC and FAT32 architecture.  
>>> As well as ARM assembly, IRQ, DMA, image building etc
>>> on a wickedly powerful IoT platform, the BBB!
>>> It builds under GNU/GCC, all the makefile stuff is there.  
>>> It was a long time coming.  The TI code was very well written, 
>>> but also unnecessarily complicated.  Well, I removed all that.  
>>> So, now you can use/mod/hack it with relative confidence
>>> for your IoT project.  
>>>
>>> hack on my brothers.dd
>>>
>>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/be5694e8-eb73-41e2-85a9-c1b7c1bf9ae2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Booting from eMMC issue

[Nuno Silva]

Hello George,

For the time being I cannot help you. First because I also don't know what
is happening. Second because after what has happened to my BBBL I didn't
tried to reflash the eMMC. I'm still doing some stuff with it, booting from
the sdCard (and working fine, but I didn't tried to update or upgrade so,
don't know if it fails or not at some point) and until I'm finished with
doing that I will do nothing with the eMMC. When I do, then I'll tell you
what was the result: a bricked BBBL or success.

The more savvy guys could help us but or there is no one in the forum or
they are not willing to help us.

My thoughts are: some software issues with Debian image; issue with the
eMMC; issue with the electronics that choose from where to boot, something
like a fried resistor, a chip or something like that.

Regards,
Nuno

On Wed, Jan 3, 2018 at 2:07 PM,  wrote:

> Hi Nuno and everyone else,
>
> We have recently come across this peculiar issue: The EMMC of the
> beaglebone blue just stopped booting up without an apparent reason. At the
> same time, we noticed erratic behavior by the BB during updates and/or
> downloads. In particular, the update hangs at random stages of the download
> and Ctrl-C is the only solution. However, after the interruption, the BB is
> not working properly (e.g, recurring hangs and in several cases errors in
> the file system ). Regardless, only hard reset works (i.e., issuing a
> reboot command will just hang the board again).
>
> We initially though that the use of stretch was probably the cause for the
> issue, bit the same problem occurred with Debian Jessie SD card. We have
> re-written the Debian image multiple times and the same problem (i.e., the
> hangs during updates) re-occurs consistently at various stages of the
> update. It should be noted that the EMMC is still not bootable, but we
> haven't attemped to re-flash it.
>
> Looking forward to your help and comments
>
> Regards
>
> George
>
> --
> 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/NTNVHB-l1Hg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/5e566b3a-1756-4aea-9bbb-c45e46eaaf6c%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAFaiEC%2BUKu4%2BtNk66KLyZNnUO6WRhf0UaheaxUD0-%3Deh7ejEMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB MMC bare metal demo program

['dd' via BeagleBoard]

Hi Mike.  It is not related to the sourceforge starterware project, but 
they are free to rip it.  
I had a look at them, i did not see anyone spearheading the project.  
It would be great to have a collaboration of contributors, this is a huge 
undertaking.  
we really need a real-time library that we can build on.   

hack on brothersdd

On Wednesday, January 3, 2018 at 10:47:41 AM UTC+2, mike.ma...@gmail.com 
wrote:
>
> Is this somehow related to the free StarterWare project at Sourceforge? If 
> no: any chance it will be integrated there?
>
> On Monday, January 1, 2018 at 2:22:34 PM UTC+1, dd wrote:
>>
>> Hi 2 all 'bone programmers.  
>> The starterware MMC port is finally finished.  
>> This is a great opportunity to learn MMC and FAT32 architecture.  
>> As well as ARM assembly, IRQ, DMA, image building etc
>> on a wickedly powerful IoT platform, the BBB!
>> It builds under GNU/GCC, all the makefile stuff is there.  
>> It was a long time coming.  The TI code was very well written, 
>> but also unnecessarily complicated.  Well, I removed all that.  
>> So, now you can use/mod/hack it with relative confidence
>> for your IoT project.  
>>
>> hack on my brothers.dd
>>
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d5a3e345-4884-45c5-9019-2f9c28dd4783%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.