Echelon FT 5000 EVB - Manual (Page 19)

FT 5000 EVB Hardware Guide 11
Performing In-Circuit Programming of External Serial Memory Devices
The JP23 header along with the jumpers on JP1 provides support for third-party in-circuit device
programmers, which you can use to update the data in the external serial EEPROM and flash devices
used by the FT 5000 Smart Transceiver on the FT 5000 EVB. This provides an alternative to loading
application images into these external serial memory devices over the TP/FT-10 network. Note that
the NodeBuilder tool and Mini kit only support downloading application images over a L
ON W ORKS
network; they do not directly support loading application images through third-party device
programmers or memory ICE. Echelon has tested a third-party in-circuit programmer, the Aardvark™
I2C/SPI USB Host Adapter from TotalPhase™, as described later in this section.
To perform in-circuit programming of the external serial EEPROM and flash memory devices on the
FT 5000 EVB, you use the devices’ I2C and SPI interfaces. You must use the I
2 C interface to program
the EEPROM device on the FT 5000 EVB, and you use the SPI interface to program flash device on
the FT 5000 EVB.
To perform in-circuit programming of the external serial EEPROM and flash memory devices on the
FT 5000 EVB, follow these steps:
1. Power off the FT 5000 EVB.
2. Remove jumpers 1-2, 3-4, and 5-6 from JP1 to disconnect the external serial non-volatile memory
from the FT 5000 EVB.
• If you are programming the serial flash device on the FT 5000 EVB, hang the shunt off pin 1
because you will need to use pin 2.
• If you are programming the serial EEPROM device on the FT 5000 EVB, hang the shunt off
pin 5 because you will need to use pin 6.
3. Power on the FT 5000 EVB.
4. Ground the Reset pin on the FT 5000 EVB. To do this, connect pins 16 and 20 on the Gizmo I/O
Connector on the FT 5000 EVB. This holds the RST~ line low, places the I 2 C and SPI interfaces
into a high-impedance state, and idles the Neuron chip. This eliminates the possibility of the
Aardvark programmer conflicting with the Neuron chip when the Aardvark is accessing the I
2 C
and SPI interfaces.