41CL Self-Update

[aurelio]

(11-03-2017 12:58 AM)Sylvain Cote Wrote:  

(11-02-2017 10:15 PM)aurelio Wrote:  I have rechecked the connection the setup of the COM25 related to the usb adapter (4800......etc.) seems to be everything OK but three attempts with the same result: anyone have experienced the same problem while using a serial adapter?

There are several usb-to-serial adapter chip manufacturer, some legal and some not-so-legal (cloned), be sure to install the appropriate driver that match the chipset.

(11-02-2017 10:15 PM)aurelio Wrote:  C:\clupd>java -jar clupdate-1.0.0.jar --upload UPDAT-3A.ROM COM25 4800

Command line is good

(11-02-2017 10:15 PM)aurelio Wrote:  21:14:29 --upload [fileName: UPDAT-3A.ROM] [portName: COM25] [baudRate: 4800]

java was found, jar file was found and the proper command selected

(11-02-2017 10:15 PM)aurelio Wrote:  21:14:29 File UPDAT-3A.ROM loading ... done [YCRC=0x8D9DEE9B Rev:2017-09-22]

ROM file was found and properly understood

(11-02-2017 10:15 PM)aurelio Wrote:  21:14:30 Serial COM25 opened.

Serial port found and opened

(11-02-2017 10:15 PM)aurelio Wrote:  21:14:35 Sending 4096 = 4096 bytes sent

File data was transferred to the transmit buffer and accepted by the JSerialComm library to be transmitted asynchronously.

(11-02-2017 10:15 PM)aurelio Wrote:  21:15:47 Serial COM25 closed.
Exception: TimeoutException [message: wait-time > 60000 milliseconds]

For some reason the low level driver (written in C) of the JSerialComm library was not able to asynchronously send the data from the transmit buffer to the serial port driver, hence the TimeoutException message a little more than a minute after the Sending message.

This point to either a problematic usb-to-serial adapter or more probably a driver not matching the usb-to-serial adapter chipset.

Sylvain

thank you for the step-by-step analysis
I'm more convinced that the problem is due to the driver.
I downloaded it from this page and when I tryed to install it a warning at the end of the setup "the setup is complete but could be a problem while using this driver" or something like that. in the device property box was marked infact with the sign (!) , but after unplugging and plugging it into another usb port was completed the setup and everithing seems to be normal