SourcePoint Intel Help
Table of Contents
- Using Help
- Contacting ASSET InterTech
- Introduction to SourcePoint
- SourcePoint Environment
- SourcePoint Overview
- SourcePoint Parent Window Introduction
- SourcePoint Icon Toolbar
- File Menu
- File Menu - Project Menu Item
- File Menu - Layout Menu Item
- File Menu - Program Menu Item
- File Menu - Macro Menu Item
- File Menu - Print Menu Items
- File Menu - Update Emulator Flash Menu Item
- File Menu - Program Target Device Menu Item
- File Menu - Other Menu Items
- Edit Menu
- View Menu
- Processor Menu
- Options Menu
- Options Menu - Preferences Menu Item
- Options Menu - Target Configuration Menu Item
- Options Menu - Load Target Configuration File Menu Item
- Options Menu - Save Target Configuration File Menu Item
- Options Menu - Emulator Configuration Menu Item
- Options Menu - Emulator Connection Menu Item
- Options Menu - Emulator Reset Menu Item
- Options Menu - Confidence Tests Menu Item
- Window Menu
- Help Menu
- How To -- SourcePoint Environment
- Add Emulator Connections
- Configure Custom Macro Icons
- Configure Autoloading Macros
- Display Text on the Icon Toolbar
- Edit Icon Groups to Customize Your Toolbars
- Modify a Defined Memory Region
- Refresh SourcePoint Windows
- Save a Program
- Start SourcePoint With Command Line Arguments
- Use the New Project Wizard
- Verify Emulator Network Connections
- SourcePoint Overview
- Breakpoints Window
- Breakpoints Window Overview
- How To - Breakpoints
- Code Window
- Command Window
- Command Window Overview
- Confidence Tests Window
- Confidence Tests Window Overview
- Descriptors Tables Window
- Descriptors Tables Window Overview
- How To - Descriptors
- Devices Window
- Devices Window Overview
- How To - Devices Window
- Log Window
- Log Window Overview
- Memory Window
- Memory Window Overview
- How To - Memory Window
- Page Translation Window
- Page Translation Windows Overview
- PCI Devices Window
- PCI Devices Window Overview
- How To - PCI Devices Window
- Registers Window
- Registers Window Overview
- How To - Registers
- Symbols Windows
- Symbols Window Overview
- How To - Symbols Window
- Trace Window
- Trace Window Overview
- How To - Trace Window
- Advanced
- Viewpoint Window
- Viewpoint Window Overview
- Watch Window
- Watch Window Overview
- How To - Watch Window
- Technical Notes
- Descriptor Cache: Revealing Hidden Registers
- UEFI Framework Debugging
- Memory Casting
- Microsoft PE Format Support in SourcePoint
- Multi-Clustering
- Python/CScripts
- OpenIPC Integration, Installation and Usage
- Registers Keyword Table
- SourcePoint Licensing
- Stepping
- Symbols Textsym Format
- Target Configuration
- Using Bookmarks
- Which Processor Is Which
- Getting Started with DbC
- SourcePoint Command Language
- Overview
- Commands and Control Variables
- aadump
- abort
- abs
- acos
- advanced
- asin
- asm
- asmmode
- atan
- atan2
- autoconfigure
- base
- bell (beep)
- bits
- break
- breakall
- cachememory
- cause
- Character Functions
- clock
- continue
- cos
- cpubreak commands
- cpuid_eax
- cpuid_ebx
- cpuid_ecx
- cpuid_edx
- createprocess
- cscfg, local_cscfg
- csr
- ctime
- cwd
- dbgbreak commands
- defaultpath
- #define
- define
- definemacro
- deviceconfigure
- devicelist
- devicescan
- disconnect
- displayflag
- do while
- dos
- dport
- drscan
- edit
- editor
- emubreak, emuremove, emudisable, emuenable
- emulatorstate
- encrypt
- error
- eval
- evalprogramsymbol
- execution point ($)
- exit
- exp
- fc
- fclose
- feof
- fgetc
- fgets
- first_jtag_device
- flist
- flush
- fopen
- for
- forward
- fprintf
- fputc
- fputs
- fread
- fseek
- ftell
- fwrite
- getc
- getchar
- getnearestprogramsymbol
- getprogramsymboladdress
- gets
- globalsourcepath
- go
- halt
- help
- homepath
- idcode
- if
- include
- invd
- irscan
- isdebugsymbol
- isem64t
- isprogramsymbol
- isrunning
- issleeping
- issmm
- itpcompatible
- jtagchain
- jtagconfigure
- jtagdeviceadd
- jtagdeviceclear
- jtagdevices
- jtagscan
- jtagtest
- keys
- last
- last_jtag_device
- left
- libcall
- license
- linear
- list, nolist
- load
- loadbreakpoints
- loadlayout
- loadproject
- loadtarget
- loadwatches
- log, nolog
- log10
- loge
- logmessage
- macropath
- Memory Access
- messagebox
- mid
- msgclose
- msgdata
- msgdelete
- msgdr
- msgdump
- msgir
- msgopen
- msgreturndatasize
- msgscan
- msr
- num_activeprocessors
- num_all_devices
- num_devices
- num_jtag_chains
- num_jtag_devices
- num_processors
- num_uncore_devices
- openipc
- pause
- physical
- port
- pow
- print cycles
- printf
- proc
- processorcontrol
- processorfamily
- processormode
- processors
- processortype
- projectpath
- putchar
- puts
- rand
- readsetting
- reconnect
- Register Access
- reload
- reloadproject
- remove
- reset
- restart
- return
- right
- runcontroltype
- safemode
- save
- savebreakpoints
- savelayout
- savewatches
- selectdirectory
- selectfile
- shell
- show
- sin
- sizeof
- sleep
- softbreak, softremove, softdisable, softenable
- sprintf
- sqrt
- srand
- step
- stop
- strcat
- strchr
- strcmp
- strcpy
- _strdate
- string [ ] (index into string)
- strlen
- _strlwr
- strncat
- strncmp
- strncpy
- strpos
- strstr
- _strtime
- strtod
- strtol
- strtoul
- _strupr
- swbreak
- switch
- swremove
- tabs
- tan
- tapdatashift
- tapstateset
- targpower
- targstatus
- taskattach
- taskbreak, taskremove, taskdisable, taskenable
- taskend
- taskgetpid
- taskstart
- tck
- time
- uncoreconfigure
- uncorescan
- #undef
- unload
- unloadproject
- upload
- use
- verify
- verifydeviceconfiguration
- verifyjtagconfiguration
- version
- viewpoint
- vpalias
- wait
- wbinvd
- while
- windowrefresh
- wport
- writesetting
- yield
- yieldflag
Python/CScripts Introduction, Installation and Usage
Introduction
CScripts (Customer Scripts) are a collection of Python scripts provided by Intel to assist customers with platform debug and validation. ย Asset-InterTech has support in place to run these scripts in its SourcePoint product. ย
Note: ย This technical note discusses running CScripts from within the SourcePoint Command view. ย CScripts can also be run in an external CLI. ย This has the advantage of supporting tab completion, coloring, and other advanced features. ย See the OpenIPC Integration, Installation and Usage for more information.
Requirements
CScripts are designed to be run inside SourcePoint, using its Command view. ย Therefore, the host system requirements are the same as the requirements and pre-requisites for SourcePoint. ย Refer to SourcePointโs Installation Guide for these requirements.
As CScripts are written in Python, the host system will need to have Python installed. ย Current support is in place for 32-bit Python version 2.7. ย Some scripts are compiled, so CScripts will not function correctly if you have a different version of Python installed on your host.
In case you donโt already have a python installation, SourcePointโs installer comes packaged with Python 2.7.5. ย Allow the installer to maintain the default settings to ensure compatibility.
Installation
CScripts come packaged in a .zip file. This .zip file can be extracted to anywhere on the host system; however, it is recommended that it be extracted into the C:\CS folder. If a different location is chosen, please ensure there are no blank spaces in the folder name. It is a requirement that the directory structure be kept intact when extracting the .zip file, as individual script files reference other files using virtual path names.
Usage in SourcePoint
The SourcePoint Command View is not a separate python command window, rather a python environment integrated inside the application's GUI. Some aspects of SourcePoint python may not behave identically to Intel ITP II's CLI, or to a native python command window, but the CScripts should provide the same behavior.
SourcePoint python retains the concept of a viewpoint processor and supports the Intel ITP II logical node tree and the CScripts devicelist-based logical node tree.
This userโs guide describes using SourcePoint on a Microsoft Windows system with USB interface. It does not describe setup of the network interface. The SourcePoint help files have documentation on these topics.
Known current limitations:
SourcePoint does not support pyreadline, and has no tab-completion. Use the dir() command with a module name to see names of interest.
Invoking CScripts under SourcePoint
There are currently three ways to load CScripts. Option #1 is easy and recommended for both new and experienced users.
Option #1:
-
Locate the root directory of the CScripts and use the mouse drag/drop technique to drag the file <startup script name>.py into the SourcePoint Command view. This will switch to python mode, import the CScripts, and display the initial screen.
Option #2:
-
In the Command view, enter 'python' to switch to python mode.
-
Enter a second prompt to cause the python version to appear, indicating interactive mode python initialization.
-
At the prompt, enter (for example) 'arium.runfile("<path>\startivt_oem_arium.py")' to import the CScripts. ย The name of the startup script may be slightly different from the above, depending on the version of CScripts being used. ย If thatโs the case, just replace the name in the above command with the correct script name.
Option #3:
-
In the command view, enter 'python' to switch to python mode.
-
Enter a second prompt to cause the python version to appear, indicating interactive mode python initialization.
-
At the prompt enter 'arium.runfile()' and hit return to bring up a windows explorer window, then navigate to the root directory of the CScripts package and double-click on the startup script start_oem_arium.py (or similar) to run it.
The various functions of CScripts can now be used as described in the CScripts User Guide from the SourcePoint Command view, noting that tab completion doesnโt work, and the display will be embedded in the application UI. ย The CScripts User Guide can be found in the root directory of the CScripts package.
To exit the session, enter the command 'cscript()' to exit python mode, then exit to leave SourcePoint.