Hardfault when debugging rt1189

arunkumar_g · ‎03-21-2024

Hello,

I imported rtos hello world demo app in vscode and when debugging, it hits a hardfault as shown in screenshot.

SDK-2.15, EVK- RT1189B0 , example app: freertos_hello_cm33. Linkserver v3.122. EVK SW5 0100

I'm not sure i'm seeing this same error as in https://community.nxp.com/t5/Cognex-i-MX8M-NOTE-Shared-with/Putting-heap-in-SRAM-OC1-leads-to-HardFa...

If it is VScode i'm not sure how edit the config variables.

Thanks

diego_charles · ‎04-02-2024

Hi @arunkumar_g

From the log, I can see that the on-board debugger ( MCU-Link ) is not running the latest version available.

INFO: MCU-Link firmware update check: local firmware [3.133] can be programmed on the selected probe ([FKEE1042ZRODR] [MCU-LINK on-board (r0E2) CMSIS-DAP V3.122])

You can update the on-board debugger as well.

Download and install the latest version of LinkServer https://www.nxp.com/lgfiles/updates/mcuxpresso/LinkServer_1.4.85.exe

Set the on-board debugger to ISP mode. By closing asserting the ISP pin of the LPC55s69, then doing a power cycle. On RevC2 board, this is the related jumper

After installing the new LinkServer.exe, please navigate to C:\nxp\LinkServer_1.4.85\MCU-LINK_installer\scripts. Run any of the below scripts, them remove the ISP jumper of the LPC55s69. If you are still experiencing issues with LinkServer, please test with J-Link.

Please try again to do a mass erase to the flash, and if you are still getting issues, let me know. We could do a mass erase over UART/USB using MCUXpresso Secure Provisioning Tool.

Diego

在原帖中查看解决方案

arunkumar_g · ‎03-27-2024

The explanation and fix for hard fault there is

"Please change the start address of OCRAM from 0x20480000 to 0x204A0000 and retest.

In the B0 silicon the first 72K OCRAM is used by OSSCA and sysROM."

But in this case I dont know whether that is the same issue and I cannot change that value in VScode anyway. I tried changing that value in .ld file but that doesn't seem to have any effect.

diego_charles · ‎03-27-2024

Hi @arunkumar_g

Thanks for letting me know.

I am checking this internally, let me get back to you soon with a response.

Best regards,

Diego

diego_charles · ‎04-01-2024

Hi @arunkumar_g

Many thanks for your patience so far, and for your report.

We ran the demo, and we did not met the hardfault. We tested with EVK Rev C2 and the same configuration you used, per our knowledge.

With regards, to the OCRAM, we do not expect that customers need to do additional setup. The SDK example should work as it is. But somehow you are getting this issue, that I want to narrow down.

Just to double check, we recommend doing a mass erase to the EVK's flash memory. Then test the demo one more time. If you are still getting issues, please support me with the following:

- The freertos_hello_cm33.elf you generated.
- Did the hardfault appeared before or after the demo prints hello world?
- The toolchain you used to compile the demo

All the best,

Diego

arunkumar_g · ‎04-01-2024

EVK is Rev B.

Hard fault happens before demo print.

ELF is attached

Toolchain is ../.mcuxpressotools/arm-gnu-toolchain-12.3.rel1-mingw-w64-i686-arm-none-eabi"

How to do a mass erase? I tried with Linkserver flash programmer as in screenshot

But that gave an error as below

