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]:
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?
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).
Does this adapter ( XDP to 10Pin JTAG Adapter Pins https://designintools.intel.com/product_p/itpxdp10pinjtagquark.htm) 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?
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 :
I want to be able to debug the Quark SoC on the Intel Galileo Board from the reset vector (or close to it).
I know that OpenOCD can't do a direct reset/break debug since the ARM JTAG interface on the board doesn't include the two necessary pins for such procedure.
I want to start developing code for the Quark processor. I have an Intel Galileo Board that I have started working with.
I would like to know if there is a way to obtain the Intel ITP-XDP3 JTAG probe as an educator. My budget as an educator is limited.
It is a high end probe, but it seems to be the only probe available to debug the Quark's UEFI or any code from the reset vector on which is what I want to do.
the latest compiler version comes with gdb-ia or gdb-mic. Obviously idb has been dropped. This is not unexpected (see https://software.intel.com/en-us/forums/topic/326535).
But: Intels version of gdb (gdb-ia) seems to provide only a minimalistic text console interface. Not even a TUI like gdb.
Or am I missing something?
Trying to start up idb I get the crash below.
Probably hard to debug without the executable, but I can't send it without permission, so let me know if you need it and I'll see what I can do.