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 <[email protected]> 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 <[email protected]> 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
> > > timer_thread: set timer successfully
> > > sec=31 min=5 hour=1
> > > sec=32 min=5 hour=1
> > > now=3933:13853 -> every 2.0s: Hello World
> > > timer_thread: set timer successfully
> > > now=3933:20576 -> every 5.0s: This is a Test
> > > timer_thread: set timer successfully
> > > now=3933:27680 -> every 5.0s: This is a Test
> > > timer_thread: set timer successfully
> > > now=3933:34786 -> every 5.0s: This is a Test <- LAST OUTPUT
> > > -----------------------------------------------------------------
> > > And I have repeated the test 4 times and get the same result
after 1hour
> > > 5minutes and 30 odd seconds all 4 times.
> > >
> > >
> > > I have not attached the compiler output files, as even
compressed, is
> > > greater than 6MBytes.
> > >
> > > I can provide more details on request, please advise.
> > >
> > > Karel Seeuwen
> > >
> > >
> > >
> > >
> > >
> > >
> > > -----------d*
> > > *
> > >
> >
> > _______________________________________________
> > devel mailing list
> > [email protected]
> > http://lists.riot-os.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
[email protected]
http://lists.riot-os.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
[email protected]
http://lists.riot-os.org/mailman/listinfo/devel
