The Segger Wiki page for J-Flash SPI says:
"J-Flash SPI is able to program all kinds of SPI flashes, even if the CPU connected to them, is not supported by J-Link / Flasher. This is because J-Flash SPI communicates directly with the SPI flash, bypassing all other components of the hardware. Directly communicates with the SPI flash via SPI protocol, no MCU in between required."
So if I understand this correctly, J-Flash SPI will interface directly to a SPI flash chip via a J-link or a Flasher unit. If that's the case then the SPI signals will be sent over the JTAG/SWD interface correct? Dedicated programming pads, connected to the SPI flash pins, will need to be laid out on the board. However, I do not find any information on how these SPI signal are mapped to the JTAG/SWD signals. Is this really how J-Flash SPI works or am I missing something?
Henry
"J-Flash SPI is able to program all kinds of SPI flashes, even if the CPU connected to them, is not supported by J-Link / Flasher. This is because J-Flash SPI communicates directly with the SPI flash, bypassing all other components of the hardware. Directly communicates with the SPI flash via SPI protocol, no MCU in between required."
So if I understand this correctly, J-Flash SPI will interface directly to a SPI flash chip via a J-link or a Flasher unit. If that's the case then the SPI signals will be sent over the JTAG/SWD interface correct? Dedicated programming pads, connected to the SPI flash pins, will need to be laid out on the board. However, I do not find any information on how these SPI signal are mapped to the JTAG/SWD signals. Is this really how J-Flash SPI works or am I missing something?
Henry
The post was edited 1 time, last by gfisys ().