Intel® System Studio
Ask questions and share information with other users of the Intel® System Studio.
Announcements
Intel® System Studio components are now transitioned to several Intel® oneAPI toolkits and can be found under Intel oneAPI Base Toolkit and Intel oneAPI IoT Toolkit. Use the respective forums for questions related to these components. Getting Started questions can be asked in the Registration, Download, Licensing and Installation forum. If you have Priority Support you can submit your question in the Online Service Center.
348 Discussions

DCI Connection Problems

Miles__Craig
Beginner
‎03-26-2018 02:16 PM
3,518 Views
Hello all,
 
I'm trying to use Intel System Studio / Intel System Debugger to JTAG debug a NUC system over DCI. I have tried two different connection types, DCI USB 3.x Debug Class and the Intel(R) DCI OOB, but neither allows System Studio to successfully connect to the target.
 
Here is my setup:
Host: Intel NUC615SYK with Windows 10 and Intel System Studio (Installer: system_studio_2018.040_windows_target_online.exe)
Target: Intel NUC BOXNUC7i7BNKQ (Core™ i7-7567U 7th Gen Kaby Lake) with Windows 10 and Silicon Debug Features enabled in the BIOS.
 
Can anyone confirm that my target system actually supports JTAG debugging over DCI?
Does the Silicon Debug Features BIOS option on the target enable DCI?
If my target does support remote JTAG debugging over DCI, how can I fix my connection problems?
 
Below are the error messages I get when System Studio tries to connect to the target, under both connection types.
 
Connection Method: Intel(R) DCI USB 3.x Debug Class
 
13:44:18 [INFO ] Attempting to connect to Target
13:44:18 [INFO ] Starting DAL ...
13:44:18 [DAL  ] Registering MasterFrame...
13:44:19 [DAL  ] Using Intel DAL 1.9.9588.100 Built 10/23/2017 against rev ID 544636 [1742]
13:44:19 [DAL  ] Using Python 2.7.12 (64bit), .NET 2.0.50727.8825, Python.NET 2.0.18, pyreadline 2.0.1
13:44:20 [DAL  ] Note:   No devices found to initialize control variables
13:44:20 [DAL  ] Warn: Cores previously specified in the 'coregroups' control variable are no longer present(may have been powered off?).
13:44:21 [DAL  ] Using KBL_KBP_OpenDCI_CCA_[DbC]_ReferenceSettings
13:44:21 [DAL  ] []> DAL startup completed
13:44:22 [INFO ] Connection successful for Target '7th Gen Intel Core Processor (Kaby Lake) / Intel 200 Series Chipset (Kaby Lake PCH-H)' with connection method 'Intel(R) DCI USB 3.x Debug Class'
13:44:23 [FATAL] Unable to connect to target.
Error in connecting to the target. Target has no connected debug devices.
 
Connection Method: Intel(R) DCI OOB
 
13:35:48 [INFO ] Connecting to target: '7th Gen Intel Core Processor (Kaby Lake) / Intel 200 Series Chipset (Kaby Lake PCH-H)' with connection method: 'Intel(R) DCI OOB'
13:35:48 [INFO ] Attempting to configure connection for Target '7th Gen Intel Core Processor (Kaby Lake) / Intel 200 Series Chipset (Kaby Lake PCH-H)' with connection method 'Intel(R) DCI OOB'
13:35:48 [INFO ] Connection configuration successful for Target '7th Gen Intel Core Processor (Kaby Lake) / Intel 200 Series Chipset (Kaby Lake PCH-H)' with connection method 'Intel(R) DCI OOB'
13:35:48 [INFO ] Attempting to connect to Target
13:35:48 [INFO ] Starting DAL ...
13:35:48 [DAL  ] Registering MasterFrame...
13:35:50 [DAL  ] Using Intel DAL 1.9.9588.100 Built 10/23/2017 against rev ID 544636 [1742]
13:35:50 [DAL  ] Using Python 2.7.12 (64bit), .NET 2.0.50727.8825, Python.NET 2.0.18, pyreadline 2.0.1
13:35:58 [DAL  ] DCI: A DCI device has been detected, attempting to establish connection
13:35:58 [DAL  ] DCI: Read FPGA Version: 0x80020124
13:35:58 [DAL  ] DCI: CCA FPGA image is already up to date
13:35:58 [DAL  ] DCI: Sending BSSB connect pattern...
13:36:00 [DAL  ] DCI: The CCA probe was successfully initialized but no target was detected, your target may be misconfigured, powered down, or unplugged.
13:36:01 [DAL  ] Target Configuration: KBL_KBP_OpenDCI_CCA_[DbC]_ReferenceSettings
13:36:04 [DAL  ] Warn:   No CPU power detected on pod 0, skip detecting tap devices on this pod!
13:36:05 [DAL  ] Warn:   Auto configuration failed due to The requested operation has timed out
13:36:05 [DAL  ] 
13:36:05 [DAL  ] Please power-cycle the target and perform itp.forcereconfig().
13:36:05 [DAL  ] Note: Power Restore occurred
13:36:05 [DAL  ] Note: Target reset has occurred
13:36:05 [DAL  ] Note:   No devices found to initialize control variables
13:36:05 [DAL  ] Warn: Cores previously specified in the 'coregroups' control variable are no longer present(may have been powered off?).
13:36:05 [DAL  ] Using KBL_KBP_OpenDCI_CCA_[DbC]_ReferenceSettings
13:36:05 [DAL  ] []> DAL startup completed
13:36:06 [INFO ] Connection successful for Target '7th Gen Intel Core Processor (Kaby Lake) / Intel 200 Series Chipset (Kaby Lake PCH-H)' with connection method 'Intel(R) DCI OOB'
13:36:08 [FATAL] Unable to connect to target.
Error in connecting to the target. Target has no connected debug devices.
 
 
 
