From 8a5e0eb783c49dcb97cd932a0fce9ce1ab3527c5 Mon Sep 17 00:00:00 2001 From: NIIBE Yutaka Date: Thu, 23 Aug 2018 14:30:07 +0900 Subject: [PATCH] Fix README about -no-vidpid file name. --- README | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README b/README index cb81ba0..f33f3e4 100644 --- a/README +++ b/README @@ -419,11 +419,11 @@ Olimex STM32-H103 board ----------------------- If you are using Olimex JTAG-Tiny, type following to invoke OpenOCD -and write "gnuk-vidpid.elf" to Flash ROM: +and write "gnuk.elf" to Flash ROM: $ openocd -f interface/ftdi/olimex-jtag-tiny.cfg \ -f board/olimex_stm32_h103.cfg \ - -c "program build/gnuk-vidpid.elf verify reset exit" + -c "program build/gnuk.elf verify reset exit" Command invocation is assumed in src/ directory. @@ -436,7 +436,7 @@ If you are using Flying Stone Tiny 01, you need a SWD writer. OpenOCD 0.9.0 now supports ST-Link/V2. We can use it like: $ openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg \ - -c "program build/gnuk-vidpid.elf verify reset exit" + -c "program build/gnuk.elf verify reset exit" @@ -447,7 +447,7 @@ Reset the board with "USER" switch pushed. Type following to write to flash: # cd ../tool - # ./dfuse.py ../src/build/gnuk-vidpid.hex + # ./dfuse.py ../src/build/gnuk.hex Then, reset the board.