H10 5GB hardware buttons not working anymore

[stanelie]

Hello.

I am having this issue with my player where Rockbox boots but none of the hardware buttons except the power button work anymore. They used to work one week ago but now, without any software change, they've stopped working.

Where it gets strange is that if I boot it while holding down the back button to revert to the original firmware, all the buttons work with the original firmware. So, this would likely indicate the the hardware is fine and that there is a problem with my rockbox install.

I tried reinstalling to no avail.

One more thing of interest : this player has been modified, I added a physical line in in place of the remote connector near the headphone plug and the bottom connector has been completely removed and a mini-usb connector has been put in it's place. I doubt any of these things have anything to do with my issue as it used to be working fine last week.

Any ideas are welcome.
Thanks!
http://img813.imageshack.us/i/h10linein.jpg/
http://img41.imageshack.us/i/h10miniusb.jpg/

Post Merge: April 11, 2011, 08:37:43 AMAlso, to verify that it's not a problem with the scroll strip that is stuck depressed, I tried booting Rockbox with the strip disconnected.

The other buttons still do not work.

Edit : I switched out the scroll strip with that of another H10 player, same thing.

So, as far as I can tell, the buttons are mecanically sound, but Rockbox does not register them, or does not boot far enough to initialize them. Does this make any sense?

[stanelie]

I just restored the original bootloader and firmware, and then reinstalled a fresh rockbox bootloader and rockbox build (yesterday's build).

Same thing : the keys work with the original firmware, but they don't with rockbox (aside from the power key).

Any ideas?

[Chronon]

It sounds like the same problem as here:
http://forums.rockbox.org/index.php?topic=22516.0

[stanelie]

Maybe the scroll strip is only a little bit messed up, not enough that the original firmware would complain, but enough for Rockbox to think that it is depressed.

I just ran a test on the H10 20gb that I also have, if I hold down the scroll script while I boot, I have the exact same symptoms : all buttons are non-functional except the power button!

I was having this issue too with the H10 20gb scroll strip in place of the H10 6Gb's one. Maybe Rockbox is too sensitive?

So, is there a way to make the scroll strip less sensitive in the Rockbox code? Where can I find the specific source code that has to do with the H10 scroll strip?

Should I file a bug report?

Post Merge: April 13, 2011, 10:30:47 AMHello Chronon.

My problem looks similar, but it looks a bit different as I can use my power button under rockbox.

So, trying to verify that my scroll strip is indeed the problem (or the reading of it's value), I tried commenting out

^{/* Read scroller */
        if ( GPIOD_INPUT_VAL & 0x20 )
        {
            GPIO_CLEAR_BITWISE(GPIOD_OUTPUT_VAL, 0x40);
            udelay(250);
            data = adc_scan(ADC_SCROLLPAD);
            GPIO_SET_BITWISE(GPIOD_OUTPUT_VAL, 0x40);
            
            if(data < 0x224)
            {
                btn |= BUTTON_SCROLL_DOWN;
            } else {
                btn |= BUTTON_SCROLL_UP;
            }
        }}

from the rockbox/firmware/target/arm/iriver/h10/button-h10.c file. It did not work, I still cant use the other buttons.

Any other ideas?

Also, how do I build without building the plugins each time? I find it very time consuming to wait 5 minutes for make to finish every time I change one thing... I'm sure there is a better way.

Post Merge: April 13, 2011, 10:49:33 AMOk, turns out I don't have to do a ../tools/configure every time I want to build.

This is a lot faster.

Edit : nope, my changes are not applied if I do that. I have to do a configure after all...

[gevaerts]

Edit : nope, my changes are not applied if I do that. I have to do a configure after all...

No you don't

[stanelie]

You are right.

So, any ideas on how to go about this? Is there a way to have rockbox boot straight into a display of the read value of the scroll strip? That would at least indicate if it thinks it is depressed or not.

[saratoga]

So, any ideas on how to go about this? Is there a way to have rockbox boot straight into a display of the read value of the scroll strip? That would at least indicate if it thinks it is depressed or not.

Add a splash screen with the values somewhere in main.c.

[stanelie]

I put
splash(HZ*2, str(adc_scan(ADC_SCROLLPAD)));
in main.c

I'm doing it wrong I'm sure, I get a different word printed on screen everytime I boot :
files
bookmark
system...

Kinda fun, but not what I want. I pulled that adc_scan(ADC_SCROLLPAD string from the button-h10.c file. Does the main.c see the button-h10.c stuff?

[saratoga]

I put
splash(HZ*2, str(adc_scan(ADC_SCROLLPAD)));
in main.c

I'm doing it wrong I'm sure, I get a different word printed on screen everytime I boot :
files
bookmark
system...

You're printing a random string from a the language file, not the value of adc_scan.  splash works just like printf, so try:

splash(HZ*2, "The value of adc_scan is:  %x", adc_scan(ADC_SCROLLPAD));

[stanelie]

I get :
error: too many arguments to function 'splash'

[gevaerts]

try splashf() instead of splash()

[stanelie]

Yup,

It was splashf, not splash.

I get 17 or 18 as the value. Also, if I push anywhere on the strip as it boots, I get a reading of 400.

The function in button-h10.c compares a hard coded value of 0x224 to determine if it is a DOWN or UP command.

Is the 17 value in hex?

Is this not strange?
Post Merge: April 13, 2011, 01:16:25 PMWether or not the strip is depressed seems to be available in the GPIOD_INPUT_VAL from button-h10.c

How do I go about printing this?
 
I tried splashf(HZ*2, "The value of adc_scan is:  %x", adc_scan(ADC_SCROLLPAD)); b ut I get a "%x expects type 'unsigned int', but the argument 3 has type 'long unsigned int'"

Post Merge: April 13, 2011, 02:48:39 PMOk, I managed to do this :
splashf(HZ*2, "valeur: %lx", GPIOD_INPUT_VAL);

The output is DD when the strip is not depressed and FD while it is depressed.

Is this what I should be reading in a working player?
Post Merge: April 13, 2011, 03:23:25 PMAlso, i did this hoping I would get a readout when I pushed down or up :

<sub>/* Read scroller */
        if ( GPIOD_INPUT_VAL & 0x20 )
        {
            GPIO_CLEAR_BITWISE(GPIOD_OUTPUT_VAL, 0x40);
            udelay(250);
            data = adc_scan(ADC_SCROLLPAD);
            GPIO_SET_BITWISE(GPIOD_OUTPUT_VAL, 0x40);

            
            if(data < 0x224)
            {
                btn |= BUTTON_SCROLL_DOWN;
            } else {
                btn |= BUTTON_SCROLL_UP;
      splashf(HZ*2, "valeur: %lx", GPIOD_INPUT_VAL);
            }
        }</sub>

I do not get a readout. However, I do get a PANIK, but only when I push on the upper part of the scroll strip. If I move my "break point" to the BUTTON_SCROLL_DOWN part of the code, it crashes only when I push down.

All of would indicate that the scroll wheel does get registered within Rockbox. So, then, why won't it scroll??
Post Merge: April 14, 2011, 09:31:31 AMSo,

It's been established that the scroll strip works, and that rockbox is not froozen once done booting.

However, the buttons do not work once rockbox is booted up, except for the power button.

Anything else I should look at? I am really uninspired...