Re: [beagleboard] Connecting/configuring ublox M8n GPS to Mission Planner Passthrough with BBBlu

[Timothy Litvin]

Aaand. Done. I have GPS and blue-arduplane. Thanks Robert and Jason. 
Now you'll be able to say you "knew me when..."
Cheers to you both. 



On Thursday, July 6, 2017 at 3:36:27 PM UTC-7, Jason Kridner wrote:
>
> Indeed, TX on the GPS (the one spitting out data) should be RX on the 
> UART. 
>
> On Jul 6, 2017, at 6:27 PM, Timothy Litvin  > wrote:
>
> I've wondered that too, but haven't yet switched them; I wanted to first 
> confirm that the software really should be that simple. 
> I'm probing the GPS signal at the uBlox board itself, definitely the wire 
> silkscreened "Tx": I'm getting a signal there. Not likely my spliced 
> connector leads are shorted: they're soldered and wrapped. On the BBBlue, 
> that wire is connected to the 4th pin from the silkscreened dot (which I 
> assume is the Pin1 connector end, furthest from the USB end of the board) 
> corresponding to UART2_Tx on the GPS connector in the schematic.  The fact 
> that the uBlox is powered-up suggests my assumptions about the pin 
> numbering are correct. I had dismissed the thought that these might need to 
> be wired Tx/Rx cross-over, but suddenly I'm less sure of that.
>
>
> On Thursday, July 6, 2017 at 2:46:12 PM UTC-7, RobertCNelson wrote:
>>
>> On Thu, Jul 6, 2017 at 3:18 PM, Timothy Litvin  
>> wrote: 
>> > In my previous post I re-flashed the BBBlue because, after some amount 
>> of 
>> > poking around troubleshooting, on reboot somehow I had disabled all my 
>> > comms.  So: clean slate. Reflash. I setup WIFI and, with an updated 
>> Debian 
>> > image, installed the most recent recipe for blue-arduplane, (the latest 
>> > build that pre-assigns the BBBlue GPS socket’s pins P9.21 and P9.22 as 
>> > UART): 
>> > 
>> > sudo apt update && sudo apt upgrade –y 
>> > 
>> > sudo apt install -y bb-cape-overlays cpufrequtils ardupilot-plane-blue 
>> > 
>> > sudo sed -i 's/GOVERNOR="ondemand"/GOVERNOR="performance"/g' 
>> > /etc/init.d/cpufrequtils 
>> > 
>> > cd /opt/scripts && sudo git pull 
>> > 
>> > sudo /opt/scripts/tools/update_kernel.sh --ti-rt-channel --lts-4_4 
>> > 
>> > sudo reboot 
>> > 
>> > 
>> > 
>> > I use tio to query the pins (on ttyS2) and confirmed they’re UART.  The 
>> blue 
>> > LED on the uBlox is blinking to indicate satellite lock. When I attempt 
>> to 
>> > connect to my uBlox M8n GPS, (blindly using 4800, 9600, 19200, 38400 
>> baud on 
>> > that port) I still get no GPS data stream.  So I checked the GPS output 
>> on 
>> > the o’scope and get 9600 baud pulses on the GPS’ Tx pin (and nothing on 
>> the 
>> > Rx pin). I try config-pin query again with: 
>> > 
>> > tio -b 9600 /dev/ttyS2 
>> > 
>> > …and Jason’s one-liner tests 
>> > 
>> > stty -F /dev/ttyO2 ispeed 9600 ospeed 9600;tail -f /dev/ttyO2 
>> > 
>> > …with no response from the GPS. 
>> > 
>> > Did I miss something? 
>>
>> Is there any chance the tx/rx is reversed on the ublox module? 
>>
>> 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/19f0fc31-2846-40d9-8d37-04763377aa12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Connecting/configuring ublox M8n GPS to Mission Planner Passthrough with BBBlu

[Jason Kridner]

Indeed, TX on the GPS (the one spitting out data) should be RX on the UART. 

