Hi everyone,
That was a good idea Markus. Have dropped "Debug Server delay (ms)" to
1000 and now the whole start up takes about 20 secs. Still slow but a
big improvement.
So I can now get both the Sun WTK and Microemu to start and load my app.
Initially I used the eclipse Debug dialog 'Midlet' taboption
'Executable' set to "Midlet" and put in my midlet class name. However,
as soon as startApp():-
public void startApp() throws MIDletStateChangeException {
DImainThread = new DImain(); //a sub-class of Thread
DImainThread.start();
}
returns the whole midlet terminates despit the fact that the
'DImainThread' has just started and continues to run. I have found this
characteristic with both emulators (Sun's and microemu).
So I tried packageing the midlet and launching via the .jad file. (the
JAD URL option in the 'Midlet' tab)
Working! Now I can set break points in my DImainThread code and step
through that to see what's going on.
So more progress.
BUT now I cannot open a serial port (I really need this for my app). I have,
String strCOM = "comm:com0;blocking=on;baudrate=115200";
asc0 = (CommConnection)Connector.open(strCOM);
but it throws,
java.lang.IllegalArgumentException, Illegal device name
(Note: com1 has the same effect)
I get similar effects with microemu.
Anyone successfully used the serial port from within an emulator? any
idea what I might be doing wrong?
Many thanks,
John
Markus Sinner wrote:
>Take a look at the eclipse-settings, J2ME-category. There is a "Debug
>Server delay (ms)", maybe that value is much to high.
>
>John Pote schrieb:
>
>
>>Markus,
>>Turned off antivirus and firewall. From a command prompt the SUN WTK
>>does indeed start up in 5 secs. From within eclipse it is different.
>>click app name in eclipse's debug menu,
>>After 5 secs emulator skin is shown and menu items seem to be fully
>>working. Eclipse console shows the following (and "launching appname"
>>progress indicator shows 87% done):-
>> Connecting to 127.0.0.1 on port 2800
>> Waiting for debugger on port 1271
>> Running with storage root DefaultGrayPhone
>> Waiting for KVM...
>> Running with locale: English_United Kingdom.1252
>> Running in the identified_third_party security domain
>> Connected to KVM
>>
>>Now it takes another 55 to 60 secs to receive the debug connection when
>>the console shows:-
>> Connection received.
>>A further 10 to 15 secs are now needed for the eclipse debug perspective
>>to open, show the various app threads and run the app.
>>
>>If I close the emulator skin during the 55 sec period eclipse reports in
>>the console:
>>Warning: Could not start new emulator process:
>> java.lang.NullPointerException
>>DebuggerListener: socket closed
>>
>>but continues to wait for the full period when it reports a "Problem
>>occured" dialog error with the following detail msg:-
>> Couldn't connect to virtual machine
>> Connection refused: connect
>>
>>Anyone any thoughts on this?
>>
>>Thanks,
>>John
>>
>>
>>Markus Sinner wrote:
>>
>>
>>
>>>Hello Pote,
>>>
>>>I cannot acknowlede your experience. My SUN-WTK-Emulator starts in
>>>about 5 Seconds or less. Maybe a antivirus-software, that makes it
>>>hanging?
>>>
>>>:-)
>>>Markus
>>>
>>>John Pote schrieb:
>>>
>>>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Eclipseme-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/eclipseme-users
