Re: [beagleboard] Re: possible workaround for BeagleBone Ethernet PHY problems

[Grzegorz G]

I don't have my design hardware, I've bought many bbb boards and some of 
them with ethernet issues after many hours working without any problems 
link becomes down. Does the kernel with -bone60 or greater suffix is the SW 
workaround? Is the power management of the LAN chip couse the problem?

below log from kernel when problems occur:
Dec  6 14:22:17 beaglebone kernel: [709664.393005] libphy: 4a101000.mdio:00 
- Link is Down
Dec  6 14:22:20 beaglebone kernel: [709666.620148] net eth0: initializing 
cpsw version 1.12 (0)
Dec  6 14:22:20 beaglebone kernel: [709666.622540] net eth0: phy 
4a101000.mdio:00 not found on slave 0
Dec  6 14:22:20 beaglebone kernel: [709666.628940] libphy: PHY 
4a101000.mdio:01 not found
Dec  6 14:22:20 beaglebone kernel: [709666.634052] net eth0: phy 
4a101000.mdio:01 not found on slave 1
Dec  6 14:22:20 beaglebone kernel: [709666.644534] IPv6: 
ADDRCONF(NETDEV_UP): eth0: link is not ready

and when no problems - at boot time:
Jan  1 01:00:13 beaglebone kernel: [6.183325] net eth0: initializing 
cpsw version 1.12 (0)
Jan  1 01:00:13 beaglebone kernel: [6.187580] net eth0: phy found : id 
is : 0x7c0f1
Jan  1 01:00:13 beaglebone kernel: [6.187608] libphy: PHY 
4a101000.mdio:01 not found
Jan  1 01:00:13 beaglebone kernel: [6.192679] net eth0: phy 
4a101000.mdio:01 not found on slave 1
Jan  1 01:00:13 beaglebone kernel: [6.224917] IPv6: 
ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan  1 01:00:13 beaglebone kernel: [6.580019] omap_rng 4831.rng: 
base address of priv is -97452032
Jan  1 01:00:13 beaglebone kernel: [6.614128] omap_rng 4831.rng: 
OMAP Random Number Generator ver. 20
Jan  1 01:00:13 beaglebone kernel: [   10.333416] libphy: 4a101000.mdio:00 
- Link is Up - 100/Full
Jan  1 01:00:13 beaglebone kernel: [   10.333488] IPv6: 
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Today I'll check current kernel version of the board with ethernet issues.

Regards

Grzegorz

W dniu poniedziałek, 12 grudnia 2016 23:03:09 UTC+1 użytkownik 
RobertCNelson napisał:
>
> On Mon, Dec 12, 2016 at 1:10 PM, Grzegorz G  > wrote: 
> > I wonder if the ethernet problems (link is down) has been resolved? 
> > 
>
> We have a software workaround, depending on your kernel version (uname 
> -r)... Otherwise if your designing your own hardware, make sure you 
> tie a gpio line the phy's reset line.. 
>
> On the bbb design, the phy reset is tied to the processor reset... 
>
> 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/9bb027f6-8bcd-4b19-8baf-cb238f3bb1bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBBWL ifconfig...something missing?

[Mark]

Robert!

Much better. I get WL/BT leds fully lit, which I neglected to mention were 
previously unresponsive. But USR0 led is kind of in tachycardia. OK, heart 
rate is down now.

Added your line below line for 1835 which was commented out...

##BeagleBone Black: wl1835
#dtb=am335x-boneblack-wl1835mod.dtb

##Added per RCN
dtb=am335x-boneblack-wireless.dtb
 
On the reboot, am unable to shell in. So, will reflash your 12-12, swap the 
comment lines in uEnv.txt and reboot for a looksee.

Thank you for catching that line in the output I attached.
Mark


-- 
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/d2f16708-73e2-42af-a137-f60804f05289%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] [BBB/BBG] RS485 read after write problem by linux 485 serial system call

[張皓傑]

Hi all

I'm useing debian 7.11(kernel 3.8) version image.
I'm trying to use rs485 cape on BBB or BBG. Below are the cape I use.
485 CAN CAPE
http://www.waveshare.com/wiki/RS485_CAN_CAPE
485 CLICK BOARD
http://www.mikroe.com/click/rs485-3.3v/

As I know these boards don't have capability to auto handle read/write mode 
switching.
I try to use linux rs485 mode to auto handle switching problem.
The attached file is my sample code.

My problem is if I read data after writing, the receiving data will add a 
redundant data(0x00) at the beginning of the buffer.
Below is the result.
This is modbus command, that due to the redundant data, the modbus command 
will be failed.
So I use raw command to get data.

send: 01 04 00 00 00 01 31 CA
receive: 00 01 04 02 01 3E 39 70

send: 01 04 00 01 00 01 60 0A
receive: 00 01 04 02 00 E2 39 79

send: 02 04 00 00 00 01 31 F9
receive: 00 02 04 02 00 BA 7C 83

send: 02 04 00 01 00 01 60 39
receive: 00 02 04 02 00 FA 7D 73

send: 03 04 00 00 00 01 30 28
receive: 00 03 04 02 03 11 00 0C

send: 03 04 00 01 00 01 61 E8
receive: 00 03 04 02 00 DE 40 A8

This redundant data is not read data from modbus device. I use another 
rs485 cable to monitor the data will not have this redundant data.
Like this:
send: 01 04 00 00 00 01 31 CA
receive: 01 04 02 01 3E 39 70

If I only use receive mode, there will not be any redundant data in the 
buffer.

As I tried, kernel 4.4 cannot work 485 system call.

I'm not familiar in kernel, does anyone could give me some advice?

Many thanks,
Harvey 

-- 
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/c220e9fe-f495-4e4b-b94b-52379e0b94a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
# -*- coding: utf-8 -*-
import minimalmodbus
import serial, fcntl, struct, time
from datetime import datetime

ROOM1 = '1'
TANK1 = '1'

ser = serial.Serial(
port='/dev/ttyO2', 
baudrate=9600, 
timeout=1,
parity=serial.PARITY_NONE,
stopbits=serial.STOPBITS_ONE,
bytesize=serial.EIGHTBITS
)

# Standard Linux RS485 ioctl:
TIOCSRS485 = 0x542F
 
# define serial_rs485 struct per Michael Musset's patch that adds gpio RE/DE 
# control:
# (https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.8/patches/fixes/0007-omap-RS485-support-by-Michael-Musset.patch#L30)
SER_RS485_ENABLED = (1 << 0)
SER_RS485_RTS_ON_SEND = (1 << 1)
SER_RS485_RTS_AFTER_SEND  = (1 << 2)
SER_RS485_RTS_BEFORE_SEND = (1 << 3)
SER_RS485_USE_GPIO= (1 << 5)
 
# Enable RS485 mode using a GPIO pin to control RE/DE: 
RS485_FLAGS = SER_RS485_ENABLED | SER_RS485_USE_GPIO 
# With this configuration the GPIO pin will be high when transmitting and low
# when not
 
# If SER_RS485_RTS_ON_SEND and SER_RS485_RTS_AFTER_SEND flags are included the
# RE/DE signal will be inverted, i.e. low while transmitting
 
# The GPIO pin to use, using the Kernel numbering: 
RS485_RTS_GPIO_PIN = 50 # GPIO1_18 -> GPIO(1)_(18) = (1)*32+(18) = 50
 
# Pack the config into 8 consecutive unsigned 32-bit values:
# (per  struct serial_rs485 in patched serial.h)
serial_rs485 = struct.pack('', 
   RS485_FLAGS,# config flags
   0,  # delay in us before send
   0,  # delay in us after send
   RS485_RTS_GPIO_PIN, # the pin number used for DE/RE
   0, 0, 0, 0  # padding - space for more values 
   )
 
# Apply the ioctl to the open ttyO2 file descriptor:
fd=ser.fileno()
fcntl.ioctl(fd, TIOCSRS485, serial_rs485)
 
# Send some bytes:
# GPIO1_16 should be low here
time.sleep(0.2)

print ('connect to port %s' %ser.port)

now = datetime.now().strftime('%Y-%m-%d %H:%M:%S')  #this will remove decimal point value
date = str(datetime.now().date().today())
print('date: %s' %now)

print('test in Room %s tank %s\n' %(ROOM1, TANK1))

cmd1 = b'\x01\x04\x00\x00\x00\x01\x31\xCA'
ser.write(cmd1)
out = bytearray(ser.read(8))
#print('%02X %02X %02X %02X %02X %02X %02X %02X' %(out[0], out[1], out[2], out[3], out[4], out[5], out[6], out[7]))
salinity = (out[4] * (16**2) + out[5]) / 100.0

print('Salinity value: %.2f%%' %salinity)

cmd2 = b'\x01\x04\x00\x01\x00\x01\x60\x0A'
ser.write(cmd2)
out = bytearray(ser.read(8))
#print('%02X %02X %02X %02X %02X %02X %02X %02X' %(out[0], out[1], out[2], out[3], out[4], out[5], out[6], out[7]))
temp = (out[4] * (16**2) + out[5]) / 10.0

a = u'\u2103'
print('temperature value: %.1f %s' %(temp, a.encode('utf8')))

line = ROOM1 + ' ' + TANK1 + ' ' + \
   now + ' ' + str(salinity) + ' ' + str(temp)
print('data format: %s' %line)

time.sleep(0.1)
print('')

[beagleboard] [BBB] RS485 read after write problem by linux rs485 mode

[張皓傑]

Hi all

I'm useing debian 7.11(kernel 3.8) version image.
I'm trying to use rs485 cape on BBB or BBG. Below are the cape I use.
485 CAN CAPE
http://www.waveshare.com/wiki/RS485_CAN_CAPE
485 CLICK BOARD
http://www.mikroe.com/click/rs485-3.3v/

As I know these boards don't have capability to auto handle read/write mode 
switching.
I try to use linux rs485 mode to auto handle switching problem.
The attached file is my sample code.

