Installation Guide and Release Notes
Intel® System Studio 2013
Intel® JTAG Debugger 3.0
Installation Guide and Release Notes
Installation Guide and Release Notes
Document number: 327661-004US
14 February 2013
Contents
1
Introduction ......................................................................................................................... 4
2
Technical Support and Documentation ............................................................................... 5
2.1
3
4
5
Product Contents ......................................................................................................... 5
What's New ......................................................................................................................... 6
3.1
General Updates .......................................................................................................... 6
3.2
Target Platform Support ............................................................................................... 7
System Requirements ......................................................................................................... 7
4.1
Host Software Requirements ....................................................................................... 7
4.2
Target Software Requirements .................................................................................... 7
4.3
Hardware Requirements .............................................................................................. 7
4.4
Ordering required JTAG Device ................................................................................... 8
4.4.1
Intel® ITP-XDP3 ................................................................................................... 8
4.4.2
Macraigor* usb2Demon* ....................................................................................... 8
Installation Notes ................................................................................................................ 9
5.1
Pre-Installation Steps ................................................................................................... 9
5.1.1
Notes on installing a 32bit JRE on a 64bit Windows* system ................................ 9
5.2
Product Installation (Online Installer) ..........................................................................10
5.3
Product Installation (Full Product) ...............................................................................10
5.4
Silent Install ................................................................................................................10
5.5
Installing Intel® XDP3 JTAG Probe.............................................................................10
5.6
Installing Macraigor Systems* usb2Demon* Support ..................................................11
5.7
Uninstalling the Product ..............................................................................................12
Intel® JTAG Debugger Installation Guide and Release Notes
1
6
7
Features ............................................................................................................................13
6.1
Full Intel LPIA Silicon & Chipset support .....................................................................13
6.2
Execution Trace Support.............................................................................................13
6.3
OS Awareness / Kernel Module Debugging ................................................................13
6.4
Scripting Language .....................................................................................................14
6.5
Page Translation Table ...............................................................................................14
6.6
Unload of Symbol Information .....................................................................................14
6.7
Power Events Handling ...............................................................................................14
6.8
NAND Flashing support on Intel® Atom™ Processor CExxxx .....................................14
6.9
Supported Flash Types ...............................................................................................14
Usage Notes ......................................................................................................................16
7.1
Starting the Debugger .................................................................................................16
7.2
Burning blank flash on Intel® Atom™ Processor CE5300 based platforms .................16
7.3
eMMC Flash Recovery on Intel® Puma6™ Media Gateway .......................................16
7.4
eMMC Flash on Intel® Atom™ Processor CE42xx and CE53xx .................................17
7.4.1
Partitions..............................................................................................................17
7.4.2
Addressing...........................................................................................................17
7.4.3
Erasing ................................................................................................................17
7.5
8
FTL Lite NAND Flash Programming on the Intel® Atom™ Processor CE4100 ...........18
7.5.1
Addressing...........................................................................................................18
7.5.2
Backup.................................................................................................................18
7.6
Enabling Run-Time Loaded Kernel Module Debugging ...............................................19
7.7
Unload of Symbol Information .....................................................................................19
Issues and Limitations........................................................................................................19
8.1
Known Issues and Limitations .....................................................................................19
8.1.1
Support for Intel® Atom™ processor bitfield editor register views ........................19
8.1.2
Macraigor Systems* usb2Demon* does not support single stepping on Intel®
Puma6™ Media Gateway ..................................................................................................19
8.1.3
Locals Window updates can be slow ...................................................................20
8.1.4
Kernel Threads Window Population Slow ............................................................20
8.1.5
Debugger puts a Windows file system lock on symbol files ..................................20
8.1.6
Frequently loading and unloading debug symbols ...............................................20
8.1.7
Flash programming with empty flash parts (CE4200) ...........................................20
Intel® JTAG Debugger Installation Guide and Release Notes
2
8.1.8
Use of Macraigor* usb2Demon to debug Intel® Atom™ processor CE4xxx based
platforms may require board changes ................................................................................20
8.1.9
Older Macraigor* usb2Demon 60pin connector headers ......................................21
8.1.10
Backup of large flash partitions may fail ...............................................................21
8.1.11
Verification of flash content on Intel® Atom™ processor E6xx based platform.....21
8.1.12
Function and file information not listed for watchpoints in breakpoint window ......21
8.1.13
Target doesn't boot when Macraigor* usb2Demon* JTAG device is not initialized
21
8.1.14 Local variables and evaluation windows do not display multi-dimensional arrays
correctly 21
8.1.15
Evaluation window for global variables may be missing type information .............21
8.1.16 Writing to a non-writable vector registers may incorrectly update register value
display 22
8.1.17 With Intel® Hyper-Threading Technology disabled in BIOS debugger SMP
configuration must be disabled as well when using Macraigor Systems* usb2Demon* ......22
8.1.18
Root or Sudo Access required for JTAG Debugger Install....................................22
8.1.19
Memory Writes to Un-Initialized Memory..............................................................22
8.1.20
Flash Writer disables pre-existing Breakpoints.....................................................22
8.1.21 Master Flash Header Read/Write not supported for Intel® Atom™ Processor
CE4200 22
9
10
Attributions .........................................................................................................................23
Disclaimer and Legal Information ...................................................................................24
Intel® JTAG Debugger Installation Guide and Release Notes
3
1 Introduction
This Intel® JTAG Debugger 3.0 release for the Intel® System Studio 2013 provides a Windows*
7 hosted cross-debug solution for software developers to debug kernel sources and dynamically
loaded drivers and kernel modules on devices based on the Intel® Atom™ Processor CE41xx,
CE42xx, CE53xx and the Intel® Puma6™ Media Gateway. It does so using the In-Target Probe
eXtended Debug Port (ITP-XDP) on these platforms
As JTAG communication device you have the choice between the Macraigor* usb2Demon* and
the Intel® ITP-XDP3. Beyond this the debugger also offers convenient and in-depth access to
underlying hardware properties through a powerful graphical user interface (GUI). This makes it
an ideal assistant for initial platform bringup and firmware and BIOS debugging. A set of
features providing in-depth access to the development platform complete the offering for system
developers:



Execution trace support for identifying incorrect execution paths or memory accesses
Graphical representation of the page translation table with full access of the descriptor
tables
Flashing Support
These debugger capabilities minimize the time it takes to isolate and correct platform and
system level problems.
This document provides system requirements, installation instructions, issues and limitations,
and legal information.
Intel® JTAG Debugger Installation Guide and Release Notes
4
2 Technical Support and Documentation
The default installation directory is
C:\Program Files(x86)\Intel\System Studio 2013.0.xxx\
The directory <INSTALL-DIR>\Documentation\en_US\debugger\xdb includes
these release and installation notes w_jtag_release_install.pdf.
The directory
<INSTALL-DIR>\Documentation\en_US\debugger\xdb\first_use\
contains the QuickStart Guide xdb_quickstart_win.pdf and debugger Usage Guide
xdb_usage.pdf
In addition, the Intel® JTAG Debugger user manual and “Intel® Debugger Online Help” can be
accessed at
<INSTALL-DIR>\Documentation\en_US\debugger\xdb\cl\index.htm.
If you did not register your compiler during installation, please do so at the Intel® Software
Development Products Registration Center. Registration entitles you to free technical support,
product updates and upgrades for the duration of the support term.
To submit issues related to this product please visit the Intel Premier Support webpage and
submit issues under the product Intel(R) System Studio for Linux* OS.
Additionally you may submit questions and browse issues in the Intel® System Studio User
Forum.
For information about how to find Technical Support, product documentation and samples,
please visit http://software.intel.com/en-us/intel-system-studio.
Note: If your distributor provides technical support for this product, please contact them for
support rather than Intel.
2.1

Product Contents
Intel® JTAG Debugger 3.0
Intel® JTAG Debugger Installation Guide and Release Notes
5
3 What's New
Below are some of the new features in the Intel® JTAG Debugger
3.1
General Updates

Instruction Trace Window:
The new instruction trace window provides collapsible source assembly instruction
display. Also new “Source follows Trace” and “Disassembly follows Trace” features
have been added. This allows moving around in the trace output window and having the
source and disassembly windows automatically jump to those locations as well.

Extensible Firmware Interface (EFI) Support:
When the target is booting through an EFI BIOS (PEI or DXE phase of the boot process)
which has been built with debug information, the debugger can parse the PE/COFF
headers and locate an address in source.
Use the command
xdb> efi “loadthis <address>”
Providing an address is optional. If no address is passed on the current instruction
pointer is used.
In addition the EFI plugin is able to automatically search and find the system table
pointer. Once found many of the key aspects of the EFI environment including loaded
services and modules can be listed.
xdb> efi “showsystab”
xdb> efi “showmodules”
Please see the output of the
xdb> efi “showhelp”
command for more details.

Updated Eclipse* RCP based graphical user interface

Fixes of outstanding issues
Intel® JTAG Debugger Installation Guide and Release Notes
6
3.2

Target Platform Support
Support for Intel® Puma6™ Media Gateway
The Intel® JTAG Debugger has been tested against debugging CE Linux* PR28 builds
on Intel® Software Development Platforms based on the Intel® Puma6™ Media
Gateway.

Flashing Support for eMMC NAND flash Intel® Puma6™ Media Gateway
The Intel® JTAG Debugger is now able to flash eMMC NAND flash on Intel® Software
Development Platforms based on the Intel® Puma6™ Media Gateway.

