You were right the first time, thank you! It is very confusing isn’t it!
On 30 January 2014 at 14:34:07, [email protected] ([email protected]) wrote: On 29/01/14 21:29, Lee Armstrong wrote: > However isn’t it actually pin 31? > > pin 31 (44e1087c) 00000027 pinctrl-single that's pin 31 in the pinmux table, it's not a simple relationship from pinmux number to gpio number on my kernel there's 141 items in that list, but there are only 118 gpios. gpios0,1&2 have 32 pins, gpio 3 only has 22... according to the datasheet anyway... If you look in the kernel source.. arch/arm/mach-omap2/mux34xx.c seems to contain the mapping, although I can't say I understand how to read it > I’m still not getting a PPS input there but am wondering now if the GPS needs > a fix before it even outputs one at all. Probably, most gps modules I've encountered only output pps after you get a fix, the EM406A I'm using is like that. Depends on the module, but you may be able to check with an LED attached to the pps output. My EM406A has a 1uS pps pulse width, so you need a scope to see that. -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
