still don't get it
still don't get it Posted on: 10.04.2009 by Vincent Wantah hey guys, I've been trying to upgrade my vci 100 and i always got another message, this time it's: OS: Windows XP [Admin] FDT API initialised: version 4, 02, 00, 008 Clock Frequency (External) = 24.0000MHz, Clock Mode = 0, CKM = 1, and CKP = N/A Connecting to device 'H8/3052F' on 'COM3' Configuration: 'BOOT Mode' connection - using emulated interface Opening port 'COM3' ... Loading Comms DLL Loaded Comms DLL Initiating BOOT SCI sequence Attempting 9600 Attempting 4800 Attempting 2400 Attempting 1200 Error No 15024: Boot failed I'm really sorry to bother you with this, but could anyone help me with this, I'm desperate.... | |
| Adena Charman 12.06.2009 |
Originally Posted by midifidler
Do you believe it could be the cable? I heard a null modem cable has the best results? Unfortunately I don't know what type of serial cabe I'm using but it does say 'NON-UL 9C CABLE ROHS COMPLIANT' on the cable sleeve, if that means anything? Any help is still greatly appreciated, it's starting to do my head in. |
| Vincent Wantah 10.04.2009 | hey guys, I've been trying to upgrade my vci 100 and i always got another message, this time it's: OS: Windows XP [Admin] FDT API initialised: version 4, 02, 00, 008 Clock Frequency (External) = 24.0000MHz, Clock Mode = 0, CKM = 1, and CKP = N/A Connecting to device 'H8/3052F' on 'COM3' Configuration: 'BOOT Mode' connection - using emulated interface Opening port 'COM3' ... Loading Comms DLL Loaded Comms DLL Initiating BOOT SCI sequence Attempting 9600 Attempting 4800 Attempting 2400 Attempting 1200 Error No 15024: Boot failed I'm really sorry to bother you with this, but could anyone help me with this, I'm desperate.... |
| Reece Murray 15.06.2009 | Yeah, you definitely need a driver. If your cable came with a disk, the driver should be on there. If it didn't, you could get a new cable with a driver... I had some problems at first, but got it eventually. I don't know much about windows machines, so I'll try and elaborate by memory. I used a usb to serial cable from radioshack. I installed the supplied driver (the pc could also find the driver and download it). I followed the instructions located in the community section where you are getting an error, specifically a time-out error. I followed these instructions to the letter, except for one variation, discovered by trial and error (it wasn't working for me without doing this): I set the baud rate to 4800 exactly - slowing down the info transfer solved the problem. I don't entirely remember if this was within the firmware update app or the os, look for it in either. You can do it!! |
| Adolf Hit 15.06.2009 | Hi Balsa, sorry to hear you have still had no luck. If your computer is not finding drivers for the USB serial cable there is no way that it will work so I would suggest finding the drivers for it. Then check the COM port it comes up under, and try again with that com port selected. If the COM port that gets assigned to it is above 5 set it to say 3 and disable any other serial devices using 3 for their COM port (disable driver under device manager) Also I would try powering the VCI of another computer while trying to update, that has fixed the boot issue for some people |
| Adena Charman 16.06.2009 | Ok, I've been trying over and over again over the past few days and still can't do it. I've changed the baud rate (bits per second?) from 9600 down to 300 and up to 38400. . I'm sure I've tried every combination of settings, changing 'data bits' and 'stop bits' aswell as the buffer settings in advanced settings. I've also changed the settings on 'FDTAdvandcedSetup.exe' but still get the same error. I did what you said with the USB cable and it pops up under 'other devices' as 'USB-Serial controller', when Windows searches for the drivers it says it could not find any. I used the usb cable before in bootcamp on my MBP and the same happened. I've tried everything I've seen on DJTT and there's next to no information anywhere else on the internet, so I'm almost ready to give up, unless there's anyone that has found a solution that hasn't been written about, or you, midifidler, know anything else that could help? If I find a solution I will make sure I post about it just incase there is anyone else in my situation. |
| Adolf Hit 12.06.2009 | Ok only (as I believe you know ) the 9 pin port is actually serial - the 25 pin is parrallel. So with no USB-Serial cables plugged in go to device manager, find the serial port and under advanced settings set it to COM1. Now try again using COM 1 in the software, try setting the delay settings as well as reducing the baud rate. Also try again using your usb to serial cable - if you have device manager open when you plug it in you can see it pop up, click on it, and check the com port under the advanced settings. If it is coming up as a port higher than 5 try setting it to 3. I found that the upgrade software does not like com numbers above about 5 or 6. |
| Adena Charman 12.06.2009 |
Originally Posted by midifidler
Do you believe it could be the cable? I heard a null modem cable has the best results? Unfortunately I don't know what type of serial cabe I'm using but it does say 'NON-UL 9C CABLE ROHS COMPLIANT' on the cable sleeve, if that means anything? Any help is still greatly appreciated, it's starting to do my head in. |
| Adolf Hit 11.06.2009 | how many com ports do you have? if you are using the hardware port on ur pc it will almost def be com1 not 3 |
| Adena Charman 11.06.2009 | Hello, I'm still getting this 'Boot failed' problem. I'm using a serial-serial cable on my desktop after it not working on my MBP using a serial-usb cable. I've gone through the 'Common problems' guide on here, but it doesn't really help as it seems serial cables don't have any problems, yet I'm having one. I've tried changing the COM Ports but it doesn't help. I've made sure the firmware kit is seated properly on the board. Does anyone know anything else that might work or that has worked for them? Any help would be greatly greatly appreciated. |
| Reece Murray 10.04.2009 | Looks like you're getting a time-out message. I assume you're using a usb to serial connection? Did you first try and set the serial delay as outlined in the "Common Problems" section of the Firmware Upgrade area? -I still had problems after that, but setting the actual baud rate to like 4800 did the trick. |
| Robbi Papst 10.04.2009 | read the FAQ common problems |
<< Back to DJ TechTools' VCI-100 FAQReply