Gemalto is now part of the Thales Group, find out more.

You are here

Can't configure Watchdog properly on EHS6 | Thales IoT Developer Community

April 29, 2015 - 11:43am, 2542 views

Hello, I'm a bit green to Gemalto programming, but making good progress. I have an application, where the modem reads serial input and writes the data to a cloud server. We have been using previously a Cinterion mc88i which had EGS5 Java module. There we used Java commands like Watchdog.start(300) and watchdog.kick().

Now Ecliple Java ME says that for EHS6 the type Watchdog is deprecated, but Watchdog2 will not work in the same manner.

Then I can see there is also a hardware watchdog, which seems like a completely different system. I am able to activate it through AT^SCFG="Userware/Watchdog","1" but I am unsure does this affect the Java watchdog or the hardware one.

My specific questions:

1) How can I use the Java watchdog2?

2) Reading through EHSxT HW desc. V04 I can see there are many parameters defining watchdog behaviour, but reading from 8.3.1.1 onwards it seems that all functionalities are disabled by default (like RST_REP, RST_UART etc.). So if I activate the watchdog through AT^SCFG="Userware/Watchdog","1" then what does the watchdog DO since all features are disabled by default?

3) I would like to configure the hardware watchdog from my Java midlet, but can't manage to communicate with the hw watchdog unit. Also there are no examples online that I could find. Also, all AT^SSPI commands return an ERROR in the usb console, so I am unable to even try passing commands through the i2c bus.

I hope you can clarify the case with two separate (?) watchdogs and how they can be used to reboot the device in the case of jamming. Thank you all.