Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
  • #7268
    Joseph Grey

    I just purchased a BerryGPS-IMU.  Followed the instructions (I think) to get it all hooked up.  It seems completely dead.  No lights, no returned data.  Nothing.  Anything I should do to test it?


    Joseph Grey

    I tested and it does have three volts going to the board.  Should it have any LEDs or anything?  This board seems completely dead.

    Mark Williams

    The LEDs will only light up once there is a GPS fix.

    Can you see the IMU i2c addresses?
    Have you configured the serial correctly?

    Mark --

    Joseph Grey

    I followed the setup guide on this page:

    But there was no mention of how to look for the i2c address.  Could you point me to the page?


    Joseph Grey

    Oh, one other thing that might make a difference, I am on a Raspberry Pi 3.

    And one other question.  I have soldered on the header and that is where I have the Pi connected.  But I really expected I would be able to read three volts at the center “break out” point.  I get zero volts here even though I have confirmed I have voltage going into the header.


    Joseph Grey

    Ok, it looks like they do show up.  The top is with the Berry unplugged and once I plug it in the addresses do show up.


    Mark Williams

    doesn’t matter what Pi you have, they all work the same.

    As you see the i2c addresses, this shows me that the IMU is working.

    Have you tested any of the code for the IMU.

    Regarding the GPS, have you setup the serial interface correctly? Can you show me the contents of /boot/config.txt

    Mark --

    Joseph Grey

    I really think this unit is defective in some way.  I couldn’t get any further with the GPS stuff so thinking I had done something wrong I did a fresh install of Raspbian Stretch and followed the instructions on this site to get it talking to the Berry.  Now there is nothing.  No i2c addresses showing up either.  How can I go about getting an exchange for a working unit?


    Mark Williams

    I am happy to exchange your unit.. but first I want to make sure there is a problem with the one you have.
    We test every single board before we send them.

    Please show me the output of these commands;

    cat /boot/config.txt

    cat /boot/cmdline.txt

    cat /etc/default/gpsd

    dmesg | grep tty

    ls -l /dev/serial*

    ls -l /dev/i2c*

    cat /etc/modules

    ps ax | grep gpsd

    gpsmon -r

    Mark --

    Joseph Grey

    pi@raspberrypi:~ $ cat /boot/config.txt
    # For more options and information see
    # Some settings may impact device functionality. See link above for details

    # uncomment if you get no picture on HDMI for a default “safe” mode

    # uncomment this if your display has a black border of unused pixels visible
    # and your display can output without overscan

    # uncomment the following to adjust overscan. Use positive numbers if console
    # goes off screen, and negative if there is too much border

    # uncomment to force a console size. By default it will be display’s size minus
    # overscan.

    # uncomment if hdmi display is not detected and composite is being output

    # uncomment to force a specific HDMI mode (this will force VGA)

    # uncomment to force a HDMI mode rather than DVI. This can make audio work in
    # DMT (computer monitor) modes

    # uncomment to increase signal to HDMI, if you have interference, blanking, or
    # no display

    # uncomment for composite PAL

    #uncomment to overclock the arm. 700 MHz is the default.

    # Uncomment some or all of these to enable the optional hardware interfaces

    # Uncomment this to enable the lirc-rpi module

    # Additional overlays and parameters are documented /boot/overlays/README

    # Enable audio (loads snd_bcm2835)

    # Added by Joseph Grey

    pi@raspberrypi:~ $ cat /boot/cmdline.txt
    dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=db09dfc6-02 rootfstype=ext4 elevator=deadline rootwait quiet splash plymouth.ignore-serial-consoles
    pi@raspberrypi:~ $ cat /etc/default/gpsd
    # Default settings for the gpsd init script and the hotplug wrapper.

    # Start the gpsd daemon automatically at boot time

    # Use USB hotplugging to add new USB devices automatically to the daemon

    # Devices gpsd should collect to at boot time.
    # They need to be read/writeable, either by user gpsd or the group dialout.

    # Other options you want to pass to gpsd

    pi@raspberrypi:~ $ 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=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=db09dfc6-02 rootfstype=ext4 elevator=deadline rootwait quiet splash plymouth.ignore-serial-consoles
    [ 0.000284] console [tty1] enabled
    [ 0.670448] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
    [ 0.672007] 3f215040.serial: ttyS0 at MMIO 0x0 (irq = 166, base_baud = 31250000) is a 16550

    pi@raspberrypi:~ $ ls -l /dev/serial*
    lrwxrwxrwx 1 root root 5 May 22 20:15 /dev/serial0 -> ttyS0
    lrwxrwxrwx 1 root root 7 May 22 20:15 /dev/serial1 -> ttyAMA0

    pi@raspberrypi:~ $ ls -l /deve/i2c*
    ls: cannot access ‘/deve/i2c*’: No such file or directory

    pi@raspberrypi:~ $ ls -l /dev/i2c*
    crw-rw—- 1 root i2c 89, 1 May 22 20:15 /dev/i2c-1

    pi@raspberrypi:~ $ cat /etc/modules
    # /etc/modules: kernel modules to load at boot time.
    # This file contains the names of kernel modules that should be loaded
    # at boot time, one per line. Lines beginning with “#” are ignored.


    pi@raspberrypi:~ $ ps ax | grep gpsd
    22090 ? S<s 0:00 /usr/sbin/gpsd -N /dev/serial0
    29642 pts/0 S+ 0:00 grep –color=auto gpsd

    pi@raspberrypi:~ $ gpsmon -r
    gpsmon: invalid option — ‘r’
    usage: gpsmon [-?hVn] [-l logfile] [-D debuglevel] [-t type] [server[:port:[device]]]
    pi@raspberrypi:~ $

    Mark Williams

    thanks… two last commands.

    gpspipe -r

    i2cdetect -y 1

    I assume you have it connected by placing it directly on top of the Pi GPIOs?
    Can you send me a closeup of how you soldered the female header.

    And lastly, please send your order receipt to sales<@>, in case we cant get this one going.

    Mark --

    Joseph Grey

    pi@raspberrypi:~ $ /usr/bin/gpspipe -r

    pi@raspberrypi:~ $ i2cdetect -y 1
    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: — — — — — — — — — — — — —
    10: — — — — — — — — — — — — — — — —
    20: — — — — — — — — — — — — — — — —
    30: — — — — — — — — — — — — — — — —
    40: — — — — — — — — — — — — — — — —
    50: — — — — — — — — — — — — — — — —
    60: — — — — — — — — — — — — — — — —
    70: — — — — — — — —
    pi@raspberrypi:~ $

    Mark Williams

    I see the problem

    Did you mean to solder the header on the incorrect side?

    Anyway… it will still work if cabled correctly. Looking at the image, this isn’t the case.


    In the image below, the top yellow square describes the pinouts for the spare pins in the second yellow square. It looks like you have used these to reference the pins in the female header, which means ground isn’t connected properly and nothing would work.

    The pins on the female header match up to the first 10 pins on the Raspberry Pi.

    Blue arrow below needs to connected to RXD on the Pi… this is physical pin 10
    The red arrow below shows where GND is connected.  You can use the Pi physical pin 6

    The purple jumper should connected to 3.3v  (pin 1)
    Green should connect to SDA (pin 3)
    Yellow should connect to SCL (pin5)



    Mark --

Viewing 13 posts - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.

Blip, blop, bloop…