On Tue, Jun 27, 2017 at 5:39 PM, Timothy Litvin <[email protected]> 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.000000] 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 = 3000000) is a 8250 > > [ 2.505478] console [ttyS0] enabled > > [ 2.506866] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 159, > base_baud = 3000000) is a 8250 > > [ 2.507975] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 160, > base_baud = 3000000) is a 8250 > > [ 2.509094] 481a6000.serial: ttyS3 at MMIO 0x481a6000 (irq = 161, > base_baud = 3000000) is a 8250 > > [ 2.510109] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 162, > base_baud = 3000000) is a 8250 > > [ 2.511416] 481aa000.serial: ttyS5 at MMIO 0x481aa000 (irq = 163, > base_baud = 3000000) 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 [email protected]. 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.
