CW308T-D2000 - Revision history

Coflynn: Replaced content with "== Page Moved == See [https://rtfm.newae.com/Targets/UFO%20Targets/CW308T-D2000/ NewAE RTFM Page] which is now built from the [https://github.com/newaetech/chipwhisperer-..."

2020-07-29T19:32:52Z

Replaced content with "== Page Moved == See [https://rtfm.newae.com/Targets/UFO%20Targets/CW308T-D2000/ NewAE RTFM Page] which is now built from the [https://github.com/newaetech/chipwhisperer-..."

Show changes

Adewar: /* Building Firmware */

2018-11-06T17:11:22Z

‎Building Firmware

Adewar at 17:10, 6 November 2018

2018-11-06T17:10:55Z

Coflynn at 03:45, 12 July 2018

2018-07-12T03:45:04Z

Fheubach at 18:21, 1 May 2018

2018-05-01T18:21:20Z

Coflynn at 12:52, 5 April 2018

2018-04-05T12:52:18Z

Coflynn: /* Programming */

2018-02-23T04:37:33Z

‎Programming

Coflynn: /* Programming */

2018-02-23T04:36:55Z

‎Programming

Coflynn: /* OpenOCD Board Setup */

2018-02-22T14:45:15Z

‎OpenOCD Board Setup

Coflynn: /* OpenOCD Board Setup */

2018-02-22T14:44:48Z

‎OpenOCD Board Setup

@@ Line 65: / Line 65: @@
 === Troubleshooting ===
 * No such file or directory when building on Windows
-** This is usually caused by the default make directory command (<code>md</code>) not working. First, ensure that you have <code>mkdir</code> and cp on your system by opening <code>cmd</code> and running them. Then open <code>hardware/victims/firmware/intel_quark/qmsi/base.mk</code> and change:
+** This is usually caused by the default make directory command (<code>md</code>) not working. First, ensure that you have <code>mkdir</code> and cp on your system by opening <code>cmd</code> and running them. Then open <code>hardware/victims/firmware/intel_quark/qmsi/base.mk</code> and change:<syntaxhighlight lang="makefile">
-** <syntaxhighlight lang="makefile">
 # Any other version of Windows
 mkdir = @md $(subst /,\,$(1)) > nul 2>&1 || exit 0
 copy = @copy $(subst /,\,$(1)) $(subst /,\,$(2)) > nul 2>&1 || exit 0
-</syntaxhighlight>to:
+</syntaxhighlight>to:<syntaxhighlight lang="makefile">
-** <syntaxhighlight lang="makefile">
 # Any other version of Windows
 mkdir = @mkdir -p $(1) || exit 0

@@ Line 55: / Line 55: @@
 else:
      raise IOError("Did not detect external clock from D2000. Confirm jumpers and rerun, or increase delay before sample."
 </syntaxhighlight>

@@ Line 189: / Line 189: @@
 == Schematic ==
-See GIT Repo for PDF of schematic.
+See GIT Repo for PDF of schematic. Note there is a new "03C" rev that changes the shunt resistor (R1) to a 1-ohm resistor. This results in a much more reliable device, as the original 10-ohm shunt caused occasional crashes. If you are using an older revision device, you can mount a shunt/jumper between "SH-" and "SH+" on the UFO board to achieve a similar effect.
 [[File:CW308T-D2000-02_schematic.png|1000px]]

@@ Line 196: / Line 196: @@
 See GIT Repo for gerber files.
 {{Template:Hardware}}
 [[Category:CW308 Targets]]

← Older revision		Revision as of 12:52, 5 April 2018
Line 14:		Line 14:
	}}		}}

−	~~[[File:d2000_topdown.jpg\|400px]]~~

	The D2000 target is a bit of an oddball. It's an x86 target, but is really a microcontroller (internal flash etc).		The D2000 target is a bit of an oddball. It's an x86 target, but is really a microcontroller (internal flash etc).