[2024-04-01T16:01:38.446] [proc] [info] Cmd: C":\Program Files\SEGGER\JLink\JLinkGDBServerCL.exe" -listprobes USB
[2024-04-01T16:01:38.447] [error] Operation could not be completed due to invalid PEmicro path: "C:\PEMicro\gdbserver\pegdbserver_console.exe". Please try again after correcting it in settings.
[2024-04-01T16:01:38.449] [error] Operation could not be completed due to invalid PEmicro path: "C:\PEMicro\gdbserver\pegdbserver_console.exe". Please try again after correcting it in settings.
[2024-04-01T16:01:38.455] [proc] [info] Cmd: C":\Program Files\SEGGER\JLink\JLinkGDBServerCL.exe" -version
[2024-04-01T16:01:38.463] [proc] [info] Cmd: c:\NXP\LinkServer_1.4.85\LinkServer.exe probes --json
[2024-04-01T16:01:38.464] [error] Operation could not be completed due to invalid PEmicro path: "C:\PEMicro\gdbserver\pegdbserver_console.exe". Please try again after correcting it in settings.
[2024-04-01T16:01:39.518] [proc] [info] Cmd: c:\NXP\LinkServer_1.4.85\LinkServer.exe flash --probe FKEE1042ZRODR --no-boot MIMXRT1189xxxxx:MIMXRT1180-EVK load c:\nxp\src\demo\mimxrt1180evk_freertos_hello_cm33_1\armgcc\debug\freertos_hello_cm33.elf --erase-all
[2024-04-01T16:01:43.140] [proc] [error] c:\NXP\LinkServer_1.4.85\LinkServer.exe exited with code 4294967295
[2024-04-01T16:01:43.140] [proc] [error] Firmware update check: - the update can be performed using `auto` mode
Ns: MCUXpresso IDE RedlinkMulti Driver v11.9 (Dec 11 2023 18:02:10 - crt_emu_cm_redlink.exe build 2)
Pc: (  0) Reading remote configuration
Wc(03). No cache support.
Nc: Found chip XML file in ....\AppData\Local\Temp\tmp_ojq74og\MIMXRT1189xxxxx.xml
Pc: (  5) Remote configuration complete
Nc: Reconnected to existing LinkServer process.
Wc: ============= SCRIPT: RT1180_connect_M33_wake_M7.scp =============
Wc: RT1180 Connect M33 and Wake M7 to DTC Script
Wc: DpID = 5BA02477
Wc: APID = 0x74770001
Wc: ************ System Reset *************
Wc: ********** Initialize CM33 ************
Wc: Filling 0xE000E180 + 0x00000040 with 0xFFFFFFFF
Wc: Filling 0xE000E280 + 0x00000040 with 0xFFFFFFFF
Wc: Filling 0x201E0000 + 0x00020000 with 0x00000000
Wc: Filling 0x20200008 + 0x0001FFF8 with 0x00000000
Wc: ============= END SCRIPT =========================================
Nc: Probe Firmware: MCU-LINK on-board (r0E2) CMSIS-DAP V3.122 (NXP Semiconductors)
Nc: Serial Number:  FKEE1042ZRODR
Nc: VID:PID:  1FC9:0143
Nc: USB Path: 0001:0004:00
Nc: Using memory from core 3 after searching for a good core
Pc: ( 30) Emulator Connected
Nc: processor is in secure mode
Pc: ( 40) Debug Halt
Pc: ( 50) CPU ID
Nc: debug interface type      = CoreSight DP (DAP DP ID 5BA02477) over SWD TAP 0
Nc: processor type            = Cortex-M33 (CPU ID 00000D21) on DAP AP 3
Nc: number of h/w breakpoints = 8
Nc: number of flash patches   = 0
Nc: number of h/w watchpoints = 4
Nc: Probe(0): Connected&Reset. DpID: 5BA02477. CpuID: 00000D21. Info: <None>
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Ns: Content of CoreSight Debug ROM(s):
Nc: RBASE E00FF000: CID B105100D PID 04000BB4C9 ROM (type 0x1)
Nc: ROM 1 E000E000: CID B105900D PID 04000BBD21 CSt ARM ARMv8-M type 0x0 Misc - Undefined
Nc: ROM 1 E0001000: CID B105900D PID 04000BBD21 CSt ARM DWTv2 type 0x0 Misc - Undefined
Nc: ROM 1 E0002000: CID B105900D PID 04000BBD21 CSt ARM FPBv2 type 0x0 Misc - Undefined
Nc: ROM 1 E0000000: CID B105900D PID 04000BBD21 CSt ARM ITMv2 type 0x43 Trace Source - Bus
Nc: ROM 1 E0041000: CID B105900D PID 04002BBD21 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
Nc: ROM 1 E0042000: CID B105900D PID 04000BBD21 CSt ARM CTIv2 type 0x14 Debug Control - Trigger, e.g. ECT
Nc: NXP: MIMXRT1189xxxxx
Nc: Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MIMXRT1180_SFDP_FlexSPI1_A_QSPI.cfx
Nc: Image 'iMXRT1180_SFDP_FlexSPI1_A_QSPI Dec 12 2023 17:27:31'
Nc: Opening flash driver MIMXRT1180_SFDP_FlexSPI1_A_QSPI.cfx
Nc: VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.
Nc: Using SOFT reset to run the flash driver
Nc: Flash variant 'iMXRT1180_SFDP_FlexSPI1_A_QSPI Dec 12 2023 17:27:31' detected (16MB = 256*64K at 0x28000000)
Nc: Closing flash driver MIMXRT1180_SFDP_FlexSPI1_A_QSPI.cfx
Nc: Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MIMXRT1180_SFDP_FlexSPI1_A_QSPI_S.cfx
Nc: Image 'iMXRT1180_SFDP_FlexSPI1_A_QSPI (Secure) Dec 12 2023 17:28:24'
Nc: Opening flash driver MIMXRT1180_SFDP_FlexSPI1_A_QSPI_S.cfx
Nc: VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.
Nc: Using SOFT reset to run the flash driver
Nc: Flash variant 'iMXRT1180_SFDP_FlexSPI1_A_QSPI (Secure) Dec 12 2023 17:28:24' detected (16MB = 256*64K at 0x38000000)
Nc: Closing flash driver MIMXRT1180_SFDP_FlexSPI1_A_QSPI_S.cfx
Pc: ( 65) Chip Setup Complete
Pc: ( 70) License Check Complete
Nt: Loading 'freertos_hello_cm33.elf' ELF 0x0FFE0000 len 0x803C
Ed:05: File 'freertos_hello_cm33.elf' load failure: Ef(11). No flash configured at the specified address.
Pc: (100) Target Operation Failed

INFO: Exact match for MIMXRT1189xxxxx:MIMXRT1180-EVK found
INFO: Selected device MIMXRT1189xxxxx:MIMXRT1180-EVK
INFO: Getting available probes
INFO: Selecting probe by serial substring
INFO: Selected probe #1 FKEE1042ZRODR (MCU-LINK on-board (r0E2) CMSIS-DAP V3.122)
INFO: MCU-Link firmware update check: local firmware [3.133] can be programmed on the selected probe ([FKEE1042ZRODR] [MCU-LINK on-board (r0E2) CMSIS-DAP V3.122])
CRITICAL: Critical error
ERRMSG: subprocess.CalledProcessError: Command '['c:\\NXP\\LinkServer_1.4.85\\binaries\\crt_emu_cm_redlink.exe', '--redlink-port', '11111', '--flash-dir', 'c:\\NXP\\LinkServer_1.4.85\\binaries\\Flash', '-x', '.....\\AppData\\Local\\Temp\\tmp_ojq74og', '-pMIMXRT1189xxxxx', '--vendor', 'NXP', '-g', '--cache', 'dis', '--probeserial', 'FKEE1042ZRODR', '--coreindex', '3', '--no-packed', '--dapstride', 'short', '--connectscript', 'RT1180_connect_M33_wake_M7.scp', '--flash-mass-load-exec', 'C:\\nxp\\src\\demo\\mimxrt1180evk_freertos_hello_cm33_1\\armgcc\\debug\\freertos_hello_cm33.elf']' returned non-zero exit status 1.

diego_charles · ‎04-01-2024

Hi @arunkumar_g

Thanks for your reply, I am checking with my peer, Iet me get back to you as soon as possible.

@arunkumar_g , here is an update. Please set the RT1180 into serial downloader mode and do a power cycle. The attempt to do a mass erase again using LinkServer/SWD.

Please let me know your results.

I hope this could help you.

Diego

arunkumar_g · ‎04-02-2024

Thanks, I changed the switch to 0001 and repeated the same using linkserver flash programmer.

Here is the output - different than earlier, but still reported failure

