Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
wildmetal:
Greetings!
I have just made an acount on this forum to let you know of my troubles with rockbox on my v2 fuze and i can try diferent build's on my fuze to help find the bugs on v2.
The only build that doesn't give me the "Bad checksum" on my v2 fuze is this http://download.rockbox.org/daily/sansafuzev2/rockbox-sansafuzev2.zip
And with this build i can browse the contents of the internal memory and the sd card but when i play a song it plays fine but when it should pass to the next song it crashes.
Also i have been trying some games and some of them crashes when exiting.
Cumps
FlynDice:
It seems that r25502 "Bookmark.c cleanup, still no functional changes... yet" has broken playback from the uSD on my clip+. I looked quickly and can't see quite why this would be yet. It also prevents the player from booting with uSD installed.
Anyone else notice this? Or am I just special again... ;)
funman:
See http://www.anythingbutipod.com/forum/showthread.php?t=53702&page=8
Same build works differently on 2 Clip+ -> non-deterministic bug again?
Today I tried to use different transfer request sizes (DMA_S4 / DMA_S1) : no result.
I tried to panicf() from the ISR when the error bits were set but nothing happened, I could insert µSD and see the info in debug menu > disk info, but entering the filebrowser locked the Clip+
keland44:
--- Quote from: wildmetal on April 07, 2010, 01:27:51 PM ---Greetings!
I have just made an acount on this forum to let you know of my troubles with rockbox on my v2 fuze and i can try diferent build's on my fuze to help find the bugs on v2.
The only build that doesn't give me the "Bad checksum" on my v2 fuze is this http://download.rockbox.org/daily/sansafuzev2/rockbox-sansafuzev2.zip
And with this build i can browse the contents of the internal memory and the sd card but when i play a song it plays fine but when it should pass to the next song it crashes.
Also i have been trying some games and some of them crashes when exiting.
Cumps
--- End quote ---
i've noticed the same thing with the 0407 build for today maybe tonights build will be different hopefully
FlynDice:
I was convinced I had solved the random freezups last night by not turning off the dma synchronization logic. We disable this logic right now and for the v1's I think it's ok but for the v2's I think we probably should leave it enabled for the sd controller. The manual says that if the dma controller and the peripheral are using the same clock you can disable this logic to get better throughput. I think with the v2's though we are definitely on 2 different clocks. Well, I added this change to what I was working with and got 8 straight hrs with no lockup last night. I turned the unit off at that point, reverted to svn and started adding my changes part by part to see what the magic piece was and now I can't seem to get back there. I figured it was either only configuring the FIFO once or the DMA sync logic but perhaps it is a timing issue and some of the debug code I had in place was making it work. Still investigating... I have tried different watermark levels and different dma sizes and like funman have had similar results.
As far as SD writes go the problem to solve now is a FIFO over/underrun error whenever we try to write to the card. We do get data into the FIFO as you can read the MCI_FIFO_COUNT to see how many bytes are there but I have not yet gotten to looking at the MCI_TCBCNT & MCI_TBBCNT registers (card byte count & bus byte count) nor any sd card response values which may help.
Edit:
On further thought perhaps playing with the software hold enabled on the clip+ is what helps. Testers? please report your results good or bad!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version