Rockbox Development > New Ports
Cowon D2
FranzD2:
--- Quote from: shotofadds on October 07, 2008, 05:16:08 PM ---
1) I'll do some testing to find the optimum wait time necessary (20ms is likely to be several orders of magnitude more than necessary!) and then commit a fix.
2) EDIT: Using a vertical back porch value of 0x1 fixed the missing lines at the top, but caused a missing line at the bottom. A value of 0x2 works better for me - does this work for you as well?
--- End quote ---
1) Be careful, i tried a value of 10 ms and that worked several times for me, however the problem was still present; i think that the correct value should be as near as possible to 10 ms but to be really sure it needs several trying.
2) I'll try asap and i'll let yow know
EDIT: Yes you're right.
ThibG:
Hm, I tried rockbox again today and... It won't boot (I tried 4 times, "file not found"...)
I have the same D2 as before (a 4Go one), but I have the 2.57 firmware now.
shotofadds:
Don't worry, the different firmware version won't matter - it'll be the same old "unreliable NAND driver" problem. I'm working on a new version which should improve things, and I'll keep you posted when there's something to test (hopefully in the next week or two).
man.dovvn:
I have also experienced file corruption using the supplied firmware.
Perhaps code could be written to calibrate file access based around an earlier thought. It was proposed here that Rockbox would write known unique data to all memory addresses, and then read back the data, in order to map the memory. If this is still a feasible solution, code could be written to do this, then save the map file and use it to access memory addresses correctly. It would be time consuming to map, and it'll slow down the whole firmware to use a memory look-up table, but it may be better than nothing.
shotofadds:
That's not really an option, since the mapping between logical block (LBA) and physical NAND address is dynamic and changes as data is written to the NAND. This is how the OF implements wear levelling, by ensuring that data is written evenly across different physical blocks. Unfortunately it also makes our job rather more complicated...
But like I said, check back in a week or two as I'm hopefully not far off a breakthrough in this area.
I'll try to keep the TelechipsNAND wiki page updated with any findings, but at the moment that's a secondary concern, after making the damn thing work in the first place. :D
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version