Results 1 to 4 of 4
  1.    #1  
    I have a serial peripheral keyboard (Ergo) that Iíve been using for my M515. Since Palm has been selling a serial peri keyboard for its Treo600, I surmised maybe I could make an adapter that will mate the M series keyboard with my Treo 600. Using the M series serial peripheral pinout schema below and some trial-andĖerror with the keyboard, I was able to work out the pinout of the keyboard in relation with the M series pinout. Here they are:

    (M series) Tungsten T3, T, T2, C, W, Zire 71, m125, m130, m500, m505, m515, i705 pinout
    Pin Signal Description
    1 GND Signal- and charge ground (connected to pin 7)
    2 USB_D+ Positive USB data signal
    3 USB_D- Negative USB data signal
    4 VBUS VBUS signal
    5 HOTSYNC HotSync IRQ - +3.3V for button push
    6 N/C Not Connected
    7 GND Signal- and charge GND (connected to pin 1)
    8 ID Identification for peripherials, resistor to ground. Should be short: USB cradle, 7.5 KOhm: Serial cradle, 20 KOhm: Mfg. Test Cradle, 47 KOhm: USB peripheral, 100 KOhm: Serial peripheral, 220 KOhm: modem
    9 Vout +3.2V supply output, 100mA max.
    10 RxD RS-232 RxD signal (input), GPS T
    11 TxD RS-232 TxD signal (output), GPS R
    12 DETECT peripherial detect - tied to ground by peripherials
    13 CTS RS-232 CTS signal (input)
    14 RTS RS-232 RTS signal (output)
    15 DTR RS-232 DTR signal (output)
    16 CHARGE +5V charge supply input, 500-700mA

    Serial Peripheral Keyboard (Ergo) Pinout
    Pin Signal Equivalent Description
    1 GND Connected (shorted) to pin 12
    5 HOTSYNC
    9 Vout
    10 RxD
    12 DETECT
    14 RTS
    Note: The rest of the pins (2, 3, 4, 6, 7, 8, 11, 13, 15, and 16) are NOT CONNECTED in any way.




    Here is the Treo 600 serial connector pinout based on the Developer Reference Guide.
    Palm One Treo 600 Pinout
    Pin Name Description How it works
    1 RXD Receive Data connects to the Treo 600 CPU UART. Note that RXD is TTL level, not RS-232 level. This signal is used for asynchronous serial communications between the handheld and a cradle or peripheral. RXD is an input to the handheld and an output from a cradle or peripheral.
    2 TXD O/P Transmit Data/Power connects to the CPUís UART. Note that TXD is TTL level, not RS-232 level. This signal is used for asynchronous serial communications between the handheld and a cradle or peripheral. TXD is an output from the handheld and an input to a cradle or peripheral. This pin provides up to 3 mA maximum at 2.7V when HS2* is asserted for low-power peripherals, such as keyboards. The short circuit current is 6mA minimum
    3 No Connect GPIO to internal bat pack
    4 HS2* Serial Cradle Detect active-low pin is held low in order to indicate the presence of a keyboard or a serial cradle.
    5 HS1* HotSync Interrupt active- low interrupt pin is asserted low in order to initiate a HotSync with the handheld. In a cradle application, a push button would momentarily short this signal to GND to begin a HotSync.
    6 GND Ground ground connection to the handheld. This signal must be connected to the ground reference in the cradle or peripheral.
    7 USB D- I/O USB Data Negative I/O USB Data Negative
    8 USB D+ I/O USB Data Positive I/O USB Data Positive
    9 DQ I/O 1-wire com pin will support an al battery through the cradle interface. Unused pins from previous Treo products will be used to support the al battery. The al battery pack will also contain the same Dallas Semiconductor DS2761 gas gauge IC that will communicate to the CPU using the 1-wire protocol. The battery acts as a second battery
    10 PACK+ a1 Bat Positive Terminal will support an al battery through the cradle interface. The 2 PACK+ pins are used to support the al battery and basically connected directly to the internal battery. Be very careful not to ground them, short them. They are connected to the internal battery and an al peripheral could draw some amount of current from these pins
    11 PACK+ a1 Bat Positive Terminal -same as above-
    12 GND Ground -same as above-
    13 GND Ground -same as above-
    14 VDOCK Cradle Power (charging) provides a charging path to Treo 600. The voltage provided to these pins should be 5.2V +/- 5% at 1A for best compatibility
    15 VDOCK Cradle Power (charging) -same as above-
    Note: Active low signals have a ď*Ē at the end of their names

    Pin Name How it works
    1 RXD connects to the Treo 600 CPU UART. Note that RXD is TTL level, not RS-232 level. This signal is used for asynchronous serial communications between the handheld and a cradle or peripheral. RXD is an input to the handheld and an output from a cradle or peripheral.
    2 TXD connects to the CPUís UART. Note that TXD is TTL level, not RS-232 level. This signal is used for asynchronous serial communications between the handheld and a cradle or peripheral. TXD is an output from the handheld and an input to a cradle or peripheral. This pin provides up to 3 mA maximum at 2.7V when HS2* is asserted for low-power peripherals, such as keyboards. The short circuit current is 6mA minimum
    3 No Connect
    4 HS2* active-low pin is held low in order to indicate the presence of a keyboard or a serial cradle.
    5 HS1* active- low interrupt pin is asserted low in order to initiate a HotSync with the handheld. In a cradle application, a push button would momentarily short this signal to GND to begin a HotSync.
    6 GND ground connection to the handheld. This signal must be connected to the ground reference in the cradle or peripheral.
    7 USB D- I/O USB Data Negative
    8 USB D+ I/O USB Data Positive
    9 DQ will support an al battery through the cradle interface. Unused pins from previous Treo products will be used to support the al battery. The al battery pack will also contain the same Dallas Semiconductor DS2761 gas gauge IC that will communicate to the CPU using the 1-wire protocol. The battery acts as a second battery
    10 PACK+ will support an al battery through the cradle interface. The 2 PACK+ pins are used to support the al battery and basically connected directly to the internal battery. Be very careful not to ground them, short them. They are connected to the internal battery and an al peripheral could draw some amount of current from these pins
    11 PACK+ -same as above-
    12 GND -same as above-
    13 GND -same as above-
    14 VDOCK provides a charging path to Treo 600. The voltage provided to these pins should be 5.2V +/- 5% at 1A for best compatibility
    15 VDOCK -same as above-


    Now the next step should be to pair the pins from the M series connector via the keyboardís pinout to the Treo600ís, but hereís my problem lies: not all of the pins from the two pinouts can be directly paired as you can see above. Only the GND (Pin 1) and RXD (Pin 10) could be directly paired. However, reading from the short descriptions, here is my proposed layout.


    Keyboard Pin M series Equiv Proposed Treo Equiv
    1 GND GND (Pin 6, 12, 13) *
    5 HOTSYNC HS1 (Pin 5)?
    9 Vout Pack + (Pin 10, 11)?
    10 RxD RxD (Pin 1) *
    12 DETECT HS2 (Pin 4)?
    14 RTS TXD (Pin )?
    * Directly paired
    ? Proposed pairing


    So here are the issues:
    1) Is the proposed pairing correct? Suggestions/ comments please.
    - What is the output current of Pack + pin (Treo 600) when active?
    - What is the current characteristic of RTS pin (M series) when active?
    2) If not, do I need an active IC- based converter? Diagrams please.
    3) Where can I find a document describing the pinout of the M series connector that is similar to the Treo 600 developer guide?
    4) Where can I find a circuit description of the serial peripheral keyboard for Treo 600 being sold by Palm?

    Now, Iíve already acquired the necessary hardware and before I do the mixing-and- matching of the wires, I guessed, I should consult with you guys first. Any constructive suggestion or proposal will be highly appreciated. You can email me at sakuji@yahoo.com.

    P.S.
    Why do I have to do this and not just buy that darn keyboard? Because, I want to. Besides, itís a challenge geeks could not afford to miss.
  2. #2  
    I quickly looked over the pinout, and I think as long as the pins are appropriately matched (which seems pretty straight forward given the pinout for each device), you should be all set on the hardware aspect. How about software? You can send all the signals you want through the serial interface of the Treo, but what does it matter if the Treo does not know how to interpret them. You would need to write drivers which interpret signals on the serial interface.


  3. #3  
    <moved>
    V > Vx > m505 > m515 > T/T > T3 > TC > 650 > 680
    <script type="text/javascript" src="http://download.skype.com/share/skypebuttons/js/skypeCheck.js"></script>
    <a href="skype:wwgamble?call"><img src="http://mystatus.skype.com/balloon/wwgamble" style="border: none;" width="150" height="60" alt="My Skype status" /></a>
  4. #4  
    nice lil project, id like to see some results, always fun to see useable hardware hacks, ive been looking for a good wired kb for the treo

Posting Permissions