Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
saratoga:
--- Quote from: ranma on February 16, 2010, 10:27:34 AM ---Now I have to figure out how to best proceed in testing the pins...
--- End quote ---
This can probably help:
http://forums.rockbox.org/index.php?topic=14064.msg129684#msg129684
funman:
Quick update:
LCD now works on Clip+ since r24729.
It's at the same state than Clipv2, i.e. only buttons & lcd work, still not storage.
Further development is still blocked until someone figures how to use the SD controller.
mkamsboot reported to work (r24727) on my Clip+, FlynDice one and 2 other testers from the irc channel (tested 2GB, 4GB and 8GB).
If you want to help you can test it on your Clip+ and report if it bricked it or not (still not sure what happened on the 2 bricked Clip+)
ranma:
--- Quote from: ranma on February 16, 2010, 10:27:34 AM ---Now I have to figure out how to best proceed in testing the pins...
--- End quote ---
Battle plan:
Either the 0V pin is TRST and TDO is tristated during reset or it's TDO and TRST is floating.
Check if it can be pulled up (TRST) or not (then it's most likely TDO).
Assuming it's TRST, check the other pins for 0V or 3V, I'd expect TDO to have logic level now.
For the remaining 3 pins there should only be 3! = 6 possible combinations left.
I also bought two 74HC00, LEDs and resistors to build a SR flop for manual clocking and to show the pin state.
[edit]
Ok, unfortunately TDO is tristated as long as the state machine is not in a 'shift data' mode.
But I got the pinout now:
--- Code: ---C240v2 JTAG pinout
USB
1 GND
F 2 TDO
L 3 TCLK
A 4 TMS
S 5 TDI
H 6 TRST
7 VCC
RAM
--- End code ---
TRST is asynchronous, just checked that.
Here ist the test rig I used for figuring out the pinout:
http://uguu.de/~ranma/jtag_test_rig.jpg
Two 74HC00 Quad NANDs, 2 NANDs form a SR-Flipflop to debounce the clock switch (left), 4 drive the upper LEDs for monitoring which pin is TDO, 2 are unused (inputs tied to gnd).
TMS is fed in using the dark blue jumper cable.
TRST is the white cable on the right side pulled up to VCC using a 10K resistor.
Unfortunately the girl with the Jtagkey wasn't at the hacker space today, so I can't go on and try to upload a debricker just yet.
[/edit]
saratoga:
--- Quote from: ranma on February 18, 2010, 12:27:46 AM ---Unfortunately the girl with the Jtagkey wasn't at the hacker space today, so I can't go on and try to upload a debricker just yet.
--- End quote ---
If you can get JTAG running while in some part of the OF, it would be really interesting to know what settings it uses for the various AS3525v2 clocks and voltage regulators. We're clearly not setting a few things correctly and knowing the OF settings would be useful to figure out what.
funman:
--- Quote from: saratoga on February 18, 2010, 11:24:27 AM ---If you can get JTAG running while in some part of the OF, it would be really interesting to know what settings it uses for the various AS3525v2 clocks and voltage regulators.
--- End quote ---
You mean AS3525? The v2 is only in Clipv2/Clip+/Fuzev2 not in c200v2.
Not sure how c200v2's battery life but I would expect it to be lower than OF like the other AMS, and indeed JTAG could be very helpful.
Can you insert breakpoints ? I think it's the only way to be able to know what the i2c registers are set to (Reading a register isn't simply a load), unless we find that the OF keeps a cached table of registers content
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version