RCW Override, Error: Connect Failed. Failed to correctly configure the JTAG chain(CCSProtocolPlugin) Error: Connect Failed.

cancel
Showing results for 
Search instead for 
Did you mean: 

RCW Override, Error: Connect Failed. Failed to correctly configure the JTAG chain(CCSProtocolPlugin) Error: Connect Failed.

Jump to solution
254 Views
Contributor I

Hello NXP,

Board: T1042 D4 RDB - 64 b

Problem: Unable to execute RCW override script ( <CWInstallDir>\PA\PA_Support\Initialization_Files\jtag_chains ) with NOR flash Target Task.

I want to flash some new U-boot and RCW to my Custom Board for t1042d4 . First, I wanted to try RCW override method on RDB but I am had this error. Asleep led is lit. I changed HEX values of the RCW in script file with the values of a sample RCW generated with YOCTO SDK. I also validated each step in Freescale\CW_PA_v10.5.1\PA\Help\PDF\Targeting_PA_Processors.pdf documentation of Code Warrior.

I am able to write something on flash with default RCW in NOR flash or Hardcoded RCW.

What is the reason behind this error ? 

Thanks.

Labels (1)
0 Kudos
1 Solution
26 Views
NXP TechSupport
NXP TechSupport

Hello Ahmet Demir,

In JTAG configuration file, please modify (210007 0xec02f000) to (210007 0xfc027000).

RCW[PBI_SRC]

Options:
0000 I2C1 normal addressing (up to 256 byte ROMs)
0001 I2C1 extended addressing
0100 SPI 16-bit addressing
0101 SPI 24-bit addressing
0110 SD/MMC
1110 IFC (The RCW field IFC_MODE configures the
IFC, provided the IFC has not already been
configured by the cfg_rcw_src configuration input
signals, which have precedence.)
1111 Disabled
All other encodings are reserved.

Thanks,

Yiping

View solution in original post

0 Kudos
7 Replies
26 Views
NXP TechSupport
NXP TechSupport

Hello Ahmet Demir,

Please check whether your custom RCW is valid on T1042D4RDB, please configure your target board as hardcoded RCW, then program your custom RCW and u-boot on NOR flash to check whether u-boot can boot up successfully.

Would you please capture low level CodeWarrior CCS log to me to do more investigation?

Please create a bareboard project for T1042RDB, then configure JTAG configuration file in CW IDE overriding RCW.

Before connect to the target, please enable CCS log from "Run->Debug Configurations-><project>-core0_RAM_-Attach->Edit...->Advanced->Advanced CCS setting->Enable logging", and connect to the target from "Run->Debug Configurations-><project>-core0_RAM_-Attach->Debug”, the CCS log will be printed in the console panel in CodeWarrior IDE.

Note: Please open the console panel from Window->Show View->Console, and if nothing displayed, please choose the correct session on the right top icon in the panel.If the CCS log in the console is truncated, please enlarge the console buffer from Window->Preferences->Run/Debug->Console->uncheck "Limit console output".

Thanks,

Yiping

0 Kudos
26 Views
Contributor I

Hello yipingwang ,

I believe the RCW I used is correct because I copied the values from working U-boot console logs to JTAG Configuration File. The values are coming from Yocto SDK Generated RCW named 'rcw_1400Mhz.bin' under SDK directory '<SDK_dir>/<t1042_build_dir>/tmp/deploy/images/rcw/t1042d4rdb/RR_P_86/rcw_1400Mhz.bin'.

RCW values from U-boot console ( U-boot is booting with this rcw successfully ):

Reset Configuration Word (RCW):
       00000000: 0c18000e 0e000000 00000000 00000000
       00000010: 86000002 40000002 ec02f000 21000000
       00000020: 00000000 00000000 00000000 00030810
       00000030: 00000000 01fe580f 00000000 00000000

Inside JTAG Config File:

T1042 (2 1) (210001 0x0c18000e) (210002 0x0e000000) (210003 0x00000000) (210004 0x00000000) (210005 0x86000002) (210006 0x40000002) (210007 0xec02f000) (210008 0x21000000) (210009 0x00000000) (210010 0x00000000) (210011 0x00000000) (210012 0x00030810) (210013 0x00000000) (210014 0x01fe580f) (210015 0x00000000) (210016 0x00000000)

I attached full logs and required files.

The debug session is ended with Failed to Configure JTAG Chain error.

0 Kudos
26 Views
NXP TechSupport
NXP TechSupport

Hello Ahmet Demir,

In the CCS log, it failed at ccs_reset_to_debug, there is problem at JTAG reset sequence.

When this RCW deploying on NOR flash, have you tried whether CodeWarrior bareboard project (without JTAG configuration file enabled) can connect to the target board?

Thanks,

Yiping

0 Kudos
26 Views
Contributor I

Hello yipingwang,‌

Without RCW override, Seems I am able to debug the board without any error.

I attached the new configuration(Target Type is only T0142) and JTAG logs.

0 Kudos
27 Views
NXP TechSupport
NXP TechSupport

Hello Ahmet Demir,

In JTAG configuration file, please modify (210007 0xec02f000) to (210007 0xfc027000).

RCW[PBI_SRC]

Options:
0000 I2C1 normal addressing (up to 256 byte ROMs)
0001 I2C1 extended addressing
0100 SPI 16-bit addressing
0101 SPI 24-bit addressing
0110 SD/MMC
1110 IFC (The RCW field IFC_MODE configures the
IFC, provided the IFC has not already been
configured by the cfg_rcw_src configuration input
signals, which have precedence.)
1111 Disabled
All other encodings are reserved.

Thanks,

Yiping

View solution in original post

0 Kudos
26 Views
Contributor I

Hello yipingwang‌,

Connect Failed error is gone now. But there exists another error when I try to execute Target Task. Debugging is working without any error but executing Target Task for burning new U-boot is giving,

Error: The algorithm was not able to run on the target or the flash is not configured properly.
Error: Getting flash ID failed
Error: The algorithm was not able to run on the target or the flash is not configured properly.

I also attached JTAG logs.

Should I post this on another question?

Thanks. 

0 Kudos
26 Views
Contributor I

Many Thanks.

0 Kudos