[2024-04-02T08:38:04.426] [error] Operation could not be completed due to invalid PEmicro path: "C:\PEMicro\gdbserver\pegdbserver_console.exe". Please try again after correcting it in settings.
[2024-04-02T08:38:04.435] [proc] [info] Cmd: C":\Program Files\SEGGER\JLink\JLinkGDBServerCL.exe" -listprobes USB
[2024-04-02T08:38:04.438] [error] Operation could not be completed due to invalid PEmicro path: "C:\PEMicro\gdbserver\pegdbserver_console.exe". Please try again after correcting it in settings.
[2024-04-02T08:38:04.445] [proc] [info] Cmd: C":\Program Files\SEGGER\JLink\JLinkGDBServerCL.exe" -version
[2024-04-02T08:38:04.457] [proc] [info] Cmd: c:\NXP\LinkServer_1.4.85\LinkServer.exe probes --json
[2024-04-02T08:38:04.458] [error] Operation could not be completed due to invalid PEmicro path: "C:\PEMicro\gdbserver\pegdbserver_console.exe". Please try again after correcting it in settings.
[2024-04-02T08:38:05.558] [proc] [info] Cmd: c:\NXP\LinkServer_1.4.85\LinkServer.exe flash --probe FKEE1042ZRODR --no-boot MIMXRT1189xxxxx:MIMXRT1180-EVK load c:\nxp\src\demo\mimxrt1180evk_freertos_hello_cm33_1\armgcc\debug\freertos_hello_cm33.elf --erase-all
[2024-04-02T08:38:19.352] [proc] [error] c:\NXP\LinkServer_1.4.85\LinkServer.exe exited with code 4294967295
[2024-04-02T08:38:19.352] [proc] [error] Firmware update check: - the update can be performed using `auto` mode
Ns: MCUXpresso IDE RedlinkMulti Driver v11.9 (Dec 11 2023 18:02:10 - crt_emu_cm_redlink.exe build 2)
Pc: (  0) Reading remote configuration
Wc(03). No cache support.
Nc: Found chip XML file in ......\AppData\Local\Temp\tmp79v798pm\MIMXRT1189xxxxx.xml
Pc: (  5) Remote configuration complete
Nc: Reconnected to existing LinkServer process.
Wc: ============= SCRIPT: RT1180_connect_M33_wake_M7.scp =============
Wc: RT1180 Connect M33 and Wake M7 to DTC Script
Wc: DpID = 5BA02477
Wc: APID = 0x74770001
Wc: ************ System Reset *************
Wc: ********** Initialize CM33 ************
Wc: Filling 0xE000E180 + 0x00000040 with 0xFFFFFFFF
Wc: Filling 0xE000E280 + 0x00000040 with 0xFFFFFFFF
Wc: Filling 0x201E0000 + 0x00020000 with 0x00000000
Wc: Filling 0x20200008 + 0x0001FFF8 with 0x00000000
Wc: ============= END SCRIPT =========================================
Nc: Probe Firmware: MCU-LINK on-board (r0E2) CMSIS-DAP V3.122 (NXP Semiconductors)
Nc: Serial Number:  FKEE1042ZRODR
Nc: VID:PID:  1FC9:0143
Nc: USB Path: 0001:000d:00
Nc: Using memory from core 3 after searching for a good core
Pc: ( 30) Emulator Connected
Nc: processor is in secure mode
Pc: ( 40) Debug Halt
Pc: ( 50) CPU ID
Nc: debug interface type      = CoreSight DP (DAP DP ID 5BA02477) over SWD TAP 0
Nc: processor type            = Cortex-M33 (CPU ID 00000D21) on DAP AP 3
Nc: number of h/w breakpoints = 8
Nc: number of flash patches   = 0
Nc: number of h/w watchpoints = 4
Nc: Probe(0): Connected&Reset. DpID: 5BA02477. CpuID: 00000D21. Info: <None>
Nc: Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Ns: Content of CoreSight Debug ROM(s):
Nc: RBASE E00FF000: CID B105100D PID 04000BB4C9 ROM (type 0x1)
Nc: ROM 1 E000E000: CID B105900D PID 04000BBD21 CSt ARM ARMv8-M type 0x0 Misc - Undefined
Nc: ROM 1 E0001000: CID B105900D PID 04000BBD21 CSt ARM DWTv2 type 0x0 Misc - Undefined
Nc: ROM 1 E0002000: CID B105900D PID 04000BBD21 CSt ARM FPBv2 type 0x0 Misc - Undefined
Nc: ROM 1 E0000000: CID B105900D PID 04000BBD21 CSt ARM ITMv2 type 0x43 Trace Source - Bus
Nc: ROM 1 E0041000: CID B105900D PID 04002BBD21 CSt ARM ETMv4.0 type 0x13 Trace Source - Core
Nc: ROM 1 E0042000: CID B105900D PID 04000BBD21 CSt ARM CTIv2 type 0x14 Debug Control - Trigger, e.g. ECT
Nc: NXP: MIMXRT1189xxxxx
Nc: Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MIMXRT1180_SFDP_FlexSPI1_A_QSPI.cfx
Nc: Image 'iMXRT1180_SFDP_FlexSPI1_A_QSPI Dec 12 2023 17:27:31'
Nc: Opening flash driver MIMXRT1180_SFDP_FlexSPI1_A_QSPI.cfx
Nc: VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.
Nc: Using SOFT reset to run the flash driver
Nc: AFTER driver startup timeout (302 5ms retries)
Wc: Driver Addresses
Wc:  Start:  20000000
Wc:  Entry:  2000009D
Wc:  End:    2000074C
Wc:  Stack:  20002750
Wc:  Mailbox:2000A750
Wc: Driver Register State
Wc:  R0:     525E0000
Wc:  R1:     00000008
Wc:  R2:     20000490
Wc:  R3:     00000001
Wc:  R4:     00000002
Wc:  R5:     00000000
Wc:  R6:     200004C4
Wc:  R7:     00000000
Wc:  R8:     00000000
Wc:  R9:     00000000
Wc:  R10:    00000000
Wc:  R11:    00000000
Wc:  R12:    00000004
Wc:  SP:     20002700
Wc:  LR:     20000285
Wc:  PC:     10008F20
Wc:  xPSR:   69000000
Wc:  MSP:    20002700
Wc:  PSP:    20002750
Wc:  CFBP:   00000001 (CONTROL=0x0, FAULTMASK=0x0, BASEPRI=0x0, PRIMASK=0x1)
Nc: Flash Driver V.2 startup failed - rc Ef(34): Timed-out initializing flash.
Ec: vendor chip initialization failed - Ef(34): Timed-out initializing flash.
Wc: failed to initialize flash driver MIMXRT1180_SFDP_FlexSPI1_A_QSPI.cfx
Nc: Inspected v.2 External Flash Device on SPI using SFDP JEDEC ID MIMXRT1180_SFDP_FlexSPI1_A_QSPI_S.cfx
Nc: Image 'iMXRT1180_SFDP_FlexSPI1_A_QSPI (Secure) Dec 12 2023 17:28:24'
Nc: Opening flash driver MIMXRT1180_SFDP_FlexSPI1_A_QSPI_S.cfx
Nc: VECTRESET requested, but not supported on ARMv8-M CPUs. Using SOFTRESET instead.
Nc: Using SOFT reset to run the flash driver
Nc: AFTER driver startup timeout (302 5ms retries)
Wc: Driver Addresses
Wc:  Start:  20000000
Wc:  Entry:  2000009D
Wc:  End:    2000074C
Wc:  Stack:  20002750
Wc:  Mailbox:2000A750
Wc: Driver Register State
Wc:  R0:     525E0000
Wc:  R1:     00000008
Wc:  R2:     20000490
Wc:  R3:     00000001
Wc:  R4:     00000002
Wc:  R5:     00000000
Wc:  R6:     200004C4
Wc:  R7:     00000000
Wc:  R8:     00000000
Wc:  R9:     00000000
Wc:  R10:    00000000
Wc:  R11:    00000000
Wc:  R12:    00000004
Wc:  SP:     20002700
Wc:  LR:     20000285
Wc:  PC:     10008F20
Wc:  xPSR:   69000000
Wc:  MSP:    20002700
Wc:  PSP:    20002750
Wc:  CFBP:   00000001 (CONTROL=0x0, FAULTMASK=0x0, BASEPRI=0x0, PRIMASK=0x1)
Nc: Flash Driver V.2 startup failed - rc Ef(34): Timed-out initializing flash.
Ec: vendor chip initialization failed - Ef(34): Timed-out initializing flash.
Wc: failed to initialize flash driver MIMXRT1180_SFDP_FlexSPI1_A_QSPI_S.cfx
Pc: ( 65) Chip Setup Complete
Pc: (100) Target Operation Failed

