[riot-devel] CPU ID for Intel Galileo

[SHUBHAM CHHABRA]

Hi,
I am interested to work on Issue#1511(
https://github.com/RIOT-OS/RIOT/issues/1511), developing CPU-ID for Intel
Galileo.
Can anyone help me with possible cross-compiler required to build code for
Quark SoC?
Shubham Chhabra
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] TLS

[Thomas C. Schmidt]

Hi Matthias,

there is ongoing work on DTLS + additional authentication.

There is also a port of the Relic library toolkit 
https://code.google.com/p/relic-toolkit/ including an extension for 
modern Edwards Curves (ECC).


There should be also additional work, but I'm not sure about its status.

Best,
 Thomas

On 10.03.2015 21:11, Matthias Dübon wrote:

Hello everyone,

I just heard about the RIOT project and it seems very promising. I
also heard some people are also working on some kind of security suite
for RIOT. Could I have some more information about the idea and the
status of that approach?

best
Matthias

ᐧ
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel



--

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidtFax: +49-40-42875-8409 °

--

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidtFax: +49-40-42875-8409 °
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] TLS

[Matthias Dübon]

Hello everyone,

I just heard about the RIOT project and it seems very promising. I
also heard some people are also working on some kind of security suite
for RIOT. Could I have some more information about the idea and the
status of that approach?

best
Matthias

ᐧ
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] GSOC-2015 Application

[Shrenik Jain]

Sir/Ma'am,

I am Shrenik Jain, a second year undergraduate student of Computer Science and 
Engineering at International Institute of Information Technology, Hyderabad. I 
am passionate about Open Source Development especially working with python and 
C. I also have experience working with git and I aspire to contribute to RIOT 
as Open source Developer under Google Summer of Code and I am interested in 
working on the project "Supporting Riot in ns3", since I feel I have the 
enthusiasm and skills required. I will appreciate any assistance with regards 
to beginner contribution on this project.

Waiting for a positive and quick response.

Sincerely,
Shrenik Jain
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] CC430 compile

[Hauke Petersen]

Hi İlkay,

to my knowledge anyone has started to port RIOT to the EW430 board, yet. 
So go ahead! For first steps have a look at the development procedures 
[1] and our porting guide [2].


Have fun coding!

Cheers,
Hauke

[1] https://github.com/RIOT-OS/RIOT/wiki/Development-procedures
[2] https://github.com/RIOT-OS/RIOT/wiki/Porting-Guide


On 10.03.2015 10:21, ilkay KOZAK wrote:

Hello All,
Has anyone ported RIOT-OS to IAR EW430 ?

Regards,

İlkay KOZAK



___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel


___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Help need

[saurabh]

Hi,
My name is Saurabh Chaudhari, I am a Final year student.
I have worked previously with MSP430 variants and Arduino boards.
I am interested in participating in GSOC this year and I found "riot" as 
an organization matching my intrests.
I would like to start actively contributing to riot and so I would be 
grateful if I could get a few heads up regarding how to get started with 
the code-base and the reference documents.




Regards,
Saurabh Chaudhari
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] CC430 compile

[ilkay KOZAK]

Hello All,
Has anyone ported RIOT-OS to IAR EW430 ?

Regards,

İlkay KOZAK



smime.p7s
Description: S/MIME cryptographic signature
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT/tests/vtimer_msg/main.c Failure after 1 hour 5 minutes an 32 seconds

[Hauke Petersen]

Hi Baptiste, hi Karel,

the vtimer problems are (infamously) well known at the moment. We are 
currently putting a timer task-force in place that will focus on 
re-designing the timer infrastructure. So expect some further 
information on this soon!


Cheers,
Hauke


On 10.03.2015 09:32, Baptiste Clenet wrote:
Thank for your answer, I'm going to investigate a bit more. Hopefully 
the RIOT team will solve those vtimer problem soon.


Cheers,

2015-03-10 8:56 GMT+01:00 kareponX . >:


Hi Baptiste,
I am sorry, but after the original failure, I tried tweaking a few
things like timer intervals, length of text in the print statement
etc, but the only difference was in when it failed, e.g. 50minutes,
1hour 10minutes etc.
RIOT is/was one of many RTOSes I've been looking at, and the
"/RIOT/tests/vtimer_msg"
program was the second program I ran, after the hello world program,
and frankly I had no time to set up a debugging environment, so I can
only guess at the cause. It could be a trap (pointer access to invalid
memory etc), a Uart buffer bug, getting locked at empty/full, but not
so likely. My final guess is a Semaphore/Mutex lockup bug, because the
Uart output is never garbled, is complete, and in my case always ended
with
  sec=31 min=5 hour=1
  sec=32 min=5 hour=1
these lines suspiciously missing from the final lines of output. But
who knows...

wish you all luck. Karel

On 3/10/15, Baptiste Clenet mailto:bapcle...@gmail.com>> wrote:
> Hello Karel,
>
> Have you managed to solve your vtimer problem? I've got a
similar problem
> (different time) on the SAMR21. Look at Jan second answer.
>
> Best,
>
> 2015-02-26 9:53 GMT+01:00 Cenk Gündogan
mailto:cenk.guendo...@fu-berlin.de>>:
>
>>  I am not certain if Karel joined the mailing list here yet..
you might
>> want to include him directly until we know more.
>>
>>
>> On 26.02.2015 09 :48, Jan Wagner wrote:
>>
>>  Ok. got it wrong - the SERIAL STOPS! is important. hm sorry -
hm what
>> happens if you modify
>>
>>  sleep
>>
>>  value? (lower fe.) how many output ? differnt behavoir?
>>
>>  greets Jan
>>
>>  ps sorry for the missunderstanding
>>
>>
>> > Jan Wagner mailto:m...@jwagner.eu>>
mailto:m...@jwagner.eu>> hat am 26. Februar 2015
>> um 09:40 geschrieben:
>> >
>> >
>> > Hi,
>> >
>> > maybe I am not gettting the problem right - but if you read
the source:
>> >
>> >
https://github.com/RIOT-OS/RIOT/blob/master/tests/vtimer_msg/main.c
>> >
>> > lines 123 - 126 show
>> >
>> > while (1) {
>> > vtimer_sleep(sleep);
>> > msg_try_send(&m, pid2);
>> > }
>> >
>> > that this is regular behavior :)
>> >
>> > https://github.com/RIOT-OS/RIOT/tree/master/examples/default
>> >
>> > is the way to go to get an first impression - for simple
output use
>> helloworld
>> > example
>> >
>> >
>> > Greets Jan
>> >
>> > > Christian Mehlis mailto:christ...@m3hlis.de>> mailto:christ...@m3hlis.de>> hat am
>> 26. Februar 2015 um 09:26
>> > > geschrieben:
>> > >
>> > >
>> > > Hi Karel,
>> > >
>> > > I'm currently not offering (paid) private consulting for RIOT.
>> > >
>> > > I'll forward your mail to to the public RIOT devel list and the
>> further
>> > > discussion about your issue should happen there.
>> > >
>> > > Alternatively you can ask for a consultant there, too.
>> > >
>> > > Best
>> > > Christian
>> > >
>> > >
>> > > Am 26.02.2015 um 03:12 schrieb karel:
>> > > > Dear Cenk, Christian
>> > > >
>> > > > forgive me for the direct mail, but I am not up to speed
on how to
>> use
>> > > > GitHub for reporting these issues.
>> > > >
>> > > > yesterday I cloned RIOT-OS/RIOT from github.
>> > > >
>> > > > I made the vtimer_msg project
>> > > >
https://github.com/RIOT-OS/RIOT/blob/master/tests/vtimer_msg/main.c
>> > > >
>> > > > On a Windows 7 platform under minGW using the latest
>> > > > https://launchpad.net/gcc-arm-embedded compiler
>> > > >
>> > > > karel@bogus-PC /c/gat/riot-os/RIOT/examples/hello-world
>> > > > $ export
>> PATH=/c/gat/riot-os/tools/gcc-arm-none-eabi-4_9-2014q4/bin:$PATH
>> > > >
>> > > > karel@bogus-PC /c/gat/riot-os/RIOT/examples/hello-world
>> > > > $ export
>> > > >
>>

