[beagleboard] OpenGL support for Beaglebone Black

[sajeevan k]

Hi all,

I have been using Linaro Tool chain and sysroot for cross compiling and 
building my Qt applications for Beaglebone Black Rev C with debian image  

Cross Compile Tool chain used - 
gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabihf 
Sysroot used - sysroot-eglibc-linaro-2017.01-arm-linux-gnueabihf.

Does this arrangement support OpenGL? 

Is there any sysroot available for Beaglebone Black with installed OpenGL 
ES packages ?


Thanks & Regards,
Sajeevan.K

-- 
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/ad1c83de-3821-4d21-a259-65bcad0c448d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Rs-485 Linux embedded

[Angelo Fares Menhem]

Micka,

Eldo succeeded in building the kernel and the device tree. It worked like a 
breeze (so far).

Thank you very much. You have made friends here. If you need  help in anything 
that we can help, just let me know.

Best regards

Angelo

Sent from my iPhone

On 2 Aug 2017, at 13:26, Micka 
> wrote:

Well, to summarize you have to compile the kernel 4.4: in the menu of the 
configuration, you switch to 
omap-serial.c
  with CONFIG_SERIAL_OMAP

and on the device tree you have to put something like :


_pinmux {

uart1_pins: pinmux_uart1_pins {
pinctrl-single,pins = <
AM33XX_IOPAD(0x980, PIN_INPUT | MUX_MODE0) /* P9.26 uart1_rxd.uart1_rxd  
INPUT   OK*/
AM33XX_IOPAD(0x984, PIN_OUTPUT | MUX_MODE0) /* P9.24 uart1_txd.uart1_txd  
OUTPUT   OK*/
AM33XX_IOPAD(0x9a4,  PIN_OUTPUT | MUX_MODE7) /* TX enable GPIO 3_19   OK*/
AM33XX_IOPAD(0x848,  PIN_OUTPUT | MUX_MODE7) /* RX enable P9.14 GPIO 1_18 mode 
7 OK*/
>;
};
.

};


 {
pinctrl-names = "default";
pinctrl-0 = <_pins>;
status = "okay";
rts-gpio = < 19 GPIO_ACTIVE_HIGH>; // 3_19
cts-gpio = < 18 GPIO_ACTIVE_HIGH>; // 1_18
rs485-rts-active-high;
rs485-rts-delay = <0 0>;
linux,rs485-enabled-at-boot-time;
};


Enjoy !

Micka,


Le mer. 2 août 2017 à 17:33, Angelo Fares Menhem 
> a écrit :
Eldo

Attached are the prints of my chat wit Michael Musset.

Please follow his instructions.

He kindly offered to help us via email.

If necessary send him a message copying me.

Regards

-- 
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/C49B083F-2FD4-444E-A383-01BE48F6A3F2%40concert.com.br.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBBW does not recognizes wifi

[subbuti]

Hello,
my board does not connect to wifi because does not recognize wifi. I tried 
almmost all the flashers and other builds for sd. 
but when i plug external wifi over usb connects to internet.

pls help me .

thank you in advance.

debian@beaglebone:~$ connmanctl technologies
/net/connman/technology/ethernet
  Name = Wired
  Type = ethernet
  Powered = True
  Connected = False
  Tethering = False
debian@beaglebone:~$


connmanctl> scan wifi
Error /net/connman/technology/wifi: Method "Scan" with signature "" on 
interface "net.connman.Technology" doesn't exist

 ifconfig
eth0  Link encap:Ethernet  HWaddr 50:65:83:d2:e8:e0
  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)
  Interrupt:173

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:292 errors:0 dropped:0 overruns:0 frame:0
  TX packets:292 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1
  RX bytes:22211 (21.6 KiB)  TX bytes:22211 (21.6 KiB)

usb0  Link encap:Ethernet  HWaddr 50:65:83:d2:e8:e2
  inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
  inet6 addr: fe80::5265:83ff:fed2:e8e2/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:6402 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1607 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:632943 (618.1 KiB)  TX bytes:315179 (307.7 KiB)

