Firmware Problem Solved.
Firmware Problem Solved. Posted on: 18.07.2009 by Debroah Genteman I have spent 6 hours now using 3 different PC's (XP and Vista) and using a serial to serial cable and brand new upgrade kit, and still the same problem everyone else has:OS: Windows Vista/Server 2008 [Non-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 'COM1' Configuration: 'BOOT Mode' connection - using emulated interface Opening port 'COM1' ... Loading Comms DLL Loaded Comms DLL Initiating BOOT SCI sequence Attempting 9600 Attempting 4800 Attempting 2400 Attempting 1200 Error No 15024: Boot failed This happens everytime no matter what. I have read the common problems, toggled every option possible on the PCs, used different computers and cables to power the USB, tested the upgrade kit with a meter for shorts, and every possbile software option in renesas. It appears from this community that this firmware upgrade is randomly successful. It's a shame that Vestax made such a crippled product. I'll try a few more hours then back to square one looking for a DJ solution. Be warned!! | |
| Oren Sicilia 21.07.2009 | Another point to note. I was not following this exact procedure at first. Once I followed these exact steps the upgrade worked. |
| Oren Sicilia 21.07.2009 | Another point to note. I was not following this exact procedure at first. Once I followed these exact steps the upgrade worked. |
| Oren Sicilia 21.07.2009 | Another point to note. I was not following this exact procedure at first. Once I followed these exact steps the upgrade worked. |
| Oren Sicilia 21.07.2009 | Another point to note. I was not following this exact procedure at first. Once I followed these exact steps the upgrade worked. |
| Oren Sicilia 21.07.2009 | Another point to note. I was not following this exact procedure at first. Once I followed these exact steps the upgrade worked. |
| Oren Sicilia 21.07.2009 | Another point to note. I was not following this exact procedure at first. Once I followed these exact steps the upgrade worked. |
| Oren Sicilia 21.07.2009 | Another point to note. I was not following this exact procedure at first. Once I followed these exact steps the upgrade worked. |
| Oren Sicilia 21.07.2009 | Another point to note. I was not following this exact procedure at first. Once I followed these exact steps the upgrade worked. |
| Debroah Genteman 18.07.2009 | I have spent 6 hours now using 3 different PC's (XP and Vista) and using a serial to serial cable and brand new upgrade kit, and still the same problem everyone else has: OS: Windows Vista/Server 2008 [Non-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 'COM1' Configuration: 'BOOT Mode' connection - using emulated interface Opening port 'COM1' ... Loading Comms DLL Loaded Comms DLL Initiating BOOT SCI sequence Attempting 9600 Attempting 4800 Attempting 2400 Attempting 1200 Error No 15024: Boot failed This happens everytime no matter what. I have read the common problems, toggled every option possible on the PCs, used different computers and cables to power the USB, tested the upgrade kit with a meter for shorts, and every possbile software option in renesas. It appears from this community that this firmware upgrade is randomly successful. It's a shame that Vestax made such a crippled product. I'll try a few more hours then back to square one looking for a DJ solution. Be warned!! |
| Estefana Ramsay 07.08.2009 | After having tried the usb to serial route with much frustration I figured the serial to serial method was the best. As stated above, it's impossible to tell the difference between the two versions of serial cables. The solution? Your friendly IT department. I swung down 'round that end of the building the other day, told the guys what I was trying to do, et. viola - half an hour later one of the IT guys stops by my desk with two serial cables - one null modem, the other, ummm...the other kind. Tried both cables later that evening , still to this day not sure which one worked, but in the end, I'm now fw 1.3! The moral of the story here is - if you've got an IT dep. at work, go talk to them. Chances are they've got hundreds of these cables lying around gathering dust (remember, these are the cables that were (in some cases still are) used to update phone systems), and they're more than happy to get rid of them to someone that has a use for them. |
| Adolf Hit 03.08.2009 | Hi Andy, Just to clarify, an "standard" cable is straight through, the cable you are describing is a "Null modem" cable, used to connect two computers or similar devices together, this crosses RX and TX. Having the wrong cable has been a common problem, unfortunatley unlike with a network cable you cannot visually tell the difference between a null modem and a standard cable, the only way is to check with a multimeter. |
| Debroah Genteman 25.07.2009 | It was the firmware kit!! After getting a replacement kit from DJTT the whole process took about 15 mins. What an ordeal, but I'm glad it was only a defective kit. I wouldn't reccomend someone without a background in electronics attempt this install, but DJTT made this as easy as possible. thanks! |
| Debroah Genteman 25.07.2009 | I have a replacement firmware kit and I am going to try it one more time today. |
| Oren Sicilia 23.07.2009 | There was nothing wrong with the kit, the first promblem was the serial cable and the second was the order to plug in and turn on. |
| Debroah Genteman 21.07.2009 | I checked my cable with a meter and it is indeed a "straight thru" cable as I thought. andyc, was it the new kit or the following the procedure that worked for you? |
| Oren Sicilia 21.07.2009 | Another point to note. I was not following this exact procedure at first. Once I followed these exact steps the upgrade worked. |
| Oren Sicilia 21.07.2009 | OK, I figured it out. The problem was with the cable. Standard serial cables have pins 2 and 3 crossed as most computers have a master serial port which connect to other devices with master ports hence 2 and 3 are crossed so the TX pin goes to the RX pin and vice versa. The serial port on the upgrade kit is a slave port which does not need the pins to be crossed, so a "straight through" cable is required. That's pins 2 - 2 RX, 3 - 3 TX and 5 - 5 GND. Everyone else having this issue, use a meter and check that the wiring is straight through and pins 2 and 3 are not crossed. Looking forward to trying out the new f/w toevening . Andy |
| Oren Sicilia 21.07.2009 | I am also having exactly the same issue. This is a kit I purchased a week ago. Maybe a faulty batch of kits? I have also verified everything I can find and what is mentioned in this thread. As far as I can tell everything is good, USB, serial, controller is boot mode etc. Andy |
| Debroah Genteman 19.07.2009 | Boot mode confirmed - everything off with USB power mode switched while kit inserted. I've tried the USB power from 2 PC's and my Macbook. I checked the kit for bad solder joints or obvious problems and it seemed fine. The only place I have the resources to do this is about 100 miles away and I simply ran out of time today. I will contact orders and see about a replacement kit since I have to use this controller every week for a radio show. thanks for replying |
| 19.07.2009 | Sorry your having trouble- I wish we could make it fail proof but there are a lot of variables. That being said- everyone with a PC and a serial cable has had very little trouble. I would stick to the XP computer and only test variables on that. A few general questions: is the vci-100 actually in boot mode? (red jogs and then everything is off) are you sure the kit is not defective? Email orders@djranking s.com to get a new one is the VCI getting power from the same computer? Worse case scenario- if it just wont work, send your controller to us and we will do the upgrade for free. |
<< Back to DJ TechTools' VCI-100 FAQReply