On Sat, Jul 1, 2017 at 2:34 AM Timothy Litvin <[email protected]> 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.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.002905] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0' > [ 2.488082] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158, > base_baud = 3000000) is a 8250 > [ 2.501480] console [ttyS0] enabled > [ 2.502849] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 159, > base_baud = 3000000) is a 8250 > [ 2.503933] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 160, > base_baud = 3000000) is a 8250 > [ 2.505034] 481a6000.serial: ttyS3 at MMIO 0x481a6000 (irq = 161, > base_baud = 3000000) is a 8250 > [ 2.506066] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 162, > base_baud = 3000000) is a 8250 > [ 2.507345] 481aa000.serial: ttyS5 at MMIO 0x481aa000 (irq = 163, > base_baud = 3000000) 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? > [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 <[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%2BT6QPnD49ntUCM7Bu%2BE8s3fiA%3D4a%3D4d1nW9aePLWZf1PMC8Sg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
