Server Products
Data Center Products including boards, integrated systems, Intel® Xeon® Processors, RAID Storage, and Intel® Xeon® Processors
Announcements
All support for Intel NUC 7 - 13 systems has transitioned to ASUS. Read latest update.
4732 Discussions

Eagle Stream CScripts: halt() command is not working.

joberski
Beginner
2,345 Views

I'm attemting to setup CSripts for use with our Eagle Streams platform. The tool seems to be working, but the halt() command returns an error. I've applied all the BIOS changes listed in Section 6 of the Eagle Stream CScripts User Guide. What's the workaround?

See trace below:


c:\cscripts>dflaunch startCscripts.py -a ipc -p SPR
"WARNING: IPC_PATH environment variable is set and this OpenIPC instance will be"
" used. If this is intentional you can ignore this warning, otherwise"
" please unset the IPC_PATH environment variable and rerun the script."
" Note that this variable might be defined globally/system-wide."
Python 3.8.16 (default, Feb 20 2023, 18:54:26) [MSC v.1929 64 bit (AMD64)] on win32
PythonSv running in interactive mode
win32com not found, using alternative check_running_windows method
Connecting to IPC API....
IPC-CLI: 3.23.20218.100, OpenIPC:c13b8e12535d1a93e31f6da : 23.6.12785.200
Initializing IPC API....

Info - OpenIPC using automatic configuration

Info - Added debug port 0 for probe XDPA 1-2

Info - Detected SPR_CLTAP E2 on JTAG chain 0 at position 0

Info - Detected EBG B1 on JTAG chain 1 at position 0

Info - Survivability Preset was requested, but no supported devices were detected. Preset will be applied when a supported device is detected.
TargetEvent: Power : On -- 12:18:53.734743 2023-03-22
TargetEvent: PowerDomain : PCH : On -- 12:18:53.734743 2023-03-22
Target System: SPR - sapphirerapids
ipc.clients: [{'name': 'pythonsv-ipccli_10688@CNBULAB01-LAP', 'Id': 1}]
Current Working Dir: C:\Users\joberski\PythonSv

*******************************************************************************
Welcome to CScripts for Server & Micro-server platforms!
These scripts are provided as-is as a courtesy to assist with platform
debug. They are NOT intended for manufacturing or production line validation,
and Intel makes no guarantee, implied or otherwise, that these scripts will
function in a production environment. They are not fully validated by Intel
nor guaranteed to execute as described. These scripts rely on (in some cases)
unspecified features within our components which may or may not be functional
from stepping to stepping, or from product to product. They are provided at
no cost. Customers are free to modify these scripts as needed for their own
platform debugging purposes. Defects should be reported to your Intel account
representative.

All log files will be placed in C:\Users\joberski\PythonSv
For help on functions or objects when in the shell type help(NAME)

*******************************************************************************

Cscripts version: EGS.2307.6000.3873
IPC-CLI Version 3.23.20218.100
Probe Information: PortPath: 1-2, SerialNum: 62042471, FwRev: XDP3_fpga_09020215, AsmNum: E17244-001
Start Platform Stuff with access type ipc
PCH type is unknown on a running system - check PCH later.
Socket 0: detected Server, 52 cores, E2, PCI Segment 0, Bus List = [0x00, 0x15, 0x3f, 0x69, 0x93, 0xbd, 0xe7, 0xe8, 0xea, 0xec, 0xed, 0xef, 0xf1, 0xf2, 0xf4, 0xf6, 0xf7, 0xf9, 0xfe, 0xff]
>>> halt()
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "cscripts\dependencies\ipccli\ipc_env\ipc_baseaccess.py", line 1274, in halt
File "cscripts\dependencies\py2ipc\IPC2PyUtils.py", line 106, in newfunc
File "cscripts\dependencies\py2ipc\Service_OperationReceipt.py", line 170, in Flush
File "cscripts\dependencies\py2ipc\IPCTypes.py", line 83, in IPC_ErrorCheck
py2ipc.IPCErrorCodes.IPC_Error: RunControl_Timeout == 0x800a0004
. Timeout occurred while waiting for threads to halt with 0 retries
>>>

0 Kudos
8 Replies
Allan_A_Intel
Moderator
2,289 Views

Hello, joberski,


I suggest you checking this article for ways of getting help with CScripts for Platforms: https://www.intel.com/content/www/us/en/support/articles/000088384/programs/resource-and-documentation-center.html


Also, I might find more information. Please let me know what is the motherboard's brand and model.


Best regards,

Allan


0 Kudos
ganeshks
Beginner
2,224 Views

Hi Allan,

I am having the same issue as well while using CScripts, the platform I have is Archer City CRB, CPUs are Sapphire Rapids Gold 6442Y, please let me know how this can be resolved.

