9b3e144 Removed kde_helper test files
451ac95 Merge branch 'release_internal' into release_external
d9976cf Merge branch 'master' into release_internal
0a6fb58 RPL parent update handle update
59b145b Fixed Ifdown / UP sequence and and discovery state set own hop to 0xff.
9103d68 Fixed dwell time, clock drift and timing accuracy values
56831ad Wi-sun BBR Slaac Ula support fix
add63fe Modified advertisiement trickle handling to remove congestion
7683bef Added storing of all MAC frame counters to NVM
b8a4f8d MAC ACK handler update:
ba09c34 Added adaptation layer TX queue size statistic
2fe2a6c MAC update:
6d288ce MAC security update:
c870b76 Added skipping of fragment length to EAP-TLS protocol and other improvements
561280b Wi-sun Discovery update:
5b153f4 DHCPv6 Client and Server update
ab849c6 Corrected skipping of other elements than KDEs on EAPOL key frames
61ebe10 Removed RPL version number increment.
b423c46 RPL parent select update
7d2f967 Corrected setting of test GTK on supplicant
454faf6 Do not balck list neighbour if link fail to ARO.
8120b37 Wi-sun RPL candidate accept update
ebe0dad fixed bbr for ULA prefix to real prefix change
bb42fad Added Network size setup for certificate test
9a7849b Fixed uninitilized fixed channel use case for test purpose.
bca8b0f Disabled check for certificate valid from field
2a5ae7c Fixed eapol target selection sort algorithm
9b283cb Fixed FHSS configuration API
76089cb Fixed ASYNCH message send for fixed channel setup.
0c94982 When starting bootstrap clear candidate parent list
6c25cf5 Dynamic min lifetime for temporary neighbour.
0b7c87a Retry timeout based on NW size is set after receiving identity
7ec9ef1 Corrected supplicant and controller authentication result causes
f5a00a0 Fixed DHCPv6 prefix update case
e06c8b2 Nanostack: sync with mbed os
ffe9351 Refactored the EAPOL target scanning
0880162 Added target EUI-64 to authentication result callback
c110c19 Added tx failure cause to initial EAPOL-key security protocol
git-subtree-dir: features/nanostack/sal-stack-nanostack
git-subtree-split: 9b3e144f5b519955837117a544168f06192b16a0
Currently mbed-os-example-blinky and mbed-os-example-wifi are built for each and every target in Mbed OS. This will change that only DISCO_L475VG_IOT01A is built for mbed-os-example-wifi. DISCO_L475VG_IOT01A was chosen as its one of the wi-fi supported boards and having integrated wi-fi.
Ticless on STM32 F4 boards causes SPI issue with following PR:
# 11682 Make FPGA tests to pass on CI targets (SPI, analogIn, PWM)
In asynch mode, using interrupts, SPI hardware detect an RX overrun.
Our understanding is that lpticker wrapper latency
causes issue similar to #8714 and #9785,
specially with SPI asynch which use interrupts.
* Make mbed_error use bitwise MbedCRC call rather than local
implementation.
* Remove use of POLY_32BIT_REV_ANSI from LittleFS.
* Move some MbedCRC instances closer to use - construction cost is
trivial, and visibility aids compiler optimisation.
* Use compile-time detection of hardware CRC capability, so unneeded
code and tables do not go into the image.
* Add global JSON config option to allow choice between no tables,
16-entry tables or 256-entry tables for software CRC. Default set
to 16-entry, reducing ROM size from previous 256-entry.
* Allow manual override in template parameter to force software or
bitwise CRC for a particular instance.
* Micro-optimisations, particularly use of `RBIT` instruction and
optimising bitwise computation using inline assembler.
Incompatible changes:
* Remove special-case "POLY_32BIT_REV_ANSI" - users can use standard
POLY_32BIT_ANSI, which now uses the same 16-entry tables by default,
or can use hardware acceleration, which was disabled for
POLY_32BIT_REV_ANSI. MbedCRC<POLY_32BIT_ANSI, 32, CrcMode::TABLE> can
be used to force software like POLY_32BIT_REV_ANSI.
* The precomputed table for POLY_16BIT_IBM had errors - this has been
corrected, but software CRC results will be different from the previous
software calculation.
* < 8-bit CRC results are no longer are shifted up in the output value,
but placed in the lowest bits, like other sizes. This means that code
performing the SD command CRC will now need to use `(crc << 1) | 1`,
rather than `crc | 1`.
* Change "is supported" check to be a macro, so it can be done at
compile-time.
* Eliminate weird shift on 7-bit CRCs.
* Add support for 32-bit CRCs and reversals to TMPM3HQ.
These targets below just support PRNG, not real TRNG. They cannot annouce TRNG.
- NUMAKER_PFM_NUC472
- NUMAKER_PFM_M487
- NUMAKER_IOT_M487
On targets without TRNG, to run mbedtls applications which require entropy source,
there are two alternatives to TRNG:
- Custom entropy source:
Define MBEDTLS_ENTROPY_HARDWARE_ALT and provide custom mbedtls_hardware_poll(...)
- NV seed:
1. Define MBEDTLS_ENTROPY_NV_SEED
2. Define MBEDTLS_PLATFORM_NV_SEED_READ_MACRO/MBEDTLS_PLATFORM_NV_SEED_WRITE_MACRO and provide custom mbedtls_nv_seed_read(...)/mbedtls_nv_seed_write(...).
3. Don't define MBEDTLS_PSA_INJECT_ENTROPY. Meet mbedtls_psa_inject_entropy(...) undefined and then provide custom one, which must be compatible with mbedtls_nv_seed_read(...)/mbedtls_nv_seed_write(...) above.
4. For development, simulating partial provision process, inject entropy seed via mbedtls_psa_inject_entropy(...) pre-main.
The addition of trace logging during greentea tests pushes the multithreaded
read-write test beyond the limits of the stack it allocates for its threads.
The increase of 128 bytes was chosen by experimentation.
4-byte addressing has been seen to cause failures on NORDIC
boards and with Macronix memories. Suppress the attempt to enable it
on that hardware (via vendor quirks and a target check) until either
the failure cause can be fixed or a more robust suppression mechanism
is implemented.
Use a vendor id check to only perform this enable on devices which define the
second configuration register where the fast mode enable bit lives.
Change _enable_fast_mode to use the standard status register reading and writing functions
Default to 2 status registers, but update this value if necessary
during vendor quirk handling for parts (currently only Macronix)
which have one status register and two control registers. For the
purposes of QSPIFBlockDevice, these are all considered status
(or at least "status-like") registers because they are all written
via the Write Status Register instruction.
Set the custom RDCR instruction for Macronix during quirk handling.
Update reading and writing of status registers to handle a variable
number of status registers.
Introduce a separate function for handling alterations to device interaction
which are not covered by the SFDP tables and therefore require checking against
the vendor id.
QSPIFBlockDevice::_clear_block_protection() has logic to retain the
WIP and WEL bits in status register 1, but it failed to account for
the situation where the QE bit is also in status register 1.
In _sfdp_set_quad_enabled, note the status register and bit therein
for the quad enable, so that _clear_block_protection can retain it.
This function writes a "config" register to ensure that the flash part
is in high performance mode, not low-power mode. This is required at
by at least MX25R6435F in order to operate at frequencies > 33MHz
(for reference, DISCO_L475VG_IOT01A runs the QSPI interface at 80 MHz).
The config register that this writes does not appear to be covered by
the SFDP spec (JESD216D.01) so this remains the status quo of
unconditional execution, as has been done on master since #8352.