You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Kaspar Schleiser 26b99a57be cpu: native: add vfs wrappers 6 years ago
include Merge pull request #6434 from aabadie/petersen_typo 6 years ago
netdev2_tap cpu/native: adapt start-up and auto-init for multiple netdev2_tap 6 years ago
osx-libc-extra cpu/native: malloc.h for osx: fix doxygen, move 8 years ago
periph periph/hwrng: use void* buf for hwrng_read() 6 years ago
vfs cpu: native: add vfs wrappers 6 years ago
Makefile cpu: native: add vfs wrappers 6 years ago
Makefile.features native: support add periph/pm support 6 years ago
Makefile.include cbor: fix redefined macro error on macOS 7 years ago make: introduce netif_default pseudomodule 7 years ago
async_read.c cpu/native: allow multiple netdev2 tap devices 6 years ago
irq_cpu.c native: support add periph/pm support 6 years ago
native_cpu.c cpu: native: fix thread_yield_higher inisr() case 6 years ago
panic.c documentation: update my name (Ortmann -> Knüpfer) 8 years ago
startup.c cpu/native: adapt start-up and auto-init for multiple netdev2_tap 6 years ago
syscalls.c native: indicate interrupt status in ISR context 7 years ago
tramp.S native: add syscall-leave trampoline 7 years ago

Valgrind Support

Rebuild your application using the all-valgrind target like this:

make -B clean all-valgrind

That way native will tell Valgrind about RIOT's stacks and prevent Valgrind from reporting lots of false positives. The debug information flag -g is not strictly necessary, but passing it allows Valgrind to tell you precisely which code triggered the error.

To run your application run:

make term-valgrind

All this does is run your application under Valgrind. Now Valgrind will print some information whenever it detects an invalid memory access.

In order to debug the program when this occurs you can use the targets debug-valgrind-server and debug-valgrind. Therefore, you need to open two terminals and run:

make debug-valgrind-server

in the first one and run:

make debug-valgrind

in the seconde one. This starts per default gdb attached to valgrinds gdb server (vgdb).

Network Support

If you compile RIOT for the native cpu and include the netdev2_tap module, you need to specify a network interface like this:

make term PORT=tap0

Please note: in case you're using RIOT's default network stack, the GNRC stack, you may also use gnrc_netdev_default module and also add auto_init_gnrc_netif in order to automatically initialize the interface.

Setting Up A Virtual Network

There is a shellscript in RIOT/dist/tools/tapsetup called tapsetup which you can use to create a network of tap interfaces.

Usage: To create a bridge and two (or count at your option) tap interfaces:

../../dist/tools/tapsetup/tapsetup [-c [<count>]]

On OSX you need to start the RIOT instance at some point during the script's execution. The script will instruct you when to do that.

To delete the bridge and all tap interfaces:

../../dist/tools/tapsetup/tapsetup -d

For OSX you have to run this after killing your RIOT instance and rerun ../../dist/tools/tapsetup [-c [<count>]] before restarting.

Please note: If you want to communicate between RIOT and your host operating system, you must not use the tapsetup script, but create and activate the tap interface manually. On Linux you can do so, by calling

sudo ip tuntap add tap0 mode tap user ${USER}
sudo ip link set tap0 up


You can daemonize a riot process. This is useful for larger networks. Valgrind will fork along with the riot process and dump its output in the terminal.


./bin/native/default.elf -d

Compile Time Options

Compile with


to exit the riot core after the last thread has exited.