Bootloading mimxrt1175 processor

[rk_892]

We have been using the mimxrt1170 evkb sdk version 2.10 since long time, we recently updated the sdk version to mimxrt1170 evkb sdk version 2.16. When we try to bootload through qspi flash xip feature we are gettting DAP access error everytime. But when we used the 2.10 sdk xip files with new sdk version 2.16. files the bootloading is working properly. Please explain what might be the issue, and how to resolve it.

Thank you.

[Gavin_Jia]

Hi @rk_892 ,

Thanks for your interest in NXP MIMXRT series!

Could you help me upgrade the IDE to the latest version? To prevent problems caused by differences in download algorithms. Also, are you experiencing the same phenomenon with CMSIS-DAP and JLink?

Best regards,
Gavin

[rk_892]

Previously we are using the 11.7 version mcuxpresso ide, currently we have upgraded to 2.12.148 version ide. And we are facing the issue of the dap access with JTAG while try to load the code into the processor.

[Gavin_Jia]

Hi @rk_892 ,

RT1170-EVK/EVKB are all using SWD by default, switching to JTAG requires hardware rework. so I tried the following test environment in my local area and it tested fine:

RT1170-EVK
- IDE: v25.6
- SDK: 2.16.000
- debugger: CMSIS-DAP and JLink
- interface: SWD

I'm sorry I can't reproduce your test results.

Best regards,
Gavin

[rk_892]

Thanks for the reply@Gavin_Jia.

I want to mention something, that we have been using xip flash bootloading with 2.10 sdk of mimxrt1170evkb. But when sdk updated to 2.16 we have been facing bootloading (dap access issues with swd with cmsis-dap and jlink). One interesting think i observed is that when we use the 2.10 evkb sdk's xip folder replaced with the 2.16 sdk version xip folder, bootloading is working fine without any issues. I am not getting what is the actual reason for working with older sdk xip folder but not with new sdk 2.16 xip folder with same application code, processor and everything.

Please clarify this issue and let me know the proper explain of this case.

Thank you.

[Gavin_Jia]

Hi @rk_892 ,

Thanks for your clarification. I understand your point.

However, the issue is that using SDK 2.16 on your end is problematic and requires pairing it with the XIP file from SDK 2.10. But SDK 2.16 works fine on my end. I can't reproduce this issue here.

You may need to compare the changes in the SDK's XIP files and verify whether you can successfully flash the simplest hello_world project from SDK 2.16 directly. Additionally, has your flash memory been modified? It's best to validate this using an EVK/EVKB board. I believe that it isn't a project-related issue; it's a matter of misalignment.

Best regards,
Gavin

[rk_892]

Hi @Gavin_Jia 

Thanks for the reply and efforts. I will definitely try with the EVK/EVKB board and comeback to you. Mean while once copy the xip of sdk2.10 and replace in sdk2.16 and see if the loading working fine or not? And i need steps to change the memory settings and restrictions, measures need to be taken when want to change the memory settings. Becoz i got the linkerscript build error when i try to debug after change the memory settings.

BR,

rk