SAMSUNG YH-920

[pyro_maniac]

Thank you for that hint. But my problem with the original bootloader is the validation, like you can see in the posts befor. I thought i could replace that bootloader with a multibootloader without validation.
So that seems to be impossilble.

Am i right when i say that the pp5020.h defines all codes for the firmware?
I dont understand how can find out that for my device.

EDIT: Sorry that i ask that newbie questions in here. Or should i make a thread in an other place?

[Bagder]

I think you're better off learning how the other mi4-based players work.

In Rockbox we typically don't meddle with the original bootloader but simply provide our own mi4 instead, and that mi4 is our bootloader that then can either load and run Rockbox or load and run the OF.

The original bootloader does have a "validation" check of the mi4 file but we've already found out how to circumvent that check and mi4code helps you with that.

[pyro_maniac]

Yes and i also red your page for mi4 files. But the codes you wrote there are quite different to mine.
And in the typical rockbox way i cant make it work, because i cant replace the bootloader.

[Bagder]

Then read my text again. I did not suggest you should replace any bootloader.

[pyro_maniac]

I tried to read the mi4 file header and compared with your example on your mi4 page but my version seems to be different.
Should i post my file or the header?

[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: [Select]

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


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 ...

[pyro_maniac]

The rockbox files didn't create a tmp folder.

I copied all files of a H10 5G Build into the system folder and in the root folder, created a tmp folder on both directories and started the player but there happened nothing new.
/EDIT: And i had a file 7 on the device for firmware.

/EDIT2: After this test, i had to rebuild my device completly. I don't know why.

[wolly-p]

If you are really serious about porting rockbox to the YH-920, it won't have been the last time you completely re-built your device 

You need to put together a new build, starting with an existing one which allows at least harddisk and display access, otherwise it's going to be pretty difficult to get anywhere. The existing H10 build provides a good starting point (PP5020 player), but in my previous thoughts I made a mistake with the display, so you could not see anything. Here are my findings:

1. LCD:
I could find "S4E1 5002" on the plastic stripe, which means that according to this it is
identical to the LCD used in Iriver H1xx .

2. Power chip Linear LTC3455
also used in Meizu M6, you might re-use some drivers from there.

3. Audio AKM AK4537VN
I could not find any other player with this component, so here you have to start from zero. Seems to be well documented, however.

4. mi4 format
The header of the two most recent Samsung mi4-firmwares seem to fully comply to the 01020100 "standard" as indicated here, without the exception at 0x18 , which only existed for the earlier two firmwares.

If you would like to continue (but pls consider if it's worth it, I won't be able to help significantly), read here and there, setup your development environment, start with the H10 5GB port, replace the display driver with (hopefully) an appropriate one from H1x0, and watch, smell, and listen. Good luck!

[pyro_maniac]

how can i change the powerchip in a h10 build to a meizu powerchip?

[wolly-p]

Did you check what happens in 'config-meizu-m6sl.h' and related files? You can also ask in the Meizu M6 forum thread. For he first tries, just comment it out or leave as it is if you do not find anything particular to the LTC3455.

[pyro_maniac]

Yes i made a diff of both configurations. After that, i tried to learn something more about the structure. I thought that i only have to change the small part for the power chip but its much more different.Yes i made a diff of both configurations. After that, i tried to learn something more about the structure. I thought that i only have to change the small part for the power chip but in the meizu firmware the powermanagment seems not to be separated.

Maybe i will ask in the meizu thread later on. First i will try on my own.