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] 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] Connecting/configuring ublox M8n GPS to Mission Planner Passthrough with BBBlu

[Timothy Litvin]

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/32c47d8a-bfac-4623-a3c1-4bb8394808ce%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]

After running those commands and typing my post, it occurred to me that I 
hadn't rebooted. When i did, I lost all comms: no WIFI, USB, IP, COM. 
Please bear with me, as I've got a busy day ahead, but I'll re-flash and 
re-setup later and take another whack at it. 

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/3043d69b-4c72-4b12-a1d4-45a4b8eca777%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 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/CAOCHtYh3Orv3xhX%3DSme7R5JMrDAXyktvZLS9yF-iqUPanotLgw%40mail.gmail.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]

On Sat, Jul 1, 2017 at 5:16 AM Jason Kridner  wrote:

> On Sat, Jul 1, 2017 at 2: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
>> debian@beaglebone:~$
>>
>> I check the ports again...
>>
>> debian@beaglebone:~$ dmesg | grep tty
>> [0.00] Kernel command line: console=ttyO0,115200n8
>> root=UUID=1b96dc8c-4e92-4f4f-86de-36d769439063 ro rootfstype=ext4 rootwait
>> coherent_pool=1M net.ifnames=0 quiet cape_universal=enable
>> [0.002905] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
>> [2.488082] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
>> base_baud = 300) is a 8250
>> [2.501480] console [ttyS0] enabled
>> [2.502849] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 159,
>> base_baud = 300) is a 8250
>> [2.503933] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 160,
>> base_baud = 300) is a 8250
>> [2.505034] 481a6000.serial: ttyS3 at MMIO 0x481a6000 (irq = 161,
>> base_baud = 300) is a 8250
>> [2.506066] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 162,
>> base_baud = 300) is a 8250
>> [2.507345] 481aa000.serial: ttyS5 at MMIO 0x481aa000 (irq = 163,
>> base_baud = 300) is a 8250
>> [9.537077] systemd[1]: Created slice system-getty.slice.
>> [9.613554] systemd[1]: Created slice system-serial\x2dgetty.slice.
>> debian@beaglebone:~$
>>
>> ...which are unchanged.
>>
>> I run the tio command anyway, trying several different baud (4800, 9600,
>> 38400) on ttyS1 and ttyS2 and, unsurprisingly, get no GPS:
>>
>> debian@beaglebone:~$ tio -b 38400 /dev/ttyS1
>>
>
> I doubt this is the correct default baud rate. Can you try 9600 and 4800?
>

Ooops, I didn't read your e-mail well. I see you said you tried each.

Running 'sudo perl /opt/scripts/device/bone/show-pins.pl' is often helpful
for debugging the pinmux situation.


>
>
>> [tio 06:21:56] tio v1.20
>> [tio 06:21:56] Press ctrl-t q to quit
>> [tio 06:21:56] Connected
>> [tio 06:22:01] Disconnected
>>
>>
>>
>> On Friday, June 30, 2017 at 9:36:03 AM UTC-7, RobertCNelson wrote:
>>
>>> On Thu, Jun 29, 2017 at 5:38 PM, Timothy Litvin 
>>> wrote:
>>> > Robert, Easy enough: I’ve deleted the
>>> dtb=am335x-boneblue-ArduPilot.dtb from
>>> > /boot/uEnv.txt and rebooted. So, explicitly, the Blue-Ardupilot recipe
>>> line
>>> > #3 Add BLUE DTB
>>> >
>>> > sudo sed -i 's/#dtb=$/dtb=am335x-boneblue-ArduPilot.dtb/'
>>> /boot/uEnv.txt
>>> >
>>> > is now obsolete with Jason’s recent DTB fix.  Now I get:
>>> >
>>> >
>>> > kimo@beaglebone:~$ sudo /opt/scripts/tools/version.sh
>>> >
>>> > [sudo] password for kimo:
>>> >
>>> > git:/opt/scripts/:[6d017b3c0902fd4e67fa6ef4801139da9a1726d6]
>>> >
>>> > eeprom:[A335BNLTBLA21712EL005600]
>>> >
>>> > dogtag:[BeagleBoard.org Debian Image 2017-02-19]
>>> >
>>> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
>>> > 2017.03-rc2-2-g11d4fd]
>>> >
>>> > kernel:[4.4.68-ti-rt-r111]
>>> >
>>> > nodejs:[v4.8.3]
>>> >
>>> >
>>> > However, having done so hasn’t yet gotten a GPS signal through. A
>>> query
>>> >
>>> > desmg | grep tty
>>> >
>>> > returns the same Port report I’ve gotten all along (included in the
>>> original
>>> > post). I’ve nevertheless tried the blue-arduplane/Mission Planner with
>>> > various parameters, e.g.,
>>> >
>>> >  sudo /usr/bin/ardupilot/blue-arduplane -C udp:192.168.8.132:14550 -B
>>> > /dev/ttyO2
>>> >
>>> > that continue to transmit telemetry without GPS.
>>> >
>>> > I’ve verified that I’m updated on Debian, blue-arduplane and the RT
>>> kernel.
>>>
>>> Hi Timothy,
>>>
>>> i think i found the problem... the pinmux was still not being setup
>>> properly..
>>>
>>> I just pushed a config-pin update for the Blue..
>>>
>>> sudo apt update
>>> sudo apt upgrade
>>> sudo apt install tio
>>>
>>> i picked up a uBlox PAM-7Q module, it's only 3.3v so i have it hooked
>>> up to UT1, i know your on GPS connector (5.0v)
>>>
>>> So on bootup we see:
>>>
>>> (UT1)
>>> debian@beaglebone:~$ config-pin -q P9.24
>>> P9_24 Mode: none
>>> debian@beaglebone:~$ config-pin -q P9.26
>>> P9_26 Mode: none
>>>
>>> and (GPS)
>>> debian@beaglebone:~$ config-pin -q P9.21
>>> P9_21 Mode: none
>>> debian@beaglebone:~$ config-pin -q P9.22
>>> P9_22 Mode: none
>>>
>>> So by default, using tio:
>>>
>>> debian@beaglebone:~$ tio -b 9600 /dev/ttyS1
>>> [tio 16:32:20] tio v1.20
>>> [tio 16:32:20] Press ctrl-t q to quit
>>> [tio 16:32:20] Connected
>>>
>>>
>>> 
>>>
>>> If i switch P9.24/P9.26 to uart:
>>>
>>> debian@beaglebone:~$ config-pin P9.24 uart

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

