Rockbox Development > New Ports
Cowon D2
dasimmet:
thanks for help
holding the power swich was what i tried firt time...
i dont know how this old version could get on my d2, i downloaded it from the info page.
now its running fine
Dicky Dave:
Hi Guys,
I just tried installing Andiator's pre-built patched binary for v3.57 (rev17784) and I am getting a similar error to that reported by talex and couple of weeks ago:
--- Code: ---*PANIC*
BMPM total_banks m
ismatch
--- End code ---
However, this is on a 4GB D2 not a 16GB. I had my 16GB SDHC card in at first and thought this might be the problem. So I tried again with it removed but kept getting the same problem. Any ideas?
shotofadds:
Interesting. Could you try uploading this binary with tcctool? It's one that I built for debugging the 16Gb support, so it should show some diagnostic information when you run it.
Let me know what shows up...
Dicky Dave:
Hi shotofadds,
Here is the output:
--- Code: ---Bank 0: Manuf, 0xEC Id 0xD5
Bank 1: Manuf, 0xEC Id 0xD5
Bank 2: Manuf, 0xEC Id 0xD5
Bank 3: Manuf, 0xEC Id 0xD5
Banks 0,1 have same manuf. id
Banks 0,2 have same manuf. id
Banks 0,2 have same UID
Total banks: 2
BMP tag: 0x42 0x4D 0x50 0xFF 0xFF
--- End code ---
The other thing that might be worth noting is that my 4GB D2 is one of the earliest revisions (I think it is 1.0, but the revision is on the box and I cannot find it at the moment). It was bought in Feb 07.
shotofadds:
--- Quote from: Dicky Dave on June 26, 2008, 07:00:01 AM ---
--- Code: ---BMP tag: 0x42 0x4D 0x50 0xFF 0xFF
--- End code ---
The other thing that might be worth noting is that my 4GB D2 is one of the earliest revisions (I think it is 1.0, but the revision is on the box and I cannot find it at the moment). It was bought in Feb 07.
--- End quote ---
Ah, I've seen that before on a 2Gb D2, running firmware 2.20. On most D2's the first 0xFF shows up as 0x4D (the ASCII code for 'M') and the second is the number of NAND banks present. It's easy to fix - I'll to update the code to ignore those last two values if they're 0xFF.
I guess it's dependant on which firmware version originally formatted the drive - newer versions fill in those two values, older ones don't.
EDIT: This version should work for you, it's v3.57 patched with a modified bootloader.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version