This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#9955 - Bootloaders for 3.4 - please test
Attached to Project:
Rockbox
Opened by Jonas Häggqvist (rasher) - Thursday, 26 February 2009, 01:32 GMT+2
Last edited by Frank Gevaerts (fg) - Friday, 07 August 2009, 12:38 GMT+2
Opened by Jonas Häggqvist (rasher) - Thursday, 26 February 2009, 01:32 GMT+2
Last edited by Frank Gevaerts (fg) - Friday, 07 August 2009, 12:38 GMT+2
|
DetailsThese are bootloaders for the PP targets which will be released with USB enabled for 3.2. As the main feature, they do not boot the OF when booting with USB inserted.
Please test and report back. The zip contain all bootloaders placed in a directory structure that should be self-explanatory. Tested BROKEN: Tested OK: - Ipod 4G - Ipod Video - Iriver H10-5GB - M:Robe 100 - Sansa C200 - Sansa E200 - Sansa E200R - Iriver H10 (20GB) Needs testing: It turns out that these bootloaders haven't changed behavior for Ipods, so no need to test those, as we won't be releasing updated bootloaders for Ipods. |
This task depends upon
Closed by Frank Gevaerts (fg)
Friday, 07 August 2009, 12:38 GMT+2
Reason for closing: Out of Date
Additional comments about closing: There are newer bootloaders already on the download server, just waiting to be moved to the right place. These are also available from the "Official Test Builds" forum
Friday, 07 August 2009, 12:38 GMT+2
Reason for closing: Out of Date
Additional comments about closing: There are newer bootloaders already on the download server, just waiting to be moved to the right place. These are also available from the "Official Test Builds" forum
Loading Rockbox: works
Loading OF: works
On USB insert Rockbox is loaded
Loading Rockbox w/sdhc: works
Loading Rockbox wo/sdhc: works
Loading OF w/sdhc: works
Loading OF wo/sdhc: works
USB insert w/sdhc: works (Rockbox boots and connects)
USB insert wo/sdhc: works (Rockbox boots and connects)
Loading Rockbox:works
Loading OF: doesn't work (Hangs after the "Using the default key" string )
USB inserts loads the OF
If the H10 is loaded with Rockbox and the USB is inserted, it works perfectly
(although my linux box recognizes a DAP when plugging from the OF and when using Rockbox it shows my H10 as a mass storage device, but that's okay)
Loading Rockbox: works
Loading OF: works
USB insertion: works (Rockbox boots and disk gets mounted)
Loading Rockbox: works
Loading OF: works
USB insertion: works (Rockbox boots, disk gets mounted by Vista)
BTW I've never seen previous versions of the bootloader boot into emergency disk mode.
Unfortunately, I dropped my H10 and broke the hard drive, so can't do the testing myself.
RB USB mode is entered upon cable connection from power-off state with and without SDHC
USB connection mode can still be skipped by pressing the select button during boot.
Keylock prevents boot-up
I installed using the sansapatcher for 32-bit Linux linked to in the manual with the following command:
./sansapatcher -a firmware.mi4
I'm assuming that's the correct procedure. Anyway, it seems to be working great! Thanks a lot for your work on this.
Power off, connect USB - boots rockbox and shows USB plug, but status bar shows playback in progress and it doesn't connect to PC. Disconnecting sometimes gives a data abort (at 00008F20 (0)) and sometimes freezes on the main menu with Resume Playback highlighted and the disk activity icon shown.
Without the SDHC card, it seems to behave correctly. CHKDSK says the SDHC filesystem is clean.
FS#9935- that's a different bug. FS#9957 is still not fixed.but wouldnt it make more sense if on hold when being plugged in the bootloader charges the battery to 100% and then turns off?
Rockbox boot loader
Version: r20108-090226
iriver H10 20GB
HTC426020G7CE10
Partition 0: 0x0C 19077 MB
Loading original firmware..
Trying /System/OF.mi4
Can't load /System/OF.mi4
File not found
i have not renamed the file contained in the zip files provided here. shall i rename it and then try again?
I renamed the iriver-downloaded file to OF.mi4
I copied the bootloader from this thread to the System folder
Starting the original firmware works
Starting rockbox works
Usb connection works
Copying works
Deleting works
Returning to the main menu when the device is removed in the OS works
when booting rockbox by plugging in the usb connector when the sansa is powered off, ejecting the drive leads to a rockbox crash (data abort or hang).
(the error does not happen when booting the device manually and then connecting... so it must have something to do with the bootloader i suppose).
- player off, then cable plug in >> player boots to rockbox, but no usb-connection established (also no usb-picture on screen)
- player on, then cable plug in >> player switch to usb-connection with usb-picture on screen
works okay, but would be better if the player also starts the usb-connection when the player was off before.
actually you have to reattach the cable to start the connection.
Main Menu: works
Files: works
Settings: works
Database: doesn't work
Tested on r20281
It's only possible to quickformat microsd-cards, not full format (under windows).
Testet on latest build with Transcend 1GB and Kingston 8GB SDHC.
........................................................................................................................................................
Comment by Steve Semke (quad) - Wednesday, 11 March 2009, 14:51 GMT+1
Tested it with several other start-screens:
Main Menu: works
Files: works
Settings: works
Database: doesn't work
...................................................................
I merely wanted to say the bad behavior is also seen if the start screen is Resume Playback
On Ubuntu 9.04 64bit:
- player off, then cable plug in >> player boots to rockbox, usb-picture on screen, but does NOT mount as a mass storage device
- player on, then cable plug in >> the same.
Bizarre: if I push button on the device, the desktop OS will react by furiously turning the system volume down.
lsusb of the device is attached.
1. Bumping the bootloader version number(s)
2. Displaying that version number rather than the revision during boot
3. Probably other things