usb1  Link encap:Ethernet  HWaddr 50:65:83:d2:e8:e5
  inet addr:192.168.6.2  Bcast:192.168.6.3  Mask:255.255.255.252
  UP BROADCAST MULTICAST  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)

-- 
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/15085a34-fe0b-4870-b2a5-971cb7f9cbc0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: NFS boot hangs

[digitalwiz42]

I've been playing around with this most of the day and I think I've made 
some progress. I think the nfs-uEnv.txt script that comes with Debian 8.6 
is missing some stuff. First off, it doesn't load the initrd file. From 
what I can tell that seems to be necessary. Then there are some command 
line options that the MMC boot script defines that aren't in the NFS script.

So I modified nfsboot_uname_r to load the initrd and pass it to the kernel. 
Here is my cmdline:
cmdline=quiet coherent_pool=1M net.iframes=0 cape_universal=enable

This seems to get me farther, I think.

Starting kernel ...

[0.001033] clocksource_probe: no matching clocksources found
[2.058442] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[2.239713] omap_voltage_late_init: Voltage driver support not added
[2.247404] PM: Cannot get wkup_m3_ipc handle
Loading, please wait...
[7.889354]  remoteproc1: failed to load am335x-pru0-fw
[7.919494]  remoteproc1: request_firmware failed: -2
[7.924703] pru-rproc 4a334000.pru0: rproc_boot failed
[8.045662]  remoteproc1: failed to load am335x-pru1-fw
[8.063312]  remoteproc1: request_firmware failed: -2
[8.068516] pru-rproc 4a338000.pru1: rproc_boot failed
IP-Config: eth0 hardware address 80:30:dc:90:9b:da mtu 1500
IP-Config: eth0 guessed broadcast address 192.168.1.255
IP-Config: eth0 complete:
 address: 192.168.1.50 broadcast: 192.168.1.255netmask: 
255.255.255.0   
 gateway: 192.168.1.1  dns0 : 0.0.0.0  dns1   : 
0.0.0.0 
 rootserver: 192.168.1.2 rootpath: 
 filename  : 
[  OK  ] Started Flush Journal to Persistent Storage.
 Starting Create Volatile Files and Directories...
[  OK  ] Started udev Kernel Device Manager.
 Starting LSB: Tune IDE hard disks...
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Create Volatile Files and Directories.
 Starting Update UTMP about System Boot/Shutdown...
 Starting Network Time Synchronization...
[  OK  ] Started LSB: Tune IDE hard disks.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on bonescript.socket.
[  OK  ] Listening on cloud9.socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
[  OK  ] Listening on node-red.socket.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
 Starting BB WL18xx wlan0 Service...
 Starting Login Service...
[  OK  ] Started Regular background program processing daemon.
[  OK  ] Started Deferred execution scheduler.
 Starting System Logging Service...
 Starting LSB: Start busybox udhcpd at boot time...
 Starting LSB: Load kernel modules needed to enable cpufreq 
scaling...
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
 Starting Generic Board Startup...
 Starting Cape Manager Service...
[  OK  ] Started Bonescript autorun.
 Starting Restore Sound Card State...
 Starting Restore /etc/resolv.conf i...e the ppp link was shut 
down
[  OK  ] Started D-Bus System Message Bus.
 Starting Connection service...
 Starting Avahi mDNS/DNS-SD Stack...
[  OK  ] Started System Logging Service.
[  OK  ] Started BB WL18xx wlan0 Service.
[  OK  ] Started Cape Manager Service.
[  OK  ] Started Restore Sound Card State.
[  OK  ] Started Restore /etc/resolv.conf if...ore the ppp link was shut 
down..
[  OK  ] Started LSB: Start busybox udhcpd at boot time.
[  OK  ] Started Login Service.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Connection service.
[  240.434411] INFO: task kworker/0:8:849 blocked for more than 120 seconds.
[  240.441295]   Not tainted 4.4.54-ti-r93 #1
[  240.445799] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this 
message.
[  360.450413] INFO: task kworker/0:8:849 blocked for more than 120 seconds.
[  360.457296]   Not tainted 4.4.54-ti-r93 #1
[  360.461797] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this 
message.

