Hello devel team,
I forward my question to you. I’m having some issues compiling the project sixlowpan for msp430, due to some basic functions that are missing (like stdin and sscanf).
Have you compiled this project for the ws430-v1_4 board? if yes, wich compiler version are you using?
The same for the stm32f4discovery board, since the compiler version that you propose in the “Getting started” guide is not compatible with cortex-m4 architectures.
Thanks in advance!
Best regards.
Francisco Javier Acosta Padilla PhD Student at TRISKELL and ACES teams INRIA Rennes, France +33 2 99 84 73 42 +33 7 61 94 04 28 -------- Original Message --------
Hi,
Have you compiled this project for the ws430-v1_4 board? if yes, wich
compiler version are you using?
I tried this, with the msp430-gcc version 4.6.3, however the compiler
complained of about 16k missing. I do not think there is any chance to get
the current 6lowpan implementation on a msp430f16xx.
Regards,
Milan
Hi,
The same for the stm32f4discovery board, since the compiler version that you propose in the "Getting started" guide is not compatible with cortex-m4 architectures.
for stm32f4xx i use : "GNU Tools for ARM Embedded Processors" https://launchpad.net/gcc-arm-embedded.
Stefan
Hi!
>I tried this, with the msp430-gcc version 4.6.3, however the compiler
>complained of about 16k missing. I do not think there is any chance to get
>the current 6lowpan implementation on a msp430f16xx.
now that sucks. can we get that running? sounds like a good example
for mature optimization...
I fully agree with Kaspar and I think this should be an important goal for the
next release. I guess the planned refactoring of the network stack will help
us a lot to see where the memory is wasted.
However, when I try to build the sixlowpan project for the wsn430-v1_3b
platform, there are "just" 3kB missing.
Cheers,
Oleg
Hi Francisco,
I forward my question to you. I'm having some issues compiling the
project sixlowpan for msp430, due to some basic functions that are
missing (like stdin and sscanf).
the missing stdin for MSP430 based platform is a known issue:
https://github.com/RIOT-OS/RIOT/issues/21
But since all platforms should have a working UART driver by now, this seems
easily solvable.
sscanf is missing, too, but can be replaced:
https://github.com/RIOT-OS/projects/pull/34
The missing ssize_t goes into RIOT with
https://github.com/RIOT-OS/RIOT/pull/195
The next missing thing is the missing calloc() for MSP430, but this should be
pretty easy to solve, too.
Cheers,
Oleg
Hi Oleg,
Thank you so much for the answers, now I subscribed to the mailing list, so I can receive the messages by myself.
I'm having that issue about the memory, so I'll see if we can do some optimizations for reducing code size. However, we have some documentation about this example? Maybe I can adapt the code only to my needs and run my application example for the experiment that I'm trying to deploy.
Thanks again!
Cheers,
Francisco