[riot-notifications] [RIOT-OS/RIOT] pkg/openwsn: re-integrate the network stack as a package (#13824)
notifications at github.com
Wed May 20 11:02:24 CEST 2020
@fjmolinas commented on this pull request.
> + * - To explore the channel hopping mechanism there are rather expensive
+ * multi-channel sniffers such as the BeamLogic 802.15.4 Site Analyzer that can
+ * sniff all channels simultaneously. Alternatively you can set up multiple
+ * separate sniffer devices locally or make use of the `sniffer_aggregator` on
+ * the IoT-LAB testbed.
+ * - There is a collection of external tools to interact with the IoT nodes from
+ * a host computer via `openserial`. Please refer to the
+ * [OpenWSN software](https://github.com/openwsn-berkeley/openwsn-sw) repository
+ * for further information.
+ * ## Todos
+ * - `sctimer` to trigger an ISR immediately using sw isr.
+ * - `RTT_FREQUENCY` is not configurable for most platforms, implementations
+ * should be adapted to make this configurable to be able to set RTT_FREQUENCY
+ * to 32768Hz or the closer possible value.
Yes, for most platforms the clock is 32Khz, but the define `RTT_FREQUENCY` is sometimes fixed at a value, if its too small (e.g. 1Hz) then the timer will not operate adequately enough even when shifted (since this is still in a trick to fake a "faster" timer at the cost of some tick inaccuracy by loosing the amount of bits you shift). And when you scale or shift there is still some cost, whether it is tick inaccuracy or conversion time, so when possible you would still want to set it to 32768.
I've moved some platforms to be able to configure `RTT_FREQUENCY`, e.g. `stm32` and `nrf5x`, but I haven't done it for others like `sam0` (I'm just lucky that there the fixed value is 32768).
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications