Carsten Bormann wrote:
> https://twitter.com/c4bo/status/676393852798922752
OK, that may have been a bit opaque :-)
http://www.barrgroup.com/Embedded-Systems/How-To/Malloc-Free-Dynamic-Memory-Allocation
https://twitter.com/c4bo/status/676393852798922752
:-)
Grüße, Carsten
Sam Kumar wrote:
> Hello,
> I noticed that there is a "oneway-malloc" module in RIOT OS. It appears
> to be a thin wrapper around sbrk that only supports allocating memory,
> not freeing it.
>
> I am doing some development
Hi,
NETOPT_ACK_REQ is currently not handled by the at86rf2xx driver but IIRC
NETOPT_AUTOACK covers both for that device (didn't check that).
Best
Peter
Am 09.08.2016 um 16:44 schrieb Simon Brummer:
Hi Oleg,
netopt_enable_t opt = NETOPT_DISABLE;
gnrc_netif_get(ifs);
gnrc_netapi_set(ifs[0],
Hi Simon!
On Tue, Aug 09, 2016 at 04:44:40PM +0200, simon wrote:
> netopt_enable_t opt = NETOPT_DISABLE;
> gnrc_netif_get(ifs);
> gnrc_netapi_set(ifs[0], NETOPT_AUTOACK, 0, , sizeof(opt));
> gnrc_netapi_set(ifs[0], NETOPT_ACK_REQ, 0, , sizeof(opt));
>
>
> Did the trick. So there is a way to
Hi Ludwig!
On Tue, Aug 09, 2016 at 02:30:25PM +0200, Ludwig Knüpfer wrote:
> Without any further insights I would say your case is different because the
> board is actively maintained, used, and can be bought.
> In the case of the FU boards I had in mind (msb430*) none of these points is
> true.
Hi Simon!
On Tue, Aug 09, 2016 at 02:33:56PM +0200, simon wrote:
> Currently I am testing my TCP implementation between two samr21 Boards
> and a Raspberry Pi as sniffing Probe in between.
>
> My measured network dump contains a few unexpected retransmissions and
> i am unable to distinguish
[ek-lm4f120-xl board can't be bought anymore, only its replacement TivaC can
(and it is not supported by RIOT, at least at the moment)]
It is actively maintained... sort of. I have the feeling that no RIOT developer
has time for it. It is not listed on the RIOT wiki and it is hard to find
Hello Everybody,
Currently I am testing my TCP implementation between two samr21 Boards
and a Raspberry Pi as sniffing Probe in between.
My measured network dump contains a few unexpected retransmissions and
i am unable to distinguish between retransmissions caused by 15.4 and
retransmissions
Hi I have performed the following in order to setup a test network of
devices on Ubuntu 14.04 with Vagrant and vbox. (see below)
I am getting the following error:
ifconfig 4 add 2001:db8::1
error: unable to add IPv6 address.
I cant get around this.
I believe I am using the native chipset in
Hey,
This discussion is also related to
https://github.com/RIOT-OS/RIOT/pull/5412#issuecomment-237688208
I'm trying to enhance support for ek-lm4fxl-120 board, which is not as popular
as stm boards...
It's a bit complicated to find reviewers with some extra time for reviewing,
and even more
Hey!
On Tue, Aug 09, 2016 at 02:06:07PM +0200, Ludwig Knüpfer wrote:
> I'm all for cleaning up stale boards, especially I'd they are as hard to
> obtain as for example the FU boards.
Well, hopefully this situation is about to change once the RasPi
infrastructure is in place.
Cheers,
Oleg
--
Yo
All of them?
Am 9. August 2016 14:11:12 MESZ, schrieb Martine Lenders
:
>Hi Ludwig,
>well at least the FU boards are now "obtainable" through the IoT-Lab
>testbed. ;-)
>
>Cheers,
>Martine
>
>2016-08-09 14:06 GMT+02:00 Ludwig Knüpfer
>:
>>
> P.S: Anyone who have tried to run an app on Arduino Uno, please be kind to
> tell me if they succeed!
What I have personnaly tested on real hardware and works fine is :
- hello_world
- timer_periodic_wakeup
- ipc_pingpong
from RIOT/examples/ directory
--
« On ne résout pas un problème
Hi Ludwig,
well at least the FU boards are now "obtainable" through the IoT-Lab
testbed. ;-)
Cheers,
Martine
2016-08-09 14:06 GMT+02:00 Ludwig Knüpfer :
> Hi,
>
> I'm all for cleaning up stale boards, especially I'd they are as hard to
> obtain as for example the
Hi,
I'm all for cleaning up stale boards, especially I'd they are as hard to obtain
as for example the FU boards.
If I'm not mistaken this would also enable the removal of at least one legacy
driver interface (I have some GPIO API in mind).
Cheers,
Ludwig
Am 9. August 2016 13:52:56 MESZ,
Hi again.
The point is that the VM hasn't got an OS.
I mean that when I try to run the app on VM, the VM must not have
Linux/MacOSX/Windows or whatever.
The only thing that exists on the VM must be the RIOT app.
From that point of view, yes, an OS must be running.
P.S: Anyone who have
I agree with dropping qemu-i386
On the same subject, would it make sense to clean up some other boards
with less than ideal support?
chronos is one board which I frequently run into trouble with because
it is never up to date with the other platform implementations,
especially the stdio is very
Hi,
If you have been told to write an application that runs on a VM without using
an OS, RIOT is not the answer because it is an OS, so your application is using
an OS.
Apart from that there is no difference between running on native and running on
QEMU from the application point of view.
As
So a simple Clock-Chronometer written in shell script, wouldn't work for now?
Από: devel εκ μέρους του Laurent Navet
Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 2:26 μμ
Προς: RIOT OS kernel developers
Θέμα: Re:
> Any chances that I can run on Arduino Uno?
Arduino uno is not fully functional for now, depends on your
application needs
Basically, UART and timers should work, gpio are untested, no pwm
Fetch #5590 and #5451 PR and try
Good luck,
--
« On ne résout pas un problème avec les
Okay I understand.
Any chances that I can run on Arduino Uno?
Από: devel εκ μέρους του Rene Kijewski
Στάλθηκε: Τρίτη, 9 Αυγούστου 2016 1:53 μμ
Προς: devel@riot-os.org
Θέμα: Re: [riot-devel] Problem with
Hi!
On Tue, Aug 09, 2016 at 10:34:19AM +0200, Martine Lenders wrote:
> we now have the third person wondering about the qemu-i386 port.
For the record: I count only two.
Otherwise: +1 for the proposal.
Cheers,
Oleg
P.S. Should we drop support for the Spark as well?
--
I'm working on a
Am Tue, 9 Aug 2016 10:34:19 +0200
schrieb Martine Lenders :
> we now have the third person wondering about the qemu-i386 port. Fact
> is, it doesn't work (we do not even have the unittests activated
> anymore). Is there a reason why we did not drop it yet (except making
>
Am Tue, 9 Aug 2016 10:21:51 +
schrieb MiTsArAs Jimaras :
> Because I have told to do so from my university!
>
> I can't explain further because I DON'T KNOW WHY!
Hi,
then either ask your prof / TA what your objective is or drop the class.
You may quote the author of
Hi,
we now have the third person wondering about the qemu-i386 port. Fact
is, it doesn't work (we do not even have the unittests activated
anymore). Is there a reason why we did not drop it yet (except making
all the good work by René void)? Or are we planning to provide better
support for it in
Hahahahaha it's that WHY again!
Because I have told to do so from my university!
I can't explain further because I DON'T KNOW WHY!
Από: devel εκ μέρους του Ludwig Knupfer
Στάλθηκε: Τρίτη, 9 Αυγούστου
Hi,
Yes, you said that you want do that before but you never explained: *WHY* do
you want to do that?
Also: RIOT is an OS!
Cheers,
Ludwig
Am 9. August 2016 11:15:26 MESZ, schrieb MiTsArAs Jimaras
:
>I made trouble once, speaking about this project, but I am going at it
I made trouble once, speaking about this project, but I am going at it again!!
I want my app to run on a bare VM. Meaning that I want my VM to boot to my app
without an OS been installed in the VM emulator. Any solutions would be very
helpful!
P.S: On the other hand, I have a raspberry pi on
Hi!
On Tue, Aug 09, 2016 at 08:27:04AM +, MiTsArAs Jimaras wrote:
> Now I have another problem!
>
> I compile on native board, and everything is alright.
>
> When I am trying to compile on qemu-i386, it seems to start, but I get no
> results.
Please note that support for i386 is rather
Hi,
It's difficult to say anything about this without seeing the actual source code.
Cheers,
Ludwig
Am 9. August 2016 10:27:04 MESZ, schrieb MiTsArAs Jimaras
:
>Problem solved.
>
>Now I have another problem!
>
>I compile on native board, and everything is alright.
>
Oops, forgot to provide the link for [1]:
https://github.com/RIOT-OS/RIOT/wiki/Family%3A-native#dependencies
2016-08-09 9:19 GMT+02:00 Laurent Navet :
> Hi,
>
> Have you multilib support enabled and installed ?
>
> https://github.com/RIOT-OS/RIOT/wiki/Family:-native
>
>
Hi,
have you installed gcc-multilib and the other dependencies [1]?
Cheers,
Martine
2016-08-09 9:02 GMT+02:00 MiTsArAs Jimaras :
> Hello to all.
> I am trying to build an app with "make clean all flash term" on native
> platform, and all I get as a result that:
>
>
Hi,
Have you multilib support enabled and installed ?
https://github.com/RIOT-OS/RIOT/wiki/Family:-native
2016-08-09 9:02 UTC+02:00, MiTsArAs Jimaras :
> Hello to all.
> I am trying to build an app with "make clean all flash term" on native
> platform, and all I get as a
Hello to all.
I am trying to build an app with "make clean all flash term" on native
platform, and all I get as a result that:
Building application "time" for "native" with MCU "native".
"make" -C /home/d/RIOT/boards/native
"make" -C /home/d/RIOT/boards/native/drivers
"make" -C
34 matches
Mail list logo