[Timothy Litvin]

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
debian@beaglebone:~$
   
I check the ports again...

debian@beaglebone:~$ dmesg | grep tty
[0.00] Kernel command line: console=ttyO0,115200n8 
root=UUID=1b96dc8c-4e92-4f4f-86de-36d769439063 ro rootfstype=ext4 rootwait 
coherent_pool=1M net.ifnames=0 quiet cape_universal=enable
[0.002905] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[2.488082] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158, 
base_baud = 300) is a 8250
[2.501480] console [ttyS0] enabled
[2.502849] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 159, 
base_baud = 300) is a 8250
[2.503933] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 160, 
base_baud = 300) is a 8250
[2.505034] 481a6000.serial: ttyS3 at MMIO 0x481a6000 (irq = 161, 
base_baud = 300) is a 8250
[2.506066] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 162, 
base_baud = 300) is a 8250
[2.507345] 481aa000.serial: ttyS5 at MMIO 0x481aa000 (irq = 163, 
base_baud = 300) is a 8250
[9.537077] systemd[1]: Created slice system-getty.slice.
[9.613554] systemd[1]: Created slice system-serial\x2dgetty.slice.
debian@beaglebone:~$

...which are unchanged.

I run the tio command anyway, trying several different baud (4800, 9600, 
38400) on ttyS1 and ttyS2 and, unsurprisingly, get no GPS:

debian@beaglebone:~$ tio -b 38400 /dev/ttyS1
[tio 06:21:56] tio v1.20
[tio 06:21:56] Press ctrl-t q to quit
[tio 06:21:56] Connected
[tio 06:22:01] Disconnected
 


On Friday, June 30, 2017 at 9:36:03 AM UTC-7, RobertCNelson wrote:
>
> On Thu, Jun 29, 2017 at 5:38 PM, Timothy Litvin  > wrote: 
> > Robert, Easy enough: I’ve deleted the dtb=am335x-boneblue-ArduPilot.dtb 
> from 
> > /boot/uEnv.txt and rebooted. So, explicitly, the Blue-Ardupilot recipe 
> line 
> > #3 Add BLUE DTB 
> > 
> > sudo sed -i 's/#dtb=$/dtb=am335x-boneblue-ArduPilot.dtb/' /boot/uEnv.txt 
> > 
> > is now obsolete with Jason’s recent DTB fix.  Now I get: 
> > 
> > 
> > kimo@beaglebone:~$ sudo /opt/scripts/tools/version.sh 
> > 
> > [sudo] password for kimo: 
> > 
> > git:/opt/scripts/:[6d017b3c0902fd4e67fa6ef4801139da9a1726d6] 
> > 
> > eeprom:[A335BNLTBLA21712EL005600] 
> > 
> > dogtag:[BeagleBoard.org Debian Image 2017-02-19] 
> > 
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> > 2017.03-rc2-2-g11d4fd] 
> > 
> > kernel:[4.4.68-ti-rt-r111] 
> > 
> > nodejs:[v4.8.3] 
> > 
> > 
> > However, having done so hasn’t yet gotten a GPS signal through. A query 
> > 
> > desmg | grep tty 
> > 
> > returns the same Port report I’ve gotten all along (included in the 
> original 
> > post). I’ve nevertheless tried the blue-arduplane/Mission Planner with 
> > various parameters, e.g., 
> > 
> >  sudo /usr/bin/ardupilot/blue-arduplane -C udp:192.168.8.132:14550 -B 
> > /dev/ttyO2 
> > 
> > that continue to transmit telemetry without GPS. 
> > 
> > I’ve verified that I’m updated on Debian, blue-arduplane and the RT 
> kernel. 
>
> Hi Timothy, 
>
> i think i found the problem... the pinmux was still not being setup 
> properly.. 
>
> I just pushed a config-pin update for the Blue.. 
>
> sudo apt update 
> sudo apt upgrade 
> sudo apt install tio 
>
> i picked up a uBlox PAM-7Q module, it's only 3.3v so i have it hooked 
> up to UT1, i know your on GPS connector (5.0v) 
>
> So on bootup we see: 
>
> (UT1) 
> debian@beaglebone:~$ config-pin -q P9.24 
> P9_24 Mode: none 
> debian@beaglebone:~$ config-pin -q P9.26 
> P9_26 Mode: none 
>
> and (GPS) 
> debian@beaglebone:~$ config-pin -q P9.21 
> P9_21 Mode: none 
> debian@beaglebone:~$ config-pin -q P9.22 
> P9_22 Mode: none 
>
> So by default, using tio: 
>
> debian@beaglebone:~$ tio -b 9600 /dev/ttyS1 
> [tio 16:32:20] tio v1.20 
> [tio 16:32:20] Press ctrl-t q to quit 
> [tio 16:32:20] Connected 
>
>
>  
>
> If i switch P9.24/P9.26 to uart: 
>
> debian@beaglebone:~$ config-pin P9.24 uart 
> debian@beaglebone:~$ config-pin P9.26 uart 
> debian@beaglebone:~$ config-pin -q P9.24 
> P9_24 Mode: uart 
> debian@beaglebone:~$ config-pin -q P9.26 
> P9_26 Mode: uart 
>
> then fire up tio: 
>
> debian@beaglebone:~$ tio -b 9600 /dev/ttyS1 
> [tio 16:33:08] tio v1.20 
> [tio 16:33:08] Press ctrl-t q to quit 
> [tio 16:33:08] Connected 
> W$GPRMC,163309.00,V,,,300617,,,N*70 
> $GPVTG,N*30 
> $GPGGA,163309.00,0,00,99.99,,*68 
> $GPGSA,A,1,99.99,99.99,99.99*30 
> $GPGSV,3,1,11,01,31,123,,07,46,149,17,08,32,052,17,11,50,107,19*74 
> $GPGSV,3,2,11,13,31,299,21,15,08,327,,17,26,215,,19,02,218,*76 
> 

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

