Re: [riot-devel] Notification: 6tisch ETSI Plugtest @ Fri Nov 6 - Sun Nov 8, 2015 (RIOT Events)

[Thomas Watteyne]

:-)

On Thu, Nov 5, 2015 at 5:57 PM, Oleg Hahm  wrote:

> Hi all,
>
> please note that there is actually a small mistake in this calendar entry:
> we
> will participate in the ETSI plugtest for 6lo, _not_ 6tisch.
>
> Thanks for pointing this out, Thomas!
>
> Cheers,
> Oleg
>
> Am Thu, Nov 05, 2015 at 08:01:00AM + schrieb Google Calendar:
> > This is a notification for:
> >
> > Title: 6tisch ETSI Plugtest
> > ETSI Plugtest co-located with IETF 94
> > http://www.etsi.org/news-events/events/1003-6lo-plugtests
> >
> > When: Fri Nov 6 - Sun Nov 8, 2015
> > Where: Yokohama, Kanagawa Prefecture, Japan
> > Calendar: RIOT Events
> > Who:
> > * Peter Schmerzl - creator
> >
> > Event details:
> https://www.google.com/calendar/event?action=VIEW=dmpjM2dna3ZrZ3Vlb25pYmsxaWsxNmJjOWsgazNxbDhzZXR2N2w0OG9mbm9sMHRmdXU2dHNAZw
> >
> > Invitation from Google Calendar: https://www.google.com/calendar/
> >
> > You are receiving this email at the account peterschme...@gmail.com
> because
> > you set a notification for this event on the calendar RIOT Events.
> >
> > You can change your notifications for specific events in the event
> details
> > page in https://www.google.com/calendar/.
> >
> > Forwarding this invitation could allow any recipient to modify your RSVP
> > response. Learn more at
> > https://support.google.com/calendar/answer/37135#forwarding
>
> > ___
> > devel mailing list
> > devel@riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
>
>
> --
> panic("floppy: Port bolixed.");
> linux-2.2.16/include/asm-sparc/floppy.h
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>


-- 
___

Thomas Watteyne, PhD
Research Scientist & Innovator, Inria
Sr Networking Design Eng, Linear Tech
Founder & co-lead, UC Berkeley OpenWSN
Co-chair, IETF 6TiSCH

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

Re: [riot-devel] Notification: 6tisch ETSI Plugtest @ Fri Nov 6 - Sun Nov 8, 2015 (RIOT Events)

[Oleg Hahm]

Hi all,

please note that there is actually a small mistake in this calendar entry: we
will participate in the ETSI plugtest for 6lo, _not_ 6tisch.

Thanks for pointing this out, Thomas!

Cheers,
Oleg

Am Thu, Nov 05, 2015 at 08:01:00AM + schrieb Google Calendar:
> This is a notification for:
> 
> Title: 6tisch ETSI Plugtest
> ETSI Plugtest co-located with IETF 94
> http://www.etsi.org/news-events/events/1003-6lo-plugtests
> 
> When: Fri Nov 6 - Sun Nov 8, 2015
> Where: Yokohama, Kanagawa Prefecture, Japan
> Calendar: RIOT Events
> Who:
> * Peter Schmerzl - creator
> 
> Event details: 
> https://www.google.com/calendar/event?action=VIEW=dmpjM2dna3ZrZ3Vlb25pYmsxaWsxNmJjOWsgazNxbDhzZXR2N2w0OG9mbm9sMHRmdXU2dHNAZw
> 
> Invitation from Google Calendar: https://www.google.com/calendar/
> 
> You are receiving this email at the account peterschme...@gmail.com because
> you set a notification for this event on the calendar RIOT Events.
> 
> You can change your notifications for specific events in the event details
> page in https://www.google.com/calendar/.
> 
> Forwarding this invitation could allow any recipient to modify your RSVP
> response. Learn more at
> https://support.google.com/calendar/answer/37135#forwarding

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


-- 
panic("floppy: Port bolixed.");
linux-2.2.16/include/asm-sparc/floppy.h


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

Re: [riot-devel] RIOT os and CC430

[Attilio Dona]

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 some info and a recipe to try get a working RIOT port to "the new"
msp-elf-gcc.

I have arranged a build for chronos board with the fork:

https://github.com/attdona/RIOT (some minor patches about removing
duplicated types definition and the new msp430 gcc ISR syntax)

and with the following compiler version (not mandatory, just for
reference):

msp430-elf-gcc -v
Using built-in specs.
COLLECT_GCC=msp430-elf-gcc
COLLECT_LTO_WRAPPER=/usr/local/gcc-msp430-elf-dev-20141215/libexec/gcc/msp430-elf/5.0.0/lto-wrapper
Target: msp430-elf
Configured with: /home/attilio/MIOT/gcc_repo/gcc/configure
--prefix=/usr/local/gcc-msp430-elf-dev-20141215 --target=msp430-elf
--with-newlib --enable-languages=c
Thread model: single
gcc version 5.0.0 20141105 (experimental) (GCC)

