Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
424 Views

Intel System Studio 2020 win-win: openipc install issues, can't use XDP for capture BIOS messages

Jump to solution

Hello

During installation ISS2020 I got several errors:

Intel Studio errors durong install.png

ISS2020 provides this info (Help->About):

Intel® System Studio 2020 Update 1
OS: Windows 10, v.10.0, x86_64 / win32
Java version: 11.0.6

My target system is supported in ISS config: Intel Xeon Scalable Processor (Skylake-SP) / Intel C620 Series Chipset (Lewisburg). It's OCP Tioga Pass board, derived from Crescent City platform (only BMC was replaced to AST2500 from AST1250)

The problem is that Target Indicator shows no issues:

ITP window.png

So I can connect with the target without any problems:

----------------------

14:04:08 [INFO ] TCA (client) - Connection Manager: Status change: CONNECTING
Connection: Intel Xeon Scalable Processor (Skylake-SP) _ Intel C620 Series Chipset (Lewisburg)
Target: Intel Xeon Scalable Processor (Skylake-SP) / Intel C620 Series Chipset (Lewisburg)
Connection Method: Intel(R) In-Target Probe (Intel(R) ITP) - XDP3

14:04:08 [INFO ] TCA (server) - IPConnection: Open Connection, configuration: SKX_LBG_XDPA.
14:04:21 [INFO ] TCA (client) - Connection Manager: Status change: CONNECTED
Connection: Intel Xeon Scalable Processor (Skylake-SP) _ Intel C620 Series Chipset (Lewisburg)
Target: Intel Xeon Scalable Processor (Skylake-SP) / Intel C620 Series Chipset (Lewisburg)
Connection Method: Intel(R) In-Target Probe (Intel(R) ITP) - XDP3

14:04:21 [INFO ] [npk_config_api] Successfully created target connection.
14:04:21 [INFO ] [npk_config_api]
Querying NPK hardware...
1. NPK PCI access (0x0,0x1f,0x7): false
2. NPK CSR access: true
3. NPK hardware ready: true
14:04:21 [INFO ] [npk_config_api] Detected Intel(R) Trace Hub hardware
14:04:24 [INFO ] [npk_target_config_api] [INFO] Target debug port (0x11000) state changed UNKNOWN->INVALID for devices: ALL
14:04:24 [INFO ] [npk_target_config_api] [INFO] Target debug port (0x11000) event RESET: Started
14:04:29 [INFO ] [npk_target_config_api] [INFO] Target debug port (0x11000) state changed INVALID->INVALID for devices: ALL
14:04:29 [INFO ] [npk_target_config_api] [INFO] Target debug port (0x11000) event RESET: Completed
14:04:33 [INFO ] [npk_target_config_api] [INFO] Target debug port (0x11000) event RESET: Started
14:04:33 [INFO ] [npk_target_config_api] [INFO] Target debug port (0x11000) event RESET: Completed

-----------------------

But I can't capture any data from the target in System Trace. I got these errors:

--------------------------

14:06:11 [INFO ] Capture started
14:06:11 [INFO ] NPK TDE Launcher Version 1.2011.547.100 64 Bit (Mar 19 2020)
14:06:12 [INFO ] Establishing connection to the IPC API. This may take some time.
14:06:12 [INFO ] Successfully connected to the IPC API.
14:06:12 [ERROR] The selected mode "pti4-streaming" is not supported and execution cannot continue. No trace data will be captured.
14:06:12 [INFO ] Disconnecting from the IPC API.
14:06:12 [INFO ] Successfully disconnected from the IPC API.
14:06:12 [INFO ] MIPI STP Decoder Trace Statistics [instance: mipi]
14:06:12 [INFO ] | Master | Channel | Packets | Protocol |
14:06:12 [INFO ] | 0| 0| 0| UNDEFINED|
14:06:12 [INFO ] Trace does not contain sync packet
14:06:12 [INFO ] End of MIPI STP Decoder Trace Statistics
14:06:13 [INFO ] Capture stopped with 0 Messages.
14:06:13 [WARN ] Trace capturing stopped unexpectedly. Applying stop trace configuration.
14:06:13 [INFO ] [npk_config_api] Initiating Intel(R) Trace Hub stop sequence.
14:06:13 [INFO ] [npk_target_config_api] [INFO] IPCDID 0x10001 RESUME->HALT name: breakpoint: Sympathetic.
14:06:14 [INFO ] [npk_target_config_api] [INFO] IPCDID 0x10001 HALT->RESUME name: breakpoint: .
14:06:14 [WARN ] [AET] NPK_STH_ACPIBAR_BASE MSR (080h) must be configured before AET can be traced.
Configuration of AET will be skipped.