[Robert Nelson]

On Fri, Jun 30, 2017 at 11:53 AM, Robert Nelson  wrote:
> On Fri, Jun 30, 2017 at 11:51 AM, Jason Kridner  wrote:
>> Robert,
>>
>> Can we make sure the Blue UART pins default to UART and that config-pin is
>> not necessary? This is critical to our expected user experience where the
>> I/O ports are defined by their default function.
>>
>> What did I do wrong?
>
> I'm not sure, i had assumed your dts changes would make it default..
> but it didn't..
>
> I'll shove it in the bootscript, to fix it now...
>
> cd /opt/scripts/tools/
> git pull

Okay that's fixed:

If config-pin is too old, it'll complain..

debian@beaglebone:~$ journalctl | grep am335x_evm: | grep config-pin
Jun 30 17:23:51 beaglebone sh[429]: am335x_evm: broken
/usr/bin/config-pin upgrade bb-cape-overlays

once it's updated..

debian@beaglebone:~$ journalctl | grep am335x_evm: | grep config-pin
Jun 30 17:27:17 beaglebone sh[412]: am335x_evm: config-pin: GPS:
Setting P9.21/P9.22 as: uart: [/dev/ttyS2]
Jun 30 17:27:17 beaglebone sh[412]: am335x_evm: config-pin: UT1:
Setting P9.24/P9.26 as: uart: [/dev/ttyS1]

debian@beaglebone:~$ config-pin -q P9.24
P9_24 Mode: uart
debian@beaglebone:~$ config-pin -q P9.26
P9_26 Mode: uart
debian@beaglebone:~$ config-pin -q P9.21
P9_21 Mode: uart
debian@beaglebone:~$ config-pin -q P9.22
P9_22 Mode: uart

debian@beaglebone:~$ tio -b 9600 /dev/ttyS1
[tio 17:30:57] tio v1.20
[tio 17:30:57] Press ctrl-t q to quit
[tio 17:30:57] Connected
$GPRMC,173058.00,V,,,300617,,,N*76
$GPVTG,N*30
$GPGGA,173058.00,0,00,99.99,,*6E
$GPGSA,A,1,99.99,99.99,99.99*30
$GPGSV,1,1,02,13,,,19,17,,,22*77
$GPGLL,173058.00,V,N*42
$GPRMC,173059.00,V,,,300617,,,N*77

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/CAOCHtYiagS%3Dc%2Bq8ekshHm68yFNGkAuj3Ezic%2BgLy-ZoQBQX4fQ%40mail.gmail.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 Fri, Jun 30, 2017 at 11:51 AM, Jason Kridner  wrote:
> Robert,
>
> Can we make sure the Blue UART pins default to UART and that config-pin is
> not necessary? This is critical to our expected user experience where the
> I/O ports are defined by their default function.
>
> What did I do wrong?

I'm not sure, i had assumed your dts changes would make it default..
but it didn't..

I'll shove it in the bootscript, to fix it now...

cd /opt/scripts/tools/
git pull

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/CAOCHtYiV%2Bh9QEjzch8LBRuHRvKuPm83%3Dj7giZ--G%3DPjedVJQmQ%40mail.gmail.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]

Robert,

Can we make sure the Blue UART pins default to UART and that config-pin is
not necessary? This is critical to our expected user experience where the
I/O ports are defined by their default function.

What did I do wrong?

Regards,
Jason

On Fri, Jun 30, 2017 at 12:35 PM Robert Nelson 
wrote:

> On Thu, Jun 29, 2017 at 5:38 PM, Timothy Litvin 
> wrote:
> > Robert, Easy enough: I’ve deleted the dtb=am335x-boneblue-ArduPilot.dtb
> from
> > /boot/uEnv.txt and rebooted. So, explicitly, the Blue-Ardupilot recipe
> line
> > #3 Add BLUE DTB
> >
> > sudo sed -i 's/#dtb=$/dtb=am335x-boneblue-ArduPilot.dtb/' /boot/uEnv.txt
> >
> > is now obsolete with Jason’s recent DTB fix.  Now I get:
> >
> >
> > kimo@beaglebone:~$ sudo /opt/scripts/tools/version.sh
> >
> > [sudo] password for kimo:
> >
> > git:/opt/scripts/:[6d017b3c0902fd4e67fa6ef4801139da9a1726d6]
> >
> > eeprom:[A335BNLTBLA21712EL005600]
> >
> > dogtag:[BeagleBoard.org Debian Image 2017-02-19]
> >
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> > 2017.03-rc2-2-g11d4fd]
> >
> > kernel:[4.4.68-ti-rt-r111]
> >
> > nodejs:[v4.8.3]
> >
> >
> > However, having done so hasn’t yet gotten a GPS signal through. A query
> >
> > desmg | grep tty
> >
> > returns the same Port report I’ve gotten all along (included in the
> original
> > post). I’ve nevertheless tried the blue-arduplane/Mission Planner with
> > various parameters, e.g.,
> >
> >  sudo /usr/bin/ardupilot/blue-arduplane -C udp:192.168.8.132:14550 -B
> > /dev/ttyO2
> >
> > that continue to transmit telemetry without GPS.
> >
> > I’ve verified that I’m updated on Debian, blue-arduplane and the RT
> kernel.
>
> Hi Timothy,
>
> i think i found the problem... the pinmux was still not being setup
> properly..
>
> I just pushed a config-pin update for the Blue..
>
> sudo apt update
> sudo apt upgrade
> sudo apt install tio
>
> i picked up a uBlox PAM-7Q module, it's only 3.3v so i have it hooked
> up to UT1, i know your on GPS connector (5.0v)
>
> So on bootup we see:
>
> (UT1)
> debian@beaglebone:~$ config-pin -q P9.24
> P9_24 Mode: none
> debian@beaglebone:~$ config-pin -q P9.26
> P9_26 Mode: none
>
> and (GPS)
> debian@beaglebone:~$ config-pin -q P9.21
> P9_21 Mode: none
> debian@beaglebone:~$ config-pin -q P9.22
> P9_22 Mode: none
>
> So by default, using tio:
>
> debian@beaglebone:~$ tio -b 9600 /dev/ttyS1
> [tio 16:32:20] tio v1.20
> [tio 16:32:20] Press ctrl-t q to quit
> [tio 16:32:20] Connected
>
>
> 
>
> If i switch P9.24/P9.26 to uart:
>
> debian@beaglebone:~$ config-pin P9.24 uart
> debian@beaglebone:~$ config-pin P9.26 uart
> debian@beaglebone:~$ config-pin -q P9.24
> P9_24 Mode: uart
> debian@beaglebone:~$ config-pin -q P9.26
> P9_26 Mode: uart
>
> then fire up tio:
>
> debian@beaglebone:~$ tio -b 9600 /dev/ttyS1
> [tio 16:33:08] tio v1.20
> [tio 16:33:08] Press ctrl-t q to quit
> [tio 16:33:08] Connected
> W$GPRMC,163309.00,V,,,300617,,,N*70
> $GPVTG,N*30
> $GPGGA,163309.00,0,00,99.99,,*68
> $GPGSA,A,1,99.99,99.99,99.99*30
> $GPGSV,3,1,11,01,31,123,,07,46,149,17,08,32,052,17,11,50,107,19*74
> $GPGSV,3,2,11,13,31,299,21,15,08,327,,17,26,215,,19,02,218,*76
> $GPGSV,3,3,11,27,00,046,,28,64,291,,30,79,211,23*42
> $GPGLL,163309.00,V,N*44
> $GPRMC,163310.00,V,,,300617,,,N*78
>
>
> In your case run:
>
>
> debian@beaglebone:~$ config-pin P9.21 uart
> debian@beaglebone:~$ config-pin P9.22 uart
>
>
> debian@beaglebone:~$ tio -b 9600 /dev/ttyS2
>
> and see that happens (9600 might not be the baud)
>
> I've added both UT1 and GPS info here:
>
> https://github.com/beagleboard/beaglebone-blue/wiki/Pinouts
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
-- 
https://beagleboard.org/about

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CA%2BT6QP%3DMBcFEJWmV0XehRWaMbtjo78vz9D4k3qqcjNheSnHaxQ%40mail.gmail.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, Jun 29, 2017 at 5:38 PM, Timothy Litvin  wrote:
> Robert, Easy enough: I’ve deleted the dtb=am335x-boneblue-ArduPilot.dtb from
> /boot/uEnv.txt and rebooted. So, explicitly, the Blue-Ardupilot recipe line
> #3 Add BLUE DTB
>
> sudo sed -i 's/#dtb=$/dtb=am335x-boneblue-ArduPilot.dtb/' /boot/uEnv.txt
>
> is now obsolete with Jason’s recent DTB fix.  Now I get:
>
>
> kimo@beaglebone:~$ sudo /opt/scripts/tools/version.sh
>
> [sudo] password for kimo:
>
> git:/opt/scripts/:[6d017b3c0902fd4e67fa6ef4801139da9a1726d6]
>
> eeprom:[A335BNLTBLA21712EL005600]
>
> dogtag:[BeagleBoard.org Debian Image 2017-02-19]
>
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2017.03-rc2-2-g11d4fd]
>
> kernel:[4.4.68-ti-rt-r111]
>
> nodejs:[v4.8.3]
>
>
> However, having done so hasn’t yet gotten a GPS signal through. A query
>
> desmg | grep tty
>
> returns the same Port report I’ve gotten all along (included in the original
> post). I’ve nevertheless tried the blue-arduplane/Mission Planner with
> various parameters, e.g.,
>
>  sudo /usr/bin/ardupilot/blue-arduplane -C udp:192.168.8.132:14550 -B
> /dev/ttyO2
>
> that continue to transmit telemetry without GPS.
>
> I’ve verified that I’m updated on Debian, blue-arduplane and the RT kernel.

Hi Timothy,

i think i found the problem... the pinmux was still not being setup properly..

I just pushed a config-pin update for the Blue..

sudo apt update
sudo apt upgrade
sudo apt install tio

i picked up a uBlox PAM-7Q module, it's only 3.3v so i have it hooked
up to UT1, i know your on GPS connector (5.0v)

So on bootup we see:

(UT1)
debian@beaglebone:~$ config-pin -q P9.24
P9_24 Mode: none
debian@beaglebone:~$ config-pin -q P9.26
P9_26 Mode: none

and (GPS)
debian@beaglebone:~$ config-pin -q P9.21
P9_21 Mode: none
debian@beaglebone:~$ config-pin -q P9.22
P9_22 Mode: none

So by default, using tio:

debian@beaglebone:~$ tio -b 9600 /dev/ttyS1
[tio 16:32:20] tio v1.20
[tio 16:32:20] Press ctrl-t q to quit
[tio 16:32:20] Connected




If i switch P9.24/P9.26 to uart:

debian@beaglebone:~$ config-pin P9.24 uart
debian@beaglebone:~$ config-pin P9.26 uart
debian@beaglebone:~$ config-pin -q P9.24
P9_24 Mode: uart
debian@beaglebone:~$ config-pin -q P9.26
P9_26 Mode: uart

then fire up tio:

