| As of August 2020 the site you are on (wiki.newae.com) is deprecated, and content is now at rtfm.newae.com. |
Difference between revisions of "CW308T-D2000"
(→How to flash D2000 board using OpenOCD) |
|||
| Line 24: | Line 24: | ||
=== How to flash D2000 board using OpenOCD === | === How to flash D2000 board using OpenOCD === | ||
| − | We'll modify the provided scripts from the Intel ISSM distribution (compiler etc for D2000). | + | We'll modify the provided scripts from the Intel ISSM distribution (compiler etc for D2000). Start a Windows command prompt and run the following commands: |
| − | + | ||
| − | Start a Windows command prompt and run the following commands: | + | |
C:\IntelSWTools\ISSM_2016.0.027\issm_env.bat | C:\IntelSWTools\ISSM_2016.0.027\issm_env.bat | ||
| Line 32: | Line 30: | ||
bin\openocd.exe -f scripts\interface\ftdi\olimex-arm-usb-ocd-h.cfg -f scripts\board\quark_d2000.cfg | bin\openocd.exe -f scripts\interface\ftdi\olimex-arm-usb-ocd-h.cfg -f scripts\board\quark_d2000.cfg | ||
| − | This should result in an output like the following: | + | Note we specify two script files - the first had the JTAG connection (the olimex-arm-usb-ocd-h.cfg), the second had the D2000. This should result in an output like the following: |
Open On-Chip Debugger 0.8.0-dev-g7845893 (2015-11-26-18:12) | Open On-Chip Debugger 0.8.0-dev-g7845893 (2015-11-26-18:12) | ||
Revision as of 07:35, 31 October 2017
| CW308T-D2000 | |
|---|---|
 | |
| Target Device | Intel Quark D2000 |
| Target Architecture | x86 |
| Hardware Crypto | No |
| Design Files | OSH Park PCBs |
The D2000 target is a bit of an oddball. It's an x86 target, but is really a microcontroller (internal flash etc).
Programming
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 Olimex ARM-USB-OCD-H as is available from suppliers such as Mouser and Digi-Key (mouser link provided).
How to flash D2000 board using OpenOCD
We'll modify the provided scripts from the Intel ISSM distribution (compiler etc for D2000). Start a Windows command prompt and run the following commands:
C:\IntelSWTools\ISSM_2016.0.027\issm_env.bat cd %ISSM_DEBUGGER_ROOT%\openocd bin\openocd.exe -f scripts\interface\ftdi\olimex-arm-usb-ocd-h.cfg -f scripts\board\quark_d2000.cfg
Note we specify two script files - the first had the JTAG connection (the olimex-arm-usb-ocd-h.cfg), the second had the D2000. This should result in an output like the following:
Open On-Chip Debugger 0.8.0-dev-g7845893 (2015-11-26-18:12)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
adapter speed: 1000 kHz
trst_only separate trst_push_pull
flash_rom
Info : clock speed 1000 kHz
Info : JTAG tap: quark_d2000.cltap tap/device found: 0x0e786013 (mfg: 0x009, part: 0xe786, ver: 0x0)
Enabling lmt core tap
Info : JTAG tap: quark_d2000.lmt enabled
At this point it will hold, waiting for new commands. Open a second command prompt, and run:
C:\IntelSWTools\ISSM_2016.0.027\issm_env.bat gdb
From within this GDB console, you can run the following:
target remote :3333 monitor clk32M 500 monitor load_image C:\\chipwhisperer\\hardware\\victims\\firmware\\intel_quark\\quark_d2000_rom.bin 0x0 monitor load_image C:\\chipwhisperer\\hardware\\victims\\firmware\\intel_quark\\simpleserial_example\\release\\quark_d2000\\x86\\bin\\simpleserial_aes.bin 0x00180000
The first load_image is used for the ROM image. This may not be needed as has normally been done already. However you'll have to reload the application any time you wish to reprogram it.
Schematic
See GIT Repo for PDF of schematic.
Board Layout
See GIT Repo for gerber files.
