Rockbox Development > New Ports

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

<< < (76/386) > >>

jesterday:
non-modified actual firmware (03.01.16F). So far i can see, nothing is changed or even done when hitting the center.  :-\

Anyone played around with the MTABLE, RES_INFO, SYS_CONF sys files or the version.sdk?
The warning in the version.sdk file seems  senseless, as it is restored (like the other files) when changed or removed.

As the files obviously are checked when booting, maybe we have to modifiy them to get the Erase Firmware to work (as example changing the Firmware Text in ERASE or something other)? mentioned one i tested of course.
Just some thoughts

have a nice WE

jesterday

EDIT: Has someone done the work of find out the "meaning" (damm, cant remeber the right word :-) ) of the values in SYS_CONF.SYS? Can this be of help in any way?

lassowski:
Hi!

Perhaps this feature removes a e200xx.bin firmware image from the disk before the player is upgraded with it?

Just a thought...

Frank

saratoga:
The erase firmware is probably just a feature that Sandisk never enabled, which is why they don't mention it and why it doesn't seem to do anything.  Firmwares for mp3 players are highly modular, with parts provided by different vendors.  Just because something is included doesn't mean its actually used.

Domonoky:
Hey,

i just got a sansa m200v2 and want to help out. I have tried the clip bootloader from the git tree, but unfortunatly the buttons are different on the m200v2, so it only starts the OF for me.
 
The SansaV2Firmware wikipage tells the sansa has a 4x4 keymatrix and no directly connected buttons. So i want to try to find those buttons. I have successfully inserted a delay loop, so i know the bootloader is running, and i want to use the this delay to check for buttons.

Unfortunatly i dont know too much asm, so i am still struggeling to set those GPIO pins correctly.
As far as i know, i should set one of A4-A7 to output, then write a 1 to this output, and then check A1-A3 for changes. Could someone help me with this ?  ( i am not afraid of bricking).

EDIT:
with the help of others i found nearly all buttons and put them on the SansaV2HardwareMappings wiki page.
Now i can boot into rb-bootloader if i want, but i get no reaction as lcd and backlight dont seem to work, and there is no led on this player. So next task would be either lcd driver or backlight..

EDIT:
we can control the backlight now. LCD is still unknown. Seems to be different to the one from the Clip.


greets

funman:
Something shocked me while I was discussing with anythingbutipod people: in the diagnosis mode of the Clip there is a "SDRAM Test" which reads:

--- Quote ---bus = [16] bits
SIZE = [2] MB
R/W TEST [PASS]
--- End quote ---

bertrik also mentioned seeing code related to external memory.

And finally the loading addresses of 2 drm library blocks, plus the "otg_functio" and "usb_functio" blocks are after 0x30000000

In the AS3525 datasheet the memory between 0x30000000 and 0x3000FFFF is "External Memory IF (MPMC Bank 4 - SDRAM)"

All this lets me suspect that the assumption that there is no SDRAM on the Clip (V1) is wrong.

By the way why do you suspect there is no SDRAM on the Clip ?


I tried writing to 0x30000000 and reading back but it failed, I suppose we need to initialize the SDRAM before using it.

EDIT: it seems the Clip ships with the 224 BGA AS3525 (with memory controller ARM PL172)

Navigation

[0] Message Index

[#] Next page

[*] Previous page