I might have ruined my firmware… I got to the step where you remove the cable harness and continued until i pressed program flash and everything worked fine. I think i got confused on the last steps. After everything was complete, to see if the computer would recognise the vci with the new upgrade, I assembled it back together and plugged in and powered on my vci to the computer. The computer wouldnt even recognise the usb and no lights turned on! So i took it apart again and tried downloading the firmware with 2 cables attached and my chip still installed because i was somewhat deceived by that part of the video, This never worked either, I enterchanged both ways of installing the update numerous times with both one and two cables attached whiile the back plate of the vci was opened and got farther bad results. Im not sure if im missing something small on the very last step or if i completely ruined my firmware ?? Im am also thinking that maybe my usb connection for my vci wasnt even working during the firmware update process??? Ean do you have any idea of what im doing or did wrong???
First of don’t panic, the Vestax engineers were smart enough to design the VCI with a separate boot loader area. In plain English that means even though it is dead now we should be able to solve your problem.
To begin with we need to do a little trouble shooting. Can you confirm that the USB port on the PC you are using for the upgrade is OK. Do this by plugging in another USB device and make sure it works as intended, preferably this would be a sound card or another controller, some thing that sucks a bit more juice than a keyboard.
I tried turning on my vci with the firmware chip attached and also tried turning it on the original way before i started messing around with it. I tried doing this on every usb port on my computer…nothing worked. I checked that all usb ports work on my computer by plugging in my soundcard to each of them. The soundcard works fine on all the ports…
I will try to keep it as short and understandable as possible.
When I updated my PC to Vista, I also updated my mainbord’s USB controller drivers.
This resulted in my USB ports rendering my BCR(MIDIcontroller) useless.
I had the same issues as you have. All devices working, except for my controller.
I reinstalled Vista, left the USB controller drivers update out of the picture, and my MIDIcontroller worked again.
So that’s why I asked if you had any USB controller updates before you flashed your VCI firmware.
Nope i didnt have any usb controller updates before the firmware flash. But as you said my midi controller seems pretty much useless as of now. If anybody with some knowledge of this type of stuff could help me out and point me in the right direction it would be great.
this is the first report we have received of a VCI-100 not working after the firmware upgrade so I would not be too concerned. It sounds like you may have never successfully installed the firmware and instead interrupted it in the middle of the process.
I would recommend very carefully following the steps in the video and this forum precisely. Please don’t try and combinations of cables or steps. There is only ONE right way to do this. Once you have a successful firmware upgrade (I.E. your computer displays success at the end) then test your VCI and lets see what happens then. Its sounds like you never finished the update correctly.
I really don’t no, I followed the video step by step and looked at the forum inside out. Maybe its just me missing something small, im not sure, i hope not anywas. The flash installs every time. I get a random pop up at the end of my installation of the flash that says:" This file is not an SRecord. Loading as raw data." and then it begins to download some more. Im not sure what that means or if thats supposed to happen. Here is what the software tells me:
OS: Windows Vista/Server 2008 [Non-Admin]
Clock Frequency (External) = 24.0000MHz, Clock Mode = 0, CKM = 1, and CKP = N/A
Connecting to device ‘H8/3052F’ on ‘COM5’
Configuration:
‘BOOT Mode’ connection - using emulated interface
Opening port ‘COM5’ …
Loading Comms DLL
Loaded Comms DLL
Initiating BOOT SCI sequence
Attempting 9600
Received immediate response from device: 0xAA
Using micro-Kernel : ‘C:\Program Files\Renesas\FDT4.02\kernels\ProtB\3052\Renesas\1_2_00\uGen3052.cde’
Downloading and verifying micro kernel…
Device is erasing…
Erase Timeout value set to 21 seconds
Erase Successful
micro-Kernel download successful
Sending inquiry for getting line size
Buffer size has been set to default (128 bytes)
Sending selection of device command
Selection of Device - Device selected, code 0302
Sending selection of clock mode
Sending selection of clock mode
Selection of Clock Mode - Clock selected, code 0
Changing baud rate to 38400 bps
Set baud rate value = 38400
Downloading main kernel ‘C:\Program Files\Renesas\FDT4.02\kernels\ProtB\3052\Renesas\1_2_00\Genm3052.cde’
Main kernel download complete…
Connection complete
Processing file :“C:\Users\Al\Desktop\vci-100se_13_firmware.zip”
Processing file :“C:\Users\Al\Desktop\vci-100se_13_firmware.zip”
Operation on User Flash
Downloaded the operation module
Writing image to device… [0x00000000 - 0x00005FFF]
Data programmed at the following positions:
0x00000000 - 0x00005FFF Length : 0x00006000
24 K programmed in 33 seconds
Image successfully written to device
My only guess is that im still in boot mode some how? But when the vci is in boot mode is the computer supposed to still recognize the usb for the vci??
