screen "dirty" with my H320

[psst]

Being a long time happy user of rockbox, my h320 died.
Some months passed till I cound find another one, today I installed the rockbox in my new H320, but, though it works fine, the screen is "dirty", it's hard to describe, but spots, lines and everything appear and disappears, I can read the screen, but it's hard sometimes, and ugly.
When I boot with the iriver firmware, it works perfectly, so it's not the unit, and actualy the bootloader prints the information perfectly clean on the screen.
I tried installing the oldest rockbox I could find (a month ago), but same results.

Does it have an explanation? Is it a bug? It only happens to me?

Thank you very much for your help and your great work.

[Sando]

Sounds like you have the same screen corruption problem described in these threads:

http://forums.rockbox.org/index.php?topic=2481.0

http://forums.rockbox.org/index.php?topic=7561.0

[psst]

Thank you.
I could fix it, I changed the values of the LCD wait state in /firmware/target/coldfire/iriver/system-iriver.c  to:

MAX: 0x00003D80
NORMAL: 0x00001180
DEFAULT: 0x00000180

Now it's perfect.

[h0mer]

I have the same problem with my new H320, my ihp-120, and my old H340 are working well.

BUT I can't find the path, where can I write over the values.

I have the latest rockbox build, so there is no system-iriver.c file.

Thanks for the help!

[GodEater]

The source code to Rockbox is not included in what you download to your machine when you install it.

You'll need to grab it using subversion, then make the changes, and then compile your own build.

[h0mer]

I've downloaded the source code, but I can't know what should I overwrite.
These values?

"#if MEM < 32
#define MAX_REFRESH_TIMER     59
#define NORMAL_REFRESH_TIMER  21
#define DEFAULT_REFRESH_TIMER 4
#else
#define MAX_REFRESH_TIMER     29
#define NORMAL_REFRESH_TIMER  10
#define DEFAULT_REFRESH_TIMER 1
#endif "

After refreshing the values how can I compile it to a rockbox build?

[Chronon]

Click on "docs index" link and then choose one of the simplified guides to compiling (in the For Developers section).

[h0mer]

It looks like I'm dumb for doing that.
Could anyone help me, and send me a build with the changed values?

[Chronon]

It's really not too bad if you take it step by step (I agree that it can appear daunting at first).  I would personally rather help you learn how to build your own Rockbox than to roll a single build for you.  (Teach a man to fish, etc.)

Is there a particular part of the instructions that confuses you?

[h0mer]

Well, I'm lazy to get myself over a bunch of pages, and I wanted to test my new H320 properly as soon as it's possible.
But I think tomorrow I will need to get over my laziness and read it through. 

[h0mer]

OK, I give it up! Please pity me with a bulid, which is cure for my problem! Thanks!

[Chronon]

Anyone is free to provide such a build to you.  In the meantime, I am willing to help you get things set up so that you can build Rockbox for yourself.  If you would like help please let me know where in the instructions you got stuck.

If  you are using Windows then you can follow this guide:
http://www.rockbox.org/wiki/SimpleGuideToCompiling