Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
OldOne:
Re:Voltage Scaling
Just some brief tests. Yes my problem PQI 8gb cards work fine with voltage scaling disabled.
My A-Data card was corrupted when recording to it with voltage scaling enabled. Otherwise it worked perfectly at 1.10. I will run a battery bench both ways to get an idea of how it affects battery life and post the results.
FlynDice:
@funman:
Could you give a quick update the status for the clipv2. If I've pieced things together correctly you've got it booting with an operating display and the sd storage makes it past the initialization stage, but you don't know how to initiate a transfer yet. How am I doing so far?
funman:
FlynDice, you got it right.
Also all the buttons are working, it can help while debugging (like printing some message and waiting a button press before continuing execution).
Unhelpful reportedly had some problems with initialization but it sometimes worked, so this problem can be left for later.
sd-as3525v2.c has all the info I found so far, continue the reverse engineering is left as an exercise to the reader :)
FlynDice:
Clip+ 2Gig on the way.
Willing to risk bricking 1 unit for the project......
EDIT:
@funman:
Looking at the diff you gave me for dualboot.s and trying to understand the process. We're reading and testing pin A1. So I get the dualboot bootloader installed and then I turn the player on and hold a button. If It boots with a delay we've found a match, if there is no delay we shutdown and start again with a different button. Is this the general idea?
funman:
--- Quote from: FlynDice on January 26, 2010, 08:32:22 PM ---Looking at the diff you gave me for dualboot.s and trying to understand the process. We're reading and testing pin A1. So I get the dualboot bootloader installed and then I turn the player on and hold a button. If It boots with a delay we've found a match, if there is no delay we shutdown and start again with a different button. Is this the general idea?
--- End quote ---
Right, although we don't know if holding one particular button will set or clear A1.
First thing I would do is use unmodified dualboot.S (mkamsboot won't work out of the box, i'll let you figure why).
If it produces a brick we'll know there is something seriously wrong.
Then boot without pressing any button, then pressing one button, then pressing another one.
Just look at the delay presence in the majority of the boots and you'll know the default state.
Then boot pressing all buttons one by one and check if the default state change.
Note: looking at my previous post, it mentions setting GPIOB pin 1 and waiting a hair, I'm not sure if i've put that in the diff I sent you.
Writing a pin is more difficult, I'm not sure if you can know the previous value to restore it after your code has run. (Sounds a bit paranoiac if this pin is changed by button code in OF, but you never know..)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version