All output goes into the output folder

Makefile

@@ -223,13 +223,13 @@ debug: $(EXECUTABLE)
 	-iex 'mon halt' $<
 
 klee: buildrepo $(EXECUTABLE)
-	klee -emit-all-errors $(IROUT)
+	mkdir -p output; cp $(IROUT) output/; cd output; klee -emit-all-errors $(IROUT); cd ..
 
 run: buildrepo $(EXECUTABLE)
 	arm-none-eabi-gdb -q -x klee_stm_gdb.py $(EXECUTABLE)
 
 bench: buildrepo $(EXECUTABLE)
-	make clean; make; make klee; make clean; make wcet; make run; python profiling_db_parser.py klee_profiling.db
+	make clean; make; make klee; make clean; make wcet; make run; python profiling_db_parser.py output/klee_profiling.db
 
 define make-repo
    for dir in $(SRCDIRS); \

README.md

@@ -87,6 +87,13 @@ causes interrupts is also wonky, e.g., when sigle stepping over a `JOB_REQUEST`
 the pend bit is not correctly handeled (and the corresponding interrupt not taken). These problems are present for this project only, 
 but general to the gdb debug integration, so be aware.
 
+If not using Eclipse the way to start openocd is by invoking:
+
+```
+openocd -f st_nuclie_f4_itm.cfg
+```
+in a separate terminal.
+
 ## Problems
 
 If openocd fails to start, one possible error is that the `/tmp/swo.log` file has been locked to a bad state. Actually its not an 

klee_stm_gdb.py

@@ -17,6 +17,12 @@ object_index_current = 0
 object_index_max = 100
 
 database_name = "klee_profiling"
+path = "output"
+
+""" Create an folder named output if it doesn't exist """
+os.makedirs(path, exist_ok=True)
+""" Enter the output folder """
+os.chdir(path)
 
 """ Check if a database exists, otherwise create one """