Debug token for Apollo Lake target

Debug token for Apollo Lake target


Hello,

I'm not able to debug our Apollo Lake based target although our platform seems to be connected by System Debugger using CCA and USB3.0 port.
When I connect to our target and then when I press pause button in debugger then I get message "E-2201: Target is unresponsive":

IPC: DCI: Target connection has been fully established
INFO: Target power is now: Off
INFO: Target power is now: On
WARNING: attempting to halt an unresponsive target, this operation may fail…
E-2201: Target is unresponsive

I think that my problem to create debug token.bin by PFT to be able to debug our corebooot bios by CCA, because I need permission for this token.bin creation. Do I have right? Please could you provide this permission to me if this is what I need to be able to debug?

3 posts / 0 new

Hello,

Seems that I did debug token and properly stitched it, but now I see the next log before and after I start "Trace H/W test" in System Studio:

20:13:51 [INFO ] TCA (client) - Connection Manager: Status change: CONNECTING
    Connection: Intel Atom Processors N4200 N3350 x7-E3950 x5-39xx (Apollo Lake)
    Target: Intel Atom Processors N4200, N3350, x7-E3950, x5-39xx (Apollo Lake)
    Connection Method: Intel(R) DCI USB 3.x Debug Class

20:13:51 [INFO ] TCA (server) - IPConnection: Open Connection, configuration: BXTP_Default_TCI.
20:14:03 [INFO ] TCA (client) - Connection Manager: Status change: CONNECTED
    Connection: Intel Atom Processors N4200 N3350 x7-E3950 x5-39xx (Apollo Lake)
    Target: Intel Atom Processors N4200, N3350, x7-E3950, x5-39xx (Apollo Lake)
    Connection Method: Intel(R) DCI USB 3.x Debug Class

20:14:03 [INFO ] TCA (server) - IPCConnection: Found TAPs:

20:14:03 [ERROR] [npk_target_config_api] [ERROR] Error in connecting to the target. Target does not have power.
20:14:03 [WARN ] Intel(R) Trace Hub not detected or is unavailable. Please disconnect and enable the Intel(R) Trace Hub, then re-connect..
20:14:03 [ERROR] [npk_target_config_api] [ERROR] Error in connecting to the target. Target does not have power.
20:14:03 [ERROR] [npk_target_config_api] [ERROR] Error in connecting to the target. Target does not have power.
20:14:03 [INFO ] [npk_config_api] Successfully created target connection.
20:14:03 [ERROR] [npk_target_config_api] [ERROR] Error in connecting to the target. Target does not have power.
20:14:03 [ERROR] [npk_config_api] Failed Intel(R) Trace Hub hardware detection check!
20:14:04 [ERROR] [npk_target_config_api] [ERROR] Error in connecting to the target. Target does not have power.
20:14:24 [INFO ] [npk_target_config_api] [INFO] DCI: Target connection has been fully established
20:14:24 [INFO ] [npk_target_config_api] [INFO] Target debug port (0x11000) state changed UNKNOWN->POWER_On for devices: ALL
20:14:24 [INFO ] [npk_target_config_api] [INFO] Target debug port (0x11000) event RESET: Started
20:14:24 [INFO ] [npk_target_config_api] [INFO] Target debug port (0x11000) event RESET: Completed
20:15:20 [INFO ] [TEST] Starting Trace Hardware Tests
20:15:22 [ERROR] [npk_target_config_api] [ERROR] Error resuming the target. Target might be in an inconsistent state. Please try powering it on and off.
IPC error code: (0x80000003): Unable to perform operation because there are no GPC threads in this domain

20:15:22 [ERROR] [TEST] Could not enter probe mode.
20:15:24 [INFO ] [TEST] Checking to see if patgen is available to run test
20:15:24 [WARN ] [TEST] No available patgen for self-check. Skipping test...
20:15:25 [INFO ] [TEST] Checking Tap2Sideband Access to TraceHub CSR space
20:15:25 [ERROR] [npk_target_config_api] [ERROR] Unable to find alias:TAP2IOSF_TAP0
20:15:25 [ERROR] [npk_target_config_api] [ERROR] Unable to find alias:TAP2IOSF_TAP0
20:15:25 [ERROR] [npk_target_config_api] [ERROR] Unable to find alias:TAP2IOSF_TAP0
20:15:25 [ERROR] [TEST] Error writing & reading 57005 to register SWDEST_0

...

 

When I press pause button in debugger then I still get message "E-2201: Target is unresponsive".

Does anybody has any advice what could be the problem, why the target is always unresponsive although LED on CCA is green and status in System Studio is running?

 

 

 

 


No, "Found TAPs" list is empty. So you have actually no connection to target. You are only connected to CCA adapter.

Did you enabled Debug Interface in BIOS?

Leave a Comment

Please sign in to add a comment. Not a member? Join today