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

You are here

BGS5 watchdog trouble | Thales IoT Developer Community

July 1, 2015 - 9:07am, 4169 views

Hello,

I'm having some trouble getting the watchdog functionality to work on my BGS5T terminal.  I've followed the instructions in the manual carefully but after activating the watchdog for "GPIO reset" I cannot seem to keep it from rebooting even when toggling the GPIO signal regularly.

Here's my module info:

ATI

Cinterion

BGS5

REVISION 01.100

These are the commands I used to configure the watchdog, using ASC0 at 1200baud:

WD=MIN_START_TIME,600000,6

WD=RST_GPIO,600000,6

WD=ALWAYS_ON,60000,6

WD=ON,1,1

All commands executed successfully (the green LED flashed twice after each command).

In the "Hardware Interface Description" document (EHSxT_BGS5T_HID_v02), section 8.3.1.5 "GPIO Reset", it states that "The module has to be active on the WD_RETRIG signal by toggling the GPIO22 module output within the specified time period. Otherwise the watchdog will reset the module.".  So, in my Java MIDlet, first I open and initialize GPIO22 as output with this line of code:

AT^SCPIN=1,21,1,0

Then I toggle the GPIO22 output on and off every 10 seconds with this code:

AT^SSIO=21,1

Thread.sleep(1000)

AT^SSIO=21,0

However, the terminal always reboots after 10 minutes (= 600000ms, as specified in the WD=RST_GPIO command).

Later I discovered that there is a newer version of the "Hardware Description" document (EHSxT_BGS5T_HID_v06) which, in the same section 8.3.1.5 "GPIO Reset", says that GPIO8 must be toggled, not GPIO22.  I tried the same code as above but with GPIO8, and I get the same result.  So, my questions are:

1.  Which GPIO is the correct one?

2.  How can I toggle the GPIO correctly to keep the watchdog from rebooting?

I would appreciate any suggestions for resolving this issue.  Thank you.