Recently I started programming the Russian microcontroller MDR32F1QI. Problems with the assembly, not to mention the controller itself did not arise. However, for the past month I have been fixing the controller from Windows using Keil or a program from the delivery of the debugging board, and debugging it in Linux / Eclipse / JLink V8. Please tell me what to write in the makefile'e for the firmware of my compatriot (somehow, if only outside of the makefile'a separate utility). I tried this line:

openocd -f target/1986ve1t.cfg -c init; reset halt; flash write_image erase $(RESULT).bin 0x00000000; reset run; shutdown 
In response, I get the following:
 Open On-Chip Debugger 0.9.0 (2015-09-02-10:42) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Error: Debug adapter does not support any transports? Check config file order. Error: unable to select a session transport. Can't continue. shutdown command invoked reset: unknown terminal type halt Terminal type? 
What is the "terminal type" and what do not like openocd?
The name of the openocd configuration file (1986ve1t.cfg) has been changed (Russian letters in the file names are not understandable to all auxiliary utilities)

  • Such questions are better to ask in specialized forums: sugar, electronics and so forth, but note, the public there is irresponsible in some places. - sergw
  • Who came up with this line? unknown terminal type halt issued by the linux reset command (see man reset , well, it does not find the terminal with the name halt). Semicolons on the command line separate commands, so it happened. - sercxjo
  • Well, not really an epic fail, just all this garbage should be shoved in quotes! on parking, even this happens: (In the morning I will try ATP! This can be considered an answer, even if it does not work !!!
  • @sercxjo, post your comment as an answer. - ߊߚߤߘ

1 answer 1

unknown terminal type halt issued by the linux reset command (see man reset , well, it does not find the terminal with the name halt). Semicolons on the command line separate shell commands, so it happened.

Apparently, everything after -c should be enclosed in apostrophes:

 openocd -f target/1986ve1t.cfg -c 'init; reset halt; flash write_image erase $(RESULT).bin 0x00000000; reset run; shutdown'