I really would like some insight into this. Thanks.



-- 
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/805aa667-fe2a-4826-8b23-d88f339719bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Audio output guidance / embedded hifi audio player

[Nicolae Vlădescu]

Hello.

I am just getting started with my bbb but i can't seem to wrap my head 
around the I²S protocol.

>From what i managed to gather bbb can output audio via usb versus for 
example raspberry pi that has special I²S headers on the board.

I want to transform my bbb into an hifi audio player using runeaudio or 
volumio, but i can't seem to find any suggestion on what hardware should i 
use, is it a cape? an usb soundcard (cheapest), usb dac, usb dac with 
preamp or the more expensive usb audio interfaces?

What is the recommended hardware to take advantage of the full I²S protocol 
on bbb?

Thank you.

-- 
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/70971ff5-7d20-4f8a-a695-831b01fc9994%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: DHCP issues

[Robert Nelson]

On Aug 2, 2017 1:29 PM, "Kurt Talke"  wrote:

Jason,

After the IP address changes I’m unable to log in.

Basically, I flashed with Debian 8.8, then ran the configure_robotics_dt.sh
script.

After rebooting,
I can no longer log in.

should be easy to duplicate.


Use an older release, with the conversation to u-boot overlays, that dt
script won't work. I have that cape and need to push it out my fixes.

Busy with family stuff, so it won't be till next week.

Regards,



-K

On Aug 2, 2017, at 9:24 AM, Jason Kridner  wrote:

Can you provide a journal log?

Can you check the status of dnsmasq and connman processes?

Which script are you calling the "DT script"? https://github.com/
StrawsonDesign/Robotics_Cape_Installer/blob/master/install.sh ?
https://github.com/StrawsonDesign/Robotics_Cape_
Installer/blob/master/device_tree/configure_robotics_dt.sh ?

On Mon, Jul 31, 2017 at 6:08 PM Kurt Talke  wrote:

> Hi Jason, James,
>
> I’m running Debian 8.8 from 7/1/17, and I’m having an issue where the BBB
> no longer shows up as the default IP 192.168.7.2
>
> I’ve narrowed it down to the script which enables the device tree overlay,
> or installing the robotics cape from source code.
>
> Once I reboot, my BBB shows up as a self assigned IP 169.254.44.139, and I
> can’t connect to it.
>
> The DT script works for 8.7, but not 8.8 or the 9.1 versions.
>
> Any ideas?
>
>
>
> -Kurt

-- 
https://beagleboard.org/about


-- 
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/E11C7FFC-B7DB-48FC-874F-CBDA1B3DFB41%40eng.ucsd.edu

.

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/CAOCHtYj%2B-EL-UtmSxdiZTPt6u7zboyR83nUs693W%2BOL2S3_CyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] NFS boot hangs

[digitalwiz42]

