i.MX ProcessorsのトピックRe: Could not debug my new custom board

Could not debug my new custom board

fma23 — Wed, 20 Nov 2019 01:20:58 GMT

I am trying to debug my code using my new custom board that has iMX RT1062 MCU on it and a 16 MB flash on it: IS25LP128F-JBLE.

I verified that my boot configuration is correct. I set it internal boot. However, when I run my debugger, I get the error below:

Break at address "0xdeadbeee" with no debug information available, or outside of program code.

I am using Segger debugger. Can any one tell me what this error is all about?

Re: Could not debug my new custom board

fma23 — Wed, 20 Nov 2019 23:37:17 GMT

What I am trying to do is that I want to program my board so that I can boot from an external flash using QSPI (part number: IS25LP128F.)

The board is configured to run QSPI, but when I use Segger Jtag to debug the code this is what I get in deassembly:

......... ...
00217398:   lsls    r0, r0, #14
0021739a:   bpl.n   0x2173a4
0021739c:   ldr     r0, [r7, #0]
0021739e:   tst.w   r0, #2147483648 ; 0x80000000
002173a2:   bpl.n   0x217396
002173a4:   ldr     r0, [r6, #0]
002173a6:   lsls    r0, r0, #27
002173a8:   bmi.n   0x2173dc
002173aa:   bl      0x21aa3c
002173ae:   cbz     r0, 0x2173dc
002173b0:   ldr     r0, [r4, #0]
002173b2:   movw    r2, #57054      ; 0xdede
002173b6:   ldr     r1, [r4, #4]
002173b8:   adds    r0, r0, r2
002173ba:   str     r0, [r4, #0]
002173bc:   adc.w   r1, r1, #0
002173c0:   str     r1, [r4, #4]
002173c2:   bl      0x21a5a0
002173c6:   ldr     r0, [r4, #0]
002173c8:   movw    r2, #8482       ; 0x2122
002173cc:   ldr     r1, [r4, #4]
002173ce:   movt    r2, #65535      ; 0xffff
002173d2:   adds    r2, r0, r2
002173d4:   str     r2, [r4, #0]
002173d6:   adc.w   r0, r1, #4294967295
002173da:   str     r0, [r4, #4]
002173dc:   bl      0x20d102
002173e0:   cmp     r0, #0
002173e2:   beq.n   0x217396
002173e4:   ldr     r0, [r4, #0]
002173e6:   movw    r2, #57054      ; 0xdede
002173ea:   ldr     r1, [r4, #4]
002173ec:   adds    r2, r0, r2
002173ee:   str     r2, [r4, #0]
002173f0:   adc.w   r0, r1, #0
002173f4:   str     r0, [r4, #4]
002173f6:   bl      0x21a5b8
002173fa:   ldr     r0, [r4, #0]
002173fc:   movw    r1, #8482       ; 0x2122
00217400:   ldr     r2, [r4, #4]
00217402:   movt    r1, #65535      ; 0xffff
00217406:   adds    r1, r0, r1
00217408:   str     r1, [r4, #0]
0021740a:   adc.w   r0, r2, #4294967295
0021740e:   str     r0, [r4, #4]
00217410:   b.n     0x217396
00217412:   stmdb   sp!, {r3, r4, r5, r6, r7, r8, r9, lr}
00217416:   movw    r1, #32800      ; 0x8020
0021741a:   movt    r1, #16399      ; 0x400f
0021741e:   ldr     r6, [r1, #0]
00217420:   str     r6, [sp, #0]
00217422:   mov.w   r9, #0
......... ...

Re: Could not debug my new custom board

kerryzhou — Thu, 21 Nov 2019 03:25:25 GMT

Hi Farid Mabrouk,

Thank you for your interest in the NXP MIMXRT product, I would like to provide service for you.

Please use the JLINK commander to connect your customer MIMXRT1052 board, can you find the ARM Cortex-M7 core?

When you use the debugger, do you enable the QE bit?

If you can find the ARM core, I suggest you use the MCUBootUtility tool to conect your board in the serial download mode through the UART or the USB HID.

The MCUBootutility download link:

https://github.com/JayHeng/NXP-MCUBootUtility/releases/tag/v2.0.0
the related user manual is:
https://github.com/JayHeng/NXP-MCUBootUtility

After you test, you also can share your JLINK commander connect result, you also can tell me when you use the debugger, what's the IDE you are using?

Have a great day,
Kerry

-------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------

Re: Could not debug my new custom board

farid_mabrouk — Thu, 21 Nov 2019 03:57:13 GMT

I used Segger jlink commander, and I was able to connect, and found the ARM core. Thus I don’t think the issue is the jtag, but rather a configuration issue. I’m using a 16MB flash.

Do I need to have the reset and write enable pulled up high? I noticed these signals on iMX RT1060-evk development board are not pulled up high. How about config1 and config2, what should the values be? Config1 in my case is set to 1, config2 is set to 0x07; boot0 is low and boot1 is high.

How do you Enable the QE bit? I read that Segger jtag is configured by default to run in QSPI.

I’m using MCU expresso; and I’m using the GPIO example code to rest my board.

Thank you,

Farid

Re: Could not debug my new custom board

farid_mabrouk — Thu, 21 Nov 2019 06:17:43 GMT

Im using this flash IS25LP128, by the way. Please comment on the pull up resistors for reset and write enable pins. Do I need pull up resistors or not.

Re: Could not debug my new custom board

kerryzhou — Thu, 21 Nov 2019 06:22:09 GMT

Hi Andre marcus,

Thanks for your updated information.

Please run this SDK code from the RAM with your JLINK debugger:

SDK_2.6.2_EVK-MIMXRT1060\boards\evkmimxrt1060\driver_examples\flexspi\nor\polling_transfer

Please check can you do the external qspi flash erase, write and read operation.

This code already contains the QE enable code.

If this code can't do the flash operation, it means your hardware side still have problems, especially about the flash circuit.

About the BOOT_CFG and BOOT_MODE configuration.

All BOOT_CFG can be configured to 0, BOOT_MODE can be configured to the internal boot mode, BOOT_MODE[1:0]=10.

BTW, do you also try the MCUBootUtility tool in the serial download mode, whether that tool can find the flash or not? That tool can help you enable the QE automatically.

Please try it again.

Any updated information, please kindly let me know.

Have a great day,
Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

Re: Could not debug my new custom board

kerryzhou — Thu, 21 Nov 2019 06:37:12 GMT

Hi Andre marcus,

IS25LP128 circuit should be the same as IS25WP064AJBLE, but just IS25LP128 is 3V power.

About the pull up resistor for reset, do you mean the RT RESET pin? You can refer to the MIMXRT1060-EVK board circuit.

Have a great day,
Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

Re: Could not debug my new custom board

farid_mabrouk — Thu, 21 Nov 2019 07:27:55 GMT

Hi Kerry!

Thanks you for your support, I tried running the example you mentioned by removing the qspi fash memory configuration( I went to MCU settings and just deleted the board flash configuration) then I run the code. I was able to program the processor this way. In this case, I believe I was booting from the RAM or the internal flash that’s why the code run successfully, am I right? If I run the code as it is with the qspi flash configured, I can’t do any erase or programming.

But with jlink commander I was able to connect to the processor. I don’t know if I can use jlink commander to erase qspi flash?

The first three bits of Config2 should be 1 based on the mcu manual for QSPI flash. But you mentioned they can be Zero. Am I right?

Also I would like to know how the flexspi is configured in the source code for the demo examples of 1060-evil dev board. I don’t see those pins configured in mux.c files. Could you please say how this flexspi is configured ( pins and clock)

Cheers,

farid

Re: Could not debug my new custom board

kerryzhou — Thu, 21 Nov 2019 10:33:18 GMT

Hi Andre marcus,

1. \polling_transfer

Do you download to the RAM, run all the code, this project already contains the erase, program and read.

Don't download to the external flash, just download to the RAM, and debug it in the RAM.

2. If it works, you can test the led_blinky code, and download it to the external flash.

3. JLINK erase,

You can follow my following steps, the JLINK can erase the external QSPI flash:

4. BOOT_CFG2[2:0]

No, you need to select 000, not the 111.

Please note, 111 qspi is used for the secondary pinmux option.

5. pinmux already contains the flexspi pin

Wish it helps you!

If you still have questions about it, please kindly let me know.

Have a great day,
Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

Re: Could not debug my new custom board

farid_mabrouk — Thu, 21 Nov 2019 19:38:41 GMT

Hi Kerry! please see the messages I get when I try to do flash erase all

Re: Could not debug my new custom board

farid_mabrouk — Thu, 21 Nov 2019 19:39:52 GMT

Re: Could not debug my new custom board

farid_mabrouk — Thu, 21 Nov 2019 22:30:09 GMT

Now my BOOT_CFG1[0-7] are set to 0. and BOOT_CFG2[0-3] are also set to zero. my Boot0 is set to 0 and BOOT1 is set to 1. I still cannot erase or program the QSPI flash.

I just want to let you know that I am using these pins for my Flexspi interface. These are not the same as in the iMX RT1060-evk dev board.

also please see the test results I got with jlink commander:

IOMUXC_SetPinMux(
      IOMUXC_GPIO_AD_B1_09_FLEXSPIA_DQS,      /* GPIO_SD_B1_05 is configured as FLEXSPIA_DQS */
      1U);                                    /* Software Input On Field: Force input path of pad GPIO_SD_B1_05 */
IOMUXC_SetPinMux(
      IOMUXC_GPIO_AD_B1_15_FLEXSPIA_SS0_B,    /* GPIO_SD_B1_06 is configured as FLEXSPIA_SS0_B */
      1U);                                    /* Software Input On Field: Force input path of pad GPIO_SD_B1_06 */
IOMUXC_SetPinMux(
      IOMUXC_GPIO_AD_B1_14_FLEXSPIA_SCLK,     /* GPIO_SD_B1_07 is configured as FLEXSPIA_SCLK */
      1U);                                    /* Software Input On Field: Force input path of pad GPIO_SD_B1_07 */
IOMUXC_SetPinMux(
      IOMUXC_GPIO_AD_B1_13_FLEXSPIA_DATA00,   /* GPIO_SD_B1_08 is configured as FLEXSPIA_DATA00 */
      1U);                                    /* Software Input On Field: Force input path of pad GPIO_SD_B1_08 */
IOMUXC_SetPinMux(
      IOMUXC_GPIO_AD_B1_12_FLEXSPIA_DATA01,   /* GPIO_SD_B1_09 is configured as FLEXSPIA_DATA01 */
      1U);                                    /* Software Input On Field: Force input path of pad GPIO_SD_B1_09 */
IOMUXC_SetPinMux(
      IOMUXC_GPIO_AD_B1_11_FLEXSPIA_DATA02,   /* GPIO_SD_B1_10 is configured as FLEXSPIA_DATA02 */
      1U);                                    /* Software Input On Field: Force input path of pad GPIO_SD_B1_10 */
IOMUXC_SetPinMux(
      IOMUXC_GPIO_AD_B1_10_FLEXSPIA_DATA03,   /* GPIO_SD_B1_11 is configured as FLEXSPIA_DATA03 */
      1U);                                    /* Software Input On Field: Force input path of pad GPIO_SD_B1_11 */



       IOMUXC_SetPinConfig(
      IOMUXC_GPIO_AD_B1_09_FLEXSPIA_DQS,      /* GPIO_SD_B1_05 PAD functional properties : */
      0x10F1u);                               /* Slew Rate Field: Fast Slew Rate
                                                 Drive Strength Field: R0/6
                                                 Speed Field: max(200MHz)
                                                 Open Drain Enable Field: Open Drain Disabled
                                                 Pull / Keep Enable Field: Pull/Keeper Enabled
                                                 Pull / Keep Select Field: Keeper
                                                 Pull Up / Down Config. Field: 100K Ohm Pull Down
                                                 Hyst. Enable Field: Hysteresis Disabled */
IOMUXC_SetPinConfig(
      IOMUXC_GPIO_AD_B1_15_FLEXSPIA_SS0_B,    /* GPIO_SD_B1_06 PAD functional properties : */
      0x10F1u);                               /* Slew Rate Field: Fast Slew Rate
                                                 Drive Strength Field: R0/6
                                                 Speed Field: max(200MHz)
                                                 Open Drain Enable Field: Open Drain Disabled
                                                 Pull / Keep Enable Field: Pull/Keeper Enabled
                                                 Pull / Keep Select Field: Keeper
                                                 Pull Up / Down Config. Field: 100K Ohm Pull Down
                                                 Hyst. Enable Field: Hysteresis Disabled */
IOMUXC_SetPinConfig(
      IOMUXC_GPIO_AD_B1_14_FLEXSPIA_SCLK,     /* GPIO_SD_B1_07 PAD functional properties : */
      0x10F1u);                               /* Slew Rate Field: Fast Slew Rate
                                                 Drive Strength Field: R0/6
                                                 Speed Field: max(200MHz)
                                                 Open Drain Enable Field: Open Drain Disabled
                                                 Pull / Keep Enable Field: Pull/Keeper Enabled
                                                 Pull / Keep Select Field: Keeper
                                                 Pull Up / Down Config. Field: 100K Ohm Pull Down
                                                 Hyst. Enable Field: Hysteresis Disabled */
IOMUXC_SetPinConfig(
      IOMUXC_GPIO_AD_B1_13_FLEXSPIA_DATA00,   /* GPIO_SD_B1_08 PAD functional properties : */
      0x10F1u);                               /* Slew Rate Field: Fast Slew Rate
                                                 Drive Strength Field: R0/6
                                                 Speed Field: max(200MHz)
                                                 Open Drain Enable Field: Open Drain Disabled
                                                 Pull / Keep Enable Field: Pull/Keeper Enabled
                                                 Pull / Keep Select Field: Keeper
                                                 Pull Up / Down Config. Field: 100K Ohm Pull Down
                                                 Hyst. Enable Field: Hysteresis Disabled */
IOMUXC_SetPinConfig(
      IOMUXC_GPIO_AD_B1_12_FLEXSPIA_DATA01,   /* GPIO_SD_B1_09 PAD functional properties : */
      0x10F1u);                               /* Slew Rate Field: Fast Slew Rate
                                                 Drive Strength Field: R0/6
                                                 Speed Field: max(200MHz)
                                                 Open Drain Enable Field: Open Drain Disabled
                                                 Pull / Keep Enable Field: Pull/Keeper Enabled
                                                 Pull / Keep Select Field: Keeper
                                                 Pull Up / Down Config. Field: 100K Ohm Pull Down
                                                 Hyst. Enable Field: Hysteresis Disabled */
IOMUXC_SetPinConfig(
      IOMUXC_GPIO_AD_B1_11_FLEXSPIA_DATA02,   /* GPIO_SD_B1_10 PAD functional properties : */
      0x10F1u);                               /* Slew Rate Field: Fast Slew Rate
                                                 Drive Strength Field: R0/6
                                                 Speed Field: max(200MHz)
                                                 Open Drain Enable Field: Open Drain Disabled
                                                 Pull / Keep Enable Field: Pull/Keeper Enabled
                                                 Pull / Keep Select Field: Keeper
                                                 Pull Up / Down Config. Field: 100K Ohm Pull Down
                                                 Hyst. Enable Field: Hysteresis Disabled */
IOMUXC_SetPinConfig(
      IOMUXC_GPIO_AD_B1_10_FLEXSPIA_DATA03,   /* GPIO_SD_B1_11 PAD functional properties : */
      0x10F1u);                               /* Slew Rate Field: Fast Slew Rate
                                                 Drive Strength Field: R0/6
                                                 Speed Field: max(200MHz)
                                                 Open Drain Enable Field: Open Drain Disabled
                                                 Pull / Keep Enable Field: Pull/Keeper Enabled
                                                 Pull / Keep Select Field: Keeper
                                                 Pull Up / Down Config. Field: 100K Ohm Pull Down
                                                 Hyst. Enable Field: Hysteresis Disabled */

Re: Could not debug my new custom board

farid_mabrouk — Thu, 21 Nov 2019 22:33:54 GMT

here is my initial boot config, but now I changed it as I mentioned in the above message

Re: Could not debug my new custom board

farid_mabrouk — Thu, 21 Nov 2019 23:14:25 GMT

With the new changes for config1 and config2; I run the example: evkmimxrt1060_flexspi_nor_polling_transfer and I ended up with the error below.

if (memcmp(s_nor_program_buffer, s_nor_read_buffer, sizeof(s_nor_program_buffer)))
    {
        PRINTF("Erase data - read out data value incorrect !\r\n ");
        return -1;
    }

Re: Could not debug my new custom board

kerryzhou — Fri, 22 Nov 2019 02:59:58 GMT

Hi Andre marcus,

You give me the key clue: I just want to let you know that I am using these pins for my Flexspi interface. These are not the same as in the iMX RT1060-evk dev board.

Please share your schematic with me, I need to check the detail pins, I also need to check whether your hardware is really supported by the ROM bootloader.

If you want to boot correctly, you must refer to the RT1060 RM, Table 8-1. ROM Bootloader Peripheral PinMux

Or ,do you use the secondary pinmux option?

Please share your schematic.

This is very important to the problem solving, if you are using the secondary pinmux, you can't use the JLINK debug it, because the JLINK programmer algorithm can't support it, the JLINK programmer algorithm just support the primary mode. Then you just can try the MCUBootUtility to download the code, if you are really using the secondary pimux option, you also make sure your primary didn't connect the useful flash.

Have a great day,
Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

Re: Could not debug my new custom board

farid_mabrouk — Fri, 22 Nov 2019 05:42:36 GMT

Hi Kerry!

Thanks a lot for your generous support. Yes indeed I’m using the secondary pinmux for flexspi signals. But just to let you know I managed to erase and program the qspi flash using Segger jtag and the same configuration I sent you in the schematics screen shot before.

I just used a different board and everything worked well. I just don’t know why the changes your recommended for the configuration are different than what I have, but still my board worked. Also I want to understand how the flexspi signals are configured. I did not explicitly configured them in Pinmux.c file.

but thanks for the help.

I have more questions about the eLCDIF peripheral. Can I forward them to you in a different thread?

Thank you so much!

Farid

Re: Could not debug my new custom board

kerryzhou — Fri, 22 Nov 2019 07:18:06 GMT

Hi Andre marcus,

Sorry, I think you are using the primary flexspi in the previous time.

If you are using the secondary pinmux, you still lneed to set the BOOT_CFG2[2:0] to 111, not 000, 000 is used for the primary flexspi.

Do you try the MCUBootUtility tool in the serial downloader mode, whether it works or not? Then your code don't need to configure the pinmux.c.

If you are using the IAR download the normal app, you also don't need to configure the pinmux.c for the flexspi.

But you need to modify the option0 and option1 in the .board

the parameters can be:

"--Qspi"      - QuadSPI NOR - Quad SDR Read (same if no arg is used)
"--QspiDDR"   - QuadSPI NOR - Quad DDR Read
"--Hyper1V8" - HyperFLASH 1V8
"--Hyper3V0" - HyperFLASH 3V0
"--MxicOpiDDR"- MXIC OPI DDR (OPI DDR enabled by default)
"--McrnOct"   - Micron Octal DDR
"--McrnOpi"   - Micron OPI DDR
"--McrnOpiDDR"- Micron OPI DDR (DDR read enabled by default):
"--AdstOpi"   - Adesto OPI DDR
"--Opt0 0x..."- set Option0 hex value
"--Opt1 0x..."- set Option1 hex value

You can try it.

About the eLCDIF issue, you can create the post and let me know, I will help you in your new post.

Have a great day,
Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

Re: Could not debug my new custom board

farid_mabrouk — Tue, 26 Nov 2019 00:47:54 GMT

Hello Kelly!

Everything was working fine as supposed to be. Now when I try to boot from the QSPI flash, I see the error below:

Now I know the issue I had in the past has nothing to do with my boad, but rather it is an issue with Segger Jtag adapter, any clue please how to fix this Segger problem?

Cheers!

Re: Could not debug my new custom board

kerryzhou — Tue, 26 Nov 2019 03:19:54 GMT

Hi Andre marcus,

Thanks for your updated information.

About the Segger JTAG problem, maybe you also need to contact with Segger side:

https://www.segger.com/support/technical-support/

They will be more family with their tools.

You said: Everything was working fine as supposed to be

What's the details working? program, erase, read? Now, just QSPI boot can't work, right?

Do you tried MCUBootUtility on your side? You never answer my question about this tool, just without the debugger, use the MCUBootutility tool, can you boot from QSPI flash after the code downloading?

Have a great day,
Kerry

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

Re: Could not debug my new custom board

farid_mabrouk — Tue, 26 Nov 2019 04:11:47 GMT

Hi Kerry!

I was previously able to erase, program and debug. I don’t know what happened to my Segger debugger. I tried installing mcu bootutility tool on my machine, but it does not install; I have windows 10. Any comments on this? If I can debug using bootutility tool, I should be fine, but does u boot allows for debugging?

Cheers!