Rockbox Development > New Ports

Philips GoGear SA6045

<< < (2/2)

Orac:
It seems that the TCC8200 has its own LCD driver built in, so I wont have to write any drivers for that.

shotofad: What program are you using for programming/compiling?

EDIT: Ive figured out that turning the device off, holding down the + button (volume) and plugging it in windows recognizes the device as "Philips GoGear SA6045 Recovery", I installed the VTC drivers from the SDK and was able to download the firmware using FWDN. It dumped the file as mem.ini and it is 512kb, if I open the file in notepad its a bunch of gibberish.

I will be using TCC-TOOL as soon as it is compatible rather than the software from the SDK though.

Any input from anyone else?

Bagder:

--- Quote ---It seems that the TCC8200 has its own LCD driver built in, so I wont have to write any drivers for that.
--- End quote ---

No, it has a built-in LCD controller. You need to write a Rockbox driver to talk with that controller.

shotofadds:

--- Quote from: Orac on January 23, 2008, 06:52:40 PM ---It seems that the TCC8200 has its own LCD driver built in, so I wont have to write any drivers for that.
--- End quote ---
You would still need to write the low-level drivers to interface with the 8200, though this should be markedly simpler than directly interfacing with the LCD panel. You will probably also need to find out how to enable the power supply to both the LCD panel and backlight. The only way to do this is to find a good disassembler and figure out how the original firmware works.


--- Quote ---What program are you using for programming/compiling?
--- End quote ---
Everything you need is in the Rockbox build tree - for info see the wiki: http://www.rockbox.org/twiki/bin/view/Main/DocsIndex#For_Developers

Did you take a look at my D2 patch on Flyspray (FS#8420)? That will give you an idea of the kind of changes you would need to make.

linuxstb:

--- Quote from: Orac on January 23, 2008, 06:52:40 PM ---EDIT: Ive figured out that turning the device off, holding down the + button (volume) and plugging it in windows recognizes the device as "Philips GoGear SA6045 Recovery", I installed the VTC drivers from the SDK and was able to download the firmware using FWDN. It dumped the file as mem.ini and it is 512kb, if I open the file in notepad its a bunch of gibberish.

I will be using TCC-TOOL as soon as it is compatible rather than the software from the SDK though.

--- End quote ---

Adding support to tcctool for your device is something you'll need to do.

There are two pieces of information you will need to discover - the USB IDs of the device in recovery mode, and the value written to the SDRAM CFG register.

So far, all devices have the USB vendor ID 0x140e, and the product ID is either 0xb011 or 0xb021.  This should be easy to find out - just attach the device to your computer in recovery mode and use whatever mechanism (e.g. lsusb) your OS has for viewing attached devices.

The SDCFG value is harder.  For the D2, this was given by Cowon in the instructions accompanying the firmware recovery tool they gave (on a limited basis) to some users.  For other devices, a USB log of the official recovery tool gave this value.

If you've been able to use the Telechips FWDN application to talk to your device in recovery mode, then you should be able to retrieve the value from the settings there.

Once you have this info, just add it to the devices[] array near the top of tcctool.c (the 0x20000000 value in each line is the default start address of DRAM, which afaik is the same for all TCC chips, but check your datasheet).

fldash:
I know this is an old topic, but I'd really like to get this port going for my SA6045. 

I'm trying to understand where to start, especially with regards to the second step on getting the SDCFG value...

Navigation

[0] Message Index

[*] Previous page

Go to full version