Re: [riot-devel] replace printf, puts issue

[Ludwig Ortmann]

Hi,

Yes, we came to the same conclusion while driving to embedded world.
I've got the implementation and API  specification ready as well and will open 
a PR later.

Cheers, Ludwig

Am 27. Februar 2015 02:14:51 MEZ, schrieb Jozef Maslik :
>Hi,
>
>Yes compiler do not optimize (remove out) empty function defined as is
>suggested.
>But if RIOT does not want use macros, we can define empty function as
>static inline function in header and then will be removed by
>optimization.
>
>log_api.h
>
>#if MODULE_LOG
>void log_info(...);
>#else
>static inline void log_info(...) {}
>#endif
>
>
>BTW. Hauke idea use modules is nice.
>
>Regards,
>Jozef
>
>
>
>
>
>> On 23 Feb 2015, at 13:00, Martine Lenders 
>wrote:
>> 
>> Hi,
>> 
>> Am 23.02.2015 10:04 schrieb "Ludwig Ortmann"
>:
>> > are you suggesting macros are better than APIs + functions?
>> > If so, please explain why and what better means ;)
>> 
>> I was not sure if the compiler optimizes out empty functions, so I
>assumed
>> 
>> #define INFO(msg) (void)0;
>> 
>> to be the better solution concerning code size.
>> 
>> Regards, 
>> Martine
>> ___
>> 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

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

Re: [riot-devel] replace printf, puts issue

[Jozef Maslik]

Hi,

Yes compiler do not optimize (remove out) empty function defined as is 
suggested.
But if RIOT does not want use macros, we can define empty function as static 
inline function in header and then will be removed by optimization.

log_api.h

#if MODULE_LOG
void log_info(...);
#else
static inline void log_info(...) {}
#endif


BTW. Hauke idea use modules is nice.

Regards,
Jozef





> On 23 Feb 2015, at 13:00, Martine Lenders  wrote:
> 
> Hi,
> 
> Am 23.02.2015 10:04 schrieb "Ludwig Ortmann" :
> > are you suggesting macros are better than APIs + functions?
> > If so, please explain why and what better means ;)
> 
> I was not sure if the compiler optimizes out empty functions, so I assumed
> 
> #define INFO(msg) (void)0;
> 
> to be the better solution concerning code size.
> 
> Regards, 
> Martine
> ___
> 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

Re: [riot-devel] LGPL compliance testing

[Martine Lenders]

Hi Murat,
You made the PR to your own repository. You have to open a Pull Request to
our repository.

Hope I could help,
Martine

2015-02-26 16:56 GMT+01:00 Murat CAKMAK :