> On Jul 6, 2017, at 6:27 PM, Timothy Litvin  wrote:
> 
> I've wondered that too, but haven't yet switched them; I wanted to first 
> confirm that the software really should be that simple. 
> I'm probing the GPS signal at the uBlox board itself, definitely the wire 
> silkscreened "Tx": I'm getting a signal there. Not likely my spliced 
> connector leads are shorted: they're soldered and wrapped. On the BBBlue, 
> that wire is connected to the 4th pin from the silkscreened dot (which I 
> assume is the Pin1 connector end, furthest from the USB end of the board) 
> corresponding to UART2_Tx on the GPS connector in the schematic.  The fact 
> that the uBlox is powered-up suggests my assumptions about the pin numbering 
> are correct. I had dismissed the thought that these might need to be wired 
> Tx/Rx cross-over, but suddenly I'm less sure of that.
> 
> 
>> On Thursday, July 6, 2017 at 2:46:12 PM UTC-7, RobertCNelson wrote:
>> On Thu, Jul 6, 2017 at 3:18 PM, Timothy Litvin  wrote: 
>> > In my previous post I re-flashed the BBBlue because, after some amount of 
>> > poking around troubleshooting, on reboot somehow I had disabled all my 
>> > comms.  So: clean slate. Reflash. I setup WIFI and, with an updated Debian 
>> > image, installed the most recent recipe for blue-arduplane, (the latest 
>> > build that pre-assigns the BBBlue GPS socket’s pins P9.21 and P9.22 as 
>> > UART): 
>> > 
>> > sudo apt update && sudo apt upgrade –y 
>> > 
>> > sudo apt install -y bb-cape-overlays cpufrequtils ardupilot-plane-blue 
>> > 
>> > sudo sed -i 's/GOVERNOR="ondemand"/GOVERNOR="performance"/g' 
>> > /etc/init.d/cpufrequtils 
>> > 
>> > cd /opt/scripts && sudo git pull 
>> > 
>> > sudo /opt/scripts/tools/update_kernel.sh --ti-rt-channel --lts-4_4 
>> > 
>> > sudo reboot 
>> > 
>> > 
>> > 
>> > I use tio to query the pins (on ttyS2) and confirmed they’re UART.  The 
>> > blue 
>> > LED on the uBlox is blinking to indicate satellite lock. When I attempt to 
>> > connect to my uBlox M8n GPS, (blindly using 4800, 9600, 19200, 38400 baud 
>> > on 
>> > that port) I still get no GPS data stream.  So I checked the GPS output on 
>> > the o’scope and get 9600 baud pulses on the GPS’ Tx pin (and nothing on 
>> > the 
>> > Rx pin). I try config-pin query again with: 
>> > 
>> > tio -b 9600 /dev/ttyS2 
>> > 
>> > …and Jason’s one-liner tests 
>> > 
>> > stty -F /dev/ttyO2 ispeed 9600 ospeed 9600;tail -f /dev/ttyO2 
>> > 
>> > …with no response from the GPS. 
>> > 
>> > Did I miss something? 
>> 
>> Is there any chance the tx/rx is reversed on the ublox module? 
>> 
>> 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/A449B8EF-A96E-41E3-802B-14A6CBBDBBCD%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Connecting/configuring ublox M8n GPS to Mission Planner Passthrough with BBBlu

[Timothy Litvin]

I've wondered that too, but haven't yet switched them; I wanted to first 
confirm that the software really should be that simple. 
I'm probing the GPS signal at the uBlox board itself, definitely the wire 
silkscreened "Tx": I'm getting a signal there. Not likely my spliced 
connector leads are shorted: they're soldered and wrapped. On the BBBlue, 
that wire is connected to the 4th pin from the silkscreened dot (which I 
assume is the Pin1 connector end, furthest from the USB end of the board) 
corresponding to UART2_Tx on the GPS connector in the schematic.  The fact 
that the uBlox is powered-up suggests my assumptions about the pin 
numbering are correct. I had dismissed the thought that these might need to 
be wired Tx/Rx cross-over, but suddenly I'm less sure of that.