debian@beaglebone:~$ tio -b 9600 /dev/ttyS1
[tio 16:33:08] tio v1.20
[tio 16:33:08] Press ctrl-t q to quit
[tio 16:33:08] Connected
W$GPRMC,163309.00,V,,,300617,,,N*70
$GPVTG,N*30
$GPGGA,163309.00,0,00,99.99,,*68
$GPGSA,A,1,99.99,99.99,99.99*30
$GPGSV,3,1,11,01,31,123,,07,46,149,17,08,32,052,17,11,50,107,19*74
$GPGSV,3,2,11,13,31,299,21,15,08,327,,17,26,215,,19,02,218,*76
$GPGSV,3,3,11,27,00,046,,28,64,291,,30,79,211,23*42
$GPGLL,163309.00,V,N*44
$GPRMC,163310.00,V,,,300617,,,N*78


In your case run:


debian@beaglebone:~$ config-pin P9.21 uart
debian@beaglebone:~$ config-pin P9.22 uart


debian@beaglebone:~$ tio -b 9600 /dev/ttyS2

and see that happens (9600 might not be the baud)

I've added both UT1 and GPS info here:

https://github.com/beagleboard/beaglebone-blue/wiki/Pinouts

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/CAOCHtYiSCua8ruDMMSCUZZ4Bea7fyk40-O-enFGArGVwkNkXoA%40mail.gmail.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]

Robert, Easy enough: I’ve deleted the dtb=am335x-boneblue-ArduPilot.dtb 
from /boot/uEnv.txt and rebooted. So, explicitly, the Blue-Ardupilot recipe 
line #3 Add BLUE DTB 

sudo sed -i 's/#dtb=$/dtb=am335x-boneblue-ArduPilot.dtb/' /boot/uEnv.txt

is now obsolete with Jason’s recent DTB fix.  Now I get: 


kimo@beaglebone:~$ sudo /opt/scripts/tools/version.sh

[sudo] password for kimo:

git:/opt/scripts/:[6d017b3c0902fd4e67fa6ef4801139da9a1726d6]

eeprom:[A335BNLTBLA21712EL005600]

dogtag:[BeagleBoard.org Debian Image 2017-02-19]

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
2017.03-rc2-2-g11d4fd]

kernel:[4.4.68-ti-rt-r111]

nodejs:[v4.8.3]

However, having done so hasn’t yet gotten a GPS signal through. A query

desmg | grep tty 

returns the same Port report I’ve gotten all along (included in the 
original post). I’ve nevertheless tried the blue-arduplane/Mission Planner 
with various parameters, e.g., 

 sudo /usr/bin/ardupilot/blue-arduplane -C udp:192.168.8.132:14550 -B 
/dev/ttyO2

that continue to transmit telemetry without GPS.

I’ve verified that I’m updated on Debian, blue-arduplane and the RT kernel. 
 

On Thursday, June 29, 2017 at 9:50:51 AM UTC-7, RobertCNelson wrote:
>
> On Thu, Jun 29, 2017 at 11:44 AM, Timothy Litvin  > wrote: 
> > debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh 
> > git:/opt/scripts/:[6d017b3c0902fd4e67fa6ef4801139da9a1726d6] 
> > eeprom:[A335BNLTBLA21712EL005600] 
> > dogtag:[BeagleBoard.org Debian Image 2017-02-19] 
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> > 2017.03-rc2-2-g11d4fd] 
> > kernel:[4.4.68-ti-rt-r111] 
> > nodejs:[v4.8.3] 
> > device-tree-override:[dtb=am335x-boneblue-ArduPilot.dtb] 
>
> You don't need this /boot/uEnv.txt dtb modification 
>
> Jason fixed the base/default: am335x-boneblue.dtb last week? (maybe 2 
> weeks ago) 
>
> So just remove the dtb=am335x-boneblue-ArduPilot.dtb from /boot/uEnv.txt 
>
> 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/6e5146d2-2aa7-4b24-a373-4c93d84998b0%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]

Easy enough: I've removed that line from /boot/uEnv.txt, confirmed updates 
and rebooted. Screenshot from subsequent "sudo 
opt/scripts/tools/version.sh" included with my reply to Jason. Restarted 
and reconnected everything. So far, still no GPS connection. BTW, from 
Jason's One-Liner GPS test, I tried using an blue-arduplane GPS parameter 
of -F /dev/ttyO2, but have tried monkeying with the originally posted 
guidelines -B and /dev/ttyO5, and -B /dev/ttyO2 . 


On Thursday, June 29, 2017 at 9:50:51 AM UTC-7, RobertCNelson wrote:
>
> On Thu, Jun 29, 2017 at 11:44 AM, Timothy Litvin  > wrote: 
> > debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh 
> > git:/opt/scripts/:[6d017b3c0902fd4e67fa6ef4801139da9a1726d6] 
> > eeprom:[A335BNLTBLA21712EL005600] 
> > dogtag:[BeagleBoard.org Debian Image 2017-02-19] 
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> > 2017.03-rc2-2-g11d4fd] 
> > kernel:[4.4.68-ti-rt-r111] 
> > nodejs:[v4.8.3] 
> > device-tree-override:[dtb=am335x-boneblue-ArduPilot.dtb] 
>
> You don't need this /boot/uEnv.txt dtb modification 
>
> Jason fixed the base/default: am335x-boneblue.dtb last week? (maybe 2 
> weeks ago) 
>
> So just remove the dtb=am335x-boneblue-ArduPilot.dtb from /boot/uEnv.txt 
>
> 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/d954dd30-2e98-4fd9-bc99-7f48f40c7efa%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]

My ublox M8n has a blinking blue led which I’ve come to believe means it 
has at least a good “2D lock”, i.e., at least 3 satellites while here, 
belowdecks. My breadboard is portable; I took it topside and the GPS LED 
continues to blink blue, with no apparent change to status. 

The first One-Liner was straight copy/paste from the wiki; then as you can 
see, I tried a few 4800, 9600, and 38400 (uBlox shipped default baud). 