My problem is if I read data after writing, the receiving data will add a 
redundant data(0x00) at the beginning of the buffer.
Below is the result.
This is modbus command, that due to the redundant data, the modbus command 
will be failed.
So I use raw command to get data.

send: 01 04 00 00 00 01 31 CA
receive: 00 01 04 02 01 3E 39 70

send: 01 04 00 01 00 01 60 0A
receive: 00 01 04 02 00 E2 39 79

send: 02 04 00 00 00 01 31 F9
receive: 00 02 04 02 00 BA 7C 83

send: 02 04 00 01 00 01 60 39
receive: 00 02 04 02 00 FA 7D 73

send: 03 04 00 00 00 01 30 28
receive: 00 03 04 02 03 11 00 0C

send: 03 04 00 01 00 01 61 E8
receive: 00 03 04 02 00 DE 40 A8

This redundant data is not read data from modbus device. I use another 
rs485 cable to monitor the data will not have this redundant data.
Like this:
send: 01 04 00 00 00 01 31 CA
receive: 01 04 02 01 3E 39 70

If I only use receive mode, there will not be any redundant data in the 
buffer.

As I tried, kernel 4.4 cannot work 485 system call.

I'm not familiar in kernel, does anyone could give me some advice?

Many thanks,
Harvey 

-- 
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/c1f40c4e-e607-4d40-aa94-6c392905372b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
# -*- coding: utf-8 -*-
import minimalmodbus
import serial, fcntl, struct, time
from datetime import datetime

ROOM1 = '1'
TANK1 = '1'

ser = serial.Serial(
port='/dev/ttyO2', 
baudrate=9600, 
timeout=1,
parity=serial.PARITY_NONE,
stopbits=serial.STOPBITS_ONE,
bytesize=serial.EIGHTBITS
)

# Standard Linux RS485 ioctl:
TIOCSRS485 = 0x542F
 
# define serial_rs485 struct per Michael Musset's patch that adds gpio RE/DE 
# control:
# (https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.8/patches/fixes/0007-omap-RS485-support-by-Michael-Musset.patch#L30)
SER_RS485_ENABLED = (1 << 0)
SER_RS485_RTS_ON_SEND = (1 << 1)
SER_RS485_RTS_AFTER_SEND  = (1 << 2)
SER_RS485_RTS_BEFORE_SEND = (1 << 3)
SER_RS485_USE_GPIO= (1 << 5)
 
# Enable RS485 mode using a GPIO pin to control RE/DE: 
RS485_FLAGS = SER_RS485_ENABLED | SER_RS485_USE_GPIO 
# With this configuration the GPIO pin will be high when transmitting and low
# when not
 
# If SER_RS485_RTS_ON_SEND and SER_RS485_RTS_AFTER_SEND flags are included the
# RE/DE signal will be inverted, i.e. low while transmitting
 
# The GPIO pin to use, using the Kernel numbering: 
RS485_RTS_GPIO_PIN = 50 # GPIO1_18 -> GPIO(1)_(18) = (1)*32+(18) = 50
 
# Pack the config into 8 consecutive unsigned 32-bit values:
# (per  struct serial_rs485 in patched serial.h)
serial_rs485 = struct.pack('', 
   RS485_FLAGS,# config flags
   0,  # delay in us before send
   0,  # delay in us after send
   RS485_RTS_GPIO_PIN, # the pin number used for DE/RE
   0, 0, 0, 0  # padding - space for more values 
   )
 
# Apply the ioctl to the open ttyO2 file descriptor:
fd=ser.fileno()
fcntl.ioctl(fd, TIOCSRS485, serial_rs485)
 
# Send some bytes:
# GPIO1_16 should be low here
time.sleep(0.2)

print ('connect to port %s' %ser.port)

now = datetime.now().strftime('%Y-%m-%d %H:%M:%S')  #this will remove decimal point value
date = str(datetime.now().date().today())
print('date: %s' %now)

print('test in Room %s tank %s\n' %(ROOM1, TANK1))

cmd1 = b'\x01\x04\x00\x00\x00\x01\x31\xCA'
ser.write(cmd1)
out = bytearray(ser.read(8))
#print('%02X %02X %02X %02X %02X %02X %02X %02X' %(out[0], out[1], out[2], out[3], out[4], out[5], out[6], out[7]))
salinity = (out[4] * (16**2) + out[5]) / 100.0

print('Salinity value: %.2f%%' %salinity)

cmd2 = b'\x01\x04\x00\x01\x00\x01\x60\x0A'
ser.write(cmd2)
out = bytearray(ser.read(8))
#print('%02X %02X %02X %02X %02X %02X %02X %02X' %(out[0], out[1], out[2], out[3], out[4], out[5], out[6], out[7]))
temp = (out[4] * (16**2) + out[5]) / 10.0

a = u'\u2103'
print('temperature value: %.1f %s' %(temp, a.encode('utf8')))

line = ROOM1 + ' ' + TANK1 + ' ' + \
   now + ' ' + str(salinity) + ' ' + str(temp)
print('data format: %s' %line)

time.sleep(0.1)
print('')

[beagleboard] RS485 read after write problem by linux rs485 mode

[張皓傑]

Hi all

I'm using BBB debian 7.11 (kernel 3.8) version image.
I'm trying to use RS485 cape on BBB or BBG. The product is like below link.
485 CAN CAPE
http://www.waveshare.com/wiki/RS485_CAN_CAPE
485 CLICK BOARD
http://www.mikroe.com/click/rs485-3.3v/

As I know, these board don't have capability to auto change 
transmit/receive mode.
I try to use linux serial rs485 system call to control transmit/receive 
mode.
And I surfer from one problem is if I read data after writing, I will 
receive a 0x00 byte in the beginning of the buffer.
This is not a real data. I use another rs485 device to monitor cable, and 
doesn't receive this redundant data.

The attached file is my sample code. This is modbus command. Due to this 
redundant data, modbus command will be failed.
So I use raw command to read write data. And the result is as below.

send: 01 04 00 00 00 01 31 CA
receive: 00 01 04 02 01 3E 39 70

send: 01 04 00 01 00 01 60 0A
receive: 00 01 04 02 00 E2 39 79

send: 02 04 00 00 00 01 31 F9
receive: 00 02 04 02 00 BA 7C 83

send: 02 04 00 01 00 01 60 39
receive: 00 02 04 02 00 FA 7D 73

send: 03 04 00 00 00 01 30 28
receive: 00 03 04 02 03 11 00 0C

send: 03 04 00 01 00 01 61 E8
receive: 00 03 04 02 00 DE 40 A8


If I only use receive mode, there will not be any redundant data(0x00) in 
the buffer.

Another problem is rs485 mode will not work in kernel 4.4 as I tried.

Could anyone give me some advice that I'm not familiar in kernel.


Many thanks,
Harvey


-- 
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/9d07b367-ab24-4c89-8a8f-9d5d426764c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
# -*- coding: utf-8 -*-
import minimalmodbus
import serial, fcntl, struct, time
from datetime import datetime

ROOM1 = '1'
TANK1 = '1'

ser = serial.Serial(
port='/dev/ttyO2', 
baudrate=9600, 
timeout=1,
parity=serial.PARITY_NONE,
stopbits=serial.STOPBITS_ONE,
bytesize=serial.EIGHTBITS
)

# Standard Linux RS485 ioctl:
TIOCSRS485 = 0x542F
 
# define serial_rs485 struct per Michael Musset's patch that adds gpio RE/DE 
# control:
# (https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.8/patches/fixes/0007-omap-RS485-support-by-Michael-Musset.patch#L30)
SER_RS485_ENABLED = (1 << 0)
SER_RS485_RTS_ON_SEND = (1 << 1)
SER_RS485_RTS_AFTER_SEND  = (1 << 2)
SER_RS485_RTS_BEFORE_SEND = (1 << 3)
SER_RS485_USE_GPIO= (1 << 5)
 
# Enable RS485 mode using a GPIO pin to control RE/DE: 
RS485_FLAGS = SER_RS485_ENABLED | SER_RS485_USE_GPIO 
# With this configuration the GPIO pin will be high when transmitting and low
# when not
 
# If SER_RS485_RTS_ON_SEND and SER_RS485_RTS_AFTER_SEND flags are included the
# RE/DE signal will be inverted, i.e. low while transmitting
 
# The GPIO pin to use, using the Kernel numbering: 
RS485_RTS_GPIO_PIN = 50 # GPIO1_18 -> GPIO(1)_(18) = (1)*32+(18) = 50
 
# Pack the config into 8 consecutive unsigned 32-bit values:
# (per  struct serial_rs485 in patched serial.h)
serial_rs485 = struct.pack('', 
   RS485_FLAGS,# config flags
   0,  # delay in us before send
   0,  # delay in us after send
   RS485_RTS_GPIO_PIN, # the pin number used for DE/RE
   0, 0, 0, 0  # padding - space for more values 
   )
 
# Apply the ioctl to the open ttyO2 file descriptor:
fd=ser.fileno()
fcntl.ioctl(fd, TIOCSRS485, serial_rs485)
 
# Send some bytes:
# GPIO1_16 should be low here
time.sleep(0.2)

print ('connect to port %s' %ser.port)

now = datetime.now().strftime('%Y-%m-%d %H:%M:%S')  #this will remove decimal point value
date = str(datetime.now().date().today())
print('date: %s' %now)

print('test in Room %s tank %s\n' %(ROOM1, TANK1))

cmd1 = b'\x01\x04\x00\x00\x00\x01\x31\xCA'
ser.write(cmd1)
out = bytearray(ser.read(8))
#print('%02X %02X %02X %02X %02X %02X %02X %02X' %(out[0], out[1], out[2], out[3], out[4], out[5], out[6], out[7]))
salinity = (out[4] * (16**2) + out[5]) / 100.0

print('Salinity value: %.2f%%' %salinity)

