Hello,
I try to launch a debug session for a MSC8156AMC board but I always have the same error message (CCS Protocol : Configure chain error).
So I looked at the MSC8156AMC.cfg for the usb Tap JTAG but it looks fine.
I don't understand why it doesn't work, could you help me ?
I work with CW 10.1.8 and the USB TAP for MSC8156AMC.
Ragards
Jimmy
Solved! Go to Solution.
Hi,
To fix the problem I remeber that there is 2 modes to get the reset words configuration : by the I2C EEPROM or by hard coded option. (switch 2.8 on the board)
When I put the switch 2.8 off (hard coded RWC) it works, so the problem must comming from the I2C EEPROM.
It seems to be the same that I had, the reset words configuration was erase on the EEPROM.
To solve this problem I put the switch 2.8 off and then burned the EEPROM with the data that I put into my previous post.
Then you can put the siwtch 2.8 on it must be ok.
Regards
Jimmy
This is the ccs protocol log that I have :
ccs_open ipaddr = 127.0.0.1 port = 41475 timeout = 60 serverh = 0 ccs_open; ccs_error = 10 Error message: Connection refusedccs_open ipaddr = 127.0.0.1 port = 41475 timeout = 60 serverh = 0 ccs_open; ccs_error = 0ccs_get_connection_count serverh = 0 count = 1 ccs_get_connection_count; ccs_error = 0ccs_available_connections serverh = 0 count = 0 ccs_available_connections; ccs_error = 0ccs_available_connections serverh = 0 count = 0 ccs_available_connections; ccs_error = 0ccs_config_cc serverh = 0 config_string = utap:0 ccs_config_cc; ccs_error = 0ccs_available_connections serverh = 0 count = 1 ccs_available_connections; ccs_error = 0ccs_available_connections serverh = 0 count = 1 ccs_available_connections; ccs_error = 0ccs_cc_version serverh = 0 cc = 0 version.major = 1 version.minor = 3 ccs_cc_version; ccs_error = 0ccs_set_timeout serverh = 0 timeout = 60 ccs_set_timeout; ccs_error = 0ccs_available_connections serverh = 0 count = 1 ccs_available_connections; ccs_error = 0ccs_available_connections serverh = 0 count = 1 ccs_available_connections; ccs_error = 0ccs_available_connections serverh = 0 count = 1 ccs_available_connections; ccs_error = 0ccs_available_connections serverh = 0 count = 1 ccs_available_connections; ccs_error = 0ccs_set_timeout serverh = 0 timeout = 60 ccs_set_timeout; ccs_error = 0ccs_get_config_chain serverh = 0 device_list: (size = 0) ccs_get_config_chain; ccs_error = 0ccs_config_server serverh = 0 cc = 0 server_config = 0 value = 12500 ccs_config_server; ccs_error = 0ccs_config_chain serverh = 0 cc = 0 device_list: (size = 3) device[0]:: core_type=MSC8156(122) device[1]:: core_type=MSC8156(122) device[2]:: core_type=MSC8156(122) ccs_config_chain; ccs_error = 59 Error message: Auto chain configuration not successfulccs_reset_to_debug serverh = 0 cc = 0 ccs_reset_to_debug; ccs_error = 0ccs_config_chain serverh = 0 cc = 0 device_list: (size = 3) device[0]:: core_type=MSC8156(122) device[1]:: core_type=MSC8156(122) device[2]:: core_type=MSC8156(122) ccs_config_chain; ccs_error = 59 Error message: Auto chain configuration not successfulccs_kill_server serverh = 0 ccs_kill_server; ccs_error = 0
My chain configuration looks like ok, so I don't understand why there is an error.
Finally I found problem came that the I2C EEPROM has been erase (address 0X50) so the CCS couldn't find th.e Reset Configuration Words.
I burned the EEPROM with this configuration and now it works.
/* Reset configuration words *//* Preamble */ 0xAA, 0x55, 0xAA,/* Master Reset Configuration Word Low */ 0xFF, 0xFF, 0xFF, 0x43, 0x33, 0x00, 0x00,/* Master Reset Configuration Word High */ 0xFF, 0xFF, 0xFF, 0x00, 0x84, 0x18, 0x01,/* Number of reset slaves */ 0x02,/* Slave Reset Configuration Words */ 0x43, 0x33, 0x00, 0x00, 0x00, 0x80, 0x18, 0x09, 0x43, 0x33, 0x00, 0x00, 0x00, 0x80, 0x18, 0x11, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
Hi Jim ,
I am also facing similar problem in MSC8156AMC board , while i am lunching the code its showing unknown protocol ,
i checked in ccs server command " sh cc" which shows usb tab correctly working .
This issue comming on new 8156AMC board , could you tell me the debug steps you have followed while fixing this issue ?
How to know I2C EEPROM has been erase (address 0X50) ?
Thanks,
Sunil.
Hi,
To fix the problem I remeber that there is 2 modes to get the reset words configuration : by the I2C EEPROM or by hard coded option. (switch 2.8 on the board)
When I put the switch 2.8 off (hard coded RWC) it works, so the problem must comming from the I2C EEPROM.
It seems to be the same that I had, the reset words configuration was erase on the EEPROM.
To solve this problem I put the switch 2.8 off and then burned the EEPROM with the data that I put into my previous post.
Then you can put the siwtch 2.8 on it must be ok.
Regards
Jimmy