Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
translations translations
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Welcome to the Rockbox Technical Forums!

+  Rockbox Technical Forums
|-+  Rockbox Development
| |-+  New Ports
| | |-+  Philips GoGear Opus (SA1OPSxxK/02 models)
« previous next »
  • Print
Pages: [1]

Author Topic: Philips GoGear Opus (SA1OPSxxK/02 models)  (Read 5017 times)

Offline juannm

  • Member
  • *
  • Posts: 1
Philips GoGear Opus (SA1OPSxxK/02 models)
« on: July 25, 2011, 09:52:09 PM »
Hello all! My name is Juan Navarro, I am from Spain. I'm new in this community and would like to work in a new port. I have programming skills, so coding shouldn't be a problem.

I own a Philips GoGear Opus, model SA1OPS16K/02. This device has one of the worst user interfaces that i have ever seen, so soon after using it i started thinking on replacing the firmware with something better; here is where Rockbox comes into the scene. I like the idea of a community-developed firmware and the customisation posibilities that it brings. It's a pity that Rockbox is only available for mainly old devices, due to the very difficult task that porting is and the long time it takes... I would like to port it to my MP3 player as well. I wrote an initial document with info about the device, and took some photos of the PCB (sorry no flatbed scanner here, but the photos are taken without flash and a lot of ambient light).

The wiki page is here: http://www.rockbox.org/wiki/GoGearSA1OPS

And now I'd like to gather the missing information about the PCB, as well as being directed on what should be my next steps from here.

First question: I read HERE about placing in firmware/target/<cpu>/<manufacturer>/<model>/ all the platform-specific code. Ok, now: how do I know what must be that code? I mean, do I have to write code for every hardware chip which is in my platform? I see other GoGear devices have code for just LCD and power management... other things like Audio chips or, I don't know, memory controllers and such, are already implemented in the generic part of the source tree?
Logged

Offline pamaury

  • Developer
  • Member
  • *
  • Posts: 508
Re: Philips GoGear Opus (SA1OPSxxK/02 models)
« Reply #1 on: July 26, 2011, 10:20:23 AM »
Hello,
rockbox has some code for some chip but not for all of course. Basically, there are two possible situations:
  • Rockbox has code for your main SoC and you only need to write code for the "device" specific part
  • Rockbox doesn't have code for your main Soc and you will need to write code for both the SoC and device
Your photo shows that the main SoC is TCC8300 and unfortunaly, rockbox only has code for TCC77x and TCC78xx as far as I know so you are in the second situation. For the NAND memory, usually the SoC has a NAND interface so there is no need to worry. For the SDRAM, it depends on how the device boots and whether it initializes the RAM or not. The "0319" chip is probably the si4700 tuner chip for which we have a driver. The CS42L51 seems to be a stereo codec for which we do not have a driver but a close one (42l55).

So basically, you want to find the datasheet for the TCC8300 because that's the most important part of the device for which you'll have to write everything as far as I know.

Good Luck ! Don't hesitate to got on #rockbox irc channel to gather some help/advise.
Logged
Please don't PM me, use our IRC channel instead.

  • Print
Pages: [1]
« previous next »
+  Rockbox Technical Forums
|-+  Rockbox Development
| |-+  New Ports
| | |-+  Philips GoGear Opus (SA1OPSxxK/02 models)
 

  • SMF 2.0.19 | SMF © 2021, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.114 seconds with 23 queries.