Rockbox Development > New Ports

SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2

<< < (329/386) > >>

Jennifur:
Checking it out now and will try udelay (5000). I will let you know how it turns out.


--- Quote from: bilditup1 on May 03, 2010, 09:22:28 PM ---Yeah jennifur - the last ready-made build this works with is 25733. If you modify the file I wrote about above (funman/kugel's suggestion) and make your own build, you could work with 25791. (I'm also using an 8gb Kingston Class-4). Read the thread in the middle of the last page for more info.

Devs- one more thing. My builds show up with an "M" after the build number. Should this be cause for concern?

-e


--- End quote ---

Vague Rant:
So far write support on Clip+ seems to be working perfectly, no crashes yet and I've been messing with settings, writing a scrobbler log, creating a database, etc. My microSD is working perfectly, but has never given me any trouble while others had issues, so that's not really useful information. If it is an access speed issue that would make sense, as the mSD I'm using is a 2GB Kingston (produced in Japan); these are noted for their access speeds and my original use for it was somewhere this was important--so now that it's been commandeered for my Clip+ it makes sense that it's worked well here also.

I'm currently running audio through a speaker, so I'm not sure of the mechanics re: power usage, as the speaker is itself powered. For that reason (and also because it's not fully charged yet) I haven't run a battery bench but I will do so shortly using headphones.

EDIT: Does Rockbox on these devices currently write anything in RAM to disk upon shutdown? I played a single album with logging enabled, switched off the player, and opened the log in QTScrobbler (and also Notepad++ to verify) and only the first five tracks (of a 13-track album) appeared in the .scrobbler.log. It is reproduced below.


--- Code: ---#AUDIOSCROBBLER/1.1
#TZ/UNKNOWN
#CLIENT/Rockbox sansaclipplus $Revision: 23447 $
Patrick Wolf The Magic Position Overture 1 280 L 1274541921
Patrick Wolf The Magic Position The Magic Position 2 233 L 1274542220
Patrick Wolf The Magic Position Accident & Emergency 3 196 L 1274542457
Patrick Wolf The Magic Position The Bluebell 4 74 L 1274542655
Patrick Wolf The Magic Position Bluebells 5 314 S 1274542730
--- End code ---

7o9:
As I reported on IRC, my initial testing of the write support on my Clip+ seems very successful.

I haven't tried extended tests but I saved settings and made bookmarks on both internal and uSD.

Great job guys, even if it's not all perfect, this update makes my Clip+ so much more awesome!

bYOndo:
Wow! thanks funman and flyndice, as usual, you're great!
on my clipv2, r25799-100503, everything works fine, unless "pitch" function; if modified frequently, it leads to great unstability.
here is the error:

--- Code: ---Data abort
at 30030688
FSR 0x8
(domain 0, fault 8)
address 0xE59FF024

--- End code ---

it can be reproduced by keeping "-2%" or "+2%" button pressed for a certain period.
and with "clipline" theme, the "pitch" screen glitches.

Massimo

edit: after some test, I realized that it's not so reproducible. Some time there's the "abort" message, other time it simply freezes, other time it scrambled the file duration on WPS, but playback keeps working. 

Jennifur:
Tried what bilditup1 said. It works, it can read the uSD card. Though, I can't get the database to build. I will try it with the latest SVN build and see if that will work.

Navigation

[0] Message Index

[#] Next page

[*] Previous page