Rockbox Development > New Ports
Cowon D2
shotofadds:
Thanks, that's very helpful. The ID codes show that:
a) the 8Gb D2 is comprised of 2 banks of 4Gb flash (since 2/3 are replicated), rather than the 4 banks of 2Gb I was half expecting.
b) but we know the reading code still partially works, since you managed to display some tag information.
The ID codes suggest the 8Gb contains 2x SAMSUNG K9LBG08UOM, which at first glance seems to have the same characterstics as mine except each page is 4Kb in size rather than 2Kb. I'll update the wiki with this information later.
More reports from other D2s are welcome... but please PM them to me to avoid cluttering the forum, thanks.
linuxstb:
Nice work on getting the NAND working - I'm looking forward to having the time to try porting your code to the TCC77x.
Regarding the block translation, have you looked at the NAND driver for the iFP7xx port? IIUC, this does something similar, so may be of help/inspiration. It's in firmware/drivers/ata_flash.c
shotofadds:
I've looked at the iFP7xx code briefly, but not in much detail yet. My task for the next week is to establish how the OF block translation works, so I don't yet know how similar it may turn out to be.
I also need to update the existing code to detect the different chips used in the 2/4/8Gb models and adjust for the different page sizes, but that should be fairly trivial.
Voluspa:
--- Quote from: shotofadds on January 25, 2008, 06:43:56 PM ---More reports from other D2s are welcome... but please PM them to me to avoid cluttering the forum, thanks.
--- End quote ---
I'm not allowed to PM (too new a user?) but my test confirms andiator's. On a European 8Gb player - Sweden, bought last week, came with 2.51 FW - bank 0 is mirrored on bank 2 and bank 1 on bank 3. The NAND IDs are the same as andiator's as well.
Pressing a button while running rockbox/build/bootloader/bootloader.bin started a memory count (check ?) during which I could make coffee ;-) After ca 10 minutes - the count stopped at 2Gb or so - some dumps were showed when pressing buttons. Then came the "Helo world" screen.
A note regarding tcctool:
I'm always using fresh kernels in linux but tcctool relies on an old technique being present. So to make it work one has to compile the kernel with this checked:
Device Drivers -> [*] USB support -> [*] USB device class-devices (DEPRECATED)
[...]
This option provides backward compatibility for libusb device nodes
(lsusb) when usbfs is not used, and [...]
And furthermore, the /proc interface is completely gone even with this checked:
root@sleipner:~# uname -a
Linux sleipner 2.6.24 #1 PREEMPT Sat Jan 26 21:46:22 CET 2008 x86_64 GNU/Linux
root@sleipner:~# lsusb -t
cannot open /proc/bus/usb/devices, No such file or directory (2)
Mvh
Mats J
Yeeze:
I looked through the I2c code, that is used to receive input from the touchscreen, and noticed that it only receives the x and y position of the "cursor", my question is, is it possible to receive an array of all actually touched spots on the screen?
Because when I for example touch the screen with two fingers, the position of the "cursor" is in between the two spots I touched...
It would be very convenient, but my guess is it will be very time consuming... But if it is possible it would be nice... Does anybody know?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version