Fail to connect T1023 custom board using CW TAP

cancel
Showing results for 
Search instead for 
Did you mean: 

Fail to connect T1023 custom board using CW TAP

849 Views
abineshselvaraj
Contributor III

We are using a custom board which is based on T1023-RDB design with some memory configuration changes. The system is booting u-boot from SPI NOR (S25FL256S - 32MB). I want to flash the u-boot bin in the NOR flash.

I'm using the following tools,

CodeWarrior IDE for Power architecture v10.5.1 windows

CodeWarrior  TAP (Over USB)

Probe Tip for Power-Architecture CodeWarrior (CWH-CTP-COP-YE)

I have created a code-warrior executable project and imported the existing flash programmer XML file of T1023RDB-SPI-FLASH (64MB).The flash programmer task has been updated with program/verify action (flash offset as 0). When the project is executed, following error message is shown,

"FAILED TO CONFIGURE JTAG CHAINS". On enabling the JTAG diagnostics, following message is shown in console,

"ERROR MEASURING IR SCAN LENGTH".

Kindly suggest the reason and possible solution for this issue,

Thanks & Regards,

S.Abinesh.

0 Kudos
21 Replies

410 Views
addiyi
NXP Employee
NXP Employee

Seems to be a jtag issue. Please run in ccs console the followings commands and provide the output:

(bin) 50 % source IDcode.tcl

(bin) 51 % delete all
(bin) 52 % config cc cwtap
(bin) 53 % ccs::config_chain testcore
(bin) 54 % jtag::lock
(bin) 55 % jtag::reset_tap 1
(bin) 56 % jtag::reset_tap 1
(bin) 56 % jtag::scan_io dr 64 0x55AA55AA55AA55AA
0x55AA55AA5BA00477
(bin) 57 % jtag::scan_io ir 64 0x0000000000000000
0x0000000000000001
(bin) 58 % jtag::unlock

Adrian

0 Kudos

410 Views
abineshselvaraj
Contributor III

Hi Adrian,

Sorry for the late reply. With 64bit OS, the TAP MAC-Address is read properly. Please find the ccs log for  JTAG scan test,

(bin) 2 % findcc cwtaps
FSL042B83 (00:04:9f:04:2b:83): CodeWarrior TAP (3.3V)
Power Architecture JTAG/COP Probe Tip
Boot Loader v1.0.1
Operating System v1.0.4
(bin) 2 % source IDcode.tcl

Scanning for available TAPs connected via USB.....


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+ Available Remote Connections
+
+ 1 - CodeWarriorTAP - 00:04:9f:04:2b:83
+ 2 - CodeWarriorTAP - <Specify IP Address>
+ 3 - EthernetTAP - <Specify IP Address>
+ 4 - GigabitTAP - <Specify IP Address>
+
+ x - Exit Script without Changes
+
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Specify connection:
1

Configuring TAP Interface....

Configured Connection: cwtap : 00:04:9f:04:2b:83


TDO -----
|
|
TDI -----


###################################################
#
# configTAP - Redefine TAP interface
#
# scanboard - Scans the target system
# and returns the JTAG IDCode
#
# ir - Loopback test
#
###################################################

(bin) 3 % delete all
(bin) 4 % config cc cwtap
(bin) 5 % ccs::config_chain testcore
(bin) 6 % jtag::lock
(bin) 7 % jtag::reset_tap 1
(bin) 8 % jtag::reset_tap 1
(bin) 8 % tag::scan_io dr 64 0x55AA55AA55AA55AA
0x55AA55AA5BA00477
invalid command name "tag::scan_io"
(bin) 9 % 0x55AA55AA5BA00477

invalid command name "0x55AA55AA5BA00477"
(bin) 10 %
(bin) 10 % jtag::scan_io dr 64 0x55AA55AA55AA55AA 0x55AA55AA5BA00477
0x0000000000000000
(bin) 11 % jtag::scan_io ir 64 0x0000000000000000 0x0000000000000001
0x0000000000000009

Please provide your suggestions.

Thanks,

S.Abinesh.

0 Kudos

410 Views
addiyi
NXP Employee
NXP Employee

As I suspected, there is a problem with your jtag interface. Please check jtag interface. You can take a look on the RDB board or any other nxp board, to see the implementation.

Adrian

0 Kudos

410 Views
abineshselvaraj
Contributor III

I will check and update you on this.

Thanks,

S.Abinesh.

0 Kudos

410 Views
addiyi
NXP Employee
NXP Employee

When jtag works fine and running IDcode.tcl, you should see the IDCODE of the SoC, something like below

TDO -----
|
* Device 0 IDCODE: 5BA00477 Device: ARM DAP rev 5.x
(TAP Linked with Device: NXP LS2085A rev 1.x IDCODE: 0A01E01D)
|
TDI -----

Adrian

0 Kudos

410 Views
abineshselvaraj
Contributor III

I didn't see the device-ID of T1023 SoC, when the IDcode.tcl is running. But I'm sure that, the JTAG interface is correct. I have verified this with our HW Team. Is there any specific initialization files to be loaded in the T1023 board from CCS IDE for JTAG connection?