cmd2 = b'\x01\x04\x00\x01\x00\x01\x60\x0A'
ser.write(cmd2)
out = bytearray(ser.read(8))
#print('%02X %02X %02X %02X %02X %02X %02X %02X' %(out[0], out[1], out[2], out[3], out[4], out[5], out[6], out[7]))
temp = (out[4] * (16**2) + out[5]) / 10.0

a = u'\u2103'
print('temperature value: %.1f %s' %(temp, a.encode('utf8')))

line = ROOM1 + ' ' + TANK1 + ' ' + \
   now + ' ' + str(salinity) + ' ' + str(temp)
print('data format: %s' %line)

time.sleep(0.1)
print('')

cmd1 = b'\x02\x04\x00\x00\x00\x01\x31\xF9'
ser.writ

Re: [beagleboard] BBBWL ifconfig...something missing?

[Robert Nelson]

Uhoh!!

[2.351843] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,,'

We have a miss-programmed eeprom!!

Mark, is this a pre-production BeagleBone Black Wireless?

(is the pcb green or black?)

First let's double check the wl1835 works, then i'll walk you thru
re-programing the eeprom..

in /boot/uEnv.txt

add:

dtb=am335x-boneblack-wireless.dtb

and reboot..

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/CAOCHtYjdNUhFx04KKpL-rmj9H8KDb7fBH7LN%2Bc%3DDR5ReG1fFZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBBWL ifconfig...something missing?

[Mark]

Hi Robert --

Flashed your 12-12 image 
"BBB-blank-debian-8.6-iot-armhf-2016-12-12-4gb.img.xz".

Recv following:

root@beaglebone:~# dmesg | grep wlcore
root@beaglebone:~#

And...

root@beaglebone:~# ifconfig -a
can0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00   
   

  -00
  NOARP  MTU:16  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:10
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  Interrupt:198

can1  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00   
   

  -00
  NOARP  MTU:16  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:10
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  Interrupt:199

eth0  Link encap:Ethernet  HWaddr 50:65:83:d6:06:a5
  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:2408 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2408 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1
  RX bytes:186080 (181.7 KiB)  TX bytes:186080 (181.7 KiB)

usb0  Link encap:Ethernet  HWaddr 50:65:83:d6:06:a7
  inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
  inet6 addr: fe80::5265:83ff:fed6:6a7/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1106 errors:0 dropped:0 overruns:0 frame:0
  TX packets:163 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:294464 (287.5 KiB)  TX bytes:37349 (36.4 KiB)


What do you think?
Mark

-- 
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/72f65fbd-9c8b-4620-8aad-c112efdad36c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Using username "root".
Debian GNU/Linux 8

BeagleBoard.org Debian Image 2016-12-12

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

default username:password is [debian:temppwd]

Last login: Tue Dec 13 02:04:10 2016 from 192.168.7.1
root@beaglebone:~# cat /etc/dogtag
BeagleBoard.org Debian Image 2016-12-12
root@beaglebone:~# cat /var/lib/connman/settings
[global]
OfflineMode=false

[Wired]
Enable=true
Tethering=false

[WiFi]
Enable=true
Tethering=true
Tethering.Identifier=BeagleBone-06A5
Tethering.Passphrase=BeagleBone

[Gadget]
Enable=false
Tethering=false

[P2P]
Enable=false
Tethering=false

[Bluetooth]
Enable=true
Tethering=false
root@beaglebone:~#
root@beaglebone:~#
root@beaglebone:~# ifconfig -a
can0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
-00
  NOARP  MTU:16  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:10
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  Interrupt:198

can1  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
-00
  NOARP  MTU:16  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:10
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  Interrupt:199

eth0  Link encap:Ethernet  HWaddr 50:65:83:d6:06:a5
  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:2408 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2408 errors:0 dropped:0 overruns:0 carrier:0

Re: [beagleboard] BBBWL ifconfig...something missing?

[Mark]

Hi Robert --

>From the most recent 11-06-2016 image just returns...nothing

root@beaglebone:~# cat /etc/dogtag
BeagleBoard.org Debian Image 2016-11-06
root@beaglebone:~# dmesg | grep wlcore
root@beaglebone:~#

BTW, search of an earlier dmesg output (12-05img) showed no results on 
"wl*", "wl18*" in the text file. See attached.

Will test your 12-12 IOT and respond back here.