On Thursday, July 6, 2017 at 2:46:12 PM UTC-7, RobertCNelson wrote:
>
> On Thu, Jul 6, 2017 at 3:18 PM, Timothy Litvin  > wrote: 
> > In my previous post I re-flashed the BBBlue because, after some amount 
> of 
> > poking around troubleshooting, on reboot somehow I had disabled all my 
> > comms.  So: clean slate. Reflash. I setup WIFI and, with an updated 
> Debian 
> > image, installed the most recent recipe for blue-arduplane, (the latest 
> > build that pre-assigns the BBBlue GPS socket’s pins P9.21 and P9.22 as 
> > UART): 
> > 
> > sudo apt update && sudo apt upgrade –y 
> > 
> > sudo apt install -y bb-cape-overlays cpufrequtils ardupilot-plane-blue 
> > 
> > sudo sed -i 's/GOVERNOR="ondemand"/GOVERNOR="performance"/g' 
> > /etc/init.d/cpufrequtils 
> > 
> > cd /opt/scripts && sudo git pull 
> > 
> > sudo /opt/scripts/tools/update_kernel.sh --ti-rt-channel --lts-4_4 
> > 
> > sudo reboot 
> > 
> > 
> > 
> > I use tio to query the pins (on ttyS2) and confirmed they’re UART.  The 
> blue 
> > LED on the uBlox is blinking to indicate satellite lock. When I attempt 
> to 
> > connect to my uBlox M8n GPS, (blindly using 4800, 9600, 19200, 38400 
> baud on 
> > that port) I still get no GPS data stream.  So I checked the GPS output 
> on 
> > the o’scope and get 9600 baud pulses on the GPS’ Tx pin (and nothing on 
> the 
> > Rx pin). I try config-pin query again with: 
> > 
> > tio -b 9600 /dev/ttyS2 
> > 
> > …and Jason’s one-liner tests 
> > 
> > stty -F /dev/ttyO2 ispeed 9600 ospeed 9600;tail -f /dev/ttyO2 
> > 
> > …with no response from the GPS. 
> > 
> > Did I miss something? 
>
> Is there any chance the tx/rx is reversed on the ublox module? 
>
> 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/4360dde0-5690-45fd-8806-1ec7e03fb6f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Connecting/configuring ublox M8n GPS to Mission Planner Passthrough with BBBlu

[Robert Nelson]

On Thu, Jul 6, 2017 at 3:18 PM, Timothy Litvin  wrote:
> In my previous post I re-flashed the BBBlue because, after some amount of
> poking around troubleshooting, on reboot somehow I had disabled all my
> comms.  So: clean slate. Reflash. I setup WIFI and, with an updated Debian
> image, installed the most recent recipe for blue-arduplane, (the latest
> build that pre-assigns the BBBlue GPS socket’s pins P9.21 and P9.22 as
> UART):
>
> sudo apt update && sudo apt upgrade –y
>
> sudo apt install -y bb-cape-overlays cpufrequtils ardupilot-plane-blue
>
> sudo sed -i 's/GOVERNOR="ondemand"/GOVERNOR="performance"/g'
> /etc/init.d/cpufrequtils
>
> cd /opt/scripts && sudo git pull
>
> sudo /opt/scripts/tools/update_kernel.sh --ti-rt-channel --lts-4_4
>
> sudo reboot
>
>
>
> I use tio to query the pins (on ttyS2) and confirmed they’re UART.  The blue
> LED on the uBlox is blinking to indicate satellite lock. When I attempt to
> connect to my uBlox M8n GPS, (blindly using 4800, 9600, 19200, 38400 baud on
> that port) I still get no GPS data stream.  So I checked the GPS output on
> the o’scope and get 9600 baud pulses on the GPS’ Tx pin (and nothing on the
> Rx pin). I try config-pin query again with:
>
> tio -b 9600 /dev/ttyS2
>
> …and Jason’s one-liner tests
>
> stty -F /dev/ttyO2 ispeed 9600 ospeed 9600;tail -f /dev/ttyO2
>
> …with no response from the GPS.
>
> Did I miss something?

Is there any chance the tx/rx is reversed on the ublox module?

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/CAOCHtYjCVn6j9nOo0vZRk3%2BEA%3DQg_y%2BnnRG02u2kocHwmTSMzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBGW crash

[Sebastián Sáez]

thanks Greg,

this proyect has great documentation :)

On Wed, Jul 5, 2017 at 7:24 AM, Greg  wrote:

> I found nodejs to be amazing!  My opinion:  go with the latest and
> greatest Nodejs v8.0 and try Javascript ES6 + HTML5 + WebSockets.
> Javascript is now a reasonable language and a lot of the weirdness of
> working with it is gone.
> I had good luck with this project:
>
> https://www.hackster.io/Greg-R/beaglebone-green-wireless-
> irrigation-control-ce7c4b
>
> Once I got the BBGW configured to a simple station, it performed perfectly.
> If you have a wireless router in your home system, the AP stuff is only
> going to confuse.  Deactivate it.
>
> On Tuesday, July 4, 2017 at 1:10:10 PM UTC-4, Sebastián Sáez wrote:
>>
>> yes, I think the same.
>>
>> I'm going to explore the nodejs world.
>>
>> thanks you
>>
>


-- 
Sebastián

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CA%2B-J9cYA-VZ_smYPFNZODVv%3DcoULaizF1QK6Lfq7zEK3xHELWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Soft AP

[Robert Nelson]

On Thu, Jul 6, 2017 at 3:28 PM, Alan Marshall  wrote:
> How do you turn off the Soft AP?

in : /etc/default/bb-wl18xx

set:

TETHER_ENABLED=yes -> TETHER_ENABLED=no

full list of options:

https://github.com/rcn-ee/repos/blob/master/bb-wl18xx-firmware/suite/jessie/debian/postinst#L19

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

[beagleboard] Re: BBGW | USB hub does not work

[Sebastián Sáez]

Thanks Greg, I got another beaglebone green wireless and it worked.

Test webcam and flahs drive

Apparently the one that was using has some problem

Thank you

On Wednesday, July 5, 2017 at 7:07:54 AM UTC-4, Greg wrote:
>
> That's easy.  Here is before and after plugging in USB flash stick:
>
> debian@beaglebone:~$ lsusb
> Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> debian@beaglebone:~$ lsusb
> Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
> Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> debian@beaglebone:~$ 
>
> So it does detect the USB device.
> However, I didn't find the drive mounted in the usual places like /mnt or 
> /media.
> So that has to be done manually with the mount command?  Or maybe I wasn't 
> looking in the correct folder.
>
> Here is snippet of dmesg:
>
> [651120.233538] usb 1-1.3: new high-speed USB device number 3 using 
> musb-hdrc
> [651120.475757] usb 1-1.3: New USB device found, idVendor=058f, 
> idProduct=6387
> [651120.475820] usb 1-1.3: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [651120.475854] usb 1-1.3: Product: Mass Storage
> [651120.475883] usb 1-1.3: Manufacturer: Generic
> [651120.475911] usb 1-1.3: SerialNumber: D339585D
> [651120.492014] usb-storage 1-1.3:1.0: USB Mass Storage device detected
> [651120.505619] scsi host0: usb-storage 1-1.3:1.0
> [651120.637632] usbcore: registered new interface driver uas
> [651121.509778] scsi 0:0:0:0: Direct-Access CENTON   
>  8.07 PQ: 0 ANSI: 2
> [651121.527501] sd 0:0:0:0: [sda] 15667200 512-byte logical blocks: (8.02 
> GB/7.47 GiB)
> [651121.528032] sd 0:0:0:0: [sda] Write Protect is off
> [651121.528080] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
> [651121.528546] sd 0:0:0:0: [sda] No Caching mode page found
> [651121.534237] sd 0:0:0:0: [sda] Assuming drive cache: write through
> [651121.701820] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [651123.541720]  sda: sda1
> [651123.555958] sd 0:0:0:0: [sda] Attached SCSI removable disk
>
> Looks good to me, but this is the first time I ever plugged a USB disk 
> into a Beaglebone!
>
> Regards,
> Greg
>

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

[beagleboard] Soft AP

[Alan Marshall]

How do you turn off the Soft AP?

-- 
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/de4ac191-c581-4416-81b5-b122ea92dd94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Connecting/configuring ublox M8n GPS to Mission Planner Passthrough with BBBlu

[Timothy Litvin]

In my previous post I re-flashed the BBBlue because, after some amount of 
poking around troubleshooting, on reboot somehow I had disabled all my 
comms.  So: clean slate. Reflash. I setup WIFI and, with an updated Debian 
image, installed the most recent recipe for blue-arduplane, (the latest 
build that pre-assigns the BBBlue GPS socket’s pins P9.21 and P9.22 as 
UART):

sudo apt update && sudo apt upgrade –y

sudo apt install -y bb-cape-overlays cpufrequtils ardupilot-plane-blue 

sudo sed -i 's/GOVERNOR="ondemand"/GOVERNOR="performance"/g' 
/etc/init.d/cpufrequtils

cd /opt/scripts && sudo git pull

sudo /opt/scripts/tools/update_kernel.sh --ti-rt-channel --lts-4_4

sudo reboot

 

I use *tio* to query the pins (on ttyS2) and confirmed they’re UART.  The 
blue LED on the uBlox is blinking to indicate satellite lock. When I 
attempt to connect to my uBlox M8n GPS, (blindly using 4800, 9600, 19200, 
38400 baud on that port) I still get no GPS data stream.  So I checked the 
GPS output on the o’scope and get 9600 baud pulses on the GPS’ Tx pin (and 
nothing on the Rx pin). I try config-pin query again with: 

tio -b 9600 /dev/ttyS2

…and Jason’s one-liner tests 

stty -F /dev/ttyO2 ispeed 9600 ospeed 9600;tail -f /dev/ttyO2

…with no response from the GPS. 

Did I miss something? 

