[riot-users] Flash to board: Nucleo F446RE

Kevin Weiss kevin.weiss at haw-hamburg.de
Wed Sep 11 10:07:45 CEST 2019


It could be something to do with virtual box (in which case I cannot 
help) or it could be a number of other things:

- Check to make sure the nucleo jumpers are correct, near the usb there 
should be something named ST-LINK, ensure both jumpers are closed
- Sometimes the nucleos are in a weird power mode and have trouble 
flashing, to get it out of that state try holding the reset button down 
and releasing right before the flashing starts
- If it is something to do with the RIOT flasher or virtualbox you can 
confirm by simply copying the binary into the nucleo (though you must 
first create a binary)
         arm-none-eabi-objcopy -O binary 
${RIOTBASE}/examples/default/bin/nucleo-f446re/default.elf 
<path_to_nucleo_filesystem>.bin

I hope that helps!

-Kevin

On 11.09.19 10:00, dicek bear wrote:
> Dear RIOT users,
>
> Hello, Recently I downloaded the latest version RIOT-OS 2019-09 and 
> try to execute "default" example at first.
>
> Now it successed to run "native" target and send, receive data by 
> using "txtsnd" command between 2 ports.
>
> Next step, I want to program "default" example into Nucleo-F446RE board.
> Compiling is no problem, but flashing the board failed as following,
>
> ---------------------------------------------------------------------------------------------------------
>  vagrant at vagrant:~/RIOT/examples/default$ make BOARD=nucleo-f446re flash
> Building application "default" for "nucleo-f446re" with MCU "stm32f4".
> "make" -C /home/vagrant/RIOT/boards/nucleo-f446re
> "make" -C /home/vagrant/RIOT/boards/common/nucleo
> "make" -C /home/vagrant/RIOT/core
> "make" -C /home/vagrant/RIOT/cpu/stm32f4
> "make" -C /home/vagrant/RIOT/cpu/cortexm_common
> "make" -C /home/vagrant/RIOT/cpu/cortexm_common/periph
> "make" -C /home/vagrant/RIOT/cpu/stm32_common
> "make" -C /home/vagrant/RIOT/cpu/stm32_common/periph
> "make" -C /home/vagrant/RIOT/cpu/stm32f4/periph
> "make" -C /home/vagrant/RIOT/drivers
> "make" -C /home/vagrant/RIOT/drivers/periph_common
> "make" -C /home/vagrant/RIOT/drivers/saul
> "make" -C /home/vagrant/RIOT/sys
> "make" -C /home/vagrant/RIOT/sys/auto_init
> "make" -C /home/vagrant/RIOT/sys/auto_init/saul
> "make" -C /home/vagrant/RIOT/sys/fmt
> "make" -C /home/vagrant/RIOT/sys/isrpipe
> "make" -C /home/vagrant/RIOT/sys/newlib_syscalls_default
> "make" -C /home/vagrant/RIOT/sys/phydat
> "make" -C /home/vagrant/RIOT/sys/pm_layered
> "make" -C /home/vagrant/RIOT/sys/ps
> "make" -C /home/vagrant/RIOT/sys/saul_reg
> "make" -C /home/vagrant/RIOT/sys/shell
> "make" -C /home/vagrant/RIOT/sys/shell/commands
> "make" -C /home/vagrant/RIOT/sys/stdio_uart
> "make" -C /home/vagrant/RIOT/sys/tsrb
>    text    data     bss     dec     hex filename
>   17428     144    2660   20232    4f08 
> /home/vagrant/RIOT/examples/default/bin/nucleo-f446re/default.elf
> /home/vagrant/RIOT/dist/tools/openocd/openocd.sh flash 
> /home/vagrant/RIOT/examples/default/bin/nucleo-f446re/default.elf
> /home/vagrant/RIOT/dist/tools/openocd/openocd.sh: line 124: [: : 
> integer expression expected
> ### Flashing Target ###
> 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
> hla_swd
> 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'
> /home/vagrant/RIOT/examples/default/../../Makefile.include:556: recipe 
> for target 'flash' failed
> make: *** [flash] Error 1
> ---------------------------------------------------------------------------------------------------------
>
> It looks like that a on board ST-Link V2 programmer is not accessed 
> and accepted from the PC (RIOT-OS) crrectly.
> I only installed "git", "vartual_box" and "vagrant" in the Windows10 PC.
> Do I need to install other softwares, device drivers in the Windows 10 
> PC ?.
>
> Regards,
> Dicek Bear.
>
> _______________________________________________
> users mailing list
> users at riot-os.org
> https://lists.riot-os.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/users/attachments/20190911/c8766c9e/attachment.htm>


More information about the users mailing list