- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I imported the power example program from qmsi-master and ran it.
I receive terminal outputs:
"Low power mode example.
CPU Halt.
CPU Halt wakeup.
Go to sleep.
Wake up from sleep.
Go to deep sleep."
I am unable to exit from deep sleep though using the comparator pin 6 and I am also unable to load other programs because I think OpenOCD is unable to communicate with the D2000 due to it being in deep sleep mode.
How can I resolve this?
Can I erase the flash program memory without using OpenOCD?
I tried updating the target ROM but received the following popup window:
"
Could not update the ROM. Setup target failed.
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 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
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: quark_d2000.cltap: IR capture error; saw 0xff not 0x1
Warn : Bypassing JTAG setup events due to errors
Setup clock
adapter speed: 3 kHz
Error: Target not examined yet
Runtime Error: scripts/board/quark_d2000_onboard.cfg:83:
in procedure 'flash_rom'
in procedure 'clk32M' called at file "scripts/board/quark_d2000_onboard.cfg", line 141
in procedure 'mww' called at file "scripts/board/quark_d2000_onboard.cfg", line 83
"
I tried flashing the bsp_hello_world example but an error window popped up:
"Error in final launch sequence
Failed to execute MI command:
Error message from debugger back end:
Load failed
Load failed"
The OpenOCD Session states:
"
Command: C:\IntelSWTools\ISSM_2016.0.027\tools\debugger\openocd\bin\openocd.exe -f C:\IntelSWTools\ISSM_2016.0.027\tools\debugger\openocd\scripts\board\quark_d2000_onboard.cfg
>>> OpenOCD console:
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 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
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: quark_d2000.cltap: IR capture error; saw 0xff not 0x1
Warn : Bypassing JTAG setup events due to errors
Info : accepting 'gdb' connection from 3333
Error: Target not examined yet
in procedure 'halt'
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target running, halt it first
Error: target runnin...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi ,
If you are using the 'power' example provided without any changes you should be able to wake from deep sleep by connecting Pin 6 - this is marked as Analog Pin5 (A5) on the CRB - to GND.
Make sure this is connected before you reset the board. When the serial output shows 'Go to deep sleep' unground the pin and you should see it wake up.
Low power mode example.
CPU Halt.
CPU Halt wakeup.
Go to sleep.
Wake up from sleep.
Go to deep sleep.
Wake up from deep sleep.
However if this does not work you can recover the board by Grounding Digital Pin 0 and re-flashing the ROM (this process should work in most cases where you loose JTAG access)
- Connect a jumper wire from Digital Pin 0 to GND
- Reset the board (Power off/on)
- From the ISSM menu select 'Update Target ROM'
regards,
Michelle.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi ,
If you are using the 'power' example provided without any changes you should be able to wake from deep sleep by connecting Pin 6 - this is marked as Analog Pin5 (A5) on the CRB - to GND.
Make sure this is connected before you reset the board. When the serial output shows 'Go to deep sleep' unground the pin and you should see it wake up.
Low power mode example.
CPU Halt.
CPU Halt wakeup.
Go to sleep.
Wake up from sleep.
Go to deep sleep.
Wake up from deep sleep.
However if this does not work you can recover the board by Grounding Digital Pin 0 and re-flashing the ROM (this process should work in most cases where you loose JTAG access)
- Connect a jumper wire from Digital Pin 0 to GND
- Reset the board (Power off/on)
- From the ISSM menu select 'Update Target ROM'
regards,
Michelle.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi Michelle!
Thanks for the help knowing how to use the power example! It worked and it's also really nice to know how to update ROM if I ever get into a bind again.
Best regards,
JD

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page