PRS+ 300 (Browse Folders, Book History, Key Bindings, Dictionary, epub customization)

[kravitz]

Originally Posted by Mark Nord

kravitz
Just out of curiosity: have you found a ARM-Assembler to build the codes, or are you doing it by hand like me?

by hand)
I D A + H i e w

[kravitz]

Originally Posted by kartu

second works, but reports "" as a key instead of kHold*.

Original version returns e.g. "0", modified "", rightly?

[kartu]

Originally Posted by kravitz

Original version returns e.g. "0", modified "", rightly?

Right. Original returns "0" in both cases, yours returns "0" on simple press and empty string on hold.

[kravitz]

kartu
Could you try this (must return "old0" on hold 0)

[kartu]

Originally Posted by kravitz

kartu
Could you try this (must return "old0" on hold 0)

Empty string again (as with previous versions). Which makes me wonder how "event.getEventKey()" actually works.

PS
getEventKey seems to be mapped to binary function Fskin_device_getEventKey from Fskin.so

Update:
Renamed -hold to -bold (in ebook.so) to see if there are additional checks/lookups. It works, so there aren't any. getEventKey calmly returns kLeft-bold.

[kravitz]

Originally Posted by kartu

Empty string again (as with previous versions).

This one must send key without "kHold" in any case (like original, if my patch works)))

[kravitz]

And to be sure there are no additional checks)
This one MUST send key in hex "0x*" on hold.

[kartu]

Originally Posted by kravitz

This one must send key without "kHold" in any case (like original, if my patch works)))

Sends char(15)

Originally Posted by kravitz

And to be sure there are no additional checks)
This one MUST send key in hex "0x*" on hold.

0 gives 0x00, other numbers crash the reader (tried 8 & 5)

PS
Just a thought, maybe you could simply change the number value? 0 => simple press, 10 => hold?

[Mark Nord]

kravitz

By looking on your patch (ebook1.zip, but still valid for the following) I recognize that
.text:0000CE28 LDR R1, =aKholdD ; char *
seams to miss the [ ], thus loading the constant value 0x1160A and not the stringreference at this address.
[UPDATE] I'am wrong with this, as 0x1160a is already the string reference it should work, as the reference to .got would load the same value to the register
[/UPDATE]
IMHO it should read LDR R1, [aKhold], if this is possible.
Or maybe
LDR R3, =aKholdD
LDR R1, [R3]

My reference states:

3.8 Load and store instructions
The ARM architecture supports two broad types of instruction which load or store the value of a single
register from or to memory:
• The first type can load or store a 32-bit word or an 8-bit unsigned byte.
• The second type can load or store a 16-bit unsigned halfword, and can load and sign extend a 16-bit
halfword or an 8-bit byte. This type of instruction is only available in ARM architecture version 4
and above.
3.8.1 Addressing modes
In both types of instruction, the addressing mode is formed from two parts:
• the base register
• the offset.
The base register can be any one of the general-purpose registers (including the PC, which allows
PC-relative addressing for position-independent code).
The offset takes one of three formats:
Immediate The offset is an unsigned number that can be added to or subtracted from the base
register. Immediate offset addressing is useful for accessing data elements that are
a fixed distance from the start of the data object, such as structure fields, stack
offsets and input/output registers.
For the word and unsigned byte instructions, the immediate offset is a 12-bit
number. For the halfword and signed byte instructions, it is an 8-bit number.
Register The offset is a general-purpose register (not the PC), that can be added to or
subtracted from the base register. Register offsets are useful for accessing arrays or
blocks of data.
Scaled register The offset is a general-purpose register (not the PC) shifted by an immediate value,
then added to or subtracted from the base register. The same shift operations used
for data-processing instructions can be used (Logical Shift Left, Logical Shift Right,
Arithmetic Shift Right and Rotate Right), but Logical Shift Left is the most useful
as it allows an array indexed to be scaled by the size of each array element.
Scaled register offsets are only available for the word and unsigned byte
instructions.
As well as the three types of offset, the offset and base register are used in three different ways to form the
memory address. The addressing modes are described as follows:
Offset The base register and offset are added or subtracted to form the memory address.

PS: just working on Joystick-hold for the 505

[kravitz]

Originally Posted by kartu

Sends char(15)

Always when you hold any button, func sends 15, isn't it?

Originally Posted by kartu

0 gives 0x00, other numbers crash the reader (tried 8 & 5)

Inscrutably)))

Originally Posted by kartu

Just a thought, maybe you could simply change the number value? 0 => simple press, 10 => hold?

No problem... (I hope) but it's not a unix-way)))

[kartu]

Originally Posted by kravitz

Always when you hold any button, func sends 15, isn't it?

Yes.
--------------

[kravitz]

Originally Posted by Mark Nord

LDR R3, =aKholdD
LDR R1, [R3]

I'm not sure, but let's try it.

kartu, could you possibly test this?

[kartu]

Originally Posted by kravitz

I'm not sure, but let's try it.

kartu, could you possibly test this?

Crash on hold0 (didn't try others).

[kravitz]

Originally Posted by kartu

Just a thought, maybe you could simply change the number value? 0 => simple press, 10 => hold?

simple press: N
hold: N + 10

[kartu]

Originally Posted by kravitz

simple press: N
hold: N + 10

Works. Except 10 is hex (will do).
Great job!