Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
atomikpunk:
Wow that's great news Daniel! I looked at the M200 PCB pictures on the wiki, and there are a couple of unsoldered resistors too. There is one particularly attracting one near the JTAG connector, I guess that it will be my first look. If it works, the next thing to check will be to modify a byte or two in there to see if it will unbrick my player. I think however that I'll play safe and use a 10 or 100 ohms res. to short the pads, one never know ;)
Owh and BTW, on the (few) NAND flash datasheets I looked at that are TSOP-48, the pin which is connected to the resistor you jumped (pin 19) is almost always the write protect (/WP). So it's a bit confusing as of why it works, but maybe that pin is also connected somewhere else...
Edit: Ok I did try the same procedure and was able to see a plain'ol mass storage device in lsusb. However, unlike you Daniel, I have a device which shows up as being 0MB. I, however, only have USB 2.0 ports on my laptop so maybe this is the problem. Here is a snap of the interesting dmesg backlog:
--- Code: ---usb 4-1: new high speed USB device using ehci_hcd and address 4
usb 4-1: configuration #1 chosen from 1 choice
scsi12 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
scsi 12:0:0:0: Direct-Access UNDEF storage 1.0 PQ: 0 ANSI: 0
SCSI device sda: 1 512-byte hdwr sectors (0 MB)
sda: Write Protect is off
sda: Mode Sense: 00 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 1 512-byte hdwr sectors (0 MB)
sda: Write Protect is off
sda: Mode Sense: 00 00 00 00
sda: assuming drive cache: write through
sda:<6>sda: Current: sense key=0x0
ASC=0x0 ASCQ=0x0
unknown partition table
sd 12:0:0:0: Attached scsi removable disk sda
usb-storage: device scan complete
sda: Current: sense key=0x0
ASC=0x0 ASCQ=0x0
--- End code ---
The lsusb output is the same as yours if I use my usb ports as usb 1.1 (by rmmod-ing ehci_hcd). Maybe there is something with my linux box? So I'll try simply rebooting in windows to see what happens... (2s)
Edit 2: Well, on windows, it is detected as an "M200 Plus" device and windows installs 2 (UNDEF) drives. If I try to right-click on them, the first one seems to freeze explorer for a bunch of seconds, while right-clicking on the second one simply gives out that the drive is 0 bytes large with 0 bytes free. So it seems that there is still something missing on my side.
Any ideas out there? Daniel, you said that "I had problems on a USB2.0 port.. maybe try a USB1.1 if it doesn't work", what kind of problems did you get? Was it similar to what I'm getting now?
Owh and BTW, the M200 "bootloader" unsoldered resistor is the one right between the "repeat" button and the little battery...
PS: thanks everyone for the nice words, I really appreciate your support :)
daniel_at:
Hi atomicpunk & others,
Cool that you tried the procedure also with your device and I think its a good sign, that it works basically... Okay some ideas:
*) How did you (un-)bridge the pads? Maybe it is a timing problem, I dont know if i just had luck, but it worked three times in a row (only tried it 3x).
*) I have two Flash-Chips in my Sansa - how many have you? Maybe that is important... Maybe the bootloader OF is on the other one, and i just block (writeprotect?!) the other one.
*) What does "sudo fdisk -s /dev/sd?" say? or "sudo od /dev/sd?"
*) Under Windows: do you know WinHex ( http://www.x-ways.net/winhex/index-m.html ) - Very neat hexeditor (can open devices directly)
*) My proplems with USB2: did not work at all... the sansa booted into the OF - it gave me some thoughts "why?" and "how?"... But maybe I also had a problem while bridging the pads (bec. my computer with USB2 is in an other room - so i used other tools)
*) The computer which worked is a "native" USB1.1 (Notebook from the year 2000)
Okay.. thats all for now - would be glad if we get you (atomicpunk) back into the race :)
[edit]
I yesterday also tried to find other ways to enable the internal ROM-booldr.: I thought it would be reasonable that SanDisk put that XPC[0] Pin onto the Sansa-plug. So that a technican can flash the sansa with a special plug. Tried to pull up each pin up (one-by-one, with an external powersupply) and plug it into my USB: no luck. Than i though somewhere where it is easy reachable... There is a plastic-shield which is only glued above the battery: tried to pull up some pads, or bridge some resistors: no luck. Maybe some pin within the SD-Card reader.. so that you have to use a special crafted SD-Dummy... no luck.
But i wonder that my Sansa still works :)
[/edit]
CU
Daniel
JD24:
Nice find on the recovery thing daniel!
I read somewhere else that someone did enter the recovery mode with bridging
2 of the NAND datapins on startup. That could makes sense because
the cpu cannot read the flash correctly then.
EDIT:
I found the link:
http://s1mp3.org/en/docs_deadrec.php
JD
scharkalvin:
you may be able to find a real small surface mount spst push button switch that
can be soldered across those two pins.
andva:
I know it might be a really dumb suggestion, but if the pinouts for the SoC are standard (and thus available in the datasheet), the XPC pin may be exposed (as in, available to poke directly) somewhere.
If I'm not mistaken the SoC (at least for the e200v2, but hopefully the same for them all) is the square chip in this image (pictures already posted by Daniel):
http://www.flickr.com/photos/90053035@N00/2495459364/
Then, you may identify most of the pins making it through to the other side (I suppose the PCB is multilayer, so apparently not everyone is, though):
http://www.flickr.com/photos/90053035@N00/2496918368/
EDIT: It looks like he already did that!
http://www.flickr.com/photos/90053035@N00/2586759595
Now, anybody know what the correct pin is?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version