0 Kudos

Link Copied

6 Replies
Soflen_S_Intel
Employee
‎03-26-2018 05:12 PM
3,518 Views

Hi Craig,

There're some settings in Intel BIOS setup menu for enabling DCI debugging:

1. Intel Advanced Menu -> PCH-IO Configuration -> DCI Enable (HDCIEN) -> Set to 'Enabled'

2. Intel Advanced Menu -> CPU Configuration -> Direct Connect Interface -> Set to value <Enabled>

3. Intel Advanced Menu -> PCH-IO Configuration -> Trace Hub Configuration Menu -> Trace Hub Enable Mode -> Set to value <Host Debugger>

However, your NUC system is the production PC. It has production CPU (debugging function is locked) and customized BIOS (no DCI option in the BIOS setup menu). It means you're unable to establish the DCI connection without a BIOS engineer's help. I'm not a BIOS guy but you can mail me (soflen.shih@intel.com) and elaborate more about your purpose of debugging with DCI. Then, I can forward your request to our NUC team.

Best regards,

Soflen

0 Kudos
Copy link
Anonymous93
Beginner
‎05-07-2018 11:41 PM
3,518 Views

Soflen S. (Intel) wrote:

Hi Craig,

There're some settings in Intel BIOS setup menu for enabling DCI debugging:

1. Intel Advanced Menu -> PCH-IO Configuration -> DCI Enable (HDCIEN) -> Set to 'Enabled'

2. Intel Advanced Menu -> CPU Configuration -> Direct Connect Interface -> Set to value <Enabled>

3. Intel Advanced Menu -> PCH-IO Configuration -> Trace Hub Configuration Menu -> Trace Hub Enable Mode -> Set to value <Host Debugger>

However, your NUC system is the production PC. It has production CPU (debugging function is locked) and customized BIOS (no DCI option in the BIOS setup menu). It means you're unable to establish the DCI connection without a BIOS engineer's help. I'm not a BIOS guy but you can mail me (soflen.shih@intel.com) and elaborate more about your purpose of debugging with DCI. Then, I can forward your request to our NUC team.

Best regards,

Soflen

 

Hi Soflen,

I am running into a similar issue. I sent you an e-mail with my details. 

I appreciate any help.

Thank you.

0 Kudos
Copy link
Anonymous93
Beginner
‎05-07-2018 11:42 PM
3,518 Views

Soflen S. (Intel) wrote:

Hi Craig,

There're some settings in Intel BIOS setup menu for enabling DCI debugging:

1. Intel Advanced Menu -> PCH-IO Configuration -> DCI Enable (HDCIEN) -> Set to 'Enabled'

2. Intel Advanced Menu -> CPU Configuration -> Direct Connect Interface -> Set to value <Enabled>

3. Intel Advanced Menu -> PCH-IO Configuration -> Trace Hub Configuration Menu -> Trace Hub Enable Mode -> Set to value <Host Debugger>

However, your NUC system is the production PC. It has production CPU (debugging function is locked) and customized BIOS (no DCI option in the BIOS setup menu). It means you're unable to establish the DCI connection without a BIOS engineer's help. I'm not a BIOS guy but you can mail me (soflen.shih@intel.com) and elaborate more about your purpose of debugging with DCI. Then, I can forward your request to our NUC team.

Best regards,

Soflen

 

Hi Soflen,

I am running into a similar issue. I sent you an e-mail.

I appreciate any help.

Thanks!

0 Kudos
Copy link
Jarlstrom_Intel
Employee
‎10-22-2018 10:37 AM
3,518 Views

I am using Intel System Studio 2019 Gold Release_12 and I am trying to connect the DCI USB 3.x Debug Class Cable to a Up Squared (Apollo Lake) Board (https://www.aaeon.com/en/p/iot-gateway-maker-boards-up-squared) but I am getting a connection failure with the Error message:

10:05:21 [ERROR] Connection Manager: Status change: FAILED

Error: The selected target is not available

Connection: Intel Atom Processors N4200_ N3350_ x7-E3950_ x5-39xx (Apollo Lake) (1)

Target: Intel Atom Processors N4200, N3350, x7-E3950, x5-39xx (Apollo Lake)

Connection Method: Intel(R) DCI USB 3.x Debug Class

Any help is appreciated.

Thanks,

Laurie

 

 

0 Kudos
Copy link
Johny_P_Intel
Employee
‎10-23-2018 08:19 AM
3,518 Views
Hi Laurie,
 
Please check if your host OS is able to detect the target CPU. If you are using Windows Host, go to Device Manager and check if the device is getting listed when its plugged in (via USB). Look for "Intel DCI transports" or "Intel USB Native Debug Class Device". If the device is not getting listed in Device Manager, please check and ensure that BIOS is configured appropriately to enable USB based debugging. Let me know if you need instructions on how to setup BIOS to enable debugging on Up-Squared board.
 
 
Best regards,
Johny.
 
 
0 Kudos
Copy link
Zhokhov__Nick
Beginner
‎05-19-2019 05:42 PM
3,518 Views

Intel NUC 8i7BEH

BIOS setting
Performance->Processor->Silicon Debug Feature = yes
boot linux
modprobe msr
rdmsr 0xc80
40000000
according Intel SDM vol4
MSR C80H 3200 IA32_DEBUG_INTERFACE Silicon Debug Feature Control (R/W)
bit 0 = 0 Disabled
bit 30 = 1 latch, so bit 0 can not be set to 1.

BIOS has no settings for integrated PCH to enable DCI (USB Debug ) at all.

So I'm very disappointed.
 


 

0 Kudos
Copy link
Reply

For more complete information about compiler optimizations, see our Optimization Notice.