Installation / Removal > Cowon - Installation/Removal

The X5V has [not] become a brick?

<< < (2/2)

Bagder:

--- Quote ---Seems to be hard to do, as it shuts down immediatly.
--- End quote ---

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...

pawal:

--- Quote from: Bagder on August 01, 2006, 02:28:33 PM ---
--- Quote ---Seems to be hard to do, as it shuts down immediatly.
--- End quote ---

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...


--- End quote ---

Does not work. Nothing happens at 3. Tried this procedure on two computers now.
And booting still shuts down.

pawal:
Ah, this was extremly silly. There are TWO USB interfaces on the damn thing.

jhMikeS:
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?

LinusN:
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.

Navigation

[0] Message Index

[*] Previous page