I'm reading through all of this and I just feel like I am very close. When I try
config-pin P9.21 uart config-pin P9.22 uart I get bash: /sys/devices/platform/ocp/ocp*P9_21_pinmux/state: No such file or directory Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_21_pinmux/state Same thing if I try sudo in front of the command. The P9 output from sudo perl /opt/scripts/device/bone/show-pins.pl | grep P9. is as follows (if it helps) P9.15 16 R13 fast rx down 7 gpio 1.16 ocp/P9_15_pinmux (pinmux_P9_15_default_pin) P9.23 17 V14 fast rx down 7 gpio 1.17 ocp/P9_23_pinmux (pinmux_P9_23_default_pin) P9.14 18 U14 fast rx down 7 gpio 1.18 ocp/P9_14_pinmux (pinmux_P9_14_default_pin) P9.16 19 T14 fast rx down 7 gpio 1.19 ocp/P9_16_pinmux (pinmux_P9_16_default_pin) P9.11 28 T17 fast rx down 6 uart 4 rxd serial@481aa000 (pinmux_bb_uart4_pins) P9.13 29 U17 fast down 6 uart 4 txd serial@481aa000 (pinmux_bb_uart4_pins) P9.12 30 U18 fast rx down 7 gpio 1.28 ocp/P9_12_pinmux (pinmux_P9_12_default_pin) P9.15 34 T13 fast rx up 7 gpio 2.00 P9.22 / spi boot clk 84 A17 fast rx down 1 uart 2 rxd serial@481a6000 (pinmux_bb_uart2_pins) P9.21 / spi boot in 85 B17 fast down 1 uart 2 txd serial@481a6000 (pinmux_bb_uart2_pins) P9.18 / spi boot out 86 B16 fast rx down 7 gpio 0.04 ocp/P9_18_pinmux (pinmux_P9_18_default_pin) P9.17 / spi boot cs 87 A16 fast rx down 7 gpio 0.05 ocp/P9_17_pinmux (pinmux_P9_17_default_pin) P9.42a 89 C18 fast rx down 7 gpio 0.07 ocp/P9_42_pinmux (pinmux_P9_42_default_pin) P9.20 / cape i²c sda 94 D18 fast rx up 3 i²c 2 sda ocp/P9_20_pinmux (pinmux_P9_20_default_pin) P9.19 / cape i²c scl 95 D17 fast rx up 3 i²c 2 scl ocp/P9_19_pinmux (pinmux_P9_19_default_pin) P9.26 96 D16 fast rx down 0 uart 1 rxd serial@48024000 (pinmux_bb_uart1_pins) P9.24 97 D15 fast down 0 uart 1 txd serial@48024000 (pinmux_bb_uart1_pins) P9.31 / hdmi audio clk 100 A13 fast rx down 7 gpio 3.14 ocp/P9_31_pinmux (pinmux_P9_31_default_pin) P9.29 / hdmi audio fs 101 B13 fast rx down 7 gpio 3.15 ocp/P9_29_pinmux (pinmux_P9_29_default_pin) P9.30 102 D12 fast rx down 7 gpio 3.16 ocp/P9_30_pinmux (pinmux_P9_30_default_pin) P9.28 / hdmi audio data 103 C12 fast rx down 7 gpio 3.17 ocp/P9_28_pinmux (pinmux_P9_28_default_pin) P9.42b 104 B12 fast rx down 7 gpio 3.18 ocp/P9_92_pinmux (pinmux_P9_92_default_pin) P9.27 105 C13 fast rx down 7 gpio 3.19 ocp/P9_27_pinmux (pinmux_P9_27_default_pin) P9.41 106 D13 fast rx down 7 gpio 3.20 ocp/P9_91_pinmux (pinmux_P9_91_default_pin) P9.25 / audio osc 107 A14 fast rx down 7 gpio 3.21 ocp/P9_25_pinmux (pinmux_P9_25_default_pin) P9.41 / jtag emu3 109 D14 fast rx down 7 gpio 0.20 ocp/P9_41_pinmux (pinmux_P9_41_default_pin) On Tuesday, June 27, 2017 at 5:39:17 PM UTC-5, 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 > <http://download.ardupilot.org/epub/docs/common-ublox-gps.html>, 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? > -- 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/ddb18e6e-d9fa-45d1-b1ac-04f0f7a56d79%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
