Rockbox Technical Forums

Installation / Removal => Manual Installation => Cowon - Installation/Removal => Topic started by: pawal on August 01, 2006, 01:17:04 PM

Title: The X5V has [not] become a brick?
Post by: pawal on August 01, 2006, 01:17:04 PM
I tried to follow these instructions for my X5V: http://www.rockbox.org/twiki/bin/view/Main/IaudioBoot

After putting the bootloader, and shutting of and inserting the power, the "automatic upgrade" didn't do anything (although it briefly said upgrading). Now when I try to start it, with long and short ONs (as suggested in some forums), or holding the record key, the same result appears when trying to load the firmware: -1.

What now?

Title: Re: The X5V has become a brick?
Post by: Llorean on August 01, 2006, 01:21:21 PM
Did you also extract a daily build to the root of your player?
-1 means it can't find Rockbox, that you've only installed the bootloader and not copied the software to the device.
Title: Re: The X5V has become a brick?
Post by: Bagder on August 01, 2006, 01:23:22 PM
... and even if the bootloader would've been totallt screwed up, you can still plugin USB, your charger and then mount it as UMS again and put a fine firmware image on it to upgrade to again.
Title: Re: The X5V has become a brick?
Post by: pawal on August 01, 2006, 01:24:07 PM
Did you also extract a daily build to the root of your player?
-1 means it can't find Rockbox, that you've only installed the bootloader and not copied the software to the device.

No, I followed the instructions on that web page. Maybe a stupid thing to do...
Title: Re: The X5V has become a brick?
Post by: pawal on August 01, 2006, 01:24:51 PM
... and even if the bootloader would've been totallt screwed up, you can still plugin USB, your charger and then mount it as UMS again and put a fine firmware image on it to upgrade to again.

Seems to be hard to do, as it shuts down immediatly.
Title: Re: The X5V has become a brick?
Post by: Bagder on August 01, 2006, 01:28:33 PM
Quote
Seems to be hard to do, as it shuts down immediatly.

1. Unit is off
2. Insert powerthing
3. Insert USB

The bootloader does not run. The unit says something about connected or OK to disconnect.

Are you saying this doesn't work for you? Rockbox and the Rockbox bootloader is not involved in this scenario...
Title: Re: The X5V has become a brick?
Post by: pawal on August 01, 2006, 01:34:14 PM
Quote
Seems to be hard to do, as it shuts down immediatly.

1. Unit is off
2. Insert powerthing
3. Insert USB

The bootloader does not run. The unit says something about connected or OK to disconnect.

Are you saying this doesn't work for you? Rockbox and the Rockbox bootloader is not involved in this scenario...


Does not work. Nothing happens at 3. Tried this procedure on two computers now.
And booting still shuts down.
Title: Re: The X5V has become a brick?
Post by: pawal on August 01, 2006, 01:51:59 PM
Ah, this was extremly silly. There are TWO USB interfaces on the damn thing.
Title: Re: The X5V has [not] become a brick?
Post by: jhMikeS on August 02, 2006, 08:58:51 PM
Maybe a dumb idea but I think using descriptive error messages might help people figure things out better. Instead they could see "Firmware not Found" or  "Bad checksum",  instead of just "-1" or whatever. Globally unique error values with a language string available to describe the error might go a long way to helping people diagnose problems as well as making things more robust elsewhere but the developers would have to actually use it :). A splash_message function that can take an error value and display the string with formatting could be used everywhere. Maybe not   :-\. Thoughts?
Title: Re: The X5V has [not] become a brick?
Post by: LinusN on August 03, 2006, 12:42:23 AM
Sure. That can be done in the bootloader, but in the main Rockbox code, there are simply too many combinations of errors to make it practical, especially when we strive to keep the binary as small as possible.