[beagleboard] Re: iperf server side does not quit

[S Pazouki]

to explain the issue more in detail, I am running iperf on one BBB as a 
server and on the other BBB as a client to measure the throughput.

TX Client-side: *sudo iperf -c 192.168.0.2 -u -b 400k -l 800 -p 10001 -t 
100*

RX Server-side: *sudo iperf -u -l 800 -s -i3 -B 192.168.0.2 -p 10001*

after printing the result, the client iperf quits its function but the 
server stays in it.

On Thursday, March 4, 2021 at 3:20:10 PM UTC+1 S Pazouki wrote:

> Does it normal that the iperf in the server side does not quit even when 
> the iperf on the client side exits the function after finishes?
>
>

-- 
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/50a1eba0-0244-401f-bbd0-433560364da7n%40googlegroups.com.

[beagleboard] iperf server side does not quit

[S Pazouki]

Does it normal that the iperf in the server side does not quit even when 
the iperf on the client side exits the function after finishes?

-- 
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/0af6b7c7-f6fd-42b5-ae0b-4ff9cff5a71fn%40googlegroups.com.

[beagleboard] use iperf in python script

[S Pazouki]

Hi everyone, 
I want to write a python scipt that could use this two commands on 
Transiver BBB (Client) and receiver BBB (Server) :

sudo iperf -c 192.168.0.2 -u -b 400k -l 800 -p 10001 -t 100
sudo iperf -u -l 800 -s -i3 -B 192.168.0.2 -p 10001

Could I use directly iperf the command in the python script or I should 
convert it to some other code?

-- 
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/3760b03a-9ce6-4436-bc6a-51ba35d4784fn%40googlegroups.com.

[beagleboard] Is BBB a SoC FPGA

[S Pazouki]

Is Beagleboard Black a SoC FPGA ?
I have hard that a system with CPU and Flash is kind of SoC FPGA, Am I 
right? 

-- 
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/f2f662f9-b72a-432e-b955-63cb55a61dbcn%40googlegroups.com.

[beagleboard] How to verify eMMC and DDR?

[Venugopal S Nair]

Hello,


I would like to write some random data to some locations in eMMC and DDR, 
then read back and check whether they are same.

- From where do I get the information regarding the start and end addresses 
of eMMC and DDR?

- Does the mw and md commands in u-boot help for this activity?

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/754ce1b4-fe53-4cea-95eb-93090e3aa9d5o%40googlegroups.com.

[beagleboard] Interested in contributing

[G S Niteesh]

Hello,

I am Niteesh and I am interested in contributing to the Beaglebone org. I 
was a GSoC 2020 student working for the RTEMS organization. I love to work 
with embedded systems, bare metal but also tinker with other areas like 
compiler's, OS etc.

I went through the GSoC projects to find something interesting and found 
projects related to PRU interesting. Can someone please point me to some 
basic issues, I would like to start off with something simple and then 
build from there.

Thanks
Niteesh

-- 
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/0df797c6-ad38-4e8a-a580-fb2e098d0d84n%40googlegroups.com.

[beagleboard] What is the use of AIN7 ADC input from 3V3 rail?

[Venugopal S Nair]

What is the use of the ADC input AIN7? Is it used for any logic internally 
or just as a voltage measurement?

We are planning for a custom board based on beagle bone black. Is this pin 
absolutely necessary? Or can we just remove it from circuit?

Thanks in advance.


-- 
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/a3a8576e-b66d-4c72-b8a5-68b17d0cbed0o%40googlegroups.com.

[beagleboard] Re: Beaglebone AI UART access

[sharif . s . 786]

Hi ahni, Thanks a lot for this info, I will try This out & see if UART3 
Works.

On Thursday, April 23, 2020 at 7:53:18 AM UTC+5:30, ahni...@gmail.com wrote:
>
>
> I hope it is helpful for uart3  /dev/ttyS2 device tree implementation. 
>
> Uart3 RX starts working after the mode update to 
>
> PIN_INPUT_PULLUP | MUX_MODE1 // P9.22b uart3_rxd
>
> Mode is confirmed as the following:
>
>
> P9.22b   240 fast rx  up   1 uart 2 rxd   serial@4802 (uart3)
>
> pin 240 (PIN240) 4a0037c0 00060001 pinctrl-single ( instead of 0001)
>
>
>
> UART3 TX was working without any pull up or pull down.
>
> P9_21, MUX_MODE1 ) // P9.21 uart3_txd
>
> pin 241 (PIN241) 4a0037c4 0001 pinctrl-single
>
>
>
> To activate uart3, please add the following code into *.dts file and 
> compile to *.dtb. 
>
> Also please modify the am572*ai.dts file by deactivating the shared pins.
>
>
>  {
>
>  status = "okay";
>
>  pinctrl-names = "default";
>
>  pinctrl-0 = <_pins>;
>
> };
>
> _pmx_core {
>
>  uart3_pins: uart3 {
>
>   pinctrl-single,pins = <
>
>DRA7XX_CORE_IOPAD( P9_21, MUX_MODE1 ) // P9.21 uart3_txd
>
>DRA7XX_CORE_IOPAD( P9_22b, PIN_INPUT_PULLUP | MUX_MODE1) // P9.22b 
> uart3_rxd
>
>DRA7XX_CORE_IOPAD( P9_22a, MUX_MODE15) // P9.22a driver_off //shared-pin
>
>   >;
>
>  };
>
>  
>
> };
>
>
>

-- 
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/d09f3246-4ff1-49d8-a51a-acaf7a859c20o%40googlegroups.com.

[beagleboard] Re: Ethernet over USB adapter

[zoshi . s]

Hello again,

I came across a thread here that it is possible to use USB0 as a host. I 
could understand the hardware changes needed. Could you may be show me how 
I need to configure my Kernel to use USB0 as a host?

Regards,
Szoshi

-- 
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/2b4c1a4b-fed4-4591-af2f-c082db1e2014o%40googlegroups.com.

[beagleboard] Re: Ethernet over USB adapter

[zoshi . s]

Hi. Thanks for the quick reply. I will try it out and post my results 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/8dbbe184-cf3b-4031-b6fa-f5c0ea63cca4o%40googlegroups.com.

[beagleboard] Open Source DSP Library

[s . varunreddy09]

Hi,
I want to use an optimised(for speed) DSP(require 1D FFT,matrix operations 
etc) library which works with beaglebone. As I am a beginner, I would like 
to get a proper steps on where to find(the library) and detailed 
information regarding the link and requirements for using the Library. Can 
anyone suggest an open source DSP library that utilises ARM Neon features. 
Any suggestions will be highly appreciated.
Thanks in advance.

-- 
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/959570b1-786b-45a2-a59c-2cfd68b99430%40googlegroups.com.

[beagleboard] RE: BBONE-BLACK-4G - Lifecycle

[M S, Siddeshappa]

Any update on this, customer is asking...

Regards,
Siddu
M +919945211348

From: M S, Siddeshappa
Sent: 17 October 2019 12:03
To: 'beagleboard@googlegroups.com' 
Subject: BBONE-BLACK-4G - Lifecycle

Hi Team,

Please see the below issue one of our customer asking for the lifecycle for 
BBONE-BLACK-4G Board.


Customer Issue - do you have any information regarding the lifecycle of our 
code BBONE-BLACK-4G ? Do you think that this product will still be in our 
catalog for almost 5 years?

Siddeshappa M S

s...@element14.com<mailto:%20...@element14.com>

Product Categorisation Manager

PDD



[cid:image001.png@01D58A59.FB981C30]



IBC Knowledge Park, Tower D ,11th Floor Bannerghatta Main Road, Bangalore-29

O +91080.40003880.34904

M +919945211348

www.farnell.com<https://www.farnell.com/>
**Disclaimer*** 
The contents of this e-mail and any file transmitted with it are confidential 
and intended solely for the individual or entity to whom they are addressed.
The content may also contain legal, professional or other privileged 
information. 
If you received this e-mail in error, please destroy it immediately. 
You should not copy or use it for any purpose nor disclose its contents to any 
other person. 
The views stated herein do not necessarily represent the view of the Company. 
Please ensure you have adequate virus protection before you open or detach any 
documents from this transmission.
The Company does not accept any liability for viruses.   
element14 India Pvt Ltd
IBC Knowledge Park,
11th Floor, Tower “D”, 4/1, 
Bannerghatta Main Rd,
Suddagunte Palya,
Bengaluru-560029, 
Karnataka, India.

TEL: 91 804000 3888
FAX: 91 804000 3880 
A Premier Farnell Company 
Company Number: U30009KA2007PTC08

-- 
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/9BA0400D86F3A54389EF23F9050A3A405C8376D6C3%40SGPWEXV01P.premierfarnell.net.

[beagleboard] operating temperature

[Patil, Dilip S]

Hi team,
Could you please provide the operating temperature of SBC BBONE-AI

Datasheet: https://www.farnell.com/datasheets/2819385.pdf


Dilip Patil

d...@element14.com

Product Author

PDD



[cid:image001.png@01D5801B.A8EA5720]



#4/1, Tower D, 11th Floor

IBC Knowledge Park, Bannerghatta Road

Bangalore - 560029, INDIA

www.farnell.com
**Disclaimer*** 
The contents of this e-mail and any file transmitted with it are confidential 
and intended solely for the individual or entity to whom they are addressed.
The content may also contain legal, professional or other privileged 
information. 
If you received this e-mail in error, please destroy it immediately. 
You should not copy or use it for any purpose nor disclose its contents to any 
other person. 
The views stated herein do not necessarily represent the view of the Company. 
Please ensure you have adequate virus protection before you open or detach any 
documents from this transmission.
The Company does not accept any liability for viruses.   
element14 India Pvt Ltd
IBC Knowledge Park,
11th Floor, Tower “D”, 4/1, 
Bannerghatta Main Rd,
Suddagunte Palya,
Bengaluru-560029, 
Karnataka, India.

TEL: 91 804000 3888
FAX: 91 804000 3880 
A Premier Farnell Company 
Company Number: U30009KA2007PTC08

-- 
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/EA28D0F2432B784CB17E84D9BBB4856F5AE807FBDC%40SGPWEXV01P.premierfarnell.net.

[beagleboard] BBONE-BLACK-4G - Lifecycle

[M S, Siddeshappa]

Hi Team,

Please see the below issue one of our customer asking for the lifecycle for 
BBONE-BLACK-4G Board.


Customer Issue - do you have any information regarding the lifecycle of our 
code BBONE-BLACK-4G ? Do you think that this product will still be in our 
catalog for almost 5 years?

Siddeshappa M S

s...@element14.com<mailto:%20...@element14.com>

Product Categorisation Manager

PDD



[cid:image001.png@01D579D7.DD5FF2C0]



IBC Knowledge Park, Tower D ,11th Floor Bannerghatta Main Road, Bangalore-29

O +91080.40003880.34904

M +919945211348

www.farnell.com<https://www.farnell.com/>
**Disclaimer*** 
The contents of this e-mail and any file transmitted with it are confidential 
and intended solely for the individual or entity to whom they are addressed.
The content may also contain legal, professional or other privileged 
information. 
If you received this e-mail in error, please destroy it immediately. 
You should not copy or use it for any purpose nor disclose its contents to any 
other person. 
The views stated herein do not necessarily represent the view of the Company. 
Please ensure you have adequate virus protection before you open or detach any 
documents from this transmission.
The Company does not accept any liability for viruses.   
element14 India Pvt Ltd
IBC Knowledge Park,
11th Floor, Tower “D”, 4/1, 
Bannerghatta Main Rd,
Suddagunte Palya,
Bengaluru-560029, 
Karnataka, India.

TEL: 91 804000 3888
FAX: 91 804000 3880 
A Premier Farnell Company 
Company Number: U30009KA2007PTC08

-- 
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/9BA0400D86F3A54389EF23F9050A3A405A55A4E1C8%40SGPWEXV01P.premierfarnell.net.

[beagleboard] BBONE-AI - Operating Temp Min & Max

[M S, Siddeshappa]

Hi Team,

Please see the below issue one of customer asking for the operating Temperature 
Min & Max if available for BBONE-AI Board.


Customer Issue - 'Hello Team, customer cannot find Operating Temperature Min 
and Max - please, could you provide Thank you so much for your help Peter'


Siddeshappa M S

s...@element14.com<mailto:%20...@element14.com>

Product Categorisation Manager

PDD



[cid:image001.png@01D579D7.DD5FF2C0]



IBC Knowledge Park, Tower D ,11th Floor Bannerghatta Main Road, Bangalore-29

O +91080.40003880.34904

M +919945211348

www.farnell.com<https://www.farnell.com/>
**Disclaimer*** 
The contents of this e-mail and any file transmitted with it are confidential 
and intended solely for the individual or entity to whom they are addressed.
The content may also contain legal, professional or other privileged 
information. 
If you received this e-mail in error, please destroy it immediately. 
You should not copy or use it for any purpose nor disclose its contents to any 
other person. 
The views stated herein do not necessarily represent the view of the Company. 
Please ensure you have adequate virus protection before you open or detach any 
documents from this transmission.
The Company does not accept any liability for viruses.   
element14 India Pvt Ltd
IBC Knowledge Park,
11th Floor, Tower “D”, 4/1, 
Bannerghatta Main Rd,
Suddagunte Palya,
Bengaluru-560029, 
Karnataka, India.

TEL: 91 804000 3888
FAX: 91 804000 3880 
A Premier Farnell Company 
Company Number: U30009KA2007PTC08

-- 
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/9BA0400D86F3A54389EF23F9050A3A405A559F504D%40SGPWEXV01P.premierfarnell.net.

[beagleboard] SSH, ping over IPv6 only, not IPv4

[gerry s]

Hello All,

I'm running "*Linux beaglebone 3.8.13-bone80 #1 SMP Wed Jun 15 17:03:55 UTC 
2016 armv7l GNU/Linux*" on a Rev C BBB.
Yes, this is an old version, but have to remain on this due to the 
application, and have the latest eMMC(5.1) support(*Thank you Robert!*).

I had a query a while back about disabling wicd breaks networking 
here:https://groups.google.com/forum/#!searchin/beagleboard/wicd|sort:date/beagleboard/jxJzB6MlqeA/I3eHMpBnBAAJ
However, I found out that IPv6 works, so does beaglebone.local via putty or 
ping.

Now, I feel I may have broken some networking file when disabling wicd that 
caused this.
The following services are *disabled*:

   sudo update-rc.d apache2 disable
>sudo update-rc.d wicd disable
>sudo systemctl disable cloud9.service
>sudo update-rc.d saned disable
>sudo update-rc.d lightdm disable
>sudo systemctl stop graphical.target 
>
>sudo update-rc.d  alsa-utils disable
>sudo systemctl disable  bonescript-autorun.service
>sudo update-rc.d  cpufrequtils  disable
>sudo update-rc.d  hdparm  disable
>sudo update-rc.d  loadcpufreq  disable
>sudo systemctl disable  wpa_supplicant.service
>sudo systemctl disable  bonescript.socket
>sudo systemctl disable cloud9.socket
>sudo systemctl disable graphical.target
>

 

This is my */etc/network/interfaces* file:


> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> #auto eth0
> #iface eth0 inet dhcp
> # Example to keep MAC address between reboots
> #hwaddress ether DE:AD:BE:EF:CA:FE
>
> # The secondary network interface
> #auto eth1
> #iface eth1 inet dhcp
>
> # WiFi use: -> connmanctl
>
> # Ethernet/RNDIS gadget (g_ether)
> # Used by: /opt/scripts/boot/autoconfigure_usb0.sh
> iface usb0 inet static
> address 192.168.7.2
> netmask 255.255.255.252
> network 192.168.7.0
> gateway 192.168.7.1
>
>

*ifconfig*:

debian@beaglebone:~$ ifconfig
> 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:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> usb0  Link encap:Ethernet  HWaddr 04:a3:16:f5:25:10
>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>   inet6 addr: fe80::6a3:16ff:fef5:2510/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:479 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:75 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:61361 (59.9 KiB)  TX bytes:20074 (19.6 KiB)
>

>
Does anyone have any suggestions to get IPv4 back.

Thank you,
-Gerry

-- 
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/e2b9d883-15ce-4e4b-a2cf-8f3e209a4696%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Does wicd need to be enabled for USB Networking?

[gerry s]

Hello,

I'm running "*Linux beaglebone 3.8.13-bone80 #1 SMP Wed Jun 15 17:03:55 UTC 
2016 armv7l GNU/Linux*" on a Rev C BBB.
Yes, this is an old version, but have to remain on this due to the 
application, and have the latest eMMC(5.1) support(*Thank you Robert!*).

I have everything working as usual, but have an unusual need to disable 
wicd (*sudo update-rc.d wicd disable*). 
The application samples a GPIO and it works reliably only if wicd is 
disabled. In fact I see wicd come up on top(*top -d 1*) while the 
application is running.
Unfortunately, I also have a need for USB networking. USB0 and the RNDIS 
driver get mounted on windows alright, but ssh'ing into the BBB with wicd 
disabled does not work.

I also have the following services disabled. 

   sudo update-rc.d apache2 disable
>sudo update-rc.d wicd disable
>sudo systemctl disable cloud9.service
>sudo update-rc.d saned disable
>sudo update-rc.d lightdm disable
>sudo systemctl stop graphical.target 
>
>sudo update-rc.d  alsa-utils disable
>sudo update-rc.d  avahi-daemon  disable
>sudo systemctl disable  bonescript-autorun.service
>sudo update-rc.d  cpufrequtils  disable
>sudo update-rc.d  hdparm  disable
>sudo update-rc.d  loadcpufreq  disable
>sudo systemctl disable  wpa_supplicant.service
>sudo systemctl disable  bonescript.socket
>sudo systemctl disable cloud9.socket
>sudo systemctl disable graphical.target
>

Question: Can I get USB networking back with wicd disabled?
Thank you.

-Gerry

-- 
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/03f59d87-c322-4319-bc71-892149509ede%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: header file for CCSv6 & PRU

[Gaurav S]

Hugh,
Thanks for sharing your research.
Any chance you could also include a reference (ie where did you find this 
info)?

Thanks

On Friday, August 17, 2018 at 9:43:47 AM UTC-5, Hugh Frater wrote:
>
> I forgot this from my previous post:
>
> /* I2C2 register offsets */
>
> #define I2C2_STATUSRAW (*((volatile unsigned int*)0x4819C024))
> #define I2C2_CNT (*((volatile unsigned int*)0x4819C098))
> #define I2C2_SA (*((volatile unsigned int*)0x4819C0AC))
> #define I2C2_DATA (*((volatile unsigned int*)0x4819C09C))
> #define I2C2_CON (*((volatile unsigned int*)0x4819C0A4))
> #define I2C2_SCLL (*((volatile unsigned int*)0x4819C0B4))
> #define I2C2_SCLH (*((volatile unsigned int*)0x4819C0B8))
> #define I2C2_PSC (*((volatile unsigned int*)0x4819C0B0))
>
> I couldn't be bothered to setup a header file for this lot, so just 
> stuffed it in the top of my PRU code... Registers for other I2C modules are 
> in the memory map from the am335X_trm
>
> On Tuesday, 14 August 2018 12:29:12 UTC+1, Hugh Frater wrote:
>>
>> Does anyone know the header file I need to include to get access to the 
>> i2c2 control registers from within the PRU subsystem? Having a hard time 
>> getting any info and my google-foo is usually pretty decent...
>>
>

-- 
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/ec0bcc70-1d82-4877-b074-c762337ff4bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: No USB connection... and no wifi no more

[Henry S.]

I am having the same issue with the USB but I am using windows. I can SSH 
in through the wifi, but no USB access for me either.

-- From my earlier post --
I flashed the 9.4 IoT 2018-06-17 build to a card and that does boot it up. 
Blinking lights blink away and I can connect to its WiFi. I can also SSH in 
via the 192.168.8.1 address and the cloud9 interface works.

However, over USB nothing happens. I don't get a new network interface when 
I connect it, nothing seems to install, and nothing new shows up in device 
manager (not in network adapters or other devices). I've tried two win10 
computers and different cables. Flipping through some other posts on 
various sites, tried installing BONE_D64 driver to see if it would 
magically find something but no luck.

-S-

On Tuesday, March 20, 2018 at 5:32:30 PM UTC-4, Kjell Morgenstern wrote:
>
> Hello,
>
> I am trying to get USB connections to my three BBB rev2A boards, but they 
> do not show up anywhere (eg dmesg or lsusb), nor do I get a network 
> connection to 192.168.6.2 (or 7.2)
> Wifi works (mostly), but not really reliable enough to support a longer 
> ssh session.
>
> So, basically I have two questions, both about connecting to the boards.
>
> 1. Is the USB problem a known one? beaglebone.org getting-started 
> instructions give the impression that should just work right out of the 
> box. 
>
> 2. One of the boards stopped working via wifi (wifi led won't light up, 
> device does not show up in network scan). Is it toast now? What can I try?
>
>
> What I already tried:
>
> * three different BBB devices (all ordered at the same date and vendor)
> * different host computers: MacMini 2012 and one Ubuntu 16.04 machine that 
> has USB 3
> * 12V power supply connected to the board
> * fresh 2018-03 debian iot image (boot from SD Card)
> * install drivers for the mac (tried this about 2017-4, so it was only 
> with the older image)
> * ran the linux script to register the usb device number
> * tried three different USB cables
> * looked for any visible physical damage (none found)
> * googling ;-)
> * read the troubleshooting guide... no internet explorer involved
>
> What I did not yet try: A windows machine. In a few days I might have 
> access to one were I may install drivers and fool around, but even if that 
> works, it would not really solve my problem.
> Also, since much on BBB is based on debian: I am mainly working on Ubuntu, 
> maybe there is some 'autoconnect' service missing that is common in debian?
>
> Thanks for any hints
> Greetings, Kjell
>
>
>

-- 
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/479b87fd-ec74-4540-9321-9738f14293b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Network Fail on Rev C boards

[James S]

Thanks for the reply but that doesn't work. Remember, the same SD card 
worked for the White and the older BBB - but not on the Rev C PCB. Why does 
Rev C PCB stop this card working?


On Monday, January 22, 2018 at 2:31:58 PM UTC, amf wrote:
>
> if you want dhcp on eth0 then uncomment
> #auto eth0
> #iface eth0 inet dhcp
>
> if you want a static ip on eth0, then do like you have on usb0
>
> amf
>
> On Monday, January 22, 2018 at 6:19:02 AM UTC-6, James S wrote:
>
>> We have some legacy software running on BB White and BB Black (PCB Rev 
>> B6) for a while. Recently we have to build some more and using the Rev C 
>> BBB, the network fails to start. We are booting Debian from the same SD 
>> card, version 3.8.13-bone67.
>>
>> Can anyone tell me why the more recent hardware stops the network 
>> working? How can I get it going again? 
>> Looking at the revision history on the schematics, the only difference 
>> from Rev B to Rev C is the larger eMMC.
>>
>> Thanks,
>> James
>>
>> *ifconfig gives the following output:*
>> eth0  Link encap:Ethernet  HWaddr 38:d2:69:57:93:ed
>>   inet6 addr: fd78:6a89:d8ad:3100:3ad2:69ff:fe57:93ed/64 
>> Scope:Global
>>   inet6 addr: fe80::3ad2:69ff:fe57:93ed/64 Scope:Link
>>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>   RX packets:87010 errors:0 dropped:7 overruns:0 frame:0
>>   TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:1000
>>   RX bytes:7151565 (6.8 MiB)  TX bytes:16941 (16.5 KiB)
>>   Interrupt:40
>>
>> 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:0 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:0
>>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>
>> usb0  Link encap:Ethernet  HWaddr 92:7f:c3:3b:c8:09
>>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:1000
>>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>
>>
>> The following is part of the output of *journalctl*. It seems to show 
>> attempts to connect to the network?
>> Oct 09 01:28:04 beaglebone systemd[1]: Starting Multi-User System.
>> Oct 09 01:28:04 beaglebone systemd[1]: Reached target Multi-User System.
>> Oct 09 01:28:04 beaglebone systemd[1]: Starting Graphical Interface.
>> Oct 09 01:28:04 beaglebone systemd[1]: Reached target Graphical Interface.
>> Oct 09 01:28:04 beaglebone systemd[1]: Starting Update UTMP about System 
>> Runlevel Changes...
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Joining mDNS multicast 
>> group on interface usb0.IPv4 with address 192.168.7.2.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: New relevant interface 
>> usb0.IPv4 for mDNS.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Registering new address 
>> record for 192.168.7.2 on usb0.IPv4.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Withdrawing address record 
>> for 192.168.7.2 on usb0.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Leaving mDNS multicast 
>> group on interface usb0.IPv4 with address 192.168.7.2.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Interface usb0.IPv4 no 
>> longer relevant for mDNS.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Joining mDNS multicast 
>> group on interface usb0.IPv4 with address 192.168.7.2.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: New relevant interface 
>> usb0.IPv4 for mDNS.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Registering new address 
>> record for 192.168.7.2 on usb0.IPv4.
>> Oct 09 01:28:05 beaglebone udhcpd[1518]: udhcpd (v1.20.2) started
>> Oct 09 01:28:05 beaglebone kernel: IPv6: ADDRCONF(NETDEV_UP): usb0: link 
>> is not ready
>> Oct 09 01:28:05 beaglebone systemd[1]: Started Update UTMP about System 
>> Runlevel Changes.
>> Oct 09 01:28:05 beaglebone systemd[1]: Startup finished in 8.601s 
>> (kernel) + 15.137s (userspace) = 23.738s.
>> Oct 09 01:28:06 beaglebone dhclient[1540]: isc-dhclient-4.2.2
>> Oct 09 01:28:06 beaglebone dhclient[1541]: isc-dhclient-4.2.2
>> Oct 09 01:28:12 beaglebone login[

[beagleboard] Re: Network Fail on Rev C boards

[James S]

On Monday, January 22, 2018 at 2:31:58 PM UTC, amf wrote:
>
> if you want dhcp on eth0 then uncomment
> #auto eth0
> #iface eth0 inet dhcp
>
> if you want a static ip on eth0, then do like you have on usb0
>
> amf
>
> On Monday, January 22, 2018 at 6:19:02 AM UTC-6, James S wrote:
>
>> We have some legacy software running on BB White and BB Black (PCB Rev 
>> B6) for a while. Recently we have to build some more and using the Rev C 
>> BBB, the network fails to start. We are booting Debian from the same SD 
>> card, version 3.8.13-bone67.
>>
>> Can anyone tell me why the more recent hardware stops the network 
>> working? How can I get it going again? 
>> Looking at the revision history on the schematics, the only difference 
>> from Rev B to Rev C is the larger eMMC.
>>
>> Thanks,
>> James
>>
>> *ifconfig gives the following output:*
>> eth0  Link encap:Ethernet  HWaddr 38:d2:69:57:93:ed
>>   inet6 addr: fd78:6a89:d8ad:3100:3ad2:69ff:fe57:93ed/64 
>> Scope:Global
>>   inet6 addr: fe80::3ad2:69ff:fe57:93ed/64 Scope:Link
>>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>   RX packets:87010 errors:0 dropped:7 overruns:0 frame:0
>>   TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:1000
>>   RX bytes:7151565 (6.8 MiB)  TX bytes:16941 (16.5 KiB)
>>   Interrupt:40
>>
>> 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:0 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:0
>>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>
>> usb0  Link encap:Ethernet  HWaddr 92:7f:c3:3b:c8:09
>>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:1000
>>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>
>>
>> The following is part of the output of *journalctl*. It seems to show 
>> attempts to connect to the network?
>> Oct 09 01:28:04 beaglebone systemd[1]: Starting Multi-User System.
>> Oct 09 01:28:04 beaglebone systemd[1]: Reached target Multi-User System.
>> Oct 09 01:28:04 beaglebone systemd[1]: Starting Graphical Interface.
>> Oct 09 01:28:04 beaglebone systemd[1]: Reached target Graphical Interface.
>> Oct 09 01:28:04 beaglebone systemd[1]: Starting Update UTMP about System 
>> Runlevel Changes...
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Joining mDNS multicast 
>> group on interface usb0.IPv4 with address 192.168.7.2.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: New relevant interface 
>> usb0.IPv4 for mDNS.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Registering new address 
>> record for 192.168.7.2 on usb0.IPv4.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Withdrawing address record 
>> for 192.168.7.2 on usb0.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Leaving mDNS multicast 
>> group on interface usb0.IPv4 with address 192.168.7.2.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Interface usb0.IPv4 no 
>> longer relevant for mDNS.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Joining mDNS multicast 
>> group on interface usb0.IPv4 with address 192.168.7.2.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: New relevant interface 
>> usb0.IPv4 for mDNS.
>> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Registering new address 
>> record for 192.168.7.2 on usb0.IPv4.
>> Oct 09 01:28:05 beaglebone udhcpd[1518]: udhcpd (v1.20.2) started
>> Oct 09 01:28:05 beaglebone kernel: IPv6: ADDRCONF(NETDEV_UP): usb0: link 
>> is not ready
>> Oct 09 01:28:05 beaglebone systemd[1]: Started Update UTMP about System 
>> Runlevel Changes.
>> Oct 09 01:28:05 beaglebone systemd[1]: Startup finished in 8.601s 
>> (kernel) + 15.137s (userspace) = 23.738s.
>> Oct 09 01:28:06 beaglebone dhclient[1540]: isc-dhclient-4.2.2
>> Oct 09 01:28:06 beaglebone dhclient[1541]: isc-dhclient-4.2.2
>> Oct 09 01:28:12 beaglebone login[1226]: pam_unix(login:session): session 
>> opened for user root by LOGIN(uid=0)
>> Oct 09 01:28:12 beaglebone systemd-journal[210]: Forwarding to syslog 
>> missed 62 m

[beagleboard] Network Fail on Rev C boards

[James S]

We have some legacy software running on BB White and BB Black (PCB Rev B6) 
for a while. Recently we have to build some more and using the Rev C BBB, 
the network fails to start. We are booting Debian from the same SD card, 
version 3.8.13-bone67.

Can anyone tell me why the more recent hardware stops the network working? 
How can I get it going again? 
Looking at the revision history on the schematics, the only difference from 
Rev B to Rev C is the larger eMMC.

Thanks,
James

*ifconfig gives the following output:*
eth0  Link encap:Ethernet  HWaddr 38:d2:69:57:93:ed
  inet6 addr: fd78:6a89:d8ad:3100:3ad2:69ff:fe57:93ed/64 
Scope:Global
  inet6 addr: fe80::3ad2:69ff:fe57:93ed/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:87010 errors:0 dropped:7 overruns:0 frame:0
  TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:7151565 (6.8 MiB)  TX bytes:16941 (16.5 KiB)
  Interrupt:40

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:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

usb0  Link encap:Ethernet  HWaddr 92:7f:c3:3b:c8:09
  inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
  UP BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


The following is part of the output of *journalctl*. It seems to show 
attempts to connect to the network?
Oct 09 01:28:04 beaglebone systemd[1]: Starting Multi-User System.
Oct 09 01:28:04 beaglebone systemd[1]: Reached target Multi-User System.
Oct 09 01:28:04 beaglebone systemd[1]: Starting Graphical Interface.
Oct 09 01:28:04 beaglebone systemd[1]: Reached target Graphical Interface.
Oct 09 01:28:04 beaglebone systemd[1]: Starting Update UTMP about System 
Runlevel Changes...
Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Joining mDNS multicast group 
on interface usb0.IPv4 with address 192.168.7.2.
Oct 09 01:28:05 beaglebone avahi-daemon[1206]: New relevant interface 
usb0.IPv4 for mDNS.
Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Registering new address 
record for 192.168.7.2 on usb0.IPv4.
Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Withdrawing address record 
for 192.168.7.2 on usb0.
Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Leaving mDNS multicast group 
on interface usb0.IPv4 with address 192.168.7.2.
Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Interface usb0.IPv4 no 
longer relevant for mDNS.
Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Joining mDNS multicast group 
on interface usb0.IPv4 with address 192.168.7.2.
Oct 09 01:28:05 beaglebone avahi-daemon[1206]: New relevant interface 
usb0.IPv4 for mDNS.
Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Registering new address 
record for 192.168.7.2 on usb0.IPv4.
Oct 09 01:28:05 beaglebone udhcpd[1518]: udhcpd (v1.20.2) started
Oct 09 01:28:05 beaglebone kernel: IPv6: ADDRCONF(NETDEV_UP): usb0: link is 
not ready
Oct 09 01:28:05 beaglebone systemd[1]: Started Update UTMP about System 
Runlevel Changes.
Oct 09 01:28:05 beaglebone systemd[1]: Startup finished in 8.601s (kernel) 
+ 15.137s (userspace) = 23.738s.
Oct 09 01:28:06 beaglebone dhclient[1540]: isc-dhclient-4.2.2
Oct 09 01:28:06 beaglebone dhclient[1541]: isc-dhclient-4.2.2
Oct 09 01:28:12 beaglebone login[1226]: pam_unix(login:session): session 
opened for user root by LOGIN(uid=0)
Oct 09 01:28:12 beaglebone systemd-journal[210]: Forwarding to syslog 
missed 62 messages.
Oct 09 01:28:12 beaglebone login[1546]: ROOT LOGIN  on '/dev/ttyO0'
Oct 09 01:28:13 beaglebone kernel: net eth0: initializing cpsw version 1.12 
(0)
Oct 09 01:28:13 beaglebone kernel: net eth0: phy found : id is : 0x7c0f1
Oct 09 01:28:13 beaglebone kernel: libphy: PHY 4a101000.mdio:01 not found
Oct 09 01:28:13 beaglebone kernel: net eth0: phy 4a101000.mdio:01 not found 
on slave 1
Oct 09 01:28:13 beaglebone kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is 
not ready
Oct 09 01:28:16 beaglebone kernel: libphy: 4a101000.mdio:00 - Link is Up - 
100/Full
Oct 09 01:28:16 beaglebone kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: 
link becomes ready
Oct 09 01:28:17 beaglebone avahi-daemon[1206]: Joining mDNS multicast group 
on interface eth0.IPv6 with address fe80::3ad2:69ff:fe57:93ed.
Oct 09 01:28:17 beaglebone avahi-daemon[1206]: New relevant interface 
eth0.IPv6 for mDNS.
Oct 09 01:28:17 beaglebone avahi-daemon[1206]: Registering new address 
record for fe80::3ad2:69ff:fe57:93ed on eth0.*.
Oct 09 01:28:19 beaglebone 

Re: [beagleboard] Re: Car Hacking with a PocketBeagle (CAN, SWCAN, LIN/ISO9141/K-Line, J1850 and more)

[Earl S]

Ok, so should I use config-pin on all the red PIN labels, P2_18, P2_6, 
P2_32, etc? 

Correct. Pin labels in red coorespond to pins on PocketBeagle.

 The linux kernel has support for MCP2515 SPI.  I'm not sure yet if that is 
compiled into the standard beagle kernel but I can check.  Would I just set 
the SWC Mode pins to gpio?

Correct again, 2 mode pins would just go to GPIO outputs. Bring both HIGH 
for normal mode.

On Saturday, December 30, 2017 at 4:02:42 PM UTC-6, agent...@gmail.com 
wrote:
>
> Ok, so should I use config-pin on all the red PIN labels, P2_18, P2_6, 
> P2_32, etc?  The linux kernel has support for MCP2515 SPI.  I'm not sure 
> yet if that is compiled into the standard beagle kernel but I can check.  
> Would I just set the SWC Mode pins to gpio?
>
> On Friday, December 29, 2017 at 4:09:22 PM UTC-8, Earl S wrote:
>>
>> Since PocketBeagle (and M2) has 2 built-in CAN controllers, we needed an 
>> external CAN controller for Single-wire CAN. That MCP2515 controller is 
>> connected to PB via SPI and a couple other GPIO pins. 
>>
>> The attached schematic sketch shows the connections. We'll make a table 
>> summarizing all of the other connections between the boards later.
>>
>> Keep in mind that the library you noted here: 
>>
>>
>> https://github.com/macchina/Single-Wire-CAN-mcp2515/blob/master/src/MCP2515_sw_can.cpp
>>
>> relies on this library for functionality:
>>
>> https://github.com/macchina/mcp2515
>>
>> Thanks, ecs
>>
>> On Friday, December 29, 2017 at 3:29:43 PM UTC-6, RobertCNelson wrote:
>>>
>>>
>>>
>>> On Fri, Dec 29, 2017 at 2:55 PM, <agent...@gmail.com> wrote:
>>>
>>>> I'm familiar with the other M2 versions but I'm trying to get my head 
>>>> wrapped around the beagle version.  It appears to enable can we use 
>>>> config_pin and that connects the can transceiver of the M2 to the linux 
>>>> kernel on the beagle, correct?
>>>>
>>>> If so the next thing that would be easy to test is to connect the 
>>>> SWCAN.  As it looks like that just flows into the MCP2515 which should 
>>>> just 
>>>> show up as a CAN interface as well.  Looking at the current SWCAN 
>>>> library 
>>>> <https://github.com/macchina/Single-Wire-CAN-mcp2515/blob/master/src/MCP2515_sw_can.cpp>
>>>>  It 
>>>> looks like we setup some specific M2 related settings.  How would we do 
>>>> this as well as pass this information to the beagle to use as a can 
>>>> interface?
>>>>
>>>> My ultimate goal is to connect all the interfaces to the linux side but 
>>>> I'm trying to get up to speed on how the beagle works.  I'm familiar with 
>>>> linux, coding and the M2 but how these all work together still hasn't 
>>>> clicked.  I read the source for config-pin 
>>>> <https://github.com/cdsteinkuehler/beaglebone-universal-io/blob/master/config-pin>
>>>>  
>>>> but that didn't really clear anything up.  If I want to write the glue to 
>>>> make this cape 'just work' what's the worflow/process I should be going 
>>>> through?
>>>>
>>>> Craig
>>>>
>>>
>>> So config-pin is just a user-space utility that allows us to easily 
>>> switch the peripheral/pin mapping.
>>>
>>> On the am335x, each pins usually has 8 different modes that can be 
>>> setup. (gpio, can, usart, spi, timer, pru, etc)
>>>
>>> By default the can interface is enabled, but it's not muxed to those 
>>> pins.
>>>
>>> So when you bootup, you will see the can interface listed under 
>>> "ifconfig", but till you actually configure the pins' for can (thru 
>>> config-pin), the am335x can ip will not see any traffic..
>>>
>>> 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/eec9bea3-af9c-40d8-ae5a-7aa98137720f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Car Hacking with a PocketBeagle (CAN, SWCAN, LIN/ISO9141/K-Line, J1850 and more)

[Earl S]

Since PocketBeagle (and M2) has 2 built-in CAN controllers, we needed an 
external CAN controller for Single-wire CAN. That MCP2515 controller is 
connected to PB via SPI and a couple other GPIO pins. 

The attached schematic sketch shows the connections. We'll make a table 
summarizing all of the other connections between the boards later.

Keep in mind that the library you noted here: 

https://github.com/macchina/Single-Wire-CAN-mcp2515/blob/master/src/MCP2515_sw_can.cpp

relies on this library for functionality:

https://github.com/macchina/mcp2515

Thanks, ecs

On Friday, December 29, 2017 at 3:29:43 PM UTC-6, RobertCNelson wrote:
>
>
>
> On Fri, Dec 29, 2017 at 2:55 PM,  wrote:
>
>> I'm familiar with the other M2 versions but I'm trying to get my head 
>> wrapped around the beagle version.  It appears to enable can we use 
>> config_pin and that connects the can transceiver of the M2 to the linux 
>> kernel on the beagle, correct?
>>
>> If so the next thing that would be easy to test is to connect the SWCAN.  
>> As it looks like that just flows into the MCP2515 which should just show up 
>> as a CAN interface as well.  Looking at the current SWCAN library 
>> 
>>  It 
>> looks like we setup some specific M2 related settings.  How would we do 
>> this as well as pass this information to the beagle to use as a can 
>> interface?
>>
>> My ultimate goal is to connect all the interfaces to the linux side but 
>> I'm trying to get up to speed on how the beagle works.  I'm familiar with 
>> linux, coding and the M2 but how these all work together still hasn't 
>> clicked.  I read the source for config-pin 
>> 
>>  
>> but that didn't really clear anything up.  If I want to write the glue to 
>> make this cape 'just work' what's the worflow/process I should be going 
>> through?
>>
>> Craig
>>
>
> So config-pin is just a user-space utility that allows us to easily switch 
> the peripheral/pin mapping.
>
> On the am335x, each pins usually has 8 different modes that can be setup. 
> (gpio, can, usart, spi, timer, pru, etc)
>
> By default the can interface is enabled, but it's not muxed to those pins.
>
> So when you bootup, you will see the can interface listed under 
> "ifconfig", but till you actually configure the pins' for can (thru 
> config-pin), the am335x can ip will not see any traffic..
>
> 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/97e6a8b6-b962-40d3-86b7-4f6e9e462714%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Car Hacking with a PocketBeagle (CAN, SWCAN, LIN/ISO9141/K-Line, J1850 and more)

[Earl S]

We released the Macchina M2, an Arduino-based car tinkering interface a 
little while ago. M2’s interface board has 2X CAN, 1X SWCAN, 2X 
LIN/ISO9141/K-Line, J1850, 6X 12v GPIO and more. In our latest experiment, 
we replaced our processor board with the PocketBeagle and now we have an 
awesome Linux based car tinkering platform! We are here to show it off, get 
your feedback and find some people who want to help us test and improve it. 

We can always use an extra set of eyes on the design 
<https://github.com/macchina/pocketbeagle-adapter-hardware/>. Let us know 
what you think so far. If you are interested in playing with a beta unit, 
reach out to us at i...@macchina.cc and let us know what you have in mind. 
Here <http://docs.macchina.cc/pb_adapter/> is what we have so far for 
documentation. Let us know if you have any other questions.  

<https://lh3.googleusercontent.com/-TUiK8AK2mtk/WjgA4pF_ahI/AP0/8gB_sdlbRvItfNa1XDlQyXSeRhcBdtQJwCLcBGAs/s1600/M2%2BPB%2BBreakout.JPG>

-- 
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/9c57c08e-65d3-434a-b46b-f963b609a292%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Enabling CAN0 - "invalid mode: can"

[Josh S]

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[d36fe9a7be9ebfc872b10a470e904ab4c61c4516]
eeprom:[A335PBGL00A21744GPB20719]
dogtag:[BeagleBoard.org Debian Image 2017-10-10]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
2017.09-2-g0f3f1c7907]
kernel:[4.4.91-ti-r133]
nodejs:[v6.11.4]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20171009.0-0rcnee1~stretch+20171009]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]
debian@beaglebone:~$



On Tue, Dec 5, 2017 at 8:43 AM, Robert Nelson 
wrote:

> On Mon, Dec 4, 2017 at 9:10 PM,   wrote:
> > Wondering how to change the mode of P1_28 to CAN0RX and P1_26 to CAN0TX
> as
> > shown in the wiki:
> >
> > https://github.com/beagleboard/pocketbeagle/wiki/Peripherals#can
> >
> > It doesn't appear as though CAN is an option for those pins?
> >
> > ---
> > debian@beaglebone:/$ config-pin P1_28 can
> > Invalid mode: can
> > debian@beaglebone:/$ config-pin -l P1_28
> > default gpio gpio_pu gpio_pd spi i2c pru_uart
> > debian@beaglebone:/$ config-pin -l P1_26
> > default gpio gpio_pu gpio_pd spi i2c pru_uart
> > debian@beaglebone:/$
> >
> > ---
> >
> > Apologies if this is covered somewhere, I am still getting up to speed on
> > this cool little board. Thanks in advance!
>
>
> sudo /opt/scripts/tools/version.sh
>
> 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/CAFLypv%3D11TS45ctYBVFotV1gWzbnowYOgqN%2BXgnaShh2Em9MBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Enabling CAN0 - "invalid mode: can"

[Josh S]

Thanks Robert! Got everything working on Can0!  Attached is a screen
capture of some data. Thanks again for your help.

On Tue, Dec 5, 2017 at 9:57 AM, Robert Nelson <robertcnel...@gmail.com>
wrote:

> On Tue, Dec 5, 2017 at 9:43 AM, Josh S <rocketj...@gmail.com> wrote:
> > debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
> > git:/opt/scripts/:[d36fe9a7be9ebfc872b10a470e904ab4c61c4516]
> > eeprom:[A335PBGL00A21744GPB20719]
> > dogtag:[BeagleBoard.org Debian Image 2017-10-10]
> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
> > 2017.09-2-g0f3f1c7907]
> > kernel:[4.4.91-ti-r133]
>
> can0/1 got enabled in r135
>
> > nodejs:[v6.11.4]
> > uboot_overlay_options:[enable_uboot_overlays=1]
> > uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/
> AM335X-PRU-RPROC-4-4-TI-00A0.dtbo]
> > uboot_overlay_options:[enable_uboot_cape_universal=1]
> > pkg:[bb-cape-overlays]:[4.4.20171009.0-0rcnee1~stretch+20171009]
>
> you'll also need to update bb-cape-overlays package:
>
> So just run:
>
> sudo apt update ; sudo apt upgrade
> sudo /opt/scripts/tools/update_kernel.sh
> sudo 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/CAFLypvmEo%2BHNWJtM%3D3BOn8-9e1Am%2BtNdTeyhOzYfP_HJwnEyOg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBoneBlack. LCDPCLK Harmonics Emissions Issue

[Gaurav S]

Not sure if this is what you need, but I dont remember having issues with 
the LCD, however the 12MHz clock (and its harmonics) feeding the HDMI was 
quite troublesome.
If you dont need hdmi, you can disable CLKOUT1 (XDMA_EVENT_INTR0) by 
default by setting SYSBOOT[5] low. If you do need it, then you may need to 
think of a better way of feeding the hdmi clock.
HTH,
Gaurav

On Friday, September 22, 2017 at 5:59:16 AM UTC-5, Lee wrote:
>
> I am currently trying to get a BeagleBoneBlack to comply with Class B 
> Radiated Emissions levels.
> I am seeing noise spikes at various harmonics which I believe are 
> originating from the LCD PCLK running at approx. 38MHz.
> These are spikes are at 307, 345, 384, 422, 460, 499, 537MHz, etc. and are 
> at or above the limit for Class B emissions.
> Has anyone else managed to solve this problem and limit the harmonics 
> propagating through the system?
> Thanks.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/6fbf8719-94ae-48be-adb1-26a02c7524b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: spi / shiftout.js in 2017-03-19 image

[Gaurav S]

Also note that Derek Molly's code does not set all parameters in the 
structure spi_ioc_transfer.. Bad/undefined values can cause SPI to die. 
Ensure you set all fields to have valid values. 

struct spi_ioc_transfer 
 {
__u64    
tx_buf ;
__u64    
rx_buf ;

__u32    
len;
__u32    
speed_hz;

__u16    
delay_usecs;
__u8  
bits_per_word 
;
__u8  
cs_change;
__u8  
tx_nbits;
__u8  
rx_nbits;
__u16    
pad ;

/* If the contents of 'struct spi_ioc_transfer' ever change  * 
incompatibly, then the ioctl number (currently 0) must change;* ioctls 
with constant size fields get a bit more in the way of * error checking 
than ones (like this) where that field varies. *   * NOTE: struct 
layout is the same in 64bit and 32bit userspace. */};


On Friday, July 7, 2017 at 3:53:10 PM UTC-5, Jeff Albrecht wrote:
>
> Perhaps a year or more ago I finished Part I and II of Derek Molloy's 
> excellent book;  "Exploring Beaglebone" At the time I specifically recall 
> successfully running the shiftout.js in the cloud9 ide and the spi595.c 
> from the book. Flash forward to now I'm returning to finish part III 
> specifically PRUs but thought it prudent to review a bit.
>
> I flash my BBB with bone-debian-8.7-iot-armhf-2017-03-19-4gb.img.xz
>
> jeffa@beaglebone:~$ cat /etc/dogtag
> BeagleBoard.org Debian Image 2017-03-19
> jeffa@beaglebone:~$ uname -a
> Linux beaglebone 4.4.54-ti-r93 #1 SMP Fri Mar 17 13:08:22 UTC 2017 armv7l 
> GNU/Linux
> jeffa@beaglebone:~$
>
> While working with the spi595.c I check the slots. I'm not positive but it 
> looks like the way to configure pins now is with c*ape-universaln*. I 
> also find a handy gist 
>  from Drew 
> @pdp7 where I learn about *config-pin. *I also try loading the BB-SPIDEV0 
> and the ADAFRUIT-SPI0 in /etc/default/capemgr and rebooting.
>
> jeffa@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
>  0: PF  -1
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,cape-universaln
> jeffa@beaglebone:~$
>
> Not getting the blinkin' lighting with the spi595.c test code from the 
> book, I try the simpler shiftout.js bit banging (not spi) example from the 
> BBB documentation  
> and cloud9 ide. Nope. I write a quick bonescript .js to test my GPIOs by 
> toggling low/high. They're good.  I hook up my oscilloscope to see that I'm 
> only getting the latch (on channel 3). Where is the clock and the serial 
> in? 
>
> Are there any other changes that I may have missed? Suggestions?
>
>
> 
>
>

-- 
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/a0a154ad-cb7e-467c-9ec7-3d5ae8f2d737%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to disable clkout1?

[Gaurav S]

I am trying to disable CLKOUT1 due to EMI issues (and neither do I user 
HDMI) on Beaglebone Black. To disable CLKOUT1, TRM suggests disabling 
SYSBOOT[5]. I disable it by removing R64 and connecting R90 to ground. I 
have manually verified using a multimeter that SYSBOOT[5] is indeed 0, I 
have also verified the value by reading control_status before and after the 
change. Yet, CLKOUT1 is still enabled. I am not sure what else do I need to 
modify to kill CLKOUT1? Any suggestions would be appreciated.

Thanks
Gaurav

-- 
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/c2eba135-c238-44f2-b54e-e9f3b90d8394%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Enabling SPI1 on BBGW via DeviceTree (no capemanager)

[Gaurav S]

I had a similar issue with 4.9 kernel where I couldnt load SPI1 pins using 
BB-SPIDEV1. Apparently mcasp was also getting assigned the same pins, 
disabling audio in uEnv helps. Didnt really test it all the way, but I 
could see /dev/spidev* pins loaded and spidev module loaded. Hope this help,

Gaurav

On Friday, June 23, 2017 at 10:33:16 AM UTC-5, mjbo...@gmail.com wrote:
>
> Problem "solved" (worked around really) by switching to SPI0, changing the 
> pins around and rerouting most of our custom cape.
> There are still some problems with the SPI bus but that's a separate issue.
>

-- 
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/f755c65f-7f3f-4971-a617-3ce4d3b5dde1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Stretch (testing June 11,2017) LXQT GUI hangs on boot up

[Gaurav S]

