Rockbox Development > New Ports

SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2

<< < (124/386) > >>

sko:
Hi, I applied kugel´s changes on the fuze button driver to the modified version wich is working with the e200v2, now the DBOP-values on the debug-menu are visible on the e200v2 too.

EDIT:
Hmm... the value it shows for the REC-button seems to depend on the value of the scroll wheel (I have no plan about this dbop-voodoo thing, so I don't know if this behavior is correct or not), this are the values it shows (I turned the wheel clockwise and watched the DBOP_DIN values):
before pressing RECwhile pressing RECFFFF887F087FFFFFA87F287FFFFFE87F687FFFFFC87F487F

kugel.:
"REC-button seems to depend on the value of the scroll wheel"
What do you mean by this? Does that mean there's no reaction of dbop when pressing REC without scrollwheel, or just that the values differ?
The latter one is easily explainable. REC seems to be bit 15, which means it subtracts 8 from the 2nd pair of numbers (each pair is 1 byte). The REC button only represents 1bit, so it only changes the total number by a fixed value.

sko:
Just the values differ, it's also working while scrolling, so REC is bit 15. Thanks for the explanation :)

kugel.:
You can implement rec button reading just like it's done with the power button. But, don't forget that bit 15 NOT set indicates a button press (so something like, bool _button_rec = !(_dbop_din & (1<<15)) )

If you got it working, please post your patch to http://www.rockbox.org/tracker/task/9639

FlynDice:
I've tried this code to get the rec button.  It sees the rec button as pressed during startup and clears my settings sending me back into cabbiev and buttons/wheel don't work anymore.  Is there a reason for making a  bool _button_rec variable?

static void get_rec(void)
{
    if (!(_dbop_din & (1<<15)))
        int_btn |= BUTTON_REC;
}

Navigation

[0] Message Index

[#] Next page

[*] Previous page