> Hi Ludwig,
>
> Pull request link : https://github.com/cakmakmurat2000/RIOT/pull/1
> It is my first GIT experience. I might miss something :)
>
> Regards.
>
> -Original Message-
> From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Ludwig Ortmann
> Sent: Thursday, February 26, 2015 8:32 AM
> To: RIOT OS kernel developers
> Subject: Re: [riot-devel] LGPL compliance testing
>
> PS: can you send a link to your PR? I couldn't find it.
>
> Cheers, Ludwig
>
> Am 26. Februar 2015 07:23:52 MEZ, schrieb Ludwig Ortmann
> :
> >Hi Murat,
> >
> >Under what license are the generated files?
> >And also, how do you think your port is related to the discussion in
> >this thread?
> >
> >I can try to talk about this topic with a cypress representative today.
> >We are currently at the "embedded world" and they are too. They seemed
> >interested in RIOT in an initial chat.
> >BTW: As far as I understood it, their software can create object files
> >with library code for the psoc. Therefore I guess it should be possible
> >to link the generated psoc library with RIOT in our make system as
> >well.
> >
> >So, whatever it looks like today, please don't close your pull request
> >yet.
> >
> >Cheers, Ludwig
> >
> >Am 25. Februar 2015 21:46:45 MEZ, schrieb Murat CAKMAK
> >:
> >>Hi All,
> >>
> >>
> >>
> >>I was (still) busy to read mails about LGPL compliance so sorry for
> >>slience.
> >>
> >>
> >>As you know, I have initially ported RIOT to PsoC 5LP processor by
> >>creating a PsoC Creator IDE Projects.
> >>
> >>
> >>
> >>In my case:
> >>
> >>1.   This port not using the default RIOT build environment and
> >>PsoC
> >>Creator IDE hides linking and other details.
> >>
> >>2.   PsoC Creator IDE also creates automatically some source
> >codes.
> >>I
> >>have created an empty project with a small HW design under
> >>dist/PsoCCreator directory. But when you build project in PsoC Creator
> >>IDE, It is going to create a lot of files; system initialization, APIs
> >>for HW blocks which created for RIOT etc. I was not planning to commit
> >>those files to GIT repository because they are already created
> >>automatically by IDE.
> >>
> >>3.   Auto-generated files may be changed (e.g bug fixing) by the
> >>version
> >>of PSOC Creator IDE. So, md5 sums may be different for different
> >>versions of PsoC Creator IDE.
> >>
> >>
> >>
> >>On the other hand, I can also implemented required files instead of
> >>auto-generated PsoC Creator files, and use RIOT build system. But HEX
> >>files of PsoC processors also includes HW desing code (verilog)
> >>addition to firmware output(elf, hex etc.). I dont know how PsoC
> >>Creator IDE
> >merges
> >>Firmware code and HW design code into a single HEX file and I am not
> >>sure about PSOC Creator team share this information with me.
> >>
> >>It is the hard way and also I dont prefer to use this way. Because, in
> >>this way, we can not use advantages(ARM Core + Programmable
> >>Digital&Analog
> >>Blocks) of PsoC processors which only available by PsoC Creator IDE.
> >>
> >>
> >>
> >>So, What is the latest decision?
> >>
> >>Should I withdraw my "pull request" for PsoC 5LP port?
> >>
> >>
> >>
> >>Regards.
> >>
> >>
> >>
> >>Murat.
> >>
> >>
> >>
> >>
> >>
> >>-Original Message-
> >>From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Matthias
> >>Waehlisch
> >>Sent: Saturday, February 21, 2015 5:09 PM
> >>To: RIOT OS kernel developers
> >>Subject: Re: [riot-devel] LGPL compliance testing
> >>
> >>
> >>
> >>Hi Kaspar,
> >>
> >>
> >>
> >>On Fri, 20 Feb 2015, Kaspar Schleiser wrote:
> >>
> >>
> >>
> >>> Let me correct myself.
> >>
> >>>
> >>
> >>> There are no technical reasons against using LGPLed RIOT to develop
> >>
> >>> proprietary applications.
> >>
> >>>
> >>
> >>  it depends on how you define "technical reasons". Yes, it is not
> >>impossible to create separate object files. But you maybe don't want
> >to
> >>do
> >>this for technical optimization (see for example
> >> >>_FINAL
> >>.pdf>
> >>
> http://www.htsoft.com/news/070309_Whitepaper-OmniscientCodeGeneration_FINA
> L.
> >>pdf).
> >>
> >>
> >>
> >>> Using a "weird compiler" that cannot output the required object
> >files
> >>
> >>
> >>> because it is closed source and proprietary is purely political.
> >That
> >>
> >>
> >>> compiler could be changed trivially *if it would be open source* or
> >>
> >>> the vendor was inclined to do so. This doesn't count as technical
> >>
> >>> reason.
> >>
> >>>
> >>
> >>  I agree with Oleg's comment on this.
> >>
> >>
> >>
> >> And btw, if a compiler can "be changed trivially" depends on details
> >I
> >>suppose.
> >>
> >>
> >>
> >>> >For me the sentence "RIOT allows LGPL + proprietary source code
> >
> >>
> >>> > at the sam

Re: [riot-devel] LGPL compliance testing

[Murat CAKMAK]

Hi Ludwig,

Pull request link : https://github.com/cakmakmurat2000/RIOT/pull/1
It is my first GIT experience. I might miss something :)

Regards. 

-Original Message-
From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Ludwig Ortmann
Sent: Thursday, February 26, 2015 8:32 AM
To: RIOT OS kernel developers
Subject: Re: [riot-devel] LGPL compliance testing

PS: can you send a link to your PR? I couldn't find it.

Cheers, Ludwig

Am 26. Februar 2015 07:23:52 MEZ, schrieb Ludwig Ortmann
:
>Hi Murat,
>
>Under what license are the generated files?
>And also, how do you think your port is related to the discussion in 
>this thread?
>
>I can try to talk about this topic with a cypress representative today.
>We are currently at the "embedded world" and they are too. They seemed 
>interested in RIOT in an initial chat.
>BTW: As far as I understood it, their software can create object files 
>with library code for the psoc. Therefore I guess it should be possible 
>to link the generated psoc library with RIOT in our make system as 
>well.
>
>So, whatever it looks like today, please don't close your pull request 
>yet.
>
>Cheers, Ludwig
>
>Am 25. Februar 2015 21:46:45 MEZ, schrieb Murat CAKMAK
>:
>>Hi All,
>>
>> 
>>
>>I was (still) busy to read mails about LGPL compliance so sorry for 
>>slience.
>>
>>
>>As you know, I have initially ported RIOT to PsoC 5LP processor by 
>>creating a PsoC Creator IDE Projects.
>>
>> 
>>
>>In my case:
>>
>>1.   This port not using the default RIOT build environment and
>>PsoC
>>Creator IDE hides linking and other details. 
>>
>>2.   PsoC Creator IDE also creates automatically some source
>codes.
>>I
>>have created an empty project with a small HW design under 
>>dist/PsoCCreator directory. But when you build project in PsoC Creator 
>>IDE, It is going to create a lot of files; system initialization, APIs 
>>for HW blocks which created for RIOT etc. I was not planning to commit 
>>those files to GIT repository because they are already created 
>>automatically by IDE.
>>
>>3.   Auto-generated files may be changed (e.g bug fixing) by the
>>version
>>of PSOC Creator IDE. So, md5 sums may be different for different 
>>versions of PsoC Creator IDE.
>>
>> 
>>
>>On the other hand, I can also implemented required files instead of 
>>auto-generated PsoC Creator files, and use RIOT build system. But HEX 
>>files of PsoC processors also includes HW desing code (verilog) 
>>addition to firmware output(elf, hex etc.). I dont know how PsoC 
>>Creator IDE
>merges
>>Firmware code and HW design code into a single HEX file and I am not 
>>sure about PSOC Creator team share this information with me.
>>
>>It is the hard way and also I dont prefer to use this way. Because, in 
>>this way, we can not use advantages(ARM Core + Programmable 
>>Digital&Analog
>>Blocks) of PsoC processors which only available by PsoC Creator IDE. 
>>
>> 
>>
>>So, What is the latest decision? 
>>
>>Should I withdraw my "pull request" for PsoC 5LP port? 
>>
>> 
>>
>>Regards. 
>>
>> 
>>
>>Murat. 
>>
>> 
>>
>> 
>>
>>-Original Message-
>>From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Matthias 
>>Waehlisch
>>Sent: Saturday, February 21, 2015 5:09 PM
>>To: RIOT OS kernel developers
>>Subject: Re: [riot-devel] LGPL compliance testing
>>
>> 
>>
>>Hi Kaspar,
>>
>> 
>>
>>On Fri, 20 Feb 2015, Kaspar Schleiser wrote:
>>
>> 
>>
>>> Let me correct myself.
>>
>>> 
>>
>>> There are no technical reasons against using LGPLed RIOT to develop
>>
>>> proprietary applications.
>>
>>> 
>>
>>  it depends on how you define "technical reasons". Yes, it is not 
>>impossible to create separate object files. But you maybe don't want
>to
>>do
>>this for technical optimization (see for example 
>>>_FINAL
>>.pdf>
>>http://www.htsoft.com/news/070309_Whitepaper-OmniscientCodeGeneration_FINA
L.
>>pdf).
>>
>> 
>>
>>> Using a "weird compiler" that cannot output the required object
>files
>>
>>
>>> because it is closed source and proprietary is purely political.
>That
>>
>>
>>> compiler could be changed trivially *if it would be open source* or
>>
>>> the vendor was inclined to do so. This doesn't count as technical
>>
>>> reason.
>>
>>> 
>>
>>  I agree with Oleg's comment on this.
>>
>> 
>>
>> And btw, if a compiler can "be changed trivially" depends on details
>I
>>suppose.
>>
>> 
>>
>>> >For me the sentence "RIOT allows LGPL + proprietary source code
>
>>
>>> > at the same level of comfort compared to Linux" sounds like a
>cheap
>>
>>
>>> > marketing slogan making clear that the persons are not aware of
>the
>>
>>
>>> > IoT diversity.
>>
>>> Saying otherwise makes clear that the persons are not aware of the
>>
>>> troubles embedded linux companies go through when developing
>>
>>> proprietary devices using (L)GPLed linux + libraries.
>>
>>> 
>>
>>  Both systems address different types of devices.
>>
>> 
>>
>>> >From a professional point o

Re: [riot-devel] Feedback from emworld and future plans (partnerships AND licensing)

[Kaspar Schleiser]

Hi,

On 02/26/2015 12:35 PM, Jan Wagner wrote:

 Is the big picture clearer fo you?
>

yes kind of. but can you please tell my what this fincancial engagement is used
for? - who is defined as maintainer?

RIOT is legally fully independent and will stay so.

We're setting up a Verein in order to (among other things) get the stuff 
that's now mostly done by universities (printing t-shirts & stickers, 
being the "communication entry point", providing servers, paying the 
drinks at community meetings) into a defined independence.


