© Semtech 2006
www.semtech.com
24
User Guide
XE8000 ProStart II
I/O pin Signal name Function during programming
Signal type
PA0 TESTIN
Input
Dynamic
PA1 TESTCK Input
Dynamic
PB0 TESTOUT Output
Dynamic
Table 3 : Type I I/O pin used during programming
I/O pin Signal name Function during programming
Signal type
PB0 SCAN
Input
Static
PB1 TEST_E Input
Dynamic
PB2 TESTIN
Input
Dynamic
PB3 TESTOUT Output
Dynamic
Table 4 : Type II I/O pin used during programming
For further information on the table list of XE8000 pins, please refer to the product datasheet.
6.4.4
In Socket Debugging Principle & Hardware requirements
The In Socket Debugger is an alternative to the emulator solution; it allows the user to add breakpoints to their
code, to go step by step, to upload and download the memory. This solution requires about 1k instruction more.
Since the ISD adds code to your code you need to be able to download the code with the monitor add in and
breakpoints. Practically it means that the programming pins are used for the ISD.
To use this feature the target circuit communicates with the XE8000MP with a software UART over two I/O pins
or the hardware UART peripheral. (you can choose one ore the other in RIDE).
The I/O pins used for this feature vary between type I and type II flash.
See the table below for the pin usage (RX - TX is seen from the XE8000 chip).
Software UART
Hardware UART
Flash Type
ISD RX
ISD TX
ISD RX
ISD TX
I PA0
PB0
PB7
PB6
II PA0
PB3
PB7
PB6
Table 5 : ISD pins assignment
Important note:
Since The pin PA0 doesn’t appear in the programming pins for the type II flash, you must add
PA0 to your programming connector if you plan to do on-board In Socket Debugging