PATH=/c/gat/riot-os/tools/gcc-arm-none-eabi-4_9-2014q4/arm-none-eabi/bin:$PATH
>>
>> > > >
>> > > >
>> > > > ...
>> > > >
>> > > > karel@bogus-PC /c/gat/riot-os/RIOT/tests/vtimer_msg
>> > > > $ make BOARD=stm32f4discovery
>> > > > CAUTION: No flash tool for your host system found!
>> > > > Building application "vtimer_msg" for "stm32f4disc

[riot-devel] GSOC 2015 Project N2: Implementation of LwM2M

[Vaneet yadav]

hi all,
   I am Vaneet Singh Yadav undergraduate student of IIT Guwahati. I am
interested in LwM2M project i have a prior experience of network
programming, I implemented Kernel-bypass networking  during my internship .
This means moving control of Ethernet hardware directly into userspace
processes to avoid the overhead of communicating with the operating system
kernel. This gives userspace all of the raw performance traditionally
enjoyed by the kernel – and all of the responsibility too. This is
important for certain specialized applications that can gain as much as 20x
more performance.
it would be very helpful to me , if someone can tell me how to start or
provide me some resources .

Thank you
Vaneet Singh Yadav
___
devel mailing list
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT/tests/vtimer_msg/main.c Failure after 1 hour 5 minutes an 32 seconds

[Baptiste Clenet]

Thank for your answer, I'm going to investigate a bit more. Hopefully the
RIOT team will solve those vtimer problem soon.

Cheers,

2015-03-10 8:56 GMT+01:00 kareponX . :