Seems like /dev/fb0 is not found when lightdm runs 
(see http://paste.debian.net/971349/) but it does exist when queried 
manually.
Manually restarting lightdm fixes the boot up issue. ( sudo service lightdm 
restart)

I thought I would add this to rc.local, but rc.local is missing, I guess I 
need to create a service for this.

Anyways, this seems like a temporary fix. Any suggestions on a permanent 
fix would be appreciated.

Thanks
Gaurav

On Tuesday, June 13, 2017 at 11:03:25 AM UTC-5, Gaurav S wrote:
>
> Hello,
>  Just downloaded latest stretch LXQT image (June 11,2017). Flashed sd card 
> and popped it in. First boot worked fine, executed grow_partition script 
> and rebooted. GUI boot failed (all i see is a blinking cursor which never 
> seems to go away), but I was able to ssh. Rebooted a few more times, same 
> issue. Flashed sd-card again, first boot worked fine. Rebooted the system 
> (without executing any scripts), gui boot failed again, stuck with a bling 
> cursor again, but I am able to ssh. Have attached a copy of syslog and 
> kern.log. 
>
> I am not sure but I suspect the problem is with limghtdm.service failing. 
> From syslog: 
> Jun 13 15:44:12 beaglebone systemd[1]: lightdm.service: Main process 
> exited, code=exited, status=1/FAILURE
> Jun 13 15:44:12 beaglebone systemd[1]: lightdm.service: Unit entered 
> failed state.
> Jun 13 15:44:12 beaglebone systemd[1]: lightdm.service: Failed with result 
> 'exit-code'.
>
>
> debian@beaglebone:~$ systemctl status lightdm
> ● lightdm.service - Light Display Manager
>Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor 
> preset: enabled)
>Active: failed (Result: exit-code) since Tue 2017-06-13 15:44:37 UTC; 
> 14min ago
>  Docs: man:lightdm(1)
>   Process: 1464 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
>   Process: 1458 ExecStartPre=/bin/sh -c [ "$(cat 
> /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ] 
> (code=exited, status=0/SUCCESS)
>  Main PID: 1464 (code=exited, status=1/FAILURE)
>
> Jun 13 15:44:36 beaglebone systemd[1]: lightdm.service: Failed with result 
> 'exit-code'.
> Jun 13 15:44:37 beaglebone systemd[1]: lightdm.service: Service hold-off 
> time over, scheduling restart.
> Jun 13 15:44:37 beaglebone systemd[1]: Stopped Light Display Manager.
> Jun 13 15:44:37 beaglebone systemd[1]: lightdm.service: Start request 
> repeated too quickly.
> Jun 13 15:44:37 beaglebone systemd[1]: Failed to start Light Display 
> Manager.
> Jun 13 15:44:37 beaglebone systemd[1]: lightdm.service: Unit entered 
> failed state.
> Jun 13 15:44:37 beaglebone systemd[1]: lightdm.service: Failed with result 
> 'exit-code'.
>
> debian@beaglebone:~$ uname -a
> Linux beaglebone 4.4.68-ti-r108 #1 SMP Fri Jun 9 20:14:30 UTC 2017 armv7l 
> GNU/Linux
>
> lightdm log:
>
> root@beaglebone:/var/log/lightdm# less lightdm.log
> [+0.01s] DEBUG: Loading configuration from 
> /usr/share/lightdm/lightdm.conf.d/01_debian.conf
> [+0.01s] DEBUG: Loading configuration dirs from 
> /usr/local/share/lightdm/lightdm.conf.d
> [+0.01s] DEBUG: Loading configuration dirs from 
> /etc/xdg/lightdm/lightdm.conf.d
> [+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
> [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
> [+0.02s] DEBUG: Registered seat module xlocal
> [+0.02s] DEBUG: Registered seat module xremote
> [+0.02s] DEBUG: Registered seat module unity
> [+0.37s] DEBUG: Monitoring logind for seats
> [+0.37s] DEBUG: New seat added from logind: seat0
> [+0.37s] DEBUG: Seat seat0: Loading properties from config section Seat:*
> [+0.37s] DEBUG: Seat seat0: Starting
> [+0.37s] DEBUG: Seat seat0: Creating user session
> [+0.39s] WARNING: Error getting user list from org.freedesktop.Accounts: 
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
> org.freedesktop.Accounts was not provided by any .service files
> [+0.42s] DEBUG: Loading user config from /etc/lightdm/users.conf
> [+0.42s] DEBUG: User debian added
> [+0.44s] DEBUG: Seat seat0: Creating display server of type x
> [+0.46s] DEBUG: Could not run plymouth --ping: Failed to execute child 
> process "plymouth" (No such file or directory)
> [+0.46s] DEBUG: Using VT 7
> [+0.46s] DEBUG: Seat seat0: Starting local X display on VT 7
> [+0.47s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
> [+0.47s] DEBUG: DisplayServer x-0: Writing X server authority to 
> /var/run/lightdm/root/:0
> [+0.47s] DEBUG: DisplayServer x-0: Launching X Server
> [+0.48s] DEBUG: Launching process 1471: /usr/bin/X :0 -seat seat0 -auth 
> /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
> [+0.48s] DEBUG: DisplayServer x-0: Waiting 

Re: [beagleboard] U-boot SPI fails to load with LCD

[Gaurav S]

Hello,
http://elinux.org/4D_4.3_LCD_CAPE

Thanks for the reference Robert, that solved the issue. Apparently I should 
not be mixing uboot with "bone_capemgr.enable". I am not sure why did the 
/dev/spidev* work on the system without the LCD.

Thanks again,

gaurav

On Tuesday, May 9, 2017 at 12:38:50 PM UTC-5, RobertCNelson wrote:
>
> Which lcd?
>
> For spidev please read:
>
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Override_external_capes
>
>
> On May 9, 2017 12:16 PM, "Gaurav S" <gaurav@gmail.com > 
> wrote:
>
> Hello All,
> With LCD, it seems like SPI is behaving awkwardly. I have two beagle bone 
> boards one with LCD plugged in (SYS1) and the other stand alone beagle bone 
> (SYS2), both running latest debian lxqt 2gb image (may 7 2017). The curious 
> thing over here is that before u-boot spi was working just fine with the 
> LCD.
>
> Following are the results from each of the systems:
>
> SYS1 (beaglebone + LCD4)
>
> debian@beaglebone:~$ uname -a
> Linux beaglebone 4.4.62-ti-r99 #1 SMP Sat Apr 22 14:21:03 UTC 2017 armv7l 
> GNU/Linux
> debian@beaglebone:~$ dmesg | grep bone
> [0.00] Kernel command line: console=ttyO0,115200n8 
> bone_capemgr.enable_partno=BB-SPIDEV1 bone_capemgr.uboot_capemgr_enabled=1 
> root=UUID=e4c7e2e7-0fbf-494c-8d84-305d291d2b7a ro rootfstype=ext4 rootwait 
> coherent_pool=1M net.ifnames=0 quiet
> [2.376478] bone_capemgr bone_capemgr: Baseboard: 
> 'A335BNLT,00C0,2516BBBK2265'
> [2.376509] bone_capemgr bone_capemgr: 
> compatible-baseboard=ti,beaglebone-black - #slots=4
> [2.376544] bone_capemgr bone_capemgr: slot #0: auto loading handled by 
> U-Boot
> [2.376566] bone_capemgr bone_capemgr: slot #1: auto loading handled by 
> U-Boot
> [2.376587] bone_capemgr bone_capemgr: slot #2: auto loading handled by 
> U-Boot
> [2.376629] bone_capemgr bone_capemgr: slot #3: auto loading handled by 
> U-Boot
> [2.376655] bone_capemgr bone_capemgr: enabled_partno PARTNO 
> 'BB-SPIDEV1' VER 'N/A' PR '0'
> [2.376667] bone_capemgr bone_capemgr: slot #4: override
> [2.376681] bone_capemgr bone_capemgr: slot #4: auto loading handled by 
> U-Boot
> [2.377276] bone_capemgr bone_capemgr: initialized OK.
> [6.851318] systemd[1]: Set hostname to .
> debian@beaglebone:/dev$ ls sp*
> ls: cannot access sp*: No such file or directory
>
>
>
> SYS2 (stand along beagle bone)
>
> debian@beaglebone:~$ uname -a
> Linux beaglebone 4.4.62-ti-r99 #1 SMP Sat Apr 22 14:21:03 UTC 2017 armv7l 
> GNU/Linux
> debian@beaglebone:~$ dmesg|grep bone
> [0.00] Kernel command line: console=ttyO0,115200n8 
> bone_capemgr.enable_partno=BB-SPIDEV1 bone_capemgr.uboot_capemgr_enabled=1 
> root=UUID=599ccfe6-2803-4ea0-9141-2bb571994e70 ro rootfstype=ext4 rootwait 
> coherent_pool=1M net.ifnames=0 quiet
> [2.445200] bone_capemgr bone_capemgr: Baseboard: 
> 'A335BNLT,00C0,2516BBBK22E8'
> [2.445233] bone_capemgr bone_capemgr: 
> compatible-baseboard=ti,beaglebone-black - #slots=4
> [2.445270] bone_capemgr bone_capemgr: slot #0: auto loading handled by 
> U-Boot
> [2.445291] bone_capemgr bone_capemgr: slot #1: auto loading handled by 
> U-Boot
> [2.445337] bone_capemgr bone_capemgr: slot #2: auto loading handled by 
> U-Boot
> [2.445359] bone_capemgr bone_capemgr: slot #3: auto loading handled by 
> U-Boot
> [2.445379] bone_capemgr bone_capemgr: enabled_partno PARTNO 
> 'BB-SPIDEV1' VER 'N/A' PR '0'
> [2.445390] bone_capemgr bone_capemgr: slot #4: override
> [2.445403] bone_capemgr bone_capemgr: slot #4: auto loading handled by 
> U-Boot
> [2.446010] bone_capemgr bone_capemgr: initialized OK.
> [   17.551299] systemd[1]: Set hostname to .
> debian@beaglebone:~$ cd /dev
> debian@beaglebone:/dev$ ls sp*
> spidev1.0  spidev1.1  spidev2.0  spidev2.1
>
> Am I missing something regarding how u-boot is supposed to work?
>
>
> Thanks
> Gaurav
>
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/5852e231-e19e-4b1e-9a4f-3c9acd6656e5%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/beagleboard/5852e231-e19e-4b1e-9a4f-3c9acd6656e5%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You

Re: [beagleboard] U-boot SPI fails to load with LCD

[Gaurav S]

Hell,
Thanks for the response. Seems like spidev available on both systems.

For sys1 (beaglebone+LCD)

debian@beaglebone:~$ lsmod
Module  Size  Used by
omap_aes_driver23912  0
omap_sham  26513  0
omap_rng5544  0
rng_core9066  1 omap_rng
tilcdc 31597  0
ti_am335x_tsc   6268  0
ti_am335x_tscadc6563  1 ti_am335x_tsc
evdev  13511  0
uio_pdrv_genirq 3923  0
uio10524  1 uio_pdrv_genirq
8021q  23043  0
garp7049  1 8021q
mrp 8967  1 8021q
stp 2430  1 garp
llc 5903  2 stp,garp
usb_f_mass_storage 49849  2
usb_f_acm   8361  2
u_serial   13753  1 usb_f_acm
usb_f_ecm  11064  2
usb_f_rndis25865  2
u_ether14349  2 usb_f_ecm,usb_f_rndis
libcomposite   53618  16 
usb_f_acm,usb_f_ecm,usb_f_rndis,usb_f_mass_storage
spidev  8860  0
tieqep  9981  0
pwm_tiehrpwm5883  1
pru_rproc  15431  0
pruss_intc  8603  1 pru_rproc
pruss  12090  1 pru_rproc


for sys2 (beaglebone only):
debian@beaglebone:~$ lsmod
Module  Size  Used by
snd_soc_hdmi_codec  6738  1
ti_am335x_adc   6364  0
kfifo_buf   3732  1 ti_am335x_adc
industrialio   62863  2 ti_am335x_adc,kfifo_buf
snd_soc_simple_card 9812  0
omap_aes_driver23912  0
omap_sham  26513  0
pwm_tiecap  4571  0
omap_rng5544  0
rng_core9066  1 omap_rng
tilcdc 31597  0
c_can_platform  7581  0
c_can  12220  1 c_can_platform
can_dev14358  1 c_can
snd_soc_davinci_mcasp20606  2
snd_soc_edma1290  1 snd_soc_davinci_mcasp
snd_soc_omap3762  1 snd_soc_davinci_mcasp
snd_soc_core  190453  5 
snd_soc_hdmi_codec,snd_soc_davinci_mcasp,snd_soc_edma,snd_soc_omap,snd_soc_simple_card
snd_pcm_dmaengine   5894  2 snd_soc_core,snd_soc_omap
snd_pcm   104314  5 
snd_soc_hdmi_codec,snd_soc_davinci_mcasp,snd_soc_core,snd_soc_omap,snd_pcm_dmaengine
snd_timer  24761  1 snd_pcm
snd72473  3 snd_soc_core,snd_timer,snd_pcm
soundcore   8661  1 snd
spi_omap2_mcspi12952  0
tda998x15704  0
evdev  13511  4
ti_am335x_tsc   6268  0
ti_am335x_tscadc6563  2 ti_am335x_adc,ti_am335x_tsc
uio_pdrv_genirq 3923  0
uio10524  1 uio_pdrv_genirq
8021q  23043  0
garp7049  1 8021q
mrp 8967  1 8021q
stp 2430  1 garp
llc 5903  2 stp,garp
usb_f_mass_storage 49849  2
usb_f_acm   8361  2
u_serial   13753  3 usb_f_acm
usb_f_ecm  11064  2
usb_f_rndis25865  2
u_ether14349  2 usb_f_ecm,usb_f_rndis
libcomposite   53618  16 
usb_f_acm,usb_f_ecm,usb_f_rndis,usb_f_mass_storage
spidev  8860  0
tieqep  9981  0
pwm_tiehrpwm5883  0
pru_rproc  15431  0
pruss_intc  8603  1 pru_rproc
pruss  12090  1 pru_rproc


Thanks
Gaurav

On Tuesday, May 9, 2017 at 12:19:50 PM UTC-5, William Hermans wrote:
>
>
>
> On Tue, May 9, 2017 at 10:16 AM, Gaurav S <gaurav@gmail.com 
> > wrote:
>
>> Hello All,
>> With LCD, it seems like SPI is behaving awkwardly. I have two beagle bone 
>> boards one with LCD plugged in (SYS1) and the other stand alone beagle bone 
>> (SYS2), both running latest debian lxqt 2gb image (may 7 2017). The curious 
>> thing over here is that before u-boot spi was working just fine with the 
>> LCD.
>>
>> Following are the results from each of the systems:
>>
>> SYS1 (beaglebone + LCD4)
>>
>> debian@beaglebone:~$ uname -a
>> Linux beaglebone 4.4.62-ti-r99 #1 SMP Sat Apr 22 14:21:03 UTC 2017 armv7l 
>> GNU/Linux
>> debian@beaglebone:~$ dmesg | grep bone
>> [0.00] Kernel command line: console=ttyO0,115200n8 
>> bone_capemgr.enable_partno=BB-SPIDEV1 bone_capemgr.uboot_capemgr_enabled=1 
>> root=UUID=e4c7e2e7-0fbf-494c-8d84-305d291d2b7a ro rootfstype=ext4 rootwait 
>> coherent_pool=1M net.ifnames=0 quiet
>> [2.376478] bone_capemgr bone_capemgr: Baseboard: 
>> 'A335BNLT,00C0,2516BBBK2265'
>> [2.376509] bone_capemgr bone_capemgr: 
>> compatible-baseboard=ti,beaglebone-black - #slots=4
>> [2.376544] bone_capemgr bone_capemgr: slot #0: auto loading handled 
>> by U-Boot
>> [2.376566] bone_capemgr bone_capemgr: slot #1: auto loading handled 
>> by U-Boot
>>

[beagleboard] U-boot SPI fails to load with LCD

[Gaurav S]

Hello All,
With LCD, it seems like SPI is behaving awkwardly. I have two beagle bone 
boards one with LCD plugged in (SYS1) and the other stand alone beagle bone 
(SYS2), both running latest debian lxqt 2gb image (may 7 2017). The curious 
thing over here is that before u-boot spi was working just fine with the 
LCD.

Following are the results from each of the systems:

SYS1 (beaglebone + LCD4)

debian@beaglebone:~$ uname -a
Linux beaglebone 4.4.62-ti-r99 #1 SMP Sat Apr 22 14:21:03 UTC 2017 armv7l 
GNU/Linux
debian@beaglebone:~$ dmesg | grep bone
[0.00] Kernel command line: console=ttyO0,115200n8 
bone_capemgr.enable_partno=BB-SPIDEV1 bone_capemgr.uboot_capemgr_enabled=1 
root=UUID=e4c7e2e7-0fbf-494c-8d84-305d291d2b7a ro rootfstype=ext4 rootwait 
coherent_pool=1M net.ifnames=0 quiet
[2.376478] bone_capemgr bone_capemgr: Baseboard: 
'A335BNLT,00C0,2516BBBK2265'
[2.376509] bone_capemgr bone_capemgr: 
compatible-baseboard=ti,beaglebone-black - #slots=4
[2.376544] bone_capemgr bone_capemgr: slot #0: auto loading handled by 
U-Boot
[2.376566] bone_capemgr bone_capemgr: slot #1: auto loading handled by 
U-Boot
[2.376587] bone_capemgr bone_capemgr: slot #2: auto loading handled by 
U-Boot
[2.376629] bone_capemgr bone_capemgr: slot #3: auto loading handled by 
U-Boot
[2.376655] bone_capemgr bone_capemgr: enabled_partno PARTNO 
'BB-SPIDEV1' VER 'N/A' PR '0'
[2.376667] bone_capemgr bone_capemgr: slot #4: override
[2.376681] bone_capemgr bone_capemgr: slot #4: auto loading handled by 
U-Boot
[2.377276] bone_capemgr bone_capemgr: initialized OK.
[6.851318] systemd[1]: Set hostname to .
debian@beaglebone:/dev$ ls sp*
ls: cannot access sp*: No such file or directory



SYS2 (stand along beagle bone)

debian@beaglebone:~$ uname -a
Linux beaglebone 4.4.62-ti-r99 #1 SMP Sat Apr 22 14:21:03 UTC 2017 armv7l 
GNU/Linux
debian@beaglebone:~$ dmesg|grep bone
[0.00] Kernel command line: console=ttyO0,115200n8 
bone_capemgr.enable_partno=BB-SPIDEV1 bone_capemgr.uboot_capemgr_enabled=1 
root=UUID=599ccfe6-2803-4ea0-9141-2bb571994e70 ro rootfstype=ext4 rootwait 
coherent_pool=1M net.ifnames=0 quiet
[2.445200] bone_capemgr bone_capemgr: Baseboard: 
'A335BNLT,00C0,2516BBBK22E8'
[2.445233] bone_capemgr bone_capemgr: 
compatible-baseboard=ti,beaglebone-black - #slots=4
[2.445270] bone_capemgr bone_capemgr: slot #0: auto loading handled by 
U-Boot
[2.445291] bone_capemgr bone_capemgr: slot #1: auto loading handled by 
U-Boot
[2.445337] bone_capemgr bone_capemgr: slot #2: auto loading handled by 
U-Boot
[2.445359] bone_capemgr bone_capemgr: slot #3: auto loading handled by 
U-Boot
[2.445379] bone_capemgr bone_capemgr: enabled_partno PARTNO 
'BB-SPIDEV1' VER 'N/A' PR '0'
[2.445390] bone_capemgr bone_capemgr: slot #4: override
[2.445403] bone_capemgr bone_capemgr: slot #4: auto loading handled by 
U-Boot
[2.446010] bone_capemgr bone_capemgr: initialized OK.
[   17.551299] systemd[1]: Set hostname to .
debian@beaglebone:~$ cd /dev
debian@beaglebone:/dev$ ls sp*
spidev1.0  spidev1.1  spidev2.0  spidev2.1

Am I missing something regarding how u-boot is supposed to work?


Thanks
Gaurav

-- 
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/5852e231-e19e-4b1e-9a4f-3c9acd6656e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] UART2 don't work on BBB rev C - kernel 4.4.54

[S]

Em 10/04/2017 11:56, Robert Nelson escreveu:

On Sun, Apr 9, 2017 at 5:43 PM, Vinicius  wrote:

After a few attempts, I found that by positioning BB-UART2, on the line
below on /boot/uEnv.txt, , after BB-SPIDEV1, UART2 transmits!

Cape_enable = bone_capemgr.enable_partno =
BB-SPIDEV1,BB-UART1,BB-UART2,BB-UART4,BB-I2C1

I'm confused by this behavior, could anyone explain this?

kernel overlays are racy and can be hit and miss with a large number
of overlays.

Just convert to using U-Boot Overlays:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

Regards,


Thank you, Robert, I will see


Regards

Vinicius

--
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/53f6af2b-6614-df37-166e-27a706152159%40uol.com.br.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Does SPI1 need timer4 pin 8.07?

[Gaurav S]

Hello,

I am creating a custom cape which uses SPI1 with both cs0 and cs1 and uses 
multiple GPIO pins including 8.07 mapped as GPIO pin.. My prototype has 
been working without issues but I recently noticed a curious issue while 
parsing dmesg:


[   10.775173] pinctrl-single 44e10800.pinmux: pin 44e10890.0 already 
requested by ocp:gpio_helper; cannot claim for 481a.spi
[   10.786802] pinctrl-single 44e10800.pinmux: pin-36 (481a.spi) status 
-22
[   10.793955] pinctrl-single 44e10800.pinmux: could not request pin 36 
(44e10890.0) from group MYTEST_GPIO  on device pinctrl-single
[   10.805516] omap2_mcspi 481a.spi: Error applying setting, reverse 
things back


where MYTEST_GPIO is:

__overlay__ {
  my_example: MYTEST_GPIO {
pinctrl-single,pins = <
0x090 0x07  // P8_07 this seems to be the 
offending pin 
0x094 0x07  // P8_08 
   // few more pins not shown here
>;
 };
 };

The SPI overlay is:
bb_spi1_pins: pinmux_bb_spi1_pins {
pinctrl-single,pins = <
0x190 0x33 /* spi1_sclk, INPUT_PULLUP | MODE3 */
0x194 0x13 /* spi1_d0, OUTPUT_PULLUP | MODE3 */
0x19c 0x13 /* spi1_cs0, OUTPUT_PULLUP | MODE3 */
0x164 0x12 /* spi1_cs1 OUTPUT_PULLUP | MODE2 */
>;
};

I am not defining the use of a timer in the overlays. I understand SPI 
needs to generate a clock in master mode, though I am not sure if one of 
the timers is used for this purpose. However, I am not sure I understand 
why is the pin 8.07 physically required especially when I am mapping it as 
a GPIO pin. 

Some system information if it helps:
debian@beaglebone:~$ uname -a
Linux beaglebone 4.4.47-ti-r87 #1 SMP Mon Feb 6 22:21:49 UTC 2017 armv7l 
GNU/Linux

debian@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
 0: P---L-   0 4D 4.3 LCD CAPE- 4DCAPE-43T ,00A1,4D SYSTEMS 
 ,BB-BONE-LCD4-01
 1: PF  -1
 2: PF  -1
 3: PF  -1
 4: P-O-L-   1 Override Board Name,00A0,Override Manuf,MYTEST-SPIDEV1
 5: P-O-L-   2 Override Board Name,00A0,Override Manuf,MYTEST-GPIO

Any thoughts would be appreciated..

Thanks
Gaurav


-- 
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/6238f910-b71f-475a-ab34-a790cb892821%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Map gpio button to a combination of keyboard keys in device tree or otherwise

[Gaurav S]

Hello,
 I am using the 4G 4inch LCD. I mapped one of the GPIO pins to TAB key in 
the device tree by modifying the "linux,code" in the device tree. I would 
like to map a second GPIO pin to SHIFT + TAB combination. However, the 
documentation 
(http://lxr.free-electrons.com/source/Documentation/devicetree/bindings/input/gpio-keys.txt)
 
does not specify how to achieve this. Any suggestions will be appreciated? 
I am wondering if I actually need to write a driver to map sequence of keys?

Thanks
Gaurav

-- 
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/4879e2e3-7616-471c-aad6-141eea88ca05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: [beagle-alpha] v4.9.x-ti now open for testing...

[Franklin S Cooper Jr]

So one thing I noticed is that the eqep node isn't adding any clocks
compared to EHRPWM and ECAP. So I would be curious if adding the
following entries to the eqep node may solve. I don't really remember
how we came up with this

clocks = <_root_clk_div>;
clock-names = "fck";

>From what I remember for ECAP and PWM that the PWMSS clock gate wouldn't
allow a clock to be ungated once you tell it to gate it. However, the
patch you mentioned shouldn't change anything because by default (on
reset) PWMSS ungates the PWM, ECAP and EQEP clocks.

You mind sharing a boot log showing this failure? Also can you share the
patch your using now for the eqep driver along with dts changes?


On 01/30/2017 03:15 AM, Drew Fustini wrote:
> On Sun, Jan 29, 2017 at 3:13 AM, Drew Fustini  wrote:
>> eqep was working for me in 4.4.x but I get a segmentation fault when I
>> read the sysfs position file:
>> # cat /sys/devices/platform/ocp/48304000.epwmss/48304180.eqep/position
>> [ 1858.108446] Unhandled fault: external abort on non-linefetch
>> (0x1028) at 0xfa304184
>>
>> I'm now reading about pm_runtime_get_sync() in
>> Documentation/power/runtime_pm.txt.  I'll update if I make any
>> progress.
> 
> I'm still investigating but I did notice that the original tieqep
> driver had this code to enable the clock to the eQEP unit:
> https://github.com/Teknoman117/beaglebot/blob/master/encoders/patches/0001-tieqep-driver.patch#L721
> 
> // Enable the clock to the eQEP unit
> status = pwmss_submodule_state_change(pdev->dev.parent, PWMSS_EQEPCLK_EN);
> 
> // If we failed to enable the clocks, fail out
> if (!(status & PWMSS_EQEPCLK_EN_ACK))
> {
>dev_err(>dev, "PWMSS config space clock enable failed\n");
>ret = -EINVAL;
>goto pwmss_clk_failure;
> }
> 
> The function pwmss_submodule_state_change() appears to have been
> removed by this commit:
> 
> commit cc37655e6bbf83ded1e4d1d7ffd977786a845a67
> Author: Cooper Jr., Franklin 
> Date:   Mon Mar 7 13:33:56 2016 -0600
> 
> pwm: pwm-ti*: Remove support for local clock gating
> 
> The PWMSS local clock gating registers have no real purpose on OMAP ARM
> devices. These registers were left over registers from DSP IP where the
> PRCM doesn't exist. There is a silicon bug where gating and ungating 
> clocks
> don't function properly. TRMs will be update to indicate that these
> registers shouldn't be touched.
> 
> Therefore, all code that accesses the PWMSS_CLKCONFIG or PWMSS_CLKSTATUS
> will be removed by this patch with zero loss of functionality by the ECAP
> and EPWM drivers.
> 
> 
> -Drew
> 

-- 
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/a438a516-5f97-9af8-cd26-0e95237544c6%40ti.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Building a 2gb lxqt version

[Gaurav S]

Hello All,

Question: I have noticed the recent builds of lxqt come only in 4GB flavor.

Instead of manually deleting files I was wondering I could get access to a 
2GB version with the latest kernel versions? 

If they don't exist, how do I go about generating one? 

The elinux wiki page 
(http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Build_Instructions)
 
provides some instructions but it clearly states I should use a "fairly 
beefy ARM system". All I have access to is a Beaglebone black rev C. I can 
try building on that but if there are scripts which could do the job on a 
fairly powerful intel/amd machine, i would prefer that instead. 

Using a console version is not an option since I need to build a gui as 
well, hence starting from lxqt seems logical to me. However, if I am wrong 
please correct me.

Thanks
Gaurav

-- 
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/b15f4362-9c30-43da-858b-3752dc31e815%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black can't get USB audio to work

[Jim S]

I got the kernel recompiled with disabled DMA and installed it.  Sound now 
works fine.  

For anyone else wanting to do this I followed Roberts notes and used a 
couple other pages to help with figuring out some details such as 
installing things needed for the cross compile on a Ubuntu PC:
http://elinux.org/Building_BBB_Kernel
http://wiki.beyondlogic.org/index.php/BeagleBoneBlack_Building_Kernel

I didn't mess with TFTP as both those pages show.  After the cross compile 
I  transferred the new kernel file to the BBB with Filezilla (after I 
backed up the system in case of trouble) and installed with dpkg -i ... as 
Robert suggested.  



On Wednesday, November 23, 2016 at 10:26:43 AM UTC-6, RobertCNelson wrote:
>
> On Wed, Nov 23, 2016 at 10:00 AM, Jim S <jimski...@gmail.com > 
> wrote: 
> > Thanks!  I take it that is done on the BBB itself?  (rather than cross 
> > compiled)  Any issue with doing this over ssh?  (particularly the 
> selecting 
> > of kernel configuration boxes) 
>
> Depends, run it on x86, it'll be pretty quick.. 
>
> Run on beagle, wait a few hours.. 
>
> 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/3fa9b2bc-8689-4dfa-ac71-5dab3afadb9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black can't get USB audio to work

[Jim S]

Thanks!  I take it that is done on the BBB itself?  (rather than cross 
compiled)  Any issue with doing this over ssh?  (particularly the selecting 
of kernel configuration boxes)

I saw in another thread

https://groups.google.com/forum/embed/?place=forum/beagleboard=true=true=false=true=http%3A%2F%2Fbeagleboard.org%2Fdiscuss#!category-topic/beagleboard/usb/HQnLSvyYISI
 that it might be possible to achieve the same thing by adding *musb_hdrc*.
*use_dma*=n to the kernel cmdline.  I have only fiddled a bit with this on 
desktops and the BBB is a little different.  Can I add this as to uEnv.txt 
as an addition to the optargs=... line?  That would be a lot simpler, at 
least to test and verify that this is the issue, than recompiling the 
kernel.  If not there, where do I place that? 

-- 
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/af6583cb-66ec-412e-940c-325b079afd9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone Black can't get USB audio to work

[Jim S]

Apparently, from a little searching and reading others are having similar 
trouble and the issue is DMA for the USB audio - it needs to be disabled (I 
think...).  This requires recompiling the kernel with this disabled.  
Haven't compiled a kernel before so am looking for some detailed 
instructions on this and replacing the existing kernel (would like to keep 
the rest of the configured system if possible).  Anyone have any good links 
on doing this?  I have found several places that give the line setting the 
option of disabling DMA and I think I could add that to detailed kernel 
cross compiling instructions...

-- 
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/b52dce74-7d6a-4c05-ae3b-98f5d2881028%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] There is a Linux live image for BBB ?

[S]

Anyone know if exist a Debian (or another Linux distro) Live image for 
BBB, bootable from uSD card?


I need a system that can boot in a RAM disk, without modifying any files 
on the uSD card, because I need the operating system to be verifiable, 
via SHA sum, for example, and therefore must be immutable.


Debian have scripts to build a live image, but only for i386 and AMD64 
architectures.



Thanks in advance,


Vinicius

--
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/1978b669-c155-7e1c-8a74-6fe100bd8e9b%40uol.com.br.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beaglebone Black can't get USB audio to work

[Jim S]

Trying to add USB audio device to BBB.  I am running this headless - no 
HDMI display, no direct keyboard or mouse.  USB audio device is C-Media.  
Have a powered USB hub.  Have an Arduino board connected by USB but don't 
think it affects this issue.  USB audio device is seen by aplay -l and 
aplay -L but trying to use it doesn't work and usually hangs the system 
requiring a power cycle.  System is for Asterisk VOIP and from here:
http://beaglebone-asterisk.raspbx.org/


root@raspbx:~# uname -a
Linux raspbx 3.14.37-ti-r57 #1 SMP PREEMPT Sat Apr 4 06:18:14 UTC 2015 
armv7l armv7l armv7l GNU/Linux

root@raspbx:~# aplay -l
 List of PLAYBACK Hardware Devices 
card 0: Black [TI BeagleBone Black], device 0: HDMI hdmi-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Device [C-Media USB Audio Device], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
root@raspbx:~#

root@raspbx:~# aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
default:CARD=Black
TI BeagleBone Black,
Default Audio Device
sysdefault:CARD=Black
TI BeagleBone Black,
Default Audio Device
dmix:CARD=Black,DEV=0
TI BeagleBone Black,
Direct sample mixing device
dsnoop:CARD=Black,DEV=0
TI BeagleBone Black,
Direct sample snooping device
hw:CARD=Black,DEV=0
TI BeagleBone Black,
Direct hardware device without any conversions
plughw:CARD=Black,DEV=0
TI BeagleBone Black,
Hardware device with all software conversions
default:CARD=Device
C-Media USB Audio Device, USB Audio
Default Audio Device
sysdefault:CARD=Device
C-Media USB Audio Device, USB Audio
Default Audio Device
front:CARD=Device,DEV=0
C-Media USB Audio Device, USB Audio
Front speakers
surround40:CARD=Device,DEV=0
C-Media USB Audio Device, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=Device,DEV=0
C-Media USB Audio Device, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Device,DEV=0
C-Media USB Audio Device, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Device,DEV=0
C-Media USB Audio Device, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Device,DEV=0
C-Media USB Audio Device, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=Device,DEV=0
C-Media USB Audio Device, USB Audio
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=Device,DEV=0
C-Media USB Audio Device, USB Audio
Direct sample mixing device
dsnoop:CARD=Device,DEV=0
C-Media USB Audio Device, USB Audio
Direct sample snooping device
hw:CARD=Device,DEV=0
C-Media USB Audio Device, USB Audio
Direct hardware device without any conversions
plughw:CARD=Device,DEV=0
C-Media USB Audio Device, USB Audio
Hardware device with all software conversions
root@raspbx:~#

As an attempt to test I ran:
root@raspbx:/opt/jimscripts# speaker-test -D default:Device

speaker-test 1.0.27.2

Playback device is default:Device
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 2048 to 16384
Period size range from 1024 to 1024
Using max buffer size 16384
Periods = 4
was set period_size = 1024
was set buffer_size = 16384
 0 - Front Left

At this point the system hung and I had to power cycle.

I edited /boot/uboot/eEnv.txt to disable HDMI audio so USB is default audio 
but this didn't seem to help.  Current line in that file is:

optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN

What should I be looking at/doing?  Any help is appreciated.

-- 
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/e677854e-521c-40ef-abb1-b5c1c8fc4709%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] live image for BBB ?

[S]

Anyone know if exist a Debian Live image for BBB, bootable from uSD card?

I need a system that can boot without modifying any files on the uSD 
card, because I need the operating system to be verifiable, via SHA sum, 
for example, and therefore must be immutable.


Debian have scripts to build a live image, but I don't know if it works 
on BBB.



Thanks in advance,


Vinicius

--
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/e1181bb6-ac5b-00a6-b1a5-d49e16f87167%40uol.com.br.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Installing SGX drivers - omaplfb & pvrsrvkm not loaded

[James S]

I know nothing about this but here's what I did tonight to get this going 
(its failed many times in the past for me!)

- Downloaded 
https://rcn-ee.com/rootfs/bb.org/testing/2016-10-09/lxqt-4gb/bone-debian-8.6-lxqt-4gb-armhf-2016-10-09-4gb.img.xz
- Burned a card, booted and grew the partition. Rebooted.
- Ran sudo ./update_kernel.sh --bone-rt-kernel --lts. Rebooted.
- Installed the correct Linux headers

