Rockbox Technical Forums

Support and General Use => Hardware => Topic started by: Ricardo Dawkins on June 28, 2006, 01:19:02 PM

Title: Rockbox vs. iriver firmware
Post by: Ricardo Dawkins on June 28, 2006, 01:19:02 PM
Hello boys!

I'm newbie here but managed to install this build of Rockbox Exp (2.8.1d) over the 1.29K firmware on my iriver H320.

Now, the original iriver firmware can't load after pressing and hold record before turning on the player. Player get stuck on the loading screen.

I followed all the advice on the Rockbox.org page about: resetting the player, scanning the disk, renaming or removing some files on the player and even formatting the drive twice. And got the same result with the 1.29K firmware stuck on the loading screen.

Tried to downgrade to a old version of Rockbox and got the same results. Rockbox still loads fine.

What should I do to recover the 1.29K firmware since I want to play videos ?
The is a way to recover the firmware without doing the procedure described on the player's manual ?

Any clues. Thanks for any answer and regards.
Title: Re: Rockbox vs. iriver firmware
Post by: ego on June 28, 2006, 02:43:06 PM
just in case, check make sure:

with the player off, hold record. hold play, and keep both buttons pressed until the iriver logo displays.

if that doesn't help, can you describe with more detail what is wrong? when you say 'stuck on the loading screen,' do you mean the bootloader loading screen or the iriver loading screen?
Title: Re: Rockbox vs. iriver firmware
Post by: Ricardo Dawkins on June 28, 2006, 03:04:05 PM
Hi Ego

I did what you told me. Still, freeze (stuck) on the iriver's loading screen. It reads-...
Ver 1.29K
LOADING...

What happens is that I need to boot on the iriver firmware. After pressing holding both record + play to load it my player is always freezing on the load screen since I updated to Rockbox Experimental build 2.8.1d from this site:
http://rockbox.biniaris.net/KoshBuilds.html

Check the thread here about this build:
http://www.misticriver.net/showthread.php?t=38917&page=57

Rockbox is still working fine. the bootloader version is 5. Before all this, dual boot was working fine. Shame on me.

Hoping someone else can help me, too.
Title: Re: Rockbox vs. iriver firmware
Post by: ego on June 28, 2006, 03:37:03 PM
hm. try plugging the player in to AC while it's off, or holding record and plugging it into USB. if you can make the iriver fw boot somehow, you can flash to a clean copy of 1.29k and then try again (which is my only idea for a solution).  good luck. the people at the rockbox IRC channel might be able to offer advice too, usually most of the devs hang out there.

because it sounds like a bootloader problem and not a rockbox problem, the build you're using probably doesn't matter... i think.
Title: Re: Rockbox vs. iriver firmware
Post by: Llorean on June 28, 2006, 03:44:32 PM
Though it's strange that the problem started according to him after he switched builds. I'd be curious to know if it was from an official build to one of the experimental/optimized/whatever other builds.
Title: Re: Rockbox vs. iriver firmware
Post by: Ricardo Dawkins on June 28, 2006, 03:50:42 PM
Ego

Option 1: it goes direct to charging under the iriver firmware. Big battery logo splash with the charging word below and the blue bars.

Option 2: it goes direct to charging under the iriver firmware. Big battery logo splash with the charging word below and the blue bars.

final result: cant load into iriver firmware

Llorean.
Switched from the halfway build (drippy) to one of the Kosh-PaulHue 2.7 build. After that went to Kosh-PaulHue build 2.8.

final result: Rockbox build load fine and cant load into iriver firmware
Title: Re: Rockbox vs. iriver firmware
Post by: Febs on June 28, 2006, 03:51:19 PM
hm. try plugging the player in to AC while it's off, or holding record and plugging it into USB. if you can make the iriver fw boot somehow, you can flash to a clean copy of 1.29k and then try again (which is my only idea for a solution).  good luck. the people at the rockbox IRC channel might be able to offer advice too, usually most of the devs hang out there.

because it sounds like a bootloader problem and not a rockbox problem, the build you're using probably doesn't matter... i think.
I just want to point out that if the problem is a bad hard drive, he is much better off having the Rockbox bootloader than the iriver bootloader.
Title: Re: Rockbox vs. iriver firmware
Post by: Febs on June 28, 2006, 03:52:16 PM
Ego

Option 1: it goes direct to charging under the iriver firmware. Big battery logo splash with the charging word below and the blue bars.

Option 2: it goes direct to charging under the iriver firmware. Big battery logo splash with the charging word below and the blue bars.

final result: cant load into iriver firmware
Try pressing ON/PLAY when it is in this state.  What happens?
Title: Re: Rockbox vs. iriver firmware
Post by: Ricardo Dawkins on June 28, 2006, 04:05:40 PM
Febs:

nothing special happens. I did the following:

Press ON / PLAY : nothing. just keep on Charging

Hold ON / PLAY: nothing. just keep on charging


Remember that before asking for any advice & help, I reset the player, ran a scandisk on it (W2K & XP) that found nothing, renamed and removed folders and files, formatted twice and still same problem.

I tried installing older versions of RB from MAY. But, same problem. I think is the bootloader that is borked.

I hope this thing doesnt brick. Any other advice boys beyond keeping RB just for playing music ?
(I bought this 'cause it "could" play videos)
Title: Re: Rockbox vs. iriver firmware
Post by: Ricardo Dawkins on June 28, 2006, 06:21:42 PM
Ok. Looking on the H320 drive with command line under WinXP found the following folders
Recycled
System Volume Information

The 2nd folder have information regarding Rockbox, please check the following images
Command line box...Notice the two hidden folders Recycled and System Volume Information

(http://www.cacoabbo.com/folders.jpg)

Notice the files inside one of the sub-folders into "System Volume Information". On the notepad windows you can see the information inside a few of those files

(http://www.cacoabbo.com/folders_files.jpg)


(http://www.cacoabbo.com/folders_files1.jpg)


(http://www.cacoabbo.com/folders_files2.jpg)

My question is: should I delete these folders since anyone here no more advice for me ?
Regards.

BTW, notice how the iriver firmware is recreating the RECORD folder with its subfolders every time I delete it.
Title: Re: Rockbox vs. iriver firmware
Post by: pabouk on June 29, 2006, 02:39:23 AM
The "Recycled" and "System Volume Information" folders are not important. You can safely delete them. They are created automatically by Windows (XP or ME).

"Recycled" contains "deleted" files which can be eventually restored.

"System Volume Information" contains automatic backups of some files. The backup is created by the "System Restore" service.
Title: Re: Rockbox vs. iriver firmware
Post by: Mad Dog McKill on June 29, 2006, 03:45:23 AM
This is exactly what I am having as well..

I described my problem here and so far.. there hasn't been any progress.. I wonder how widespread this thing is..

http://www.misticriver.net/showthread.php?p=465237#post465237 (http://www.misticriver.net/showthread.php?p=465237#post465237)

I am using Iriver's 1.29k firmware.. and so far besides not booting up, the contrast has been messed up once again...

In my case though, the problem began not when I upgraded to another build but 3 weeks after I started using using a bleeding edge Rockbox build dated 23 of May.
Title: Re: Rockbox vs. iriver firmware
Post by: petur on August 15, 2006, 07:26:04 PM
I've just added the eeprom driver for h300 series and a way to write a file to it.

This way it should be possible to restore OF eeprom settings if rockbox wiped them. It can also be used to find the source of the wiping.
Title: Re: Rockbox vs. iriver firmware
Post by: prop on August 16, 2006, 07:15:55 AM
I've just added the eeprom driver for h300 series and a way to write a file to it.

This way it should be possible to restore OF eeprom settings if rockbox wiped them. It can also be used to find the source of the wiping.

It works!
Thanks!!! :))))))
Title: Re: Rockbox vs. iriver firmware
Post by: petur on August 16, 2006, 07:28:55 AM
you mean you took an internal_eeprom.bin from another player and wrote it back?

I've started a separate thread with instructions and a copy of my eeprom
Title: Re: Rockbox vs. iriver firmware
Post by: prop on August 16, 2006, 07:38:29 AM
i just checked out all rockbox sources from cvs and compiled. after rockbox boot, i successfully rebooted into original firmware
Title: Re: Rockbox vs. iriver firmware
Post by: petur on August 16, 2006, 09:39:30 AM
i just checked out all rockbox sources from cvs and compiled. after rockbox boot, i successfully rebooted into original firmware

errr.... what was your problem then? The driver does absolutely nothing on its own (on h300 at least) - it's only accessed when selecting those two entries in the debug screen (see other thread)
Title: Re: Rockbox vs. iriver firmware
Post by: Ricardo Dawkins on August 16, 2006, 11:02:55 AM
I've just added the eeprom driver for h300 series and a way to write a file to it.

This way it should be possible to restore OF eeprom settings if rockbox wiped them. It can also be used to find the source of the wiping.


Exuce me, Sir. how do I place a original H320 firmware back on my player with this eeprom driver ?

What file I need and what method shoudl I use ?

There are safety or backup measures for not bricking my player ?
Title: Re: Rockbox vs. iriver firmware
Post by: petur on August 16, 2006, 11:49:35 AM
The eeprom is a programmable chip where the original iriver firmware stores its settings. Writing to it will not brick your player.