That Verein will have statues to keep RIOT independant and free and 
everyone will be able to join, taking part of that Verein's decision 
making processes.


That said - most of us are not free from the need to get paid by 
someone, and many would like to work on RIOT on some kind of salary.

We're trying to find a way to make that possible without selling our souls.

I agree with you - this stuff costs coding time. ;)

Kaspar


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

Re: [riot-devel] Feedback from emworld and future plans (partnerships AND licensing)

[Jan Wagner]

> Is the big picture clearer fo you?
>  

yes kind of. but can you please tell my what this fincancial engagement is used
for? - who is defined as maintainer?
(dont get me wrong I dont care about any fincial balances - I will never want a
single dime - my work for this project
is unpayable) - I dont know what kind of costs ther are etc. GIT, MAIL, what
else?

thanks for your answers!

I will not thinking about RIOT licenses, foundations, companies anymore - and
just keep coding :) (so no further questions
or ideas - I am wasting coding time :) - I abandon your (riot-core) plans and
decisions. dont sell your soul.

greets jan

> Emmanuel Baccelli  hat am 26. Februar 2015 um
> 11:42 geschrieben:
> 
>  Hi Jan,
>   
>  that's a lot of questions ;)
>  Long story short, the way I see it:
>   
>  - RIOT was initially developed by manpower funded by FU Berlin, INRIA, HAW
>  - nowadays, most core maintainers are still affiliated to these institutions
> (though there is a tendency towards more maintainers with other affiliations,
> which is great)
>  - FU Berlin, INRIA and HAW might not be able to sustain their current level
> of financial engagement (funding RIOT maintainers)
>  - even if FU Berlin, INRIA and HAW are able to sustain their current level of
> financial engagement, the community grows, and more maintainers are needed
>  - experience shows that it is difficult to rely only on people that do this
> on their "free time", especially when the community is as young as ours (e.g.,
> compare to Linux at its beginning)
>   
>  Therefore, the goals below are important:
>  1 - make sure there is nothing fundamental blocking our way towards
> accommodating a new wave of people that are paid to develop/maintain RIOT
>  2 - look for opportunities to work more closely with more
> companies/organizations that can (directly or indirectly) provide such
> manpower
>   
>  The license discussion relates to point 1. Getting legal advice from an
> organization such as FSF or Eclipse Foundation also relates to point 1.
> Opportunities for "matchmaking" with other communities and/or companies
> relates to point 2.
>   
>  Is the big picture clearer fo you?
>   
>  Best,
>   
>  Emmanuel
>   
>   
>   
>   
>   
>   
>   
> 
>  On Thu, Feb 26, 2015 at 8:23 AM, Jan Wagner   > wrote:
>> > Hi devs,
> > 
> >you have read that many of you are currently at embedded world meeting
> > with
> >representatives and "unbrella" corps.
> >I did not understand the future plans for the RIOT-OS yet. Its not even
> > clear to
> >me why and for what in details
> >RIOT needs business support. I mean we all have freedom incl the final
> > freedom
> >to fork etc and therefore
> >the plans of RIOT are imortant for me but not essential. Maybe someone
> > can
> >answer me the follwing list of
> >questions:
> > 
> >- RIOT is an OS that is mostly powered by the community with alot of
> > students
> >of european universities(?)
> >-If RIOT is an open source Project why would it require "legal services"
> > and
> >"promise promition", matchmaking??
> >- Why is RIOT searching for partnerships is it only about money? - and
> > for what
> >is that money exatly needed?
> >- Why are Business Partnerships needed? - the business gets a free OS and
> > saves
> >tons of development months,
> >with GPL that "can" give someone back - or simply hide the GPL code -
> > even if
> >they do not hide it its more a
> >moral problem because if you get sued - "by who?", and how mutch will it
> > cost?
> >(even in the times of
> >
> >almost nothing happend) (sorry but thats exatly what happend
> >with this "applicance like
> >systems" starting +15y ago.
> > 
> >I asked this questions to "understand the big picture" - and it can be
> > quite
> >different to my idea :
> > 
> >A strong, minimal and open IOT OS - that does NOT need promotion or
> > partnerships
> >- yeah be a partner its called
> >GPL join the code. I want "people" and "corps" to join simply for selfish
> >reasons - to get a better OS that
> >I am currently working with and supporting code too. A selflish but fair
> > win-win
> >of plain simple gpl.
> > 
> >Q: I dont want to start a "a deep philosophical" discussion - But what
> > EXACLTY
> >is RIOT searching for? - any I am not
> >talking about these beatifull business buzzwords. How mutch money is
> > needed and
> >for what "sections" (I just dont
> >see it - dont need exact numbers).
> > 
> >Q: Do we need promotion at all?
> > 
> >Q: I am straight spitter: I have heard that RIOT will have a "full time
> >worker/developer" hired - or was
> >already hired - Where does the money for the salery of this person comes
> > from?
> > 
> > 
> >Greets Jan
> >___
> >devel mailing list
> >d

Re: [riot-devel] LGPL compliance testing

[Kaspar Schleiser]

Hi,

On 02/25/2015 09:46 PM, Murat CAKMAK wrote:

So, What is the latest decision?

No decision, yet. Stay tuned. ;)


