Does DDR validation work with hardware rcw config?

[frank2li]

I run DDR validation on B4860QDS board and my customize board with hardware rcw config, both failed, below are the logs. And I have adjust DDR rate to 1600MT. I have two question:

1. I want to know if DDR validation must run with NOR rcw config or other correct rcw connfig. If not, how to fix the issue of scan timeout? What meaning is scan timeout?

2. If using normal rcw, uboot hang due to ddr config might not be optimized. Is that impact the test of DDRv?

From QCVS, it reported:

#################### Result for: write_read_compare_test ###### Run 1 #############################

Test was not executed!

Err. capture registers:
0xE20, 0x100000000 0xE24, 0x100000000 0xE28, 0x100000000 0xE40, 0x100000000
0xE44, 0x100000000 0xE48, 0x100000000 0xE4C, 0x100000000 0xE50, 0x100000000
0xE54, 0x100000000 0xE58, 0x100000000

Dump:
0xF00, 0x100000000 0xF04, 0x100000000 0xF08, 0x100000000 0xF0C, 0x100000000
0xF10, 0x100000000 0xF14, 0x100000000 0xF18, 0x100000000 0xF1C, 0x100000000
0xF20, 0x100000000 0xF24, 0x100000000 0xF28, 0x100000000 0xF2C, 0x100000000
0xF30, 0x100000000 0xF34, 0x100000000 0xF38, 0x100000000 0xF3C, 0x100000000
0xF40, 0x100000000 0xF44, 0x100000000 0xF48, 0x100000000 0xF4C, 0x100000000
0xF50, 0x100000000 0xF54, 0x100000000 0xF58, 0x100000000 0xF5C, 0x100000000
0xF60, 0x100000000 0xF64, 0x100000000 0xF68, 0x100000000 0xF6C, 0x100000000
0xF70, 0x100000000 0xF74, 0x100000000 0xF78, 0x100000000 0xF7C, 0x100000000
0xF80, 0x100000000 0xF84, 0x100000000 0xF88, 0x100000000 0xF8C, 0x100000000
0xF90, 0x100000000 0xF94, 0x100000000 0xF98, 0x100000000 0xF9C, 0x100000000
0xFA0, 0x100000000 0xFA4, 0x100000000 0xFA8, 0x100000000 0xFAC, 0x100000000
0xFB0, 0x100000000 0xFB4, 0x100000000 0xFB8, 0x100000000 0xFBC, 0x100000000
0xFC0, 0x100000000 0xFC4, 0x100000000 0xFC8, 0x100000000 0xFCC, 0x100000000
0xFD0, 0x100000000 0xFD4, 0x100000000 0xFD8, 0x100000000 0xFDC, 0x100000000
0xFE0, 0x100000000 0xFE4, 0x100000000 0xFE8, 0x100000000 0xFEC, 0x100000000
0xFF0, 0x100000000 0xFF4, 0x100000000 0xFF8, 0x100000000 0xFFC, 0x100000000

Data:
0x00000000

--------------------------------------------------------------------
Exception: (<<Error configuring the target! - 2147500037 (Scan timeout)>>)
--------------------------------------------------------------------
Target system was initialized 0 times and it took 0.000000 seconds.
Target system effective test execution took 0.000000 seconds.

From the CCS, it outputs below:

CCSAPI connection #1 accepted from Lee-E7450 at Tue Nov 21 11:59:21 2017
check_min_version(serverh=0,*version)
api version: 00000004 00000006
available_connections(serverh=0,*count,*cc)
connections: {0,73,0xa9fea8a3}
cc_version(serverh=0,cc_index=0,index=0,*version)
config_chain(serverh=0,cc=0,count=1,*devlist,*generic)
devlist: t4amp
available_connections(serverh=0,*count,*cc)
connections: {0,73,0xa9fea8a3}
get_config_chain(serverh=0,cc=0)
*** unhandled(command=163) ***
config_template(coreh.{serverh=0,cc_index=0,chain_pos=0},config_reg=0,config_data=0x000007D0)
write_memory(coreh.{serverh=0,cc_index=0,chain_pos=0},
addr.{addr_hi=0x00030000,addr_lo=0x00000C00,size=4,space=0},count=4,*data)
data: 00000000
write_memory(coreh.{serverh=0,cc_index=0,chain_pos=0},
addr.{addr_hi=0x00030000,addr_lo=0x00000C04,size=4,space=0},count=4,*data)
data: 80000000
write_memory(coreh.{serverh=0,cc_index=0,chain_pos=0},
addr.{addr_hi=0x00030000,addr_lo=0x00000C08,size=4,space=0},count=4,*data)
data: 81000013
write_memory(coreh.{serverh=0,cc_index=0,chain_pos=0},
addr.{addr_hi=0x00030000,addr_lo=0x00000C10,size=4,space=0},count=4,*data)
data: 00000000
write_memory(coreh.{serverh=0,cc_index=0,chain_pos=0},
addr.{addr_hi=0x00030000,addr_lo=0x00000C14,size=4,space=0},count=4,*data)
data: 00000000
write_memory(coreh.{serverh=0,cc_index=0,chain_pos=0},
addr.{addr_hi=0x00030000,addr_lo=0x00000C18,size=4,space=0},count=4,*data)
data: 8100001E
read_memory(coreh.{serverh=0,cc_index=0,chain_pos=0},
addr.{addr_hi=0x00000000,addr_lo=0xFFDF00C2,size=1,space=0},count=4,*data)
data: 00 00 00 00
ERROR(47): Scan timeout
read_memory(coreh.{serverh=0,cc_index=0,chain_pos=0},
addr.{addr_hi=0x00030000,addr_lo=0x00008E20,size=1,space=0},count=4,*data)
data: 00 00 00 00
ERROR(47): Scan timeout
read_memory(coreh.{serverh=0,cc_index=0,chain_pos=0},
addr.{addr_hi=0x00030000,addr_lo=0x00008F00,size=1,space=0},count=4,*data)
data: 00 00 00 00
ERROR(47): Scan timeout

