This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#5731 - Build target for iriver H10
Attached to Project:
Rockbox
Opened by Barry Wardell (barrywardell) - Friday, 28 July 2006, 17:38 GMT+2
Last edited by Dave Chapman (linuxstb) - Friday, 28 July 2006, 17:41 GMT+2
Opened by Barry Wardell (barrywardell) - Friday, 28 July 2006, 17:38 GMT+2
Last edited by Dave Chapman (linuxstb) - Friday, 28 July 2006, 17:41 GMT+2
|
DetailsWARNING: This code has been known to cause permanent damage to the hdd of an iriver H10.
This is an initial build target for the iriver H10. It currently applies to the 20GB version running firmware 2.51. It has been tested to successfully build a bootloader. It doesn't actually boot Rockbox yet. It allows code that is in bootloader/h10.c to be run. This has been used for testing and investigative purposes. To build, select 22 - iriver H10 as the build target and select bootloader for build type. This expects mi4code to be in /tools. For more information on mi4code, see http://daniel.haxx.se/sansa/mi4.html. Once the build has been completed you need to run mi4code twice more: mi4code encrypt rockbox.irver H10_20GC_unsigned.mi4 20gc_eng mi4code sign H10_20GC_unsigned.mi4 H10_20GC.mi4 Now, copy H10_20GC.mi4 to the System directory on your player. It's probably a good idea to keep a backup copy of the H10_20GC.mi4 that is already there. |
This task depends upon
Closed by Hristo Kovachev (bger)
Friday, 11 August 2006, 12:48 GMT+2
Reason for closing: Accepted
Additional comments about closing: Accepted, thank you
Friday, 11 August 2006, 12:48 GMT+2
Reason for closing: Accepted
Additional comments about closing: Accepted, thank you
I'm just curious about a little clarification of what went wrong with your unit.
When I turn it on and it's not connected to the computer it seems to load the bootloader fine but then isn't able to load the firmware which is stored on the hdd.
I can't figure out what caused it. It may have even just been coincidental. My H10 had been acting up a bit recently and I had disassembled it to scan the pcb. And it was in a semi-dismantled state when the problem happened.
Keys have been defined for all plugins and screens. I haven't thoroughtly tested the key definitions, so any suggested changes are welcome.
Also, a H10_20GC.mi4 file is now automatically generated using mkmi4.sh when make is run. mi4code has to be in your $PATH for this to work.
The bootloader file h10.c has also been updated with most irrelevant code stripped out.
'target/arm/iriver/h10/ata-h10.c' and 'target/arm/iriver/h10/ata-target.h' which are in the current CVS are no longer used and can be deleted.
1) Actually detect buttons properly
2) Detect power button
3) Check if hold is on