Rockbox

Tasklist

FS#5063 - RoLo not working correctly on X5

Attached to Project: Rockbox
Opened by Rani Hod (RaeNye) - Friday, 07 April 2006, 20:00 GMT
Last edited by Daniel Stenberg (bagder) - Thursday, 27 April 2006, 13:13 GMT
Task Type Bugs
Category Operating System/Drivers
Status Closed
Assigned To No-one
Operating System iAudio X5
Severity Medium
Priority Normal
Reported Version
Due in Version Version 3.1
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Upon selecting the new rockbox.iaudio, the new firmware is loaded and the font is changed into random bitmaps.
Returning to the WPS screen causes "I00: at 3101C97A".

This task depends upon

Closed by  Linus Nielsen Feltzing (linusnielsen)
Thursday, 13 July 2006, 21:22 GMT
Reason for closing:  Fixed
Comment by Daniel Stenberg (bagder) - Monday, 10 April 2006, 09:03 GMT
Why do you consider this to be "critical" ?
Comment by Rani Hod (RaeNye) - Monday, 10 April 2006, 13:27 GMT
Maybe I don't fully understand the difference between priority and severity;
I consider a bug that crashes the DAP as critical, although not prioritized since
(a) X5 is not a main target of the 3.0 version, and
(b) it can be avoided by /not using/ the RoLo feature.

IMHO, the bug should be first hidden by disabling RoLo for X5 targets and on a later stage fixed thoroughly;
Once it's in the state of "X5 doesn't support RoLo", the severity is medium or less, but I don't want to be able to crash the device by clicking the rockbox.iaudio file in the root directory.
Comment by newbeewan (newbeewan) - Saturday, 24 June 2006, 12:49 GMT
I think I have something like the same pb, but it appears when trying to stop music (long stand on the play/stop button)...
It never happen if I let my X5 play until the end of the playlist.

To reproduce it :
- play music
- stop with the play/pause button
I03 : AddrErr
at 0009DF28

Maybe it is not the same pb...
Comment by Rani Hod (RaeNye) - Saturday, 24 June 2006, 19:12 GMT
It's not the same problem.
You're seeing a RB crash; the exception handler always prints something like:

I<error code>: <error name>
at <code address>

Report it as another bug.

Loading...