- This topic has 13 replies, 3 voices, and was last updated 13 years, 4 months ago by
.
-
Posts
-
Upgrading AFTER THE OCTOPUS IS DEAD I have no idea to fix MANUAL TO KNOW WHY NOT GOOD ENGLISH CAN SOMEONE TO HELP U.S. WITH A MORE SIMPLE WAY The version I had was the 1.60 and tried to Upgrading 1.62 IN THE MIDDLE OF THE Midi
i Used hyperterminal for windows 7 my pc and octapus is on conection and the terminal say this.
Non-certified release, version UNKNOWN – built 04:27:46, Mar 12 2005
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
RAM: 0x00000000-0x00200000, [0x0000cfa0-0x001ee800] available
FLASH: 0x01800000 – 0x1a00000, 32 blocks of 0x00010000 bytes each.Adapted by genoQs Machines in 2006 as Octopus boot loader.
== Executing boot script in 1.000 seconds – enter ^C to abort
Octopus> fis load OCT_OS.elf
Octopus> go
+FLASH: driver init failed: Driver does not support device
Sorry, FLASH config exceeds available space in FIS directoryRedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version UNKNOWN – built 04:27:46, Mar 12 2005Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
RAM: 0x00000000-0x00200000, [0x0000cfa0-0x001fe800] available
FLASH: 0x00000000 – 0x1, 0 blocks of 0x00000000 bytes each.Adapted by genoQs Machines in 2006 as Octopus boot loader.
Octopus>PLZZZZZ HELLP :sick: :sick: :sick: :sick: :sick: :sick: :sick: :sick: :sick: :sick:
Post edited by: nicos, at: 2010/11/12 18:58
Nicos,
First off, you should be sure that your terminal app is set to send data in binary format.
If you do the correct steps to load the OS file in the updating PDF, it should work. Did you follow the instructions on page 8?
– – – – – – – – – –
First, we will tell Octopus that we are about to send something, so Octopus will open a connection and wait for the file to be transmitted. We issue the following command (followed by pressing “Enter”):Octopus> load -m ymodem -b 0x00010000
Send the new OS file to Octopus
With Octopus waiting for the transmission (as we saw above) you should then proceed with sending the OS .elf file using the YModem protocol, supported by your terminal program. To do this, on zTerm we choose the menu “File -> Send Files -> YModem-1k”. Other terminal programs may vary in terminology slightly.When prompted, select the .elf OS file to be sent from where you have stored it locally and press the “Open” button.
– – – – – – – – – –Note that the latest version of OS 1.62 was made by one of our community of users, and contains some post-genoQs fixes, including improved MIDI sync. It’s located here:
http://www.socialentropy.com/studio/OCT_162_jk03.elf
See the forum thread in this section called "multiple h/w sequencers & timing" for the background on this.
I’ll be happy to try to help more if no one else responds!
i am ready to sent file but i dont understand how make the redboot setup on mac os i have the file from the page ecos libs but i dont understand.
plz help somebody 4 day i have this headate :blink: :blink: :blink:
Post edited by: nicos, at: 2010/11/15 14:46
Sorry to keep you waiting Nicos, I thought maybe you would email me directly.
Once your terminal program recognizes that Octopus is connected, press and release the reset button. As you know, the terminal should say:
+
RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version UNKNOWN – built 04:27:46, Mar 12
2005
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
RAM: 0x00000000-0x00200000, [0x0000cfa0-0x001ee800] available
FLASH: 0x01800000 – 0x1a00000, 32 blocks of 0x00010000 bytes
each.
Adapted by genoQs Machines in 2006 as Octopus boot loader.
== Executing boot script in 1.000 seconds – enter ^C to abort
Octopus> fis load OCT_OS.elf -b 0x00010000
Octopus> go…BUT according to your posting, instead there is a message that Octopus has a problem booting on its own.
Try doing the next step in the procedure anyway:
Hold down the *control* key and the C key on your computer’s keyboard, and then press the reset button and hold it for 2 seconds, then release. Now quickly release the two keyboard keys. This should interrupt whatever is going wrong anyway.
If you see this:
RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version UNKNOWN – built 04:27:46, Mar 12 2005
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
octopus – MIDI Control Sequencer OS Update via USB
genoQs Machines, 2008 6
RAM: 0x00000000-0x00200000, [0x0000cfa0-0x001ee800] available
FLASH: 0x01800000 – 0x1a00000, 32 blocks of 0x00010000 bytes
each.
Adapted by genoQs Machines in 2006 as Octopus boot loader.
== Executing boot script in 1.000 seconds – enter ^C to abort
^C
Octopus>(Extra ^C’s are OK as long as the last line is there!)
…then you should be okay to continue.
Complete the last line exactly as below, then hit ENTER:
Octopus> load -m ymodem -b 0x00010000
The Terminal program will let you navigate to the OS file.
Now go to page 10 of the PDF instructions to continue.
Let us know if it works!If you are not sure about any part of the procedure that comes after this, don’t worry–you’ll be able to start over!
i make this and i send the file elf but show me this
RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version UNKNOWN – built 04:27:46, Mar 12 2005Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
RAM: 0x00000000-0x00200000, [0x0000cfa0-0x001ee800] available
FLASH: 0x01800000 – 0x1a00000, 32 blocks of 0x00010000 bytes each.Adapted by genoQs Machines in 2006 as Octopus boot loader.
== Executing boot script in 1.000 seconds – enter ^C to abort
^C
Octopus> load -m ymodem -b 0x00010000
CCCCCCCCCC
### Send (Y) OCT_OS_v160.elf: Cancelled
Unrecognized image type: 0x434f0f00
xyzModem – Cksum mode, 1(SOH)/1(STX)/0(CAN) packets, 12 retries
Octopus>
nicos wrote:Quote:i make this and i send the file elf but show me thisRedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version UNKNOWN – built 04:27:46, Mar 12 2005Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
RAM: 0x00000000-0x00200000, [0x0000cfa0-0x001ee800] available
FLASH: 0x01800000 – 0x1a00000, 32 blocks of 0x00010000 bytes each.Adapted by genoQs Machines in 2006 as Octopus boot loader.
== Executing boot script in 1.000 seconds – enter ^C to abort
^C
Octopus> load -m ymodem -b 0x00010000
CCCCCCCCCC
### Send (Y) OCT_OS_v160.elf: Cancelled
Unrecognized image type: 0x434f0f00
xyzModem – Cksum mode, 1(SOH)/1(STX)/0(CAN) packets, 12 retries
Octopus>Nicos,
Are you using the OCT_162_jk03.elf, with a file size of 304,848 bytes? Be sure your copy of the file is good.
Do you have your terminal program set to send the .elf file in binary format? Look in the settings menu and be sure "binary" is checked. That has been a problem for some people.
Let me know if anything gets better!
cikira wrote:
Quote:Nicos,Are you using the OCT_162_jk03.elf, with a file size of 304,848 bytes? Be sure your copy of the file is good.
Do you have your terminal program set to send the .elf file in binary format? Look in the settings menu and be sure "binary" is checked. That has been a problem for some people.
Let me know if anything gets better!
load -m ymodem -b 0x00010000
CC
### Send (Y) OCT 162.elf: Cancelled
Entry point: 0x00010040, address range: 0x00010000-0x00051e5c
xyzModem – CRC mode, 1(SOH)/296(STX)/0(CAN) packets, 3 retries
Octopus> fis create -b 0x00010000 -l 0x00070000 -f 0x01820000 OCT_OS.elf
An image named ‘OCT_OS.elf’ exists – continue (y/n)? y
… Erase from 0x01820000-0x01890000: …….
… Program from 0x00010000-0x00080000 at 0x01820000: …….
… Erase from 0x019f0000-0x01a00000: .
… Program from 0x001f0000-0x00200000 at 0x019f0000: .
Octopus> and then i i try to hold CLR button of octopus and reset (red button) and the next messege is .+
RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version UNKNOWN – built 04:27:46, Mar 12 2005Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
RAM: 0x00000000-0x00200000, [0x0000cfa0-0x001ee800] available
FLASH: 0x01800000 – 0x1a00000, 32 blocks of 0x00010000 bytes each.Adapted by genoQs Machines in 2006 as Octopus boot loader.
== Executing boot script in 1.000 seconds – enter ^C to abort
Octopus> fis load OCT_OS.elf
Not a loadable image – try using -b ADDRESS option
Octopus> go
No entry point known – abortedand the octopus stay dead
help plz. sorry for noob
What happens if you enter the "fis list" command after writing the new OS to flash? See the bottom of Page 10 of the PDF. Does the result look like this?
Octopus> fis list
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
Octopus>Have you tried updating using a different .elf file? Have you tried the one on this site?
What happens if you go back to v1.60? The link to that file is the one in the PDF instructions, even though the link URL says 1.62.
The USB update to 1.6.2 is not on this website, but I can give you the .elf file if you need it.
Which model is your Octopus? What serial number? I’m curious about whether it’s an older or newer one. What OS was in the machine before?
Sounds like the machine is functioning OK, which is a good thing–it just doesn’t like the file.
Did you send email to the genoQs guys and get no reply?
fis list is same 1.60 and 1.62 but again the problem dont fixed
my machine is new classic number 20 os ver 1,60
Adapted by genoQs Machines in 2006 as Octopus boot loader.
== Executing boot script in 1.000 seconds – enter ^C to abort
Octopus> fis load OCT_OS.elf
Not a loadable image – try using -b ADDRESS option
Octopus> go
No entry point known – aborted
Octopus> fis create -b 0x00010000 -l 0x00070000 -f 0x01820000 OCT_OS.elf
An image named ‘OCT_OS.elf’ exists – continue (y/n)? y
… Erase from 0x01820000-0x01890000: …….
… Program from 0x00010000-0x00080000 at 0x01820000: …….
… Erase from 0x019f0000-0x01a00000: .
… Program from 0x001f0000-0x00200000 at 0x019f0000: .
Octopus> +
RedBoot(tm) bootstrap and debug environment [ROM]
Non-certified release, version UNKNOWN – built 04:27:46, Mar 12 2005Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
RAM: 0x00000000-0x00200000, [0x0000cfa0-0x001ee800] available
FLASH: 0x01800000 – 0x1a00000, 32 blocks of 0x00010000 bytes each.Adapted by genoQs Machines in 2006 as Octopus boot loader.
== Executing boot script in 1.000 seconds – enter ^C to abort
Octopus> fis load OCT_OS.elf
Not a loadable image – try using -b ADDRESS option
Octopus> go
No entry point known – aborted
Octopus>the broblem is this again
Nicos, did you buy this machine directly from genoQs, or was it a used one?
Did the machine work for you before this problem happened?
Maybe problem is in the flash memory, but if so, this is the first such instance I’ve heard of with an Octopus. I’m sorry I can’t be more helpful.
thank you for the help so far, cikira,i appreciate it.
I was sent mail to the genoqs and Gabriel replied.
Today i sent him details for the problem, and wait anxiously what to do.i have bought the octopus from the genoqs a year ago, and everything goes well until the upgrades…..
thank you for the help so far, cikira,i appreciate it.
I was sent mail to the genoqs and Gabriel replied.
Today i sent him details for the problem, and wait anxiously what to do.i have bought the octopus from the genoqs a year ago, and everything goes well until the upgrades…..
- You must be logged in to reply to this topic.