You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Ludwig Knüpfer eda6328e21 documentation: update my name (Ortmann -> Knüpfer) 7 years ago
..
include documentation: update my name (Ortmann -> Knüpfer) 7 years ago
netdev2_tap documentation: update my name (Ortmann -> Knüpfer) 7 years ago
periph documentation: update my name (Ortmann -> Knüpfer) 7 years ago
Makefile sys: net: replace dev_eth with netdev2, adapt native tap driver 7 years ago
Makefile.include cpu: native: remove hwtimer_compat dependency 7 years ago
README.md native: remove uart0 7 years ago
irq_cpu.c documentation: update my name (Ortmann -> Knüpfer) 7 years ago
lpm_cpu.c documentation: update my name (Ortmann -> Knüpfer) 7 years ago
native_cpu.c documentation: update my name (Ortmann -> Knüpfer) 7 years ago
panic.c documentation: update my name (Ortmann -> Knüpfer) 7 years ago
startup.c documentation: update my name (Ortmann -> Knüpfer) 7 years ago
syscalls.c documentation: update my name (Ortmann -> Knüpfer) 7 years ago
tramp.S documentation: update my name (Ortmann -> Knüpfer) 7 years ago

README.md

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 pass the --db-attach parameter to Valgrind. E.g:

valgrind --db-attach=yes ./bin/native/default.elf tap0

Now, you will be asked whether you would like to attach the running process to gdb whenever a problem occurs.

In order for this to work under Linux 3.4 or newer, you might need to disable the ptrace access restrictions: As root call:

echo 0 > /proc/sys/kernel/yama/ptrace_scope

Network Support

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

make term PORT=tap0

Setting Up A Tap 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.

Daemonization

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.

Usage:

./bin/native/default.elf -d

Compile Time Options

Compile with

CFLAGS=-DNATIVE_AUTO_EXIT make

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