Octopus gone dark o...
 
Notifications
Clear all

Octopus gone dark on upgrade to OS5


stratblue
(@stratblue)
Member
Joined: 2 years ago
Posts: 67
Topic starter  

Hi there.

 

tried to update to the new OS 5 but I have run into a problem. The Octopus display is dark but if i restart it or reset using the red button I can see the boot sequence in Zterm

 
I get error: 6 in SerGetBuf when I start it. Any ideas where to go from here?
 
Thanks.
This topic was modified 1 year ago 5 times by stratblue

Quote
Eric
 Eric
(@eellis)
Member Admin
Joined: 2 years ago
Posts: 46
 

Hey Nick,

From the terminal output it looks like you issued the command to load the ELF file but you didn’t actually send it using your terminal. Then, I think you saved ... a failed transfer to NAND memory (flash). Now the boot loader can’t start the machine because the OS is missing. You should be able to transfer the ELF successfully, save it and get the machine back. The bootloader is stored in a different location so I don’t think there is anything wrong. Just be careful to double check the commands, or copy/paste directly from the guide. 

We can help you transfer using the terminal. You need to select the file before it times out. It looks like you took too long :/ it will take about 3 mins and you’ll see a progress bar in the terminal UI. 


ReplyQuote
stratblue
(@stratblue)
Member
Joined: 2 years ago
Posts: 67
Topic starter  

Crikey Eric, that's quick, I just went to sit down in the garden and de stress! I'll try it now.


ReplyQuote
stratblue
(@stratblue)
Member
Joined: 2 years ago
Posts: 67
Topic starter  

Ok...this is what I have now:

 
I see no way to actually send the file, it just seems to hang with no progress bar movement. I realised also that the pdf I was following lacks the instructions to switch to 'binary data' in the transfer convert menu.
This post was modified 1 year ago by stratblue

ReplyQuote
Eric
 Eric
(@eellis)
Member Admin
Joined: 2 years ago
Posts: 46
 

Hm, I remember this has happened to me. Your terminal may be hanging up because the settings are off. Or, maybe it timed out again. After you issue the load command, you select your file and it should transfer, unless it times out. You will see the terminal print a character every second or so and after five or ten it gives up. If you send the file after it gives up, you will get a stuck transfer, which is what you have. I recommend you try again. 


ReplyQuote
stratblue
(@stratblue)
Member
Joined: 2 years ago
Posts: 67
Topic starter  

@eellis

I have tried a few times now, even being conscious of a timeout situation I did it as quickly as possible, I also tried loading it from a different folder. So what are these 'settings' of which you speak....?


ReplyQuote
Eric
 Eric
(@eellis)
Member Admin
Joined: 2 years ago
Posts: 46
 

Hey, I’ll be out for a bit and I need my computer to check. It may be the baud rate being too high, or one of the connection protocol check boxes. @handsfelloff knows a lot more about different terminal software. I’m guessing you’re on Mac and I run Linux so I’ll do my best. I’ll post in ~4 hours. 


ReplyQuote
stratblue
(@stratblue)
Member
Joined: 2 years ago
Posts: 67
Topic starter  

@eellis

Hey Eric, no need, I got it sorted. Not being so much of a computer geek, I had forgotten that 'enter' is not the same as 'return'. Doh! Anyway, for anyone reading this, it's accessed via a modifier + return key on new Macs, I think. I just dug out an ancient keyboard. Thanks for your help, once you pointed out that I wasn't uploading the file, I managed to figure it out.


ReplyQuote
Share: