topic Re: MiMXRT1062CVJ5B debugging problems in i.MX Processors

MiMXRT1062CVJ5B debugging problems

robertomorsiani — Tue, 05 Apr 2022 08:02:17 GMT

The program I'm using is the very simple "Hello world" demo app with semihost consol.

I have a castom board with MiXRT1062, which is configured similar to the evaluation board(EVK 1060).

The difference is that I have a flash S25LP064DJBLE flash which is similar (3.3v)

If I use Jlink Plus (Segger) the program is loaded and executed correctly.

If I use the PE micro FX the program is loaded (it looks correctly) but then when it has to run it reads all 0x00s and the instructions are all MOVS.

Has anyone had this problem?

Thank you

Re: MiMXRT1062CVJ5B debugging problems

kerryzhou — Wed, 06 Apr 2022 09:20:41 GMT

Hi @robertomorsiani ,

If you can use the Segger JLINK, just use the JLINK to debug your RT1062+QSPI flash.

About the PEMicro debugger issues, it should be related to the flash driver, which IDE and version you are using? You can check the log, whether it calls the QSPI flashdriver for your PEmicro.

Best Regards,

Kerry

Re: MiMXRT1062CVJ5B debugging problems

robertomorsiani — Wed, 06 Apr 2022 09:45:39 GMT

MCUXpresso IDE v11.5.0 [Build 7232] [2022-01-11]

SDK_2.11.1 - Manifert Version 3.9.0

In the project FLASH Driver MIMXRT1060_SFDP_QSPI.cfx

PE Flash Algorithm issi_is25wp064_1x32x2meg_imxrt1062.arp

Re: MiMXRT1062CVJ5B debugging problems

kerryzhou — Wed, 06 Apr 2022 10:04:08 GMT

Hi @robertomorsiani ,

MIMXRT1060_SFDP_QSPI.cfx won't be used to PE.

PE just use issi_is25wp064_1x32x2meg_imxrt1062.arp, in my memory, in the old MCUXPresso IDE version, this works perfectly.

But seems, the new MCUXPresso IDE has the related issues.

Please also share me your log, I mean, PE download the total log, then I will try to find some way to check it.

Best Regards,

kerry

Re: MiMXRT1062CVJ5B debugging problems

robertomorsiani — Wed, 06 Apr 2022 11:26:35 GMT

Thanks so much but I managed to get it going.
I deleted the Debug.launch file and made a new one and now this problem hasn't occurred anymore.

I didn't understand what happened but for now it works.