Rockbox Development > New Ports
SanDisk Sansa m200 series (v1)
alsaf:
What I be correct in saying that the porting effort can't go ahead until the partition containing the firmware can be accessed?
Based on imagination rather than experience I can only think of two options to get around this:
1) Use an alternative way of accessing the partition.
2) Finding the firmware in the datadump, amend it then DD it back to m240.
I'll have to check to see if any of the above options are actually possible.
EDIT: Either that or figure a way to get player into recovery mode if that is possible?
Bagder:
Normally we want a way to get out of a bad firmware install. I'd say that's the primary thing a porter wants.
Once the firmware upgrade file format is figured out and a brave soul wants to try it, how can (s)he get back to the original one afterwards?
alsaf:
From the looks of the data dump, the partition where music files can be stored and can be accessed is physically the first one on disk. After that it is the partition that contains firmware which can't be accessed.
According to the link on the MSWIN4.1 Boot Record in previous thread, the boot sector starts with 52 52 61 41 and ends with AA55.
As seen from the following extract from the dump, the boot sector is on the second partition.
--- Quote ---14904E70 02 F0 FE FD 2A 1C 69 46 07 98 00 F0 6F FF 00 28 ....*.iF....o..(
14904E80 00 D1 E5 62 68 46 02 F0 0B FE 01 20 E4 E7 00 00 ...bhF..... ....
14904E90 55 AA 00 00 52 52 61 41 72 72 41 61 00 00 55 AA U...RRaArrAa..U.
149084C0 B1 F9 00 28 03 DA 20 1C FF F7 86 F8 51 E6 20 1C ...(.. .....Q. .
149084D0 FF F7 82 F8 00 20 4E E6 F0 FF 00 00 88 DF 00 00 ..... N.........
149084E0 F4 0F 00 00 67 45 23 01 55 AA 00 00 FF FF FF 0F ....gE#.U.......
--- End quote ---
I'm not sure if the M200 series has a recovery mode. Will have to do a google and post for a few related forums.
Edit:
From the below link it looks like the M200 series does not have a recovery mode. Not exactly from the horses mouth but the explanation is plausible.
http://www.anythingbutipod.com/forum/showthread.php?t=6530&highlight=recovery
alsaf:
Apologies for repeating what other posters have said (and stating the obvious) but it looks like the next step in this port is to try and update the firmware to expose the second partition. I wouldn't know how to even start doing this, yet.
Is anybody currently working on this port? Although I am only poking about with the player and learning as I go, I want to at least try to do something constructive to get the port moving on rather than repeating something that's already done or is being worked on.
linuxstb:
I bought a Sansa M260 (v1) a couple of weeks ago - for 20 GBP from here:
http://www.bigpockets.co.uk/product.php?lang=&product=SANDISK044
(they still have some in stock).
It seems to be extremely similar to the Logik DAX player I'm (slowly) in the progress of porting Rockbox to. It has the same family (tcc77x) of SoC and is using the same LCD controller (SSD1815) to drive a 128x64 mono LCD.
The tcc77x has a USB boot mode, but I couldn't find a way to enter this mode via key combinations whilst booting. So I used the same trick that worked on my Logik DAX - I removed the NAND module from the motherboard - not being able to find the NAND module causes the tcc77x to default to USB boot mode.
Once I did this, I could use tcctool (the -d c100 option worked) to transfer and run some test code compiled for the Logik DAX - and it worked, including the LCD driver.
The M260's backlight is connected to a different GPIO pin, but a search of an original firmware disassembly and some luck found that - pin 0x40 on GPIOA.
My logik DAX port is still in the very early stages (I have a basic bootloader build working, with a working LCD driver capable of displaying debugging info on the screen), so this is all I can do on the M260 as well.
But as I work on the DAX, I'll be trying to keep the M260 version in sync.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version