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

You are here

Community > Forum > Cellular Hardware > Debug RAS connection is not installed! Please start...

Debug RAS connection is not installed! Please start Cinterion CMTK setup in maintenance mode and select "Repair" and then repair does not repair anything. | Thales IoT Developer Community

Like
0
11
fongang's picture
fongang

October 11, 2014 - 4:17am, 13175 views

Hello, While trying to run examples, I get "Debug RAS connection is not installed! Please start Cinterion CMTK setup in maintenance mode and select "Repair". " 95% of the time. It takes forever to run repair and then "repair" "scans the disks" to find installations (which it never remembers) and concludes that the problem is fixed, but then I try to run the project from eclipse and it fails again with the same error message. This is a terrible experience! I accessed it 8 hours ago and been trying in vain for 6 hours. Please provide step by step to improve reliability in accessing the Concept Board from the bundled eclipse install in windows 8.
11
Comment
Log in or register to post comments
1 - 10 of 11 Comments

Pages

Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
Oct 13 2014 - 1:30pm
Hello, according to Java Usersguide Windows 8 is not supported - you're using it on your own risk. Officially supported versions are: - Windows XP, - Windows Vista - Windows 7 Please try with one of the above and inform if the issue persists. Regards Jedrzej
fongang's picture
fongang
Oct 13 2014 - 5:52pm
I am aware that windows 8 is not officially supported. But doubt this is the problem. Most software that works well with Windows 7 also works fine in windows 8. But you are right: I am in an unsupported configuration and will need to try with a supported configuration. Will try with windows XP service pack 3 and report here. Still think there is a need for a reliable list of "Things to check when RAS connection fails".
fongang's picture
fongang
Oct 13 2014 - 7:45pm
Hello, I get the same behavior under Windows XP SP3. the exact error is: Using USB port COM6. Switching on module... Failed to switch on module! Passing control to external device emulator... *** Error *** Device "IMP_NG_EHS5_REMOTE1" not registered! End of debug session. Emulator is closed! Note that during the "repair" process there was a message about using port COM3 instead.
Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
Oct 15 2014 - 7:14pm
Hello, Please ensure that COM6 is not blocked by another program (i.e. some terminal program you might be using to communicate with the module). To be sure that the debugger is using the proper port check in Windows device manager under Modems what port number the Java Debug Modem is using. When you start maintenance mode and repair be sure that OJMEE Device Manager is not running (it is started by the emulator and you can see it's icon in the Windows system tray near the clock). Please import one of the example projects as described in the Java User's Guide document to be sure that your project's configuration is correct. If you still have problems it might be better to uninstall instead of running in maintenance mode, restart the computer and install again. To be sure that your firewall is not blocking the connection turn it off for test. Regards Jedrzej
fongang's picture
fongang
Oct 16 2014 - 9:44am
Hello Jedrzej. I am no longer interested in using the built in debug mechanism: I spent too much time trying this. I will instead look for ways to load the applet manually: accessing COM ports manually using various tools never fails. I have an applet copied to the flash file system, I install and start the applet, but it does not start. What could be wrong? Here is the output: at^sjam=4 ^SJAM: "a:/JRC-1.50.11.jad","Java Remote Control MIDlet Suite","Cinterion","1.50.11",1,669201,0 OK AT^SJAM=0,"a:/AtCmdDemo.jad","" OK AT^SJAM=1,"a:/AtCmdDemo.jad","" OK at^sjam=4 ^SJAM: "a:/AtCmdDemo.jad","BattleTank","Concurrent Systems Pty","1.0.0",1,47695,0 ^SJAM: "a:/JRC-1.50.11.jad","Java Remote Control MIDlet Suite","Cinterion","1.50.11",1,669201,0 OK at^sjam=5 ^SJAM: "a:/JRC-1.50.11.jad","Java Remote Control MIDlet Suite","Cinterion","1.50.11",1 OK EDIT: It works now. Had an issue with the autostart order clashing with the order of JRC applet. Funny that it did not complain though... So what works for me is: - Copy jad and jar files using the moduledownloader.py from ALOPEZ - Activate manually using a sequence of AT^SJAM Commands
Jędrzej Gemalto Moderator's picture
Jędrzej Gemalto...
Oct 16 2014 - 5:21pm
Hello, It's great that your MIDlet is finally working! You can also use MES (Module Exchange Suite) to transfer MIDlets or any other files to module's file system. Command line tools are also included (please find details in Java User’s Guide). If you mean the order that at^sjam=4 command is using, it does not mean that the MIDlets will be started in this order. In the Java User's Guide it's written that for MIDlets with the same level the start order is not defined. And you can assign 0-5 values to Oracle-MIDlet-Autostart in the jad file where 0 means no autostart. JRC has the highest autostart priority equal 1. Please consider setting your MIDlet autostart ordering value to 2 especially if your MIDlet uses AT command interface. If you experienced some order clashing issue and need our further investigation, please deliver AT command and Java stdout log. Please also verify if some exceptions are thrown. Regards Jedrzej
fongang's picture
fongang
Oct 16 2014 - 7:00pm
I meant the Oracle-MIDlet-Autostart was set to 1 in my applet's jad file. After I set it to 2 it worked. Also, I redirected System.out to specific USB port and I am able to debug and catch issues.
marcmelita's picture
marcmelita
Nov 10 2014 - 11:57am

Hi, 

I'm tryng to run some MIDlet on my Cinterion Concept Board. I'm using Eclipse Juno as IDE on Windows 7 (32bit machine).

Once I've created the package, and copy & paste the Jar and Jad files to the module's file system, I realized that file properties (of both files) in the module, in terms of creation date, are completely different from the original (the files created by the IDE, located in the Eclipse Workspace).
Since I'm not able anymore to install the files on the module (using the hyperterminal the command AT^SJAM=0,"a:/HelloWorld.jad","" return ERROR), do you think it could be related to the date/properties mismatch?

How do I could set/fix the date/time in the module?

Tanks a lot

Marcello 

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Nov 10 2014 - 2:59pm

Hi Marcello ,

The date in file properties is connected with the date actually set in the module. This date is reset when you cut off the power and you can set it by the AT+CCLK command. 

This is not the cause of your problem. If you get error while installing the MIDlet it usually means some problem with MIDlet itself. You can try to issue AT+CMEE=2 command before MIDlet installation and maybe you'll get more information. But first of all try to make sure that the MIDlet you install is properly built.

Regards,

Bartłomiej

hmjarrett's picture
hmjarrett
May 10 2016 - 4:56pm

Bartłomiej, are you still there?

1 - 10 of 11 Comments

Pages