eMMC flash recovery on Intel® Puma6™ Media Gateway
The Intel® JTAG Debugger is now able to flash eMMC NAND flash on Intel® Software
Development Platforms based on the Intel® Puma6™ Media Gateway, even if no
platform initialization has taken place and no cache or RAM is available to upload the
burn algorithm. Please see the eMMC Flash Recovery entry in the Usage Notes for
details.
4 System Requirements
4.1
Host Software Requirements
1. Microsoft* Windows* 7.
2. Java runtime environment (JRE) 1.5 or newer to use the Eclipse* framework. In a web
browser, access www.java.com , and download and install JRE 1.6. Ensure that the
Java runtime environment is 32bit even if you are installing on a 64bit system. (Go to
http://www.java.com/en/download/manual.jsp and select “Windows 7, XP Offline (32bit)”.
4.2
Target Software Requirements
The target platform should be based on one of the following environments:



4.3

Bare metal, BIOS, firmware environment
CE Linux* OS PR28 for Intel® Atom™ Processor CE4xxx, CE53xx and Intel® Puma6™
Media Gateway
Yocto Project* 1.x for Intel® Atom™ Processor Z5xx, E6xx, N2xxx, D2xxx
Hardware Requirements
IA-32 or Intel® 64 architecture based host computer supporting Intel® Streaming SIMD
Extensions 2 (Intel® SSE2) instructions (Intel® Pentium® 4 processor or later), or
compatible non-Intel processor.
o For the best experience, a multi-core or multi-processor system is recommended.
Intel® JTAG Debugger Installation Guide and Release Notes
7






4.4
1GB RAM (2GB recommended)
4GB free disk space for all product features and all architectures
USB 2.0 host interface
In-Target Probe eXtended Debug Port on target platform
Intel® Puma6™ Media Gateway based plaform
Intel's ITP-XDP3 JTAG Hardware Adapter or alternatively Macraigor Systems*
usb2Demon* JTAG Hardware Adapter
Ordering required JTAG Device
4.4.1 Intel® ITP-XDP3
To order the Intel® ITP-XDP3 device, please contact the Hibbert Group* at
[email protected] and request the VTG order form.
4.4.2 Macraigor* usb2Demon*
Go to http://www.macraigor.com/usbDemon.htm and select the Intel Atom™ Processor target
with the appropriate 24, 31 or 60 pin connector for your target device.
Intel® JTAG Debugger Installation Guide and Release Notes
8
5 Installation Notes
5.1
Pre-Installation Steps
Install the latest Java JRE. In a web browser, access www.java.com , and download and install
JRE 1.6. Ensure that the Java runtime environment is 32bit even if you are installing on a 64bit
system. (Go to http://www.java.com/en/download/manual.jsp and select “Windows 7, XP Offline
(32-bit)”.
5.1.1
Notes on installing a 32bit JRE on a 64bit Windows* system
Check your %PATH% environment variable
Please check your %PATH% environment variable to make sure it is pointing to the 32-bit JRE
installation. (Generally the one in “C:\Program Files (x86)” as opposed to the one in
“C:\Program Files”)
Rename “java.exe” and “javaw.exe” in “C:\Windows\System32”
Also check your “C:\Windows\System32” directory. There appears to be local copies of
the java.exe and javaw.exe in this folder. These are usually from the original Java* installation
and most likely the 64-bit versions. Since “C:\Windows\System32” is always in your
%PATH% these copies of the java executables will be used before the JRE directory added to
your system %PATH%. Please delete the copies of “java.exe” and “javaw.exe” in
“C:\Windows\System32” so that the Java directory in your PATH variable pointing to the
32-bit JREs will be used.
Verify the correct Java* Runtime Environment is used
To verify that the correct JRE is being used open a command prompt and change directory to
the bin folder in the XDB install directory.
> cd <INSTALL-DIR>\bin
> java CheckJRE
x86
Intel® JTAG Debugger Installation Guide and Release Notes
9
If the output of this call is x86 and not x64 or amd64 than you are ready to launch XDB.
5.2
Product Installation (Online Installer)
The Intel® JTAG Debugger 3.0 on Windows* host component of the Intel® System Studio 2013
is available as a smaller downloadable online installer. Only the Intel® JTAG Debugger is
included in this package. Using the online installer requires to be connected to the internet and
that https protocol based component downloads are permitted by your firewall.
Double-click on the executable file (w_cembd_online_p_2013.0.xxx.exe) to begin installation.
And follow the installer guidance.
The default installation directory is
C:\Program Files (x86)\Intel\System Studio 2013.0.xxx\
5.3
Product Installation (Full Product)
The Intel® JTAG Debugger 3.0 on Windows* host component of the Intel® System Studio 2013
is available as a downloadable file. Only the Intel® JTAG Debugger is included in this package.
Double-click on the executable file (w_cembd_p_2013.0.xxx.exe) to begin installation. And
follow the installer guidance.
The default installation directory is
C:\Program Files (x86)\Intel\System Studio 2013.0.xxx\
5.4
Silent Install
For information on automated or “silent” install capability, please see http://intel.ly/ngVHY8.
Please note that the Intel® ITP-XDP3 JTAG device driver installation does not support silent
install. If you choose silent installation for the Intel® JTAG Debugger, this device driver will need
to be installed separately afterwards
5.5
Installing Intel® XDP3 JTAG Probe
If it is not already pre-installed, the Intel® ITP-XDP3 driver is automatically installed as part of
the Intel® JTAG Debugger installation process.
The Intel® ITP-XDP3 driver installer will issue a warning that the publisher could not be verified.
Please acknowledge the warning and proceed with the installation.
Intel® JTAG Debugger Installation Guide and Release Notes
10
5.6
Installing Macraigor Systems* usb2Demon* Support
The Macraigor Systems* usb2Demon* device can be ordered at
http://www.macraigor.com/usbDemon.htm.
To enable support for the Macraigor Systems* usb2Demon* device for debugging Intel® Atom™
processor based platforms with the Intel® JTAG Debugger it is necessary to install the
Windows* drivers for the Macraigor Systems* usb2Demon* device. The driver can be found at
http://www.macraigor.com/full_gnu.htm.
You can install either the IA-32 or the Intel®64 version of the Hardware Support Package to
provide the device driver support
The Intel® JTAG Debugger has been validated for use with the Macraigor Systems*
usb2Demon* device and OCDRemote* 9.81. We recommend using OCDRemote* 9.72 for
Intel® Atom™ Processor CE53xx and at least version 9.81 of the Macraigor* Systems* driver
for all other intended target platforms.
For further details on how to configure the OCDRemote* driver set from Macraigor* Systems,
please refer to the full installation instructions at http://www.macraigor.com/full_gnu.htm .
Intel® JTAG Debugger Installation Guide and Release Notes
11
5.7
Uninstalling the Product
In the Windows* 7 Control Panel, select Add/Remove Application and choose the Intel® System
Studio 2013
To also uninstall the Intel® ITP-XDP3 driver please select


Windows Driver Package – Intel Corporation XDP USB Device
Usermode Driver for XDP Hardware
as well.
To also uninstall the Macraigor* Systems usb2Demon device driver please select

OCD Commander
as well.
Intel® JTAG Debugger Installation Guide and Release Notes
12
6 Features
6.1
Full Intel LPIA Silicon & Chipset support
Provides an in-depth view into Intel® Atom™ Processor chipsets. Supports silicon specific
features, including architectural registers, Intel® Streaming SIMD Extensions 3 (SSE3), as well
as Graphics Chipset Register support through JTAG. Graphical representation of peripheral
registers and bit fields with online documentation.
6.2
Execution Trace Support
Enables viewing of execution history and thus enhances understanding of the flow of an
executed program allowing the analysis of the execution path to find errors and identify the root
cause for exceptions.
6.3
OS Awareness / Kernel Module Debugging
The Linux* OS awareness pulldown menu allows visibility of all currently active kernel threads. It
also provides the ability to view a list of all currently loaded kernel modules with status
information and memory location of initialization methods and cleanup methods. Setting whether
to stop the target and commence debugging a kernel module on module load, initialization or
cleanup/exit allows to start debugging a kernel module and loading its symbolic information. You
can then set your breakpoints at the function entry points of the kernel module you want to
debug, release the target using the run command and trigger an event that will cause the
breakpoint to be hit to start your actual debug session.
You do not need to select kernel modules that are already loaded, but can add additional kernel
module names to the list of kernel modules that are monitored and have the debugger stop at
load, initialization or cleanup just as it would with the kernel modules that are already populated
in the OS awareness pulldown menu as they were loaded during the Linux* OS boot process.
To debug kernel modules the following steps additional to selecting or adding a kernel module
in the module list are necessary.
In a debugger script or in the debugger console window enter the following commands:
SET DIRECTORY "<kernel module path>"
This path setting is necessary to enable the automatic source and symbol info mapping upon
kernel module load as described above.
To use this feature for runtime loaded kernel module debugging you will need to have the kernel
module xdbntf.ko running and installed on the target device. The folder <INSTALLDIR>\kernel-modules\xdbntf contains code to generate a Linux* kernel module that
enables kernel module debugging with the Intel system debugger.
For generation simply transfer these files to your target system and invoke make. This will
generate the kernel object xdbntf.ko.
Intel® JTAG Debugger Installation Guide and Release Notes
13
To enable module debugging this object has to be loaded prior to starting the debugger via the
command insmod xdbntf.ko. After finishing the debug session, the module can be
unloaded with rmmod xdbntf.
6.4
Scripting Language
Create a batch file based on a rich set of powerful debugging script language commands and
execute it in non-interactive mode. Results can be logged and analyzed afterwards.
6.5
Page Translation Table
Instant and simple resolution and translation between physical and virtual address space.
6.6
Unload of Symbol Information
To unload a symbol file, open the Load dialog. Click the “Unload Symbol File” tab and select the
symbol file to be unloaded. This will remove the symbol information from the debug session.
Removing symbol information is useful in order to load different or new symbol information.
6.7
Power Events Handling
The debugger can properly handle externally controlled power events without needing to close
the debugger. If a target is reset or powered-off the debugger will identify the “Target power
loss.” Once power is restored the debugger will attempt to halt the target at the reset vector.
6.8
NAND Flashing support on Intel® Atom™ Processor CExxxx
The Intel® JTAG Debugger supports flashing eMMC NAND partitions on Intel® Atom™
Processor CE4xxx, CE5xxx and Intel® Puma6™ Media Gateway based reference platforms.
6.9
Supported Flash Types
Below is a brief description of the supported flash types for the specific target platforms:
Intel® Atom™ procesor E6xx

SPI-FLASH
Intel® Atom™ procesor N2xx/D2xxx

SPI-FLASH
Intel® Atom™ Processor CE4xxx,CE53xx

NOR Flash
Intel® JTAG Debugger Installation Guide and Release Notes
14



eMMC NAND Flash
eMMC Boot Partitions
eMMC User Partition
Intel® Puma6™ Media Gateway:




SPI-Flash
eMMC NAND Flash
eMMC Boot Partitions
eMMC User Partition
Intel® JTAG Debugger Installation Guide and Release Notes
15
7 Usage Notes
7.1
Starting the Debugger
To start the Intel® JTAG Debugger for Intel® Atom™ Processor change into the
C:\Program Files (x86)\Intel\System Studio 2013.0.xxx\
installation directory.
From there run the debugger launch shell script that best fits your host-target setup.
Below is a list of ready to go target connection configurations:
start_xdb_MCRG_Z500.bat
start_xdb_XDP3_Z500.bat
start_xdb_MCRG_E600.bat
start_xdb_XDP3_E600.bat
start_xdb_MCRG_N2000.bat
start_xdb_XDP3_N2000.bat
start_xdb_MCRG_CE4100.bat
start_xdb_XDP3_CE4100.bat
start_xdb_MCRG_CE4200.bat
start_xdb_XDP3_CE4200.bat
start_xdb_MCRG_CE5300.bat
start_xdb_XDP3_CE5300.bat
start_xdb_MCRG_CE2600.bat
start_xdb_XDP3_CE2600.bat
Intel® Atom™ Processor Z5xx
Macraigor* usb2Demon*
Intel® Atom™ Processor Z5xx
Intel® ITP-XDP
Intel® Atom™ Processor E6xx Macraigor* usb2Demon*
Intel® Atom™ Processor E6xx
Intel® ITP-XDP
Intel® Atom™ Processor N2xxx/D2xxx Macraigor*
usb2Demon*
Intel® Atom™ Processor N2xxx/D2xxx Intel® ITP-XDP
Intel® Atom™ Processor CE41xx Macraigor* usb2Demon*
Intel® Atom™ Processor CE41xx Intel® ITP-XDP
Intel® Atom™ Processor CE42xx Macraigor* usb2Demon*
Intel® Atom™ Processor CE42xx Intel® ITP-XDP
Intel® Atom™ Processor CE53xx Macraigor* usb2Demon*
Intel® Atom™ Processor CE53xx Intel® ITP-XDP
Intel® Puma6™ Media Gateway
Macraigor* usb2Demon*
Intel® Puma6™ Media Gateway
Intel® ITP-XDP
In the Windows* 7 start menu select
All Programs>Intel® System Studio 2013>Intel® JTAG Debugger Startup
Use the launch script entry for Intel ITP-XDP3 Probe or Macraigor Systems* usb2Demon*
Probe respectively.
7.2
Burning blank flash on Intel® Atom™ Processor CE5300 based platforms
Burning blank flash, requires that the SPI boot path is enabled and that the board is not
configured to boot from eMMC.
If the board is configured to boot from eMMC and the eMMC flash is empty than the target is
held in reset. This is indicated by an active yellow LED on the board. There are switches on
the board that are used to select the boot path, on the platform code-named “Mt. Carmel” Fab
B, these are switches SW3F1 switch 6 and switch 7. For SPI boot, switch 6 should be OFF and
switch 7 should be on. Please ensure that SPI boot is enabled if the a blank flash is to be
written.
7.3
eMMC Flash Recovery on Intel® Puma6™ Media Gateway
Intel® JTAG Debugger Installation Guide and Release Notes
16
For flashing a blank or corrupted eMMC flash on a platform based on the Intel® Puma6™ Media
Gateway we provide a special flash recovery script in conjunction with the Intel® JTAG
Debugger GUI Flash Memory Tool plugin.
Please follow the steps below to recover corrupted eMMC flash or write to blank eMMC flash
memory on a platform based on the Intel® Puma6™ Media Gateway:
1. Power cycle the board
Launch start_xdb_MCRG_CE2600_eMMC_Flash_Recovery.bat (Macraigor*
usb2Demon*) or start_xdb_XDP3_CE2600_eMMC_Flash_Recovery.bat
(Intel® ITP-XDP3) in a command line window from the
C:\Program Files (x86)\Intel\System Studio 2013.0.xxx\
directory.
2. Wait for the "Flash Recovery completed successfully!" message on the
command line and then exit.
3. If using the Macraigor* usb2demon, it is now recommended to power the target off and
back on again.
Launch start_xdb_MCRG_CE2600.bat in
C:\Program Files (x86)\Intel\System Studio 2013.0.xxx\
4. from a command line window Close assembler window
5. Open flash plugin
a. Select CE2600 in Board dropdown and eMMC-user in the Flash dropdown box
6. Set Data file to your CEFDK binary (ce2600.bin), set Offset to 0x80800 and select burn
7. Restart target and it should boot to CEFDK.
7.4
eMMC Flash on Intel® Atom™ Processor CE42xx and CE53xx
7.4.1 Partitions
There are 3 partitions defined on eMMC. Our flash tool is capable of programming each of the
3 partitions: boot1, boot2 and the user partition.
7.4.2 Addressing
Addressing space for each partition is independent. Therefore you should address the
beginning of each partition as address 0. Currently 32KB is the minimum write or read size that
we support.
7.4.3 Erasing
Block erasing is not implemented for this flash. eMMC flash can be written to without erasing
first. Therefore the only erase we support is on the entire partition.
Note- Currently “Verification” is not supported on eMMC flash. Please do a backup and manual
binary diff the two files.
Intel® JTAG Debugger Installation Guide and Release Notes
17
7.5
FTL Lite NAND Flash Programming on the Intel® Atom™ Processor
CE4100
Note- Please see the Platform Support Guide that came with your development kit for more
detailed information about programming the FTL Lite partition in the Intel® Atom™ Processor
CE4100 NAND flash.
The first 66 blocks of the flash memory is reserved as the FTL Lite partition. In this space each
block is written redundantly 8 times per DHG’s spec. In order to minimize user complexity, our
implementation of the FTL Lite partition accounts for these extra copies. However, by doing so,
this requires a minimum read or write size to be 1 block (128 KB).
7.5.1 Addressing
The conversion from FTL Lite partition block number to address is simple however not
straightforward. Since the redundant blocks are not addressable you must divide the block
number by 8 (number of redundant copies) than multiply by block size (128KB). Below is a
formula and table that converts some frequently used block locations. (As described in the
Platform Support Guide)
address = block # / 8 * 0x20000
Data
Block
#
Address
MBH and BBT
0
0x 0000
0000
CEFDK
8
0x 0002
0000
Redboot
40
0x 000A
0000
Platform parameters
48
0x 000C
0000
7.5.2 Backup
When doing a backup use the same addressing method described above. For the length
parameter, values must be a multiple of block size. Therefore 128KB (0x20000) is the minimum
read size. Also keep in mind that only 1 block will be read from the first 8 blocks of redundant
data. Our algorithm automatically accounts for the redundant block and will return only 1 of the
8 copies. Therefore reading 2 blocks at offset 0 will return block 0 and block 8.
Intel® JTAG Debugger Installation Guide and Release Notes
18
Warning- Reading back a recently erased block of data will sometimes crash the target. ECC
error logic isn’t in sync with erased blocks and therefore can cause the target to hang.
7.6
Enabling Run-Time Loaded Kernel Module Debugging
To use this feature for runtime loaded kernel module debugging you will need to have the kernel
module xdbntf.ko running and installed on the target device. The folder /kernelmodules/xdbntf contains code to generate a Linux kernel module that enables kernel module
debugging with the Intel system debugger.
For generation simply transfer these files to your target system and invoke make. This will
generate the kernel object xdbntf.ko.
The xdbntf Makefile has been modified to allow building within the CE Linux* environment, but
these modifications are not guaranteed to work with all CE Linux* flavors. Please see the
"read.me" in the xdbntf source solder for the latest info.
To enable module debugging this object has to be loaded prior to starting the debugger via the
command insmod xdbntf.ko. After finishing the debug session, the module can be unloaded
with rmmod xdbntf.
7.7
Unload of Symbol Information
To unload a symbol file, open the Load dialog. Click the “Unload Symbol File” tab and select the
symbol file to be unloaded. This will remove the symbol information from the debug session.
Removing symbol information is useful in order to load different or new symbol information.
8 Issues and Limitations
8.1
Known Issues and Limitations
8.1.1 Support for Intel® Atom™ processor bitfield editor register views
To receive information on how to access bitfield editor chipset register views for Intel® Atom™
Processors, please send an email to [email protected] for details.
8.1.2
Macraigor Systems* usb2Demon* does not support single stepping on Intel®
Puma6™ Media Gateway
The Macraigor Systems* usb2Demon* driver OCDRemote* 9.9-0 does currently not properly
support halt on breakpoint and single step on the Intel® Pume6™ Media Gateway. It is
recommended to use the Intel® ITP-XDP3 device until an updated OCDRemote distribution is
available.
Intel® JTAG Debugger Installation Guide and Release Notes
19
8.1.3 Locals Window updates can be slow
The local window updates may be slow in many cases where it is evaluating many large structs
or in scopes with many locals. If the slowness is noticed, it is recommended to close the locals
window.
8.1.4 Kernel Threads Window Population Slow
The Linux* OS awareness plug-in for the Intel® JTAG Debugger includes a Kernel Threads
Window, that displays all current kernel threads and information about their state. When the
Kernel Threads Window is opened it can take several seconds before the actual content is
displayed. The initial window content of “No data.” will disappear once kernel thread data is
available. This can take up to 20 seconds.
8.1.5 Debugger puts a Windows file system lock on symbol files
Currently when a Symbol file is loaded in the debugger a file system lock is placed on this file to
prevent other processes from deleting or modifying this file. If this lock is preventing you from
recompiling your program, simply use the Unload feature found in the Load Dialog. Unloading a
symbol file will release the file system lock and allow you to modify or delete the symbol file
without exiting the debugger.
8.1.6
Frequently loading and unloading debug symbols
Reloading symbol information numerous times can cause an “Out of Memory” exception and
crash the debugger. Due to memory leaks, reloading symbol information numerous times
without exiting the debugger can cause the debugger to use more than the maximum allotted
amount of memory. This will cause a fatal exception and will crash the debugger. A work around
for this issue is to exit the debugger if the memory usage becomes high.
8.1.7 Flash programming with empty flash parts (CE4200)
In order for the flash burning algorithm to execute the target must first be restarted and sitting at
the reset vector. This is normally handled by the flash plugin. However, on CE4200 boards that
do not have programmed flash parts, the platform’s reset does not function. Therefore, when
programming these boards, a manual reset is required.
To successfully burn flash on platforms with blank flash, a user should follow these steps:
1) Connect the debugger, and verify that the target is halted
2) Manually reset the target by pressing the reset button on the target
3) Verify that the EIP is not pointing at 0xFFF0
4) Open the flash plugin dialog and resume normal steps to program the flash.
Use of Macraigor* usb2Demon to debug Intel® Atom™ processor CE4xxx based
platforms may require board changes
On some of the Intel reference platforms for Intel® Atom™ processor CE4100 the RefDes serial
resistor R6D20 may need to be replaced with a 0 Ohm resistor. On some of the Intel reference
platforms for Intel(R) Atom(TM) processor CE4200 the RefDes serial resistor R4E5 may need to
8.1.8
Intel® JTAG Debugger Installation Guide and Release Notes
20
be replaced with a 0 Ohm resistor. Please refer to the board schematics and the platform design
guides for details.
8.1.9 Older Macraigor* usb2Demon 60pin connector headers
The reference voltage and signal voltage pins on Macraigor* usb2Demon 60pin connector
headers from prior to September 2010 are connected. Since those two voltages differ from each
other on the Intel® Atom™ Processor E600 reference platform it is strongly recommended to
only use recently purchased Macraigor* usb2Demon 60pin connector headers with these
platforms. Not following this recommendation can damage the reference platform.
8.1.10 Backup of large flash partitions may fail
It is recommended to avoid using the flash writer plug-in to backup large flash partitions
(>200Mb) from the Intel® Atom™ Processor onto the workstation.
8.1.11 Verification of flash content on Intel® Atom™ processor E6xx based platform
Verifying flash content may only be possible immediately after writing it. When the system
boots, it might modify the flash content (e.g. saving changed settings). When the flash content
will be compared to the original file that got written to the flash, the verification will show
differences.
8.1.12 Function and file information not listed for watchpoints in breakpoint window
When setting a data breakpoint (watchpoint) the breakpoint listing in the breakpoint window
does not contain file and function information for the data breakpoint.
8.1.13 Target doesn't boot when Macraigor* usb2Demon* JTAG device is not initialized
If the Macraigor* probe is connected to the host system the first time, it doesn't get initialized
until a debugger is using the probe. Without initialization the probe, the JTAG pins are in an
undefined state and can prevent the target system from booting. The might lead to unstable
behavior on the target including failing boot sequence. After the debugger has initialized the
probe the target system should boot without problems.
This does not affect the XDP3 connection. XDP3 probe is automatically initialized when it gets
plugged into the host system.
8.1.14 Local variables and evaluation windows do not display multi-dimensional arrays
correctly
Multi-dimensional arrays are displayed as vectors in the debugger's local variables window and
evaluations window suppressing one dimension of the array.
8.1.15 Evaluation window for global variables may be missing type information
When evaluating a global variable in a debugger evaluation window the variable name and it’s
value are displayed, but type information may not be displayed.
Intel® JTAG Debugger Installation Guide and Release Notes
21
8.1.16 Writing to a non-writable vector registers may incorrectly update register value
display
In the vector register window it is possible that a write to a vector register seems to have been
successful, when a new value was entered from within said window, despite the register being
non-writable at the time and not actually having been updated.
8.1.17 With Intel® Hyper-Threading Technology disabled in BIOS debugger SMP
configuration must be disabled as well when using Macraigor Systems*
usb2Demon*
When Intel® Hyper-Threading Technology is disabled in the BIOS, the debugger SMP
configuration must be turned off as well. The Macraigor System* driver interface returns an
error condition on disabled processor cores that is indistinguishable from other error conditions
for the debugger. If SMP support is disabled, the debugger will not try to access the second
hyper-thread and thus the error condition will not occur.
To disable SMP support please edit xdb.sh in the /opt/intel/System Studio
2013.0.xxx/debugger/xdb directory and change -tgttype 'JTAG IA SMP' to -tgttype 'JTAG IA' in
the java launch command line.
With current Macraigor Systems* drivers the above mentioned error condition may rarely also
occur if on an SMP enabled system one hyper-thread is halted during debugger memory
read/write operations.
8.1.18 Root or Sudo Access required for JTAG Debugger Install
To be able to install the Intel(R) JTAG Debugger it is necessary to either launch the tool suite
installation script install.sh with root privileges or to select "install as root" or "install as root using
sudo" during the Intel® System Studio installation process. Installation without root privileges
will not be successful.
8.1.19 Memory Writes to Un-Initialized Memory
Memory writes to un-initialized or read-only memory (this includes setting software breakpoints
or accessing memory mapped registers) can lead to a crash of the target or a loss of the target
control. The debugger will not prevent these memory accesses when requested by the user
(e.g. changing instructions in the disassembly window).
8.1.20 Flash Writer disables pre-existing Breakpoints
Flashing the BIOS will disable all code breakpoints and data breakpoints you may have had set
prior to using the flash writer.
8.1.21 Master Flash Header Read/Write not supported for Intel® Atom™ Processor
CE4200
On the Intel® Atom™ Processor CE4200 the Master Flash Header serves as a road map for the
contents of flash that are processed by security and host firmware. It contains the location and
Intel® JTAG Debugger Installation Guide and Release Notes
22
size of each element in the flash, as well as a list of host firmware images that the security
processor will attempt to boot. Currently the flash writer plug-in for the Intel® JTAG Debugger
does not support writing or modifying the Master Flash Header.
It is of course possible to use the terminal Master Flash Header commands mfhlist mfhinfo and
mfhinit in conjunction with the Intel® JTAG Debugger flash writer plug-in.
mfhlist provides the location of the Master Flash Header entries and where the current platform
boot configuration expects the various flash images to be put. It’s output can be used as a
guidance for setting the start address when using the flash writer plug-in.
For NOR Non-Trusted Boot and NAND/eMMC Non-Trusted boot can be configured such that
target boot is possible even if no Master Flash Header is present on the platform.
eMMC Trusted Boot does require the presence of a Master Flash Header and requires that the
actual memory layout does match its contents.
Please read the Platform User Guide closely for further details on the Master Flash Header and
its usage.
9 Attributions
Portions of this software were originally based on the following:
- software copyright (c) 1999, IBM Corporation., http://www.ibm.com.
- software copyright (c) 1999, Sun Microsystems., http://www.sun.com.
- the W3C consortium (http://www.w3c.org) ,
- the SAX project (http://www.saxproject.org)
- voluntary contributions made by Paul Eng on behalf of the
Apache Software Foundation that were originally developed at iClick, Inc.,
software copyright (c) 1999.
This product includes updcrc macro,
Satchell Evaluations and Chuck Forsberg.
Copyright (C) 1986 Stephen Satchell.
This product includes software developed by the MX4J project
(http://mx4j.sourceforge.net).
This product includes ICU 1.8.1 and later.
Copyright (c) 1995-2006 International Business Machines Corporation and others.
Portions copyright (c) 1997-2007 Cypress Semiconductor Corporation.
All rights reserved.
This product includes XORP.
Copyright (c) 2001-2004 International Computer Science Institute
Intel® JTAG Debugger Installation Guide and Release Notes
23
This product includes software licensed from Macraigor Systems, LLC.
Copyright (c) 2004-2009, Macraigor Systems LLC. All rights reserved.
This product includes software from the book
"Linux Device Drivers" by Alessandro Rubini and Jonathan Corbet,
published by O'Reilly & Associates.
This product includes hashtab.c.
Bob Jenkins, 1996.
10 Disclaimer and Legal Information
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL
PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO
ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT
AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS,
INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR
IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS
INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR
PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR
OTHER INTELLECTUAL PROPERTY RIGHT.
A "Mission Critical Application" is any application in which failure of the Intel Product could
result, directly or indirectly, in personal injury or death. SHOULD YOU PURCHASE OR USE
INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL
INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND
AFFILIATES, AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS
AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE
ATTORNEYS' FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, ANY CLAIM OF
PRODUCT LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF
SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS
SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF
THE INTEL PRODUCT OR ANY OF ITS PARTS.
Intel may make changes to specifications and product descriptions at any time, without notice.
Designers must not rely on the absence or characteristics of any features or instructions marked
"reserved" or "undefined". Intel reserves these for future definition and shall have no
responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.
The information here is subject to change without notice. Do not finalize a design with this
information.
The products described in this document may contain design defects or errors known as errata
which may cause the product to deviate from published specifications. Current characterized
Intel® JTAG Debugger Installation Guide and Release Notes
24
errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and
before placing your product order.
Copies of documents which have an order number and are referenced in this document, or
other Intel literature, may be obtained by calling 1-800-548-4725, or go to:
http://www.intel.com/design/literature.htm
MPEG-1, MPEG-2, MPEG-4, H.261, H.263, H.264, MP3, DV, VC-1, MJPEG, AC3, AAC, G.711,
G.722, G.722.1, G.722.2, AMRWB, Extended AMRWB (AMRWB+), G.167, G.168, G.169,
G.723.1, G.726, G.728, G.729, G.729.1, GSM AMR, GSM FR are international standards
promoted by ISO, IEC, ITU, ETSI, 3GPP and other organizations. Implementations of these
standards, or the standard enabled platforms may require licenses from various entities,
including Intel Corporation.
BlueMoon, BunnyPeople, Celeron, Celeron Inside, Centrino, Centrino Inside, Cilk, Core Inside,
E-GOLD, Flexpipe, i960, Intel, the Intel logo, Intel AppUp, Intel Atom, Intel Atom Inside, Intel
Core, Intel Inside, Intel Insider, the Intel Inside logo, Intel NetBurst, Intel NetMerge, Intel
NetStructure, Intel SingleDriver, Intel SpeedStep, Intel Sponsors of Tomorrow., the Intel
Sponsors of Tomorrow. logo, Intel StrataFlash, Intel vPro, Intel XScale, InTru, the InTru logo,
the InTru Inside logo, InTru soundmark, Itanium, Itanium Inside, MCS, MMX, Moblin, Pentium,
Pentium Inside, Puma, skoool, the skoool logo, SMARTi, Sound Mark, Stay With It, The
Creators Project, The Journey Inside, Thunderbolt, Ultrabook, vPro Inside, VTune, Xeon, Xeon
Inside, X-GOLD, XMM, X-PMU and XPOSYS are trademarks of Intel Corporation in the U.S.
and/or other countries.
* Other names and brands may be claimed as the property of others.
Microsoft, Windows, Visual Studio, Visual C++, and the Windows logo are trademarks, or
registered trademarks of Microsoft Corporation in the United States and/or other countries.
Java is a registered trademark of Oracle and/or its affiliates.
Copyright (C) 2008–2013, Intel Corporation. All rights reserved.
Intel® JTAG Debugger Installation Guide and Release Notes
25
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement