mirror of https://github.com/ARMmbed/mbed-os.git
afba4e1eb5
* Fix for calculating CAN timing settings. NominalPrescaler value needs to be as high as possible to ensure a good approximation of the target CAN speed. Previous usage of macro IS_FDCAN_DATA_TSEG1 refers to (unsupported by Mbed ) FDCAN CAN controller settings and leads to too low prescaler values. Usage Macro IS_FDCAN_NOMINAL_TSEG1 yields optimum results. See also correct macro usage in line #158. * Add complete support of DHCP relay interface ID option RFC3315 specifies the following: "The relay agent MAY send the Interface-id option to identify the interface on which the client message was received. If a relay agent receives a Relay-reply message with an Interface-id option, the relay agent relays the message to the client through the interface identified by the option." The current implementation of the DHCP relay reply handling, the interface ID field from the server response is ignored. Managing the interface ID is very important especially as DHCP requests/replies use link-local addresses. The consequence of this is that the interface must always be specified because the routing layer cannot guess the correct interface. Moreover, Mbed provides a mechanism to enable/disable the interface ID option on a DHCP relay instance, so it is important to fully support it. The reason why this issue has not been discoverd until now is that the DHCP relay is mainly used on systems that use only one interface (such as Wi-SUN routers). By default, when no interface ID is specified for the socket, the latter will choose 6loWPAN interface by default. This means that if two interfaces are used on the same device, the 6loWPAN interface is always selected. The commit adds code to retrieve the interface-id value contained within the DHCP relay reply message and write it to a control message header that is added to the socket message. This tells the socket which interface to choose. If the interface-id option is not enabled on the relay, this procedure is simply ignored. * Support Nuvoton target NUMAKER_IOT_M467 1. Based on alpha version BSP (85564a2716548e7b6d6a79a490c6d94a24cf9bcf) 2. Continuing above, tweak BSP: (1) Add EPWM_ConfigOutputChannel2() to enable below 1Hz and below 1% duty cycle for PWM output (m460_epwm.h/c). (2) Add dummy RTC_WaitAccessEnable() for consistency with previous ports (m460_rtc.h). 3. Target NuMaker-M467HJ V0.1 board temporarily 4. Support Arduino UNO form factor for NUMAKER_IOT_M467 target 5. Enable export to Keil/IAR project - tools/arm_pack_manager/index.json - tools/export/iar/iar_definitions.json * M467: Fix Greentea reset_reason test failure HRESETRF is combined reset flag. Filter it out to avoid interference with reset reason check. * M467: Support HyperRAM 1. For GCC, support multi-block .data/.bss initialization 2. HyperRAM is mapped to two regions: 0x0A000000 and 0x80000000 According to default system address map, 0x0A000000 is located at 'Code' region and 0x80000000 at 'RAM' region. With MPU enabled on Mbed OS, 'Code' region is write-never and 'RAM' region execute-never. 0x80000000 is chosen because 'RAM' regioin is naturally for HyperRAM. 3. Configurable multi-function pins for HBI 4. To locate code/data at external HyperRAM: - Specify __attribute__((section(".text.nu.exthyperram"))) for RO/.text/readonly section type Invoke mbed_mpu_manager_lock_ram_execution()/mbed_mpu_manager_unlock_ram_execution() to run HyperRAM code - Specify __attribute__((section(".data.nu.exthyperram"))) for RW/.data/readwrite section type - Specify __attribute__((section(".bss.nu.exthyperram"))) for ZI/.bss/zeroinit section type 5. Add readme * Config for M460 EMAC * Add M460 EMAC driver * Adjust M460 EMAC RX/TX buffer * M467: Fix EMAC compile error with IAR * M467: Support Crypto SHA/ECC H/W 1. Prepare crypto common code 2. Support list - SHA - ECC NOTE: AES/RSA are to support in other works NOTE: Compared to M487, M467's SHA supports context save & restore (DMA Cascade mode) and so no software fallback is needed. NOTE: M467's ECC, following M487, goes partial-module replacement and it can just improve primitives e.g. point addition/doubling by 2X, and cannot improve high level point multiplication because MbedTLS doesn’t open it. To improve performance best, full-module replacement is needed. NOTE: Continuing above, add support for Montgomery curve * M467 H/W AES self-test pass * M467 Support crypto GCM H/W * M467: GCM support one simple mode instead of using composite GHASH & CTR MODE * Update M467 AES-GCM to pass AWS-IoT test * Update M467 AES-GCM for H/W gcm in-buffer creteria * M467: Improve Crypto H/W wait helper routine Add crypto_xxx_wait2 helper routine to replace crypto_xxx_wait for Crypto H/W control * M467: Seed PRNG with TRNG for SCAP According to TRM, it is suggested PRNG be seeded by TRNG on every Crypto H/W reset. * M467: Support Crypto RSA H/W 1. Crypto RSA H/W supports 1024/2048/3072/4096 key bits. Fall back to software implementation for other key bits. 2. For decrypt, if MBEDTLS_RSA_NO_CRT isn't defined, go CRT, or normal. 3. For decrypt, when blinding (f_rng != NULL), enable SCAP mode. 4. Recover from Crypto RSA H/W failure: (1) Enable timed-out wait to escape from RSA H/W trap (2) On RSA H/W timeout, stop this RSA H/W operation (3) Fall back to S/W implementation on failure NOTE: RSA 4096 key bits can fail with default mbedtls configuration MBEDTLS_MPI_MAX_SIZE. Enlarge MBEDTLS_MPI_MAX_SIZE to 1024 or larger if this feature is required. NOTE: Fixed in BSP RSA driver, for non-CRT+SCAP mode, temporary buffer for MADDR6 requires to be key length plus 128 bits. NOTE: Fixed in BSP RSA driver, DMA buffer must be 4-word aligned, or RSA H/W will trap. * M467 Support crypto AES-CCM H/W with one-shot & cascade mode * M467: Support Crypto ECC H/W in full-module replacement 1. Replace ecp.c full-module, and other ec modules dependent on ecp.c (ecdh.c/ecdsa.c/ecjpake.c) will improve followingly. 2. Recover from Crypto ECC H/W failure: (1) Enable timed-out wait to escape from ECC H/W trap (2) On ECC H/W timeout, stop this ECC H/W operation (3) Fall back to S/W implementation on failure 3. Support Short Weierstrass curve 4. Support Montgomery curve Montgomery curve has the form: B y^2 = x^3 + A x^2 + x (1) In S/W impl, A is used as (A + 2) / 4. Figure out its original value for engine. |
||
|---|---|---|
| .. | ||
| doxygen | ||
| nanostack | ||
| source | ||
| .gitattributes | ||
| .gitignore | ||
| .mbedignore | ||
| CMakeLists.txt | ||
| DOXYGEN_FRONTPAGE.md | ||
| Doxyfile | ||
| LICENSE-Apache-2.0 | ||
| LICENSE-BSD-3-Clause | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| include_dirs.mk | ||
| mbed_lib.json | ||
| sources.mk | ||
README.md
ARM Mesh networking stack
This repository contains the ARM mesh networking stack that provides support for the following mesh protocols:
- 6LoWPAN with Neighbor Discovery (ND) and Mesh Link Establishment (MLE)
- Wi-SUN
All networking stacks are using IEEE 802.15.4 based radios.
The full documentation is hosted in Mbed OS documentation.
On mbed OS, mesh networking stacks can be used through Mbed Mesh API and Network Socket API.
To see, how the mesh networking stack works, check the example application mbed-os-example-mesh-minimal.
6LoWPAN with ND and MLE
This networking stack is using standard 6LoWPAN and uses:
- Neighbor Discovery Protocol (RFC4861) to locate other devices in the mesh network.
- Mesh-Link-Establishment (draft-kelsey-intarea-mesh-link-establishment-06) is used for establishing and configuring secure radio links.
Wi-SUN
Wi-SUN (Smart Utility Networks) specification is standardized by Wi-SUN Alliance.
License
The software is partially provided under a Apache 2.0 license and partially BSD-3-Clause as described below.
This project also contains code from other projects as listed below. The original license text is included in those source files.
- Public header files are provided under Apache 2.0 license.
- Source code excluding Thread protocol, is provided under Apache 2.0
- Source code implementing Thread protocol is provided under BSD-3-Clause
- mDNS library is from FNET project and provided under Apache 2.0 license.