I'm having an odd problem trying to boot the BBB over NFS. Specifically, 
I'm trying to mount the Debian image dated 2017-03-19. Here's the output I 
get:
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: 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:
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
cpsw
Press SPACE to abort autoboot in 2 seconds
board_name=[A335BNLT] ...
board_rev=[000C] ...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
** Bad device 0:2 0x8200 **
** Bad device 0:2 0x8200 **
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0: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
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
1650 bytes read in 30 ms (53.7 KiB/s)
gpio: pin 55 (gpio 55) value is 1
Loaded environment from /uEnv.txt
Importing environment from mmc ...
Checking if uenvcmd is set ...
gpio: pin 56 (gpio 56) value is 1
Running uenvcmd ...
1483 bytes read in 37 ms (39.1 KiB/s)
debug: [/boot/vmlinuz-4.4.54-ti-r93] ...
8652712 bytes read in 576 ms (14.3 MiB/s)
debug: [/boot/initrd.img-4.4.54-ti-r93] ...
5035153 bytes read in 346 ms (13.9 MiB/s)
debug: [/boot/dtbs/4.4.54-ti-r93/am335x-boneblack.dtb] ...
56827 bytes read in 113 ms (490.2 KiB/s)
debug: [console=tty0 console=ttyO0,115200n8 root=/dev/nfs 
nfsroot=192.168.1.2:/h
ome/doug/bbbfs rootfstype=ext4 rootwait fixrtc coherent_pool=1M 
net.ifnames=0 qu
iet cape_universal=enable] ...
debug: [bootz 0x8200 0x8808:4cd491 0x8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Using Device Tree in place at 8800, end 88010dfa

Starting kernel ...

[0.001037] clocksource_probe: no matching clocksources found
[2.058506] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[2.239707] omap_voltage_late_init: Voltage driver support not added
[2.247425] PM: Cannot get wkup_m3_ipc handle
Loading, please wait...
[4.837347]  remoteproc1: failed to load am335x-pru0-fw
[4.866502]  remoteproc1: request_firmware failed: -2
[4.871686] pru-rproc 4a334000.pru0: rproc_boot failed
[4.977254]  remoteproc1: failed to load am335x-pru1-fw
[4.983007]  remoteproc1: request_firmware failed: -2
[4.988172] pru-rproc 4a338000.pru1: rproc_boot failed
IP-Config: eth0 hardware address 80:30:dc:90:9b:da mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
IP-Config: eth0 hardware address 80:30:dc:90:9b:da mtu 1500 DHCP RARP
IP-Config: eth0 guessed broadcast address 192.168.1.255
IP-Config: eth0 complete (dhcp from 192.168.1.1):
 address: 192.168.1.128broadcast: 192.168.1.255netmask: 
255.255.255.0   
 gateway: 192.168.1.1  dns0 : 192.168.1.1  dns1   : 
0.0.0.0 
 rootserver: 192.168.1.1 rootpath: 
 filename  : 
[FAILED] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-tmpfiles-setup.service' for details.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Reached target System Time Synchronized.
 Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
 Starting LSB: Tune IDE hard disks...
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[FAILED] Failed to start Update UTMP about System Boot/Shutdown.
See 'systemctl status systemd-update-utmp.service' for details.
[DEPEND] Dependency failed for Update UTMP about System Runlevel Changes.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Stopped Network Time Synchronization.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[  OK  ] Started LSB: Tune IDE hard disks.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on 

[beagleboard] Re: DHCP issues

[Kurt Talke]

Jason,

After the IP address changes I’m unable to log in.

Basically, I flashed with Debian 8.8, then ran the configure_robotics_dt.sh 
script.

After rebooting,
I can no longer log in.

should be easy to duplicate.

-K

> On Aug 2, 2017, at 9:24 AM, Jason Kridner  wrote:
> 
> Can you provide a journal log?
> 
> Can you check the status of dnsmasq and connman processes?
> 
> Which script are you calling the "DT script"? 
> https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/install.sh
>  
> 
>  ?  
> https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/device_tree/configure_robotics_dt.sh
>  
> 
>  ? 
> 
> On Mon, Jul 31, 2017 at 6:08 PM Kurt Talke  > wrote:
> Hi Jason, James,
> 
> I’m running Debian 8.8 from 7/1/17, and I’m having an issue where the BBB no 
> longer shows up as the default IP 192.168.7.2
> 
> I’ve narrowed it down to the script which enables the device tree overlay, or 
> installing the robotics cape from source code.
> 
> Once I reboot, my BBB shows up as a self assigned IP 169.254.44.139, and I 
> can’t connect to it.
> 
> The DT script works for 8.7, but not 8.8 or the 9.1 versions.
> 
> Any ideas?
> 
> 
> 
> -Kurt
> -- 
> https://beagleboard.org/about 

-- 
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/E11C7FFC-B7DB-48FC-874F-CBDA1B3DFB41%40eng.ucsd.edu.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: DHCP issues

[Jason Kridner]

Can you provide a journal log?

Can you check the status of dnsmasq and connman processes?

Which script are you calling the "DT script"?
https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/install.sh
?

https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/device_tree/configure_robotics_dt.sh
 ?

On Mon, Jul 31, 2017 at 6:08 PM Kurt Talke  wrote:

> Hi Jason, James,
>
> I’m running Debian 8.8 from 7/1/17, and I’m having an issue where the BBB
> no longer shows up as the default IP 192.168.7.2
>
> I’ve narrowed it down to the script which enables the device tree overlay,
> or installing the robotics cape from source code.
>
> Once I reboot, my BBB shows up as a self assigned IP 169.254.44.139, and I
> can’t connect to it.
>
> The DT script works for 8.7, but not 8.8 or the 9.1 versions.
>
> Any ideas?
>
>
>
> -Kurt

-- 
https://beagleboard.org/about

-- 
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/CA%2BT6QP%3DgtjimgeirxFw14hoRxpOR8E145R%2BWzR5aVaPiRkpKtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Reading analog in on the stretch (9.1) images

[Mark A. Yoder]

It sounds like I can either have a Blue that boots as a robot, or boots as 
an embedded processor, but not both at the same time.
I need to see what it would take to remove the ADC from the robots control.

--Mark

On Tuesday, August 1, 2017 at 4:57:09 PM UTC-4, Hugh Briggs wrote:
>
> I have lived on BBB + Robotics Cape in James' world for some time. While I 
> haven't done this with a Blue, I suspect what I did can work there too. I 
> did do his installation (for a Rev C BBB and a Rev D Robotics Cape). With 
> Robert's help I put the Capemgr back in the DTs and added the capemgr 
> partno boot line for BB-ADC.  This seems to be a workable combination of 
> the two worlds. My premise is that I don't try to do both at once.  That 
> is, I don't run any of the rc_* apps or services while trying to read the 
> ADCs from /sys/bus/iio. So far it seems to work for me.
> Hugh
>
> On Monday, July 31, 2017 at 11:44:09 AM UTC-7, Mark A. Yoder wrote:
>
>> Yup, this is the Blue.
>> In there short term is there an easy way to turn off the robotics stuff 
>> and get easy access to the analog in?
>>
>> In the long term, what will it take to convert James' robot stuff to 
>> libiio?  I might take a shot at it if it isn't too hard.
>>
>> --Mark
>>
>> On Friday, July 28, 2017 at 5:56:30 PM UTC-4, RobertCNelson wrote:
>>>
>>> On Fri, Jul 28, 2017 at 4:40 PM, Mark A. Yoder  
>>> wrote: 
>>> > How do I read AIN on the latest images?  I don't know where to find it 
>>> in 
>>> > /sys/ 
>>>
>>> Hi Mark, 
>>>
>>> This is with the Blue right? 
>>>
>>> James' got the ADC tied up in mmap for the Robotic's cape library.. 
>>>
>>>
>>> https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/libraries/mmap/rc_mmap_gpio_adc.c
>>>  
>>>
>>> We need to convert his library to use libiio, then we can just enable 
>>> the ADC's as an iio device and share usage with the library.. 
>>>
>>> https://analogdevicesinc.github.io/libiio/ 
>>>
>>> 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/21c5fd9a-8961-4c81-a2f9-65e953512ee5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBone Blue; Pinout diagram / System Reference Manual ?

[Mark A. Yoder]

Wow, that's a great diagram.  It makes it very clear what pins are where.

--Mark

On Tuesday, August 1, 2017 at 8:15:30 PM UTC-4, nms...@gmail.com wrote:
>
>
> 
>
>
> On Sunday, July 9, 2017 at 4:23:09 AM UTC+1, Jeff Albrecht wrote:
>>
>> I'm looking for a detailed pinout of the BBBlue. Hopefully similar to 
>> this, or the many similar ones, for the BBB.
>>
>>
>>
>> The BBBlue FAQ has a Pinouts 
>> section 
>> with this picture. For instance I found the SPI connector but I don't know 
>> the pin numbers and pin names on the connector to hook up the hardware.
>>
>> [image: Image result for beaglebone blue pinout]
>>
>> I found Pin Multiplexing  on 
>> the Strasown Design site. It's getting closer but not a definitive 
>> reference for me. Perhaps this could be added to the Pinouts of the BBBlue 
>> FAQ.
>>
>> I have a 6-wire JST-SH connector. Not sure where pin 1 is on the 
>> connector or which pin is SCLK, MOSI, MIS0 SS* etc...
>>
>> Does a detailed pinout for the BBBlue exist?
>>
>> The BeagleBone Blue  page refers to the 
>> System Reference Manual on the github page but I'm not finding it. Does the 
>> System Reference Manual for the 'blue exist?
>>
>> Browse the BeagleBone Blue Github page 
>>  to find all available 
>> hardware specifications such as:
>>
>>
>>- Bill of materials
>>  - PCB source files
>>  - Manufacturing files
>>  - Schematic (PDF and source)
>>  - System Reference Manual
>>   
>>  
>>
>>
>>

-- 
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/dafcb626-f17e-455b-af9a-779a5329c672%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Disabling the cape EEPROM address range

[jake49388]

Is there a way to free the address range of the cape EEPROM (0x54-0x57) 
that will allow me to use that address range to connect an I2C devices 
through the headers on that address range? I have two I2C devices that use 
the same fixed address and would like to connect them to I2C1 and I2C2 
headers. I won't be using any capes in the project.

Thank you.
Jake

-- 
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/f91474f4-afb3-4c9e-9159-26913ee30a6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to know and decide loadaddr for zImage.

[dharminec1]

How to decide from what address zImage should start? 

-- 
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/e73c0096-9912-4b79-9ef1-ba2cd7c1af78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Change hdmi resolution not working (tried using xrandr and modifying uEnv.txt)

[Poppy Miller]

Hi,

I am using the latest MachineKit (downloaded from 
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit)
 
image and am trying to change the hdmi resolution to use it with a generic 
5 inch lcd screen. The resolution I require is 800x480.

What I have tried:

- xrandr: I tried following the instructions on the main beaglebone page (
http://elinux.org/Beagleboard:BeagleBoneBlack_HDMI#Forcing_A_Resolution)

Open terminal
Type export XAUTHORITY=`ls /var/run/gdm/auth-for-root-*/database` and hit 
enter.
Type export DISPLAY=:0.0 and hit enter.
Type xrandr --output HDMI-0 --mode 800x480 --rate 60. You can substitute 
different resolutions and refresh rates if you like. Hit enter.

This method gives an error "No protocol specified. Can't open display :0.0"

I have tried other lcd names such as "default" and "HDMI-0"

- modifying uEnv.txt: I tried adding "
kms_force_mode=video=HDMI-A-1:800x480M@60" to the uEnv.txt file (in both 
/boot and /media/machinekit/boot) as suggested at 
http://blog.machinekit.io/2013/07/custom-hdmi-resolution.html. I tried 
changing the name of the screen from "HDMI-A-1" to "HDMI-0" and "default".

This gives no errors, but also seems to have no effect on the resolution.


I am doing this on a tv screen which may not support the resolution I am 
trying to change it to. This is because I cannot see enough of the screen 
on the lcd at the wrong resolution to open the terminal and modify things- 
could this be causing a problem? Should I be changing the settings via 
putty instead?

Thank you in advance,

Cheers,
Poppy

-- 
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/8d4997f4-d399-4bef-8cd6-2d60393b270d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beaglebone black with Mpg123 and usb audio ?

[Riko Ho]

Dear Beagleboard Team Member,

How can I use snd-usb-audio with mpg123 on beaglebone black ?

I've tested with "aplay test.wav", and it works, but not yet with MP3..

Thanks,

--
*

/***/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/***/

*

--
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/5401e906-a3fe-a8c2-4ef8-b91008e3ed9c%40gmail.com.
For more options, visit https://groups.google.com/d/optout.