Other Parts Discussed in Thread: UNIFLASH
Currently we are following the steps mentioned in Manual JTAG Load to download the Flash Programmer and Programming the Flash Device to burn the Application Binary on to the QSPI flash in our board. We have couple of questions on the above steps.
TI Programming sequence suggests that the Boot mode should be set to “0000 – No Boot mode” before downloading the Flash Programmer.
Also a UART port to be connected to download the “Application Binary” which is going to be flashed on QSPI device.
Questions:
- To avoid DIP Switch - Can we program the flash in “QSPI boot mode – 1001” without the boot mode pins changed to “0000 – No boot mode” ?
- Our understanding is that the JTAG interface takes control of the processor when it downloads the Flash Programmer
- When it is executed it will receive the Application Binary thru UART port and burn the QSPI flash.
- In this case we can avoid the DIP switch setting. Is this understanding correct ?
- To avoid Serial Interface - Is it possible to download the Application Binary also thru JTAG interface instead of downloading thru UART (serial) port ? and use the JTAG console to issue programming / erase commands to QSPI flash ?
- To avoid JTAG Interface - Is it possible to avoid JTAG interface completely and download the Flash Programmer thru serial (UART) interface and later download the Application Binary also thru serial interface and burn it in QSPI flash ?
- In Supported Platforms for K2G, we don’t see the UART as a “Download Mode” option.
- Is there a QSPI flash programming option available in CCS studio instead of all these procedure ? so that we directly provide the Application Binary file thru the JTAG debugger and directly program the QSPI flash ?