Re: [riot-devel] CC1200 Sub-GHz Transceiver

[Antonio Linan]

Hello Anon!

If you need help (as in devices with the CC1200 on board) drop me a line

Cheers,

--Antonio


> Hi Anon,
>
> it seems no one is working on this driver so please go ahead :-)! As
> long as the CC1200 is not part of the CC2538 I agree with you the the
> driver should be implemented stand alone. Compare e.g. the at86rf2xx
> driver.
>
> Best
> Peter
>
> Am 21.12.2016 um 18:41 schrieb Anon Mall:
> > Hi all,
> > I wanted to ask if someone is currently working on a driver for the
> CC1200 transceiver? Otherwise I would try my luck.
> > Also in the readme of the Remote is noted, that the CC1200 is a matter
> of the CC2538 base. As the transceiver is not included in the CC2538, I
> would think that the driver should rather be implemented stand alone or am
> I mistaken?
> >
> > Cheers and happy Holidays,
> > Anon?
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Strange errors

[Ilias Seitanidis]

Dear all,
thank you very much for your fast reply.

Best,
Ilias
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Stacksize optimization

[Oleg Hahm]

Hi!

On Mon, Jan 09, 2017 at 02:01:04PM +0100, Baptiste Clenet wrote:
> In order to optimize the statcksize of a thread, I would like to know
> when the thread uses the maximum of its stack (maximum can be 3/4 of
> the stack for instance)
> How can I find this "time"?

Sounds like a case for -finstrument-functions (man gcc).

Cheers,
Oleg
-- 
die_if_kernel("Kernel gets FloatingPenguinUnit disabled trap", regs);
linux-2.2.16/arch/sparc/kernel/traps.c


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Stacksize optimization

[Alexander Aring]

Hi,

On 01/09/2017 02:01 PM, Baptiste Clenet wrote:
> Hi,
> 
> In order to optimize the statcksize of a thread, I would like to know
> when the thread uses the maximum of its stack (maximum can be 3/4 of
> the stack for instance)
> How can I find this "time"?
> 

In my opinion:

Welcome to the embedded world problems...

I thought about to have some coverage compiler and check always the
maximum stacksize... That's my idea to get such value... but then you
need to reach 100% coverage of the thread -> good luck with that. :-)

It would maybe nice to have such feature in RIOT to coverage his "little
tiny thread application" where you could reach your 100% coverage...

Maybe also possible on other stacks for testing in native application...
and also check ISR stack size. It think it's a good research topic for
somebody who looking for academic work. :-)

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

[riot-devel] Stacksize optimization

[Baptiste Clenet]

Hi,

In order to optimize the statcksize of a thread, I would like to know
when the thread uses the maximum of its stack (maximum can be 3/4 of
the stack for instance)
How can I find this "time"?

Cheers,

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

[riot-devel] Riot commerical support Request

[Atif Shabbir]

Hello RIOT OS Developers,

  we are interested to use 
the RIOT OS in our product. We are looking for some support
  our goal is to use the 
RIOT OS in visualgdb. We are interested in the RPL Section of the RIOT OS.


1-  We are using Nordic Nrf52 Chip.

2-  We would like to import the RIOT OS into Visualgdb.

3-  We are interested if all the required file are included into the 
project instead on using the default make file.

4-  Some more information will be discus on phone.

5-  We are expecting as real commercial support.

As we are located in Germany. If the some developer belong to Germany too that 
would be great. Otherwise EU is also fine.
If you are interested then please share your contact detail with us then we 
will discuss in more details and we will also discus
About your requirements.






atif shabbir  | entwicklung

t +49 8841 6780 330
atif.shab...@werk11.de

werk11 gmbh
untermarkt 8 | 82418 murnau | germany
t +49 8841 6780 330 | fax +49 8841 6780 331 | 
www.werk11.de
USt.ID.Nr. DE296539800 | HRB 213194

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht 
gestattet.

This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorised 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden.

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

Re: [riot-devel] Strange errors

[Oleg Hahm]

Hi Ilias!

On Mon, Jan 09, 2017 at 11:54:46AM +0100, Ilias Seitanidis wrote:
> Today I came up with some strange errors while creating a new project.
> The first one is "'CREATE_STACKTEST' undeclared (first use in this function)
>  THREAD_PRIORITY_MAIN - 1, CREATE_STACKTEST,"
> 
> my code is "kernel_pid_t pid = thread_create(second_thread_stack,
> sizeof(second_thread_stack),
> THREAD_PRIORITY_MAIN - 1, CREATE_STACKTEST,
> second_thread, NULL, "pong");"
> -I used the same code ~7 months ago and it was working.

CREATE_STACKTEST got renamed some time ago:
$ git grep CREATE_STACKTEST
core/include/thread.h: *  @ref THREAD_CREATE_STACKTEST  | measures the stack's 
memory usage

I.e., it's called THREAD_CREATE_STACKTEST now.

(See also http://doc.riot-os.org/group__core__thread.html)

> The second one is "implicit declaration of function 'xtimer_usleep_until'
> [-Werror=implicit-function-declaration]
>   xtimer_usleep_until(_wakeup, INTERVAL);"
> 
> - I use the same code in another project and works

xtimer_sleep_until() got refactored to xtimer_periodic_wakeup() in
4449ba493350a3683d48a91934aa767409c42ec7

$ git log | grep -B2 xtimer_usleep_until
Merge pull request #5612 from gebart/pr/xtimer-periodic-wakeup
xtimer: Refactor xtimer_usleep_until and rename to xtimer_periodic_wakeup

(See also http://doc.riot-os.org/group__sys__xtimer.html)

Cheers,
Oleg
-- 
panic("Unable to find empty mailbox for aha1542.\n");
linux-2.2.16/drivers/scsi/aha1542.c


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Strange errors

[Kaspar Schleiser]

Hi Ilias,

happy new year to you!

On 01/09/2017 11:54 AM, Ilias Seitanidis wrote:
> The first one is "'CREATE_STACKTEST' undeclared (first use in this function)
> 
> -I used the same code ~7 months ago and it was working.

The define has been renamed, it is now called "THREAD_CREATE_STACKTEST".

> The second one is "implicit declaration of function
> 'xtimer_usleep_until' [-Werror=implicit-function-declaration]
>   xtimer_usleep_until(_wakeup, INTERVAL);"
> 
> - I use the same code in another project and works 

This function is now called "xtimer_periodic_wakeup()".

Just replacing the old names with the new ones should fix compiling.

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