Problem about JLink debug on S32K144

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problem about JLink debug on S32K144

2,247 Views
jimfung
Contributor III

When i debug the code below, then my JLink can no longer to connect with the mcu.

1. code

        /* Reprogram secure byte in Flash configuration field */
#if (FSL_FEATURE_FLS_HAS_PROGRAM_PHRASE_CMD == 1u)
        address = 0x408u;
        size = FTFx_PHRASE_SIZE;
#else   /* FSL_FEATURE_FLASH_HAS_PROGRAM_LONGWORD_CMD == 1u */
        address = 0x40Cu;
        size = FTFx_LONGWORD_SIZE;
#endif /* FSL_FEATURE_FLS_HAS_PROGRAM_PHRASE_CMD */
        ret = FlashProgram(&flashSSDConfig, address, size, unsecure_key, pCmdSequence);
        if (ret != FTFx_OK)
        {
            return ret;
        }

2. error log

SEGGER J-Link GDB Server V6.10i Command Line Version

JLinkARM.dll V6.10i (DLL compiled Oct 25 2016 19:31:51)

-----GDB Server start settings-----
GDBInit file:                  none
GDB Server Listening port:     2331
SWO raw output listening port: 2332
Terminal I/O port:             2333
Accept remote connection:      localhost only
Generate logfile:              off
Verify download:               on
Init regs on start:            on
Silent mode:                   off
Single run mode:               on
Target connection timeout:     0 ms
------J-Link related settings------
J-Link Host interface:         USB
J-Link script:                 none
J-Link settings file:          none
------Target related settings------
Target device:                 S32K144
Target interface:              SWD
Target interface speed:        1000kHz
Target endian:                 little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link OpenSDA 2 compiled Apr 24 2014 14:44:11
Hardware: V1.00
S/N: 621000000
Checking target voltage...
Target voltage: 3.30 V
Listening on TCP/IP port 2331
Connecting to target...ERROR: Kinetis (connect): Timeout while unsecuring device. Erase never starts.
Kinetis (connect): Failed to unsecure Kinetis device.
Communication timed out: Requested 4 bytes, received 0 bytes !

ERROR: Could not connect to target.
Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
Shutting down...
Could not connect to target.
Please check power, connection and settings.

0 Kudos
2 Replies

1,407 Views
lohrsistemas
Contributor IV

What is the version of your microcontroller?
I am using PS32K144UFVLL0N47 and I have a similar problem. Checking the reset pin, even with external pull up, I found a voltage of 1,250V. I'm waiting for the NXP team to give me some information.

0 Kudos

1,407 Views
jimfung
Contributor III

My version is PS32K144HFVLLON77P, but the voltage of reset pin was 3.3V.

0 Kudos