@@ Line 62: / Line 62: @@
 An external programmer is needed for this target. The Quark D2000 dev-board can be used with jumper wires, or a standard OpenOCD programmer can be used. The suggested programmer is the [https://mouser.com/ProductDetail/Olimex-Ltd/ARM-USB-OCD-H Olimex ARM-USB-OCD-H] as is available from suppliers such as Mouser and Digi-Key (mouser link provided).
-{{Warningbox|The D2000 chips have a weird combination of what they call "ROM" (actually not ROM remotely) and application space. When building you normally use the D2000 ROM provided (or can build your own). However you only need to program this section the first time - it is not recommended to reprogram it unless needed, since it is possible to brick the D2000 with a corrupt ROM load.}}
+{{Warningbox|The D2000 chips have a weird combination of what they call "ROM" (actually not ROM remotely) and application space. When building you normally use the D2000 ROM provided (or can build your own). However you only need to program this section the first time - it is not recommended to reprogram it unless needed, since it is possible to brick the D2000 with a corrupt ROM load.
 === OpenOCD Board Setup ===

← Older revision		Revision as of 04:36, 23 February 2018
Line 61:		Line 61:

	An external programmer is needed for this target. The Quark D2000 dev-board can be used with jumper wires, or a standard OpenOCD programmer can be used. The suggested programmer is the [https://mouser.com/ProductDetail/Olimex-Ltd/ARM-USB-OCD-H Olimex ARM-USB-OCD-H] as is available from suppliers such as Mouser and Digi-Key (mouser link provided).		An external programmer is needed for this target. The Quark D2000 dev-board can be used with jumper wires, or a standard OpenOCD programmer can be used. The suggested programmer is the [https://mouser.com/ProductDetail/Olimex-Ltd/ARM-USB-OCD-H Olimex ARM-USB-OCD-H] as is available from suppliers such as Mouser and Digi-Key (mouser link provided).
		+
		+	{{Warningbox\|The D2000 chips have a weird combination of what they call "ROM" (actually not ROM remotely) and application space. When building you normally use the D2000 ROM provided (or can build your own). However you only need to program this section the first time - it is not recommended to reprogram it unless needed, since it is possible to brick the D2000 with a corrupt ROM load.}}

	=== OpenOCD Board Setup ===		=== OpenOCD Board Setup ===

@@ Line 64: / Line 64: @@
 === OpenOCD Board Setup ===
-If using OpenOCD either stand-alone or as part of Intel ISSM, you'll need to define a new board file. The file is based on <code>scripts\board\quark_d2000.cfg</code> found in the following directory: <code>C:\IntelSWTools\ISSM_2016.0.027\tools\debugger\openocd\scripts\board</code>;
+If using OpenOCD either stand-alone or as part of Intel ISSM, you'll need to define a new board file. The file is based on <code>scripts\board\quark_d2000.cfg</code> found in the following directory: <code>C:\IntelSWTools\ISSM_2016.0.027\tools\debugger\openocd\scripts\board</code> (adjust for version number changes).
- (adjust for version number changes).
 You will find a line like the following in the original file:

@@ Line 64: / Line 64: @@
 === OpenOCD Board Setup ===
-If using OpenOCD either stand-alone or as part of Intel ISSM, you'll need to define a new board file. The file is based on ''scripts\board\quark_d2000.cfg'' found in the following directory: ''C:\IntelSWTools\ISSM_2016.0.027\tools\debugger\openocd\scripts\board';
+If using OpenOCD either stand-alone or as part of Intel ISSM, you'll need to define a new board file. The file is based on <code>scripts\board\quark_d2000.cfg</code> found in the following directory: <code>C:\IntelSWTools\ISSM_2016.0.027\tools\debugger\openocd\scripts\board</code>;
   (adjust for version number changes).
@@ Line 77: / Line 77: @@
    adapter_khz 125
-Save this file as ''quark_d2000_ufo.cfg''.
+Save this file as <code>quark_d2000_ufo.cfg</code>.
 === How to flash D2000 board using OpenOCD ===