INFO: Exact match for MIMXRT1189xxxxx:MIMXRT1180-EVK found
INFO: Selected device MIMXRT1189xxxxx:MIMXRT1180-EVK
INFO: Getting available probes
INFO: Selecting probe by serial substring
INFO: Selected probe #1 FKEE1042ZRODR (MCU-LINK on-board (r0E2) CMSIS-DAP V3.122)
INFO: MCU-Link firmware update check: local firmware [3.133] can be programmed on the selected probe ([FKEE1042ZRODR] [MCU-LINK on-board (r0E2) CMSIS-DAP V3.122])
CRITICAL: Critical error
ERRMSG: subprocess.CalledProcessError: Command '['c:\\NXP\\LinkServer_1.4.85\\binaries\\crt_emu_cm_redlink.exe', '--redlink-port', '11111', '--flash-dir', 'c:\\NXP\\LinkServer_1.4.85\\binaries\\Flash', '-x', 'C:\\Users\\agopinat\\AppData\\Local\\Temp\\tmp79v798pm', '-pMIMXRT1189xxxxx', '--vendor', 'NXP', '-g', '--cache', 'dis', '--probeserial', 'FKEE1042ZRODR', '--coreindex', '3', '--no-packed', '--dapstride', 'short', '--connectscript', 'RT1180_connect_M33_wake_M7.scp', '--flash-mass-load-exec', 'C:\\nxp\\src\\demo\\mimxrt1180evk_freertos_hello_cm33_1\\armgcc\\debug\\freertos_hello_cm33.elf']' returned non-zero exit status 1.

