QCVS DDR Validation Connection Refused

[rodneymclendon]

I'm trying to run a validation on the DDR controllers, however the connection is always refused regardless of the JTAG clock speed chosen.  The CW is v10.5.1, and QCVS is v4.5.  The connection setup is as follows:

The log from the ccs server is:

(bin) 2 %
CCSAPI connection #1 accepted from vmware-localhost at Tue Nov 01 16:22:50 2016
check_min_version(serverh=0,*version)
  api version: 00000004 00000006
available_connections(serverh=0,*count,*cc)
  connections: {0,73,0x0a0f9209}
cc_version(serverh=0,cc_index=0,index=0,*version)
  ERROR(10): Connection refused
get_remote_user(serverh=0,cc_index=0,*remote_user_hostname,count)
  user:ASH-5WLWZ12.INT.CW.LOCAL
CCSAPI connection #1 from vmware-localhost closed at Tue Nov 01 16:22:55 2016
(bin) 2 %

Rodney

[rodneymclendon]

Those files are in place:

[rodneymclendon]

Here it is:

[addiyi]

The workaround provided is not applied. Please recheck the file and reset CW before retesting.

Adrian

[rodneymclendon]

Still no connection from QCVS.  Here's the output from CCS:

[addiyi]

Please provide a ccs verbose log (enter 'log v' command in ccs console) when QCVS is trying to connect to the board.

Adrian

[rodneymclendon]

No, this is the T4240QDS.  In order to get the bareboard example projects to connect, I had to change the TAP reset delay to 2 secs.

[addiyi]

Replace connect.py from \eclipse\Optimization\resources\QorIQ\common\templates\init\ with the one attached.

Replace main_ppc_core.py and main_ppc_non_core.py from \eclipse\Optimization\resources\QorIQ\DDR\templates\init\ with attached files.

After replacement restart CW.

I recommend you to save the original files :smileyhappy:

Adrian

[rodneymclendon]

Here you go:

[addiyi]

Ok, so something is happened with your board. You get an error when ccs/qcvs is tryind to reset the board. This is a custom board?

Adrian

[rodneymclendon]

After restarting CW, this is what I'm getting from CCS:

Only after I reboot the probe does the 'show cc' show the TAP.  However, the connection still fails.

[addiyi]

Try in ccs:

delete all

config cc cwtap:10.15.146.9

ccs::config_chain t4240

ccs::reset_to_debug

ccs::all_run_mode

Provide the output.

Adrian

[rodneymclendon]

Well, this brings us back to my original problem, the QCVS is not connecting to/thru the CCS.

[rodneymclendon]

I don't understand your suggestion, skype this error and try again.

[addiyi]

Because config cc is working from ccs, should works from QCVS as well. 

Adrian

[rodneymclendon]

I don't think the network timeout is issue anymore, after performing a ping in a DOS shell, 'show cc' no longer times out.  The problem now is that 'findcc cwtaps -eth' still returns nothing.

[addiyi]

Yes, this is a know issue. You can skip this error and try again from QCVS to connect to target.

Adrian

[rodneymclendon]

After performing ping, the CCS 'show cc' shows cwtap but the 'findcc cwtaps' is still empty:

[rodneymclendon]

Also:

[rodneymclendon]

Here is what I get for the CCS (and yes I have a valid license in place):

[addiyi]

Try setting a bigger value for networktimeout using in ccs console:

config networktimeout <value_in sec>

Adrian