Javelin Stamp IDE with Wine under linux
alyndaker
Posts: 1
Is anyone running the IDE for the Javelin Stamp under wine? I have read in a couple of places that it could be done. The program itself works up till communication with the controller then returns the error "[noparse][[/noparse] Error IDE-052] Incompatible firmware revision ($f). It works correctly under windows so the problem is clearly with wine/linux. I would appreciate any help.
Comments
Try Project->Identify and Project->Test connection
several times. The firmware revision must be $50.
Disable the·serial port buffer if still no success.
Try the dos downloader located here
http://groups.yahoo.com/group/JavelinCode/files/JavelinDirect/
I don't know about wine, but I successfully programmed javelins
from vmware (running win98) on a xp host system (PII 450 MHz)
regards peter
·
At least that's my theory. Just hope it works. Then who needs wine anyways. LAW (linux ain't windoz).
Any help would be appreciated.
JIDE can now at least find the javelin with the correct firmware version. Identify works, but uploading programs to the javelin does not work. I get the following in the JIDE message bar:
[noparse][[/noparse]Error IDE-0022] Error reading from the serial port (timeout).
Also, wine kicks out the following messages:
fixme[noparse]:comm:[/noparse]set_queue_size insize 2048 outsize 2048 unimplemented stub
regards peter
I am also running wine as "win98" for the version. Also, I have the following installed:
DCOM95
Windows Installer
Internet Explorer 6 (for the help file support)
Javelin IDE
http://groups.yahoo.com/group/JavelinCode/files/JavelinDirect/
Unfortunately I don't have a linux executable.
You can try run my adapted version 1.2 from wine.
regards peter
I also tried the original (1.0) version, but this did not work either.
This is disappointing, really. Linux and Java are a natural fit for one another. Perhaps I'll try my hand at debugging the timeout problem wine is having.
the --path option.
Where is your file located, what is the path to javelin lib folder?
What does your commandline look like?
regards peter
·
const int kResetWait = 10000; // Time taken for SX to reset.
const int kAckWait = 10000; // (doubled 5000) The amount of time (in milliseconds) to wait for acknowledgement.
const int kResetCharWait = 3; // The amount of time to wait before sending first char after a reset.
const int kProgramWait = 4000; // (doubled 2000) The amount of time (in milliseconds) to wait for acknowledgement when programming.
const int kStepWait = 40000; // (doubled 20000) The amount of time (in milliseconds) to wait for acknowledgement when stepping.
I doubled some wait times in version 1.3 (attached) that may do the trick.
regards peter
Post Edited (Peter Verkaik) : 7/2/2006 10:22:34 AM GMT
Will this let you do debugging too (other than std out)? Or do you need JIDE for that?
on the screen. Debugging as in debugging with the IDE is not available.
After all, javelindirect is merely for creating the jemfile and downloading
it to the javelin.
You can use JideWinTerminal that allows you to send and receive messages
from the javelin. You can even send files and log the messages to a file.
http://groups.yahoo.com/group/JavelinCode/files/JideTerm/
regards peter
·
[noparse][[/noparse]Error IDE-0022] Error reading from the serial port (timeout).
That said, this is actually good progess. Since now I have the source for both sides (wine and JavelinDirect), I should be able to isolate the problem in wine. It looks to be potentially a timing issue, because if I crank up the debug features in wine, I get less far in communicating with the Javelin.
Thanks for your help. I'll keep you posted on any progress I make.
Any ideas?
JavelinDirect_1_2 folder.
I updated the zip here:
http://groups.yahoo.com/group/JavelinCode/files/JavelinDirect/
Extract in the projects folder of cbuilder.
regards peter
·
That said, I should be able to isolate the problem now. Thanks so much for all your help.
Interestingly, the javelin seems to do a reset, and my simple HelloWorld example returns it's string back. I attempted to add so diagnostics to wine, to figure our where it is getting lost, but have not been able to pinpoint the problem yet.