Rockbox vs. iriver firmware

[prop]

i just checked out all rockbox sources from cvs and compiled. after rockbox boot, i successfully rebooted into original firmware

[petur]

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)

[Ricardo Dawkins]

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 ?

[petur]

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

[petur]

Quick guide to restore eeprom settings: put the file attached to this post (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.

[Ricardo Dawkins]

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.

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 ?

[petur]

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

[Massa]

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)

[petur]

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

[prop]

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 %)

[Ricardo Dawkins]

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.

[petur]

good to hear that!

next step is finding out why rockbox is corrupting the eeprom 

[Massa]

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