> Hi Baptiste,
> I am sorry, but after the original failure, I tried tweaking a few
> things like timer intervals, length of text in the print statement
> etc, but the only difference was in when it failed, e.g. 50minutes,
> 1hour 10minutes etc.
> RIOT is/was one of many RTOSes I've been looking at, and the
> "/RIOT/tests/vtimer_msg"
> program was the second program I ran, after the hello world program,
> and frankly I had no time to set up a debugging environment, so I can
> only guess at the cause. It could be a trap (pointer access to invalid
> memory etc), a Uart buffer bug, getting locked at empty/full, but not
> so likely. My final guess is a Semaphore/Mutex lockup bug, because the
> Uart output is never garbled, is complete, and in my case always ended
> with
>   sec=31 min=5 hour=1
>   sec=32 min=5 hour=1
> these lines suspiciously missing from the final lines of output. But
> who knows...
>
> wish you all luck. Karel
>
> On 3/10/15, Baptiste Clenet  wrote:
> > Hello Karel,
> >
> > Have you managed to solve your vtimer problem? I've got a similar problem
> > (different time) on the SAMR21. Look at Jan second answer.
> >
> > Best,
> >
> > 2015-02-26 9:53 GMT+01:00 Cenk Gündogan :
> >
> >>  I am not certain if Karel joined the mailing list here yet.. you might
> >> want to include him directly until we know more.
> >>
> >>
> >> On 26.02.2015 09:48, Jan Wagner wrote:
> >>
> >>  Ok. got it wrong - the SERIAL STOPS! is important. hm sorry - hm what
> >> happens if you modify
> >>
> >>  sleep
> >>
> >>  value? (lower fe.) how many output ? differnt behavoir?
> >>
> >>  greets Jan
> >>
> >>  ps sorry for the missunderstanding
> >>
> >>
> >> > Jan Wagner   hat am 26. Februar
> 2015
> >> um 09:40 geschrieben:
> >> >
> >> >
> >> > Hi,
> >> >
> >> > maybe I am not gettting the problem right - but if you read the
> source:
> >> >
> >> > https://github.com/RIOT-OS/RIOT/blob/master/tests/vtimer_msg/main.c
> >> >
> >> > lines 123 - 126 show
> >> >
> >> > while (1) {
> >> > vtimer_sleep(sleep);
> >> > msg_try_send(&m, pid2);
> >> > }
> >> >
> >> > that this is regular behavior :)
> >> >
> >> > https://github.com/RIOT-OS/RIOT/tree/master/examples/default
> >> >
> >> > is the way to go to get an first impression - for simple output use
> >> helloworld
> >> > example
> >> >
> >> >
> >> > Greets Jan
> >> >
> >> > > Christian Mehlis   hat am
> >> 26. Februar 2015 um 09:26
> >> > > geschrieben:
> >> > >
> >> > >
> >> > > Hi Karel,
> >> > >
> >> > > I'm currently not offering (paid) private consulting for RIOT.
> >> > >
> >> > > I'll forward your mail to to the public RIOT devel list and the
> >> further
> >> > > discussion about your issue should happen there.
> >> > >
> >> > > Alternatively you can ask for a consultant there, too.
> >> > >
> >> > > Best
> >> > > Christian
> >> > >
> >> > >
> >> > > Am 26.02.2015 um 03:12 schrieb karel:
> >> > > > Dear Cenk, Christian
> >> > > >
> >> > > > forgive me for the direct mail, but I am not up to speed on how to
> >> use
> >> > > > GitHub for reporting these issues.
> >> > > >
> >> > > > yesterday I cloned RIOT-OS/RIOT from github.
> >> > > >
> >> > > > I made the vtimer_msg project
> >> > > >
> https://github.com/RIOT-OS/RIOT/blob/master/tests/vtimer_msg/main.c
> >> > > >
> >> > > > On a Windows 7 platform under minGW using the latest
> >> > > > https://launchpad.net/gcc-arm-embedded compiler
> >> > > >
> >> > > > karel@bogus-PC /c/gat/riot-os/RIOT/examples/hello-world
> >> > > > $ export
> >> PATH=/c/gat/riot-os/tools/gcc-arm-none-eabi-4_9-2014q4/bin:$PATH
> >> > > >
> >> > > > karel@bogus-PC /c/gat/riot-os/RIOT/examples/hello-world
> >> > > > $ export
> >> > > >
> >>
> PATH=/c/gat/riot-os/tools/gcc-arm-none-eabi-4_9-2014q4/arm-none-eabi/bin:$PATH
> >>
> >> > > >
> >> > > >
> >> > > > ...
> >> > > >
> >> > > > karel@bogus-PC /c/gat/riot-os/RIOT/tests/vtimer_msg
> >> > > > $ make BOARD=stm32f4discovery
> >> > > > CAUTION: No flash tool for your host system found!
> >> > > > Building application "vtimer_msg" for "stm32f4discovery" with MCU
> >> > > > "stm32f4".
> >> > > >
> >> > > > "make" -C /c/gat/riot-os/RIOT/boards/stm32f4discovery
> >> > > > "make" -C /c/gat/riot-os/RIOT/core
> >> > > > "make" -C /c/gat/riot-os/RIOT/cpu/stm32f4
> >> > > > "make" -C /c/gat/riot-os/RIOT/cpu/cortex-m4_common
> >> > > > "make" -C /c/gat/riot-os/RIOT/cpu/stm32f4/periph
> >> > > > "make" -C /c/gat/riot-os/RIOT/drivers
> >> > > > "make" -C /c/gat/riot-os/RIOT/sys
> >> > > > "make" -C /c/gat/riot-os/RIOT/sys/auto_init
> >> > > > "make" -C /c/gat/riot-os/RIOT/sys/timex
> >> > > > "make" -C /c/gat/riot-os/RIOT/sys/vtimer
> >> > > > text data bss dec hex filename
> >> > > > 13364 216 16496 30076 757c
> >> > > >
> >> c:/gat/riot-os/RIOT/tests/vtimer_msg/bin/stm32f4discovery/vtimer_msg.elf
> >> > > >
> >> > > > karel@bogus-PC /c/gat

Re: [riot-devel] RIOT/tests/vtimer_msg/main.c Failure after 1 hour 5 minutes an 32 seconds

[kareponX .]

Hi Baptiste,
I am sorry, but after the original failure, I tried tweaking a few
things like timer intervals, length of text in the print statement
etc, but the only difference was in when it failed, e.g. 50minutes,
1hour 10minutes etc.
RIOT is/was one of many RTOSes I've been looking at, and the
"/RIOT/tests/vtimer_msg"
program was the second program I ran, after the hello world program,
and frankly I had no time to set up a debugging environment, so I can
only guess at the cause. It could be a trap (pointer access to invalid
memory etc), a Uart buffer bug, getting locked at empty/full, but not
so likely. My final guess is a Semaphore/Mutex lockup bug, because the
Uart output is never garbled, is complete, and in my case always ended
with
  sec=31 min=5 hour=1
  sec=32 min=5 hour=1
