Philips GoGear 3125

[saratoga]

I read the wiki on how to work for a new port several times now... and also the Wiki PortingHowTo but I don't understand what I exectly have to do after I found everything about the Hardware... Do I only have to take an existing Built and change the values? Or do I have to write a totaly new Firmware?

You'll have to write drivers for all the hardware thats not already supported in rockbox.  Of course, to do that, you would need to get a compiler first.

[PinguinXY]

okay and where do I get a compiler? I just know the Linux Compiler :-D


btw. Is anywhere a List of all supported Hardware?

[saratoga]

okay and where do I get a compiler? I just know the Linux Compiler :-D

As I said above, it would appear that one does not exist, making this step literally impossible.

btw. Is anywhere a List of all supported Hardware?

Check the target tree in the rockbox source.  Most of it is there.

[AlexP]

thank you for introducing me into another part of capitalism :-D I think I'll have to pay for the Datasheet... 12$ isn't too much... especialy now... ( I think one € is aboeut 1.5$)

The Partt with Freescale I don't understand... What does this contract me to us?
(I'm not a native Englishspeaker and didn't understand everything :-/ )

In the English speaking world, the comma (,) is not the decimal sign, the full stop (or point, or period) (.) is.  Therefore $12,000 is 12 thousand dollars, not 12 dollars.  For you it would be written $12.000,00 - we write $12,000.00

There is another problem - even if they let you pay for it, it would be under a non-disclosure agreement (NDA).  This usually means that you cannot tell anyone else what is in the datasheet, nor publish any code written as a result of information in the datasheet.  Therefore it remains useless to us!

okay and where do I get a compiler? I just know the Linux Compiler :-D

You need a compiler that will compile code for the CPU architecture of your port, e.g. X86, ARM, m68k, etc...

Unfortunately there does not seem to be a free compiler for the architecture in your player, and therefore this project is essentially impossible.  It doesn't matter how much code you write if you cannot compile it.

[PinguinXY]

Do you think that it could happen anytime that we get a compiler or do I have to pray for a wonder?

(next time I will first look into your Database for a player and then buy one :-D )

[gevaerts]

Compilers are like rockbox ports unfortunately. They don't fall out of the sky, and I guess the compiler people have the same datasheet-getting problems.

[PinguinXY]

  :-/ It's not fair... they supply us with bad firmware and a lack of codecs for our players and we aren't allowed to make more than using this stupid crap...

[LambdaCalculus]

I'm sorry, but whining about it isn't going to make a free toolchain magically pop out of thin air. That's the reality of it all, and there are a great many Rockbox ports planned and started by people that go nowhere for one reason or another.

Twelve thousand US dollars is a LOT of money, but that money is the only way you can get that toolchain. But it's still a waste of time and money because you can't share the toolchain with us after you purchased it. All of the existing ports we have now happened because there are freely available toolchains to allow us to code for those platforms (SH-1 for the Archos players, Coldfire for the iriver H100, H300 and iAUDIO, ARM for the iPods, Sansas, H10, and Gigabeats, and TCC for the Cowon D2 and some others).

It's not our fault that SigmaTel and Motorola kept the documents and tools for the SigmaTel chipsets a secret. In fact, almost no company will ever share internal documents with open source developers. One exception was Austria Microsystems, the designers of the audio chipset in the Sansa e200 series. While there are datasheets for a lot of the hardware in the non PortalPlayer targets, we had to reverse engineer a few things, and while it's possible to reverse engineer the STMP chips, compiling for them will not happen without that toolchain.

(EDIT: BigBambi pointed out my mistake with available datasheets... thanks!)

[AlexP]

It's not our fault that SigmaTel and Motorola kept the documents and tools for the SigmaTel chipsets a secret. In fact, almost no company will ever share internal documents with open source developers. One exception was Austria Microsystems, the designers of the audio chipset in the Sansa e200 series. We had to reverse engineer nearly everything we worked on, and while it's possible to reverse engineer the STMP chips, compiling for them will not happen without that toolchain.

There are datasheets available for much of the hardware in the non-portalplayer targets....

[LambdaCalculus]

/me quietly goes to get more coffee to caffeinate his brain cells  

[GodEater]

Also, I think of the manufacturers that have proven helpful, Austrian Microsystems were the *least* helpful, since they made people go to their offices in person, and STILL they had to sign an NDA to get at the documents.

[LambdaCalculus]

Ahh, yes! I remember that now.

[PinguinXY]

So do you REALY think it is possible to port rock box on a GoGear? I am not familiar with this kind of development... You need to write in clear and easy to understand sentences :-D I am a noob in this scene xD

[AlexP]

So do you REALY think it is possible to port rock box on a GoGear? I am not familiar with this kind of development... You need to write in clear and easy to understand sentences :-D I am a noob in this scene xD

No, without a compiler it is not possible.

[PinguinXY]

Do you think I can do anything else to make work easier in the future in the case that someone is able to write a compiler because of a change in philips opinion?