Thanks,

S.Abinesh.

0 Kudos

410 Views
addiyi
NXP Employee
NXP Employee

IDcode.tcl it is basic jtag test that is trying to read SoC IDcode. If the IDcode is not returned means the jtag is not working fine. Also, using jtag scan io command from ccs, wil test the jtag. Same on this, the returned values are not correct.

Adrian

0 Kudos

410 Views
abineshselvaraj
Contributor III

The JTAG that we are using now is a new one. Did you mean that, there is a internal problem in JTAG hardware or there is an issue in  probe-tip from JTAG to T1023 board.

Thanks,

S.Abinesh.

0 Kudos

410 Views
addiyi
NXP Employee
NXP Employee

I refer only to jtag interface on the board. Once IDcode will be displayed by ccs, you will be able to use CodeWarrior.

Adrian 

0 Kudos

410 Views
abineshselvaraj
Contributor III

Hi Adrian,

When the IDcode.tcl is sourced, I'm getting an error "No TAPs found connected through USB". Also, in the "findcc cwtaps" command, the jtag firmware version is not getting displayed. But, in the device manager, under ports -> codewarrior console port is visible. The green led in TAP is blinking.

(bin) 17 % source IDcode.tcl

Scanning for available TAPs connected via USB.....

No TAPs found connected via USB

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+ Available Remote Connections
+
+ 1 - CodeWarriorTAP - <Specify IP Address>
+ 2 - EthernetTAP - <Specify IP Address>
+ 3 - GigabitTAP - <Specify IP Address>
+
+ x - Exit Script without Changes
+
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Specify connection:

can't read "CONNECTION()": no such element in array
(bin) 18 % delete all
(bin) 19 % config cc cwtap
(bin) 20 % ccs::config_chain testcore
CC config string is invalid
(bin) 21 % jtag::lock
CC config string is invalid
(bin) 22 % findcc cwtaps
(bin) 23 %
(bin) 23 % findcc cwtaps

Thanks,

S.Abinesh.

0 Kudos

410 Views
addiyi
NXP Employee
NXP Employee

Do you use CodeWarrior Tap or the old USTAP? Try in ccs console findcc utaps as well, to see if you get some output.

Adrian

0 Kudos

410 Views
abineshselvaraj
Contributor III

I'm using Codewarrior TAP (has both USB and Ethernet interface). The console is not displaying anything with "findcc utaps" also.

Thanks,

S.Abinesh.

0 Kudos

410 Views
addiyi
NXP Employee
NXP Employee

Check in device manager to have Freescale Probes > CodeWarrior TAP visible. If, this is not visible try to reinstall the driver running as admin setup.bat from \PA\ccs\drivers\usb\

Adrian

0 Kudos

410 Views
abineshselvaraj
Contributor III

The device manager has the Freescale Probes > Codewarrior TAP visible.

Thanks,

S.Abinesh.

0 Kudos

410 Views
addiyi
NXP Employee
NXP Employee

This is strange. Try using the ip address when configure the connection: config cc cwtap:<ip_addr> or when runnig IDcode.tcl select the first option 1, then specify the ip.

Adrian

0 Kudos

410 Views
abineshselvaraj
Contributor III

Hi Adrian,

Currently, I'm using PC with Win7-32bit OS, CCSv10.5 installed. When I try to read JTAG firmware version from CCSv10.2 exe in Win7-64bit PC, the mac-address and bootloader version of JTAG is displayed.

Thanks,

S.Abinesh.

0 Kudos

410 Views
addiyi
NXP Employee
NXP Employee

Please provide a verbose ccs log (enter in ccs console: log v) when you are trying to connect to board.

Adrian

0 Kudos

410 Views
abineshselvaraj
Contributor III

Thanks for the reply. I will provide  the ccs log by tomorrow early.

0 Kudos

410 Views
abineshselvaraj
Contributor III

Hi,

Please find the ccs log below,

fl::target -lc "t1023_Debug_T1023_Download"
fl::target -b 0x0 0x40000
fl::target -v on -l off
cmdwin::fl::device -d "S25FL512S" -o "65536Kx8x1" -a 0x0 0x3ffffff
cmdwin::fl::image -f "D:\\ganesh\\u-boot-with-spl-pbl.bin" -t "Auto Detect" -re off -oe on -o 0x0
cmdwin::fl::erase image
Beginning Operation ...
-------------------------
Auto-detection is successful.
File is of type Binary/Raw Format.

Performing target initialization ...
Error: Connect Failed.
Failed to correctly configure the JTAG chain(CCSProtocolPlugin)
Error: Connect Failed.

Thanks,

S.Abinesh.

0 Kudos

410 Views
addiyi
NXP Employee
NXP Employee

To get the ccs log, you have to open ccs console (ccs.exe) from \PA\ccs\bin\ and in console enter "log v" command. then try to connect to the board.

One question: your board is booting correctly the uboot from spi?

Adrian

0 Kudos