On Sunday, July 2, 2017 at 1:45:17 PM UTC-7, Timothy Litvin wrote:
>
> So I’ve re-flashed the Blue, upgraded, updated and reinstalled 
> blue-arduplane (without the original uEnv.txt dtb substitution), and 
> connected WIFI via connmanctl. The board is working again, with comms back. 
> GPS blue LED is blinking (meaning that it has a GPS lock). I can again run 
> blue-arduplane and receive telemetry via WIFI to my laptop but no GPS. I 
> then ran… 
>
> config-pin –q 
>
> …on P9.21 and P9.22 and confirmed that those pins are now, in fact, 
> pre-assigned as UART.  Progress. Thank you for that simplification. 
>
> At this point I understand (please correct me if I’m wrong) that no 
> further action is required to use the UART connector silkscreened “GPS” on 
> the BBBlue, except for configuring the connection for my specific GPS’ COM 
> parameters. My uBlox neo-M8n, purchased from Hobby King, states “This 
> module ships with a baud rate of 38400, 10Hz 
> ”.
>  
>  I have not yet setup u-center to modify the GPS' firmware, so I’ll include 
> the stated default baud in my testing, as well as the more common 4800 and 
> 9600 baud and, while I'm at it, 19200.
>
> I then install the TTY terminal application tio… 
>
> sudo apt install tio
>
>  
>
> Running tio to set the connection baud of a specific port, I get back…
>
> debian@beaglebone:~$ tio -b 9600 /dev/ttyS1 
> [tio 18:52:00] tio v1.20 
> [tio 18:52:00] Press ctrl-t q to quit 
> [tio 18:52:00] Connected
>
> …no matter the baud (4800, 9600, 19200 or 38400) or the port (ttyS1, 
> ttyS2).  None of those alternatives yet yields GPS data; it just hangs at 
> “Connected” until I… 
>
> ctrl-t q
>
> Then, running Jason’s One-Liner GPS test… 
>
> stty -F /dev/ttyO2 ispeed 4800 ospeed 4800;tail -f /dev/ttyO2
>
> # also then with /dev/ttyS1 and /dev/ttyS2
>
> …with the same baud and port parameter variations above also just hangs at 
> the command line, until I ctrl-C. My guess is that this means the software 
> tools are working, telling me that this monkey is still missing something 
> important.   
>
>
>
> On Saturday, July 1, 2017 at 7:43:03 AM UTC-7, RobertCNelson wrote:
>>
>> On Sat, Jul 1, 2017 at 1:34 AM, Timothy Litvin  
>> wrote: 
>> > First, I'm genuinely appreciative of the time and attention you guys 
>> are 
>> > putting into this. I was actually worried that I've overextended my 
>> pleading 
>> > quota. That said, after running 
>> > 
>> > sudo apt update 
>> > sudo apt upgrade 
>> > sudo apt install tio 
>> > 
>> > It seems I'm still across town from Easy Street, without functioning 
>> pinmux 
>> > file: 
>> > 
>> > debian@beaglebone:~$ config-pin P9.21 uart 
>> > P9_21 pinmux file not found! 
>> > Please verify your device tree file 
>>
>> it shouldn't be doing that.. 
>>
>> try with the full path: 
>>
>> /usr/bin/config-pin P9.21 uart 
>>
>> ps, if you do: 
>>
>> cd /opt/scripts/ 
>> git pull 
>>
>> and then reboot and run: 
>>
>> journalctl | grep am335x_evm 
>>
>> it should auto-set it as a uart. 
>>
>> 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/2cf4e9bb-4206-4330-ae18-2ece99741132%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: New Beaglebone with Storage Almost Full

[Robert Nelson]

On Thu, Jul 6, 2017 at 2:25 PM, Mark Vinson  wrote:
> The Beaglebones in question were distributed by Mouser (their part #
> 958-BBB01-SC-505), and show "beagleboard.org/BeagleBone Black Rev C -
> manufactured by GHI Electronics" on each box.
>
> uname -a returns:
>
> Linux beaglebone 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l
> GNU/Linux


You just have an older version, feel free to flash the lastest
monthy/weekly snapshots of Jessie/Stretch:

console/iot/lxqt images available:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

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/CAOCHtYjuOB9PBAiUqACYN009_Bq1q1MNa3-yZ5jfPr5Da-N-yQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: New Beaglebone with Storage Almost Full

[Mark Vinson]

The Beaglebones in question were distributed by Mouser (their part # 
958-BBB01-SC-505), and show "beagleboard.org/BeagleBone Black Rev C - 
manufactured by GHI Electronics" on each box.

uname -a returns:

Linux beaglebone 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l 
GNU/Linux


