AnsweredAssumed Answered

Do I have to initialize FlexSPI in DCD for correct function or is qspiflash_config enough?

Question asked by Stefan Mitterhauser on May 12, 2020
Latest reply on May 12, 2020 by Stefan Mitterhauser

Hello,

 

the clock_config file generated by MCUXpresso Config Tools includes the following code

/* In SDK projects, external flash (configured by FLEXSPI) will be initialized by dcd.
     * With this macro XIP_EXTERNAL_FLASH, usb1 pll (selected to be FLEXSPI clock source in SDK projects) will be left unchanged.
     * Note: If another clock source is selected for FLEXSPI, user may want to avoid changing that clock as well.*/

#if !(defined(XIP_EXTERNAL_FLASH) && (XIP_EXTERNAL_FLASH == 1))
    /* Disable Flexspi clock gate. */
    CLOCK_DisableClock(kCLOCK_FlexSpi);
    /* Set FLEXSPI_PODF. */
    CLOCK_SetDiv(kCLOCK_FlexspiDiv, 3);
    /* Set Flexspi clock source. */
    CLOCK_SetMux(kCLOCK_FlexspiMux, 2);
#endif

The note mentions that for SDK projects the external flash will be initialized by dcd. Is that correct? I thought the Boot ROM initializes the FlexSPI based on the XIP data flexspi_nor_config_t qspiflash_config stored in Flash.

 

Do I have to initialize FlexSPI in DCD for correct function or is qspiflash_config enough?

 

Kind regards,

Stefan

Outcomes