Hi,
We have tried using the slightly older NXP-MCUBootUtility. With the flash settings for the ISSI_IS25LPxxxA it seems to read the flash successfully over the UART and through the serial flash loader. I imagine this confirms the FlexSPI bus and flash design. Now how to make this work for our program?
Below are the program defines and qspiflash_config in the MCUxpresso IDE produced software. A simple 'hello_world' program via UART is used. When we boot we get no UART output.
const flexspi_nor_config_t qspiflash_config = {
.memConfig =
{
.tag = FLEXSPI_CFG_BLK_TAG,
.version = FLEXSPI_CFG_BLK_VERSION,
.readSampleClksrc=kFlexSPIReadSampleClk_LoopbackFromDqsPad,
.csHoldTime = 3u,
.csSetupTime = 3u,
.sflashPadType = kSerialFlash_4Pads,
.serialClkFreq = kFlexSpiSerialClk_100MHz,
.sflashA1Size = 4u * 1024u * 1024u,
.lookupTable =
{
// 0 Read LUTs
FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xEB, RADDR_SDR, FLEXSPI_4PAD, 0x18),
FLEXSPI_LUT_SEQ(DUMMY_SDR, FLEXSPI_4PAD, 0x06, READ_SDR, FLEXSPI_4PAD, 0x04),
0,0,
// 1 Read Status
FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x81, READ_SDR, FLEXSPI_1PAD, 0x04),
0,0,0,
// 2 Reserved
0,0,0,0,
// 3 Write Enable
FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x06, STOP, FLEXSPI_1PAD, 0),
0,0,0,
// 4 Reserved
0,0,0,0,
// 5 Erase Sector
FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xD7, RADDR_SDR, FLEXSPI_1PAD, 0x18),
0,0,0,
// 6 Reserved
0,0,0,0,
// 7 Reserved
0,0,0,0,
// 8 Reserved
0,0,0,0,
// 9 Page Program
FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0x32, RADDR_SDR, FLEXSPI_1PAD, 0x18),
FLEXSPI_LUT_SEQ(WRITE_SDR, FLEXSPI_4PAD, 0x04, STOP, FLEXSPI_1PAD, 0),
0,0,
// 10 Reserved
0,0,0,0,
// 11 Chip Erase
FLEXSPI_LUT_SEQ(CMD_SDR, FLEXSPI_1PAD, 0xC7, STOP, FLEXSPI_1PAD, 0),
0,0,0,
// 12 Reserved
0,0,0,0,
},
},
.pageSize = 256u,
.sectorSize = 4u * 1024u,
.blockSize = 64u * 1024u,
.isUniformBlockSize = false,
};
Perhaps you can suggest what to check next? Thanks.
Mark
Looking at the flash memory through MCU-BootUtility tool everything looks correct to me except the 'Absolute address of the first instruction to execute from the image' offset 0x04-0x07 at 0x1000 in the IVT. (as per AN12107) But from my understand the IVT is written by the tool - how could this be incorrect?
Thanks Jing. Is there any additional documentation on RT-UFL?
For example, what operating systems are supported and how to build and run the application?
Below is the schematic of the processor / memory connection as well as the pin definitions.
Is it possible the QE bit on the flash needs to be enabled? If so, what is the easiest way to do this?
Mark
Hi @mrecoskie ,
Segger JLINK is very special. It doesn't use RT1050_SFDP_QSPI.cfx or RT1050_EVK_IS25WP064.cfx assigned by MCUXpresso. This is way we suggest you to use RT-UFL.
After you install RT-UFL, you should assign program algorithm here.
I tested your project, it can debug in mcuxpresso.
Regards,
Jing
My jlink driver is v7.82f. I copied the ‘Devices’ folder and JLinkDevices.xml to the Jlink install folder except nothing unique comes up under 'Device' to select in the MCUXpresso Debug Configurations. What should I expect here?
Thanks,
Mark