-- 
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/d1661468-858a-4fff-a6ef-711d03136a2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
root@beaglebone:~# dmesg
[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 4.4.36-ti-r71 (root@a1-imx6q-wandboard-2gb) (gcc 
version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Sun Dec 4 02:56:26 UTC 2016
[0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache
[0.00] Machine model: TI AM335x BeagleBone Black
[0.00] cma: Reserved 48 MiB at 0x9c80
[0.00] Memory policy: Data cache writeback
[0.00] On node 0 totalpages: 130560
[0.00] free_area_init_node: node 0, pgdat c105d2c0, node_mem_map 
df961000
[0.00]   Normal zone: 1152 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 130560 pages, LIFO batch:31
[0.00] CPU: All CPU(s) started in SVC mode.
[0.00] AM335X ES2.1 (sgx neon )
[0.00] PERCPU: Embedded 13 pages/cpu @df917000 s24320 r8192 d20736 
u53248
[0.00] pcpu-alloc: s24320 r8192 d20736 u53248 alloc=13*4096
[0.00] pcpu-alloc: [0] 0
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 129408
[0.00] Kernel command line: console=ttyO0,115200n8 
root=UUID=bdc8ed7a-da53-41a5-9616-f449ceb87456 ro rootfstype=ext4 rootwait 
coherent_pool=1M quiet cape_universal=enable
[0.00] PID hash table entries: 2048 (order: 1, 8192 bytes)
[0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[0.00] Memory: 444808K/522240K available (11365K kernel code, 917K 
rwdata, 3796K rodata, 748K init, 907K bss, 28280K reserved, 49152K 
cma-reserved, 0K highmem)
[0.00] Virtual kernel memory layout:
vector  : 0x - 0x1000   (   4 kB)
fixmap  : 0xffc0 - 0xfff0   (3072 kB)
vmalloc : 0xe080 - 0xff80   ( 496 MB)
lowmem  : 0xc000 - 0xe000   ( 512 MB)
pkmap   : 0xbfe0 - 0xc000   (   2 MB)
modules : 0xbf00 - 0xbfe0   (  14 MB)
  .text : 0xc0008000 - 0xc0ed694c   (15163 kB)
  .init : 0xc0ed7000 - 0xc0f92000   ( 748 kB)
  .data : 0xc0f92000 - 0xc1077528   ( 918 kB)
   .bss : 0xc107a000 - 0xc115cfa8   ( 908 kB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] Hierarchical RCU implementation.
[0.00]  Build-time adjustment of leaf fanout to 32.
[0.00]  RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1.
[0.00] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=1
[0.00] NR_IRQS:16 nr_irqs:16 16
[0.00] IRQ: Found an INTC at 0xfa20 (revision 5.0) with 128 
interrupts
[0.00] OMAP clockevent source: timer2 at 2400 Hz
[0.14] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 
89478484971ns
[0.36] clocksource: timer1: mask: 0x max_cycles: 0x, 
max_idle_ns: 79635851949 ns
[0.48] OMAP clocksource: timer1 at 2400 Hz
[0.001354] clocksource_probe: no matching clocksources found
[0.001558] Console: colour dummy device 80x30
[0.001585] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[0.001594] This ensures that you still see kernel messages. Please
[0.001600] update your kernel commandline.
[0.001620] Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656)
[0.046817] pid_max: default: 32768 minimum: 301
[0.046970] Security Framework initialized
[0.046984] Yama: becoming mindful.
[0.047021] AppArmor: AppArmor disabled by boot time parameter
[0.047190] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.047201] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.048050] Initializing cgroup subsys io
[0.048082] Initializing cgroup subsys memory
[0.048127] Initializing cgroup subsys devices
[0.048146]

Re: [beagleboard] BBBWL ifconfig...something missing?

[treadwellfrankie via BeagleBoard]

On Tue, 12/13/16, Robert Nelson  wrote:

 Subject: Re: [beagleboard] BBBWL ifconfig...something missing?
 To: "Beagle Board" 
 Cc: mkap...@gmail.com
 Date: Tuesday, December 13, 2016, 2:50 AM
 
 Hi Mark,
 
 On Mon, Dec 12, 2016 at 6:08
 PM, Mark 
 wrote:
 > Hello --
 >
 > New post as @yahoo spam cluttered up
 previous.
 >
 > Per RC
 Nelson suggestion of booting from different image obtainable
 at
 > http://beagleboard.org/latest-images, I
 made three attempts at resolving
 > lack
 of wifi on a new BBBWL.
 >
 > Three images used in these tests:
 > 1. Debian 8.6 2016-11-06 4GB SD LXQT
 > https://debian.beagleboard.org/images/bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img.xz
 >
 > 2. Debian 8.6
 2016-12-09 4GB SD IoT
 > https://debian.beagleboard.org/images/bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz
 > NOTE: This image drops my shell connxn
 after a couple minutes.
 >
 > 3.
 BBBW-blank-debian-8.6-lxqt-4gb-armhf-2016-12-05-4gb.img.xz,
 alluded to by
 > RC Nelson in response to
 post "Setup Wifi on Beaglebone Black Wireless"
 this
 > sub-forum.
 >
 > Below terminal output is consistent across
 all three images listed above: If
 >
 anyone has an idea what I am doing incorrectly, assistance
 will be very much
 > appreciated.
 > Thank you,
 > Mark
 >
 >
 >
 root@beaglebone:~#
 ifconfig
 > eth0      Link
 encap:Ethernet  HWaddr 50:65:83:d6:06:a5
 >           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
 >
 > lo        Link 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:1128 errors:0 dropped:0
 overruns:0 frame:0
 >       
    TX packets:1128 errors:0 dropped:0 overruns:0
 carrier:0
 >       
    collisions:0 txqueuelen:1
 >           RX bytes:87520
 (85.4 KiB)  TX bytes:87520 (85.4 KiB)
 >
 > usb0      Link
 encap:Ethernet  HWaddr 50:65:83:d6:06:a7
 >           inet
 addr:192.168.7.2  Bcast:192.168.7.3 
 Mask:255.255.255.252
 >       
    inet6 addr: fe80::5265:83ff:fed6:6a7/64
 Scope:Link
 >           UP
 BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
 >           RX packets:662
 errors:0 dropped:0 overruns:0 frame:0
 > 
          TX packets:130 errors:0 dropped:0
 overruns:0 carrier:0
 >       
    collisions:0 txqueuelen:1000
 >           RX bytes:179124
 (174.9 KiB)  TX bytes:30188 (29.4 KiB)
 >
 root@beaglebone:~#
 iwconfig
 > lo        no wireless
 extensions.
 >
 > eth0 
     no wireless extensions.
 >
 > usb0      no wireless extensions.
 >
 > can0      no
 wireless extensions.
 >
 > can1      no wireless extensions.
 >
 > root@beaglebone:~#
 connmanctl
 > connmanctl>
 technologies
 >
 /net/connman/technology/ethernet
 >   Name = Wired
 >   Type = ethernet
 >   Powered = True
 >   Connected = False
 >   Tethering = False
 > connmanctl> tether wifi disable
 > Error disabling wifi tethering: Method
 "SetProperty" with signature "sv" on
 > interface
 "net.connman.Technology" doesn't exist
 >
 > connmanctl> enable
 wifi
 > Error wifi: Method
 "SetProperty" with signature "sv" on
 interface
 >
 "net.connman.Technology" doesn't exist
 >
 > connmanctl> scan
 wifi
 > Error
 /net/connman/technology/wifi: Method "Scan" with
 signature "" on
 > interface
 "net.connman.Technology" doesn't exist
 >
 > connmanctl>
 services
 >
 >
 connmanctl> quit
 > root@beaglebone:~#
 
 
 can you
 test:
 
 https://rcn-ee.net/rootfs/bb.org/testing/2016-12-12/iot/
 
 made a few more changes to
 usb0 and wlan0, i'm still chasing down a
 new wlcore issue i'm seeing on two of my
 boards.. (oddly on one, only
 when using the
 microSD)
 
 so, can you also
 share:
 
 dmesg | grep
 wlcore
 
 [   48.035440] wlcore: wl18xx HW:
 183x or 180x, PG 2.2 (ROM 0x11)
 [   48.055657] genirq: Failed to
 request resources for wl18xx (irq 54)
 on
 irqchip 44e07000.gpio
 [   48.170563] wlcore: ERROR
 interrupt configuration failed
 
 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/CAOCHtYh4Db4J1_ZGObEuyLJe7v07XgAhzS8g%2BokL-8804WSOaA%40mail.gmail.com.
 For
 more options, visit https://groups.google.com/d/optout.
 nlaturarea monarhiei la 30 decembrie 1947 a creat conditiile pentru o 
modificare silita si fortata a formei de guvernare in Romania. Ea a marcat un 
pas decisiv pe calea preluarii intregii puteri politice de

Re: [beagleboard] BBBWL ifconfig...something missing?

[Robert Nelson]

Hi Mark,

On Mon, Dec 12, 2016 at 6:08 PM, Mark  wrote:
> Hello --
>
> New post as @yahoo spam cluttered up previous.
>
> Per RC Nelson suggestion of booting from different image obtainable at
> http://beagleboard.org/latest-images, I made three attempts at resolving
> lack of wifi on a new BBBWL.
>
> Three images used in these tests:
> 1. Debian 8.6 2016-11-06 4GB SD LXQT
> https://debian.beagleboard.org/images/bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img.xz
>
> 2. Debian 8.6 2016-12-09 4GB SD IoT
> https://debian.beagleboard.org/images/bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz
> NOTE: This image drops my shell connxn after a couple minutes.
>
> 3. BBBW-blank-debian-8.6-lxqt-4gb-armhf-2016-12-05-4gb.img.xz, alluded to by
> RC Nelson in response to post "Setup Wifi on Beaglebone Black Wireless" this
> sub-forum.
>
> Below terminal output is consistent across all three images listed above: If
> anyone has an idea what I am doing incorrectly, assistance will be very much
> appreciated.
> Thank you,
> Mark
>
>
> root@beaglebone:~# ifconfig
> eth0  Link encap:Ethernet  HWaddr 50:65:83:d6:06:a5
>   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:1128 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:1128 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1
>   RX bytes:87520 (85.4 KiB)  TX bytes:87520 (85.4 KiB)
>
> usb0  Link encap:Ethernet  HWaddr 50:65:83:d6:06:a7
>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>   inet6 addr: fe80::5265:83ff:fed6:6a7/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:662 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:179124 (174.9 KiB)  TX bytes:30188 (29.4 KiB)
> root@beaglebone:~# iwconfig
> lono wireless extensions.
>
> eth0  no wireless extensions.
>
> usb0  no wireless extensions.
>
> can0  no wireless extensions.
>
> can1  no wireless extensions.
>
> root@beaglebone:~# connmanctl
> connmanctl> technologies
> /net/connman/technology/ethernet
>   Name = Wired
>   Type = ethernet
>   Powered = True
>   Connected = False
>   Tethering = False
> connmanctl> tether wifi disable
> Error disabling wifi tethering: Method "SetProperty" with signature "sv" on
> interface "net.connman.Technology" doesn't exist
>
> connmanctl> enable wifi
> Error wifi: Method "SetProperty" with signature "sv" on interface
> "net.connman.Technology" doesn't exist
>
> connmanctl> scan wifi
> Error /net/connman/technology/wifi: Method "Scan" with signature "" on
> interface "net.connman.Technology" doesn't exist
>
> connmanctl> services
>
> connmanctl> quit
> root@beaglebone:~#


can you test:

https://rcn-ee.net/rootfs/bb.org/testing/2016-12-12/iot/

made a few more changes to usb0 and wlan0, i'm still chasing down a
new wlcore issue i'm seeing on two of my boards.. (oddly on one, only
when using the microSD)

so, can you also share:

dmesg | grep wlcore

[   48.035440] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[   48.055657] genirq: Failed to request resources for wl18xx (irq 54)
on irqchip 44e07000.gpio
[   48.170563] wlcore: ERROR interrupt configuration failed

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/CAOCHtYh4Db4J1_ZGObEuyLJe7v07XgAhzS8g%2BokL-8804WSOaA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBBWL ifconfig...something missing?

[Mark]

Hello --

New post as @yahoo spam cluttered up previous.

Per RC Nelson suggestion of booting from different image obtainable 
at http://beagleboard.org/latest-images, I made three attempts at resolving 
lack of wifi on a new BBBWL.

Three images used in these tests:
1. Debian 8.6 2016-11-06 4GB SD LXQT
https://debian.beagleboard.org/images/bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img.xz

2. Debian 8.6 2016-12-09 4GB SD IoT
https://debian.beagleboard.org/images/bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz
NOTE: This image drops my shell connxn after a couple minutes.

3. BBBW-blank-debian-8.6-lxqt-4gb-armhf-2016-12-05-4gb.img.xz, alluded to 
by RC Nelson in response to post "Setup Wifi on Beaglebone Black Wireless" 
this sub-forum.

Below terminal output is consistent across all three images listed above: 
If anyone has an idea what I am doing incorrectly, assistance will be very 
much appreciated.
Thank you,
Mark


root@beaglebone:~# ifconfig
eth0  Link encap:Ethernet  HWaddr 50:65:83:d6:06:a5
  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:1128 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1128 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1
  RX bytes:87520 (85.4 KiB)  TX bytes:87520 (85.4 KiB)

usb0  Link encap:Ethernet  HWaddr 50:65:83:d6:06:a7
  inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
  inet6 addr: fe80::5265:83ff:fed6:6a7/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:662 errors:0 dropped:0 overruns:0 frame:0
  TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:179124 (174.9 KiB)  TX bytes:30188 (29.4 KiB)
root@beaglebone:~# iwconfig
lono wireless extensions.

eth0  no wireless extensions.

usb0  no wireless extensions.

can0  no wireless extensions.

can1  no wireless extensions.

root@beaglebone:~# connmanctl
connmanctl> technologies
/net/connman/technology/ethernet
  Name = Wired
  Type = ethernet
  Powered = True
  Connected = False
  Tethering = False
connmanctl> tether wifi disable
Error disabling wifi tethering: Method "SetProperty" with signature "sv" on 
interface "net.connman.Technology" doesn't exist

connmanctl> enable wifi
Error wifi: Method "SetProperty" with signature "sv" on interface 
"net.connman.Technology" doesn't exist

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

connmanctl> services

connmanctl> quit
root@beaglebone:~#

-- 
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/a0c6124e-b558-40d4-9cc0-6da182dea73f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: possible workaround for BeagleBone Ethernet PHY problems

[Gerald Coley]

GPIO line as a reset only works it you configure all the lines on the MII
as inputs before you pulse the GPIO line..

Gerald


On Mon, Dec 12, 2016 at 4:02 PM, Robert Nelson 
wrote:

> On Mon, Dec 12, 2016 at 1:10 PM, Grzegorz G  wrote:
> > I wonder if the ethernet problems (link is down) has been resolved?
> >
>
> We have a software workaround, depending on your kernel version (uname
> -r)... Otherwise if your designing your own hardware, make sure you
> tie a gpio line the phy's reset line..
>
> On the bbb design, the phy reset is tied to the processor reset...
>
> 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/CAOCHtYi%3Dsc%3Dp5U_02uUe8HJCX6urRj9h%
> 2B9HN3tTM07bH1oA%3D%2Bg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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/CAHK_S%2BfbeKhfnX1Hg2b5U8u6mb7Mg%2B6OsDRnpGwGBFbGqE3%3DTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: possible workaround for BeagleBone Ethernet PHY problems

[Robert Nelson]

