Freematics Forum

Hello,

I tested FreeMatics One + Model B last year and everything worked great - information could upload to Mini server in cloud.
The device was offline and kept in a dry place last year. These few days, I need to re-visit this project, however, when running the telelogger,
, the FreeMatics One + Model B can not connect any WIFI(tried different router/AP Netgear, 2 models of TP link, Dlink , Synology, etc) and
doubt if the wifi model inside FreeMatics One + Model B is died. In order to further test it, loads different codes
under firmware_v5 and firmware_v4(with a mistake) and finally screw up the pre-build binary in FreeMatics One + Model B
. It shows below error everytime when boot up :

Memory dump at 0x400ed8b4: ffffffff ffffffff ffffffff
Guru Meditation ErrGuru Meditation Error: Core 1 panic'ed (Unhandled debug exception)
Debug exception reason: Stack canary watchpoint triggered (loopTask)
Guru Meditation Error: Core 1 panic'ed (Interrupt wdt timeout on CPU1)
Guru Meditation Error: Core 1 panic'ed (Interrupt wdt timeout on CPU1)
Guru Meditation Error: Core 1 panic'ed (Interrupt wdt timeout o


I need your help to see :

a. if can give me instruction to restore the factory binary to FreeMatics One + Model B.
b. how to check if WIFI module inside FreeMatics One + Model B is damaged or I need to order another new one.

Thank you for your help.

Best regards,

Victor

G'day Victor,

I had the same issue and seemed to fix it by doing the following.

1. Disconnect the device from OBD in car and from the USB connection to your computer (essentially powering it off).
2. Connect to your computer
3. Erase the flash using esptool.py, example command below (note, you need to change COM4 to match the com port of the device on your computer): 4. Re-load the telelogger firmware (I used Arduino IDE to do this, but you should be able to use Freematics builder).

If you don't have esptool.py on your computer, you can follow the instructions here https://cyberblogspot.com/how-to-instal ... indows-10/

Cheers

Matt

Hi Matt,

After the reset and reload the telelogger firmware, everything works fine.

Thank you very much for your help, Matt.


Thank you,

Victor

My pleasure Victor!

Enjoy