Created
February 16, 2016 21:57
-
-
Save caillou/6fb29e25e814896d9732 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vagrant@vagrant-ubuntu-trusty-64:/vagrant/eurorack-modules$ make -f peaks/makefile upload | |
openocd -f stmlib/programming/jtag/interface_arm-usb-ocd-h.cfg -f stmlib/programming/jtag/stm32f10x_jtag.cfg -f stmlib/programming/jtag/prelude_f10x.cfg -f stmlib/programming/jtag/erase_f10x.cfg -c "flash write_bank 0 build/peaks/peaks_bootloader_combo.bin 0x0" -c "verify_image build/peaks/peaks_bootloader_combo.bin" -f stmlib/programming/jtag/postlude.cfg || openocd -f stmlib/programming/jtag/interface_arm-usb-ocd-h.cfg -f stmlib/programming/jtag/stm32f10x_jtag.cfg -f stmlib/programming/jtag/prelude_f10x.cfg -f stmlib/programming/jtag/erase_f10x.cfg -c "flash write_bank 0 build/peaks/peaks_bootloader_combo.bin 0x0" -c "verify_image build/peaks/peaks_bootloader_combo.bin" -f stmlib/programming/jtag/postlude.cfg | |
Open On-Chip Debugger 0.9.0 (2016-02-16-21:26) | |
Licensed under GNU GPL v2 | |
For bug reports, read | |
http://openocd.org/doc/doxygen/bugs.html | |
Info : only one transport option; autoselect 'jtag' | |
adapter speed: 1000 kHz | |
adapter_nsrst_delay: 200 | |
jtag_ntrst_delay: 200 | |
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst | |
Warn : Using DEPRECATED interface driver 'ft2232' | |
Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/... | |
Info : max TCK change to: 30000 kHz | |
Info : clock speed 1000 kHz | |
Error: JTAG scan chain interrogation failed: all zeroes | |
Error: Check JTAG interface, timings, target power, etc. | |
Error: Trying to use configured scan chain anyway... | |
Error: stm32.cpu: IR capture error; saw 0x00 not 0x01 | |
Warn : Bypassing JTAG setup events due to errors | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Error: Target not examined yet | |
Open On-Chip Debugger 0.9.0 (2016-02-16-21:26) | |
Licensed under GNU GPL v2 | |
For bug reports, read | |
http://openocd.org/doc/doxygen/bugs.html | |
Info : only one transport option; autoselect 'jtag' | |
adapter speed: 1000 kHz | |
adapter_nsrst_delay: 200 | |
jtag_ntrst_delay: 200 | |
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst | |
Warn : Using DEPRECATED interface driver 'ft2232' | |
Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/... | |
Info : max TCK change to: 30000 kHz | |
Info : clock speed 1000 kHz | |
Error: JTAG scan chain interrogation failed: all zeroes | |
Error: Check JTAG interface, timings, target power, etc. | |
Error: Trying to use configured scan chain anyway... | |
Error: stm32.cpu: IR capture error; saw 0x00 not 0x01 | |
Warn : Bypassing JTAG setup events due to errors | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Warn : Invalid ACK 0 in JTAG-DP transaction | |
Error: Target not examined yet | |
make: *** [upload_combo_jtag] Error 1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment