Installed BerryGPS/IMU but not receiving any data

Forums Technical Support for BerryGPS and BerryGPS-IMU Installed BerryGPS/IMU but not receiving any data

Tagged: 

This topic contains 10 replies, has 4 voices, and was last updated by  Damon 2 months, 3 weeks ago.

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #6771

    Paul Ingram
    Participant

    Hello Mike,

    I have installed the BerryGPS/IMU according to your instructions and apart from some ssh weirdness after disabling console/enabling serial, I have the fix light flashing on the GPS.

    I installed minicom, screen & gpsd to test, but I am not seeing any data using cat, minicom, screen, gpsmon or cgps.

    Here is a quick dmesg dump…

    and a listing of the devices…

    root@raspberrypi:~# ls -lasih /dev/ttyS* /dev/ttyAMA* /dev/serial*
    8329 0 lrwxrwxrwx 1 root root 5 Aug 5 07:19 /dev/serial0 -> ttyS0
    7536 0 lrwxrwxrwx 1 root root 7 Aug 5 07:19 /dev/serial1 -> ttyAMA0
    1157 0 crw-rw—- 1 root dialout 204, 64 Aug 5 07:42 /dev/ttyAMA0
    1158 0 crw–w—- 1 root tty 4, 64 Aug 5 09:06 /dev/ttyS0

    Any ideas please?

    • This topic was modified 3 months, 2 weeks ago by  Paul Ingram.
    #6774

    Mark Williams
    Keymaster

    if you use “gpspipe -r” did you see any data?

    can you kill gpsd and then do a cat on /dev/serial0

    sudo killall gpsd
    cat/dev/serial0

    Do you see anything with cat now?

    Have you tried on another Raspberry Pi?

    Mark --OzzMaker.com --
    BerryIMU --
    PiScreen - 3.5" TFT for the Rasspberry Pi

    #6781

    Paul Ingram
    Participant

    Hello Mark,

    Thanks for your reply. Here are my answers…

    root@raspberrypi:/etc# systemctl start gpsd
    root@raspberrypi:/etc# gpspipe -r
    {"class":"VERSION","release":"3.11","rev":"3.11-3","proto_major":3,"proto_minor":9}
    {"class":"DEVICES","devices":[]}
    {"class":"WATCH","enable":true,"json":false,"nmea":true,"raw":0,"scaled":false,"timing":false,"split24":false,"pps":false}

    Then silence.

    root@raspberrypi:/etc# killall gpsd
    root@raspberrypi:~# cat /dev/serial0

    … no output

    I only have one Pi so I can’t test another. The one I have seems to run raspbian pretty well.

    Due to operator failure with BBcodes, the dmesg output wasn’t listed in my original post (although it was there) so here it is again…

    root@raspberrypi:/etc# dmesg | grep tty
    [    0.000000] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwidth=800 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
    [    0.000345] console [tty1] enabled
    [    0.756219] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
    [    0.757704] console [ttyS0] disabled
    [    0.757730] 3f215040.serial: ttyS0 at MMIO 0x0 (irq = 220, base_baud = 31250000) is a 16550
    [    0.764303] console [ttyS0] enabled
    [    1.799058] systemd[1]: Expecting device dev-ttyS0.device...
    #6783

    Mark Williams
    Keymaster

    Hi, that dmesg output looks strange, it shows the that serial is first disabled for the console and then it is enabled.

    please show the output of
    cat /boot/cmdline.txt
    and
    cat /boot/config.tct

    Mark --OzzMaker.com --
    BerryIMU --
    PiScreen - 3.5" TFT for the Rasspberry Pi

    #6786

    Paul Ingram
    Participant

    Hello Mark,

    Here we go – and no /boot/config.tct.

    root@raspberrypi:~# cat /boot/cmdline.txt
    dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
    root@raspberrypi:~# cat /boot/config.tct
    cat: /boot/config.tct: No such file or directory
    #6789

    Mark Williams
    Keymaster

    I am so sorry… I made a typo, it should have been /boot/config.txt

    Anyway, delete console=serial0,115200 from /boot/cmdline.txt and reboot. Try cat /dev/serial0 again.

    Mark --OzzMaker.com --
    BerryIMU --
    PiScreen - 3.5" TFT for the Rasspberry Pi

    #6791

    Paul Ingram
    Participant

    Hello Mark,

    Removed console=serial0,115200 from /boot/cmdline.txt and rebooted, still silence from the

    cat /dev/serial0

     

    #6792

    Paul Ingram
    Participant

    I might burn a new image & start from scratch with a fresh Raspbian on my Pi 3 and see how I get on – I don’t want to waste your time.

    I’ll let you know how I get on…

    #6805

    Vibhor
    Participant

    I am facing exact same issue “cat /dev/serial0” gives no output. Did you found what was the issue?

    #6820

    Damon
    Participant

    Hey Mark.

    I am having the same issues.   I cannot get any output on a Raspberry Pi 3 with BerryGPS.

    Here is my output:

    pi@raspi2:~ $ dmesg | grep tty
    [ 0.000000] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=e261b53b-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
    [ 0.000345] console [tty1] enabled
    [ 0.820557] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
    [ 0.822204] 3f215040.serial: ttyS0 at MMIO 0x0 (irq = 220, base_baud = 31250000) is a 16550
    pi@raspi2:~ $ cat /dev/ttyS0
    ^C
    pi@raspi2:~ $ cat /dev/ttyAMA0
    pi@raspi2:~ $ cat /dev/ttyS0
    ^C
    pi@raspi2:~ $ cat /dev/serial0
    ^C
    pi@raspi2:~ $ cat /boot/cmdline.txt
    dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=e261b53b-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
    pi@raspi2:~ $

    I really don’t have an option to disable the on-board Bluetooth to free up ttyAMA0 as suggested in the raspberry forum on this issue.

    I am really hoping you can help me out on this.

    Cheers mate!

    • This reply was modified 2 months, 3 weeks ago by  Damon.
    #6822

    Damon
    Participant

    Problem solved.
    With a little extra help from:  Spellfoundry and the fact that I didn’t follow instructions on wiring correctly and had Tx/Rx reversed.  (Old eyes)

    It is now running.  Yippie!!!

Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.

Blip, blop, bloop…