Calculator Community > General Calculator Help

TI-Nspire incorrectly identifying keypad

(1/2) > >>

F1lmboy:
As far as I can tell, my TI-Nspire thinks that it is using a clickpad when it is not.
According to an archived version of http://hackspire.unsads.com/wiki/index.php/Keypads, any bit set by the touchpad (what the CX series seems to use) is interpreted by the calculator as the same bit set by a clickpad - for instance, [return] functions as expected, but [X] is treated as [,]. boot2 and the diagnostics menu work as intended (perhaps they are hard-coded to accept touchpad input). Also, the diagnostics menu verifies that all individual keys still work as intended.

My question is: is there any way I can force my CX CAS to interpret its button presses as touchpad commands rather than clickpad commands? I have not taken apart the calculator yet but if there is a hardware fix I would try that.

Edit: Also, the calculator resets every time I try to turn the screen on... (e.g. ctrl+on, then on again) probably relevant to the issue but can't imagine how that would help.
Edit 2: I managed to get gpSP-Nspire on my calculator and test ran an old game - it worked fine, although I couldn't use the arrow pad. However, the rest of the buttons worked (used the number keys to navigate instead). Interesting...

Vogtinator:

--- Quote ---My question is: is there any way I can force my CX CAS to interpret its button presses as touchpad commands rather than clickpad commands? I have not taken apart the calculator yet but if there is a hardware fix I would try that.
--- End quote ---
The keypad type is indicated by ADC channel 3. Nobody knows where it is connected to on an nspire. It might be somewhere on the dock connector, if you're lucky...
Sorry that I'm not able to help much. Maybe a software-based solution is possible, hardcoding the value that is read by the OS.

F1lmboy:
The ADC test for channel 3 does read Fail... has exactly 1.5V, which would seem to be too high (But I wouldn't know anyway). The unlabelled number alternates between 465-466.

How difficult would a software-based override be to code? I don't really know much in the way of RAM maps... could give it a try though. Too bad the existing documentation is somewhat lackluster (all I could find as far as a memory map was http://hackspire.unsads.com/wiki/index.php/Memory-mapped_I/O_ports)

Or maybe I should just jam a clickpad on this calculator somehow kek

Vogtinator:

--- Quote ---The ADC test for channel 3 does read Fail... has exactly 1.5V, which would seem to be too high.
--- End quote ---
Yeah, it should be around 73, so ~0.25V.


--- Quote ---How difficult would a software-based override be to code?
--- End quote ---
I don't know. Maybe it's possible to just map the 0xC4000000 region to a crafted buffer with the correct values.
Patching the OS might be easier, but would require a refresh for every new version.


--- Quote ---Or maybe I should just jam a clickpad on this calculator somehow kek
--- End quote ---
Frankencalc... It's not as bad as combining a CX with a clickpad LCD, though :D

F1lmboy:
Existing documentation on the OS is unfortunately shoddy...  <_<
As for editing the RAM, I'm not sure where the pointer would be for the ADCs... I can get ndless to run (slightly complicated process), so I might be able to do something with that added functionality, but I'm not sure how exactly.

It also begs the question: Why does a CX calculator even have code for a clickpad?

Navigation

[0] Message Index

[#] Next page