Debug issue with SPU5746C MCU 176 pin

[ke_liang]

Hello NXP.

I have used a demo board to develop an application in MPU5746C-256 Pin MCU and I can successfuly debug my application.

Then I have ported my application project from 256 pin to 176 pin MCU and trying to debug it. But, I am not able to debug the application. It is haling at address "00000010:   se_illegal" and running  se_illegal instruction.

I have read the memory region of my application and it has loaded into the flash memory.

I need your help to sort this problem. I am sharing the logs which I have got from Console window.

Connection from "127.0.0.1" via 127.0.0.1. Connection from port "62757" to 7224
Copyright 2018 P&E Microcomputer Systems,Inc.
Command Line :C:\NXP\S32DS_Power_v2.1\eclipse\plugins\com.pemicro.debug.gdbjtag.ppc_1.9.9.201907200403\win32\pegdbserver_power_console -device=MPC5746C -startserver -singlesession -serverport=7224 -gdbmiport=6224 -interface=USBMULTILINK -speed=2500 -rese
Flash Data in range 0x00FA0000-0x00FA0007.
Flash Data in range 0x00FA0010-0x00FA0013.
Flash Data in range 0x01000000-0x01000167.
Flash Data in range 0x01001000-0x010010B3.
Flash Data in range 0x01002000-0x01002BFB.
Flash Data in range 0x01002C00-0x010151B2.
Flash Data in range 0x010151B4-0x01017F17.
Flash Data in range 0x01140000-0x01140167.
Flash Data in range 0x01141000-0x011410B3.
Flash Data in range 0x01142000-0x01142BFB.
Flash Data in range 0x01142C00-0x0114612B.

CMD>RE

Initializing.

Device IDCODE is $00000085
Device ID revision is $00000001
Initializing Ram Block 0x40000000-0x40007FFF.
MPC574xB/C/D Device detected.
Target has been RESET and is active.
CMD>CM C:\NXP\S32DS_Power_v2.1\eclipse\plugins\com.pemicro.debug.gdbjtag.ppc_1.9.9.201907200403\win32\gdi\P&E\nxp_mpc5746c_1x32x736k_cflash.pcp

Initializing.

Device IDCODE is $00000085
Device ID revision is $00000001
Initializing Ram Block 0x40000000-0x40007FFF.
MPC574xB/C/D Device detected.
Initialized.

;version 1.06, 06/27/2017, Copyright P&E Microcomputer Systems, www.pemicro.com [5746C_2944k]

;device NXP, MPC5746C, 1x32x736k, desc=CFlash

;begin_cs device=$00F90000, length=$002F0000, ram=$40000000

Loading programming algorithm ...
Done.
Programming sequency is : erase, blank check, program, and verify {default}
CMD>VC
Verifying object file CRC-16 to device ranges ...
block 00FA0000-00FA0007 ...
Ok.
block 00FA0010-00FA0013 ...
Calculated CRC-16 does not match block. (File = $3331, Device = $6184)
Current content of flash does not match application to be programmed

CMD>EM

Erasing.
Module has been erased.
CMD>PM

Programming.
Processing Object File Data ...


.
Programmed.
CMD>VC
Verifying object file CRC-16 to device ranges ...
block 00FA0000-00FA0007 ...
Ok.
block 00FA0010-00FA0013 ...
Ok.
block 01000000-01000167 ...
Ok.
block 01001000-010010B3 ...
Ok.
block 01002000-01002BFB ...
Ok.
block 01002C00-010151B2 ...
Ok.
block 010151B4-01017F17 ...
Ok.
block 01140000-01140167 ...
Ok.
block 01141000-011410B3 ...
Ok.
block 01142000-01142BFB ...
Ok.
block 01142C00-0114612B ...
Ok.
Checksum Verification Successful. (Cumulative CRC-16=$38B3)

CMD>RE

Initializing.

Device IDCODE is $00000085
Device ID revision is $00000001
Initializing Ram Block 0x40000000-0x40007FFF.
MPC574xB/C/D Device detected.
Target has been RESET and is active.

Device IDCODE is $00000085
Device ID revision is $00000001

Device IDCODE is $00000085
Device ID revision is $00000001

Starting reset script (C:\NXP\S32DS_Power_v2.1\eclipse\plugins\com.pemicro.debug.gdbjtag.ppc_1.9.9.201907200403\win32\gdi\P&E\s32e200_mpc574xc.mac) ...
REM This script is compatible with MPC574xC devices.
REM Clean GPRs to remove residual data after using algorithm
REM Initialize all of the Main SRAM - 512KB
Initializing RAM from $40000000 to $4007FFFF.
Initializing Ram Block 0x40000000-0x4007FFFF.

Reset script (C:\NXP\S32DS_Power_v2.1\eclipse\plugins\com.pemicro.debug.gdbjtag.ppc_1.9.9.201907200403\win32\gdi\P&E\s32e200_mpc574xc.mac) completed.

MPC574xB/C/D Device detected.
Setting PC as part of Binary Load to 0x01000000.
Interrupt command received. Halting execution.

[stanish]

Hi,

Are you able to figure out which line of code is causing application to jump at 0x0000_0010? There is probably an IVOR exception occured during code execution?

Are you able to reach main() function? If not then I'd recommend you to disable run on reset feature and check if startup code is executed correctly:

If the very first instruction causes the IVOR exception please check if MCU Reset Configuration Half Word + reset vector is correct and check ABS/FAB pins so the internel flash boot mode is enabled.

If it does not help could you send us more information e.g.:

The debugger screenshots that depict the error.

Describe the circumstances before the error occurs.

Are you using a custom board or NXP evaluation board?

This will help us to resolve this iisue much faster

Thanks!

Stan