Aaaaaaand. 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 <capnt...@gmail.com > <javascript:>> 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 <capnt...@gmail.com> >> 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.
