Rockbox Development > New Ports

SAMSUNG YH-920

<< < (11/46) > >>

wolly-p:
pyro_maniac,

as indicated on the wiki page there are at least three different original mi4 firmwares available for the YH-920. Can you tell us which one you use (or otherwise pls upload it to some place and post the link here)? Maybe I can find out some things for us.

Do I understand you correctly that up till now, you have not been able to run any other than the original mi4-firmware on the device because you always get a "corrupt firmware" error?

As mentioned by Bagder and others, we should progress as follows:

1. get any other than the original firmware (initially iRiver H10 port) accepted by the bootloader
2. modify existing H10 port to include hardware components used in the YH-920
3. disassemble / reverse engineer original YH-920 firmware to build new yet unknown hardware drivers
(2+3 iteratively)

pyro_maniac:
thanks wolly-p for your interest.

I am using a YH-920 with a Napster branding and a v1.05 bootloader. Its got a sticker with the name YH-920GS on the back, maybe this is need to know.

I attached a zip file with the complete filesystem of the device after a rebuild with the recovery tool in it. I also made the first steps to reverse engeneer it, as i wrote in the upper part.
I never ran an other firmware on the device. No other original and none of my own.

At the moment i am trying to learn more about the firmware in rockbox and how to get involved in rockbox.

/EDIT: I loaded up the file because its bigger than 256kb. Download here

wolly-p:
pyro_maniac,

ok then. Do you have time for some trial and error? I don't, unfortunately, but I have uploaded a few mi4-files here for which we need to check if they will be accepted by the YH920 bootloader, and if so whether they at least create files on the disk (they will crash/freeze, but hopefully it will not matter  :-\). Rename the mi4-files individually to PP5020.mi4, replace the original PP5020.mi4 in the System directory, and let us know what happens.

/EDIT And here are all the original mi4-firmwares for the YH920 I know of (newer than your version), including the bootloader.

pyro_maniac:
OK thank you for your work. I am so happy that somebody is helping my getting on the way.
I have tested all firmware files you uploaded. Here are my results:


--- Code: ---040731 PP5020.mi4:   - loaded
                     - napster branding
                     - works completly

040810 PP5020.mi4:   - loaded
                     - napster branding
                     - works completly

040924 FW_YH920.mi4: - loaded
                     - plays music
                     - no radio function inside

050128 FW_YH920.mi4: - loaded
                     - displays the samsung logo
                     - warning for currupt font files

105t920n.mi4:        - warning for currupt firmware

H10-5.mi4:           - displays the samsung logo
                     - nothing else happens

H10to920.mi4:        - loaded
                     - clear Screen
                     - backlight on

H10to920n.mi4:       - warning for currupt firmware

rbh10_5.mi4:         - loaded
                     - clear Screen
                     - backlight on


--- End code ---

There is something different else but i noticed that to late. There is a "tmp" folder generated automatically. The difference is that the place of this folder is sometimes in the root folder and sometimes in the system folder. Don't now if this is relevant.

What can you see in this results? is there something else i can do?

wolly-p:
sounds promising  :)

To explain shortly:

1. files 1+2 are Napster branded firmwares -> work as expected
2. files 3+4 are Samsung branded firmwares -> work, but probably some problems with built-in bootloader in Napster device (just guessing)
3. files 5+8 fail the bootloader CRC check -> not relevant anymore
4. file 6: original Iriver H10-5GB-version firmware, to see whether it gets loaded -> not relevant anymore
5. file 7: Rockbox build for H10-20GB-version with adapted header -> does it generate /tmp ?
6. file 9: Rockbox build for H10-5GB-version with adapted header -> does it generate /tmp?

For files 7+9, which seem to get loaded, we need to know more what happens. I would suggest to start with H10-5GB-version. Could you put the whole Rockbox build on the disk but with file 9 above as PP5020.mi4 and tell us what happens?

Remember that due to different hardware components in the devices the Rockbox H10 build can only do initial things like (hopefully) recognising PP5020 and ATA interface and writing some files to disk, until it stalls or crashes.

After that, real work begins ...

Navigation

[0] Message Index

[#] Next page

[*] Previous page