Rockbox Development > New Ports
Cowon D2
Rapide_23:
I just flashed my D2 to the D2+ firmware with rockbox.
However, when I try to boot rockbox, all I get is "*PANIC* Max NAND write caches reached".
I'm using a 16GB D2. Did I not install something properly, or is rockbox still not quiet ready for the 16GB?
Any help would be greatly appreciated.
shotofadds:
--- Quote from: buk on March 21, 2009, 04:56:19 PM ---Maybe the SS_CTRL value should be increased. It seems to be used to determine if the stations signal level allow stereo decoding. With the actual value, I can hear some noise with some stereo stations.
In the OF, the SS_CTRL seems to be higher than rockbox.
--- End quote ---
I always found it quite annoying that the OF seems to need a particularly strong signal before it will enable stereo. The current behaviour in Rockbox seems to match what I'd expect from a portable device, so I think we should leave it how it is (and there's always the Force Mono option if you prefer it...)
--- Quote from: hpfmn on March 25, 2009, 03:58:28 PM ---Is it alowed to ask whether there is any development on the sd card driver (reading would be nice and write extreamely awsome!)?
--- End quote ---
You can ask but you might not necessarily get an answer! There was some work done on an SD driver a while ago, but I'm not sure of its current status.
--- Quote from: markV on March 26, 2009, 11:53:16 PM ---First (neophyte) question: I know Rockbox bootloader is patched in the original firmware with mktccboot, does that mean Rockbox is like a "parasite" application ? I mean does Rockbox send commands to the hardware through the original software or directly to the hardware ?
--- End quote ---
Rockbox is a complete firmware replacement, so it doesn't use any part of the original firmware. The only reason we patch the original firmware at all is to provide the dual-boot function. You could potentially flash just Rockbox, without the Cowon firmware, but that would be rather silly at this stage...
--- Quote from: markV on March 26, 2009, 11:53:16 PM ---Second question: I remember having seen somewhere on this site something about database corruption being related to a bad bootloader patching or something... Is that what I'm experiencing on the "original firmware side" (complete database corruption, like 'hpfmn' wrote) or this database corruption is really just from the new Cowon 2.59 firmware ?
--- End quote ---
It's extremely unlikely that Rockbox could affect anything in the Cowon firmware. I've never seen any reports of this or "bad bootloader patching"...
--- Quote from: markV on March 26, 2009, 11:53:16 PM ---Ok, now some observations I made (could this help) on my Rockboxed (v. r20457-090322) 8GB D2:
1- when the backlight goes to sleep there is still a faint (so faint !) amount of light emitted when using a white background theme (like iCatcher)
2- I still got the two-bottom-lines-at-top problem, like once in 20 boots or so (random for sure)
3- I have a weird problem when getting the power button back from the locked position: most of the times the player goes to a paused state but gets back to the main menu and can not resume playing. A less frequent symptom is the player shutting down after a couple of clicks.
--- End quote ---
1. Yeah, I see that too. It's because the LCD isn't actually being switched off, only the backlight. This is intentional for some Rockbox targets, as the screen can still be read with no backlight. I should fix that, as it's wasting power having the LCD switched on all the time.
2. It looks like there's still a timing problem in the LCD init code, but it seems to happen much less often now. I need to study the OF code again to see how they do it. :P
3. This is a flaw in the keymapping. To get out of hold mode you need to slide the hold switch and then press another button to see the screen. If you slide the switch all the way over, it acts as a POWER key press - this is mapped to STOP, which will stop playback and exit to the menu. I'm not sure how best to solve that.
--- Quote from: Pivot on March 27, 2009, 11:54:52 AM ---Hi, I am looking for pre-built mktccboot (with associated bootloader.bin). I would try Rockbox on my D2 and haven't develop's environment.
--- End quote ---
First of all, Rockbox isn't really ready for general use (mainly just for development / testing at the moment) so we haven't made easy installation tools available yet. I did intend to provide some pre-built tools to aid people testing builds, but I wanted to wait until the NAND code was more reliable. It's not ready yet...
--- Quote from: Rapide_23 on March 28, 2009, 01:16:28 AM ---I just flashed my D2 to the D2+ firmware with rockbox. However, when I try to boot rockbox, all I get is "*PANIC* Max NAND write caches reached".
--- End quote ---
What version of the bootloader did you use to patch the firmware (or did you download someone else's pre-patched build)? There was a fix a few weeks ago (r20168) which might help.
Rapide_23:
--- Quote from: shotofadds on March 28, 2009, 07:04:56 PM ---What version of the bootloader did you use to patch the firmware (or did you download someone else's pre-patched build)? There was a fix a few weeks ago (r20168) which might help.
--- End quote ---
I'm using the one on iaudiophile: http://www.iaudiophile.net/forums/showthread.php?t=26360 (The patched 3.02 in the download link at the bottom of the first post).
shotofadds:
That's the problem when other people distribute builds - I don't know exactly what version it is, or what other changes it might contain. So it's pretty much impossible to debug.
Are you able to use tcctool? If so could you try a debug build I made a few weeks ago for someone with a similar problem. See here.
Rapide_23:
--- Quote from: shotofadds on March 28, 2009, 08:11:30 PM ---That's the problem when other people distribute builds - I don't know exactly what version it is, or what other changes it might contain. So it's pretty much impossible to debug.
Are you able to use tcctool? If so could you try a debug build I made a few weeks ago for someone with a similar problem. See here.
--- End quote ---
Thats the problem. I don't know how to build a bootloader :'(
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version