Should I withdraw my “pull request” for PsoC 5LP port?
Definately not. I guess whatever the license discussion will lead to, it 
will be possible to use that port even for proprietary application.


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

Re: [riot-devel] Feedback from emworld and future plans (partnerships AND licensing)

[Emmanuel Baccelli]

Hi Jan,

that's a lot of questions ;)
Long story short, the way I see it:

- RIOT was initially developed by manpower funded by FU Berlin, INRIA, HAW
- nowadays, most core maintainers are still affiliated to these
institutions (though there is a tendency towards more maintainers with
other affiliations, which is great)
- FU Berlin, INRIA and HAW might not be able to sustain their current level
of financial engagement (funding RIOT maintainers)
- even if FU Berlin, INRIA and HAW are able to sustain their current level
of financial engagement, the community grows, and more maintainers are
needed
- experience shows that it is difficult to rely only on people that do this
on their "free time", especially when the community is as young as ours
(e.g., compare to Linux at its beginning)

Therefore, the goals below are important:
1 - make sure there is nothing fundamental blocking our way towards
accommodating a new wave of people that are paid to develop/maintain RIOT
2 - look for opportunities to work more closely with more
companies/organizations that can (directly or indirectly) provide such
manpower

The license discussion relates to point 1. Getting legal advice from an
organization such as FSF or Eclipse Foundation also relates to point 1.
Opportunities for "matchmaking" with other communities and/or companies
relates to point 2.

Is the big picture clearer fo you?

Best,

Emmanuel








On Thu, Feb 26, 2015 at 8:23 AM, Jan Wagner  wrote:

> Hi devs,
>
> you have read that many of you are currently at embedded world meeting with
> representatives and "unbrella" corps.
> I did not understand the future plans for the RIOT-OS yet. Its not even
> clear to
> me why and for what in details
> RIOT needs business support. I mean we all have freedom incl the final
> freedom
> to fork etc and therefore
> the plans of RIOT are imortant for me but not essential. Maybe someone can
> answer me the follwing list of
> questions:
>
> - RIOT is an OS that is mostly powered by the community with alot  of
> students
> of european universities(?)
> -If RIOT is an open source Project why would it require "legal services"
> and
> "promise promition", matchmaking??
> - Why is RIOT searching for partnerships is it only about money? - and for
> what
> is that money exatly needed?
> - Why are Business Partnerships needed? - the business gets a free OS and
> saves
> tons of development months,
> with GPL that "can" give someone back - or simply hide the GPL code - even
> if
> they do not hide it its more a
> moral problem because if you get sued - "by who?", and how mutch will it
> cost?
> (even in the times of
> gpl-violations.org almost nothing happend) (sorry but thats exatly what
> happend
> with this "applicance like
> systems" starting +15y ago.
>
> I asked this questions to "understand the big picture" - and it can be
> quite
> different to my idea :
>
> A strong, minimal and open IOT OS - that does NOT need promotion or
> partnerships
> - yeah be a partner its called
> GPL join the code. I want "people" and "corps" to join simply for selfish
> reasons - to get a better OS that
> I am currently working with and supporting code too. A selflish but fair
> win-win
> of plain simple gpl.
>
> Q: I dont want to start a "a deep philosophical" discussion - But what
> EXACLTY
> is RIOT searching for? - any I am not
> talking about these beatifull business buzzwords. How mutch money is
> needed and
> for what "sections" (I just dont
> see it - dont need exact numbers).
>
> Q: Do we need promotion at all?
>
> Q: I am straight spitter: I have heard that RIOT will have a "full time
> worker/developer" hired - or was
> already hired - Where does the money for the salery of this person comes
> from?
>
>
> Greets Jan
> ___
> 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

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

[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
> > > 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
> > > ---

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

[Jan Wagner]

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
> > > 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 at

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

[Jan Wagner]

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
> > 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
> 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

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

[Christian Mehlis]

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
textdata bss dec hex filename
   13364 216   16496   30076757c
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
devel@riot-os.org
http://lists.riot-os.org/mailman/listinfo/devel