On Thursday, July 6, 2017 at 3:02:54 PM UTC-4, Mark Vinson wrote:
>
> Greg - Thanks for the feedback. From my new Beaglebone Blacks:
>
> *Debian release: (uname –r):* 4.4.9-ti-r25
>
>
> *df –h:*
>
> Filesystem  Size  Used Avail Use% Mounted on
>
> udev 10M 0   10M   0% /dev
>
> tmpfs99M  8.4M   91M   9% /run
>
> /dev/mmcblk0p1  3.5G  3.2G   57M  99% /
>
> tmpfs   247M  4.0K  247M   1% /dev/shm
>
> tmpfs   5.0M  4.0K  5.0M   1% /run/lock
>
> tmpfs   247M 0  247M   0% /sys/fs/cgroup
>
> tmpfs50M 0   50M   0% /run/user/1000
>
> Apparently something in my "/" mount is taking up most of the storage. 
> This is an out of the box unit - as received. My next step will be to start 
> comparing all the stuff under "/" to my Debian 7 units to see what's 
> different. I don't know enough about Debian to spot the obvious otherwise.
>
> But it seems like a flaw to receive 11 new units, all with almost no 
> available storage.
>
> Thanks for your help. Any other ideas before I start ignorantly searching?
>
> Thanks,
>
> Mark Vinson
>
> On Wednesday, July 5, 2017 at 5:57:31 PM UTC-4, Greg wrote:
>>
>> Wow, that's weird.  Are you able to get to a terminal and run this 
>> command?
>>
>> df -h
>>
>> Here is what my BBGW shows:
>>
>> Filesystem  Size  Used Avail Use% Mounted on
>> udev 10M 0   10M   0% /dev
>> tmpfs98M  2.8M   95M   3% /run
>> /dev/mmcblk1p1  3.6G  1.7G  1.7G  50% /
>> tmpfs   245M 0  245M   0% /dev/shm
>> tmpfs   5.0M 0  5.0M   0% /run/lock
>> tmpfs   245M 0  245M   0% /sys/fs/cgroup
>>
>> This is a Debian 8 IOT images, and about half of the storage is used. 
>>  Plenty for more stuff!
>>
>> The only thing I can think of is to run the partition expander script:
>>
>> sudo /opt/scripts/tools/grow_partition.sh
>>
>> Check before and after running above script.  I hope it helps, but no 
>> promises.
>>
>> Regards,
>> Greg
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/3778a70f-215d-4c65-bbd1-5fba59f85b8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: New Beaglebone with Storage Almost Full

[Mark Vinson]

Greg - Thanks for the feedback. From my new Beaglebone Blacks:

*Debian release: (uname –r):* 4.4.9-ti-r25


*df –h:*

Filesystem  Size  Used Avail Use% Mounted on

udev 10M 0   10M   0% /dev

tmpfs99M  8.4M   91M   9% /run

/dev/mmcblk0p1  3.5G  3.2G   57M  99% /

tmpfs   247M  4.0K  247M   1% /dev/shm

tmpfs   5.0M  4.0K  5.0M   1% /run/lock

tmpfs   247M 0  247M   0% /sys/fs/cgroup

tmpfs50M 0   50M   0% /run/user/1000

Apparently something in my "/" mount is taking up most of the storage. This 
is an out of the box unit - as received. My next step will be to start 
comparing all the stuff under "/" to my Debian 7 units to see what's 
different. I don't know enough about Debian to spot the obvious otherwise.

But it seems like a flaw to receive 11 new units, all with almost no 
available storage.

Thanks for your help. Any other ideas before I start ignorantly searching?

Thanks,

Mark Vinson

On Wednesday, July 5, 2017 at 5:57:31 PM UTC-4, Greg wrote:
>
> Wow, that's weird.  Are you able to get to a terminal and run this command?
>
> df -h
>
> Here is what my BBGW shows:
>
> Filesystem  Size  Used Avail Use% Mounted on
> udev 10M 0   10M   0% /dev
> tmpfs98M  2.8M   95M   3% /run
> /dev/mmcblk1p1  3.6G  1.7G  1.7G  50% /
> tmpfs   245M 0  245M   0% /dev/shm
> tmpfs   5.0M 0  5.0M   0% /run/lock
> tmpfs   245M 0  245M   0% /sys/fs/cgroup
>
> This is a Debian 8 IOT images, and about half of the storage is used. 
>  Plenty for more stuff!
>
> The only thing I can think of is to run the partition expander script:
>
> sudo /opt/scripts/tools/grow_partition.sh
>
> Check before and after running above script.  I hope it helps, but no 
> promises.
>
> Regards,
> Greg
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/c8a11210-6f2e-4db8-8c6c-e9045ee0a293%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: uEnv.txt parsing