14:06:14 [INFO ] [npk_target_config_api] [INFO] IPCDID 0x10001 RESUME->HALT name: breakpoint: Sympathetic.
14:06:14 [INFO ] [npk_target_config_api] [INFO] IPCDID 0x10001 HALT->RESUME name: breakpoint: .
14:06:16 [WARN ] Timeout waiting for capture process start, applying configuration now. Initial events might be missed in the capture.
14:06:17 [INFO ] [npk_target_config_api] [INFO] IPCDID 0x10001 RESUME->HALT name: breakpoint: Sympathetic.
14:06:17 [INFO ] [npk_target_config_api] [INFO] IPCDID 0x10001 HALT->RESUME name: breakpoint: .
14:06:17 [INFO ] [npk_config_api]
Querying NPK hardware...
1. NPK PCI access (0x0,0x1f,0x7): false
2. NPK CSR access: true
3. NPK hardware ready: true
14:06:17 [INFO ] [npk_config_api] Initiating Intel(R) Trace Hub start sequence.
14:06:18 [INFO ] [npk_target_config_api] [INFO] IPCDID 0x10001 RESUME->HALT name: breakpoint: Sympathetic.
14:06:18 [INFO ] [npk_target_config_api] [INFO] IPCDID 0x10001 HALT->RESUME name: breakpoint: .
14:06:18 [WARN ] [AET] NPK_STH_ACPIBAR_BASE MSR (080h) must be configured before AET can be traced.
Configuration of AET will be skipped.

14:06:18 [INFO ] [npk_target_config_api] [INFO] IPCDID 0x10001 RESUME->HALT name: breakpoint: Sympathetic.
14:06:19 [INFO ] [npk_target_config_api] [INFO] IPCDID 0x10001 HALT->RESUME name: breakpoint: .

-----------------------

When I discovered the qiestion, I found only one link about it:

https://community.intel.com/t5/Intel-System-Studio/Connection-problems-with-a-win10-target/m-p/11936...

Unfortunately, it does not related to my question directly - it's about DCI transport that I don't need to use because I have XDP. Just in case I reinstlalled DCI driver, as it was advised there, "Setup_x64_Intel_DCI_Driver_XYZ.msi"

but nothing changed.

Next I tried to run ipccli.exe from "C:\IntelSWTools\sw_dev_tools\tools\python3\Scripts" directory to check and got this:

My Python script with XDP.png

This is screenshot of my ISS window where I can't capture data:

ISS Screenshot.png

The only guess I have that ISS considers my PC as 32-bit system in some strange way (from Help->About) OS: Windows 10, v.10.0, x86_64 / win32)

I understand that root cause of my problem is the post-install message "install_openipc.ps1 completed with error 1332", but how I can fix that?

I also tried to istall Update 2, but the situation become much worse - I couldn't see my target platform in ISS configs at all.

WBR,

Nikolay

0 Kudos

Accepted Solutions
Highlighted
Moderator
370 Views

Nikolay 

For the first issue I dont think the Install Failures will prevent you from using the tool , its most probably irrelevant to the issue you are seeing.

For the System Trace issue, System Trace can only collect messages when you are collecting them through Intel DCI based probes which are CCA and DBC. While you can connect to the platform and do source level debug with the ITP-XDP probe the System Trace capability is not supported by it

In the screenshot you shared - You can see that SKL-LBG is supported with ITP-XDP for use of System Debug and System Debug Legacy but the System Trace feature is grayed out.

View solution in original post

0 Kudos
12 Replies
Highlighted
Moderator
400 Views

Nikolay

I sent you an email , could you confirm and reply back to me there if you have received it?

Juhi


0 Kudos
Highlighted
Beginner
380 Views

Hi Juhi

I have answered on the email.

There are new circumstances I found out since yestersay.

1. To exclude HW issue I installed ISS Update 2 on another PC (my personal notebook). Same environment (Win10) with the same error:

fail2.png

2. I also found a contradiction:

- I watched Intel's  training "Introduction of System Debug and Trace in Intel® System Studio 2018" and found out that C620 PCH doesn's support XDP3 tool:

AvailableDebuggers.png

However, in ISS2020 it is supported:

Create connections.png

Maybe ISS2018 didn't support XDP3, but... To which source I should trust?

WBR,

Nikolay

 

0 Kudos
Highlighted
Moderator
371 Views

Nikolay 

For the first issue I dont think the Install Failures will prevent you from using the tool , its most probably irrelevant to the issue you are seeing.

For the System Trace issue, System Trace can only collect messages when you are collecting them through Intel DCI based probes which are CCA and DBC. While you can connect to the platform and do source level debug with the ITP-XDP probe the System Trace capability is not supported by it

In the screenshot you shared - You can see that SKL-LBG is supported with ITP-XDP for use of System Debug and System Debug Legacy but the System Trace feature is grayed out.

View solution in original post

0 Kudos
Highlighted
Beginner
342 Views

Hi Juhi

It looks like you mean this picture, right? DCI only can be used there?

TraceHub.png

