IoT 9DoF Data Logger firmware corrupted?

Hi,

I’ve been running my IoT 9DoF DataLogger (DEV-20594) on the bench with a BME688 Sensor (SEN-19096) connected, on battery power ((PRT-13854), for a week or two, monitoring the data and periodically recharging the battery via the DataLogger’s USB-C port, with a data-capable cable plugged into a port on an iMac, and everything seemed to be working fine until I noticed that the blue LED had stopped flashing. I disconnected everything and checked that the 32MB card was not full. There was just under 151MB used, so there was plenty of space left.

I reconnected the DataLogger by itself, via the USB cable and connected to the serial port using CoolTerm. The data stream was as shown in the attached screenshot. I pressed the RESET button but the data stream simply restarted as before when it was released. Pressing the 0/BOOT button halted the data stream and the message:

rst:0x10 (RTCWDT_RTC_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))

waiting for download

was displayed.

I tried downloading the firmware binary, placing it on the MicroSD card and rebooting the logger in the hope that this would reload the firmware, with no success. The documentation shows how to upgrade the firmware but only using the menu options, with a working device.

My Logger seems to have corrupted firmware, for some unknown reason. Please can you show me where to find out how to reload it, if this is possible?

Thank you.

Maybe try the long press described here https://docs.sparkfun.com/SparkFun_Data … ot-buttons (‘user’ button = ‘0/boot’ button)…any luck?

It sounds like you’ve tried this one already, right? https://docs.sparkfun.com/SparkFun_Data … te-sd-card

Finally, there is a board recovery bin (ver 1.00.01) here https://github.com/sparkfun/SparkFun_Da … r/releases with some info on how to use a workaround to try and get the bin onto the board (you maybe need to specify the python version when sending the command, and/or “python -m” if esptool isn’t executing) :slight_smile:

Thanks TS-Russel,

I tried the sequence of Boot and Reset pushbuttons you suggested and got a new message but no firmware loading activity and no change in the logger after a power cycle.

New message:

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

invalid header: 0x66392e30

invalid header: 0x66392e30

invalid header: 0x66392e30

invalid header: 0x66392e30

invalid header: 0x66392e30

invalid header: 0x66392e30

invalid header: 0x66392e30

invalid header: 0x66392e30

ets Jul 29 2019 12:21:46

rst:0x10 (RTCWDT_RTC_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))

waiting for download

ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))

waiting for download

I’m going to try the third option but my iMac doesn’t seem to have pip installed. I’ll go through the process of installing what’s needed to get esptool working and get back to you.

Thanks again.