Hi all,
I have a second iteration of my board with an RT1062 and an IS25WP256D-JLLE. I have the following issue:
I try to connect to the board through the bootloader (Serial bootload from MCUBootUtility (v3.4)) I get the following error:
These are the settings that I am using (these settings worked with the previous iteration of my board with an IS25WP064A-JBLE):
On the NXP-MCUBootUtility, I see this as an error just before the above error message:
Executing: C:\nxp\NXP-MCUBootUtility-master\tools\blhost2_3\win\blhost -t 50000 -p COM38,115200 -j -- configure-memory 9 538976256
toolStatus: 0
commandOutput: {
"command" : "configure-memory",
"response" : [],
"status" : {
"description" : "20107 (0x4E8B) kStatus_FlexSPINOR_SFDP_NotFound",
"value" : 20107
}
}
What is this issue about?
Do I have to change any settings?
Some more info:
• Visual inspection of the board seems ok.
• 2 boards tested so far and exhibit the same behavior.
• This is the schematic (same pins selected as the previous version):
• This is the device status and the log (log.txt attached) from NXP-MCUBootUtility
--------MCU device Register----------
OCOTP->UUID[31:00] = 0x61374919
OCOTP->UUID[63:32] = 0x91c79d7
SRC->SBMR1 = 0x0
SRC->SBMR2 = 0x1000009
BMOD[1:0] = 2'b01 (Serial Downloader)
HAB status = Open
--------MCU Flashloader info-------
Current Version = K2.1.0
Target Version = T1.0.0
--------MCU device eFusemap--------
(0x450) BOOT_CFG0 = 0x0
(0x460) BOOT_CFG1 = 0x8
(0x470) BOOT_CFG2 = 0x0
BT_FUSE_SEL = 1'b0
When BMOD[1:0] = 2'b00 (Boot From Fuses), It means there is no application in boot device, MCU will enter serial downloader mode directly
When BMOD[1:0] = 2'b10 (Internal Boot), It means MCU will boot application according to both BOOT_CFGx pins and Fuse BOOT_CFGx
----------FlexRAM memory-----------
IOMUXC_GPR->GPR16 = 0x200003
FlexRAM configuration is from eFuse
OCOTP->MISC_CONF0[31:00] = 0x40
FlexRAM Partion =0000 - 128KB ITCM, 128KB DTCM, 256KB OCRAM
Hi @tcha_ub ,
Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.
1) Do you have a known working FDCB config for the specific flash (IS25WP256D-JLLE)?
-- For IS25WP256D, it can support 4-byte or 3-byte address mode, so the FDCB can be different for these two modes, so I think it'd be better to discuss how to configure the FDCB before you can access IS25WP256D-JLLE successfully by NXP-MCUBootUtility.
Further, I'd like to know whether the above issue happens on all of the boards.
Have a great day,
TIC
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
------------------------------------------------------------------------------
The main difference between IS25WP064A and IS25WP256D is address range. IS25WP256D supports 4bytes address.
Do you have chance to run \SDK_2_12_0_EVK-MIMXRT1060\boards\evkmimxrt1060\driver_examples\flexspi\nor\polling_transfer demo? What's the result?
And also you can try to use 1bit SDR flash model in MCUBootUtility to configure this flash, see section 2.3 in https://www.cnblogs.com/henjay724/p/12984020.html
Hi @jay_heng,
I will try to run the demo and report back the results.
In the meantime, is there a good source/tutorial on how to create/modify an FDCB configuration (most helpful would be through NXP-MCUBootUtility as it seems easier for now).
Do you have a known working FDCB config for the specific flash (IS25WP256D-JLLE)?
As this is the 1st time working with FDCB, any help will be really appreciated!
Thank you for your prompt reply!
Tasos
FDCB is complicatied , It's hard to explain it in a nutshell.
Below FDCB should be working for IS25WP256D (It is 1bit SDR mode)
\NXP-MCUBootUtility-3.5.0\src\targets\fdcb_model\cfg_fdcb_RTxxx_1bit_sdr_flashA.bin