[Kenny Koller]

>
> (The purpose of the mmcblk1boot* devices is unknown at present.)
>

Four years later I happened across this post and found it helpful.

I believe these devices map to the hidden boot sectors within the eMMC 
which hangs off the MMC1 peripheral. 

-- 
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/4353a1e6-4ca3-4246-848c-d02eacdc0c48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Porting from BeagleBone Black (BBB) to BeagleBone Green Wireless (BBGW)

[marteleus]

Hi there,

Sorry, that I can't answer the question. I am curious on the same thing 
with you. Did you get an answer to this question?

Best Regards,
Deemarc B.

เมื่อ วันเสาร์ที่ 25 กุมภาพันธ์ ค.ศ. 2017 3 นาฬิกา 55 นาที 53 วินาที UTC+7, 
agm...@gmail.com เขียนว่า:
>
> Hello All,
>
> I've been working with BBB on a project which uses Xenomai (2.6.4 and 3), 
> PRU and bunch of serial devices (UART, I2C and SPI). I want to move my 
> application to BBGW (for WiFi and Bluetooth). 
>
> I know there are images for BBGW (i'm still unclear which image to use), 
> but can someone confirm if they have used Xenomai and PRUs with BBGW and if 
> they had any difficulty. 
>
> I'd really appreciate any advice on which image/kernel version to use. 
>
> 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/dc15e90f-0f84-46da-9a51-cd9cc50e121b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Using Bluetooth Connection on Beaglebone Bkue

[Brandon Sights]

I'm interested in using Bluetooth to communicate from an Android device to the 
Beaglebone Blue. Has anyone done this?

Sincerely, 
Brandon Sights 

-- 
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/52427e2f-a65b-4380-9cb5-830b80383311%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] CAN Bus on Beaglebone Blue

[Brandon Sights]

Does anyone have an example, or tips, on reading/writing to the CAN port on the 
Beaglebone Blue?

Thank you, 
Brandon Sights 

-- 
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/14f710ba-2ffe-42a2-af9e-72aea7d53671%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] CAN Bus on BBB

[Brandon Sights]

Are there any examples for using the CAN bus on BBB? Any tips that can be 
provided for using the CAN bus?

Thank you,
Brandon Sights

-- 
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/96d28eb3-449c-4569-a781-508ed8fe6cff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: connmanctl

[gokhanaykan]

Hi,

I cannot enable wifi using *connmanctl.*

*connmanctl** can ot recognize wlan, *only shows ethernet when technologies 
is asked.
May I ask you which image are you using ?

Gokhan 


On Saturday, April 8, 2017 at 7:02:44 AM UTC+3, Mala Dies wrote:
>
> Hey Yo,
>
> *connmanctl *is used as the initial command from 
> https://01.org/connman/documentation.
>
> Then, you have to type in, while under the command connmanctl, *wifi 
> enable*. While still under the connmanctl command, type in *wifi scan* 
> and then type *services*. It will show your *wifi_blah, blah, blah, blah, 
> blah_blah, blah, blah_managed_psk *Wifi address to type in once you type 
> *agent 
> on* and then *connect*. So you would type this under connmanctl:
>
> wifi enable
>
> wifi scan
>
> services
>
> agent on
>
> connect wifi___managed_psk
>
> then...
>
> You will be asked for a password. Enter the password you have for your 
> router.
>
> Done! I was taught this earlier today.
>
> Seth
>
> P.S. Enjoy!
>
> On Friday, April 7, 2017 at 8:18:00 PM UTC-5, Mala Dies wrote:
>>
>> Hello,
>>
>> I am using connmanctl to "try" to get into a valid configuration for WiFi 
>> for a BBBW. I am not successful yet. Does anyone have any pointers?
>>
>> Seth
>>
>

-- 
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/b1371359-5b92-486f-b533-70590c0495fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] config-pin conflict on hdmi, hdmi is disabled

[terra ÜÝÜ]

Dear Robert,

Thank You, for anyone looking here is my complete /boot/uEnv.txt, changed 
in bold

#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

uname_r=4.4.54-ti-r93
#uuid=
#dtb=

##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..)

##BeagleBone Black: HDMI (Audio/Video) disabled:
#dtb=am335x-boneblack-emmc-overlay.dtb

##BeagleBone Black: eMMC disabled:
#dtb=am335x-boneblack-hdmi-overlay.dtb

##BeagleBone Black: HDMI Audio/eMMC disabled:
#dtb=am335x-boneblack-nhdmi-overlay.dtb

