Difference between revisions of "i.MXRT117x"
(Created page with "=QSPI support= The RT117x does not come with internal flash but with external flash connected to the FlexSPI bus, only. The external FlexSPI controller allows to connect sever...") |
|||
| Line 1: | Line 1: | ||
| − | =QSPI support= |
+ | ==QSPI support== |
The RT117x does not come with internal flash but with external flash connected to the FlexSPI bus, only. The external FlexSPI controller allows to connect several different flash types like QSPI, HyperFlash and Octaflash. Furthermore, the external flash can be connected to different pin / ports of the FlexSPI controller which makes a auto-detection very difficult thus a out-of-the-box solution which works for all setups is kind of impossible. For that reason, the J-Link software supports the evaluation board setup, only. Other setups may work but without any warranty or guarantee from SEGGER. If you are working with a different setup and looking for support for this setup, please get in touch with SEGGER. |
The RT117x does not come with internal flash but with external flash connected to the FlexSPI bus, only. The external FlexSPI controller allows to connect several different flash types like QSPI, HyperFlash and Octaflash. Furthermore, the external flash can be connected to different pin / ports of the FlexSPI controller which makes a auto-detection very difficult thus a out-of-the-box solution which works for all setups is kind of impossible. For that reason, the J-Link software supports the evaluation board setup, only. Other setups may work but without any warranty or guarantee from SEGGER. If you are working with a different setup and looking for support for this setup, please get in touch with SEGGER. |
||
| − | ==Supported QSPI setup== |
+ | ===Supported QSPI setup=== |
*J-Link Software: >= V6.64 |
*J-Link Software: >= V6.64 |
||
*Hardware: NXP MIMXRT1170-EVK |
*Hardware: NXP MIMXRT1170-EVK |
||
| Line 25: | Line 25: | ||
|- |
|- |
||
|} |
|} |
||
| + | |||
| + | ==Reset== |
||
| + | The device has a ROM code which needs to be run after reset. It seems like when a reset via the debugger is performed, the device remains in an endless loop in the boot ROM although the boot image was accepted as valid by the boot ROM. As most IDEs set PC & SP manually after reset, this is not a problem. |
||
Revision as of 16:20, 28 August 2020
QSPI support
The RT117x does not come with internal flash but with external flash connected to the FlexSPI bus, only. The external FlexSPI controller allows to connect several different flash types like QSPI, HyperFlash and Octaflash. Furthermore, the external flash can be connected to different pin / ports of the FlexSPI controller which makes a auto-detection very difficult thus a out-of-the-box solution which works for all setups is kind of impossible. For that reason, the J-Link software supports the evaluation board setup, only. Other setups may work but without any warranty or guarantee from SEGGER. If you are working with a different setup and looking for support for this setup, please get in touch with SEGGER.
Supported QSPI setup
- J-Link Software: >= V6.64
- Hardware: NXP MIMXRT1170-EVK
- Flash: IS25WP128-JBLE (QSPI flash) connected to FlexSPI port A
| Signal Name | GPIO name | IO function |
|---|---|---|
| FlexSPI_A_DQS | GPIO_SD_B2_05 | flexspi1.A_DQS |
| FlexSPI_A_SS0 | GPIO_SD_B2_06 | flexspi1.A_SS0_B |
| FlexSPI_A_CLK | GPIO_SD_B2_07 | flexspi1.A_SCLK |
| FlexSPI_A_D0 | GPIO_SD_B2_08 | flexspi1.A_DATA[0] |
| FlexSPI_A_D1 | GPIO_SD_B2_09 | flexspi1.A_DATA[1] |
| FlexSPI_A_D2 | GPIO_SD_B2_10 | flexspi1.A_DATA[2] |
| FlexSPI_A_D3 | GPIO_SD_B2_11 | flexspi1.A_DATA[3] |
Reset
The device has a ROM code which needs to be run after reset. It seems like when a reset via the debugger is performed, the device remains in an endless loop in the boot ROM although the boot image was accepted as valid by the boot ROM. As most IDEs set PC & SP manually after reset, this is not a problem.
