Hi @tbiberdorf ,
From your description, your MIMXRT1062CVJ5B hardware is configured with a S26KS512SDPBHI020 HyperFLASH memory is totally working, as the MCUBootUtility already can do the write and erase.
Now, just the JLINK debugger lack the flashdriver.
As the new JLINK driver didn't add the related hyperflash driver, just the default flashdriver is used for the QSPI flash:
So, you can't make it works.
Don't worry, we have another Jlink flashdriver named as RT-UFL, you can refer to it:
https://github.com/JayHeng/RT-UFL
To the JLINK driver install with RT-FUL, please refer to this post:
https://www.cnblogs.com/henjay724/p/14942574.html
When you select the device, use the following _L1, or L2, that is for the hyperflash.
Wish it helps you!
Best Regards,
kerry
Hi Kerry
This provide solution does not make sense. I've been working on implementing it, but the numbers representing the FLASH size do not make any sense.
When I compare to my working connection to my IMXRT1050-EVKB I see that the assigned FLASH is 64MB, as expected:
But the provided driver patch has the flash size at an extreme size of 960MB which is much larger than the expected 64MB.
This is what my .xml edit specifies:
<Device>
<ChipInfo Vendor="NXP"
Name="MIMXRT1060_UFL_L2"
WorkRAMAddr="0x20000000"
WorkRAMSize="0x00080000"
Core="JLINK_CORE_CORTEX_M7"
Aliases="MIMXRT1061xxx5A; MIMXRT1061xxx6A; MIMXRT1062xxx5A; MIMXRT1062xxx6A" />
<FlashBankInfo Name="HyperFlash"
BaseAddr="0x60000000"
MaxSize="0x04000000"
MaxSize="0x08000000"
Loader="Devices/NXP/iMXRT_UFL/MIMXRT_FLEXSPI_UFL_512B_64KB.FLM"
LoaderType="FLASH_ALGO_TYPE_OPEN" />
</Device>
Hi @tbiberdorf ，
This point is easy to realize, as the ongoing :MIMXRT_FLEXSPI_UFL_512B_64KB.FLM
is defined to the larger memory. ，_L1/2 used for Hyper Flash（Page size 512 Bytes，Sector size 4KB/64KB）
You can check the RT-UFL source code, in FlashDev.c, The above
MIMXRT_FLEXSPI_UFL_512B_64KB.FLM
is:
struct FlashDevice const FlashDevice = {
FLASH_DRV_VERS, // Driver Version, do not modify!
"MIMXRT_FLEXSPI", // Device Name
EXTSPI, // Device Type
0x00000000, // Device Start Address
0x40000000, // Device Size in Bytes (1GB)
FLASH_DRV_PAGE_SIZE, // Programming Page Size
0, // Reserved, must be 0
0xFF, // Initial Content of Erased Memory
3000, // Program Page Timeout 100 mSec
15000, // Erase Sector Timeout 15000 mSec
// Specify Size and Address of Sectors
FLASH_DRV_SECTOR_SIZE, 0x00000000, // Sector Size 4kB (256 Sectors)
SECTOR_END
};
That's why you find the size is large, as you know, our RT-UFL is not only used for the 64MB flash, but it also can support the large flash sizes.
So, if you care about the JLINK interface FLASH size, you totally can modify the RT-UFL source code, generate the new .flm, then test it again.
I think, now, you don't need to care about size at first, after your board RT1060+hyperflash can program and boot works OK, then we can modify the source code, that is easy to realize.
Best Regards,
Kerry
Hi @tbiberdorf ,
Please follow me do some testing at first:
1. Check the hardware connection is good
I checked your picture: MemoryMods.jpg
That is correct in the hardware modification points, but we still need to check it is really working.
2. Please run this code in the internal RAM:
SDK_2_12_0_MIMXRT1060-EVKB\boards\evkbmimxrt1060\driver_examples\flexspi\hyper_flash\polling_transfer
Check the printf information, whether the erase, program and read are all passed?
If yes, it means the hardware totally works
3. Seems you also use the NXP-MCUBootUtility.exe,
Do you use the serial download mode to download app, then check the boot, whether that works or not?
serial download mode: SW4 1-OFF,2-ON, 3-OFF, 4-ON
Internal boot mode: SW4 1-OFF, 2-ON, 3-ON, 4-OFF
3. When use the JLINK, please remove these jumper: J3,J4,J9,J10
4. JLINK plus+hyperflash+RT-UFL
Do you try the JFLASH in the JLINK driver, what's the detail test result, after you do the connection, program app, what's the error reported with the original RT-UFL, device: MIMXRT1060_UFL_L1
Don't use your modified firmware, just the original firmware, what's the result?
I write a RT1170 document with RT-UFL, maybe you also can refer to it, the test method is useful to you.
https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/RT1170-Octal-flash-enablement/ta-p/1498369
Please share me your JFlash or the JLINK command related situation, I will help you to check it.
In the previous time, I have tested MIMXRT1060-EVK+hyperflash, that works OK with RT-UFL, the EVKB should be the same.
5. Please note, when you use the hyperflash, your SDK app FCB need to be modified:
const flexspi_nor_config_t hyperflash_config = {
.memConfig =
{
.tag = FLEXSPI_CFG_BLK_TAG,
3
.version = FLEXSPI_CFG_BLK_VERSION,
.readSampleClksrc=kFlexSPIReadSampleClk_ExternalInputFromDqsPad,
.csHoldTime = 3u,
.csSetupTime = 3u,
.columnAddressWidth = 3u,
// Enable DDR mode, Wordaddassable, Safe configuration, Differential clock
.controllerMiscOption =
(1u << kFlexSpiMiscOffset_DdrModeEnable) | (1u << kFlexSpiMiscOffset_WordAddressableEnable) |
(1u << kFlexSpiMiscOffset_SafeConfigFreqEnable) | (1u << kFlexSpiMiscOffset_DiffClkEnable),
.sflashPadType = kSerialFlash_8Pads,
.serialClkFreq = kFlexSpiSerialClk_133MHz,
.sflashA1Size = 64u * 1024u * 1024u,
.dataValidTime = {16u, 16u},
.lookupTable =
{
// Read LUTs
FLEXSPI_LUT_SEQ(CMD_DDR, FLEXSPI_8PAD, 0xA0, RADDR_DDR, FLEXSPI_8PAD, 0x18),
FLEXSPI_LUT_SEQ(CADDR_DDR, FLEXSPI_8PAD, 0x10, DUMMY_DDR, FLEXSPI_8PAD, 0x06),
FLEXSPI_LUT_SEQ(READ_DDR, FLEXSPI_8PAD, 0x04, STOP, FLEXSPI_1PAD, 0x0),
},
},
.pageSize = 512u,
.sectorSize = 256u * 1024u,
.blockSize = 256u * 1024u,
.isUniformBlockSize = true,
};Or you can use the RT1050 SDK FCB directly.
Best Regards,
kerry
Hi @tbiberdorf ,
So, now, which device name you are using in both the JFLASH and the MCUXPresso JLINK debug configuration?
Normally, JFlash works, then the MCUXpresso IDE works, as the MCUXPresso IDE will call the related jlink driver, but you need to select the correct device name and the JLINK driver path.
I checked your attachment:
Do you still use the RT1050? I mean, you select the device name as:MIMXRT1050_UFL_L2?
I open your JFLASH project, didn't find your device name:
In the MCUXpresso IDE, debug configuration area, the JLINK device name should be the same as your JFLASH.
https://www.cnblogs.com/henjay724/p/15430619.html
The following picture also need to select the working JLINK driver file:
I have tested the MIMXRT1060-EVK+hyperflash, that works OK, as you know, EVKB is totally the same flash chip to the EVK.
Best Regards,
Kerry
When discussing this issue with the Future FAE, we found the solution using the provided Segger J-Flash release 7.68c
After doing the 5 modifications MCUXpresso is now able to write new SDK example code to HyperFLASH:
- Make all hardware adjustments to the development board (IMXRT1060-EVKB) to convert from QSPI to HyperFLASH.
- Create example SDK project (ie evkbmimxrt1060_igpio_led_output).
- Replace qspiflash config with a hyperflash config, inside the following xip source file .../xip/evkbmimxrt1060_flexspi_nor_config.c
#if 1
const flexspi_nor_config_t hyperflash_config = {
.memConfig =
{
.tag = FLEXSPI_CFG_BLK_TAG,
.version = FLEXSPI_CFG_BLK_VERSION,
.readSampleClksrc=kFlexSPIReadSampleClk_ExternalInputFromDqsPad,
.csHoldTime = 3u,
.csSetupTime = 3u,
.columnAddressWidth = 3u,
// Enable DDR mode, Wordaddassable, Safe configuration, Differential clock
.controllerMiscOption =
(1u << kFlexSpiMiscOffset_DdrModeEnable) | (1u << kFlexSpiMiscOffset_WordAddressableEnable) |
(1u << kFlexSpiMiscOffset_SafeConfigFreqEnable) | (1u << kFlexSpiMiscOffset_DiffClkEnable),
.sflashPadType = kSerialFlash_8Pads,
.serialClkFreq = kFlexSpiSerialClk_133MHz,
.sflashA1Size = 64u * 1024u * 1024u,
.dataValidTime = {16u, 16u},
.lookupTable =
{
// Read LUTs
FLEXSPI_LUT_SEQ(CMD_DDR, FLEXSPI_8PAD, 0xA0, RADDR_DDR, FLEXSPI_8PAD, 0x18),
FLEXSPI_LUT_SEQ(CADDR_DDR, FLEXSPI_8PAD, 0x10, DUMMY_DDR, FLEXSPI_8PAD, 0x06),
FLEXSPI_LUT_SEQ(READ_DDR, FLEXSPI_8PAD, 0x04, STOP, FLEXSPI_1PAD, 0x0),
},
},
.pageSize = 512u,
.sectorSize = 256u * 1024u,
.blockSize = 256u * 1024u,
.isUniformBlockSize = true,
};
#else
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 = 8u * 1024u * 1024u,
.lookupTable =
{
// 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),
},
},
.pageSize = 256u,
.sectorSize = 4u * 1024u,
.blockSize = 64u * 1024u,
.isUniformBlockSize = false,
};
#endif - Modify the Debug Configurations and replace the MIMXRT1062xx6A to MIMXRT1052xxxA
- Added the following Device to the Segger JLinkDevices.xml file:
</Device>
<Device>
<ChipInfo Vendor="NXP" Name="MIMXRT1062xxx6A" WorkRAMAddr="0x20000000" WorkRAMSize="0x00080000" Core="JLINK_CORE_CORTEX_M7" JLinkScriptFile="Devices/NXP/iMXRT105x/NXP_iMXRT105x.pex" />
<FlashBankInfo Name="HyperFlash" BaseAddr="0x60000000" MaxSize="0x04000000" Loader="Devices/NXP/iMXRT105x/NXP_iMXRT105x_HyperFlash.elf" LoaderType="FLASH_ALGO_TYPE_OPEN" />
</Device>
Sorry everyone but I made an error in my reply, step 4 below should be set to MIMXRT1052xxxB not MIMXRT1052xxxA:
