Re: [riot-devel] Ceedling

Some time ago I managed to write some tests with Unity. It is not difficult to integrate into RIOT build system. As prerequisite you need ruby (sudo apt install ruby) and Unity installed somewhere (/opt/Unity-master) My opinionated recipe was to create the module libunity (and libcmock): sys

Re: [riot-devel] OpenOCD threads support

Hi Vincent, just a quick "black box" test ... openocd master branch with patch 4256 works on my board (cc3200-launchxl) Waiting to see this patch merged! Greetings Attilio Open On-Chip Debugger 0.10.0+dev-00199-g667cf951 (2017-10-17-19:45) Licensed under GNU GPL v2 For bug reports, read

Re: [riot-devel] About CC3200 RF support in RIOT OS

project with the same, can you share me the > link? > > Thanks, > Ameya Joshi > > > On Tue, Jun 6, 2017 at 2:19 PM, Attilio Dona <attilio.d...@gmail.com> > wrote: > >> Hy Ameya, >> >> nice to meet you >> >> You need to write an OS adapta

Re: [riot-devel] About CC3200 RF support in RIOT OS

Hy Ameya, nice to meet you You need to write an OS adaptation layer for cc3200 simple link driver if you want use wifi. Some time ago I wrote a preliminary adaptation layer but I did not share publicly. Please let me understand if I can share something useful, I'm thinking about creating a

Re: [riot-devel] Support for cc3200

Just few considerations, I hope they are useful I implemented the WLAN support using the Texas Instrument simplelink driver. It is something I never shared because it worked fine for me but it was not a state of the art piece of software, it lacks review and clean up ... My approach was to

Re: [riot-devel] RIOT, Windows, and Code Composer Studio

project, the compiler you use, ecc ecc, but I hope this may help you to go in the right direction. Attilio On Thu, Jun 23, 2016 at 3:34 PM, Clark Leach <clark.le...@gmail.com> wrote: > I don't suppose you want to share details? > > > On Wed, Jun 22, 2016 at 5:28 AM, Attil

Re: [riot-devel] Question about RIOT/tests/thread_msg

Hi Jianwen, thread_msg does a context switch between p3 and p1 because p1 does not have a message queue. The second message from p3 causes p3 to go into a blocked state and give up control otherwise the previous message will be lost. if in p1 a msg_queue is defined: void *thread1(void *arg) {

Re: [riot-devel] Low-power WAN

Hi All, Hi Dinh [ thanks for the citation :) ] To be precise I'm not yet porting RIOT to cc1310 ... nevertheless I'm very interested into the cc13xx new chips family and I'm trying to evaluate this first part in detail. ciao Attilio On Fri, Dec 11, 2015 at 2:55 PM, Nguyễn Quốc Đính

Re: [riot-devel] RIOT os and CC430

Hi Viktor, first a disclaimer: It is a lot of time that I don't work with msp430 silicon, so my knowledge it is not up to date, so please take this a a starting point: I think a RIOT msp430 maintainer could make a more clean and polite job than me, and I think it would be a GREAT thing. Now

Re: [riot-devel] OpenOCD-RTOS support for RIOT

Great job Daniel Just to report that I've tested OCD with this patch on TI cc3200 with a to be merged RIOT port [1] into mainstream and it works. [1] https://github.com/attdona/RIOT Cheers Attilio On Thu, Oct 15, 2015 at 6:58 PM, Daniel Krebs wrote: > Dear fellow

Re: [riot-devel] RIOT preview for TI cc3200

t; Am 25.09.2015 um 14:27 schrieb Attilio Dona: > > Ok, > > just for sharing a little roadmap I'm starting to work on the wifi module > integration. > > I need a little bit of time for this task, I think some weeks. > > Could make sense create a PR after the completion of

Re: [riot-devel] RIOT preview for TI cc3200

} } } On Thu, Sep 24, 2015 at 1:29 PM, Hauke Petersen <hauke.peter...@fu-berlin.de > wrote: > Hej, > > On 03.09.2015 23:22, Attilio Dona wrote: > > Ciao Kaspar, > > I agree with RIOT philosophy, so a rewrite could be a nice thing, but I > also think that

Re: [riot-devel] RIOT preview for TI cc3200

g > configuration file is already available. > You can put that in the board/dist. I am not sure but I think cc3200prog > binary may be license limited. > More over it will be helpful even for debugging :) > > Thanks and Regards, > Rakendra > > > On Tue, Sep 1, 2015 at 8:2

[riot-devel] RIOT preview for TI cc3200

Hello dear RIOTers, I've pushed a cc3200 (http://www.ti.com/product/cc3200) RIOT basic port here: https://github.com/attdona/RIOT SimpleLink Wi-Fi CC3200 LaunchPad is the working board ( http://www.ti.com/tool/cc3200-launchxl). This is my first contribution to RIOT, so it would be great if you

Re: [riot-devel] Changing the workflow.

Just for add a bit of documentation for helping discovering the best workflow: http://nvie.com/posts/a-successful-git-branching-model/ The post contains some good points in my opinion, for example the guideline that a feature branch have to exists in developer repo and not in origin. ciao

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

;) Cheers, Ludwig On Mon, Feb 23, 2015 at 09:26:34AM +0100, Attilio Dona wrote: Also for me the MACRO approach has to be considered in a design review, eventually in addition to a tracing API layer. Just to add my bit of experience with RIOT about porting msp430 family on new TI/redhat gcc