Welcome to the Rockbox Technical Forums!
That pretty much looks like dram controller misconfiguration which is odd considering that we relay on init performed by original first stage bootloader and don't touch it. There are two things you can try (depending how skilled you are):1) Build hwstub for rk27xx (utils/hwstub/stub/rk27xx), convert binary to rkw format (according to convert_to_rkw.txt) and copy it as rockbox.rkw (this will preserve possibility to boot original firmware). Then you can boot this debug stub and poke ram and ram config with help of PC side utilities (/utils/hwstub/tools/hwstub_shell and /utils/regtools/qeditor). This may give a clue whats wrong.2) Disassemble BASE.RKW to see if it performs dram controller init (previous versions didn't do that)You can try to catch me on IRC if you need assistance.
we relay on init performed by original first stage bootloader and don't touch it.
Hello!My name is Eugene and I found your account on Rockbox forums while trying to install Rockbox firmware on HM-603. Yeah, it's a really old stuff and your wrote there a years ago, but the problem is still actual.It seems that my HM has the same problem with a wrong display type so there is a white screen after loading Rockbox. Here https://forums.rockbox.org/index.php?topic=51233.0 you wrote that you reconfigure the script and successfully built a 4MB build. As I understand, it works well and you could install Rockbox firmware on your HM-603, right? Could you please share configured build in this case? That topic on rockbox forum was literally the only one possible solution of problem that I found.
190|hifimanhm60x) target_id=79 modelname="hifimanhm60x" target="HM60X" memory=16 arm7ejscc tool="$rootdir/tools/scramble -rkw -modelnum=79" bmp2rb_mono="$rootdir/tools/bmp2rb -f 0" bmp2rb_native="$rootdir/tools/bmp2rb -f 4" output="rockbox.rkw" bootoutput="bootloader.rkw" appextra="recorder:gui" plugins="yes" swcodec="yes" # toolset is the tools within the tools directory that we build for # this particular target. toolset="$genericbitmaptools" # architecture, manufacturer and model for the target-tree build t_cpu="arm" t_manufacturer="rk27xx" t_model="hm60x" ;;
I read somewhere that it is possible to close the contacts on Samsung chip on inner plate and somwhen it could help, so I'll try to find out more about. Otherwise it seems that I have to find the donor or buy the whole player.
Page created in 0.067 seconds with 22 queries.