On Thursday, June 29, 2017 at 10:31:53 AM UTC-7, Jason Kridner wrote:
>
> On Thu, Jun 29, 2017 at 12:57 PM Timothy Litvin  > wrote:
>
>> Hi Jason, thanks for your support as well. The One-Liner tests should be 
>> a great help. When I try your GPS one-liner verbatim, or set to 9600, the 
>> line feeds, but then just sits until I ctrl-C. What does this tell me?
>>
>
> Can you copy the text out of the window to show what you typed and what 
> you got?
>
> I suspect it means you don't have a GPS lock, which is typical for 
> indoors. Most GPS devices I've played with tend to be a bit quiet when they 
> don't have a lock. They also typically have an LED pattern saying if they 
> have a lock or not.
>  
>
>>
>>

-- 
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/74e6efe6-d5b2-4fcb-ab54-bb344f465130%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]

Hi Jason, thanks for your support as well. The One-Liner tests should be a 
great help. When I try your GPS one-liner verbatim, or set to 9600, the 
line feeds, but then just sits until I ctrl-C. What does this tell me?

On Wednesday, June 28, 2017 at 1:45:24 PM UTC-7, Jason Kridner wrote:
>
> With my latest device tree patches, it should be UART by default without 
> any config-pin calls. 
>
> Most of these GPS devices are 4800 or 9600 baud by default. 
>
> I've created a page for one-liner tests for various modules: 
> https://github.com/beagleboard/beaglebone-blue/wiki/One-Liner-Module-Tests 
> On Tue, Jun 27, 2017 at 9:52 PM Robert Nelson  > wrote:
>
>> On Tue, Jun 27, 2017 at 5:39 PM, Timothy Litvin > > wrote:
>> > Greetings from the steep learning curve.  I’m setting up my first 
>> Arduplane
>> > while learning Linux on my first AP (BBBlue) with my first GCS (Mission
>> > Planner) on Windows 10, for use in a custom vessel. Practically 
>> speaking,
>> > it's been a recipe for delayed gratification, uncomfortably akin to a 
>> monkey
>> > with a typewriter.
>> >
>> > I now have blue-arduplane running on the Bone (sudo
>> > /usr/bin/ardupilot/blue-arduplane -C udp:192.168.8.132:14550 -B 
>> /dev/ttyO5
>> > with telemetry reporting via wifi to my Windows 10 laptop, but no signal
>> > arrives from the GPS (booted, with flashing blue led). My GPS is a 
>> generic
>> > ublox neo-M8n (with compass), plugged into the GPS jst-sh (wired 
>> according
>> > to attached jpeg). Windows Device Manager reports ublox Virtual Com 
>> Port on
>> > COM5.
>> >
>> > I’m guessing the GPS needs to be further configured, i.e., I need to 
>> either
>> > download/install or create a new ublox-M8 configuration file. I've 
>> installed
>> > u-center to configure the GPS; u-center reports nothing.  That feed 
>> seems to
>> > imply/require a Passthrough connection in Mission Planner while running
>> > blue-arduplane) so, in the Flight Data screen, ctrl-F:
>> >
>> > It’s unclear whether the “MAVSerial pass” button is activated on click
>> > (doesn’t toggle color, just grays temporarily on rollover & click).
>> > u-center 8.25 doesn’t detect GPS on any port. Tried also creating a TCP
>> > connection in u-center through Network Connection, New, setting Address 
>> to
>> > tcp://localhost:500, set baud to 38400 (with and without AutoBaud) after
>> > which I get a Connection Error message.
>> >
>> > I then installed minicom on the Bone. When I run "dmesg | grep tty" I 
>> get:
>> >
>> >
>> >
>> > [0.00] Kernel command line: console=ttyO0,115200n8
>> > root=UUID=1b96dc8c-4e92-4f4f-86de-36d769439063 ro rootfstype=ext4 
>> rootwait
>> > coherent_pool=1M net.ifnames=0 quiet cape_universal=enable
>> >
>> > [0.002863] WARNING: Your 'console=ttyO0' has been replaced by 
>> 'ttyS0'
>> >
>> > [2.492065] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
>> > base_baud = 300) is a 8250
>> >
>> > [2.505478] console [ttyS0] enabled
>> >
>> > [2.506866] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 159,
>> > base_baud = 300) is a 8250
>> >
>> > [2.507975] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 160,
>> > base_baud = 300) is a 8250
>> >
>> > [2.509094] 481a6000.serial: ttyS3 at MMIO 0x481a6000 (irq = 161,
>> > base_baud = 300) is a 8250
>> >
>> > [2.510109] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 162,
>> > base_baud = 300) is a 8250
>> >
>> > [2.511416] 481aa000.serial: ttyS5 at MMIO 0x481aa000 (irq = 163,
>> > base_baud = 300) is a 8250
>> >
>> > [9.819121] systemd[1]: Created slice system-getty.slice.
>> >
>> > [9.831852] systemd[1]: Created slice system-serial\x2dgetty.slice.
>> >
>> >
>> >
>> > In Minicom I took a blind whack at setting Serial Port ttyS5 (and 
>> ttyS4) to
>> > 38400 Baud, 8N1 and Hardware control on/off, to my chagrin, no effect 
>> on the
>> > non-existent GPS connection. U-center still can't connect, so I can't
>> > configure the GPS...if that's what i need to do. Minicom reports the 
>> port's
>> > values have been changed, but  "dmesg | grep tty" reports the same as 
>> above,
>> > unchanged. I've also tried using the -B /dev/ttyS5 alternative for GPS 
>> when
>> > starting blue-arduplane. At this point it occurs to me that I could've
>> > steered wrong repeatedly, or just missed a step.
>> >
>> > If you know what you’re doing, by now it’s probably clear that I don’t.
>> > Helpful hints anyone?
>>
>> so you need to connect the pin to the peripheral:
>>
>> #uart 2 (gps)
>> config-pin P9.21 uart
>> config-pin P9.22 uart
>>
>> #uart 1
>> config-pin P9.24 uart
>> config-pin P9.26 uart
>>
>> PS, i just pushed an arduplane deb update today too..
>>
>> 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 

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

[Robert Nelson]

