SAC57D54H with QFP package always on Reset after flash

[johnkevintoral]

Hi Support, 

I have made custom board with SAC57D54H(208 pin QFP package) using JTAG debugging protocol with IDE S32DS. The board is in accordance with all docs so it should behave just fine. However, upon loading program, the board is always on reset. 

I have been using its evaluation board 'MAC57D54MB' but with the 516 BGA package, so i hope the debugging should be the same. I was wondering it is in the software part that is wrong, there might be some codes that I have to modify to suit with the package but I am not sure where it is. 

I would appreciate someone to share a working code with the 208 package. Below is the console error for comment. thank you.

Starting reset script (C:\NXP\S32DS_ARM_v2.2\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_4.4.6.201912192052\win32\gdi\P&E\supportFiles_ARM\NXP\MAC57D5xx\MAC57D54H.mac) ...
REM Initialize 32KB IOP SRAM
REM Mode Entry Change to DRUN
REM SRAM initialization through DMA
REM Turn on read/write access for all masters
Delaying for 2000mS ...
Done.
REM Some useful multi-core hints:
REM The following may be prepended to any command:
REM "M4" - Selects the primary Cortex-M4 core before executing command
REM "A5" - Selects the Cortex-A5 core before executing command
REM "M0" - Selects the Cortex-M0+ core before executing command

Reset script (C:\NXP\S32DS_ARM_v2.2\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_4.4.6.201912192052\win32\gdi\P&E\supportFiles_ARM\NXP\MAC57D5xx\MAC57D54H.mac) completed.

Warning - Debug module not powering up. Try extending power up delay.
UsageFault: A divide by zero error has occurred.
UsageFault: An unaligned access error has occurred.
UsageFault: A coprocessor access error has occurred. The coprocessor is disabled or not present.
UsageFault: An integrity check error has occurred on EXC_RETURN.
UsageFault: An instruction executed with an invalid EPSR.T or EPSR.IT field.
UsageFault: The processor has attempted to execute an undefined instruction.
BusFault: A bus fault has occurred on exception entry.
BusFault: A bus fault has occurred on exception return.
BusFault: An imprecise (asynchronous) data access error has occurred.
BusFault: A precise (synchronous) data access error has occurred.
Possible BusFault location: 0xFFFFDEFF.
MemManage: Fault occurred during floating-point lazy state preservation.
MemManage: Stacking for an exception entry has caused one or more access violations.
MemManage: Unstacking for an exception return has caused one or more access violations.
MemManage: The processor attempted a load or store at a location that does not permit the operation.
MemManage: The processor attempted an instruction fetch from a location that does not permit execution.
Possible MemManage fault location: 0xFFFFDEFF.
HardFault: A fault has been escalated to a hard fault.
HardFault: A BusFault has occurred on a vector table read during exception processing.
Warning - Debug module not powering up. Try extending power up delay.
Disconnected from "127.0.0.1" via 127.0.0.1. Disconnection by port "49508" from 6224
Disconnected from "127.0.0.1" via 127.0.0.1. Disconnection by port "49509" from 7224
Target Disconnected.

MemManage: The processor attempted an instruction fetch from a location that does not permit execution.

[Zhiming_Liu]

Hi @johnkevintoral 

Please create case in S32 group.

Best Regards

Zhiming