Dear Adeel, Check your the status of st-link connection.
Your log has a clue that "Error: open failed". That means "Can not open jtag or st-link device" On Tue, Jul 12, 2016 at 6:09 PM, Adeel Mohammad Malik < [email protected]> wrote: > Hi all, > > > > I followed this guide > https://github.com/RIOT-OS/RIOT/wiki/Getting-started-with-STM32F%5B0%7C3%7C4%5Ddiscovery-boards > to flash RIOT code onto a STM32F4DISCOVERY board. I get the following > error:- > > > > command: "BOARD=stm32f4discovery make flash" > > > > Compiling successfully. > > > > ### Flashing Target ### > > Open On-Chip Debugger 0.10.0-dev-00325-g12e4a2a (2016-07-12-10:00) > > Licensed under GNU GPL v2 > > For bug reports, read > > http://openocd.org/doc/doxygen/bugs.html > > 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 > > srst_only separate srst_nogate srst_open_drain connect_deassert_srst > > 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' > > > > Done flashing > > > > Any clue what could be causing this? > > > > /Adeel > > > > _______________________________________________ > devel mailing list > [email protected] > https://lists.riot-os.org/mailman/listinfo/devel > >
_______________________________________________ devel mailing list [email protected] https://lists.riot-os.org/mailman/listinfo/devel