On Thu, Jun 29, 2017 at 11:44 AM, Timothy Litvin  wrote:
> debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
> git:/opt/scripts/:[6d017b3c0902fd4e67fa6ef4801139da9a1726d6]
> eeprom:[A335BNLTBLA21712EL005600]
> dogtag:[BeagleBoard.org Debian Image 2017-02-19]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2017.03-rc2-2-g11d4fd]
> kernel:[4.4.68-ti-rt-r111]
> nodejs:[v4.8.3]
> device-tree-override:[dtb=am335x-boneblue-ArduPilot.dtb]

You don't need this /boot/uEnv.txt dtb modification

Jason fixed the base/default: am335x-boneblue.dtb last week? (maybe 2 weeks ago)

So just remove the dtb=am335x-boneblue-ArduPilot.dtb from /boot/uEnv.txt

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/CAOCHtYiRBQMwFrf%2B8oA5_duOYViDjKcpGDjOXXh48KwMQpnb-w%40mail.gmail.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]

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[6d017b3c0902fd4e67fa6ef4801139da9a1726d6]
eeprom:[A335BNLTBLA21712EL005600]
dogtag:[BeagleBoard.org Debian Image 2017-02-19]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
2017.03-rc2-2-g11d4fd]
kernel:[4.4.68-ti-rt-r111]
nodejs:[v4.8.3]
device-tree-override:[dtb=am335x-boneblue-ArduPilot.dtb]
debian@beaglebone:~$


On Thursday, June 29, 2017 at 8:23:59 AM UTC-7, RobertCNelson wrote:
>
> On Thu, Jun 29, 2017 at 10:20 AM, Timothy Litvin  > wrote: 
>
> Please run: 
>
> sudo /opt/scripts/tools/version.sh 
>
> and copy the output to us for review 
>
> 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/3be419aa-be0c-4fb5-a836-42d9e47dc7a7%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, Jun 29, 2017 at 10:20 AM, Timothy Litvin  wrote:
> Thanks Robert, I've loaded your update. I had assumed the BBBlue had those
> pins pre-allocated (as the PCB silkscreen indicates).  Mirko's instructions
> made the GPS sound like plug-n-play, not referencing additional setup. I’ve
> installed the config-pin utility, and a command-line entry of the line sudo
> config-pin P9.21 uart informs me “P9_21 pinmux file not found! Please verify
> your Device Tree File.”  From this I take it that I need to load
> cape-universala…

it's actually installed by default, and our local version has a few
changes from Charles' original.

it was only a recent kernel that has the uart change by default..

Please run:

sudo /opt/scripts/tools/version.sh

and copy the output to us for review

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/CAOCHtYgJWOigYYT%2B2QXgs%2BmhJrg75DZjCR8GgP1cXn0ZfEzvZw%40mail.gmail.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]

Thanks Robert, I've loaded your update. I had assumed the BBBlue had those 
pins pre-allocated (as the PCB silkscreen indicates).  Mirko's instructions 
made the GPS sound like plug-n-play, not referencing additional setup. I’ve 
installed the config-pin utility, and a command-line entry of the line sudo 
config-pin P9.21 uart informs me “P9_21 pinmux file not found! Please 
verify your Device Tree File.”  From this I take it that I need to load 
cape-universala… 


>
>
>
>
>
>
>
>
>
>
>
> *so you need to connect the pin to the peripheral: #uart 2 (gps) 
> config-pin P9.21 uart config-pin P9.22 uart #uart 1 config-pin P9.24 uart 
> config-pin P9.26 uart PS, i just pushed an arduplane deb update today 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0b265e33-b2b8-4f51-b0cd-559f1136b96a%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]

With my latest device tree patches, it should be UART by default without
any config-pin calls.

Most of these GPS devices are 4800 or 9600 baud by default.

I've created a page for one-liner tests for various modules:
https://github.com/beagleboard/beaglebone-blue/wiki/One-Liner-Module-Tests
On Tue, Jun 27, 2017 at 9:52 PM Robert Nelson 
wrote:

> On Tue, Jun 27, 2017 at 5:39 PM, Timothy Litvin 
> wrote:
> > Greetings from the steep learning curve.  I’m setting up my first
> Arduplane
> > while learning Linux on my first AP (BBBlue) with my first GCS (Mission
> > Planner) on Windows 10, for use in a custom vessel. Practically speaking,
> > it's been a recipe for delayed gratification, uncomfortably akin to a
> monkey
> > with a typewriter.
> >
> > I now have blue-arduplane running on the Bone (sudo
> > /usr/bin/ardupilot/blue-arduplane -C udp:192.168.8.132:14550 -B
> /dev/ttyO5
> > with telemetry reporting via wifi to my Windows 10 laptop, but no signal
> > arrives from the GPS (booted, with flashing blue led). My GPS is a
> generic
> > ublox neo-M8n (with compass), plugged into the GPS jst-sh (wired
> according
> > to attached jpeg). Windows Device Manager reports ublox Virtual Com Port
> on
> > COM5.
> >
> > I’m guessing the GPS needs to be further configured, i.e., I need to
> either
> > download/install or create a new ublox-M8 configuration file. I've
> installed
> > u-center to configure the GPS; u-center reports nothing.  That feed
> seems to
> > imply/require a Passthrough connection in Mission Planner while running
> > blue-arduplane) so, in the Flight Data screen, ctrl-F:
> >
> > It’s unclear whether the “MAVSerial pass” button is activated on click
> > (doesn’t toggle color, just grays temporarily on rollover & click).
> > u-center 8.25 doesn’t detect GPS on any port. Tried also creating a TCP
> > connection in u-center through Network Connection, New, setting Address
> to
> > tcp://localhost:500, set baud to 38400 (with and without AutoBaud) after
> > which I get a Connection Error message.
> >
> > I then installed minicom on the Bone. When I run "dmesg | grep tty" I
> get:
> >
> >
> >
> > [0.00] Kernel command line: console=ttyO0,115200n8
> > root=UUID=1b96dc8c-4e92-4f4f-86de-36d769439063 ro rootfstype=ext4
> rootwait
> > coherent_pool=1M net.ifnames=0 quiet cape_universal=enable
> >
> > [0.002863] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
> >
> > [2.492065] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
> > base_baud = 300) is a 8250
> >
> > [2.505478] console [ttyS0] enabled
> >
> > [2.506866] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 159,
> > base_baud = 300) is a 8250
> >
> > [2.507975] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 160,
> > base_baud = 300) is a 8250
> >
> > [2.509094] 481a6000.serial: ttyS3 at MMIO 0x481a6000 (irq = 161,
> > base_baud = 300) is a 8250
> >
> > [2.510109] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 162,
> > base_baud = 300) is a 8250
> >
> > [2.511416] 481aa000.serial: ttyS5 at MMIO 0x481aa000 (irq = 163,
> > base_baud = 300) is a 8250
> >
> > [9.819121] systemd[1]: Created slice system-getty.slice.
> >
> > [9.831852] systemd[1]: Created slice system-serial\x2dgetty.slice.
> >
> >
> >
> > In Minicom I took a blind whack at setting Serial Port ttyS5 (and ttyS4)
> to
> > 38400 Baud, 8N1 and Hardware control on/off, to my chagrin, no effect on
> the
> > non-existent GPS connection. U-center still can't connect, so I can't
> > configure the GPS...if that's what i need to do. Minicom reports the
> port's
> > values have been changed, but  "dmesg | grep tty" reports the same as
> above,
> > unchanged. I've also tried using the -B /dev/ttyS5 alternative for GPS
> when
> > starting blue-arduplane. At this point it occurs to me that I could've
> > steered wrong repeatedly, or just missed a step.
> >
> > If you know what you’re doing, by now it’s probably clear that I don’t.
> > Helpful hints anyone?
>
> so you need to connect the pin to the peripheral:
>
> #uart 2 (gps)
> config-pin P9.21 uart
> config-pin P9.22 uart
>
> #uart 1
> config-pin P9.24 uart
> config-pin P9.26 uart
>
> PS, i just pushed an arduplane deb update today too..
>
> 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/CAOCHtYgGjBjPfyc6Cmqo5Wep6%2BWMNBCr0Rhu2kw6a9M-DzLBqA%40mail.gmail.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 

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

[Robert Nelson]

On Tue, Jun 27, 2017 at 5:39 PM, Timothy Litvin  wrote:
> Greetings from the steep learning curve.  I’m setting up my first Arduplane
> while learning Linux on my first AP (BBBlue) with my first GCS (Mission
> Planner) on Windows 10, for use in a custom vessel. Practically speaking,
> it's been a recipe for delayed gratification, uncomfortably akin to a monkey
> with a typewriter.
>
> I now have blue-arduplane running on the Bone (sudo
> /usr/bin/ardupilot/blue-arduplane -C udp:192.168.8.132:14550 -B /dev/ttyO5
> with telemetry reporting via wifi to my Windows 10 laptop, but no signal
> arrives from the GPS (booted, with flashing blue led). My GPS is a generic
> ublox neo-M8n (with compass), plugged into the GPS jst-sh (wired according
> to attached jpeg). Windows Device Manager reports ublox Virtual Com Port on
> COM5.
>
> I’m guessing the GPS needs to be further configured, i.e., I need to either
> download/install or create a new ublox-M8 configuration file. I've installed
> u-center to configure the GPS; u-center reports nothing.  That feed seems to
> imply/require a Passthrough connection in Mission Planner while running
> blue-arduplane) so, in the Flight Data screen, ctrl-F:
>
> It’s unclear whether the “MAVSerial pass” button is activated on click
> (doesn’t toggle color, just grays temporarily on rollover & click).
> u-center 8.25 doesn’t detect GPS on any port. Tried also creating a TCP
> connection in u-center through Network Connection, New, setting Address to
> tcp://localhost:500, set baud to 38400 (with and without AutoBaud) after
> which I get a Connection Error message.
>
> I then installed minicom on the Bone. When I run "dmesg | grep tty" I get:
>
>
>
> [0.00] Kernel command line: console=ttyO0,115200n8
> root=UUID=1b96dc8c-4e92-4f4f-86de-36d769439063 ro rootfstype=ext4 rootwait
> coherent_pool=1M net.ifnames=0 quiet cape_universal=enable
>
> [0.002863] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
>
> [2.492065] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158,
> base_baud = 300) is a 8250
>
> [2.505478] console [ttyS0] enabled
>
> [2.506866] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 159,
> base_baud = 300) is a 8250
>
> [2.507975] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 160,
> base_baud = 300) is a 8250
>
> [2.509094] 481a6000.serial: ttyS3 at MMIO 0x481a6000 (irq = 161,
> base_baud = 300) is a 8250
>
> [2.510109] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 162,
> base_baud = 300) is a 8250
>
> [2.511416] 481aa000.serial: ttyS5 at MMIO 0x481aa000 (irq = 163,
> base_baud = 300) is a 8250
>
> [9.819121] systemd[1]: Created slice system-getty.slice.
>
> [9.831852] systemd[1]: Created slice system-serial\x2dgetty.slice.
>
>
>
> In Minicom I took a blind whack at setting Serial Port ttyS5 (and ttyS4) to
> 38400 Baud, 8N1 and Hardware control on/off, to my chagrin, no effect on the
> non-existent GPS connection. U-center still can't connect, so I can't
> configure the GPS...if that's what i need to do. Minicom reports the port's
> values have been changed, but  "dmesg | grep tty" reports the same as above,
> unchanged. I've also tried using the -B /dev/ttyS5 alternative for GPS when
> starting blue-arduplane. At this point it occurs to me that I could've
> steered wrong repeatedly, or just missed a step.
>
> If you know what you’re doing, by now it’s probably clear that I don’t.
> Helpful hints anyone?

so you need to connect the pin to the peripheral:

#uart 2 (gps)
config-pin P9.21 uart
config-pin P9.22 uart

#uart 1
config-pin P9.24 uart
config-pin P9.26 uart

PS, i just pushed an arduplane deb update today too..

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