diego_charles · ‎04-02-2024

Hi @arunkumar_g

From the log, I can see that the on-board debugger ( MCU-Link ) is not running the latest version available.

INFO: MCU-Link firmware update check: local firmware [3.133] can be programmed on the selected probe ([FKEE1042ZRODR] [MCU-LINK on-board (r0E2) CMSIS-DAP V3.122])

You can update the on-board debugger as well.

Download and install the latest version of LinkServer https://www.nxp.com/lgfiles/updates/mcuxpresso/LinkServer_1.4.85.exe

Set the on-board debugger to ISP mode. By closing asserting the ISP pin of the LPC55s69, then doing a power cycle. On RevC2 board, this is the related jumper

After installing the new LinkServer.exe, please navigate to C:\nxp\LinkServer_1.4.85\MCU-LINK_installer\scripts. Run any of the below scripts, them remove the ISP jumper of the LPC55s69. If you are still experiencing issues with LinkServer, please test with J-Link.

Please try again to do a mass erase to the flash, and if you are still getting issues, let me know. We could do a mass erase over UART/USB using MCUXpresso Secure Provisioning Tool.

Diego

arunkumar_g · ‎04-02-2024

OK I updated firmware to 3.133, did a mass erase via mcuxpresso ide and now vscode debug works without segfault. Thanks for the help.

diego_charles · ‎04-02-2024

Glad to know that this solved the issue, thank you.

diego_charles · ‎03-26-2024

Hi @arunkumar_g

Unfortunately, I can not access to the community space your are pointing to.

Currently, I still do not have this board in my office, but let me check how can replicate this, asking another colleague.

Still, I want to know if you get any different result by trying to change build configuration for the project.

Thanks a lot!

Diego

arunkumar_g · ‎03-25-2024

bump...