Rockbox Development > New Ports
Cowon D2
Yeeze:
I made some tests with the "0" firmware, and it is actually a basic firmware, I can play music and browse the content, but it is quite messed up, there are a lot of bugs with rendering, and not all features work...
Since I installed the resource file from 3.51, not all pictures are loaded, but I think, the the file in folder "1" only updates the firmware(installs the new features and stuff), so isn't the file in folder "0" the important one?
Anyways next I will see if a formated D2 can install only the file from folder "1", I'm just a little scared that this could brick my D2, what do you think?
linuxstb:
Yeeze,
If I was you, I wouldn't play too much with the firmware updates, although the recovery tool looks like it should help you recover from any mishaps.
In terms of porting Rockbox (which after all is the subject of this thread), the most important thing is being able to test-run code without permanently installing it on the device (so you can easily recover when it inevitably crashes) - which is what tcctool should hopefully do.
punit:
Following linuxstb's instructions, I was successfully able to upload firmware d2N.bin from the "1" folder.
The D2 started successfully, after the upload.
I had to change tcctool.c to increase the maximum size of allowed firmware.
Hurray!
Now that we can upload programs to the D2 and transfer control to it - What's next on the agenda? Anybody have a working toolchain and a rockbox compiled binary for testing?
saratoga:
Probably figure out how the LCD works and then write a driver for it so that you can print things to teh screen.
Bagder:
For toolchain, run the tools/rockboxdev.sh script in the rockbox source tree to get that setup.
Most often, we first work on getting the bootloader to build and run, and it more or less implies working LCD and button drivers, together with the ability to read the nand flash (so that rockbox can be read from it).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version