these lines suspiciously missing from the final lines of output. But
who knows...

wish you all luck. Karel

On 3/10/15, Baptiste Clenet  wrote:
> Hello Karel,
>
> Have you managed to solve your vtimer problem? I've got a similar problem
> (different time) on the SAMR21. Look at Jan second answer.
>
> Best,
>
> 2015-02-26 9:53 GMT+01:00 Cenk Gündogan :
>
>>  I am not certain if Karel joined the mailing list here yet.. you might
>> want to include him directly until we know more.
>>
>>
>> On 26.02.2015 09:48, Jan Wagner wrote:
>>
>>  Ok. got it wrong - the SERIAL STOPS! is important. hm sorry - hm what
>> happens if you modify
>>
>>  sleep
>>
>>  value? (lower fe.) how many output ? differnt behavoir?
>>
>>  greets Jan
>>
>>  ps sorry for the missunderstanding
>>
>>
>> > Jan Wagner   hat am 26. Februar 2015
>> um 09:40 geschrieben:
>> >
>> >
>> > Hi,
>> >
>> > maybe I am not gettting the problem right - but if you read the source:
>> >
>> > https://github.com/RIOT-OS/RIOT/blob/master/tests/vtimer_msg/main.c
>> >
>> > lines 123 - 126 show
>> >
>> > while (1) {
>> > vtimer_sleep(sleep);
>> > msg_try_send(&m, pid2);
>> > }
>> >
>> > that this is regular behavior :)
>> >
>> > https://github.com/RIOT-OS/RIOT/tree/master/examples/default
>> >
>> > is the way to go to get an first impression - for simple output use
>> helloworld
>> > example
>> >
>> >
>> > Greets Jan
>> >
>> > > Christian Mehlis   hat am
>> 26. Februar 2015 um 09:26
>> > > geschrieben:
>> > >
>> > >
>> > > Hi Karel,
>> > >
>> > > I'm currently not offering (paid) private consulting for RIOT.
>> > >
>> > > I'll forward your mail to to the public RIOT devel list and the
>> further
>> > > discussion about your issue should happen there.
>> > >
>> > > Alternatively you can ask for a consultant there, too.
>> > >
>> > > Best
>> > > Christian
>> > >
>> > >
>> > > Am 26.02.2015 um 03:12 schrieb karel:
>> > > > Dear Cenk, Christian
>> > > >
>> > > > forgive me for the direct mail, but I am not up to speed on how to
>> use
>> > > > GitHub for reporting these issues.
>> > > >
>> > > > yesterday I cloned RIOT-OS/RIOT from github.
>> > > >
>> > > > I made the vtimer_msg project
>> > > > https://github.com/RIOT-OS/RIOT/blob/master/tests/vtimer_msg/main.c
>> > > >
>> > > > On a Windows 7 platform under minGW using the latest
>> > > > https://launchpad.net/gcc-arm-embedded compiler
>> > > >
>> > > > karel@bogus-PC /c/gat/riot-os/RIOT/examples/hello-world
>> > > > $ export
>> PATH=/c/gat/riot-os/tools/gcc-arm-none-eabi-4_9-2014q4/bin:$PATH
>> > > >
>> > > > karel@bogus-PC /c/gat/riot-os/RIOT/examples/hello-world
>> > > > $ export
>> > > >
>> PATH=/c/gat/riot-os/tools/gcc-arm-none-eabi-4_9-2014q4/arm-none-eabi/bin:$PATH
>>
>> > > >
>> > > >
>> > > > ...
>> > > >
>> > > > karel@bogus-PC /c/gat/riot-os/RIOT/tests/vtimer_msg
>> > > > $ make BOARD=stm32f4discovery
>> > > > CAUTION: No flash tool for your host system found!
>> > > > Building application "vtimer_msg" for "stm32f4discovery" with MCU
>> > > > "stm32f4".
>> > > >
>> > > > "make" -C /c/gat/riot-os/RIOT/boards/stm32f4discovery
>> > > > "make" -C /c/gat/riot-os/RIOT/core
>> > > > "make" -C /c/gat/riot-os/RIOT/cpu/stm32f4
>> > > > "make" -C /c/gat/riot-os/RIOT/cpu/cortex-m4_common
>> > > > "make" -C /c/gat/riot-os/RIOT/cpu/stm32f4/periph
>> > > > "make" -C /c/gat/riot-os/RIOT/drivers
>> > > > "make" -C /c/gat/riot-os/RIOT/sys
>> > > > "make" -C /c/gat/riot-os/RIOT/sys/auto_init
>> > > > "make" -C /c/gat/riot-os/RIOT/sys/timex
>> > > > "make" -C /c/gat/riot-os/RIOT/sys/vtimer
>> > > > text data bss dec hex filename
>> > > > 13364 216 16496 30076 757c
>> > > >
>> c:/gat/riot-os/RIOT/tests/vtimer_msg/bin/stm32f4discovery/vtimer_msg.elf
>> > > >
>> > > > karel@bogus-PC /c/gat/riot-os/RIOT/tests/vtimer_msg
>> > > > $
>> > > >
>> > > > I "flashed" the stm32f4discovery board (CPU: STM32F407VGT6) with
>> > > > the
>> > > > "vtimer_msg.hex" file using the STmicroelectronics STM32 ST-Link
>> Utility
>> > > > V3.5.0 (latest), as I have done so for many other projects on this
>> boards.
>> > > >
>> > > > The Problem:
>> > > >
>> > > > The program stops outputting data to the serial port, as follows
>> > > > -