[ufedor]

> 1. I want to know if DDR validation must run with NOR rcw config or other correct rcw connfig.

It is recommended tat valid RCW from NOR Flash has to be provided for the normal DDRV Tool operation.

> 2. If using normal rcw, uboot hang due to ddr config might not be optimized. Is that impact the test of DDRv?

No.

Have you performed an initial board bring-up?

What are RESET_REQ_B and ASLEEP signals levels during POR sequence?

[frank2li]

Hi Ufedor

Thanks you very much!

We do not process RESET_REQ_B request now. And I measured the ASLEEP signal, after PORESET signal poll up, ASLEEP takes about 400ms to pull down. From the power on sequence of B4860 RM, I think it might be normal. The reason are my board is using spi flash bootup, PBL needs to take more time to read SPL, comparing of Nor flash bootup; is that guess correct? 

Now I'm using the rcw of spi boot, and the uboot can boot to the shell. But the target connection of DDR validation failed, it reports "Target is not ready: 214750037 (B4860: invalid parameter)", sometimes it reports timeout. I think it might relate to the more time of POR.  How can i change the qvcs option to resolve the problem?

The below is the log:

CCSAPI connection #1 accepted from Lee-E7450 at Wed Nov 22 21:09:57 2017
check_min_version(serverh=0,*version)
api version: 00000004 00000006
available_connections(serverh=0,*count,*cc)
connections: {0,73,0xa9fe923b}
cc_version(serverh=0,cc_index=0,index=0,*version)
config_chain(serverh=0,cc=0,count=1,*devlist,*generic)
devlist: t4amp
ERROR(39): Subcore error encountered during multicore operation
config_chain(serverh=0,cc=0,count=1,*devlist,*generic)
devlist: testcore
reset_to_debug(serverh=0,cc=0)
config_chain(serverh=0,cc=0,count=1,*devlist,*generic)
devlist: t4amp
ERROR(39): Subcore error encountered during multicore operation
config_chain(serverh=0,cc=0,count=1,*devlist,*generic)
devlist: t4amp
ERROR(39): Subcore error encountered during multicore operation
config_chain(serverh=0,cc=0,count=1,*devlist,*generic)
devlist: t4amp
ERROR(39): Subcore error encountered during multicore operation
config_chain(serverh=0,cc=0,count=1,*devlist,*generic)
devlist: t4amp
ERROR(39): Subcore error encountered during multicore operation
parse_error_ext(coreh.{serverh=0,cc_index=0,chain_pos=0}, 39)
error: B4860: Invalid parameter
CCSAPI connection #1 from Lee-E7450 closed at Wed Nov 22 21:10:00 2017
CCSAPI connection #1 accepted from Lee-E7450 at Wed Nov 22 21:11:57 2017
check_min_version(serverh=0,*version)
api version: 00000004 00000006
available_connections(serverh=0,*count,*cc)
connections: {0,73,0xa9fe923b}
cc_version(serverh=0,cc_index=0,index=0,*version)
config_chain(serverh=0,cc=0,count=1,*devlist,*generic)
devlist: t4amp
available_connections(serverh=0,*count,*cc)
connections: {0,73,0xa9fe923b}
get_config_chain(serverh=0,cc=0)
*** unhandled(command=163) ***
config_template(coreh.{serverh=0,cc_index=0,chain_pos=0},config_reg=0,config_data=0x000007D0)
CCSAPI connection #2 accepted from Lee-E7450 at Wed Nov 22 21:12:04 2017
check_min_version(serverh=1,*version)
api version: 00000004 00000006
available_connections(serverh=1,*count,*cc)
connections: {0,73,0xa9fe923b}
cc_version(serverh=1,cc_index=0,index=0,*version)
config_chain(serverh=1,cc=0,count=1,*devlist,*generic)
devlist: t4amp
available_connections(serverh=1,*count,*cc)
connections: {0,73,0xa9fe923b}
get_config_chain(serverh=1,cc=0)
*** unhandled(command=163) ***
config_template(coreh.{serverh=0,cc_index=0,chain_pos=0},config_reg=0,config_data=0x000007D0)

[ufedor]

It will be more convenient to investigate the issue as a Technical Case:

https://community.freescale.com/thread/381898

[frank2li]

Just created one tc. Thank you very much!