thanks!!!
thanks!!!
I'm using windows 7 usb-serial to upgrade from 1.3 to 1.4
After flashing it says "Image successfully written to device."
I then try to turn my VCI-100 on to use with Traktor and the power button goes on(red) but nothing else. It seems like there is no data being transferred or it's stuck in boot mode.
Any ideas?? I hope the controller isn't broken.
Last edited by EliPsE; 10-18-2010 at 04:05 PM.
::.VCI-100 SE 1.4.::::.Traktor 1.2.7.::
::.Motu-Ultralite.::.OSX 10.6.6.::
http://twitter.com/PhunkTronix
http://www.mixcloud.com/phunktronix/
Two things to check here - 1 that you selected the correct file to upload to the device (some people have flashed it with the .zip, the .exe etc) this just corrupts the firmware, and secondly are you removing the update kit before powering it back on after update.
It is the update kit which forces it into bootloader mode. However I suspect you are just not flashing the correct file.
1)powered off vci
2)removed harness
3)inserted the pcb
4)connected usb
5)opened the program with the firmware file
6)Turned the VCI on
7)flashed it
8)Turned the VCI off then removed the pcb and reconnected the harness
am I doing something wrong??
Clock Frequency (External) = 24.0000MHz, Clock Mode = 0, CKM = 1, and CKP = N/A
Connecting to device 'H8/3052F' on 'COM4'
Configuration:
'BOOT Mode' connection - using emulated interface
Opening port 'COM4' ...
Loading Comms DLL
Loaded Comms DLL
Initiating BOOT SCI sequence
Attempting 9600
Received immediate response from device: 0xAA
Using micro-Kernel : 'C:\Program Files (x86)\Renesas\FDT4.05\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 (x86)\Renesas\FDT4.05\kernels\ProtB\3052\Renesas\1 _2_00\Genm3052.cde'
Main kernel download complete...
Connection complete
Processing file :"C:\Users\Gabriel\Downloads\VCI1001_4\VCI100-DaveX-1.4.mot"
Operation on User Flash
Downloaded the operation module
Writing image to device... [0x00000000 - 0x0000907F]
Writing image to device... [0x00009080 - 0x0000917F]
Writing image to device... [0x00009180 - 0x00009AFF]
Data programmed at the following positions:
0x00000000 - 0x0000907F Length : 0x00009080
0x00009080 - 0x0000917F Length : 0x00000100
0x00009180 - 0x00009AFF Length : 0x00000980
38.75 K programmed in 49 seconds
Image written to device
::.VCI-100 SE 1.4.::::.Traktor 1.2.7.::
::.Motu-Ultralite.::.OSX 10.6.6.::
http://twitter.com/PhunkTronix
http://www.mixcloud.com/phunktronix/
Sorry about that. Yes, I open the Basic program first then load the firmware file.
Everything is put back together securely
::.VCI-100 SE 1.4.::::.Traktor 1.2.7.::
::.Motu-Ultralite.::.OSX 10.6.6.::
http://twitter.com/PhunkTronix
http://www.mixcloud.com/phunktronix/
Problem Fixed!!!
Apparently, my VCI did not like the usb port that was used to successfully flash the firmware which is strange.
I also unplugged the usb from the computer while the VCI was on. After that, all the lights and data being transmitted were active.
Last edited by EliPsE; 10-20-2010 at 08:54 AM. Reason: Solution
::.VCI-100 SE 1.4.::::.Traktor 1.2.7.::
::.Motu-Ultralite.::.OSX 10.6.6.::
http://twitter.com/PhunkTronix
http://www.mixcloud.com/phunktronix/
I have a USBtinyISP programmer. Could I use this to update the firmware on my 100? If so, what is the pinout that I should have from the 6-pin header?
Thanks!
I got my upgrade kit and followed the steps outlined in the video. However, when I power on the unit the LED lights turn on. Apparently, I can't make it go into Boot Mode. I double and triple checked to make sure the kit is sitting snug on the connector. The only other thing I can think might possibly be wrong is that I have my COM Port set up incorrectly. ...Or perhaps my Serial Cable is bad. Would either of these things prevent my unit from entering boot mode?
|
Bookmarks