Rockbox Technical Forums
Installation / Removal => Manual Installation => Olympus - Installation/Removal => Topic started by: cereal_killer on April 23, 2020, 02:58:59 PM
-
I have a m:Robe 500 with OF version 1.03 and I followed the instructions on the wiki using the well tested method. When Rockbox launches it hangs on the boot screen:
Rockbox boot loader
Version r20941 :20942M-090516
ATA
disk
mount
Loading firmware
Lenght: E446C
Checksum: 578D8F5
Model name: m500
Loading rockbox.mrobe500
Sum: 578D8F5
Only a reset helps.
How can I start Rockbox?
-
What version of Rockbox are you running? The m:Robe is one of our more neglected targets, so it's quite possible that we've inadvertently broken it since whoever last tested it.
-
What version of Rockbox are you running? The m:Robe is one of our more neglected targets, so it's quite possible that we've inadvertently broken it since whoever last tested it.
I downloaded a dev build some days ago: version 84624e14f8-200415
So you mean it is a problem of the Rockbox build not of the bootloader? I will try to reinstall and use a recent build.
-
I reinstalled everything from scratch using the latest dev build. Same result, but with slightly different text on the screen.
Rockbox boot loader
Version r20941 :20942M-090516
ATA
disk
mount
Loading firmware
Lenght: E447C
Checksum: 578E1E5
Model name: m500
Loading rockbox.mrobe500
Sum: 578E1E5
When I install the modified firmware using the Windows updater, the information on the screen of my PC says version 1.05, but when checking the version on the m:Robe it says 1.03. Is this intended?
My next step is to find out the latest working build. Can I do this with bisect? https://www.rockbox.org/wiki/UsingGit#How_do_I_bisect_using_git_63
-
Does anyone have a working build for this player and would share it with me? That would be nice.
-
My next step is to find out the latest working build. Can I do this with bisect? https://www.rockbox.org/wiki/UsingGit#How_do_I_bisect_using_git_63
You should definitely be able to bisect, but I think your first step should be figuring out whether the problem is in the bootloader itself or the rockbox image.
-
You should definitely be able to bisect, but I think your first step should be figuring out whether the problem is in the bootloader itself or the rockbox image.
If it is the bootloader, then I am at my wit's end. But I thougt start with trying a build that is known to work.
-
I found the first commit that prevents rockbox booting on the m:Robe. Here ist the bisect output:
b0de98ad3b1391ec0dfe4f8eced0a6833490cd8f is the first bad commit
commit b0de98ad3b1391ec0dfe4f8eced0a6833490cd8f
Author: Frank Gevaerts <frank@gevaerts.be>
Date: Fri Jul 19 15:16:37 2019 +0200
Put -lfirmware in CORE_LIBS, to fix -thumb builds
For unknown reasons, -thumb builds need -lfirmware after -lrbcodec (but
still before -lunwarminder)i. Other builds are still happy if we do that.
Including it via CORE_LIBS instead of explicitly achieves that.
Change-Id: Id69e4a0c042f90f71cfd9a72202ce4d8ef6a4181
:040000 040000 e5cac9a75f7658e322ccd7a3e2578f131a0b6963 fa56bd4d120d068a91aee7a086855d154767aae1 M firmware
:040000 040000 3131d2cf4ee7d85c49bb57159fb4caa397e70570 550368bc81d55c203214d484a45d0dceb792b5a4 M tools
I had a look at the diffs, but this is way over my head. How could this be fixed?
-
Because of speachys comment on IRC (https://www.rockbox.org/irc/log-20200511#21:42:42) I tried builds before and after this commit to see if they were working or not working:
Revision 8bd992c works and revision 3e2b50e doesn't work.
It seems, that this might be related to the toolchain, see discussion on IRC (https://www.rockbox.org/irc/log-20200512#19:50:50)