Once the desired configuration is
completed in the GUI, the binary file used to program the TPS257xx-Q1 device can be
generated. This binary file is then downloaded to the hardware by one of two
transport mechanisms:
- Direct programming of the binary
image into onboard EEPROM using I2C:
- This mode is the default
method used during development
- Programming using the
built-in connections on the TPS257xx-Q1 EVM using the onboard TIVA MCU
or directly using an external programming tool such as the Total Phase
Aardvark I2C/SPI Host Adapter (see Section 5.4)
- This method of
programming is required to load the production-ready binary image into a
blank EEPROM device during production
- Secure programming of the binary
image into onboard EEPROM using USB:
- This mode is accessed
using the TPS257xx-Q1-GUI for post-production field updates of custom
hardware (can also be used during development).
- The TPS257xx-Q1 device
must be powered up into Firmware Update mode (FWUP), configuring
Port A as a USB endpoint connection
- The binary image is
programmed into EEPROM by the TPS257xx-Q1 device after verification of
matching keys between the binary image and previously-programmed EEPROM
image at production
Version control can be embedded
manually to a GUI-generated binary file to uniquely identify and track changes. For
more details, See Appendix A.
The following sections describe the
methods used to load the custom application configuration onto the hardware.