LeafLabs Garden » Topic: Program upload problems

LeafLabs Garden » Topic: Program upload problems http://forums.leaflabs.com/topic.php?id=74192 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:18:17 +0000 http://bbpress.org/?v=1.0.2 <![CDATA[Search]]> q http://forums.leaflabs.com/search.php gbulmer on "Program upload problems" http://forums.leaflabs.com/topic.php?id=74192#post-105111 Tue, 24 Dec 2013 14:49:28 +0000 gbulmer 105111@http://forums.leaflabs.com/ samtal - My suggestion looks wrong. I apologise. It seemed such an elegant explanation, if both boards still had the same problem. It's odd you can't find a plausible .jar file to contain RXTXPort, but not worth looking. So, the errant board: 1. runs the perviously uploaded program 2. won't talk to the host PC as a USB serial device 3. can't be contacted by the IDE to upload a new program Is that all correct? Further, the errant board: 4. can't be put into 'Perpetual bootloader mode', or can be, but the IDE still can't upload a program. Which is it? It looks like some part of the USB is broken. It is most likely electrical if the boards were identical. Have you tried a couple of different USB leads to eliminate that as a possible cause? One of the lines, USBDP, or USB D+, should get pulled up to about 3.3V if everything at the lowest levels are working correctly. So testing for this might give some hints on the health of the board. If you can see D+ being pulled up, then the bootloader is running okay, and the wiring upto the point your testing looks okay. Have you got access to any measuring equipment? Have you got any way to get at the USB signals? For example an old USB cable that you don't mind 'sacrificing' (by taking it apart to get at the wires), or fine pointed probes on a multimeter or oscilloscope? I've never tried disassembling a USB mini cable. I imagine it is delicate but doable. The signal exits the board on a wire in the USB cable, so that might provide the most information, but if you haven't got a cable you could take apart, your next best approach would be a fine probe and a multimeter or oscilloscope, and looking at the PCB. (You could also try to use another maple, instead of a multimeter or oscilloscope to detect a voltage or signal, but there is still the problem of connecting to the signal.) The signal appears on pin 45 of the STM32F, and there is a small resistor (R14) which you might be able to test if you have good eyesight, or a magnifying glass, and a steady hand. (Of course, you might be quite confident, in which case you might even try soldering a fine wire to a resistor. terminal) To get at the resistor terminals, you'd need to know which one it is (a good solution would be to install a free version of Eagle, and use its 'Show' command to highlight the signal, vias and resistor on the PCB layout). There is also a .png file of the top copper which clearly shows the USB socket and D+ signal. So that may be enough to locate the resistor which is due 'East', and directly connected to that signal. R14 is the 5th one from the top of the row of small, two terminal components directly behind the USB socket. Fortunately, R14, and it's neighbouring part C10 have the same signal connected to them so you have a reasonable place to press a probe (also C10 is a pale colour, and id due 'South' of R14 [with the USB socket to the West] so it is easier to orientate yourself when looking at the board). Then you'd need a fine multimeter or oscilloscope probe to connect to the resistor. You'll need a steady hand as the resistor and capacitor are small (0402), and is in a row of parts. If you have access to an oscilloscope with a good probe, you might want to see if anything happens on either of the two USB lines when the Maple is plugged in. The oscilloscope will load the signals, so it might be too distorted to communicate reliably, but seeing any signals on those wires suggests the host PC can see the Maple's USB electrical signals, even if nothing higher is working. HTH (Merry Christmas and Happy New Year) samtal on "Program upload problems" http://forums.leaflabs.com/topic.php?id=74192#post-105109 Tue, 24 Dec 2013 08:16:43 +0000 samtal 105109@http://forums.leaflabs.com/ Thanks. I may have miss led you by not writing a new post, as the original issue with the java messages is gone, part of the problem remains, though.. Sorry. My problem now is as in the last post, and it is only with one board, on two different computers, which indicates that the problem is with the board rather than the system. (Other two boards are OK). Nevertheless, I took your advice, but could not locate the files you mention in my Java files or elsewhere on my computer (WinXP). My Java is JAVA_VERSION="1.7.0" all files are dated Oct. 2013 (I'm not sure if these are install or original dates). So - I still can not access the serial USB on that board, but I can run it. gbulmer on "Program upload problems" http://forums.leaflabs.com/topic.php?id=74192#post-105105 Sun, 22 Dec 2013 13:03:12 +0000 gbulmer 105105@http://forums.leaflabs.com/ samtal - The original error message starts with a Java error, but different from the errors on OS X (though, if you aren't using OS X, it may be different anyway). Maybe it's nothing to do with the Maple? Have you recently installed an update to Java on the machine? If so, maybe try to find the .jar file which contains gnu.io.RXTXPort, and see what its last update date was? It is RXTXcomm.jar on OS X. If that has been updated, then it may be the culprit. If you find the file, you might also have a look at it using a program called jar (if you have it), which is a Java version of zip. On my machine, the files inside RXTXcomm.jar were last updated on "Mon Jan 30 00:27:04 GMT 2006" (full disclosure: I am not a member of LeafLabs staff.) samtal on "Program upload problems" http://forums.leaflabs.com/topic.php?id=74192#post-105101 Sun, 22 Dec 2013 02:09:46 +0000 samtal 105101@http://forums.leaflabs.com/ The Maple "boot loader" and the IDE together are supposed to load the built-in ST ARM USB driver AND its Windows Serial implementation driver, using two drivers: The Serial and the DFU (for win). (Both are located in the Maple Drivers library). The problem I am facing is that while the USB driver and port load nicely, it is not implemented as a serial port. Uninstalling and re-install the port makes no change to that. I have learned (and experienced) that kind of problem with Win7, but I am running WinXP which runs OK for other Maples. I have tried the same board, another computer, fresh Maple download (all, incl. drivers) for no avail, which indicates the problem is with the board. It still shows the Maple003 as pure USB port, no serial. Can anyone help? samtal on "Program upload problems" http://forums.leaflabs.com/topic.php?id=74192#post-105039 Sun, 08 Dec 2013 11:25:10 +0000 samtal 105039@http://forums.leaflabs.com/ Hi, In continuation to my previous post here, I have now a situation in which the USB does not install as a serial, but rather as a pure USB. I have tried all install options, but the Maple003 appears not as a serial, and thus is not recognized by the IDE. The drivers files maple_serial.inf, libusb0.dll, libusb0.sys are present, and the install runs but not as a serial port. I have seen several posts but non helped. Any idea? samtal on "Program upload problems" http://forums.leaflabs.com/topic.php?id=74192#post-105035 Sun, 08 Dec 2013 04:51:40 +0000 samtal 105035@http://forums.leaflabs.com/ Hi, I need urgent advice, as follows: All of a sudden, my 2 boards will not load program, but will show a long red error message as shown below. (on WinXP 32, same as always!) The previously loaded program runs, resets and maple program reload did not make a difference. I also noticed that one board has its USB port as a serial one, the other is shown as a pure USB port, but both will not load, and show the same error. This to me is a catastrofic situation, as I need to present my program after making some minor changes. Thanks samtal Here is the full shown message: Going to build using 'armcompiler' (ARM) Compiling core... No libraries to compile. Compiling the sketch... Linking... Computing sketch size... E:\DOCUME~1\SAM~1.TAD\LOCALS~1\Temp\build1812029404505690763.tmp\WaferMapping08.cpp.bin : section size addr .data 17984 0 Total 17984 Binary sketch size is reported above. Check it against a 108000 byte maximum. Loading via dfu-util Resetting to bootloader via DTR pulse java.io.IOException: No error in nativeDrain at gnu.io.RXTXPort.nativeDrain(Native Method) at gnu.io.RXTXPort$SerialOutputStream.flush(RXTXPort.java:1201) at processing.app.Serial.write(Serial.java:470) at processing.app.Serial.write(Serial.java:492) at processing.app.debug.DFUUploader.emitResetPulse(DFUUploader.java:170) at processing.app.debug.DFUUploader.uploadViaDFU(DFUUploader.java:100) at processing.app.debug.DFUUploader.uploadUsingPreferences(DFUUploader.java:57) at processing.app.Sketch.upload(Sketch.java:1473) at processing.app.Sketch.exportApplet(Sketch.java:1405) at processing.app.Sketch.exportApplet(Sketch.java:1368) at processing.app.Editor$45.run(Editor.java:1965) at java.lang.Thread.run(Thread.java:619) Searching for DFU device [1EAF:0003]... dfu-util - (C) 2007-2008 by OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY Couldn't find the DFU device: [1EAF:0003]