Upgraded successfully, but not sure!
Upgraded successfully, but not sure! Posted on: 03.10.2009 by Denny Nehrt Hi there. I upgraded my firmware and it all looked successful., however, I haven't used my VCI-100 in quite some time and forgot how to identify the ramp up problem, so I am not completely sure how to know I have 1.3The sticky post is lacking a bit of detail, so could someone give me the tell-tale signs of 1.2 and 1.3 so I can switch and verify all of that functionality? Thanks Chris | |
| Xavier Emanuels 12.10.2009 |
Originally Posted by depeche818
|
| Denny Nehrt 06.10.2009 | I should note that if I immediately remove my finger, it seems to stay lit for just a little while. I guess the big question in my previous post was what exactly the ramp-up issue is and how I would find it so I can identify that my FW upgrade was successful (see my output log above). Is there any tell-tale sign of 1.3? Perhaps "Press this button and this will happen", or "press this button and observe the MIDI code"? I know that supposedly, a few of the buttons send multiple codes that 1.2 didn't do.
Originally Posted by BentoSan
|
| Denny Nehrt 03.10.2009 | Hi there. I upgraded my firmware and it all looked successful., however, I haven't used my VCI-100 in quite some time and forgot how to identify the ramp up problem, so I am not completely sure how to know I have 1.3 The sticky post is lacking a bit of detail, so could someone give me the tell-tale signs of 1.2 and 1.3 so I can switch and verify all of that functionality? Thanks Chris |
| Xavier Emanuels 12.10.2009 |
Originally Posted by depeche818
|
| Denny Nehrt 06.10.2009 | I should note that if I immediately remove my finger, it seems to stay lit for just a little while. I guess the big question in my previous post was what exactly the ramp-up issue is and how I would find it so I can identify that my FW upgrade was successful (see my output log above). Is there any tell-tale sign of 1.3? Perhaps "Press this button and this will happen", or "press this button and observe the MIDI code"? I know that supposedly, a few of the buttons send multiple codes that 1.2 didn't do.
Originally Posted by BentoSan
|
| Denny Nehrt 06.10.2009 | WHen I throw the jog wheel, it stays red until it stops. This indicates 1.1 from the identify your firmware post earlier. This is the output of programming my device.... all looks proper, no? 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 '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\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:\Vestax VCI-100\VCI-100SE_1.3_Firmware.mot" Operation on User Flash Downloaded the operation module Writing image to device... [0x00000000 - 0x000000FF] Writing image to device... [0x00000200 - 0x0000647F] Writing image to device... [0x00008000 - 0x0000807F] Writing image to device... [0x00009000 - 0x0000907F] Writing image to device... [0x00009080 - 0x0000917F] Writing image to device... [0x00009180 - 0x00009AFF] Data programmed at the following positions: 0x00000000 - 0x000000FF Length : 0x00000100 0x00000200 - 0x0000647F Length : 0x00006280 0x00008000 - 0x0000807F Length : 0x00000080 0x00009000 - 0x0000907F Length : 0x00000080 0x00009080 - 0x0000917F Length : 0x00000100 0x00009180 - 0x00009AFF Length : 0x00000980 27.75 K programmed in 491 seconds Image successfully written to device Disconnecting Disconnected |
| Denny Nehrt 06.10.2009 | Well, that light doesn't seem to remain lit after I let it go. Is is possible that the firmware update said it was successful and didn't actually do anything? That sounds odd.... I know for sure that I had had v. 1.1 of the firmware, as I bought it right when it came out. Also, how would I identify the ramp-up issue? Thanks for your help. Chris |
| Xavier Emanuels 05.10.2009 | Unplug the VCI-100 - Hold the top little black button on the top left of the unit as you turn your VCI-100 on and replug in the VCI-100. If the LED right next to this black button lights up for a little while as the unit boots (indicating you have booted into firmware 1.2 mode) then your VCI-100 has firmware 1.2. Also firmware 1.1 is the only version with a ramp up issue, firmware 1.2 does not contain this issue Hope that helps ! |
<< Back to DJ TechTools' VCI-100 FAQReply