The ugly part it is that I needed to patch the compiler !!!

You will find the instructions into cpu/msp430-common/gcc-patch/README.md

I've just verified that the platform build successfully but I have not
tested the fw.

Let me know if it works for you.

ciao
Attilio



On Thu, Oct 29, 2015 at 7:35 PM, Viktor Váczi 
wrote:

> Hi!
> I try to port riot to CC430F5137 using a panstamp board (
> http://www.panstamp.com/product/197/ ). I didn't have any luck with the
> old msp430debug package which i've found in the latest ubuntu. The first
> thing I've tried to do is to get a simple UART example working, but when
> I've tried to enable the interrupts with:
>  __bis_SR_register(LPM0_bits + GIE);   // Enter LPM0, interrupts
> enabled
> the whole thing freezed. I guess that some other kind of interrupt happens
> all the time, but I haven't been able to debug it ( yet ).
> So I've started using TI's / redhat's gcc compiler, and it worked just ok
> ( under windows ). So I've moved on to this compiler, which I've installed
> by this tutorial:
> http://www.simplyembedded.org/tutorials/compile-install-msp430-gcc/
> I've tried to use chronos version for the first time, I've deleted all the
> LCD headers, and modified stdio.h a little bit, so it doesn't looks for
> these kind of files. The compilation worked previously with the obsolete
> mspgcc, so that worked somewhat.
> Now when I do BOARD=chronos make then it doesn't finds msp430-gcc. So I've
> moved everything from opt/msp430-toolchain/bin ( the place where I've
> installed the new TI mspgcc ) to bin, so it found the new mspgcc compiler.
> Now it was missing the header file, I've modified the makefile.include so
> it found it now. There were some missing stuff , but I've solved these
> problems, but now I have this error:
> as: unrecognized option '-mP'
> I've did a verbose output with make -n, this came out:
> http://pastebin.com/BDQjdaJG
> I have found -mP but only with msp430-gcc, and there is no as program as
> far as I know, so I doesn't really understand this.
>
> My first question is: how to install this compiler properly, so that
> whenever I use msp430-gcc then this new compiler will be called? I've also
> tried to use the installersh file from ti, but it doesn't install it to
> /bin or anything in the $PATH so I can't use it with the current makefiles.
> The current solution is.hmm kind of ugly and doesn't works :)
>
> The second question: Should I use the obsolete ti compiler instead? What
> causes this bug?
>
> The third one is: What is this as / -mp thing?
>
> Thanks for any help, and sorry for my ugly English.
> Viktor
>
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] usb device stack ...

[Johann Fischer]

Hello hardworking developers,

if someone wants to test "USB Device Stack # 3890" on Phytec boards or 
want to use the Board (PhyNode, pba-d-01-kw2x) as a boarder router, I 
have completed the PR with instructions for the modifications [1].


[1] https://github.com/RIOT-OS/RIOT/pull/3890#issuecomment-154106351

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

Re: [riot-devel] How to Choose Network Interface to Send Packets Over

[Mark Solters]

[Sorry if this message ends up in the wrong place or as a separate thread
-- I was stuck in digest mode and it was not clear to me how to reply to a
single message.]

Oleg, thank you very much for the description of and reference to the
packet routing protocol -- I did not realize that RIOT followed the
contents of the RFC document so precisely.

I now know that the process of deciding what network interface to route a
packet to comes down to (at first) finding an on-link match between the
destination IP address and the available interfaces (if one exists).  This
is done by examining the prefixes for a match.

In my case, I have two interfaces, ethernet and 802.15.4, with
auto-assigned local IPV6 addresses:

[Iface 6, 802.15.4] = fe80::5846:346f:c2da:ad12/64
[Iface 7, ethernet] = fe80::204:25ff:fe19:1a3e/64

So I think my problem is as follows.  I am transmitting packets to a
destination IP that reads:

fe80::3a2c:4aff:fe6e:19f3

And therefore the fe80:: could match the 64-bit prefix of *either* of those
interfaces.  I think that the request is then being routed to the first
match, which is 802.15.4, which is incorrect, because that IP address is
actually an ethernet neighbor, not a radio one.  When I disable Iface 6,
the packets DO reach their destination on Iface 7.

Maybe I'm wrong; but it would seem that my problem is, I need to change the
prefix of my 802.15.4 interfaces to something other than fe80:: so they do
not conflict with the ethernet interface's prefix, which is beyond my
control.

Am I on the right track here?  I do not as of yet fully comprehend the
addition of the global affe::2 address in the gnrc_border_router example;
and additionally, I am uncertain if my reasoning here is still flawed due
to a deeper failure to internalize the core concept behind RIOT's
implementation of the packet routing algorithm.

Many thanks,

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