Hi @PragalfSIL ，
This morning, I also find one SLN-VIZN-IOT to test it again, still works.
I have a question for you, do you connect both two USB port to your PC?
This is my test result:
You can see, I am connecting both two USB, from your side, please double check it.
BTW, please check your board like my picture 3, make sure 2 boards connection is stable, as sometimes, I find I can't find the USB port in the MCUBootUtility tool, because two board connection is not OK, I connect it again, then board works again.
Wish it helps you!
If you still have questions about it, please kindly let me know.
Best Regards,
kerry
Hai Kerry,
We changed our board and the hardware issue is resolved. We programed our flash using MCUBootUtility tool in serial mode. But after that MCUBootUtility cant recognize the device connected. Device is not shown in device manager too. 
When we try to run the program in RAM through debugger it works fine (We checked it using led blinky and output is verified). But when we try to run flexspi_hyper_flash_polling_transfer program, debugger couldn't detect hyperflash memory. And when step through the program it shows a forced hard fault.
Sometimes when we step through, program run without any error or results.
We thought the it was due to some problem of hyperflash but when we try to mass erase flash it works. Log message is given below
Executing flash operation 'Erase' (Erase flash) - Thu Oct 07 11:16:08 IST 2021
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.3 (Jan 11 2021 16:41:13 - crt_emu_cm_redlink.exe build 9)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in D:/PROJECTS/Workspace/MIMXRT1061_Project_GPIO_toggle _modiftn/Debug\MIMXRT1061xxxxA.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
============= SCRIPT: RT1060_connect.scp =============
RT1060 Connect Script
DpID = 0BD11477
APID = 0x04770041
Disabling MPU
Configure FlexRAM for 768KB OC RAM, 128KB I-TCM, 128KB D-TCM
Finished
============= END SCRIPT =============================
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.361 (NXP Semiconductors)
Serial Number: FTCQD2OU
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&e81fc0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
( 30) Emulator Connected
( 40) Debug Halt
( 50) CPU ID
debug interface type = CoreSight DP (DAP DP ID 0BD11477) over SWD TAP 0
processor type = Cortex-M7 (CPU ID 00000C27) on DAP AP 0
number of h/w breakpoints = 8
number of flash patches = 0
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 0BD11477. CpuID: 00000C27. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FD000: CID B105100D PID 000008E88C ROM (type 0x1)
ROM 1 E00FE000: CID B105100D PID 04000BB4C8 ROM (type 0x1)
ROM 2 E00FF000: CID B105100D PID 04000BB4C7 ROM (type 0x1)
ROM 3 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
ROM 3 E0001000: CID B105E00D PID 04000BB002 Gen DWT (type 0x0)
ROM 3 E0002000: CID B105E00D PID 04000BB00E Gen (type 0x0)
ROM 3 E0000000: CID B105E00D PID 04000BB001 Gen ITM (type 0x0)
ROM 2 E0041000: CID B105900D PID 04001BB975 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
ROM 2 E0042000: CID B105900D PID 04004BB906 CSt type 0x14 Debug Control - Trigger, e.g. ECT
ROM 1 E0040000: CID B105900D PID 04000BB9A9 CSt type 0x11 Trace Sink - TPIU
ROM 1 E0043000: CID B105F00D PID 04001BB101 Sys (type 0x0)
NXP: MIMXRT1061xxxxA
DAP stride is 1024 bytes (256 words)
XML Error - no license-type XML file 'crt_common.xme' on path.
note - part information contained no product license-type data
Inspected v.2 External Flash Device on SPI MIMXRT1050-EVK_S26KS512S.cfx
Image 'MIMXRT1050-EVK_S26KS512S Dec 17 2020 10:04:47'
( 65) Chip Setup Complete
Connected: was_reset=false. was_stopped=true
( 70) License Check Complete
Opening flash driver MIMXRT1050-EVK_S26KS512S.cfx
Sending VECTRESET to run flash driver
Flash device supported (64MB = 256*256K at 0x60000000)
Mass Erase flash at 0x60000000
EraseChip (0x0, 0x0, 0x0) status 0x40 - driver reports init failure - EXTSPI driver rc -1 (0xFFFFFFFF)
complains because another operation was called after Init failed (status 0x40)
There was a problem after unexpected flash driver bahaviour was seen, so we are going to compare the flash driver code with the memory where it was loaded.
Note that, after driver initialization, some difference is normal in 'generic' drivers.
Driver from AXF file:
20001078: 1f78a400 00000000 00000000 ..x.........
Driver code in memory:
20001078: 23c34600 016e3600 00008000 .F.#.6n.....
Driver may be corrupt - halting target for post-mortem
Driver Addresses
Start: 20000000
Entry: 2000009D
End: 200010F4
Stack: 200020F8
Mailbox:2000A0F8
Driver Register State
R0: FFFFFFFF
R1: 00000849
R2: 00000002
R3: 00000100
R4: 2000A0F8
R5: 00000000
R6: 00000040
R7: FFFFFFFF
R8: 00000000
R9: 00000000
R10: 00000000
R11: 00000000
R12: 00000014
SP: 200020D8
LR: 20000AA3
PC: 200000B4
xPSR: 61000000
MSP: 200020D8
PSP: 200020F8
CFBP: 00000001 (CONTROL=0x0, FAULTMASK=0x0, BASEPRI=0x0, PRIMASK=0x1)
Stacked Exception information at MSP (not in exception now)
200020F4: xPSR: 2000009D
200020F0: VECTPC: 00000000
200020EC: LR: 00000000
200020E8: R12: 00000000
200020E4: R3: 00000000
200020E0: R2: 00000000
200020DC: R1: 00000000
200020D8: R0: 2000A0F8
Exception registers
E000ED04: ICSR: 00000000
E000ED08: VTOR: 00200000 TBLBASE=0(INCODE), TBLOFF=0x4000
E000ED28: MMFSR: 00
E000ED29: BFSR: 00
E000ED2A: UFSR: 0000
E000ED2C: HFSR: 00000000
E000ED30: DFSR: 00000001 (HALTED)
E000ED3C: AFSR: 00000000
E000ED24: SHCSR: 00000000
E000ED34: MMAR: 00000000
E000ED38: BFAR: 00000000
E000EDFC: DEMCR: 01000000 (TRCENA)
Closing flash driver MIMXRT1050-EVK_S26KS512S.cfx
MassErase completed (in 90ms)
Thank you,
Hi @PragalfSIL ,
Do you just test the MCU board directly? Without the another board in SLN-VIZNAS-IOT?
Do you try to add the other board? Or another way, you can use the SLN-VIZNAS-IOT board, just replace the on board RT106F to your RT1061, then test it, whether the MCUbootUtility connection is OK or not?
As the serial download mode or internal boot mode will be configured in another board:
So, if you just test one board, no matter the power on or the boot mode, I am afraid you are not correct.
So, if you have resource, can you use the NXP official board SLN-VIZNAS-IOT, and replace the MCU to RT1060 and test it? As your own board may have the stable issues.
If the official board works, then you can compare your board with the official board, it will make things easy.
Any updated information, please kindly let me know.
Best Regards,
Kerry
Hai Kerry,
In the case of second board, yes we are using the both boards (both control board and vizion board). As far as we checked connections and components are good. Boot mode pins are also configured correctly. As your suggestion, we can't change the IC in board since we cant that much delicate work now and it also take lots of time. We will check it eventually,
As I mentioned in the previous post there is problem in checking the hyperflash using hyperflash_polling_transfer. Usually the program detect the hyperflash the return an error while trying to erase it. But now program returns an errror before detecting the hyperflash. Please help me in this problem.
1. Usual hyperflash error. Hyperflash detected and error occurred during erase.
2. Error now. Hyperflash is not detected. Error occurred.
Thank you
Hai Kerry,
We tried to replace MXRT106F in SLN_VIZNAS board with MXRT1061, but now we cant detect the IC in debugger. We will try to figure out the hardware issues and will get back to you soon.
In case of our custom board, we cant even detect flash memory in debugger. Does the flash drive any role in all these issues? Does these problems are due to a faulty flash memory?
Thank You.
Hi @PragalfSIL ,
Today, I help you check the external hyperflash circuit connection, it is the same as the MIMXRT1060-EVK, so the SDK hyperflash should works directly on your board, if your board has no issues.
This SDK project even can work with your original SLN_VIZNAS board.
This is my test result with both the MCUbootUtility and the SDK project.
You can see, all works, my debugger is also the LPC-LINK2 CMSIS DAP.
So, maybe the hardware still have issues, do you have more SLN_VIZNAS board? You also can test it directly.
About the rework board for SLN_VIZNAS board with RT1061 chip, can't enter debug issue may caused by you didn't sold the RT chip stably, please double check it.
LPC-LINK2 also can be used as JLINk, you also can use the JLINK command test, whether you can find the ARM core or not?
This will help you check the rework RT chip connection.
Wish it helps you!
Best Regards,
Kerry
Hai Kerry,
We are trying to get a new board and figure out hardware issues. In the mean time I just need clarification on two things.
1. As you said, SDK program for hyperflash will work on MIMXRT1060 EVK and SLN_VIZNAS_IOT board. We were using SLN_VIZNAS_IOT board for programming. We already tested 5 different boards (3 boards by NXP and 2 custom boards), each board shows the same problem. When debugging program can detect hyperflash but cant erase the flash. Why is it showing same mistake every time.
(Note that we are using SLN_VIZNAS_IOT board and MXRT1060 SDK. SLN_VIZNAS board uses IS26KL series hyperflash and MIMXRT1060 EVK uses IS26KS series flash. Does this affect the result)
2. When we used MCUBootUtility for serial programming, we could successfully program the flash. But after programing, when we try to connect the board to MCUBootUtility again board wont be detected in MCUBootUtility and also in device manager. Board will we discoverable only after running it in debugger mode using MCUXpresso. Could you explain why it is like this?
Thank You,
Hi @PragalfSIL ,
Thanks for your effort.
Now, just based on your NXP SLN_VIZNAS_IOT board which without the modification, and talk the question again.
1. About debug
Please help to check the debugger, do you use the LPC-LINK2 CMSIS DAP?
My version is V5.361, what about you?
What the SDK version you are using? I am using the SDK2.10.0
When you debug the code, you even can set the board mode to internal boot mode.
J27 connect to 0.
2. About the MCUbootUtility
Please check your board J27, do you connect to 0?
In fact, I have connected the board, download the tool attached code:
NXP-MCUBootUtility-3.3.1\apps\NXP_MIMXRT1060-EVK_Rev.A1\led_blinky_0x60002000.srec
Then reset, power off and power on the board again, I still can enter the serial download mode, and detect the USB HID.
Pleas check your two board connection, make sure the MCU board and the vision board connection is oK.
Please try it again.
This morning, I test my NXP SLN-VISION-IOT board again, connection is OK, please also check the configuration, whether you set the boot device configuration the same as me.
Any updated information, please kindly let me know.
Best Regards,
Kerry
Hai Kerry,
We got a new SLN-VIZNAS-IOT board and now we are using it for debugging. It is the original board from NXP with MXRT106F IC. I think now we can eliminate hardware issues.
from the figure you can see that boot mode is selected for internal boot. Boot jumper is connected to 0.
We are using MCUXpresso IDE version 11.3.0, SDK_2.x_MIMXRT1061xxxxA 2.10.1 and LPC link2 version V5_361
Still we are getting errors while checking the flash using hyperflash polling transfer. When we step in through the program error occurs in different locations.(Every time it changes where the error occures)
Advanced thanks for support.
Hi @PragalfSIL ,
Thanks for your effort.
I test it again， still works OK.
I attach my test project, also based on SDK2.10.1
But, I find your MCUXpresso IDE is old, please use the MCUXpresso 10.4.1.
Then try it again.
LPC-LINK2 board J7 interface connect to the SLN-VIZNAS-IOT J6.
Your boot mode is OK.
Please use the new MCUXpresso IDE test my attached project.
If you still have issues, please kindly let me know.
Based regards,
kerry
Hai Kerry,
We upgraded the MCUXpresso IDE to version 11.4.1. Also we imported your project to IDE. Still the same error is happening again. We cant figure out the why. Is it because we are using SLN-VIZN board?
Since the error is there from the start, does that mean something wrong in our basic settings?
We are using latest versions of IDE and SDK. What should we do to make it work?
Thank you.
Hi @PragalfSIL ，
This morning, I also find one SLN-VIZN-IOT to test it again, still works.
I have a question for you, do you connect both two USB port to your PC?
This is my test result:
You can see, I am connecting both two USB, from your side, please double check it.
BTW, please check your board like my picture 3, make sure 2 boards connection is stable, as sometimes, I find I can't find the USB port in the MCUBootUtility tool, because two board connection is not OK, I connect it again, then board works again.
Wish it helps you!
If you still have questions about it, please kindly let me know.
Best Regards,
kerry
Hai Kerry,
It worked. The problem was due to insufficient power. Thanks for the support. It's been really helpful. Now the hyperflash checking program shows correct outputs.
In our custom board, we can run the program without error. But the example failed. What would be the possible problem in our board?
Now the hyperflash is OK (SLN_ VIZN_IOT board), we tried to load the sample program led blinky to hyperflash. Project settings are given below.
But we cant debug the project. We cant even step in to program or cant use any break points in main. It looks like program is stuck somewhere before entering main.
Thanks in advance
Hi @PragalfSIL ，
I have tested it on my nxp sln-viza-iot board, it works OK.
1. J27 connect to 1
2. MCUXpresso code modify XIP from QSPI to hyper flash
3. debugger flash driver modify from QSPI to hyper flash.
this is my test result
You can see code is in the flash.
I also attach my test project, it is the helloworld.
Wish it helps you!
Best Regards,
Kerry
Hai Kerry,
We tried to write to flash with boot mode selection in 1, as you mentioned, and it worked. We checked with your sample program and also gpio toggling program. Debugger shows correct results and disassembler shows memory locations.
But when we tried to check the output using multimeter, pin status isn't changing. Our code for gpio toggling is given with it.
We are using GPIO_B1_11 as output pin. We used J5 to check the output.Result is,
- When R113 is open output is low
- When R113 is short output is high.
Thanks
