From f665ace38cfa4613fb911cb68f6662b15720ffea Mon Sep 17 00:00:00 2001
From: Kevin Hester <kevinh@geeksville.com>
Date: Sun, 11 Aug 2013 11:34:19 -1000
Subject: Add scripts for debugging with openocd

Note: We now use the version of stm32f4x that comes with openocd 0.7.0 or later
---
 Debug/olimex-px4fmu-debug.cfg | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 Debug/olimex-px4fmu-debug.cfg

(limited to 'Debug/olimex-px4fmu-debug.cfg')

diff --git a/Debug/olimex-px4fmu-debug.cfg b/Debug/olimex-px4fmu-debug.cfg
new file mode 100644
index 000000000..61d70070d
--- /dev/null
+++ b/Debug/olimex-px4fmu-debug.cfg
@@ -0,0 +1,22 @@
+# program a bootable device load on a mavstation
+# To run type openocd -f mavprogram.cfg
+
+source [find interface/olimex-arm-usb-ocd-h.cfg]
+source [find px4fmu-v1-board.cfg]
+
+init
+halt
+
+# Find the flash inside this CPU
+flash probe 0
+
+# erase it (128 pages) then program and exit
+
+#flash erase_sector 0 0 127
+# stm32f1x mass_erase 0 
+
+# It seems that Pat's image has a start address offset of 0x1000 but the vectors need to be at zero, so fixbin.sh moves things around
+#flash write_bank 0 fixed.bin 0
+#flash write_image firmware.elf
+#shutdown
+
-- 
cgit v1.2.3