Part Number: AWR1642
Tool/software: Code Composer Studio
Hi CCS Team,
I'm working with a customer of mine, who recently updated their XDS110 drivers. This update changed their COM port numbers, and we are now having issues running software on their AWR1642 EVMs. Prior to this everything was running without issue. I have checked their target configuration against mine(working), and everything matches, but they are getting the below errors when trying to connect to the EVM after a full system reset.
C674X_0: GEL: Error while executing OnPreTargetConnect(): Target failed to read 0x500006CC@System_View
at gempwrsmcfg4_rd=*((unsigned int *) (0x50000400U+0x000002CCU)) [xwr16xx_dss_csdap.gel:152]
at DSS_PreConnect_CheckResetStatus()
at GEL_EvalOnTarget("CS_DAP_0", "DSS_PreConnect_CheckResetStatus()", 1) [xwr16xx_dss_init.gel:11]
at OnPreTargetConnect()
C674X_0: Error connecting to the target: (Error -275 @ 0x0) The attempt to poll a target device exceeded its timeout limit. The utility or debugger has requested that a target device be repeatedly accessed for a specific data or status value. This has failed because the built-in limit for the maximum number of attempts when polling the JTAG scan-path has been exceeded. (Emulation package 8.0.27.9)
C674X_0: Error connecting to the target: (Error -1146 @ 0x0) Data scanned out of device is corrupt and not valid. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.0.27.9)
Cortex_R4_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.0.27.9)
Cortex_R4_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.0.27.9)
Originally we were also seeing error -615 @ 0x0.
Please let me know your thoughts on what may be causing this!
Thanks,
Barend