Rockbox

Several problem occurs with those format on Fuze+'s port. The problem has been identified as player specific as it doesn't occurs on clip+ and has been seen on 2 differents Fuze+ unit.

The problem are quite random which lead to difficulties to track them down precisely. Nevertheless, 3 differents phases can be observe regarding the behaviour of the fuze+ and mpc files:

- Normal behaviour (files can be selected, play, playlist also play without problem)
- Non-playing behauviour (files are skipped one after the other till the end of the dynamic play list) -- Nothing consistent was found on how to go from normal into non-playing behaviour or reverse.
- Buggy behaviour (you can actually play and skip between files but after playing one file, the player will just hang stucked or go into panic at the moment to load the next one:
Two different value set were observed for now (backtrace remains the same):
Data abort at 63E57B28
FSR 0x8
(domain 0, fault 8)
address 0x64000000
backtrace start
A: 0x63E56AE8
A: 0x60040D28
A: 0x6003D87C
A: 0x6003DB50
backtrace end

or:

Data abort at 63E57B24
FSR 0x8
(domain 0, fault 8)
address 0x64000001
backtrace start
A: 0x63E56AE8
A: 0x60040D28
A: 0x6003D87C
A: 0x6003DB50
backtrace end

Several tests were made so far to establish that:

1) The problem is not files specific as normal behaviour and non-playing and buggy behaviour occurs on the same sets of files. Differents tag coding and even wiping all the tag away didn't help either.

2) The problem is not related to database as not building it and/or erasing all DB files doesn't wipe out the buggy behaviour.

3) The problem ist not be related to specific settings or if so, it is related to defaut settings. Recompiling, reinstalling rockbox from scratch doesn't solve the buggy behaviour

4) Nothing consistent was found about how the player goes from normal to non-playing or reverse. However some consistent (systematical) way to go from non-playing to buggy phase was found:
- Reinitialize the database (wether if there are no DB or an already present up-to-date one). But the player will then be back on non-playing phases after reboot.
- Playing a big directory with a lot of files after skipping 20 to 50 of then the player will eventually start playing one of then (a random one nothing consistent here to)
- desactivating the directory's cache option (settings > system > disk) this way is the only way to remains even after reboot.

5) the backtrace of panic occuring in buggy behaviour was given into the ./utils/analisys/find_address.pl tool with the following result:
https://gist.github.com/1434466

6) Flac format as been seen with the same non-playing behviour. But buggy phases gave no backtrace:
Data abort at 63E71120
FSR 0x1
(domain 0, fault 1)
address 0x00004D6B