August 4, 2009 at 20:20 #1003
Hello. I just tried to upload the OCT_OS_v16200.syx file to my Octopus. After uploading, I pushed the program button to write the new OS file to flash and saw a progress bar. When it appeared to be completed, I tried to restart, but nothing happened. I cannot get back in to system mode or anything. When I turn it back on, there are no lights or anything.
BarryAugust 4, 2009 at 21:11 #2500
I have to say the exact same thing happened to me.
Until we know more about this, I would suggest to everybody NOT to install OS 1.62August 5, 2009 at 21:59 #2503
Yikes :dry:August 6, 2009 at 03:24 #2505
I tried loading the OS via usb per instructions from Genoqs and that didn’t work either.August 6, 2009 at 11:48 #2506
OK – getting closer.
There are 2 versions of 1.60: the .27 (the one coming from v1.42) and the .32 release. They only differ in 2 very minor bug fixes. It appears however that .27 has trouble with 1.62.00 while 1.60.32 is fine. So far so good. Why the USB method would fail is still puzzling though..
Post edited by: gseher, at: 2009/08/06 13:49August 6, 2009 at 12:52 #2511
My Octopus had version 1.60.32 before I tried the update.
Is there any way to reset my Octopus? Right now, it is just a cool looking paper weight. :unsure:
Post edited by: Oxix52, at: 2009/08/06 15:23August 6, 2009 at 13:27 #2513
Hi Barry, the way to reset it would be to install 1.62 via the USB route. Let me know if you need assistance with it. Cheers,
GabrielAugust 6, 2009 at 15:20 #2514
Gabriel I have the latest beta version. Am I safe to upgrade to the new version?
LDT which version did you upgrade from??
mattAugust 6, 2009 at 15:33 #2520
I tried to upgrade from the newest of the betas. (1.61.08 I suppose).Quote:Am I safe to upgrade to the new version?
I would stick to that beta for a while .
Post edited by: LDT, at: 2009/08/06 17:34August 6, 2009 at 17:48 #2515
Thank you Gabriel. I probably need help loading the OS via USB. I am using zTerm. I have both the OCT_OS_v16200.elf and the OCT_OS_v160.elf files. I am following the instructions on the "OS Udate via USB" pdf. I am able to get communication with the Octopus, but when I try to send the new OS file to the Octopus, I get this message:
### Send (Y) OCT_OS_v16200.elf: Cancelled
Unrecognized image type: 0x434f1100
xyzModem – CRC mode, 1(SOH)/1(STX)/0(CAN) packets, 7 retries
I must be doing something wrong.
I don’t know if it helps, but this is the flash contents list when I issue a "fis list" command:
Name FLASH addr Mem addr Length Entry point
RedBoot 0x01800000 0x01800000 0x00020000 0x00000000
OCT_OS.elf 0x01820000 0x00010000 0x00070000 0x00010040
FIS directory 0x019F0000 0x019F0000 0x0000F800 0x00000000
RedBoot config 0x019FF800 0x019FF800 0x00000800 0x00000000
Post edited by: Oxix52, at: 2009/08/06 19:55August 6, 2009 at 21:00 #2521
Finally fixed my Octopus! I had to use a windows machine to get the transfer to work. I downloaded the 1.62 OS without problems using the USB connection. Now my Octopus is living again!:laugh:
Thank you very much.
BarryAugust 6, 2009 at 21:14 #2522
Oxix52 wrote:Quote:Finally fixed my Octopus! I had to use a windows machine to get the transfer to work. I downloaded the 1.62 OS without problems using the USB connection. Now my Octopus is living again!:laugh:
Thank you very much.
So did you just follow the USB update pdf word for word on windows and it worked Barry?August 6, 2009 at 21:20 #2516
Also, did you lose all your data when reinstalling via the USB route barry?
mattAugust 6, 2009 at 21:50 #2523
Yes. I followed it exactly as specified. I used a machine with windows vista 64. I downloaded and installed the FTDI driver as instructed and then installed Hyperterm. Then, following the instructions, I downloaded the OS and wrote to flash. It did take a couple of seconds before I saw the download proceed. I mean, I sent the file, but got no response for a couple of seconds. Once it was finished, Hyperterm reported that the download was stopped by the connected device. I hit OK and then rebooted the Octopus as instructed in the pdf.
I had not written anything to the memory to lose. I have been just saving sysex files to my computer for my sequences. I also tend to start things from scratch and then leave the Octopus powered up for a long time.
BarryAugust 6, 2009 at 22:26 #2524
It is good to hear.
I have previously had the same "unrecognized image type" error using a mac to do the usb update procedure. But I must admit I had to give up just installing the driver on my pc.
I am certainly not looking forward to do the usb thing on pc, but I suppose it can be done.
You must be logged in to reply to this topic.