23
KeyMap (KM)
The KeyMap is only supported in Bluetooth version 2.0
firmware. KM enables any available GPIO between GPIO11-
GPIO15 to be assigned as keyboard shortcut key. User_
Defined_Function_n_A/B/C registers (where, n=1, 2, 3, 4 or
5) allow configuration of User_Defined_Function_n_A/B/C
registers (where, n=1, 2, 3, 4 or 5). Thus, the sensor can be
customized to implement standard Microsoft keyboard
shortcut keys or special shortcut keys used in different
applications, e.g. Office, CAD, PC Games, etc.
The respective first and second byte of keyboard code A, B
and C can be assigned to programmable button n (where,
n=1, 2, 3, 4 or 5) in the MConfig software program. The
first byte usually consists of any combinations for keys
located on the either side (left or right only) of a standard
keyboard as listed:
• Windows Logo Key (“LWIN”, “ RWIN”)
• CTRL (“LCTRL”, “ RCTRL”)
• SHIFT (”LSHIFT”, ” RSHIFT”)
• ALT (”LALT”, ” RALT”)
The second byte can be referred to any single keyboard
key scan code available from Windows Platform Design
Notes on Keyboard Scan Code Specification, which can be
downloaded from:
http://www.microsoft.com/whdc/archive/scancode.mspx
Some examples of possible key combinations for pro-
grammable buttons below:
If keyboard code A of programmable button 1 is shortcut
key of “Windows Logo Key”,
Keyboard code A byte1 = "LWin" (or "RWin")
Keyboard code A byte2 = Not Support
User_Defined_Function_1_A = a1 01 08 00 03 00 00 00 00 00
If keyboard code A of programmable button 2 is shortcut
key of “Enter”,
Keyboard code A byte1 = "Not Support"
Keyboard code A byte2 = "ENTER"
User_Defined_Function_2_A = a1 01 00 00 28 00 00 00 00 00
If keyboard code B for programmable button 5 is shortcut
key of “Ctrl+Alt+Delete”,
Keyboard code B byte1 = "LAlt+LCtrl" (or "RAlt+RCtrl")
Keyboard code B byte2 = "Delete"
User_Defined_Function_5_B = a1 01 05 00 4c 00 00 00 00 00
Note: “LCtrl+RAlt” and “RCtrl+LAlt” are not supported.
EEPROM Write Protect Feature
Notice that B8/WP can either be used as a programmable
button or LED indicator, or even as an I/O pin for EEPROM
Write Protect function. In the event where all I/Os above
are used up in a Bluetooth Mouse with tilt wheel, sche-
matic below can be used to generate a ‘pseudo I/O’ for
EEPROM Write Protect function. However, if all I/Os are used
up in a Bluetooth Mouse without tilt wheel, there will be no
EEPROM Write Protect function in the mouse. Though the
possibility of EEPROM being overwritten through normal Figure 17. “Pseudo I/O” for EEPROM Write Protect Function
TW 1
TW2
VOUT
4K7
4K7
R22
R23
SDS511Q/DN1
D4
SDS511Q/DN1
D6 EEPROMWP
470K R20
mouse operation is low, Avago Technologies highly recom-
mends mouse makers to use either B8/WP or the “pseudo
I/O” method for EEPROM Write Protect function.
Media Buttons
The Media button featuring audio control is supported in
both Bluetooth version 2.0 and 2.1 firmwares. The ADNS-
7630 is the first one-chip mouse sensor to support Con-
sumer Control usages as defined in the Consumer Page
(page 0x0C) in the Universal Serial Bus HID Usage Tables
Version 1.0 specification. For more information, please visit
http://www.usb.org/developers/hidpage/.
This feature is related to User-Defined HID Programma-
ble Buttons listed in EEPROM registers. For example, in
order to define one function of consumer page, the value
should be set in the format of “a1 07 xx yy 00 00 00 00 00 00”,
where xx yy should be replaced by the usage ID of the tar-
get function in byte-inverted sequence, eg. “cd 00” for ID =
cd and “25 02” for ID = 225. When manually setting this me-
dia button function in MConfig software program, both first
and second bytes of corresponding Keyboard Code A, B or
C must be set to “Not Support”. The User Defined Function
C for each programmable button will cease to be effective
when SSP is enabled in Bluetooth-Version-2.1’s firmware.
Table 15. Example of Consumer Page audio controls supported
in Windows 2000.
Usage Name Type
0xE0 Volume* Linear Control (LC)
0xE2 Mute* On/Off Control (OOC)
0xE3 Bass Linear Control (LC)
0xE4 Treble Linear Control (LC)
0xE5 Bass Boost* On/Off Control (OOC)
0xE7 Loudness On/Off Control (OOC)
0xE9 Volume Increment* Re-trigger Control (RTC)
0xEA Volume Decrement* Re-trigger Control (RTC)
* These controls are supported in Windows 98 (original release and
Service Pack 1 release).
Note: Programmable buttons with RTC usage type controls should be
assigned to single click function only. If the button is pressed continuously
and not released, the event will be retriggered. Thus, there should not be
any long press function assigned to these buttons. For example, if user
keeps pressing the Volume Increment button, ADNS-7630 will perform
the actual re-triggering of events that will lead to continuous increments
of the volume until the button has been released or until the maximum
volume has been reached.