Problem uploading firmware with Olimex


#1

Hi.

I already install the Vagrant environment in my computer and I can compile perfectly but when I try to upload the firmware using the recommended Olimex programmer I have the following error.

Open On-Chip Debugger 0.9.0 (2015-06-12-21:39)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Error: The specified debug interface was not found (ft2232)
The following debug interfaces are available:
1: ftdi
2: usb_blaster
3: usbprog
4: jlink
5: vsllink
6: rlink
7: ulink
8: arm-jtag-ew
9: hla
10: osbdm
11: opendous
12: aice
13: cmsis-dap

make: ***** [upload_combo_jtag] Error 1

Any idea??

Thanks!!


#2

Can you post the command that resulted in this error message.

This looks like a discrepancy between the version of openocd installed (0.9.0) and the use of older programming scripts. It would seem that your version of stmlib is not up to date.


#3

Here is.

vagrant@vagrant-ubuntu-trusty-64:/vagrant/eurorack-modules$ make -f rings/makefile upload_combo_jtag
openocd -f stmlib/programming/jtag/interface_arm-usb-ocd-h.cfg -f stmlib/programming/jtag/stm32f4xx_jtag.cfg -f stmlib/programming/jtag/prelude_f4xx.cfg  -f stmlib/programming/jtag/erase_f4xx.cfg -c "flash write_bank 0 build/rings/rings_bootloader_combo.bin 0x0" -c "verify_image build/rings/rings_bootloader_combo.bin" -f stmlib/programming/jtag/postlude.cfg || openocd -f stmlib/programming/jtag/interface_arm-usb-ocd-h.cfg -f stmlib/programming/jtag/stm32f4xx_jtag.cfg -f stmlib/programming/jtag/prelude_f4xx.cfg  -f stmlib/programming/jtag/erase_f4xx.cfg -c "flash write_bank 0 build/rings/rings_bootloader_combo.bin 0x0" -c "verify_image build/rings/rings_bootloader_combo.bin" -f stmlib/programming/jtag/postlude.cfg
Open On-Chip Debugger 0.9.0 (2018-06-28-23:51)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Error: The specified debug interface was not found (ft2232)
The following debug interfaces are available:
1: ftdi
2: usb_blaster
3: usbprog
4: jlink
5: vsllink
6: rlink
7: ulink
8: arm-jtag-ew
9: hla
10: osbdm
11: opendous
12: aice

Open On-Chip Debugger 0.9.0 (2018-06-28-23:51)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Error: The specified debug interface was not found (ft2232)
The following debug interfaces are available:
1: ftdi
2: usb_blaster
3: usbprog
4: jlink
5: vsllink
6: rlink
7: ulink
8: arm-jtag-ew
9: hla
10: osbdm
11: opendous
12: aice

make: *** [upload_combo_jtag] Error 1

Thanks


#4

Yeah, you’re using an old version of stmlib. It uses custom scripts for interfaces and targets (stmlib/programming/jtag/interface_arm-usb-ocd-h.cfg) which no longer work with the most recent versions of openocd. You need to run git submodule update to retrieve the latest version of stmlib.


#5

Hi again.

I did it and now I have the following error.

vagrant@vagrant-ubuntu-trusty-64:/vagrant/eurorack-modules$ git submodule update
vagrant@vagrant-ubuntu-trusty-64:/vagrant/eurorack-modules$ make -f rings/makefile upload_combo_jtag
openocd -f interface/stlink-v2.cfg -f target/stm32f4x.cfg -c "init" -c "halt" -c "sleep 200" \
				-f stmlib/programming/jtag/erase_f4xx.cfg \
				-c "flash write_bank 0 build/rings/rings_bootloader_combo.bin 0x0" \
				-c "verify_image build/rings/rings_bootloader_combo.bin" \
				-c "sleep 200" -c "reset run" -c "shutdown"
Open On-Chip Debugger 0.9.0 (2018-06-28-23:51)
Licensed under GNU GPL v2
For bug reports, read
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
none separate
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : clock speed 1800 kHz
Error: open failed
in procedure 'init' 
in procedure 'ocd_bouncer'

make: *** [upload_combo_jtag] Error 1


#6

At this point it’s a problem with your cable/module.