Sparkfun RTK Reference Station Not Booting

Product is GPS-22429. This is the first power on of the device.

Connected as described in the SparkFun RTK Reference Station Hookup Guide, with GPS antenna, ESP32 antenna, and a FAT32 formatted SD card inserted. Powering the device using the supplied USB wall wart and USB-C cable does not show any activity, either via LEDs or the OLED display. Connecting from PC to the CONFIG UBLOX port shows as a COM port in Windows 10. Ublox U-Center successfully connects to the GPS and shows it with an eventual 3D/DGNSS lock, with NMEA messages enabled. Connecting to the port CONFIG ESP32 shows as a COM port in Windows 10. Using putty, the following is displayed from this port:

rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

configsip: 0, SPIWP:0xee

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00

mode:DIO, clock div:1

load:0x3fff0030,len:1240

load:0x40078000,len:13012

load:0x40080400,len:3648

entry 0x400805f8

ets Jul 29 2019 12:21:46

This exact message repeats at some rate of approximately >5 Hz. A screenshot of the Putty window is attached. Pressing the MODE or RESET buttons does not have any apparent effect.

Are there any additional steps to initializing the device?

My 1st guess would be that maybe there is a power issue that exists outside of the device itself - can you test the cable/wall wart with another device (something else that requires ~5v @ 1a, or 5w) or a multimeter to see if it is browning out for some reason and report back?

Sorry for the hassle! The unit’s firmware is corrupted. Would you mind trying to re-flash the firmware? Instructions are here: https://docs.sparkfun.com/SparkFun_RTK_ … re_update/

If that’s too much of a hassle, or doesn’t fix the problem, we’re happy to get the unit back for inspection. I’m not sure what happened but I’ll pull stock on Tuesday and verify this is not a widespread issue.

@jjetton

Nerk Ahia?

Flashing the firmware seems to have corrected the problem, and the unit seems to be working as it should. Thanks.

Excellent! Sorry again for the bad start.

Just info:

First unit ordered on 6/23 worked great

Two units ordered on 7/3 came with same firmware issue.

Up and running after flashing new firmware to both.

Thanks,

Hi originaldev,

Sincere apologies for the inconvenience. I’m glad you were able to update both units. We are investigating this internally and will take corrective action.

Very best wishes,

Paul

Sorry for the delay on this, the July 4th holiday week was a bit of a black hole.

We found a bad error in our production test and programming script that caused the production firmware to get loaded incorrectly. It’s been fixed, we’ve modified the test procedure to catch issues like this in the future, and we’ve reprogrammed all the units in the warehouse. If anyone else comes across this issue, please try reprogramming then let us know if you continue to have issues.