Phillips GoGear HDD6330

[b0hoon]

Seeing all of the progress on the HDD6330 port makes me want to get another unit for myself. I gave mine to lowlight.

If I find another unit, I'll come back in full swing for testing and contributions again.

That would be great. I don't know if i'm able to finish what i have started, cause my hdd6320 is unfortunately partially broken.

(EDIT) Would anyone say that the port is far along enough to be good for everyday use? If so, I'm thinking of adding in support for installing builds via Rockbox Utility.

The bootloader doesn't want to load the OF, so maybe it would be better to wait for a solution before adding it to the Rockbox Utility?

[LambdaCalculus]

The bootloader doesn't want to load the OF, so maybe it would be better to wait for a solution before adding it to the Rockbox Utility?

IIRC from the time I had the HDD6330, USB worked quite well from within Rockbox on it. If such is the case, perhaps we could just ditch any notions of dual-booting and make it a proper firmware replacement on this device? Such is already the case for the iAudio devices and the Gigabeat F/X. Thoughts?

[scallopedllama]

The OF Requires that the user sync the device with their computer using an outdated version Windows Media Player, 10 or 11.
I think that this alone would make it ok for Rockbox to act as a full replacement of the OF, since the OF isn't even supported by Philips anymore.

Also, I think it'd be desirable to get plugins too.. no keymaps for them yet

[LambdaCalculus]

I need another HDD6300 in order to work on plugins first.

Luckily, and unlike the SA9200, the LCD on the HDD6330 is the same resolution as a few other devices (220x176x16), so all it takes to get plugins working is just to add in keymaps. Once that's done, enabling them should make the port fully functional.

[b0hoon]

Today i found the magic numbers in the registers (r0,r1,r2,r3) in order to boot the original firmware from the Rockbox bootloader. I used special mi4 image (the buzzer was clicking and gave me the right values, bit after bit). I will commit it ASAP. I'm not sure if i can do it this week, cause it's freeze time.

[saratoga]

Today i found the magic numbers in the registers (r0,r1,r2,r3) in order to boot the original firmware from the Rockbox bootloader. I used special mi4 image (the buzzer was clicking and gave me the right values, bit after bit). I will commit it ASAP. I'm not sure if i can do it this week, cause it's freeze time.

We branched, so the freeze is over.   Plus the free doesn't apply to targets that aren't being released yet.

[LambdaCalculus]

Have you actually checked that 64MB works?  I know that the documentation says 64, but when I tried before it didn't work. Try loading a playlist so that it will buffer more than 32MB, like a bunch of flac files.

I just tried a build on my HDD6330 that I built from SVN (r28439). In tools/configure it's configured with 64MB, but playback crashed when I tried loading files. I'm setting it back to 32MB for now until we absolutely know for sure that this device does indeed have 64MB RAM.

[b0hoon]

Have you actually checked that 64MB works?  I know that the documentation says 64, but when I tried before it didn't work. Try loading a playlist so that it will buffer more than 32MB, like a bunch of flac files.

I just tried a build on my HDD6330 that I built from SVN (r28439). In tools/configure it's configured with 64MB, but playback crashed when I tried loading files. I'm setting it back to 32MB for now until we absolutely know for sure that this device does indeed have 64MB RAM.

I've checked it on mine before committing and it works. The buffer is filled completely, i can rew/ff every song. Sometimes i was listening it for about one or two hours without a problem (when sitting at my PC). Maybe the HDD6330 doesn't have 64MB of memory (or some version of it)? Maybe it would be good idea to look inside it. IIRC my HDD6320 has the Samsung K4S51163PF, but i will disassembly it once again.

[LambdaCalculus]

I was discussing this with kugel on IRC before. Perhaps some models of the HDD63x0 are built with the Samsung K4551163PF chip, and there are some that have the Samsung K4S56163PF chip that the HDD16x0 models use. This means that we can do a check at startup for which chip is in the device and set the buffer accordingly, like on the iPod video build.

The IRC conversation starts here: http://www.rockbox.org/irc/log-20101101#23:19:50
You may want to also look at SVN revision r27960 to see if maybe we can implement the same trick for the HDD63x0.

[torne]

As long as the 32MB of ram is mirrored in a 64MB region of address space then the same trick will work. r27937 contains the code to detect the ram size.

[scallopedllama]

I've been using r28308 configured to used 64 mb of ram for a couple weeks and have had no crashing at all.

[LambdaCalculus]

I've been using r28308 configured to used 64 mb of ram for a couple weeks and have had no crashing at all.

Is your device the HDD6320 or HDD6330?

[scallopedllama]

Back says HDD6330/17

[LambdaCalculus]

scallopedllama, per a few IRC conversations, I just may have had a stroke of bad luck with the initial build I ran last night. I'm going to build another build tonight with 64MB enabled again and try it once more. If it does work, I'll set tools/configure to build it with 64MB again.

In the meantime, can you do me a favor and tell me if you've noticed the LCD refresh to be a bit sluggish in Rockbox? Mine appears sluggish, but it could be because we haven't really optimized the LCD drivers enough (and I don't know very much about the hardware or where to poke into to optimize the speed).

In the meantime, anyone who wants to try out the port can download it from here and follow the installation instructions on the page: http://www.rockbox.org/wiki/GoGearHDD6330#Installation_steps_for_HDD63x0
Plugins are enabled and have keymaps, but please test and tell me if any changes need to be made to the keymaps; a few are a little crude.

[LambdaCalculus]

Locking this thread now, as this port was just promoted to Unstable. Any further changes or updates will go straight into SVN and be reflected on the front page.

Installation instructions are currently available in the above link. Any installation questions should go into the appropriate subforums.

If you want to help with development, get in touch with us using IRC or sign up for the development mailing list.