Re: [riot-users] Flash to board: Nucleo F446RE

2019-09-12 Thread dicek bear 
Hello. Mr, Abadie,

As you pointed out, The Nucleo-F446RE directory is not automatically
mounted.
So I needed to add the STM32 ST-Link into the VirtualBox.
In detail, STMicroelectronics STM32 ST-Link is added to
[Setting]->[USB]->[USB device filter] of VirtualBox.

Now it is possible to flash "default" example to Nucleo-F446RE board.
The flashing issue is solved.

Thank you very much for your kind and good advice.

Regards,
Dicek Bear.


2019年9月11日(水) 18:17 Alexandre Abadie :

> Hi,
>
> If I understand correctly, you are trying to flash the nucleo board from a
> virtual machine running on a Windows host. In this case, if no NUCLEO-F446
> directory is automatically mounted when you plug the board, this means:
> - you have to install the virtualbox extension pack corresponding to your
> virtualbox version. If I remember correctly, you must stop virtualbox
> during the setup of the extension.
> - you need to enable USB support in the VM settings and verify virtualbox
> can share the USB device with the VM.
>
> Let us know if this solves your flashing issue.
>
> Alex
>
> - Le 11 Sep 19, à 10:00, dicek bear  a écrit :
>
> 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@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
>textdata bss dec hex filename
>   17428 1442660   202324f08
> /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@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/users
>
> ___
> users mailing list
> users@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/users
>
___
users mailing list
users@riot-os.org

Re: [riot-users] Adding more examples

2019-09-12 Thread Ken Bannister 
Also consider if the example would fit better in the applications
repository [1].

Ken

[1] https://github.com/RIOT-OS/applications


On 9/12/19 5:15 AM, Robert Hartung wrote:
> Make sure to give your PR a good title and description. Create separate
> PRs if the examples are different in their scope. Maybe not all examples
> are useful for RIOT upstream. In addition tests are always very welcome!
>
> On 11.09.19 21:30, Philipp Blum wrote:
>> Create a Pull-Request on Github. Someone will review your PR and
>> eventually it gets merged into the main branch.
>> https://help.github.com/en/articles/about-pull-requests
>>
>> Am 2019-09-11 17:46, schrieb Burak Karaduman:
>>
>>> Hi All,
>>> I am about the finish my master thesis Platform Specific Modeling of
>>> Riot OS is about to finish and I can satisfy new examples for Riot OS.
>>> Is there a way to share them to be included in the official GitHub
>>> repository?
>>>  
>>> Thanks.
>>>
>>> ___
>>> users mailing list
>>> users@riot-os.org 
>>> https://lists.riot-os.org/mailman/listinfo/users
>>  
>>
>>  
>>
>> ___
>> users mailing list
>> users@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/users
>>


pEpkey.asc
Description: application/pgp-keys
___
users mailing list
users@riot-os.org
https://lists.riot-os.org/mailman/listinfo/users

Re: [riot-users] Flash to board: Nucleo F446RE

2019-09-12 Thread dicek bear 
Hello. Mr Weiss,

At first, I checked the Nucleo-F446RE board jumper settings.The named
ST-LINK both jumpers are closed, it was no problem.
I checked the VirtuaBox setting as Mr Abadie pointed out. The problem was
that the Nucleo-F446RE board was not automatically
mounted.

Now the problem is solved.
I can flash "default" example to Nucleo-F446RE board.

Thank you very much for your kind and quick support.

Regards,
Dicek Bear.

2019年9月12日(木) 17:11 dicek bear :

> Hello. Mr, Abadie,
>
> As you pointed out, The Nucleo-F446RE directory is not automatically
> mounted.
> So I needed to add the STM32 ST-Link into the VirtualBox.
> In detail, STMicroelectronics STM32 ST-Link is added to
> [Setting]->[USB]->[USB device filter] of VirtualBox.
>
> Now it is possible to flash "default" example to Nucleo-F446RE board.
> The flashing issue is solved.
>
> Thank you very much for your kind and good advice.
>
> Regards,
> Dicek Bear.
>
>
> 2019年9月11日(水) 18:17 Alexandre Abadie :
>
>> Hi,
>>
>> If I understand correctly, you are trying to flash the nucleo board from
>> a virtual machine running on a Windows host. In this case, if no
>> NUCLEO-F446 directory is automatically mounted when you plug the board,
>> this means:
>> - you have to install the virtualbox extension pack corresponding to your
>> virtualbox version. If I remember correctly, you must stop virtualbox
>> during the setup of the extension.
>> - you need to enable USB support in the VM settings and verify virtualbox
>> can share the USB device with the VM.
>>
>> Let us know if this solves your flashing issue.
>>
>> Alex
>>
>> - Le 11 Sep 19, à 10:00, dicek bear  a écrit :
>>
>> 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@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
>>textdata bss dec hex filename
>>   17428 1442660   202324f08
>> /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)