C:\cscripts>dflaunch startCscripts.py -a ipc -p SPR
...
Python 3.8.15 (default, Nov 10 2022, 21:28:27) [MSC v.1916 64 bit (AMD64)] on win32
PythonSv running in interactive mode
win32com not found, using alternative check_running_windows method
Connecting to IPC API....
IPC-CLI: 3.22.22507.100, OpenIPC:bcd4bb5227e107cf2a38084 : 23.2.12727.200
Initializing IPC API....

Info - OpenIPC configuration 'SPR_EBG_XDPA'; probe plug-in(s): 'XDPA'

Info - Added debug port 0 for probe XDPA 1-5

Info - Detected SPR_CLTAP S3 on JTAG chain 0 at position 1
Info - Detected SPR_CLTAP S3 on JTAG chain 0 at position 0

Info - Detected EBG B1 on JTAG chain 1 at position 0

Info - Survivability Preset was requested, but no supported devices were detected. Preset will be applied when a supported device is detected.
Target System: SPR - sapphirerapids
ipc.clients: [...]
Current Working Dir: C:\Users\...\PythonSv

*******************************************************************************
Welcome to CScripts for Server & Micro-server platforms!

...

Cscripts version: EGS.2232.6000.2585
IPC-CLI Version 3.22.22507.100
Probe Information: PortPath: 1-5, SerialNum: 62204098, FwRev: XDP3_fpga_09020215, AsmNum: E17244-001
Start Platform Stuff with access type ipc
PCH type is unknown on a running system - check PCH later.
Socket 0: detected Server, 24 cores, S3, PCI Segment 0, Bus List = [0x00, 0x16, 0x29, 0x3c, 0x4f, 0x62, 0x75, 0x7a, 0x7c, 0x7e, 0x7f]
Socket 1: detected Server, 24 cores, S3, PCI Segment 0, Bus List = [0x80, 0x98, 0xaa, 0xbc, 0xce, 0xe0, 0xf2, 0xf7, 0xf9, 0xfe, 0xff]

>>> itp.halt()
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "cscripts\dependencies\ipccli\ipc_env\ipc_baseaccess.py", line 1125, in halt
File "cscripts\dependencies\py2ipc\IPC2PyUtils.py", line 106, in newfunc
File "cscripts\dependencies\py2ipc\Service_OperationReceipt.py", line 170, in Flush
File "cscripts\dependencies\py2ipc\IPCTypes.py", line 72, in IPC_ErrorCheck
py2ipc.IPCErrorCodes.IPC_Error: RunControl_Timeout == 0x800a0004
. Timeout occurred while waiting for threads to halt with 0 retries


>>> itp.ishalted()
False
>>> itp.isrunning()
True

0 Kudos
joberski
Beginner
2,214 Views

Hi Allan,

Theat link didn't really help, but I have resolved my problem on my own. I discovered that I needed to load a debug BIOS which enables the halt() capability, and I have obtained and installed such a BIOS.

0 Kudos
Allan_A_Intel
Moderator
2,213 Views

Hello, joberski,


Thank you for the update. I am glad to see that you were able to find a solution.


Best regards,

Allan


0 Kudos
astera-cmorrison
Beginner
719 Views

I'm also facing this issue. I've tried BKCs: PLR2-3 (EGSDCRB.SYS.OR.64.2023.21.5.02.0737.1_SPR_EBG_SPS_IPClean.bin) and 2023-WW13 (EGSDCRB.SYS.OR.64.2023.11.2.03.1901.1_SPR_EBG_SPS_IPClean.bin) and no luck. Can someone elaborate on what the "debug BIOS" is and where to download it?

 

Thanks,

Casey

iqbalr
Beginner
366 Views

Having the same issue with our Eagle Stream 2 Socket Platform running:

  • Host image: EGSDCRB1.SYS.0084.D24.2207132145
  • BMC: egs-0.91-194-g07d197-9248c75

Agree with @astera-cmorrison - can someone elaborate what special BIOS is needed to enable this?

@joberski - can you provide firmware details?

0 Kudos
iqbalr
Beginner
364 Views

Per the thread below - seems like we need to apply for access to unlock the CPU(s)? Can anyone confirm?


https://community.intel.com/t5/Software-Archive/Target-did-not-halt-execution/td-p/1023405

0 Kudos
iqbalr
Beginner
349 Views

Also noticed this in the release notes for most recent CScripts release (12/13/2023):

*Note: CScripts is validated with non-production BIOS as access to certain DFX registers that CScripts requires is removed in production BIOS. If you test with production BIOS, some RAS functions may fail or return unexpected results. We highly recommend you use a non-production BIOS when testing with CScripts. Please contact your Intel representative for any questions.

**SPR BKC no longer includes a debug binary for the BIOS. If you cannot halt the cores to execute some CScripts functions, CPU Debugging must be enabled in the BIOS image via FITM tool.

0 Kudos
Reply