On Mon, Dec 12, 2016 at 1:10 PM, Grzegorz G  wrote:
> I wonder if the ethernet problems (link is down) has been resolved?
>

We have a software workaround, depending on your kernel version (uname
-r)... Otherwise if your designing your own hardware, make sure you
tie a gpio line the phy's reset line..

On the bbb design, the phy reset is tied to the processor reset...

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/CAOCHtYi%3Dsc%3Dp5U_02uUe8HJCX6urRj9h%2B9HN3tTM07bH1oA%3D%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Ftdi driver issue

[Sylvain]

Hello,

I try to plug more than one FTDI Usb Serial Adapter on a BeagleBone Black.

I tried several adapters and all work fine if plugged directly on the USB 
Host port.

But if I use an USB hub - I tried several - or a specific cape (
http://www.titan.tw/product/USB_2COM_BB.html), the ftdi driver complains:

[ 1544.135039] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set 
> databits/stopbits/parity
> [ 1545.143074] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set 
> baudrate
> [ 1550.151247] ftdi_sio ttyUSB0: urb failed to clear flow control



Here comes the different cases:

BBB Usb Host > USB Cape > Ftdi Usb Serial Adapter 1
> Ftdi Usb Serial Adapter 2

BBB Usb Host > USB Hub > Ftdi Usb Serial Adapter 1
   > Ftdi Usb Serial Adapter 2 

BBB Usb Host > USB Hub > USB Cape > Ftdi Usb Serial Adapter 1
  > Ftdi Usb Serial Adapter 2

--> fails



BBB Usb Host > Ftdi Usb Serial Adapter 1
BBB Usb Host > USB Cape 

--> works


   - Does this issue come from the Ftdi driver? 
   - Is it a BBB hardware problem? (The issue is reproduced on all my four 
   BBB)
   - Where can I send this report to the good guy?
   


Thank you,

Sylvain

-- 
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/a53c3db9-d531-491e-8f44-62c7163ba64a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: possible workaround for BeagleBone Ethernet PHY problems

[Grzegorz G]

I wonder if the ethernet problems (link is down) has been resolved?

W dniu piątek, 13 stycznia 2012 13:18:04 UTC+1 użytkownik Gerald napisał:
>
> Thank you!
>  
> Gerald
>
>
>  
> On Fri, Jan 13, 2012 at 4:49 AM, Jorgen 
> > wrote:
>
>> I shipped the board today. I expect the 'Beagle Hospital' ;-) will
>> receive it on Monday.
>>
>> On Jan 12, 3:20 pm, Gerald Coley  wrote:
>> > Yes, there may be a manufacturing defect. That is why we want the board
>> > back. We have shipped 4500 boards so far, on only have a few that show 
>> this
>> > issue, and none of them are in our possession. We may have something 
>> that
>> > we are missing in our production testing. In order to fix it, we have to
>> > figure out what it is. And based on what it is we can figure out how to
>> > test for it and resolve the issue.
>> >
>> > Gerald
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Thu, Jan 12, 2012 at 5:11 AM, Jorgen  wrote:
>> > > My fix, where I replaced R23 (10K) with 3.6K only worked for a short
>> > > while. The initial reset voltage was ~2.5V, but after perhaps half an
>> > > hour it fallen to 1.6V, and the Ethernet port was once again not
>> > > working. I then replaced the pull-up resistor with 340R, and measured
>> > > 3.1V for reset. This time I put a scope on the signal, and found that
>> > > the reset signal was toggling between ~3.1V and ~2.6V. I am pretty
>> > > sure that if I replaced R23 with 3.6K again, I would see the voltage
>> > > toggling between 3.3V and 1.6V (the average of these is pretty close
>> > > to the 2.5V I measured with a multimeter).
>> >
>> > > One explanation for this is that there may be a manufacturing defect
>> > > on the board, shorting the reset signal to another signal. Another
>> > > possibility is that the CPU is driving the reset signal from the
>> > > NRESET_INOUT pin, because it can't be the U16A buffer, which should
>> > > easily be able to drive the reset signal to ground, even with a 340
>> > > ohm pull to 3.3V.
>> >
>> > > I have sent full details, including a scope shot, to beagleboard RMA.
>> > > I will also be returning the board in a couple of days, so they can
>> > > take a look at it.
>> >
>> > > On Jan 12, 10:20 am, Jorgen  wrote:
>> > > > As I mentioned before, I found that on my board nRST to the PHY was
>> > > > only 1.4V. According to the LAN8710A datasheet, Vih(min) is also 
>> 1.4V,
>> > > > so it is not surprising that the PHY sometimes starts up, and
>> > > > sometimes doesn't, since there is no noise margin at all.
>> >
>> > > > It turns out that the reset signal is driven by an open-collector
>> > > > buffer U16A, with a 10K pull to VDD_3V3A. I measured the VDD_3V3A
>> > > > supply to be 3.3V. I replaced R23 with a 3.6K resistor, and now I
>> > > > measure 2.5V for nRST. The board is currently running, and I am 
>> going
>> > > > to leave it on for a couple of days to be sure that the ethernet 
>> does
>> > > > not shut down again.
>> >
>> > > > There must be an internal pull down on the reset pins on either the
>> > > > LAN8710A or the AM3359 (perhaps both), nothing else is connected to
>> > > > this net. There is no mention of an internal pull resistor in the
>> > > > LAN8719A DC specs. I haven't checked the 3359 datasheet.
>> >
>> > > > I would suggest that you check the nRST voltage on some more boards,
>> > > > if they all have marginal values, you should change the value of R23
>> > > > to something lower.
>> >
>> > > > On Jan 11, 5:45 pm, Jorgen  wrote:
>> >
>> > > > > I have had the board in our lab, and tried to measure if there 
>> were
>> > > > > any obvious problems. The only thing I found was that nRST is at 
>> about
>> > > > > 1.4V, so it looks like the reset signal is not being driven. The 
>> PHY
>> > > > > is also not sending link pulses, but doesn't necessarily need to 
>> be
>> > > > > because of the reset signal, the PHY coould be in powerdown mode. 
>> But
>> > > > > ss can be seen from the kernel message (PHY 0:00 not found) it is 
>> not
>> > > > > responding on the management interface, which definitely should 
>> not
>> > > > > happen unless the part is reset.
>> >
>> > > > > I'm going to try to solder a pullup on the reset signal, that 
>> should
>> > > > > help. But I won't have time until tomorrow. I'll let you know the
>> > > > > result.
>> >
>> > > > > On Jan 11, 5:22 pm, Jorgen  wrote:
>> >
>> > > > > > I'd rather not. I'm in Europe (Denmark), and I looked up the 
>> shipping
>> > > > > > cost of returning the board. It is quite a bit more than I paid 
>> for
>> > > > > > the board (incl. shipping) in the first place :-(
>> >
>> > > > > > On Jan 11, 5:11 pm, Gerald Coley  
>> wrote:
>> >
>> > > > > > > I suggest you send it in under an RMA so we can look at it 
>> from an
>> > > > > > > electrical point of view.
>> >
>> > > > > > > Gerald
>> >
>> > > > > > > On Wed, Jan 11, 2012 at 10:06 AM, Jorgen <
>> jsabraham...@gmail.com>
>> > > wrote:
>> > > > > > > > Well that was fast, the PHY is once again not responding.
>> >
>> > 

Re: [beagleboard] Which way BBBW or BBGW

[mariselafortenberry via BeagleBoard]

On Mon, 12/12/16, William Hermans  wrote:

 Subject: Re: [beagleboard] Which way BBBW or BBGW
 To: beagleboard@googlegroups.com
 Date: Monday, December 12, 2016, 9:43 PM
 
 I
 think the SiP on the beaglebone black wireless is really
 cool, but it also seems to add cost. For board designers the
 SiP is a god send, for many reasons. But in cases like this
 where it adds additional costs to an "end product"
 . . . yeah.
 
 Hopefully, once the sales of the SiP
 increase over time. The cost will come down.
 
 On Mon, Dec 12, 2016 at
 12:39 PM, Ross Morrison 
 wrote:
 On
 Mon, 12 Dec 2016 12:29:37 -0700
 
 William Hermans 
 wrote:
 
 
 
 > The beaglebone black wireless seems to have HDMI, where
 the beaglebone
 
 > green's do not.
 
 >
 
 > On Mon, Dec 12, 2016 at 12:14 PM, Ross Morrison 
 
 > wrote:
 
 >
 
 > > Now that the BBBW is out (in stock), my question
 is: Which one, the
 
 > > BBBW or the BBGW board for a project? This project
 will be small
 
 > > volume this year (under 15), but could grow to 25
 - 50 annually.
 
 > > Yes, the obvious differences are the number of on
 board USB ports
 
 > > and the removal of the power jack from the BBGW
 (both a non-issue
 
 > > for me). The other obvious difference is the
 price, $20 difference
 
 > > here in the USA (that is a big difference).
 I'm just trying to get
 
 > > a good gut check on which way to go. I've been
 working the both the
 
 > > BBG and BBGW and have had no problems. Why should
 one spend the
 
 > > extra money for the BBBW? Are Octavo and GHI going
 to be around
 
 > > awhile and yes, Seeed Studios could go away
 tomorrow (I understand
 
 > > that). Are there any real technical differences
 between the two, ie
 
 > > performance, heat dissipation, noise immunity,
 noise radiation?
 
 > > They both seem to have the same wireless TI part,
 so no differences
 
 > > there???
 
 > >
 
 > > Anyway, thanks for listening. If possible any
 feedback would be
 
 > > greatly appreciated.
 
 > >
 
 > > --
 
 > > Ross Morrison
 
 > >
 
 > > --
 
 > > 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+unsubscribe@
 googlegroups.com.
 
 > > To view this discussion on the web visit
 
 > > https://groups.google.com/d/
 
 > > msgid/beagleboard/
 20161212111410.75b6dd6e% 40kubuntu-14-04. For more
 
 > > options, visit https://groups.google.com/d/
 optout.
 
 > >
 
 >
 
 
 
 Forgot to mention that one (HDMI), another don't need
 for my project.
 
 So, it does seem to be a self answering question, go with
 the BBGW. I
 
 just want to make sure that is the best decision,
 considering all known
 
 factors (pricing, availability, longevity, reliability,
 compatibility,
 
 support, other user's experiences).
 
 
 
 Thanks again,
 
 --
 
 Ross Morrison
 
 
 
 --
 
 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+unsubscribe@
 googlegroups.com.
 
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/beagleboard/ 20161212113916.51b427ee%
 40kubuntu-14-04.
 
 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/CALHSORqxSmAykzC6TGSz8p84p3tJpW-L9ThFK8BdSNKjiCxsXQ%40mail.gmail.com.
 
 For more options, visit https://groups.google.com/d/optout.
  mod decisiv  la desavarsirea programului revolutionar comun al tuturor

-- 
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/1075231131.1566079.1481574421802%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Which way BBBW or BBGW

[William Hermans]

I think the SiP on the beaglebone black wireless is really cool, but it
also seems to add cost. For board designers the SiP is a god send, for many
reasons. But in cases like this where it adds additional costs to an "end
product" . . . yeah.

Hopefully, once the sales of the SiP increase over time. The cost will come
down.

On Mon, Dec 12, 2016 at 12:39 PM, Ross Morrison  wrote:

> On Mon, 12 Dec 2016 12:29:37 -0700
> William Hermans  wrote:
>
> > The beaglebone black wireless seems to have HDMI, where the beaglebone
> > green's do not.
> >
> > On Mon, Dec 12, 2016 at 12:14 PM, Ross Morrison 
> > wrote:
> >
> > > Now that the BBBW is out (in stock), my question is: Which one, the
> > > BBBW or the BBGW board for a project? This project will be small
> > > volume this year (under 15), but could grow to 25 - 50 annually.
> > > Yes, the obvious differences are the number of on board USB ports
> > > and the removal of the power jack from the BBGW (both a non-issue
> > > for me). The other obvious difference is the price, $20 difference
> > > here in the USA (that is a big difference). I'm just trying to get
> > > a good gut check on which way to go. I've been working the both the
> > > BBG and BBGW and have had no problems. Why should one spend the
> > > extra money for the BBBW? Are Octavo and GHI going to be around
> > > awhile and yes, Seeed Studios could go away tomorrow (I understand
> > > that). Are there any real technical differences between the two, ie
> > > performance, heat dissipation, noise immunity, noise radiation?
> > > They both seem to have the same wireless TI part, so no differences
> > > there???
> > >
> > > Anyway, thanks for listening. If possible any feedback would be
> > > greatly appreciated.
> > >
> > > --
> > > Ross Morrison
> > >
> > > --
> > > 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/20161212111410.75b6dd6e%40kubuntu-14-04. For more
> > > options, visit https://groups.google.com/d/optout.
> > >
> >
>
> Forgot to mention that one (HDMI), another don't need for my project.
> So, it does seem to be a self answering question, go with the BBGW. I
> just want to make sure that is the best decision, considering all known
> factors (pricing, availability, longevity, reliability, compatibility,
> support, other user's experiences).
>
> Thanks again,
> --
> Ross Morrison
>
> --
> 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/20161212113916.51b427ee%40kubuntu-14-04.
> 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/CALHSORqxSmAykzC6TGSz8p84p3tJpW-L9ThFK8BdSNKjiCxsXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Which way BBBW or BBGW

[Ross Morrison]

On Mon, 12 Dec 2016 12:29:37 -0700
William Hermans  wrote:

> The beaglebone black wireless seems to have HDMI, where the beaglebone
> green's do not.
> 
> On Mon, Dec 12, 2016 at 12:14 PM, Ross Morrison 
> wrote:
> 
> > Now that the BBBW is out (in stock), my question is: Which one, the
> > BBBW or the BBGW board for a project? This project will be small
> > volume this year (under 15), but could grow to 25 - 50 annually.
> > Yes, the obvious differences are the number of on board USB ports
> > and the removal of the power jack from the BBGW (both a non-issue
> > for me). The other obvious difference is the price, $20 difference
> > here in the USA (that is a big difference). I'm just trying to get
> > a good gut check on which way to go. I've been working the both the
> > BBG and BBGW and have had no problems. Why should one spend the
> > extra money for the BBBW? Are Octavo and GHI going to be around
> > awhile and yes, Seeed Studios could go away tomorrow (I understand
> > that). Are there any real technical differences between the two, ie
> > performance, heat dissipation, noise immunity, noise radiation?
> > They both seem to have the same wireless TI part, so no differences
> > there???
> >
> > Anyway, thanks for listening. If possible any feedback would be
> > greatly appreciated.
> >
> > --
> > Ross Morrison
> >
> > --
> > 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/20161212111410.75b6dd6e%40kubuntu-14-04. For more
> > options, visit https://groups.google.com/d/optout.
> >
> 

Forgot to mention that one (HDMI), another don't need for my project.
So, it does seem to be a self answering question, go with the BBGW. I
just want to make sure that is the best decision, considering all known
factors (pricing, availability, longevity, reliability, compatibility,
support, other user's experiences).

Thanks again,
-- 
Ross Morrison

-- 
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/20161212113916.51b427ee%40kubuntu-14-04.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Which way BBBW or BBGW

[William Hermans]

Well, that, and the beaglebone black wireless also does not have the two
grove connectors. Which personally I found no use for.

On Mon, Dec 12, 2016 at 12:29 PM, William Hermans  wrote:

> The beaglebone black wireless seems to have HDMI, where the beaglebone
> green's do not.
>
> On Mon, Dec 12, 2016 at 12:14 PM, Ross Morrison  wrote:
>
>> Now that the BBBW is out (in stock), my question is: Which one, the BBBW
>> or the BBGW board for a project? This project will be small volume
>> this year (under 15), but could grow to 25 - 50 annually. Yes, the
>> obvious differences are the number of on board USB ports and the
>> removal of the power jack from the BBGW (both a non-issue for me). The
>> other obvious difference is the price, $20 difference here in the USA
>> (that is a big difference). I'm just trying to get a good gut check on
>> which way to go. I've been working the both the BBG and BBGW and have
>> had no problems. Why should one spend the extra money for the BBBW? Are
>> Octavo and GHI going to be around awhile and yes, Seeed Studios could
>> go away tomorrow (I understand that). Are there any real technical
>> differences between the two, ie performance, heat dissipation, noise
>> immunity, noise radiation? They both seem to have the same wireless
>> TI part, so no differences there???
>>
>> Anyway, thanks for listening. If possible any feedback would be greatly
>> appreciated.
>>
>> --
>> Ross Morrison
>>
>> --
>> 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/ms
>> gid/beagleboard/20161212111410.75b6dd6e%40kubuntu-14-04.
>> 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/CALHSORrCCT67NXqb6Z74QhVqbZvRg1jEg9KPCxHFv9kMRCMqOg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Which way BBBW or BBGW

[William Hermans]

The beaglebone black wireless seems to have HDMI, where the beaglebone
green's do not.

On Mon, Dec 12, 2016 at 12:14 PM, Ross Morrison  wrote:

> Now that the BBBW is out (in stock), my question is: Which one, the BBBW
> or the BBGW board for a project? This project will be small volume
> this year (under 15), but could grow to 25 - 50 annually. Yes, the
> obvious differences are the number of on board USB ports and the
> removal of the power jack from the BBGW (both a non-issue for me). The
> other obvious difference is the price, $20 difference here in the USA
> (that is a big difference). I'm just trying to get a good gut check on
> which way to go. I've been working the both the BBG and BBGW and have
> had no problems. Why should one spend the extra money for the BBBW? Are
> Octavo and GHI going to be around awhile and yes, Seeed Studios could
> go away tomorrow (I understand that). Are there any real technical
> differences between the two, ie performance, heat dissipation, noise
> immunity, noise radiation? They both seem to have the same wireless
> TI part, so no differences there???
>
> Anyway, thanks for listening. If possible any feedback would be greatly
> appreciated.
>
> --
> Ross Morrison
>
> --
> 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/20161212111410.75b6dd6e%40kubuntu-14-04.
> 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/CALHSORrb%3DELPYc5waPscVHryZSAX6C9x8r6GtVLR8t%3DqmLBaOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Which way BBBW or BBGW

[Ross Morrison]

Now that the BBBW is out (in stock), my question is: Which one, the BBBW
or the BBGW board for a project? This project will be small volume
this year (under 15), but could grow to 25 - 50 annually. Yes, the
obvious differences are the number of on board USB ports and the
removal of the power jack from the BBGW (both a non-issue for me). The
other obvious difference is the price, $20 difference here in the USA
(that is a big difference). I'm just trying to get a good gut check on
which way to go. I've been working the both the BBG and BBGW and have
had no problems. Why should one spend the extra money for the BBBW? Are
Octavo and GHI going to be around awhile and yes, Seeed Studios could
go away tomorrow (I understand that). Are there any real technical
differences between the two, ie performance, heat dissipation, noise
immunity, noise radiation? They both seem to have the same wireless
TI part, so no differences there???

Anyway, thanks for listening. If possible any feedback would be greatly
appreciated.

-- 
Ross Morrison

-- 
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/20161212111410.75b6dd6e%40kubuntu-14-04.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BUS ERROR modprobe uio_pruss extram_pool_sz=0x800000

[William Hermans]

I suspect that you need to make these changes in the overlay file you use
to initially configure the PRU's.

On Mon, Dec 12, 2016 at 9:39 AM, TJF  wrote:

> Hi malkowki!
>
> Sorry, I cannot really help. Just some info: The same commands work well
> for me on several kernel versions (3.8, 4.1 and 4.4, but no rt). I use them
> often and I always get the first two messages
>
> Am Montag, 12. Dezember 2016 10:32:31 UTC+1 schrieb malkowki:
>>
>> [  749.642962] pruss_uio 4a30.pruss: Unbalanced pm_runtime_enable!
>> [  749.643073] pruss_uio 4a30.pruss: pins are not configured from
>> the driver
>>
>
> But I never got the fault message
>
>
>> [  763.164615] Unhandled fault: external abort on non-linefetch (0x1018)
>> at 0xb6e33000
>> [  763.172351] pgd = ddde8000
>> [  763.175081] [b6e33000] *pgd=9c27e831, *pte=4a304303, *ppte=4a304a33
>>
>
> I wonder why the fault comes with some delay (> 5 s).
>
> 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/7db92f8b-21cd-4193-9569-f24c62f2080f%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/CALHSORr4reEq1anHBzoeJKwegLxsDTGTDo%2BkZnVd%3DwePtmymrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PRU PID Motor Speed Controller Using RemoteProc and RPMsg

[treadwellfrankie via BeagleBoard]

On Mon, 12/12/16, lorrianemayfield via BeagleBoard 
 wrote:

 Subject: Re: [beagleboard] PRU PID Motor Speed Controller Using RemoteProc and 
RPMsg
 To: beagleboard@googlegroups.com
 Date: Monday, December 12, 2016, 5:44 PM
 
 
 
 On Mon, 12/12/16, mariselafortenberry via BeagleBoard 

 wrote:
 
  Subject: Re: [beagleboard] PRU PID Motor Speed Controller
 Using RemoteProc and RPMsg
  To: beagleboard@googlegroups.com
  Date: Monday, December 12, 2016, 7:08 AM
  
  
  
  On Mon, 12/12/16, Jason Kridner 
  wrote:
  
   Subject: Re: [beagleboard] PRU PID Motor Speed
 Controller
  Using RemoteProc and RPMsg
   To: beagleboard@googlegroups.com
   Date: Monday, December 12, 2016, 6:57 AM
   
   Thanks
   for this! Care to post the same with some details on
 the
   steps and code to Hackster.io?
   On Dec 11,
   2016, at 7:33 PM, Greg 
   wrote:
   
   Here is a quick overview of
   this project at youtube:
   https://youtu.be/wzNGHVjAqL8
   
   This is
   based on the example project from Texas
   Instruments:
   http://www.ti.com/tool/tidep0073
   
   I have
   used the latest Debian version 8 Beaglebone Green
 IOT
   image.There was a bit of hacking to convert to
   the System Interrupts from the older Mailbox
   implementation.All hacking was done on the BBG
   using the clpru compiler.  I did not use IDE or
   crosscompiler to get this to work.
   A very minor change to a Device Tree
   file was required.  Thanks to Robert Nelson's
   scripting, this process was trivial!
   Also, I used a different DC
   motor-encoder I found on eBay.  It works perfectly
 with
   this project and is slightly cheaper than the
 recommended
   motor/encoder.
   I will
   publish to Github with documentation soon.I think
   the project is really cool, and the material provided
 by
   Texas Instruments is amazing and a huge help in
 showing
  how
   to use C programming with the PRU and
   Remoteproc/RPMsg!
   Regards,Greg
   
   
   
   
   -- 
   
   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/b3398633-1252-47ca-a986-19230f33c68d%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/530DA12C-781A-41DC-94EB-9520D050D87B%40gmail.com.
   
   For more options, visit
  https://groups.google.com/d/optout.
   ata de acest act care nu contine decat curatul adevar
 si
  este icoana credincioasa a erintelor si nedreptatilor
  seculare ce le indura poporul roman din Transilvania si
  Ungaria trebuia i egimul ori sa se desvinovateasca ori
 sa-si
  rasbune
  
  -- 
  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/2030396546.1040740.1481519286809%40mail.yahoo.com.
  For more options, visit
  https://groups.google.com/d/optout.n
 perioada stalinizarii tarii  partidul comunist a
 concentrat  in mod absolut puterea in mainile sale.
 Devenit principalul agent executor al unui sistem politic
 dictatorial  partidul si-a sporit randurile  de la
 720 000 membri in 1950 la 1 450 000 in 1965. intre 1945-1947
 chiar si o parte dintre fostii simpatizanti ai Garzii de
 Fier si-au gasit refugiul in randurile comunistilor.
 
 -- 
 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/1148960508.1168854.1481557460599%40mail.yahoo.com.
 For more options, visit
 https://groups.google.com/d/optout.1 ian. - Prima Constitutie a U.R.S.S. oct. 
nov. - U.R.S.S. este recunoscuta de Franta  Anglia Italia  Austria  Norvegia  
Suedia  China.

-- 
For more options, visit http://

[beagleboard] Re: could not open binary file

[Graham]

When I look at the download website for VMWare Horizon CLient, 
I don't see a client for Linux-ARM, just a client for Linux-Windows 32 or 
64.

The only ARM client I see is for Android.

If you want to run on Debian-ARM, I suspect you will have to build from 
source.

--- Graham

==

On Monday, December 12, 2016 at 10:27:55 AM UTC-6, TJF wrote:
>
>
>
> Am Montag, 12. Dezember 2016 13:42:25 UTC+1 schrieb Alan Jelani:
>>
>> Hi there, i have installed vmware horizon client on my beaglebone black, 
>> i could see the icon on my desktop but when i clicked it, it wont open, 
>> when i enter "vmware-view" on the terminal i got a message said that "could 
>> not execute binary file". is there any solution to the problem that i have 
>> ? thank you in advance for your reply.
>>
>
> Obviously the program isn't executable, either for a specific user, or not 
> at all. Check output of man chmod for details.
>
> 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/522b95a7-55f3-4742-a866-14e9f1848254%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BUS ERROR modprobe uio_pruss extram_pool_sz=0x800000

[TJF]

Hi malkowki!

Sorry, I cannot really help. Just some info: The same commands work well 
for me on several kernel versions (3.8, 4.1 and 4.4, but no rt). I use them 
often and I always get the first two messages

Am Montag, 12. Dezember 2016 10:32:31 UTC+1 schrieb malkowki:
>
> [  749.642962] pruss_uio 4a30.pruss: Unbalanced pm_runtime_enable!
> [  749.643073] pruss_uio 4a30.pruss: pins are not configured from the 
> driver
>

But I never got the fault message
 

> [  763.164615] Unhandled fault: external abort on non-linefetch (0x1018) 
> at 0xb6e33000
> [  763.172351] pgd = ddde8000
> [  763.175081] [b6e33000] *pgd=9c27e831, *pte=4a304303, *ppte=4a304a33
>

I wonder why the fault comes with some delay (> 5 s).

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/7db92f8b-21cd-4193-9569-f24c62f2080f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: could not open binary file

[TJF]

Am Montag, 12. Dezember 2016 13:42:25 UTC+1 schrieb Alan Jelani:
>
> Hi there, i have installed vmware horizon client on my beaglebone black, i 
> could see the icon on my desktop but when i clicked it, it wont open, when 
> i enter "vmware-view" on the terminal i got a message said that "could not 
> execute binary file". is there any solution to the problem that i have ? 
> thank you in advance for your reply.
>

Obviously the program isn't executable, either for a specific user, or not 
at all. Check output of man chmod for details.

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/2421781b-6c6d-4b95-8f79-5caa4c9cc787%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone default GPIO values

[TJF]

Hi Łukasz!

Am Montag, 12. Dezember 2016 13:07:31 UTC+1 schrieb Łukasz Taras:
>
> Hi all,
> I have an issue (my fault probably) where i would like to define default 
> states of GPIO ports. I have created my own cape based on univ-all where i 
> define two port's as follows:
> P8_03_default_pin: pinmux_P8_03_default_pin {
> pinctrl-single,pins = <0x018  0x27>; };
> P8_03_gpio_pin: pinmux_P8_03_gpio_pin {
> pinctrl-single,pins = <0x018  0x27>; };
>
> P8_04_default_pin: pinmux_P8_04_default_pin {
> pinctrl-single,pins = <0x01c  0x17>; };
> P8_04_gpio_pin: pinmux_P8_04_gpio_pin {
> pinctrl-single,pins = <0x01c  0x17>; };
>

This looks like a device tree (overlay) fragment. You can set the pin 
muxing by loading an device tree (overlay), but you cannot set the state of 
an output pin that way. Therefor you have to export the pin and set its 
state accordingly.

BTW: The configurations are equal (for P8_03 as well as for P8_04). Why do 
you declare them twice?
 

>
> 0x27 should read as: mode 7, input, pulldown
> 0x17 should read as: mode 7, output, pullup.
>
> My goal is to have port P8_03 loaded as input with LOW state (0V) by 
> default (so cat gpio38/value would show 0), and port P9_04 as output with 
> HIGH state (3,3V) by default (so cat gpio39/value would show 1).
>

As you stated, P8_03 is configured as an input pin. You cannot load an 
input at any state. Its value depends on the connected hardware. If voltage 
at this pin is above 1V6 you'll see high state. Voltages below 0V8 result 
in low state, inbetween it's undefined.

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/a6f29c68-3f2e-4279-ba65-9e1fb07c2256%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone default GPIO values

[Graham]

I think you need to read the System Reference Manual a few more times.

P8 Pins 3 through 6, and Pins 20 through 25 are used by the eMMC, so if you 
reassign those pins, you will only be able to boot/run from uSD card, eMMC 
will no longer work.

P8 Pins 31 through 46 are "Boot Pins." If you try to use those pins, and do 
not add some circuitry so that they are not isolated during boot process, 
the BBB will no longer boot.

P8 Pins 27 through 46 are used if there is an LCD display, so if you use 
these pins, it will not be possible to also use an LCD display. You may or 
may not care about this.

--- Graham

===

On Monday, December 12, 2016 at 6:21:18 AM UTC-6, Łukasz Taras wrote:
>
>
> 
> Thats how i wanted to make them by default.
>

-- 
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/cdfc979b-cf27-4bc4-bf6d-56e5d5551c3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PRU PID Motor Speed Controller Using RemoteProc and RPMsg

[lorrianemayfield via BeagleBoard]

On Mon, 12/12/16, mariselafortenberry via BeagleBoard 
 wrote:

 Subject: Re: [beagleboard] PRU PID Motor Speed Controller Using RemoteProc and 
RPMsg
 To: beagleboard@googlegroups.com
 Date: Monday, December 12, 2016, 7:08 AM
 
 
 
 On Mon, 12/12/16, Jason Kridner 
 wrote:
 
  Subject: Re: [beagleboard] PRU PID Motor Speed Controller
 Using RemoteProc and RPMsg
  To: beagleboard@googlegroups.com
  Date: Monday, December 12, 2016, 6:57 AM
  
  Thanks
  for this! Care to post the same with some details on the
  steps and code to Hackster.io?
  On Dec 11,
  2016, at 7:33 PM, Greg 
  wrote:
  
  Here is a quick overview of
  this project at youtube:
  https://youtu.be/wzNGHVjAqL8
  
  This is
  based on the example project from Texas
  Instruments:
  http://www.ti.com/tool/tidep0073
  
  I have
  used the latest Debian version 8 Beaglebone Green IOT
  image.There was a bit of hacking to convert to
  the System Interrupts from the older Mailbox
  implementation.All hacking was done on the BBG
  using the clpru compiler.  I did not use IDE or
  crosscompiler to get this to work.
  A very minor change to a Device Tree
  file was required.  Thanks to Robert Nelson's
  scripting, this process was trivial!
  Also, I used a different DC
  motor-encoder I found on eBay.  It works perfectly with
  this project and is slightly cheaper than the recommended
  motor/encoder.
  I will
  publish to Github with documentation soon.I think
  the project is really cool, and the material provided by
  Texas Instruments is amazing and a huge help in showing
 how
  to use C programming with the PRU and
  Remoteproc/RPMsg!
  Regards,Greg
  
  
  
  
  -- 
  
  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/b3398633-1252-47ca-a986-19230f33c68d%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/530DA12C-781A-41DC-94EB-9520D050D87B%40gmail.com.
  
  For more options, visit
 https://groups.google.com/d/optout.
  ata de acest act care nu contine decat curatul adevar si
 este icoana credincioasa a erintelor si nedreptatilor
 seculare ce le indura poporul roman din Transilvania si
 Ungaria trebuia i egimul ori sa se desvinovateasca ori sa-si
 rasbune
 
 -- 
 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/2030396546.1040740.1481519286809%40mail.yahoo.com.
 For more options, visit
 https://groups.google.com/d/optout.n perioada stalinizarii tarii  partidul 
comunist a concentrat  in mod absolut puterea in mainile sale. Devenit 
principalul agent executor al unui sistem politic dictatorial  partidul si-a 
sporit randurile  de la 720 000 membri in 1950 la 1 450 000 in 1965. intre 
1945-1947 chiar si o parte dintre fostii simpatizanti ai Garzii de Fier si-au 
gasit refugiul in randurile comunistilor.

-- 
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/1148960508.1168854.1481557460599%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] could not open binary file

[Alan Jelani]

Hi there, i have installed vmware horizon client on my beaglebone black, i 
could see the icon on my desktop but when i clicked it, it wont open, when 
i enter "vmware-view" on the terminal i got a message said that "could not 
execute binary file". is there any solution to the problem that i have ? 
thank you in advance for your reply.

-- 
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/e179b1aa-db45-4f0e-9b8f-e576622b7b63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Chaning Bootdelay and rebuilding u-boot

[Patrick Schmelzer]

Hi all

I changed the Bootdelay in the am335x_evm_defconfig to 0. I can see also 
the zero value in the .config file.
The problem is that always when I flash the U-Boot to the SD Card and put 
it in the BeagleBone Black i havee bootdelay=1 (print bootdelay) in the 
u-boot environment.

Where does this come from?

Thanks a lot
Patrick

-- 
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/4aeb2c65-078f-47db-aa8b-3786389858f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone default GPIO values

[Łukasz Taras]

Thats how i wanted to make them by default.

-- 
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/1294a72e-9374-4e2c-99b4-300dc19936a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Access EEPROM of BBB

[Ankita Thummar]

New with BBB. I want to know how to access EEPROM (4KB) of BBB and read and 
write a data structure into it. 
Please suggest me some documents or codes from which I can make my concepts 
clear.
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/a76c52f2-1eeb-4fba-81f6-fffa1da8e3a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PRU PID Motor Speed Controller Using RemoteProc and RPMsg

[mariselafortenberry via BeagleBoard]

On Mon, 12/12/16, Jason Kridner  wrote:

 Subject: Re: [beagleboard] PRU PID Motor Speed Controller Using RemoteProc and 
RPMsg
 To: beagleboard@googlegroups.com
 Date: Monday, December 12, 2016, 6:57 AM
 
 Thanks
 for this! Care to post the same with some details on the
 steps and code to Hackster.io?
 On Dec 11,
 2016, at 7:33 PM, Greg 
 wrote:
 
 Here is a quick overview of
 this project at youtube:
 https://youtu.be/wzNGHVjAqL8
 
 This is
 based on the example project from Texas
 Instruments:
 http://www.ti.com/tool/tidep0073
 
 I have
 used the latest Debian version 8 Beaglebone Green IOT
 image.There was a bit of hacking to convert to
 the System Interrupts from the older Mailbox
 implementation.All hacking was done on the BBG
 using the clpru compiler.  I did not use IDE or
 crosscompiler to get this to work.
 A very minor change to a Device Tree
 file was required.  Thanks to Robert Nelson's
 scripting, this process was trivial!
 Also, I used a different DC
 motor-encoder I found on eBay.  It works perfectly with
 this project and is slightly cheaper than the recommended
 motor/encoder.
 I will
 publish to Github with documentation soon.I think
 the project is really cool, and the material provided by
 Texas Instruments is amazing and a huge help in showing how
 to use C programming with the PRU and
 Remoteproc/RPMsg!
 Regards,Greg
 
 
 
 
 -- 
 
 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/b3398633-1252-47ca-a986-19230f33c68d%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/530DA12C-781A-41DC-94EB-9520D050D87B%40gmail.com.
 
 For more options, visit https://groups.google.com/d/optout.
 ata de acest act care nu contine decat curatul adevar si este icoana 
credincioasa a erintelor si nedreptatilor seculare ce le indura poporul roman 
din Transilvania si Ungaria trebuia i egimul ori sa se desvinovateasca ori 
sa-si rasbune

-- 
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/2030396546.1040740.1481519286809%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beaglebone default GPIO values

[Łukasz Taras]

Hi all,
I have an issue (my fault probably) where i would like to define default 
states of GPIO ports. I have created my own cape based on univ-all where i 
define two port's as follows:
P8_03_default_pin: pinmux_P8_03_default_pin {
pinctrl-single,pins = <0x018  0x27>; };
P8_03_gpio_pin: pinmux_P8_03_gpio_pin {
pinctrl-single,pins = <0x018  0x27>; };

P8_04_default_pin: pinmux_P8_04_default_pin {
pinctrl-single,pins = <0x01c  0x17>; };
P8_04_gpio_pin: pinmux_P8_04_gpio_pin {
pinctrl-single,pins = <0x01c  0x17>; };

0x27 should read as: mode 7, input, pulldown
0x17 should read as: mode 7, output, pullup.

My goal is to have port P8_03 loaded as input with LOW state (0V) by 
default (so cat gpio38/value would show 0), and port P9_04 as output with 
HIGH state (3,3V) by default (so cat gpio39/value would show 1).

Most of those things are working ok, so direction are correct (by default), 
however P8_03 is 1 by default (should be 0), and P8_04 is 0 (should be 1).

What am i doing wrong here?

-- 
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/2fb85c0f-b4f4-4414-945b-cf8365a6ebd7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] PRU PID Motor Speed Controller Using RemoteProc and RPMsg

[Greg]

On Sunday, December 11, 2016 at 11:57:32 PM UTC-5, Jason Kridner wrote:
>
> Thanks for this! Care to post the same with some details on the steps and 
> code to Hackster.io?
>

Yes, I was already planning to upload the project to Hackster.io.
I've got a few hours of work to do on the documentation and cleaning up the 
repository.

Will post an update when I get it published.

Regards,
Greg

-- 
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/d650cedc-2f37-41bb-a30c-5a1d6055fe51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BUS ERROR modprobe uio_pruss extram_pool_sz=0x800000

[malkowki]

 Hi,

I am running 4.1.21-bone-rt-r20, Debian GNU/Linux 8.6 (jessie).
I run a PRU program with default DRAM size of 256KB , this works fines but 
when I tried to increase the external memory to 8MB I got a buss error

#modprobe -r uio_pruss
#modprobe uio_pruss extram_pool_sz=0x80

#dmesg | tail
[  550.971014] pruss_uio 4a30.pruss: Unbalanced pm_runtime_enable!
[  550.97] pruss_uio 4a30.pruss: pins are not configured from the 
driver
[  555.823781] Unhandled fault: external abort on non-linefetch (0x1018) at 
0xb6d43000
[  555.831519] pgd = dc258000
[  555.834249] [b6d43000] *pgd=9db2e831, *pte=4a304303, *ppte=4a304a33
[  749.642962] pruss_uio 4a30.pruss: Unbalanced pm_runtime_enable!
[  749.643073] pruss_uio 4a30.pruss: pins are not configured from the 
driver
[  763.164615] Unhandled fault: external abort on non-linefetch (0x1018) at 
0xb6e33000
[  763.172351] pgd = ddde8000
[  763.175081] [b6e33000] *pgd=9c27e831, *pte=4a304303, *ppte=4a304a33




When I read the pruio driver doc, it said that we can use 8MB max of the 
DDR.

Anybody know how can I get rid of this bus error?

-- 
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/b18dcc1f-a375-4461-8298-718a20294f0e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.