Well, but it leads to sad conclusion: I cannot use XDP-ITP adaptor with C620 PCH for work with CScripts, right?

Ok, now the second question, if I have to use DCI.CCA or DCI.DbC2-3 only: how to fix these setup error messages? install_dal script does not work, install_openipc doesn't work, too.  It looks like I can't work even through DCI, if I purchase DCI.CCA 

error_install.png

0 Kudos
Highlighted
Moderator
287 Views

I replied to your question through email Could you respond to that?

0 Kudos
Highlighted
Beginner
272 Views

Hi Juhi

Sorry for being late. I checked another options.

I got your explanation.

I tried to connect to the target via DbC2 (USB cable with Type A on both ends), and I can't connect with target system at all. Of course, I enabled DCI in BIOS image using Flash Image Tool. The problem is that my host can't see the target maschine.

DebuggerTarget.png

I think now the problem is in hardware, that's what I'm trying to find out now. Maybe I'll purchase SVT CCA adaptor to check if it is pure hardware or pure software issue, but CCA delivery will spend about a month.

Anyway, I think I got answer on my questions. Thank you!

 

WBR,

Nikolay

0 Kudos
Highlighted
Beginner
250 Views

Hi Juhi

I investigated this issue a bit further and I think now that the reason is in IIS software installation. Look:

1. I'm sure I have USB3 -> Type C cable.

2. I can use DbC3 cable only, not DbC2, by couple of reasons:

a) My schematics is for DbC3: 2 unidirectional diff pairs onlyWiwynn_sch.png

b) ISS shows that only DbC3 cable option is possible, I can't define DbC2 cable at all:

IntelStudioTargetConnection.png

3. I'm sure DCI is enabled in BIOS:

Flash Image Tool.png

So what I have now:

- PnP says that some device evolved which is not recognized on USB bus:

insert_cable.png

- Device Manager says that some device is not unstalled on USB bus:

device_manager.png

In connection with error message that I pointed at in my first post in this topic:

fail2.png

I also see that Target indicator shows DCI driver is installed (see "DCI driver: 1.10.0" caption in my previous message).

I made a conclusion that the reason of the issue is purely in ISS installation.

I also noticed that both "The Intel® DAL - Intel® Platform Debug Toolkit (Intel® PDT)" and "Intel® OpenIPC - Intel® Platform Validation Toolkit (Intel® PVT)" tools are unaccessible for me on Intel downloads. Are they prerequisites for install ISS?

What would you recommend?

WBR,

Nikolay

0 Kudos
Highlighted
Beginner
172 Views

Hello Juhi

 

I think I have fixed ISS2020 installation issues I described at the start of the topics:

fail2.png

Both install_dal.ps1 and install_opc.ps1 scripts have lines like that:

icacls `".\tools\DAL_1.2024.1316.110\TopoConfig.xml`" /inheritance:d /grant `"Users`":m

I wouldn't say I'm an expert in Windows PowerShell, but `"Users`" is probably the error. That's what I see in PowerShell by running install_dal.ps1:

WrongPowerShell.png

We wee that result in ISS installation as Error 1332 (see first picture in this comment)

Well, let's try now to fix the error writing ($user) instead of `"Users`" in install_dal.ps1 script:

ScriptInstallError.png

And run the script again:

GoodPowerShell.png

As we can see, the problem is fixed.

Same for install_opc.ps1. Only these 2 scripts contain `"Users`" string and ISS installer reports about errors in 2 these scripts execution.

Please ask ISS developers to fix that issue. BTW, the issue is well-known, I see such a string in both these scripts:

# Fix the write permissions of config files

But these issues haven't fixed in ISS Installer yet.

The problem is that I still have no access from ISS via DCI to my target board, even with correction these two issues. 

0 Kudos
Highlighted
Moderator
121 Views

Nikolay

Thanks for pointing this out - I can point this to the Dev team if its not already fixed

but as I said before the installation errors werent related to your DCI issues, the installation errors dont block you from using the tool .

 

For using Cscripts with the tool you need to download the ISD NDA version of the tool . 

One of the reasons it cant recognize the DCI device could the DCI driver on the host side too.

I would recommend that you start by installing ISD NDA and then we can have a online call to debug the issues. Let me know if that is okay with you?

If it is I will send you instructions on how to do that via email.

0 Kudos
Highlighted
Beginner
87 Views

Hello Juhi

I filled in request on Intel site to have an access toISD NDA version of the tool, but still have no answer.

WBR,

Nikolay

0 Kudos
Highlighted
Moderator
72 Views

Nikolay

Your request was approved on 13th september. Please check your inbox from Intel registration Center. Let me know how it goes.


0 Kudos
Highlighted
Beginner
68 Views

Hi Juhi

If you mean IPS, there is a smal progress: now I can see it in search results, but still can't download it.

WBR,

Nikolay

0 Kudos