Make the period for the uip-ds6 periodic task configurable
Cooja: allow setting RSSI while sending and silence

It is now possible to set the RSSI while the radio is sending or when
no radiodata is received. This is now supported by all radiomediums
exept MRM. This also includes a GUI to configure the values.
CC2538: Add a Makefile rule to generate a final assembly listing.
Declare and Implement generic ICMPv6 handler management
Replace old switch-based ICMPv6 type/code management
Register generic handlers for ICMPv6 Echo Request / Reply
Register generic ICMPv6 handlers for IPv6 ND
Register generic ICMPv6 handlers for RPL
Register generic ICMPv6 handlers for ROLL TM
Added support to program Z1 far memory with BSL
Support verbosity control when building MSP430-based platforms with
the IAR compiler.
Support verbosity control when building for STM32W-based platforms
OBJECTDIR is defined by Makefile.include
Set the RAM and flash size based on the CPU configuration for STM32W
Fix CC2538 random_init lockup

Contiki sometimes fails to boot correctly and locks up in
random_init()

This problem only manifests itself for specific versions
of the arm-gcc toolchain and then again only for specific
levels of optimisation (-Os vs -O2, depending on the
value of the SMALL make variable)

The lockup is caused when we write an RFCORE XREG before
the RF clock ungating has taken effect, which in turn
only occurs depending on the assembly generated for those
two instructions:

  REG(SYS_CTRL_RCGCRFC) = 1;

  REG(RFCORE_XREG_FRMCTRL0) = 0x00000008;

This commit makes the RNG wait for the ungating to take
effect before attempting to write the register
Merge pull request #585 from g-oikonomou/generic-icmp6-in-hooks

Generic ICMPv6 input hooks
Merge pull request #633 from nfi/verbosity-control-msp430

Add support for verbosity control for building MSP430-based platforms with the IAR compiler.
[cooja] plugins/LogListener: Prevent from throwing
ArrayIndexOutOfBoundsException in case of empty logTable
[cooja] Set location of newly created plugins relative to second last activated plugin.

Setting the position based on the number
of total inner frames was very inflexible
and caused pad positioning for larger number
of frames.

Setting the location of new plugin frames
to the second last activated one tries to
meet two requirements:
- Avoid covering the last activated plugin frame,
i.e. the one that was active when new plugin
start was invoked.
- Set new plugin near an actively used desktop pane
location and allow 'diagonal stacking'
Merge pull request #640 from ejoerns/pull-req/cooja-loglistener-fix

[Cooja] plugins/LogListener: Prevent from throwing ArrayIndexOutOfBoundsException