Re: [riot-devel] RIOT/tests/vtimer_msg/main.c Failure after 1 hour 5 minutes an 32 seconds

[Baptiste Clenet]

Hello Karel,

Have you managed to solve your vtimer problem? I've got a similar problem
(different time) on the SAMR21. Look at Jan second answer.

Best,

2015-02-26 9:53 GMT+01:00 Cenk Gündogan :

>  I am not certain if Karel joined the mailing list here yet.. you might
> want to include him directly until we know more.
>
>
> On 26.02.2015 09:48, Jan Wagner wrote:
>
>  Ok. got it wrong - the SERIAL STOPS! is important. hm sorry - hm what
> happens if you modify
>
>  sleep
>
>  value? (lower fe.) how many output ? differnt behavoir?
>
>  greets Jan
>
>  ps sorry for the missunderstanding
>
>
> > Jan Wagner   hat am 26. Februar 2015
> um 09:40 geschrieben:
> >
> >
> > Hi,
> >
> > maybe I am not gettting the problem right - but if you read the source:
> >
> > https://github.com/RIOT-OS/RIOT/blob/master/tests/vtimer_msg/main.c
> >
> > lines 123 - 126 show
> >
> > while (1) {
> > vtimer_sleep(sleep);
> > msg_try_send(&m, pid2);
> > }
> >
> > that this is regular behavior :)
> >
> > https://github.com/RIOT-OS/RIOT/tree/master/examples/default
> >
> > is the way to go to get an first impression - for simple output use
> helloworld
> > example
> >
> >
> > Greets Jan
> >
> > > Christian Mehlis   hat am
> 26. Februar 2015 um 09:26
> > > geschrieben:
> > >
> > >
> > > Hi Karel,
> > >
> > > I'm currently not offering (paid) private consulting for RIOT.
> > >
> > > I'll forward your mail to to the public RIOT devel list and the
> further
> > > discussion about your issue should happen there.
> > >
> > > Alternatively you can ask for a consultant there, too.
> > >
> > > Best
> > > Christian
> > >
> > >
> > > Am 26.02.2015 um 03:12 schrieb karel:
> > > > Dear Cenk, Christian
> > > >
> > > > forgive me for the direct mail, but I am not up to speed on how to
> use
> > > > GitHub for reporting these issues.
> > > >
> > > > yesterday I cloned RIOT-OS/RIOT from github.
> > > >
> > > > I made the vtimer_msg project
> > > > https://github.com/RIOT-OS/RIOT/blob/master/tests/vtimer_msg/main.c
> > > >
> > > > On a Windows 7 platform under minGW using the latest
> > > > https://launchpad.net/gcc-arm-embedded compiler
> > > >
> > > > karel@bogus-PC /c/gat/riot-os/RIOT/examples/hello-world
> > > > $ export
> PATH=/c/gat/riot-os/tools/gcc-arm-none-eabi-4_9-2014q4/bin:$PATH
> > > >
> > > > karel@bogus-PC /c/gat/riot-os/RIOT/examples/hello-world
> > > > $ export
> > > >
> PATH=/c/gat/riot-os/tools/gcc-arm-none-eabi-4_9-2014q4/arm-none-eabi/bin:$PATH
>
> > > >
> > > >
> > > > ...
> > > >
> > > > karel@bogus-PC /c/gat/riot-os/RIOT/tests/vtimer_msg
> > > > $ make BOARD=stm32f4discovery
> > > > CAUTION: No flash tool for your host system found!
> > > > Building application "vtimer_msg" for "stm32f4discovery" with MCU
> > > > "stm32f4".
> > > >
> > > > "make" -C /c/gat/riot-os/RIOT/boards/stm32f4discovery
> > > > "make" -C /c/gat/riot-os/RIOT/core
> > > > "make" -C /c/gat/riot-os/RIOT/cpu/stm32f4
> > > > "make" -C /c/gat/riot-os/RIOT/cpu/cortex-m4_common
> > > > "make" -C /c/gat/riot-os/RIOT/cpu/stm32f4/periph
> > > > "make" -C /c/gat/riot-os/RIOT/drivers
> > > > "make" -C /c/gat/riot-os/RIOT/sys
> > > > "make" -C /c/gat/riot-os/RIOT/sys/auto_init
> > > > "make" -C /c/gat/riot-os/RIOT/sys/timex
> > > > "make" -C /c/gat/riot-os/RIOT/sys/vtimer
> > > > text data bss dec hex filename
> > > > 13364 216 16496 30076 757c
> > > >
> c:/gat/riot-os/RIOT/tests/vtimer_msg/bin/stm32f4discovery/vtimer_msg.elf
> > > >
> > > > karel@bogus-PC /c/gat/riot-os/RIOT/tests/vtimer_msg
> > > > $
> > > >
> > > > I "flashed" the stm32f4discovery board (CPU: STM32F407VGT6) with the
> > > > "vtimer_msg.hex" file using the STmicroelectronics STM32 ST-Link
> Utility
> > > > V3.5.0 (latest), as I have done so for many other projects on this
> boards.
> > > >
> > > > The Problem:
> > > >
> > > > The program stops outputting data to the serial port, as follows
> > > > -
> > > > kernel_init(): This is RIOT! (Version: 2014.12-482-gda8b4-bogus-PC)
> > > > kernel_init(): jumping into first task...
> > > > This is thread 3
> > > > sending 1st msg
> > > > now=0:6501 -> every 2.0s: Hello World
> > > > timer_thread: set timer successfully
> > > > sending 2nd msg
> > > > now=0:14388 -> every 5.0s: This is a Test
> > > > timer_thread: set timer successfully
> > > > This is thread 4
> > > > sec=1 min=0 hour=0
> > > > now=2:9789 -> every 2.0s: Hello World
> > > > timer_thread: set timer successfully
> > > > sec=2 min=0 hour=0
> > > > sec=3 min=0 hour=0
> > > > ...
> > > > ...
> > > > now=3927:3503 -> every 2.0s: Hello World
> > > > timer_thread: set timer successfully
> > > > sec=27 min=5 hour=1
> > > > sec=28 min=5 hour=1
> > > > now=3928:16808 -> every 5.0s: This is a Test
> > > > timer_thread: set timer successfully
> > > > now=3929:6924 -> every 2.0s: Hello World
> > > > timer_thread: set timer successfully
> > > > sec=29 min=5 hour=1
> > > > sec=30 min=5 hour=1
> > > > now=3931:10345 -> every 2.0s: Hello World
> > >