Some rockbox users have reported that they are unable to start the original iriver firmware (it hangs at boot time) - however rockbox works ok. I'm assuming that the reason for this is that the settings of the original iriver firmware have become corrupted.

The reason for this driver is to allow resetting that eeprom to default values in the case of those issues.

Users unaffected by all this should not use this.

Alternatively, it can be used to find out which value iriver is storing where ;)
Title: Re: Rockbox vs. iriver firmware
Post by: petur on August 16, 2006, 11:53:11 AM
Quick guide to restore eeprom settings: put the file attached to this post (http://forums.rockbox.org/index.php?topic=5856.msg45296#msg45296 (http://forums.rockbox.org/index.php?topic=5856.msg45296#msg45296)) in the root of your player and perform the Write back EEPROM as mentioned in above linked post.

No brick risk at all.
Title: Re: Rockbox vs. iriver firmware
Post by: Ricardo Dawkins on August 16, 2006, 11:55:16 AM
The eeprom is a programmable chip where the original iriver firmware stores its settings. Writing to it will not brick your player.
ok. thanks for explaining it.

Quote
Some rockbox users have reported that they are unable to start the original iriver firmware (it hangs at boot time) - however rockbox works ok. I'm assuming that the reason for this is that the settings of the original iriver firmware have become corrupted.

I'm one of those users. What should I do to reset to default settings ? Just run this driver and I'm set ?
Title: Re: Rockbox vs. iriver firmware
Post by: petur on August 16, 2006, 03:20:35 PM
I'm one of those users. What should I do to reset to default settings ? Just run this driver and I'm set ?

Well technically you don't 'run' a driver ;)

I've added instructions in that other thread. The latest CVS build will now also print a message on success, the old version only printed something on the screen if there was a problem.

Do tell me if it fixed your problem
Title: Re: Rockbox vs. iriver firmware
Post by: Massa on August 17, 2006, 02:55:51 AM
Alternatively, it can be used to find out which value iriver is storing where ;)
Would be nice to identify the place where it stores the realtime clock values (especially the date)...
Does the bug still exist, that booting the original firmware changes the year of the rockbox clock?
Or has that already been fixed?
(I didn't use the original firmware for ages, so I don't know) ;)
Title: Re: Rockbox vs. iriver firmware
Post by: petur on August 17, 2006, 03:32:13 AM
Alternatively, it can be used to find out which value iriver is storing where ;)
Would be nice to identify the place where it stores the realtime clock values (especially the date)...
Does the bug still exist, that booting the original firmware changes the year of the rockbox clock?
Or has that already been fixed?
(I didn't use the original firmware for ages, so I don't know) ;)

The date and time are stored in the RTC, as you want them to keep being up to date, don't you?
The eeprom stores brightness, contrast, volume,.... settings
Title: Re: Rockbox vs. iriver firmware
Post by: prop on August 17, 2006, 07:56:55 AM
i just checked out all rockbox sources from cvs and compiled. after rockbox boot, i successfully rebooted into original firmware

errr.... what was your problem then? The driver does absolutely nothing on its own (on h300 at least) - it's only accessed when selecting those two entries in the debug screen (see other thread)
I could not load original firmware.
After installing of yesterday cvs version of rockbox i can load OF =)

i repeat: i did nothing, furthermore, that loaded rokbox. after this i loaded OF =)

ps. sorry for my english %)
Title: Re: Rockbox vs. iriver firmware
Post by: Ricardo Dawkins on August 17, 2006, 09:45:28 AM
I'm one of those users. What should I do to reset to default settings ? Just run this driver and I'm set ?

Well technically you don't 'run' a driver ;)

I've added instructions in that other thread. The latest CVS build will now also print a message on success, the old version only printed something on the screen if there was a problem.

Do tell me if it fixed your problem

Problem solved, petur. YOU ARE THE MAN!

Proceeded as you told me. Iriver firmware booting fine.

Forget to dump my broken eeprom setting so you could have debug it.
Title: Re: Rockbox vs. iriver firmware
Post by: petur on August 17, 2006, 11:06:06 AM
good to hear that!

next step is finding out why rockbox is corrupting the eeprom  :-\
Title: Re: Rockbox vs. iriver firmware
Post by: Massa on August 17, 2006, 01:27:23 PM
Would be nice to identify the place where it stores the realtime clock values (especially the date)...
Does the bug still exist, that booting the original firmware changes the year of the rockbox clock?
Or has that already been fixed?
(I didn't use the original firmware for ages, so I don't know) ;)
The date and time are stored in the RTC, as you want them to keep being up to date, don't you?
The eeprom stores brightness, contrast, volume,.... settings
Ahh - I thought it does only store the seconds since midnight (or something like that) in the RTC itself and the date in EEPROM ::)