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

You are here

EHS6: Update to Firmware 03.001 breaks Java security | Thales IoT Developer Community

June 17, 2015 - 11:26am, 2826 views

Hello,

we are currently updating a bunch of EHS6 terminals from

  REVISION 02.000, A-REVISION 00.000.15

to 

  REVISION 03.001, A-REVISION 00.000.14

and face problems concerning Java security with two of the devices. Before updating, all devices had active Java security and disabled MES tools/OBEX, i.e.

  AT^SJMSEC?

gave

  ^SJMSEC: 2,0,0,0

After the update, 2 of 5 devices permanently deny AT^SJMSEC commands:

 AT^SJMSEC?

 ERROR

 AT+CMEE=2

 OK

 AT^SJMSEC?

 +CME ERROR: Unknown

Trying to re-activate MES tools fails, too:

 AT^SJMSEC="cmd","23010[...redacted...]F2F9AE"

 +CME ERROR: Unknown

I also have a third device where Java security is broken, but I somehow managed to break this one without updating to release 3 firmware. While I was experimenting how to setup Java security it told me the "keystore state" (first component of answer) was "0":

AT^SJMSEC?

^SJMSEC: 0,0,1,0

According to the AT command document, this keystore state means "No keystore installed. Internal **** dedicated for manufacturer." I tried to fix this with an update to release 3 firmware and ended up with exactly the same behaviour as described above.

I have 15 more devices sitting on my desk waiting for an update and would prefer not to break them. So any help is highly appreciated. 

Best regards,

  Ingo