Now, for the SGX I followed the instructions at 
http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black but 
they didn't work. I ended up with a '.bin' rather than a tar file, in a dl 
folder but there was no deploy folder. Anyway, I had done this a few months 
ago and saved the tar file from then. I installed that tar per the 
instructions.

Then I followed the instructions at 
https://groups.google.com/forum/?hl=en#!msg/beagleboard/sOhHuq_T6KQ/xDeaoWyeBgAJ;context-place=msg/beagleboard/D-lhg28O5m4/yqRTbZPFDQAJ,
 
namely:-
sudo apt-get install ti-sgx-es8-modules-`uname -r`
sudo depmod -a `uname -r` 
sudo update-initramfs -uk `uname -rcode here...


Rebooted.

The result:
Last login: Fri Oct 14 19:27:03 2016 from 192.168.1.66
debian@beaglebone:~$ lsmod | grep omaplfb
omaplfb12048  0
tilcdc 28057  1 omaplfb
pvrsrvkm  147997  1 omaplfb
debian@beaglebone:~$ glxgears
26 frames in 5.0 seconds =  5.161 FPS
54 frames in 5.1 seconds = 10.644 FPS
54 frames in 5.0 seconds = 10.700 FPS
54 frames in 5.1 seconds = 10.670 FPS
54 frames in 5.0 seconds = 10.709 FPS
54 frames in 5.1 seconds = 10.670 FPS
54 frames in 5.0 seconds = 10.707 FPS
54 frames in 5.1 seconds = 10.670 FPS
54 frames in 5.0 seconds = 10.704 FPS
^C
debian@beaglebone:~$ uname -a
Linux beaglebone 4.1.34-bone-rt-r24 #1 PREEMPT RT Thu Oct 13 03:42:46 UTC 
2016 armv7l GNU/Linux
debian@beaglebone:~$

I think this is a complete account, I hope it helps.

Regards,
James


On Friday, October 14, 2016 at 3:09:46 PM UTC+1, Jean-Sebastien Stoezel 
wrote:
>
> Hi Robert:
>
> Would you have an additional suggestion on this issue? If not, where would 
> you suggest I turn to to investigate this further?
>
> Regards,
> JS
>
>
> On Wed, Oct 12, 2016 at 7:41 PM, Jean-Sebastien Stoezel <
> js.st...@gmail.com > wrote:
>
>> Hi Robert:
>>
>> I did upgrade to the latest -bone-rt kernel. 
>> I am not getting the error I used to have when trying to restart PVR, but 
>> suprisingly pvrsvrkm is not loaded
>>
>> root@beaglebone:~# lsmod | grep omaplfb
>> root@beaglebone:~# sudo /etc/init.d/sgx-startup.sh start
>> sgx: Starting PVR
>> root@beaglebone:~# lsmod | grep omaplfb
>> root@beaglebone:~# lsmod | grep omapl
>> root@beaglebone:~# lsmod | grep omap
>> omap_sham  19380  0
>> omap_aes   13255  0
>> omap_rng4338  0
>> rng_core7209  1 omap_rng
>> snd_soc_omap2565  1 snd_soc_davinci_mcasp
>> snd_soc_core  157683  3 
>> snd_soc_davinci_mcasp,snd_soc_edma,snd_soc_omap
>> snd_pcm_dmaengine   5045  2 snd_soc_core,snd_soc_omap
>> snd_pcm77695  4 
>> snd_soc_davinci_mcasp,snd_soc_core,snd_soc_omap,snd_pcm_dmaengine
>> spi_omap2_mcspi10456  0
>> root@beaglebone:~# lsmod | grep pvrsrvkm
>> root@beaglebone:~# sudo /etc/init.d/sgx-startup.sh restart
>> sgx: Restarting PVR
>> root@beaglebone:~# lsmod | grep pvr
>>
>> Is there another way of checking whether omaplfb and pvrsrvkm are loaded?
>>
>> Regards,
>> JS
>>
>> On Wed, Oct 12, 2016 at 5:17 PM, Jean-Sebastien Stoezel <
>> js.st...@gmail.com > wrote:
>>
>>> Hi Robert:
>>>
>>> Thank you for a quick and detailed answer. This is greatly appreciated.
>>> I will give this a try tonight.
>>>
>>> Regards,
>>> Jean-Sebastien
>>>
>>>
>>> > On Oct 12, 2016, at 17:03, Robert Nelson >> > wrote:
>>> >
>>> > On Wed, Oct 12, 2016 at 4:50 PM, Jean-Sebastien Stoezel
>>> >  wrote:
>>> >> It looks like we crossed replies/emails.
>>> >>
>>> >> I am unsure what you mean by:
>>> >> "
>>> >> http://elinux.org/BeagleBoardDebian#Mainline_.28lts.29
>>> >>
>>> >> Mainline (lts)
>>> >>
>>> >> 4.1.x BeagleBone/BeagleBone Black + SGX
>>> >> --bone-kernel --lts
>>> >>
>>> >> 4.1.x BeagleBone/BeagleBone Black + RT + SGX
>>> >> --bone-rt-kernel --lts
>>> >>
>>> >> cd /opt/scripts/tools/
>>> >> git pull
>>> >> sudo ./update_kernel.sh  "
>>> >>
>>> >> At this time I am not sure you are implying that I need to update the
>>> >> kernel, or that I need to get a different version of SGX from git. 
>>> "Install
>>> >> the "4.1.x" lts/bone kernel:
>>> >> http://elinux.org/BeagleBoardDebian#Mainline_.28lts.29;. The kernel 
>>> I am
>>> >> using is 4.1.22-ti-rt-r59.
>>> >> Would it be possible for you to clarify whether or not I have the 
>>> right
>>> >> kernel, and, if not, point me to a kernel that would allow me to 
>>> install
>>> >> am33x-v4.1, since this is the only version that currently works?
>>> >
>>> > Correct, you don't have the correct kernel..
>>> >
>>> > cd 

Re: [beagleboard] Re: How Flashing Now Works with Debian

[Joshua S]

THANKS The git pull saved me ! I couldn't get the correct loader files 
to save my life.

On Monday, July 14, 2014 at 10:50:20 AM UTC-7, RobertCNelson wrote:
>
> On Mon, Jul 14, 2014 at 12:29 PM,   
> wrote: 
> > Hi, 
> > 
> > I am getting as well the "Error: script halting, system unrecognized." 
> when 
> > executing beaglebone-black-eMMC-flasher.sh. 
> > The image I have flashed is from here 
> > http://elinux.org/BeagleBoardDebian#Flasher 
> > 
> https://rcn-ee.net/deb/flasher/wheezy/BBB-eMMC-flasher-debian-7.5-console-armhf-2014-07-06-2gb.img.xz.
>  
>
> > When I check with "LC_ALL=C lsblk -l" the mountpoint "/boot/uboot" is 
> > missing. 
> > 
> > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT 
> > mmcblk1boot0 179:16 0 1M 1 disk 
> > mmcblk1boot1 179:24 0 1M 1 disk 
> > mmcblk0 179:0 0 7.4G 0 disk 
> > mmcblk1 179:8 0 1.8G 0 disk 
> > mmcblk1p1 179:9 0 96M 0 part 
> > mmcblk1p2 179:10 0 1.7G 0 part / 
> > 
> > Is there anything that I can do? 
> > What I want to do is clone a beaglebone black to multiple others, is 
> > beaglebone-black-eMMC-flasher.sh the best way to do that? 
> > Thanks in advance. 
>
> So in, 2014-07-06 i rewrote a lot of things... 
>
> First, make sure you run: 
>
> cd /opt/scripts/tools/ 
> git pull 
>
> Next open: /boot/uEnv.txt 
>
> Uncomment this line: 
>
> #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v2.sh 
>
> At this point your microSD card is set to flash the eMMC.. so shutdown 
> (sudo halt) and get ready to flash stuff.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.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/e50a2f57-f6a9-48a2-b1d0-95b50151613e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Unable to ssh to beagleboard

[rakesh s m]

Hi,
I was using beagleboard and was able o SSH , However, all of a sudden the 
SSH is not working. I have tried with restarting the dropbear serverin 
/etc/init.d , but it says dropbear command not found. Help!

-- 
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/08205bd4-e2b1-47f3-ac3a-876d8cb71325%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBone Black (4.4.20 kernel) + RobertCNelsons SGX driver not working?

[James S]

After your first message, what steps did you make to get omaplfb loading?
Jas

On Saturday, September 10, 2016 at 11:48:47 PM UTC+1, Aitor Ardanza wrote:
>
> ome progress:
>
> Following these steps I get that the lsmod command answer me with 
> something.
>
> But I'm no sure if the 3d hardware acceleration is on.
>
> If I lanuch weston the image that I can see is no good...
>
>
> 
> How can I know if the driver is well installed?
>
> El sábado, 10 de septiembre de 2016, 3:18:52 (UTC+2), Aitor Ardanza 
> escribió:
>>
>>
>> Hi,
>>
>> I´m having troubles trying to put working the 3d acceleration with the 
>> SGX driver. I the steps I followed are:
>>
>> Base system: I'm using the 
>> BBB-eMMC-flasher-debian-8.4-lxqt-2gb-armhf-2016-04-10-2gb.img.xz 
>> 
>>  firmware 
>> with the kernel updated to 4.4.20-bone-rt-r13
>>
>> With this system glxgears command shows an average of 23 fps. I suppose 
>> that the graphics acceleration is not activated.
>> So I start following the steps of the wiki in 
>> http://elinux.org/BeagleBoardUbuntu#SGX_Drivers.
>>
>> I download the zip file from 
>> http://elinux.org/BeagleBoardUbuntu#SGX_Drivers.
>>
>> It seems that there is no error in the process and I reboot the system... 
>> but when I call "lsmod | grep omaplfb", nothing comes on the screen and 
>> glxgears shows like before...
>>
>> I'm missing a step?
>>
>> Taking advantage of this thread, another question ... My ultimate goal is 
>> to run an application with OpenGL ES 2.0. What windowing system you suggest 
>> me to manage the graphics context?
>>
>> Thaks a lot!!!
>> AItor 
>>
>

-- 
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/7cc0510d-da1f-4000-977d-89bf612ece1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to troubleshoot crash?

[Jim S]

Running 3.14 ubuntu with  asterisk image latest from 
http://beaglebone-asterisk.raspbx.org/ but support seems to be going away.  
Have added some simple scripts to talking to an Arduino board but think the 
problem is more basic.  Latest image ran ok for about a month but now is 
crashing almost daily.  This is headless and when it crashes I can't access 
it although it may still be running - I'm not sure...  Hardly any 
experience looking at logs, etc.  How do I figure out what is going on and 
how to fix - i.e. where to start?

If the fix is too involved I may just abandon asterisk for now and go with 
a maintained version of ubuntu (which one?) if that's what's needed for a 
stable system.  The other scripts are more important now and I could run 
asterisk on a real PC box.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/58698703-e570-498e-bd2a-43fdf9635f80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Bagle bone boot is stopped at starting kernel

[James S]

I found some of the following links helpful:


https://groups.google.com/forum/#!searchin/beagleboard/nfs-uEnv|sort:date/beagleboard/X5jSWpPXegY/JxjNKU22A6kJ
https://groups.google.com/forum/#!searchin/beagleboard/[FAILED]$20Failed$20to$20start$20Login$20Service.|sort:date/beagleboard/iQVDxV9wb6A/-AgFwZcvAQAJ

James


On Wednesday, July 13, 2016 at 2:49:13 PM UTC+1, Ratan wrote:
>
>
>   Hi ,
>
>  I am  newbie and trying to compile kernel and using TFTP want to boot my 
> beaglebone black .
>
> My problem is , my board gets hanged up at "starting Kernel "
>
>
> Log is as below . Thank you for any help .
>
>
> U-Boot# setenv ipaddr 192.168.1.7
> U-Boot# setenv serverip 192.168.1.5
> U-Boot# tftpboot 0x80F8 am335x-boneblack.dtb
> link up on port 0, speed 100, full duplex
> Using cpsw device
> TFTP from server 192.168.1.5; our IP address is 192.168.1.7
> Filename 'am335x-boneblack.dtb'.
> Load address: 0x80f8
> Loading: T 
>  9.8 KiB/s
> done
> Bytes transferred = 58133 (e315 hex)
> U-Boot# tftpboot 0x80007fc0 uImage-BBB
> link up on port 0, speed 100, full duplex
> Using cpsw device
> TFTP from server 192.168.1.5; our IP address is 192.168.1.7
> Filename 'uImage-BBB'.
> Load address: 0x80007fc0
> Loading: T 
> TFTP error: 'File not found' (1)
> Not retrying...
> U-Boot# tftpboot 0x80007FC0 uImage-BBB
> link up on port 0, speed 100, full duplex
> Using cpsw device
> TFTP from server 192.168.1.5; our IP address is 192.168.1.7
> Filename 'uImage-BBB'.
> Load address: 0x80007fc0
> Loading: T 
> #
>  #
>  #
>  #
>  #
>  #
>  #####
>  #
>  #
>  307.6 KiB/s
> done
> Bytes transferred = 7810336 (772d20 hex)
> U-Boot# setenv bootags console=ttyO0,115200n8 root=/dev/mmcblk0p2 ro 
> rootfstype=ext4 rootwait 
> U-Boot# bootm 0x80007fc0 - 0x80f8
> ## Booting kernel from Legacy Image at 80007fc0 ...
>Image Name:   Linux-4.1.24+
>Image Type:   ARM Linux Kernel Image (uncompressed)
>Data Size:7810272 Bytes = 7.4 MiB
>Load Address: 80008000
>Entry Point:  80008000
>Verifying Checksum ... OK
> ## Flattened Device Tree blob at 80f8
>Booting using the fdt blob at 0x80f8
>XIP Kernel Image ... OK
> OK
>Using Device Tree in place at 80f8, end 80f91314
>
> Starting kernel ...
>
>

-- 
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/e3a13ba6-a148-48ff-bca6-e92c014a0aee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Connman & bone-debian-8.5-lxqt-2gb-armhf-2016-06-19-2gb.img

[James S]

I downloaded & wrote the bone-debian-8.5-lxqt-2gb-armhf-2016-06-19-2gb.img 
image 
to a card. 
It doesn't seem to start up the ethernet connection on boot - I have to run 
sudo systemctl start connman.service from the serial terminal. Here's 
the full output.
I tried the 4gb lxqt as well but it seems to be the same.

What am I doing wrong?

James

-- 
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/9547341d-b87a-48af-82f0-e6ed78a95630%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Burned out BBB with AIN0 > 1.8V

[Doyle S]

Thanks all!

No doubt it was my fault - I'm not trying to blame anyone else, I was more 
curious about what I did to my board. =)
I had a couple other BBB's around so I was a bit cavalier with the whole 
thing - lesson learned, haha.

I really appreciate all the info, and will check all the suggested reading.

Gerald - Assuming I just killed the AM335, would most of the other 
components on the board be okay, aside from possibly the Power Management 
chip?




On Monday, June 6, 2016 at 10:12:43 AM UTC-7, Doyle S wrote:
>
> Hi,
>
> Yesterday I was trying to use some of the analog inputs on the BBB to read 
> my photodiode, and instead, I think I blew up the power supply on my board.
> With power applied, I get no PWR led, so I'm pretty certain it's dead.
> Short of replacing the power management chip, is there anything I can 
> do/replace to get the board working again?
>
>
> Brief Background
>
> I hooked up the photodiode to an Arduino and was able to read 0 - 5V 
> easily, so I wanted to do the same on the BBB.
> I read some of the materials re: AIN on the BBB, but apparently I missed 
> all the references to the max voltage of 1.8V!
> I started by enabling the analog inputs on the BBB, and started with AIN0.
>
> With nothing attached, I was reading about 0 - so far, so good.
> Then I figured I'd try to see what a full 5.0V read out, so I plugged in 
> the VDD 5V to AIN0, and all the LEDs went out instantly.
> Now all LEDs stay off, even the PWR LED, when power is applied.
>
> No doubt, it was stupid, but I have a few additional takeaways - 
> 1. Very minor references in most BBB documentation/webpages discussing 
> Analog Inputs and max voltages. 
> Coming from working with Pi's and Arduino's, it was common to have analog 
> inputs range from 0 to 5V, so the 1.8V was unexpected.
>
> 2.  Isn't there any protection at all from this kind of damage?  Or was 
> the main problem that I used the VDD 5V and fed it into the AIN0 port?
> Would I have killed it if I used the VDD ADC instead of the VDD 5v or 
> would using the VCC ADC possibly have protected it?
>
> 3.  What is the "normal" way of using the BBB analog inputs with 5V 
> levels?  Is it possible - or is there where I would use a level-shifter or 
> zener diode?
>
> Thanks for the any comments or additional info provided!
>

-- 
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/8b780479-5694-4cc5-8f60-17e9bdfd8ec5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Burned out BBB with AIN0 > 1.8V

[Doyle S]

Hi,

Yesterday I was trying to use some of the analog inputs on the BBB to read 
my photodiode, and instead, I think I blew up the power supply on my board.
With power applied, I get no PWR led, so I'm pretty certain it's dead.
Short of replacing the power management chip, is there anything I can 
do/replace to get the board working again?


Brief Background

I hooked up the photodiode to an Arduino and was able to read 0 - 5V 
easily, so I wanted to do the same on the BBB.
I read some of the materials re: AIN on the BBB, but apparently I missed 
all the references to the max voltage of 1.8V!
I started by enabling the analog inputs on the BBB, and started with AIN0.

With nothing attached, I was reading about 0 - so far, so good.
Then I figured I'd try to see what a full 5.0V read out, so I plugged in 
the VDD 5V to AIN0, and all the LEDs went out instantly.
Now all LEDs stay off, even the PWR LED, when power is applied.

No doubt, it was stupid, but I have a few additional takeaways - 
1. Very minor references in most BBB documentation/webpages discussing 
Analog Inputs and max voltages. 
Coming from working with Pi's and Arduino's, it was common to have analog 
inputs range from 0 to 5V, so the 1.8V was unexpected.

2.  Isn't there any protection at all from this kind of damage?  Or was the 
main problem that I used the VDD 5V and fed it into the AIN0 port?
Would I have killed it if I used the VDD ADC instead of the VDD 5v or would 
using the VCC ADC possibly have protected it?

3.  What is the "normal" way of using the BBB analog inputs with 5V levels? 
 Is it possible - or is there where I would use a level-shifter or zener 
diode?

Thanks for the any comments or additional info provided!

-- 
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/3dd92ed6-0fc6-44fc-8b0f-2eca5d690390%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Not getting output on the PWM

[ide . neil . s]

Hi Everyone,

I'm trying to get the PWM outputs up and rugging with this python script:

>import time

>import Adafruit_BBIO.PWM as PWM

>myPWM="P9_14"

>PWM.start(myPWM, 100, 1)
>#for i in range(0,5):
>#DC=input("What Duty Cycle Would You Like (0-100)? ")
>#PWM.set_duty_cycle(myPWM, DC)

>time.sleep(10.0)

>PWM.stop(myPWM)
>PWM.cleanup()

The script runs but I get no physical out output.  Any ideas whats going on?

-- 
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/ec83d12e-5cc8-4a97-9e1b-09a672b10f30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: VGA camera capture

[João M . S . Silva]

It does have MJPEG but opencv is converting the format to YUYV. And also
does your board have I/O pins digital and analogue?


It has lots of GPIO's, but I don't know if any of them are analog: 
https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXino-LIME/open-source-hardware


João M. S. Silva

--
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/5746D34E.4050905%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: VGA camera capture

[João M . S . Silva]

I suppose you were using OpenCV in C++. For setting the desired 
resolution in C++ you have to do as you did in the Python code. 
Something like: http://stackoverflow.com/a/24867771


You should also set it to MJPEG, if possible: 
http://docs.opencv.org/2.4/modules/highgui/doc/reading_and_writing_images_and_video.html?highlight=cv_cap_prop_frame_width#videocapture-set


Please be more structured and succinct in what your current issue is so 
that it's easier to help. Have you considered the code from 
https://linuxtv.org/downloads/v4l-dvb-apis/capture-example.html?


Is your code in Python or C++?

In order to solve the larger problem you have to break it down into 
smaller ones.


João M. S. Silva

On 05/26/2016 09:23 AM, Tinashe Mudavanhu wrote:

I have finally managed to get a video stream (at least i can say for
now) by changing the frame resolution inside the python opencv code
using instructions on
http://stackoverflow.com/questions/11420748/setting-camera-parameters-in-opencv-python.
The maximum resolution i can set it to was 640x480 with a 5fps frame
rate, increasing the frame rate will result in a select timeout message.
At 320x240 i can set it  up to 30fps and running htop the CPU
utilization will be fluctuating around 86-90%. The python code was
taking about 12% and most of the chunk was on tightvnc about 60% (maybe
because of the frame window being displayed).

This is the code i was running;

import cv2


#capture from camera at location 0
cap = cv2.VideoCapture(0)
#set the width and height, and UNSUCCESSFULLY set the exposure time
cap.set(3,320)
cap.set(4,240)
cap.set(5, 30)

while True:
 ret, img = cap.read()
 cv2.imshow("input", img)
 #cv2.imshow("thresholded", imgray*thresh2)

 key = cv2.waitKey(10)
 if key == 27:
 break


cv2.destroyAllWindows()
cap.release()

And also the resolution i forced the camera to in the opencv code is the
one displayed after running v4l2-ctl -V;
root@beaglebone:~/Project/Testing# v4l2-ctl -V
Format Video Capture:
 Width/Height  : 320/240
 Pixel Format  : 'YUYV'
 Field : None
 Bytes per Line: 640
 Size Image: 153600
 Colorspace: SRGB
root@beaglebone:~/Project/Testing#

What you figured out about bandwidth is really a serious issue. I have a
friend who did not experience this problem on their RPi (only much
higher resolutions resulted in select timeout messages, message because
i don't think it is an error)  maybe because it has many USB ports
meaning higher bandwidth compared to BBB with only one.
I wonder what will happen when connecting the BBB wirelessly, with a
wifi dongle and camera on a USB hub.



On Thu, May 26, 2016 at 8:39 AM, Tinashe Mudavanhu <tinam...@gmail.com
<mailto:tinam...@gmail.com>> wrote:

Silva,

It does have MJPEG but opencv is converting the format to YUYV. And
also does your board have I/O pins digital and analogue?

On Thu, May 26, 2016 at 8:35 AM, Tinashe Mudavanhu
<tinam...@gmail.com <mailto:tinam...@gmail.com>> wrote:

The 160x120 video stream had no latency but the other camera
with 1280x720 was slow, video was displayed as images being
flipped like book pages.

I need to understand something from your files. Does it mean the
rest of my iris recognition code has to be in the
framegrabber.py client file and also this file can also run on
BBB? Do i need the zhelper.h file when my PC is running Ubuntu?

Here is my setup like. I have a PC running Ubuntu connected to
the BBB via usb and also sharing internet via the same cable
(there is no wired connection, only the PC is connected to
wifi). I want to see the video stream on my BBB for debugging
purposes and once it is working fine it doesn't have to show the
video stream. I am accessing the BBB Desktop/GUI via a tightvnc
client running on my Ubuntu PC. Thats when i will move to the
hub for a wired connection so that everyone connected to the hub
can access web pages served by the BBB (running lighttpd
webserver).

I was successful in the part of running BBB as a webserver
(without an video stream to show on the site because i don't
need it) but then the first part of getting a video stream to
show was not possible because of select timeout errors.

On Thu, May 26, 2016 at 12:35 AM, Matthew Witherwax
<ablec...@gmail.com <mailto:ablec...@gmail.com>> wrote:

Looks like framegrabber was able to capture images based on
the output you provided. Did you look at the images?

If it works for you then the code for the subscriber here
http://blog.lemoneerlabs.com/post/bbb-mjpeg-streaming will
show you how to load it into opencv.

----
   

Re: [beagleboard] Re: VGA camera capture

[João M . S . Silva]

encoding cam
if its the software and
running at 320 is just as
efficient as preencoded hd video.


On 10 Sep 2013, at 13:16,
Matthew Witherwax
<able...@gmail.com> wrote:


João,

1.  Glad to hear you are
making progress.  My blog is
at blog.lemoneerlabs.com
<http://blog.lemoneerlabs.com>.
Unfortunately I have yet to
post my write up on the USB
cameras, but I will get it
done soon.  I can tell you
with the Logitech C920 it is
possible to capture 1920x1080
frames with the FPS set to 30
in both MJPEG and YUYV format.

2.  v4l2grab sets the format
to YUYV before grabbing the
frames.  It then converts the
captured frame to a jpeg and
saves it.  I will post a
version to my blog this week
that uses MJPEG instead.
Typical MJPEG implementations
encode each video frame as a
jpeg.  The code I wrote puts
the webcam in MJPEG mode for
capture and saves the
returned frame.  In the case
of the Logitech C920, the
returned frame is a jpeg
image.  It seems by going
this route the camera
actually creates the jpeg
sparing the BBB from having
to do it.  In addition, the
jpeg is considerably smaller
than the YUYV frame resulting
in less load on the USB.  I
would appreciate you testing
the output when I post the
code as it is entirely
possible that not all cameras
handle MJPG the same, and the
result might not be a valid jpeg.

3.  13.2 MB/s is the limit I
was able to reach through
testing.  You should note the
webcam I tested with for that
number only did bulk
transfers which guarantee
delivery.  It may be slightly
higher for isochronous
transfers as frames can (and
seem to) get dropped.  I am
not sure why that is the
limit.  It maybe a hardware
issue or a USB driver
implementation issue.  During
further testing on several
laptops, the newer ones could
reach a higher throughput
even though all had a USB 2
bus which would lead me to
believe it is hardware
related, but it is a question
for the hardware guys.

4.  I will post my code this
week.  Please test it with
your MJPEG capable cameras,
and let me k

Re: [beagleboard] Re: VGA camera capture

[João M . S . Silva]

Hi Tinashe,

My two cents:


root@beaglebone:~/libjpeg-turbo-1.3.0/build# make
make  all-recursive
make[1]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
Making all in java
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/java'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/java'
Making all in simd
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
make  all-am
make[3]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
Making all in md5
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/md5'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/md5'
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
make[1]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
root@beaglebone:~/libjpeg-turbo-1.3.0/build#


There is no error above.


Before compiling libjpeg-turbo i tested my code to see what will be
happening on the resolution and frame rate. I am working with a Logitech
QuickCam E3500 which has support for both YUVY and MJPEG. I set the
resolution to 320x240 with a 30fps frame rate but after running the
code, got select timeout errors and the resolution had changed to
640x480 YUVY with a 15fps frame rate;


Due to this, among other reasons, we gave up on the BeagleBone Black and 
are now using an A20-OLinuXino-LIME.


João M. S. Silva

--
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/5745B238.8020505%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Automatic shutdown options for loss of power?

[Jim S]

I already have a big battery in the UPS so I don't need another one.  What 
I need is control.  I have an Arduino connected to the BBB for I/O that 
could help with this.  If the Arduino could interrupt the power to the BBB 
(or trigger the boot process some other way) that would handle power up.  
It could also handle delay for power down.  Something like this:

BBB and Arduino powered from UPS.
Another wall wart power supply from AC line to Arduino to sense state of AC 
line

Upon loss of AC line the arduino would delay an amount of time and send a 
signal to the BBB to trigger shutdown.  Time delay would prevent shutdown 
for short line drops.  After time to shut down it would drop power to the 
BBB.
Upon regaining AC line it would close switch to apply power to BBB.  A 
small delay would probably be a good idea to eliminate possibility of very 
short off times.

The switch could be a relay or solid state switch.  And the Arduino could 
be any microprocessor.  

On Monday, May 16, 2016 at 11:44:59 AM UTC-5, Harvey White wrote:
>
> On Mon, 16 May 2016 09:14:13 -0700 (PDT), you wrote: 
>
> >That is pretty limited.  Sounds like just punting the software and going 
> >with a mostly hardware solution would be just as easy but then I am a 
> >hardware guy.  I think a UPS with auto shutdown AND restart capability 
> >would be something a lot of people would want but I could be wrong. 
>
>
> How about an inexpensive microprocessor (of whatever variety), an 
> on-board backup battery, and enough smarts to shut down a BBB 
> intelligently?  Perhaps a pin on the BBB might be dedicated to a 
> shutdown option.  It's a combination of both hardware and software. 
> How much you pay for it, how much you decide to build into it depends 
> on your own desires. 
>
> 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/f3a5549c-4bda-4629-a042-49b5c8d3d64f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Automatic shutdown options for loss of power?

[Jim S]

That is pretty limited.  Sounds like just punting the software and going 
with a mostly hardware solution would be just as easy but then I am a 
hardware guy.  I think a UPS with auto shutdown AND restart capability 
would be something a lot of people would want but I could be wrong.

-- 
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/1d40616f-9270-449b-86fb-e3cac2823375%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Automatic shutdown options for loss of power?

[Jim S]

Recently lost power and corrupted my sd card badly and had to start over.  
I have seen the battery "UPS" for BBB type but don't need another battery.  
I have a small APC UPS for the BBB, DSL modem, a VOIP box, and a router but 
the UPS does not have a comm port to report status to the BBB.  Would like 
to set up so that when the AC power drops the BBB will shutdown in 5 
minutes (most outages are shorter but this is still much before the UPS 
runs out of power).  If the power is restored before that continue to run.  
When power is restored start up.  With an additional wall wart power supply 
I could generate a logic level signal for when the AC line is ok (input to 
UPS).  Does anything like this exist?  If not, anything similar enough that 
I could hack up the scripts a bit and get there?  Would rather not have to 
start from scratch.

-- 
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/ed9d6695-08ab-48b6-a3dc-8e645b8f4e4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] SGX not installing

[James S]

Still not working, even tried rebooting.

debian@beaglebone:/opt/gfxinstall$ sudo /etc/init.d/sgx-startup.sh start
sgx: Starting PVR
debian@beaglebone:/opt/gfxinstall$ lsmod | grep omaplfb
debian@beaglebone:/opt/gfxinstall$ lsmod | grep omaplfb
debian@beaglebone:/opt/gfxinstall$ sudo reboot

Last login: Fri Apr  1 22:15:11 2016 from base2.lan
debian@beaglebone:~$ lsmod | grep omaplfb
debian@beaglebone:~$



On Friday, April 1, 2016 at 11:34:13 PM UTC+1, RobertCNelson wrote:
>
> On Fri, Apr 1, 2016 at 5:17 PM, James S <s19...@gmail.com > 
> wrote: 
> > Oops! I did a reboot and lsmod | grep omaplfb but nothing shows up. 
>
> sudo /etc/init.d/sgx-startup.sh start 
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] SGX not installing

[James S]

Oops! I did a reboot and lsmod | grep omaplfb but nothing shows up.

On Friday, April 1, 2016 at 11:12:13 PM UTC+1, James S wrote:
>
> Purrfect Robert, thank you for the prompt response!
>
> On Friday, April 1, 2016 at 11:07:07 PM UTC+1, RobertCNelson wrote:
>>
>> On Fri, Apr 1, 2016 at 5:03 PM, James S <s19...@gmail.com> wrote: 
>> > I followed the instructions here 
>> > http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black 
>>  and 
>> > the install fails at the BBB with: 
>> > debian@beaglebone:/opt/gfxinstall$ sudo ./sgx-install.sh 
>> > ./sgx-install.sh: 29: ./sgx-install.sh: lsb_release: not found 
>> > 
>> > The build on Ubuntu completes without reporting a fault and produces 
>> > GFX_5.01.01.02_es8.x.tar.gz. 
>> > 
>> > 
>> > What am I doing wrong? 
>> > James. 
>> > 
>> > debian@beaglebone:/opt/gfxinstall$ uname -r 
>> > 4.1.20-bone20 
>> > 
>> > debian@beaglebone:/opt/gfxinstall$ cat /etc/dogtag 
>> > BeagleBoard.org Debian Image 2016-03-27 
>>
>>
>> sudo apt-get update ; sudo apt-get install lsb-release 
>>
>> then rerun: 
>>
>> debian@beaglebone:/opt/gfxinstall$ sudo ./sgx-install.sh 
>>
>> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] SGX not installing

[James S]

Purrfect Robert, thank you for the prompt response!

On Friday, April 1, 2016 at 11:07:07 PM UTC+1, RobertCNelson wrote:
>
> On Fri, Apr 1, 2016 at 5:03 PM, James S <s19...@gmail.com > 
> wrote: 
> > I followed the instructions here 
> > http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black 
>  and 
> > the install fails at the BBB with: 
> > debian@beaglebone:/opt/gfxinstall$ sudo ./sgx-install.sh 
> > ./sgx-install.sh: 29: ./sgx-install.sh: lsb_release: not found 
> > 
> > The build on Ubuntu completes without reporting a fault and produces 
> > GFX_5.01.01.02_es8.x.tar.gz. 
> > 
> > 
> > What am I doing wrong? 
> > James. 
> > 
> > debian@beaglebone:/opt/gfxinstall$ uname -r 
> > 4.1.20-bone20 
> > 
> > debian@beaglebone:/opt/gfxinstall$ cat /etc/dogtag 
> > BeagleBoard.org Debian Image 2016-03-27 
>
>
> sudo apt-get update ; sudo apt-get install lsb-release 
>
> then rerun: 
>
> debian@beaglebone:/opt/gfxinstall$ sudo ./sgx-install.sh 
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] SGX not installing

[James S]

I followed the instructions here  
http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black  and 
the install fails at the BBB with:
debian@beaglebone:/opt/gfxinstall$ sudo ./sgx-install.sh
*./sgx-install.sh: 29: ./sgx-install.sh: lsb_release: not found*

The build on Ubuntu completes without reporting a fault and 
produces GFX_5.01.01.02_es8.x.tar.gz.


What am I doing wrong?
James.

debian@beaglebone:/opt/gfxinstall$ uname -r
4.1.20-bone20

debian@beaglebone:/opt/gfxinstall$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-03-27



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

Re: [beagleboard] BBB Jessie 8.3 boot default eMMC or sd card?

[S]

Thank you!

Vinicius

Em 23-03-2016 15:55, Robert Nelson escreveu:

On Wed, Mar 23, 2016 at 1:32 PM, S <sdmi@uol.com.br> wrote:

Is it possible to disable boot via sd card, enabling them only by pressing
the boot button?

If affirmative, how to proceed?

The boot search order is controlled from here:

https://github.com/u-boot/u-boot/blob/v2016.03/include/configs/am335x_evm.h#L87-L93

mmc 0 = microSD
mmc 1 = eMMC

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

Re: [beagleboard] VNC running on Ubuntu

[Kuba S.]

Hi,
thank you very much for your response.
It does not says "XOpenDisplay failed" any more.
I'm able to make a connection with my BBB board.
Unfortunately I have another issue that I can't get rid of.

The screen that shows up is without anything (status bar, clock, start
etc.). The only thing I can do is a right click to show context menu. There
I can choose from couple of commands like run terminal, switch monitors or
run web browser. And those works - I can run the terminal or view web
pages. However I can't get to e.g. file browser.
It's the same when I run x11vnc and tightvnc.
I've went through couple of examples from the web and proposition of
solving similar problems. Nothing worked.

Could this be somehow connected to "headless" debian installation (the
monitor was never attached)?

regards,
Kuba

2016-01-12 17:36 GMT+01:00 :

> Kuba, you have to install lightdm, then start the server with:
> sudo x11vnc -auth /var/run/lightdm/root/:0 -display :0 .forever
>
> W dniu poniedziałek, 4 stycznia 2016 13:37:59 UTC+1 użytkownik
> ja.q...@gmail.com napisał:
>>
>> Hi all,
>> I'm having similar problem with BBB (rev A5B).
>> It's running Debian 8 from official beagle bone black image.
>> I've installed *x11vnc *package using *apt-get* and it gives me the same
>> info as for Vincenzo Cacciatore (...XOpenDisplay failed. No -display or
>> DISPLAY...)
>> *pgrep -l -f -- -auth* command returns nothing.
>> *x11vnc -findauth* returns *xauth: not found*
>> I was logged as *root.*
>>
>> I did never attached external screen (over HDMI) to this board so I'm not
>> sure if GUI is there.
>>
>> Can anyone help please?
>>
>> regards,
>> Kuba
>>
>>
>> W dniu niedziela, 15 września 2013 18:15:07 UTC+2 użytkownik Nuno napisał:
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On 09/15/2013 05:16 AM, Vincenzo Cacciatore wrote:
>>> > 15/09/2013 09:15:28 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid:
>>> 2024
>>> > 15/09/2013 09:15:28 XOpenDisplay("") failed.
>>> > 15/09/2013 09:15:28 Trying again with XAUTHLOCALHOSTNAME=localhost ...
>>> > 15/09/2013 09:15:28
>>> > 15/09/2013 09:15:28 *** XOpenDisplay failed. No -display or DISPLAY.
>>> >
>>> > Can someone help me?
>>>
>>> You'll have to run x11vnc with the user that is currently running X,
>>> e.g., use sudo -u USERNAME -i for that or you can run x11vnc as root if
>>> you prefer.
>>> Alternatively you can pass the xauth option or set the XAUTHORITY
>>> environment variable and point to the right place
>>>
>>> pgrep -l -f -- -auth
>>>
>>> then
>>> x11vnc -auth BLA
>>>
>>> BLA is what the pgrep command will give you, look for the parameter
>>> after the X -auth
>>>
>>> You can also use x11vnc -findauth , check the x11vnc manual page for
>>> more details:
>>>
>>> man x11vnc
>>>
>>>
>>> cheers,
>>> Nuno
>>>
>>> - --
>>> http://aeminium.org/nuno/
>>> -BEGIN PGP SIGNATURE-
>>> Version: GnuPG v1.4.12 (GNU/Linux)
>>>
>>> iQIcBAEBAgAGBQJSNd0LAAoJEPIY6fuKMkz5zqcP/0UJHiRQIy96i8MVpWO4IOva
>>> pFrloM9yGLYDEE/8hODfDQYovGF+yrt3CsDRZzgSHSeYknnGTPUQznCQ/XkYuHOQ
>>> EklNstK1hDjdSfi1fjSKgh3ySapmIHyUm6fZtddSkibtQcmDtxl+r4ZTj8MRYF02
>>> 9KSJsG2895UdgrW5wxUcXsoUtTlSatTmQ0yAMrKsAXASqwvTTUc/KHjTLfgfqvoG
>>> GIV0yiAfNL3rEyyliS84bZEBfg4Vmpy0pXeC4+ik0LoWVzsCcjAs/klS3IPjF6sR
>>> CbS+r9MFvO/aShWQd8YzRMMh2G+sdxQDGn1XueVJVB0L3ARdKFRNuNFkP4axWFDL
>>> ED3rypG+dx2OsD5L6mvh7GC0dZ7cA4zPlUDapNitBNiH+s1UdoNiZ1UKsGSsNtfI
>>> Uf/D28GF+RF5HQRnbDwYTT98x0/YSZikvIHesFc969VcEWtRZLva/OkLKbfXgl7X
>>> L9kH40xbjzefXbauaNmSUuZOChr/UKIRrLrfk2KogtJXSICtKzlsooUmPlrAVthq
>>> hLbZg5sMlTz/VdWLWLUTbcAK5GLBtIx414pWZ4tKtJ2pFBlHQil7lv23tnE0BBQe
>>> Aeznu5/P8UmfRqk75XZRj+Q3vwV5P/0vFh8K6NihBSEd3DdZcFgU1kNSZJoabTCQ
>>> EoxaB/8VDVZYhHuMVuka
>>> =2L+9
>>> -END PGP SIGNATURE-
>>>
>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/D-lhg28O5m4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Newest Debian images from eLinux missing ntp and other packages

[Doyle S]

Thanks so much for the fast response!  

I'm helping my coworker out, so I had to ask him which images he used.

But I did a bit of research and confirmed your comments back, and it all 
makes perfect sense now. =)

We were using the 
"BBB-eMMC-flasher-debian-7.9-console-armhf-2015-11-03-2gb.img" image, 
which, as you pointed as, is a console release.
Thanks for clarifying this - I totally understand and appreciate the need 
for a lightweight image, so I didn't mean to suggest these things *should* 
be added to the console release.
Same goes for wireless-tools.

With the above image, I confirmed the lack of sbin and wrong date on boot 
up, no biggie.
I tried syncing the time, but I got command not found and didn't find it in 
sbin, but installing some version of ntp seems to resolve that.

As for the issue we faced with DNS issues and issues updating the repo, it 
was the exact same issue in this post - 
https://groups.google.com/forum/#!category-topic/beagleboard/ubuntu/DjFqxreT1AA
At the time, I had to hard code the IP for the missing repos (I think it 
was also the ports.ubuntu repo) and it worked.
But I just tested this on a fresh flash and wasn't able to recreate the 
issue, so in my test case, everything worked great.
I'll dig a bit more on this but I think this may have been a weird "freak" 
occurrence.

Thanks again for your response and help, now back to my BBB!

Have a good one, Robert

On Wednesday, December 2, 2015 at 5:48:23 PM UTC-8, RobertCNelson wrote:
>
> On Wed, Dec 2, 2015 at 6:33 PM,   wrote: 
> > I have been working the BBB Rev B and C for over a year, and I've been 
> using 
> > the Debian images provided by eLinux and Beagleboard, available from - 
> > 
> > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases 
> > 
> > and http://beagleboard.org/latest-images 
> > 
> > In the most recent builds from 2015-11-03, I've been having a lot of 
> trouble 
> > with missing system tools and packages. 
> > Some examples include - 
>
> Please include the file name, there's dozen images... 
>
> > - wrong date and time set due to ntp service not being installed, 
> installing 
> > ntp resolves this issue 
>
> wheezy: ntpdate 
> jessie: systemd-timesync 
>
> > - inability to connect using supported wifi adapter due to missing 
> > wireless-tools package 
>
> your using the "console" image... 
>
> > - missing DNS support which causes apt-get to fail as it is unable to 
> > correctly resolve the IP addresses for the rcn.ee repos included in the 
> > builds 
>
> okay, this is od.. 
>
>
> > - missing /sbin directory in PATH, including missing ifconfig command, 
> > adding /sbin to path resolves these issues 
>
> yeap, this is the "console" image, can't fix this as patch isn't 
> installed.. 
>
> > Did I miss some announcement or release notes about these releases that 
> says 
> > they are lighter than previous builds? 
> > 
> > Why didn't I have most of these issues with previous builds? 
> > IIRC, all the builds I used before included ntp, /sbin in the PATH, and 
> DNS 
> > support, and wireless worked OOTB (after editing 
> /etc/network/interfaces) 
>
> Based on that, it sounds like your using the "console" over the 
> "lxde/lxqt" image.  The goal with the "console" image was to be as 
> small but yet "flash" the eMMC..  Not everyone likes to "apt-get 
> remove xyz" instead they want something very small, and wireless tools 
> are not on that requirement list.. 
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] SPI BBB Master, BBB Slave

[ravi s]

Hi John,

Yes I can use UART or other protocol to achieve same data communication.
But I'm working for client . They should require spi slave in kernel.  So
struggling to get it up. We asked TI also regarding this but they also
don't have any sample code for testing spi slave..

Regards
Ravi
On 5 Nov 2015 23:46, "John Syne" <john3...@gmail.com> wrote:

> Hi Ravi,
>
> This is something I’m currently working on. However, for your application,
> why do you need to use SPI? Surely you could use IP Sockets or UART to
> achieve the same thing. Also, McASP has both master and slave support
> through the sound subsystem. Specifically you can use spdif_receiver.c and
> spdif_transmitter.c codecs to do what you need as show in[1]. Thereafter,
> implement something similar to alsa arecord and aplay to send and receive
> data from a user space app.
>
> [1] http://processors.wiki.ti.com/index.php/Sitara_Linux_Audio_DAC_Example
>
> Regards,
> John
>
>
>
>
> On Nov 4, 2015, at 2:29 AM, ravi@gmail.com wrote:
>
> Hi,
>
> I'm trying to setup SPI slave mode with same above method and
> changed OMAP2_MCSPI_MODULCTRL_MS set to 0 for slave mode.
>
> i'm facing issue in master mode and slave both on sckl pin configuration.
>
> http://elinux.org/BeagleBone_Black_Enable_SPIDEV in this link why sckl
> pin is configured as INPUT 0x33 but it will work with same configuration if
> i change it to OUTPUT it doesn't work with any slave device and no clock on
> that pin.
>
> Please anyone clarify this doubt and issues.
>
> For slave mode i tried to change OMAP2_MCSPI_MODULCTRL_MS bit in driver
> file spi_omap2_mcspi.c but no use. still its master only.
>
> Please provide any suggestion or exact procedure.
>
> Thank you in advance.
>
> Regard s
> Ravi
>
> On Thursday, September 18, 2014 at 5:45:47 AM UTC+5:30, phil...@gmail.com
> wrote:
>>
>>
>> I am having issues with SPI between two BBB that may be simple to solve.
>> I have spidev_test loopback working on each board but am having problems
>> connecting the two.
>>
>> spi0 master dts:
>>   0x150 0x10  /* spi0_sclk, OUTPUT_PULLUP | MODE0 */
>>   0x154 0x30  /* spi0_d0, INPUT_PULLUP | MODE0 */
>>   0x158 0x10  /* spi0_d1, OUTPUT_PULLUP | MODE0 */
>>   0x15c 0x10  /* spi0_cs0, OUTPUT_PULLUP | MODE0 */
>>
>> spi slave dts:
>>   0x150 0x30  /* spi0_sclk, INPUT_PULLUP | MODE0 */
>>   0x154 0x10  /* spi0_d0, OUTPUT_PULLUP | MODE0 */
>>   0x158 0x30  /* spi0_d1, INPUT_PULLUP | MODE0 */
>>   0x15c 0x30  /* spi0_cs0, INPUT_PULLUP | MODE0 */
>>
>>
>> The oscilloscope shows activity when spi0_sckl (P9_17) is not connected
>> but nothing when P9_17 is connected between both boards.
>> I am sending bytes from master with the command: echo 1 > /dev/spidev1.0
>>
>> I need 4-8mbit/sec transfer, is this achievable by bit banging over GPIO
>> and would that be a viable alternative to getting SPI working?
>>
>>
> --
> 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.
> 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/jQ1LH6IDH1A/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Errors loading new Debian image 2015-10-04

[lachlan . s . peter]

I have just installed the Debian 8.2 image via the eMMC 4GB flasher on the 
BeagleboneBlack RevC. As the system installs I get the following messages / 
Errors

[ 1113.740804] systemd[1]: Job console-setup.service/start deleted to break 
ordering cycle starting with basic.target/start

[ SKIP ] Ordering cycle found, skipping LSB: Set console font and keymap

.

[ 1114.681515] systemd[1]: systemd-modules-load.service: main process 
exited, code=exited, status=1/FAILURE

[FAILED] Failed to start Load Kernel Modules.

See 'systemctl status systemd-modules-load.service' for details.

.

[FAILED] Failed to start Store Sound Card State.

See 'systemctl status alsa-store.service' for details.

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

[beagleboard] Errors installing the Debian Image 2015-10-04

[lachlan . s . peter]

I have just installed the new Debian 8.2 via the flasher image on a 
BeagleboneBlack Rev C with 4DCape. I have changed the uEnv.txt file to 
disable HDMI. I get the following errors on install: (Even when I dont 
change the uEnv.txt file from default)

  [ 1113.740804] systemd[1]: Job 
console-setup.service/start deleted to break ordering cycle starting with 
basic.target/start

[ SKIP ] Ordering cycle found, skipping LSB: Set console font and keymap

.

[ 1114.681515] systemd[1]: systemd-modules-load.service: main process 
exited, code=exited, status=1/FAILURE

[FAILED] Failed to start Load Kernel Modules.

See 'systemctl status systemd-modules-load.service' for details.

.

[FAILED] Failed to start Store Sound Card State.

See 'systemctl status alsa-store.service' for details.


Then when I boot the new image I get the error:


   [FAILED] Failed to start Load Kernel Modules.

   See 'systemctl status systemd-modules-load.service' 
for details.


Then I do apt-get update.


Then when I do apt-get upgrade I get the following errors:

WARNING: missing /lib/modules/4.2.2-armv7-x2

Ensure all necessary drivers are built into the linux image!

depmod: ERROR: could not open directory /lib/modules/4.2.2-armv7-x2: No 
such file or directory

depmod: FATAL: could not search modules: No such file or directory

depmod: WARNING: could not open 
/var/tmp/mkinitramfs_0Ayicd/lib/modules/4.2.2-armv7-x2/modules.order: No 
such file or directory

depmod: WARNING: could not open 
/var/tmp/mkinitramfs_0Ayicd/lib/modules/4.2.2-armv7-x2/modules.builtin: No 
such file or directory
   .
   Warning: Unit file of cloud9.socket changed on disk, 'systemctl 
daemon-reload' recommended.
   
   c9-core-installer:Installing nak
   npm WARN excluding symbolic link 
tests/filelist_fixtures/symlink-to-1.txt -> 1.txt
   npm WARN excluding symbolic link 
tests/filelist_fixtures/symlink-to-nowhere.txt -> nowhere.txt
   npm WARN excluding symbolic link 
tests/search_fixtures/symlink-to-file1.txt -> file1.txt
   npm WARN excluding symbolic link 
tests/filelist_fixtures/symlink-to-1.txt -> 1.txt
   npm WARN excluding symbolic link 
tests/filelist_fixtures/symlink-to-nowhere.txt -> nowhere.txt
   npm WARN excluding symbolic link 
tests/search_fixtures/symlink-to-file1.txt -> file1.txt

Any ideas why this is occuring and how the problem can be fixed ?
Lachlan

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

Re: [beagleboard] Damage on power off?

[S]

I think the best approach is to use a UPS and detect the AC fault, by 
any means, and fire a automatic shutdown.
But for an unassisted equipment, how to start it when the power is 
normalized?



Vinicius

On 16-09-2015 12:38, evilwulfie wrote:

This is a problem then for random power outages. guess we all need to
use a UPS then to prevent damage ?




On 9/16/2015 6:30 AM, Robert Nelson wrote:

On Wed, Sep 16, 2015 at 7:54 AM, Bill Pretty  wrote:

So the proper thing is “sudo shutdown now –h”  ?

Or the push-button... (which does above ^^)

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

[beagleboard] WL1835MOD on Beaglebone Black

[s . bhaskar0468]

Hai all,

Greetings !!!
We got the Beaglebone Black board*(BBB)* from one of the TI distributor.
And we developed the WL1385MOD Module cape based on SDIO lines.

We want to integrate Wlan with the BBB.
can you please provide me the dts patch and expansion connections for BBB.
I have 4 lines SDIO, SDIO_CMD, SDIO_CLK, WL_ENABLE, WL_IRQ.
Please provide me the pins where i have connect in expansion of the BBB.

Thanks  Regards,
~ Bhaskar S

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

[beagleboard] Re: BeagleBone Black rev C HDMI color issues (Debian wheezy 7.8)

[Sean S]

You're right, it is to do with 16 vs 24 bit colour, 
see https://groups.google.com/d/topic/beagleboard/PjKwp6XCNnA/discussion 
for a fix that worked for me.

On Friday, July 10, 2015 at 12:09:36 PM UTC-7, David Alston wrote:

 I have been having issues with my beaglebone black when connecting to a 
 monitor over HDMI. Certain colors are missing from the output as shown in 
 the attached images. From looking around it may be an issue with the sitara 
 processor on the BB, possibly having to do with 16 vs 24 bit color. However 
 I could not get a workaround form what I have come across. Has anyone else 
 had similar problems? Ideas for a fix or solution? Any help would be 
 greatly appreciated.

 FullSizeRender is the test image on a windows machine, FullSizeRender2 is 
 as it appears on the BB using Imagemagick.

 Let me know if more information is required.


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

Re: [beagleboard] lxde works from remote desktop but not on HDMI

[S P Rao Vemuri]

Thanks. it works after screen size adjustment.

On Friday, June 19, 2015 at 8:49:06 PM UTC+5:30, RobertCNelson wrote:

 On Fri, Jun 19, 2015 at 10:13 AM,  vrks...@gmail.com javascript: 
 wrote: 
  I have BBB rev C. I updated eMMC with debian version 2015-03-1 version 
 7.8. 
  It has Lxde preinstalled. 
  Lxde works with remote desktop, but not on HDMI monitor. The HDMI 
 monitor 
  only shows beagle dog image. 
  
  Can any one tell me what is wrong with my setup. 

 First, do you see the mouse cursor moving? 

 If so, turn off HDMI over-scan on your HDMI monitor as the menu is 
 underneath. 

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

[beagleboard] Ethernet refusing connection

[James S]

I'm using BBB A5A hardware.

I just built a  card with the Debian 8 (Small Flash) kernel using the 
instructions at https://eewiki.net/display/linuxonarm/BeagleBone+Black.
 (With the following exception: Instead of
sudo cp -v ./ti-linux-kernel-dev/deploy/${kernel_version}.zImage /media/
rootfs/boot/vmlinuz-${kernel_version}
I used 
sudo cp -v ./bb-kernel/deploy/${kernel_version}.zImage /media/rootfs/boot/
vmlinuz-${kernel_version}
since ti-linux-kernel-dev directory didn't exist. All instances of 
ti-linux-kernel-dev were substituted.)

It boots fine but the ethernet connection refuses connection. Using the 
serial debug connection, I can ping from the BBB. 
I also get the the following:
root@arm:~# dmesg | grep -i phy
[0.00] Booting Linux on physical CPU 0x0
[2.805706] 47401300.usb-phy supply vcc not found, using dummy regulator
[2.808594] 47401b00.usb-phy supply vcc not found, using dummy regulator
[3.372555] davinci_mdio 4a101000.mdio: detected phy mask fffe
[3.372825] davinci_mdio: dt: updated phy_id[0] from phy_mask[fffe]
[3.372849] davinci_mdio: dt: updated phy_id[1] from phy_mask[fffe]
[3.373837] libphy: 4a101000.mdio: probed
[3.373858] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, 
driver SMSC LAN8710/LAN8720
[6.399080] net eth0: phy found : id is : 0x7c0f1
[6.399150] libphy: PHY 4a101000.mdio:01 not found
[6.404248] net eth0: phy 4a101000.mdio:01 not found on slave 1


I seen mention of the *0003-cpsw-search-for-phy.patch *here but I think 
thats already applied. (Its in the patches folder in bb-kernel)

The above output is from the 4.1 kernel, I get the following with the 3.8 
kernel:
root@arm:~# dmesg | grep -i phy
[0.00] Booting Linux on physical CPU 0x0
[0.571890] davinci_mdio 4a101000.mdio: detected phy mask fffe
[0.572897] libphy: 4a101000.mdio: probed
[0.572915] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, 
driver SMSC LAN8710/LAN8720
[4.163115] net eth0: phy found : id is : 0x7c0f1
[4.163144] libphy: PHY 4a101000.mdio:01 not found
[4.163155] net eth0: phy 4a101000.mdio:01 not found on slave 1
[7.240352] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
root@arm:~#

I've seen similar issues on this forum but I can't figure out what the 
solution is - can anyone help?

Regards,
James

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

[beagleboard] Re: Ethernet refusing connection

[James S]

I don't recognize any errors here.

root@arm:/home/debian# ifconfig -a
eth0  Link encap:Ethernet  HWaddr C8:A0:30:C3:70:BE
  inet addr:192.168.1.11  Bcast:192.168.1.255  Mask:255.255.255.0
  inet6 addr: fd78:6a89:d8ad:3100:caa0:30ff:fec3:70be/64 
Scope:Global
  inet6 addr: fe80::caa0:30ff:fec3:70be/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:199 errors:0 dropped:0 overruns:0 frame:0
  TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:37848 (36.9 KiB)  TX bytes:2104 (2.0 KiB)
  Interrupt:40

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:160 errors:0 dropped:0 overruns:0 frame:0
  TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:12960 (12.6 KiB)  TX bytes:12960 (12.6 KiB)

root@arm:/home/debian# dhclient eth0
RTNETLINK answers: File exists
root@arm:/home/debian#

Thanks for the quick response!

On Friday, May 29, 2015 at 2:56:06 PM UTC+1, James S wrote:

 I'm using BBB A5A hardware.

 I just built a  card with the Debian 8 (Small Flash) kernel using the 
 instructions at https://eewiki.net/display/linuxonarm/BeagleBone+Black.
  (With the following exception: Instead of
 sudo cp -v ./ti-linux-kernel-dev/deploy/${kernel_version}.zImage /media/
 rootfs/boot/vmlinuz-${kernel_version}
 I used 
 sudo cp -v ./bb-kernel/deploy/${kernel_version}.zImage /media/rootfs/boot/
 vmlinuz-${kernel_version}
 since ti-linux-kernel-dev directory didn't exist. All instances of 
 ti-linux-kernel-dev were substituted.)

 It boots fine but the ethernet connection refuses connection. Using the 
 serial debug connection, I can ping from the BBB. 
 I also get the the following:
 root@arm:~# dmesg | grep -i phy
 [0.00] Booting Linux on physical CPU 0x0
 [2.805706] 47401300.usb-phy supply vcc not found, using dummy regulator
 [2.808594] 47401b00.usb-phy supply vcc not found, using dummy regulator
 [3.372555] davinci_mdio 4a101000.mdio: detected phy mask fffe
 [3.372825] davinci_mdio: dt: updated phy_id[0] from phy_mask[fffe]
 [3.372849] davinci_mdio: dt: updated phy_id[1] from phy_mask[fffe]
 [3.373837] libphy: 4a101000.mdio: probed
 [3.373858] davinci_mdio 4a101000.mdio: phy[0]: device 
 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
 [6.399080] net eth0: phy found : id is : 0x7c0f1
 [6.399150] libphy: PHY 4a101000.mdio:01 not found
 [6.404248] net eth0: phy 4a101000.mdio:01 not found on slave 1


 I seen mention of the *0003-cpsw-search-for-phy.patch *here but I think 
 thats already applied. (Its in the patches folder in bb-kernel)

 The above output is from the 4.1 kernel, I get the following with the 3.8 
 kernel:
 root@arm:~# dmesg | grep -i phy
 [0.00] Booting Linux on physical CPU 0x0
 [0.571890] davinci_mdio 4a101000.mdio: detected phy mask fffe
 [0.572897] libphy: 4a101000.mdio: probed
 [0.572915] davinci_mdio 4a101000.mdio: phy[0]: device 
 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
 [4.163115] net eth0: phy found : id is : 0x7c0f1
 [4.163144] libphy: PHY 4a101000.mdio:01 not found
 [4.163155] net eth0: phy 4a101000.mdio:01 not found on slave 1
 [7.240352] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
 root@arm:~#

 I've seen similar issues on this forum but I can't figure out what the 
 solution is - can anyone help?

 Regards,
 James


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

[beagleboard] Putty, PSCP

[p . c . s . laurie . 58]

I'm just starting with a Beaglebone Black Rev C, Cortex A8

I've got Putty working over the USB cable to my desktop XP machine, and I'm 
trying to upload files from DOS using PSCP

According to Putty, I have a working directory

root@beaglebone:~/dsp

I'd have thought this should do it:

 pscp %1 root@192.168.7.2/dsp

 but I get:: 'local to local copy not supported'

 If I try

 pscp %1 root@http://192.168.7.2/dsp 



 I get  'ssh_int: Host does not exist'

 Any clues?


Ah! Got it:

pscp file to transfer root@192.168.7.2:dsp/

I'll post this because it would have helped me.



 






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

Re: [beagleboard] Re: interfacing IP camera with BBB

[Arya K S]

Hi,
I configured the BBB with DHCP settings. The board, the PC and the camera
are connected to the same network using a switch. My camera is fixed in
outdoor. Using 192 address I think it is not possible. Use DHCP
settings and try to get an IP address in the same series of camera. It will
work.

On Fri, Apr 24, 2015 at 9:45 PM, Felipe ordoñez carlosfelip...@gmail.com
wrote:


 Hi, I've been trying to do the same thing.

 In my case, I connected the BBB to the LAN network, and I can see the
 video on my BBB browser  typing 192..:port (IP camera adress).

 Another thing or problem is my Ip axis camera P1344 is PoE,  I tried to
 connect it with a switch PoE, directly to my BBB in order to access with
 the ip adress (like a short communication between BBB and Ip axis camera) ,
 It doesn't work.

 The BBB is not detecting or is able to access to the IP camera   even
 doing a ping.

 Do you know something about it???

 thanks



 El viernes, 19 de diciembre de 2014, 3:23:14 (UTC-5), aryaksa...@gmail.com
 escribió:

 Hi,

 I have an IP camera and i needs to interface it with BBB through ethernet
 port.I have configured my BBB to dhcp and it got an ip address when
 connected to our network. I don't know the following things. Please give me
 some input to my work.

 1) is BBB compatible with IP camera(device driver)?
 2)  is mjpg suitable for video streaming in BBB?

  --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups BeagleBoard group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/beagleboard/3s5ny1vewcw/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: interfacing IP camera with BBB

[Arya K S]

hi,
i have seen the video from my PC in which i have installed Mobaxterm
viewer. i also checked the board with LCD monitor through hdmi interface.
at that time i entered as debian user. otherwise u can not access the
chromium browser. in my application it is not necessary to see the video.
if you are building a standalone application it is better to use separate
display. the resolution of the camera was set to very low, since i got
overread error while running the application.

On Tue, Apr 7, 2015 at 6:02 PM, Andrew Commando lamdadro...@gmail.com
wrote:

 from where did you see the video?
 from another computer?
 from HDMI ?

 i want to build a stand alone

 On Tue, Apr 7, 2015 at 6:57 AM, Arya K S aryaksasidha...@gmail.com
 wrote:

 Hi,

 I connected Axis camera with bbb. But i didn't install any other drivers
 for it. i think drivers are available for all IP cameras. But the frame
 rate was more than 25fps. I used 'Mobaxterm' for watching the bbb. Open bbb
 as a root user. i have successfully completed my project in bbb. but the
 resolution should be very low , otherwise you will get 'overread' error.
 just change your frame rate and resolution.

 On Tue, Apr 7, 2015 at 6:07 AM, Andrew Commando lamdadro...@gmail.com
 wrote:

 Hi I want to connect also my IP camera to BBB.
 I did it with chromium extension.
 The frame rate are very slow :(. sgx driver should give more FPS ?
 I try to install zoneminder  motion with no luck.
 Did you find a solution;

  --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups BeagleBoard group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/beagleboard/3s5ny1vewcw/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.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 a topic in the
 Google Groups BeagleBoard group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/beagleboard/3s5ny1vewcw/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.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 a topic in the
 Google Groups BeagleBoard group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/beagleboard/3s5ny1vewcw/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: interfacing IP camera with BBB

[Arya K S]

Hi,

I connected Axis camera with bbb. But i didn't install any other drivers
for it. i think drivers are available for all IP cameras. But the frame
rate was more than 25fps. I used 'Mobaxterm' for watching the bbb. Open bbb
as a root user. i have successfully completed my project in bbb. but the
resolution should be very low , otherwise you will get 'overread' error.
just change your frame rate and resolution.

On Tue, Apr 7, 2015 at 6:07 AM, Andrew Commando lamdadro...@gmail.com
wrote:

 Hi I want to connect also my IP camera to BBB.
 I did it with chromium extension.
 The frame rate are very slow :(. sgx driver should give more FPS ?
 I try to install zoneminder  motion with no luck.
 Did you find a solution;

  --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups BeagleBoard group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/beagleboard/3s5ny1vewcw/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Date/Time syncronization (Ubunutu 13.04)

[s . p . emmons]

So, troubled by the same situation and not finding any alternatives, I 
tried this technique. However, it doesn't seem to work -- at least on my BB 
Black with the 2015-03-01 build.

In fact, I had a hint that it would not work even before I tried it.

My original /etc/timestamp file had a March 1 date matching the build date, 
but my /var/log/syslog timestamps on reboot began with March 5 while 
today's date is March 15.

I don't know why the system decided to startup using March 5 as its date.

And after following the suggestion of updating /etc/timestamp using a cron 
job -- I chose once per minute since the /etc/timestamp file captured only 
hours/minutes (why??) -- and confirming that the file was being updated 
appropriately, after a reboot, I'm back to March 5 until after networking 
is up and NTP can connect to a server.

So, how DOES the system decide to choose a starting time on reboot???

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

[beagleboard] HDMI issues with specific board

[johnny . s . warren]

Hey guys, I've got a screen here, it's 1280x800. Specifically it's the 
ODROID-VU.
I've also got 2 beaglebone blacks. Both are RevC. One is on 3.8.13-bone47 
so factory and the other is on 3.8.13-bone70 so latest.

Thing is the factory board shows up on my screen just fine while my updated 
one does not. I tested my cable and latest board on a 9 with the same 
resolution and it seems to work just fine so it's not the cable or the 
connector.
xrandr on both the working and non working come back with Can't open 
display 
I tried adding video=HDMI-A-1:1280x800@60 to /boot/uEnv.txt and nothing 
happened

At this point I really don't know what to do, nor do I know where to get 
the factory image.

Any ideas?

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

[beagleboard] Prevent data drop via uart

[James S]

Strange. I'm using 3 uarts at 115k baud and Qt5 and don't have a problem.

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

[beagleboard] Dell monitor touchscreen and QT tslib

[James S]

Which version of Qt are you using?
Debian or Angstrom On the Bone?
Is there any other event in /dev/input?

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

[beagleboard] Re: Changes done in uboot source code or Kernel source code not getting reflected onto Serial console

[purushotham . s . patil]

Hi srini,


Did you got the resolution for this?

Regards,
Purushotham

On Sunday, November 2, 2014 5:56:59 PM UTC+5:30, Srini wrote:

 Dear beaglebone black community,


 1. As am newbie in using ti-sdk-am335x-evm-07.00.00.00 where we have uboot 
  source code , when am trying to modify the uboot  kernel source code 
 ie., am trying to add printks in the source code , compiled  flashed the 
 images onto SD card but am unable to see the print messages that I have 
 added onto the serial console,

 Could any body please let me know why I am unable to see the print 
 messages onto the console or am I missing any uboot or kernel 
 configurations that is to be done inorder to see the print messages onto 
 the console

 Could you please provide me the detailed steps related to compiling  
 flashing the images onto SD card or Nand  with any uboot or kernel 
 configurations  inorder to see my print messgaes onto the console

 2. As am newbie to device tree concept as earlier was using board files, 
 Could any body please let me know what is the difference between board file 
  device tree,
  Could any body please help me do how to gain the quick understanding of 
 device tree in uboot  linux kernel ti-sdk-am335x-evm-07.00.00.00  what is 
 significance of uboot  kernel device tree when it would be required  how 
 to modify it

 Awaiting for your replies
 Many Thanks in advance,



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

[beagleboard] Re: Disable boot messages

[James S]

Changed the uEnv.txt line to
cmdline=quiet loglevel=0 init=/lib/systemd/systemd
worked for me.


On Thursday, November 6, 2014 3:43:00 PM UTC, James S wrote:

 I have a Qt app which launches automatically but some boot messages appear 
 on screen before it starts up. How can I disable these boot messages?

 I've tried
 1. editing  /etc/systemd/system/getty.target.wants/getty@tty1.service and 
 commenting out ExecStart.
 2. removing lightdm
 3. checking /boot/uEnv.txt, it doesn't contain any console command ( 
 https://groups.google.com/forum/?fromgroups#!searchin/beagleboard/disable$20screen$20boot$20message|sort:date/beagleboard/765LGQ4a0bY/_wqpId-7C3IJ
  
 )

 Thanks,
 James


 uname -a
 Linux beaglebone 3.8.13-bone67 #1 SMP Wed Sep 24 21:30:03 UTC 2014 armv7l 
 GNU/Linux

 Messages include...
 [0.372552] omap2_mbox_probe: platform not supported
 [0.527489] tps65217-bl tps65217-bl: no platform data provided
 [0.614605] bone-capemgr bone_capemgr.9: slot #1: No cape found
 [0.651712] bone-capemgr bone_capemgr.9: slot #2: No cape found
 [0.688822] bone-capemgr bone_capemgr.9: slot #3: No cape found
 [0.707546] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' 
 failed
 [0.741892] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
 requested by 44e10800.pinmux; cannot claim for gpio-leds.8
 [0.753606] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status 
 -22
 [0.760896] pinctrl-single 44e10800.pinmux: could not request pin 21 on 
 device pinctrl-single



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

[beagleboard] Disable boot messages

[James S]

I have a Qt app which launches automatically but some boot messages appear 
on screen before it starts up. How can I disable these boot messages?

I've tried
1. editing  /etc/systemd/system/getty.target.wants/getty@tty1.service and 
commenting out ExecStart.
2. removing lightdm
3. checking /boot/uEnv.txt, it doesn't contain any console command ( 
https://groups.google.com/forum/?fromgroups#!searchin/beagleboard/disable$20screen$20boot$20message|sort:date/beagleboard/765LGQ4a0bY/_wqpId-7C3IJ
 
)

Thanks,
James


uname -a
Linux beaglebone 3.8.13-bone67 #1 SMP Wed Sep 24 21:30:03 UTC 2014 armv7l 
GNU/Linux

Messages include...
[0.372552] omap2_mbox_probe: platform not supported
[0.527489] tps65217-bl tps65217-bl: no platform data provided
[0.614605] bone-capemgr bone_capemgr.9: slot #1: No cape found
[0.651712] bone-capemgr bone_capemgr.9: slot #2: No cape found
[0.688822] bone-capemgr bone_capemgr.9: slot #3: No cape found
[0.707546] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' 
failed
[0.741892] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[0.753606] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status 
-22
[0.760896] pinctrl-single 44e10800.pinmux: could not request pin 21 on 
device pinctrl-single

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

[beagleboard] Re: Disable boot messages

[James S]

On Thursday, November 6, 2014 3:43:00 PM UTC, James S wrote:

 I have a Qt app which launches automatically but some boot messages appear 
 on screen before it starts up. How can I disable these boot messages?

 I've tried
 1. editing  /etc/systemd/system/getty.target.wants/getty@tty1.service and 
 commenting out ExecStart.
 2. removing lightdm
 3. checking /boot/uEnv.txt, it doesn't contain any console command ( 
 https://groups.google.com/forum/?fromgroups#!searchin/beagleboard/disable$20screen$20boot$20message|sort:date/beagleboard/765LGQ4a0bY/_wqpId-7C3IJ
  
 )

 Thanks,
 James


 uname -a
 Linux beaglebone 3.8.13-bone67 #1 SMP Wed Sep 24 21:30:03 UTC 2014 armv7l 
 GNU/Linux

 Messages include...
 [0.372552] omap2_mbox_probe: platform not supported
 [0.527489] tps65217-bl tps65217-bl: no platform data provided
 [0.614605] bone-capemgr bone_capemgr.9: slot #1: No cape found
 [0.651712] bone-capemgr bone_capemgr.9: slot #2: No cape found
 [0.688822] bone-capemgr bone_capemgr.9: slot #3: No cape found
 [0.707546] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' 
 failed
 [0.741892] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
 requested by 44e10800.pinmux; cannot claim for gpio-leds.8
 [0.753606] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status 
 -22
 [0.760896] pinctrl-single 44e10800.pinmux: could not request pin 21 on 
 device pinctrl-single


uEnv.txt command line
cmdline=quiet init=/lib/systemd/systemd 

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

[beagleboard] Re: beaglebone black kernel creation error

[purushotham . s . patil]

Hello siva,

I am facing the same problem. could u help me if issue got resolved for you.

make ARCH=arm CROSS_COMPILE=arm-linux-gnu- uImage-dtb.am335x-boneblack
gives me error saying No rule to make target

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

[beagleboard] Re: getting ECC failed error when booting up

[venkatprince . s]

Hi Devanand,

i also facing the same issue now...have you find any solution reg

kindly guide me to solve the issue.


Thanks  Regards
Venkatesh S
9843968630





On Saturday, October 1, 2011 9:56:21 PM UTC+5:30, Devanand wrote:

 Hello guys, 
 My BB loaded with angstrom suddenly started giving an error as below. 
 It is not booting anymore. Any idea what went wrong, plz help. 


 Texas Instruments X-Loader 1.5.1 (Jul 20 2011 - 09:50:57) 
 Beagle Rev C1/C2/C3 
 Reading boot sector 
 Loading u-boot.bin from nand 
 ECC Failed, page 0x0008 
 14 f0 9f e5 14 f0 9f e5 14 f0 9f e5 14 f0 9f e5 14 f0 9f e5 14 f0 9f 
 e5 14 f0 9f e5 14 f0 9f e5 40 82 0 80 40 82 0 80 0 83 0 80 0 83 0 80 
 c0 83 0 80 c0 83 0 


 Devanand T

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

[beagleboard] BBB Debian Corrupt LCD

[James S]

We have a built a custom board with an LCD interface to drive a 1024 x 768 
pixel LVDS panel, 16BPP. It works great on the Beaglebone White with the 
old Angstrom 3.2 using the board file configuration.

We want to use the Beaglebone Black so we built up a system from 
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-07-22 . I added a 
dts using the same parameters from the old board file but the graphics are 
blurred and corrupted. The card I made boots on the White also and gives 
the same results as on the Black. See images below.

I’ve fiddled with the panel timings but they don’t seem to have any effect.

Does anyone have any idea what is wrong and how do I fix it? 

Regards,

James

 

This is part of the (good) image from the frame buffer.

https://lh6.googleusercontent.com/-4paVjDS0NME/U9j9QP7ZvyI/GjY/Tq2jYoa6r0Y/s1600/screen1.jpg











This is a photo of the output on the screen, showing a similar area.

https://lh6.googleusercontent.com/-qR11mE7KhYU/U9j9wMohRZI/Gjg/_lhBqXIQQyk/s1600/screen2.jpg








 

The following is the panel section of the dts file, based on an LCD4 dts:-

 

 /* Settings for AUO G121XN01 / mita cape: */

 panel {

compatible = tilcdc,panel;

pinctrl-names = default;

pinctrl-0 = bone_mita_cape_lcd_pins;

panel-info {

   ac-bias   = 255;

   ac-bias-intrpt= 0;

   dma-burst-sz  = 16;

   bpp   = 16;

   fdd   = 0x80;

   tft-alt-mode  = 0;

   stn-565-mode  = 0;

   mono-8bit-mode= 0;

   sync-edge = 0;

   sync-ctrl = 1;

   raster-order  = 0;

   fifo-th   = 0;

   invert-pxl-clk= 0;

};

display-timings {

   native-mode = timing0;

   timing0: 1024x768 {

  hactive = 1024;

  vactive = 768;

  hback-porch = 80;

  hfront-porch= 48;

  hsync-len   = 32;

  vback-porch = 15;

  vfront-porch= 3;

  vsync-len   = 4;

  clock-frequency = 5600;

  hsync-active= 0;

  vsync-active= 0;

   };

};

 };

 

 fb {

compatible = ti,am33xx-tilcdc;

reg = 0x4830e000 0x1000;

interrupt-parent = intc;

interrupts = 36;

ti,hwmods = lcdc;

ti,power-gpio = gpio1 2 0x0;

ti,allow-non-reduced-blanking-modes;

 };

 

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

[beagleboard] Re: BBB Debian Corrupt LCD

[James S]

Hi Gerald, thanks for that reminder.

However, there should be no such loading on the White since it doesn't have 
HDMI on board? The problem also occurs on the White. What else could it be?

Regards,
James

On Wednesday, July 30, 2014 3:16:18 PM UTC+1, James S wrote:

 We have a built a custom board with an LCD interface to drive a 1024 x 768 
 pixel LVDS panel, 16BPP. It works great on the Beaglebone White with the 
 old Angstrom 3.2 using the board file configuration.

 We want to use the Beaglebone Black so we built up a system from 
 http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-07-22 . I added 
 a dts using the same parameters from the old board file but the graphics 
 are blurred and corrupted. The card I made boots on the White also and 
 gives the same results as on the Black. See images below.

 I’ve fiddled with the panel timings but they don’t seem to have any effect.

 Does anyone have any idea what is wrong and how do I fix it? 

 Regards,

 James

  

 This is part of the (good) image from the frame buffer.


 https://lh6.googleusercontent.com/-4paVjDS0NME/U9j9QP7ZvyI/GjY/Tq2jYoa6r0Y/s1600/screen1.jpg











 This is a photo of the output on the screen, showing a similar area.


 https://lh6.googleusercontent.com/-qR11mE7KhYU/U9j9wMohRZI/Gjg/_lhBqXIQQyk/s1600/screen2.jpg








  

 The following is the panel section of the dts file, based on an LCD4 dts:-

  

  /* Settings for AUO G121XN01 / mita cape: */

  panel {

 compatible = tilcdc,panel;

 pinctrl-names = default;

 pinctrl-0 = bone_mita_cape_lcd_pins;

 panel-info {

ac-bias   = 255;

ac-bias-intrpt= 0;

dma-burst-sz  = 16;

bpp   = 16;

fdd   = 0x80;

tft-alt-mode  = 0;

stn-565-mode  = 0;

mono-8bit-mode= 0;

sync-edge = 0;

sync-ctrl = 1;

raster-order  = 0;

fifo-th   = 0;

invert-pxl-clk= 0;

 };

 display-timings {

native-mode = timing0;

timing0: 1024x768 {

   hactive = 1024;

   vactive = 768;

   hback-porch = 80;

   hfront-porch= 48;

   hsync-len   = 32;

   vback-porch = 15;

   vfront-porch= 3;

   vsync-len   = 4;

   clock-frequency = 5600;

   hsync-active= 0;

   vsync-active= 0;

};

 };

  };

  

  fb {

 compatible = ti,am33xx-tilcdc;

 reg = 0x4830e000 0x1000;

 interrupt-parent = intc;

 interrupts = 36;

 ti,hwmods = lcdc;

 nbs
 ...

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

Re: [beagleboard] Re: BBB Debian Corrupt LCD

[James S]

Gerald,

The pins are connected directly to the LVDS chip, a DS90C383BMT. Trace 
lengths are short and matched. 
But on the same board with the older software, it worked fine - what would 
have changed to require the use of a buffer?

Regards,
James

On Wednesday, July 30, 2014 3:43:38 PM UTC+1, Gerald wrote:

 Still could be the same issue. What buffer are you using to drive the 
 signals to the LVDS device? Are the trace lengths match to insure that all 
 the setup and hold times are met by having all signals with the same delay?

 Gerald



 On Wed, Jul 30, 2014 at 9:40 AM, James S s19...@gmail.com javascript: 
 wrote:

 Hi Gerald, thanks for that reminder.

 However, there should be no such loading on the White since it doesn't 
 have HDMI on board? The problem also occurs on the White. What else could 
 it be?

 Regards,
 James


 On Wednesday, July 30, 2014 3:16:18 PM UTC+1, James S wrote:

 We have a built a custom board with an LCD interface to drive a 1024 x 
 768 pixel LVDS panel, 16BPP. It works great on the Beaglebone White with 
 the old Angstrom 3.2 using the board file configuration.

 We want to use the Beaglebone Black so we built up a system from 
 http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-07-22 . I 
 added a dts using the same parameters from the old board file but the 
 graphics are blurred and corrupted. The card I made boots on the White also 
 and gives the same results as on the Black. See images below.

 I’ve fiddled with the panel timings but they don’t seem to have any 
 effect.

 Does anyone have any idea what is wrong and how do I fix it? 

 Regards,

 James

  

 This is part of the (good) image from the frame buffer.


 https://lh6.googleusercontent.com/-4paVjDS0NME/U9j9QP7ZvyI/GjY/Tq2jYoa6r0Y/s1600/screen1.jpg











 This is a photo of the output on the screen, showing a similar area.


 https://lh6.googleusercontent.com/-qR11mE7KhYU/U9j9wMohRZI/Gjg/_lhBqXIQQyk/s1600/screen2.jpg








  

 The following is the panel section of the dts file, based on an LCD4 
 dts:-

  

  /* Settings for AUO G121XN01 / mita cape: */

  panel {

 compatible = tilcdc,panel;

 pinctrl-names = default;

 pinctrl-0 = bone_mita_cape_lcd_pins;

 panel-info {

ac-bias   = 255;

ac-bias-intrpt= 0;

dma-burst-sz  = 16;

bpp   = 16;

fdd   = 0x80;

tft-alt-mode  = 0;

stn-565-mode  = 0;

mono-8bit-mode= 0;

sync-edge = 0;

sync-ctrl = 1;

raster-order  = 0;

fifo-th   = 0;

invert-pxl-clk= 0;

 };

 display-timings {

native-mode = timing0;

timing0: 1024x768 {

   hactive = 1024;

   vactive = 768;

   hback-porch = 80;

   hfront-porch= 48;

   hsync-len   = 32;

   vback-porch = 15;

   vfront-porch= 3;

   vsync-len   = 4;

   clock-frequency = 5600;

   hsync-active= 0;

   vsync-active= 0;

};

 };

  };

  

  fb {

 compatible = ti,am33xx-tilcdc;

 reg = 0x4830e000 0x1000;

 interrupt-parent = intc;

 interrupts = 36;

 ti,hwmods = lcdc;

 nbs
 ...

  -- 
 For more options, visit http://beagleboard.org/discuss
 --- 
 You received this message because you are subscribed to the Google Groups 
 BeagleBoard group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to beagleboard...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.




-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you

[beagleboard] GPIO input not working

[Sean S]

I have a BBB (running Ubuntu) connected to a custom cape which uses some 
GPIO pins for input and output. The output pins work as expected without 
any extra configuration, I'm just exporting the required pins in the 
/sys/class/gpio folder, setting the direction, and writing values. 

One of the GPIOs (specifically GPIO1_15) is connected to a button, which 
when pushed I want to shut down the BBB. I export the pin the same way I do 
the outputs, set the direction, and try reading the value. The value is 
always read as 0, regardless of whether the button is pressed or not. Is 
there any extra configuration needed for using GPIO inputs?

Looking at the pinmux for this pin in 
/sys/kernel/debug/pinctrl/44e10800.pinmux I get:

pin 15 (44e1083c) 0027 pinctrl-single

which I take to mean that this pin is already configured for GPIO. I did a 
device tree overlay for that pin only for testing purposes, setting it to 
0x07. The pinmux changed, but it still behaved the same way. The tree 
overlay I tried:

/dts-v1/;
/plugin/;

/ {
compatible = ti,beaglebone, ti,beaglebone-black;

/* identification */
part-number = bb-gpio;
version = 00A0;

exclusive-use =
/* the pin header uses */
P8.15,/* GPIO1_15 */
/* the hardware ip uses */
GPIO1_15;

fragment@0 {
target = am33xx_pinmux;
__overlay__ {
bb_GPIO1_15_pins: pinmux_bb_GPIO1_15_pins {
pinctrl-single,pins = 
0x03c 0x07
;
};
};
};
fragment@1 {
target = ocp;
__overlay__ {
/* avoid stupid warning */
#address-cells = 1;
#size-cells = 1;

gpio1_15_test {
compatible = bone-pinmux-helper;
pinctrl-names = default;
pinctrl-0 = bb_GPIO1_15_pins;
status = okay;
};
};
};
};




We tested the cape without a BBB attached and the button sent a signal when 
pushed as expected. Any ideas on what is going wrong?

Thanks

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Robot control architecture/IPC

[Bob S]

Hi,

I chose Newbie skill level because I'm new to BeagleBoard and to Linux, but 
I am not new to programming.

I have BeagleBoard Black running the Debian distro it shipped with and have 
set up a cross-compiler on Windows 7 using Eclipse and the Linaro 
toolchain.  This all works well, including remote debugging.

I am designing a multilayered robot control system.  The idea is that lower 
layers are responsible for low-level tasks, e.g. basic motor control, while 
higher layers will do more complicated stuff.

Anyway, my idea is to run each layer either on a separate thread, or as a 
separate process altogether.  The various layers would communicate with 
each other using a publish/subscribe messaging system.

I have done some research and at this point am leaning toward running each 
layer in a separate process and using uMundo (
https://github.com/tklab-tud/umundo) to implement the messaging system.

The question I have is whether anybody has ever run uMundo on BeagleBoard 
Black/Debian, and if so what to look out for.

Beyond that, I am also willing to discuss the basic idea with any 
interested parties.  I'm not convinced my current plan is the best way of 
going about it.

Thanks,
Bob


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

[beagleboard] Re: Booting adeneo wince 7 on beaglebone black

[s . kumawat1990]

now you got it or notsame problem i have what should i do 
plz help me..??
 

On Tuesday, October 8, 2013 12:38:22 PM UTC+5:30, Ali Asadzadeh wrote:

 Dear all
 I have loaded a 4GB SD card with the MLO and EBOOTSD.nb0 and NK.bin that 
 comes with the AM335X_BeagleBoneBlack_WEC7_BIN_V0131 package from 
 Adeno,Also I have formatted the card with Fat32 and 4096 byte sectors 
 (using windows foarmt), and I have used the TI SD card utility for flashing 
 the SD card, Also I have pushed the user button before power up,
 But nothing happens!!! 
 when I power the board up the leds won't flash, and there is no activity 
 on the Serial header, So I think it's a boot problem, How can I be sure 
 that the MLO is in the first sector of the SD card? I have loaded android, 
 angstrom and ubuntu successfully on to beaglebone balck, I want to test 
 what windows ce have to offer, So if somebody have booted successfully 
 please help me too.


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

[beagleboard] Re: SD Card as Extra Storage

[James S]

Does 
http://dotnetdavid.wordpress.com/2013/09/28/beaglebone-black-get-more-space-from-your-sd-card/help?


On Friday, May 16, 2014 5:19:08 AM UTC+1, David Song wrote:

 Hello, I am trying to use a 32GB SD card to expand my beaglebones space. 
 But, I am having trouble creating the partitions and expanding the 
 filesystem. I used Gparted to create Ex3(I think) partition and put it into 
 the BeagleBone. df lists it as being mounted on the /media folder with the 
 right amount of space, but it's not being put onto the rootfs partitions 
 space. So then it won't work as space on the system? 

 Thank you for reading and please help out by replying with a solution :)


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