EHS6 Terminal start up problems | Thales IoT Developer Community
March 30, 2015 - 12:51am, 3613 views
Hi...
I have compiled a HelloWorld.jar and jad with the SDK and I'm desperately trying to run it on an EHS6 Terminal.
I have switched off power saving on ASC0, uploaded the midlet and I can run the midlet with SJRA like this (I want to leave SJAM for later):
AT^SJRA="a:/HelloWorld.jar"
OK
However, how can I get stdout redirected to ASC0? Do I need to have two simultaneous connections as follows:
On USB5 I issue the following commands:
AT^SCFG="Userware/Stdout","ASC0"
AT^SJRA="a:/HelloWorld.jar"
...and on ASC0, I see the midlet output?
Is there any simpler way of just running a midlet without needing to have two consoles open? I'm used to the TC65i which seemed a lot simpler in this regard. Apologies if I'm missing something.
many thanks
Liam
OK, why do I want to do this?
1. When developing I like to just copy over a jar and jad and then kick off the midlet with SJRA.
2. In the field some of our engineers occasionally need to manually run the midlet and interact with it via its stdout/stdin command line console. If I need to train them to run up two separate console on two separate com ports they will have a lot of difficulty
Hello,
In EHS6 when you configure System.out on the port this port is reserved for System.out and you can't send any commands on that port.
So you need to have two connections in such a case.
In TC65i you can only run one MIDlet and when it is running the port is also reserved for System.out.
In EHS6 you can run more MIDlets at the same time and when the MIDlets are running you can still issue AT commands to the module.
Regards,
Bartłomiej