Created Sat, 29 Dec 2012 18:30:40 +0000 by cedmondson
Sat, 29 Dec 2012 18:30:40 +0000
Ok, I also posted this at arduino.cc but I might get better help here.
I was successfully using MPIDE 022 for a couple of weeks with my MAX32 board, doing some serial port routines. I needed to add a touchscreen, so ordered and ITead 5.0 inch screen, and their MEGA shield. Looking at the specs for the shield, and Henneth's documentation on UTFT, I realized that it might work better with a MEGA 2560, so I ordered one of those as well.
Went to do some work on the MEGA, and I couldn't communicate with it. Was getting device errors of "device failed to start - Code 10" which I was unable to resolve. Tried the same board on my wife's machine, and it wouldn't even install the drivers. Apparently a bad board, so back to the MAX32...
Go to start MPIDE, and now I have the dreaded launch4j errors. After a couple of hours of research, I have tried (in no particular order):
renamed the MPIDE folder in applications data - no luck turned off my wifi (I don't have bluetooth) - no joy downloaded a new rxtxserial.dll, only to find out that MPIDE doesn't use this file, it has rxtxComm.dll. No updated version for it out there.
And, probably several other things that I have forgotten. Anyone else have any ideas what to try next? I am convinced this project is cursed...
Sat, 29 Dec 2012 22:38:19 +0000
Ok, I found the problem!
During all my troubleshooting for the MEGA comms problem, I had accidentally unzipped a new driver download in my MPIDE directory. When I was cleaning that up, I also got the rxtxSerial.dll that was there. I unzipped the original MPIDE download into a new directory, and saw the files there. I copied them back to my original install directory, and I am now back in business!
Mon, 14 Jan 2013 17:32:11 +0000
What is the dreaded launch4j error?
Mon, 14 Jan 2013 17:40:27 +0000
Jacob, There are several threads across the net on the problem. The IDE tries to start up, and then gives you a lauch4j error, apparently as the java engine tries to start up a USB serial link to the board. There are various remedies out there, as I mentioned, most of which are probably out of date and fixed in later releases. In mine, I just accidentally deleted one of the necessary file.