topic After clicking "Flash programmer" icon, CodeWarrRe: Code warrior Jtag IDE connection diagnosis issue in Layerscape

Code warrior Jtag IDE connection diagnosis issue

SWETHA1 — Tue, 12 May 2026 06:04:14 GMT

Hi Team,

We are using a custom board based on the NXP LX2160A chipset and are currently trying to set up the CodeWarrior IDE environment for JTAG flashing.

The flash device used on our board is MT25QU512ABB. After configuring the IDE environment and adding the required files, we proceeded to open the Flash Programmer.

During the connection process, after "Connection Diagnosis", the Flash Programmer opens successfully, but we are facing an issue at the step: "Run Target Initialisation Script" . The error observed is attached in the screenshot.

The DIP switch is set to Hard-Coded RCW mode where we encounter the following error:
"Failed to write memory at address ..."

We have already verified the following:

* Hardware connections
* JTAG connectivity is proper
* Relevant signals were probed and appear normal

We request your support in helping us isolate the root cause and fix the issue at the earliest. Please let us know if any additional logs or configuration files are required.

Thanks & Regards,
Swetha K

Re: Code warrior Jtag IDE connection diagnosis issue

SWETHA1 — Tue, 12 May 2026 06:05:33 GMT

Please find the screenshot attached :

After clicking "Flash programmer" icon, CodeWarrRe: Code warrior Jtag IDE connection diagnosis issue

yipingwang — Tue, 12 May 2026 06:22:07 GMT

1. First Please double click LX2160_RDB(1) to Open "Target Initialization File" panel, please do the following modification.

USE_SAFE_RCW = True

2. After clicking "Flash programmer" icon, CodeWarrior Connection Server(CCS) will pop up in the Windows task bar, please double click it to open CCS console, and type "log v" in the console, then click "Flash programmer" icon again, the low level CCS log will be printed in the console. Please capture this log and send it to me.

Re: Code warrior Jtag IDE connection diagnosis issue

SWETHA1 — Mon, 18 May 2026 09:34:55 GMT

Hi
The issue has been resolved. It was caused by a hardware connection fault, which has now been fixed. We are no longer experiencing the error. Thank you for your support