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 <[email protected]> wrote: > On Thu, Jun 29, 2017 at 5:38 PM, Timothy Litvin <[email protected]> > 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-00002-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 > > > <nothing> > > 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 [email protected]. 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.
