AnsweredAssumed Answered

How do we get the mx6ull evk to boot from QSPI NOR flash?

Question asked by DJ Regan on Oct 10, 2017
Latest reply on Oct 10, 2017 by DJ Regan

Hello,

 

We have followed Yocto fsl-yocto-L4.1.15_2.0.0-ga instructions for targeting a new Yocto build for the mx6ull evk, and targeted the image for QSPI1 NOR flash.

 

We have successfully produced a new u-boot-imx image file. We were also able to use the JTAG interface on the mx6ull EVK through a Segger JLink Plus and Segger's 'JFlash' application. Using the 'JFlash' we can upload the u-boot-imx image file to 0x6000 0000 offset by 0x1000.

 

Unfortunately... we were not able to get the NXP mx6ull EVK to boot through NOR flash while there is no SD card installed.

 

A few questions...

1st question... Is there an app note that outlines the adjustments needed to make the NXP mx6ull evk to boot from QSPI NOR flash instead of the default SD card image boot? ...are there specific efuse adjustments need to be performed to transition the mx6ull evk from SD card booting to NOR flash booting (U303 on the evk's carrier module)?

 

2nd question... Mfgtool appears to reference a NOR flash config file "norconfig=qspi-nor-micron-n25q256a-config". Where is this file located? What is it's specific name? Note: This assumption comes from review of the script file 'mfgtool2-yocto-mx-14x14-arm2-qspi-nor-ull.vbs'.

 

3rd question... Is it likely that the reason we cannot boot from the mx6ull evk's NOR flash because the 1st 0x1000 of the QSPI NOR flash needs to be preinitialized with this "qspi-nor-micron-n25q256a-config" data that is referenced by the Mfgtool script file mentioned in question above?

 

4th question... Is it possible for NXP to share the default preferred 1st 0x1000 bytes of NOR flash image data for the NXP mx6ull evk? Note: Referring to the NOR flash data visible from 0x6000 0000 ...to... 0x6000 1000.

 

Thanks much in advance...

--DJ Regan

Outcomes