##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled:
#dtb=am335x-boneblack-overlay.dtb

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

##BeagleBone Green: eMMC disabled
#dtb=am335x-bonegreen-overlay.dtb

###U-Boot Overlays###
###Documentation: 
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
###Master Enable
*enable_uboot_overlays=1*
###Overide capes with eeprom
#uboot_overlay_addr0=/lib/firmware/.dtbo
#uboot_overlay_addr1=/lib/firmware/.dtbo
#uboot_overlay_addr2=/lib/firmware/.dtbo
#uboot_overlay_addr3=/lib/firmware/.dtbo
###Custom Cape
#dtb_overlay=/lib/firmware/.dtbo
###Disable auto loading of virtual capes (emmc/video/wireless)
#disable_uboot_overlay_emmc=1
*disable_uboot_overlay_video=1*
#disable_uboot_overlay_audio=1
#disable_uboot_overlay_wireless=1
###Cape Universal Enable
*enable_uboot_cape_universal=1*
###U-Boot fdt tweaks...
#uboot_fdt_buffer=0x6
###U-Boot Overlays###

cmdline=coherent_pool=1M net.ifnames=0 quiet cape_universal=enable

#In the event of edid real failures, uncomment this next line:
#cmdline=coherent_pool=1M net.ifnames=0 quiet cape_universal=enable 
video=HDMI-A-1:1024x768@60e

##Example v3.8.x
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=

##Example v4.1.x
#cape_disable=bone_capemgr.disable_partno=
#cape_enable=bone_capemgr.enable_partno=

##enable Generic eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

uuid=8731d94f-f843-483d-ac8f-791800f1dbfb


Warm Regards,
MB

On Wednesday, 5 July 2017 12:38:30 UTC+10, RobertCNelson wrote:
>
> On Tue, Jul 4, 2017 at 9:08 PM, terra ÜÝÜ > 
> wrote: 
> > Hi All :) 
> > 
> > Cannot get config-pin to work on HDMI Pins even though HDMI is disabled, 
> any 
> > tips/know how would be appreciated. 
> > 
> > In /boot/uEnv.txt I have uncommented the 
> > ##BeagleBone Black: HDMI (Audio/Video) disabled: 
> > dtb=am335x-boneblack-emmc-overlay.dtb 
> > 
> > cmdline=coherent_pool=1M net.ifnames=0 quiet cape_universal=enable 
> > 
> > 
> > Working fine 
> > config-pin P9_27 gpio_pu 
> > 
> > Not Working 
> > config-pin P8_45 gpio_pu 
> > 
> > P8_45 pinmux file not found! 
> > cape-universala overlay not found 
> > run "config-pin overlay cape-universala" to load the cape 
> > 
> > P8_26 <-> P8_46 same error (LCD/HDMI line) 
> > 
> > I am running Debian GNU/Linux 8.8 (jessie) uname -a Linux beaglebone 
> > 4.4.54-ti-r93 
> > 
> > config-pin overlay cape-universala 
> > 
> > config-pin overlay cape-unversalh 
> > 
> > dmesg output 
> > 
> > [  497.778959] bone_capemgr bone_capemgr: part_number 'cape-universala', 
> > version 'N/A' 
> > [  497.779039] bone_capemgr bone_capemgr: slot #5: override 
> > [  497.779082] bone_capemgr bone_capemgr: Using override eeprom data at 
> slot 
> > 5 
> > [  497.779132] bone_capemgr bone_capemgr: slot #5: 'Override Board 
> > Name,00A0,Override Manuf,cape-universala' 
> > [  498.006318] bone_capemgr bone_capemgr: slot #5: cape-universala 
> conflict 
> > P8.3 (#4:univ-emmc) 
> > [  498.014867] bone_capemgr bone_capemgr: slot #5: Failed verification 
> > [  516.664001] bone_capemgr bone_capemgr: part_number 'cape-unversalh', 
> > version 'N/A' 
> > [  516.664052] bone_capemgr bone_capemgr: slot #6: override 
> > [  516.664075] bone_capemgr bone_capemgr: Using override eeprom data at 
> slot 
> > 6 
> > [  516.664102] bone_capemgr bone_capemgr: slot #6: 'Override Board 
> > Name,00A0,Override Manuf,cape-unversalh' 
>
> Use U-Boot overlays, 
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays 
>
> i have the main dtb + the cape-universal overlay setup to more cleanly 
> work with config-pin/etc.. 
>
> 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/edfd6681-0b6b-4a09-ac80-bbd467a840fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.