Debug Solutions User Forum

Trouble debugging Intel Quark in Galileo with ITP-XDP 3BR and Intel System Debugger

I can't start debugging the Intel Quark target in Galileo board.

1.) I am using the "2015 Products.bat" file to start the debugger.

2.) Inside the debugger interface I use the "Intel Quark SoC x1000-60-pin XDP (Clanton)" option. No additional parameters. I know the Galileo can't work with the 60-pin interface right out of the box so I am using an adapter.

3.) This is the way the hardware is setup:

Intel System Studio 2015 For Windows

Is it possible to do XDB + JTAG debugging for the Intel Quark on Intel System Studio 2015 For Windows?

I have checked the product specifications and the only version that lists JTAG as part of the package is the Ultimate Linux version of Intel System Studio 2015.

Any help and information will be greatly appreciated.

Thank you beforehand.


Fortran PARAMETERs shown twice in debugger

When a Fortran program containing PARAMETER declarations is compiled with the /Zi /debug-parameters:used options, the parameters are displayed twice in the Locals window. Here is example code:

! test viewing PARAMETER values in debugger
program tst
implicit none
integer, parameter :: N=10,M=20,L=M+N
integer :: iv(M-N),i
do i=1,size(iv)
end do
end program

I have attached a screenshot of the duplicated display of the parameters in the debugger.

Intel System Studio 2015 (Beta) Quark JTAG access to MSR

Is it possible to gain access to the Quark's Model-Specific Registers (MSR) via JTAG using the XDB?

If it is possible, in which way can I gain access to these registers?

The Quark Debug Operations Manual suggests this [Direct quote form the Quark Debug Ops Manual, Section 5.6.11]:

Intel Sytem Studio 2015 (beta), OpenOCD Quark Real Mode Debug

Is it possible to debug the Quark SoC with Intel System Studio 2015 (Beta) and an OpenOCD probe? 

The processor always stops at the address 0x0008:0xFFFFFA72 when following the steps state below. When the debugger halts the processor at address: 0x0008:FFFFFA72, the processor is already working in protected mode, so my technique of rewriting the EIP to go back to the address in memory pointed by the jmp instruction (see the steps below) at the reset vector is useless.

Is there a way of debugging in real mode or stopping the processor before it enters protected mode?

How to debug in Intel Parallel Studio XE Composer Edition for Fortran and C++ Windows* - Named-user Commercial (ESD)


I have recently purchase "Intel Parallel Studio XE Composer Edition for Fortran and C++ Windows* - Named-user Commercial (ESD)".

While i am installing i can see that the package "Intel Debugger Extension 7.7-8.0" is included (Marked yellow in first picture).

But at the very next step it shows the warning related to debugging package( shown in the second picture).

XDP to 10Pin JTAG Adapter Pins

Does this adapter ( XDP to 10Pin JTAG Adapter Pins makes available the PRDY# and PREQ# pins that are necessary for debugging the Quark processor in reset break mode?

Since this adapter converts the ITP-XDP3 connector to the standard 10-pin ARM JTAG connector, these pins may not be available at the 10-pin side, but are they available for connection somewhere on the board?

Debug Problem


On previous, I have been used Visual Studio 2008 with Intel visual fortran 11.1.3463.2008 and move to Visual Studio 2013 and Intel Parallel Studio XE 2015 Composer  edition for fortran windows  on my 64 bit windows 7 computer. My problem is that in the debug mode the program doesn't move step by step as i shown on the figure and some time does not show the values of the variables. 

Run To Cursor at the first step :

S’abonner à Debug Solutions User Forum