nanostack border router is now owned by ISG and has been moved
out of ARMmbed and into their organisation. ISG will be
responsible for updating and testing this example going forward.
715ae9a693 Merge remote-tracking branch 'origin/release_internal' into release_external
42c9807207 Nanostak trace level configuration (#2489)
6f5217119a Bug fix: socket reference count made 16-bit (#2490)
f51669adc7 Bug fix: Do not print UFSI drift when fixed channel is used (#2488)
18fa0486e3 RPL DAO timeout update:
660e178506 Clear debug traces.
cbac0bbca4 DIO init send block for node
fed5d1c819 Created different MPL configuration based on network size
7ad7e81209 Wi-SUN recovery and BR BSI update:
d207f4d9f9 Merge branch 'release_internal' into release_external
d166c89427 MPL: buffered max limit increased to 8k (#2482)
0f6666a97e Fixed Unit test's
1ff9b1d6c6 LLC drop a packet if FHSS shedule is not configured.
7cecc28c98 Fixed missing asynch trigle setup stop at if down process
7a8b2bfd98 Wi-SUN fhss API default value setting fixes
164a3706c6 Fixed coverity issues from management API
8b5b433284 Corrected out of bounds access coverity warning (#2475)
4ffe6a12cc Multicast forwarding is separated from the routing flag
30f431581d Wi-SUN discovery staten enter upxdate
083b84e9c5 Iotthd 4308 (#2473)
fcc33d559c Removed time increment from NVM time read function on interface up
9c8e3afc9f fhss_tx_handle update
5491a6b052 Fixed UFSI update print function (#2470)
86f64c58b6 FHSS WS: Check if BC schedule is stopped before computing timeout delay (#2469)
a0b112a97b Corrected defects and coding style
2f4678a2f2 Corrected trace macro
5e967515ee Distributed key storage NVM writes to longer time period
9b3891fffb FHSS WS: handle blocked interrupts (#2466)
a792e832de Added validation at MAC ack buffer handler
2a465b2e49 DNS configuration lifetime validation
git-subtree-dir: connectivity/nanostack/sal-stack-nanostack
git-subtree-split: 715ae9a69376af5c96d53e5445b0d280ee1edf28
Don't require too old of a version of mbed-greentea, mbed-host-tests, or
mbed-ls. We conservatively limit the versions to less than 2.0 for now,
in case we'ld like to break backwards compatibility in the future.
The compile defintions should always be added depending on the
selected toolchain.
mbed_set_toolchain_options() should only be called if a third-party
toolchain file has not been used as it has compile options that can
cause conflicts.
The new function (mbed_set_cpu_core_definitions()) should always be
called as it has defintions needed by Mbed OS to work with that
particular MCU core.
mbed_set_cpu_core_options() should only be called if a third-party
toolchain file has not been used as it has compile options that can
cause conflicts.
As the assembler does not seem to recognise the request to the
linker to use microlib, remove that instruction.
Microlib is still used as the linker selects microlib as a result
of being explicitly asked to do so.
Rename the CMake variable expected from applications from MBED_ROOT to
MBED_PATH to be consistent with the naming used for the configuration file
(MBED_CONFIG_PATH) also expected from applications.
Issue https://gitlab.kitware.com/cmake/cmake/-/issues/21093
Until this is fixed, we should disable response files for ARMClang + ninja on Windows.
Other toolchains and host systems should benefit from response files thus not disabling them
completely.
This fixes the issue with not finding includes. It's not trivial to find the root cause, it took me a while to figure out why ARMClang can't find the paths.
I moved the check to Mbed OS main cmake. It should not be in the toolchain file as it is not
related to the toolchain but to generator. We need toolchain properly set up first.
Note, I had to protect setting CMAKE_NINJA_FORCE_RESPONSE_FILE. If I set it to 0, ninja
would still use rsp files so I rather protected it and define that variable only when
required, not always.
Co-authored-by: Hugues Kamba <41612201+hugueskamba@users.noreply.github.com>
$<TARGET_FILE:${target}> is the output from CMake. As it can contain suffix for some toolchains, we can use ${target} instead (output from hex/bin generation).
mbed-os consists of mbed-core and mbed-rtos
mbed-baremetal consists of mbed-core
The main change is for mbed-core. Changing from object library to be interface. This way it allows us to do the above to have 2 main targets for users to use.
This should be backward compatible change as mbed-os target we used contains the same files/options as previously set.
This ensures that applications which link with the mbed-os
CMake target still work. We want applications that require the OS
to use the mbed-os CMake target as we will be creating a new one
that will include mbed-core and mbed-rtos.
These settings like enable_language should be done in the application and just once.
We hit the issue when you expose sources to an app (interface or public), CMake errors as some of the internal settings have not been configured.
A linker script needs symbols (stack size, app size, etc). They are basic values or defines. Not any array like or string like macros. We should filter these, as they are not valid anyway.
The other option to fix this would be to fix all the macros but I dont think it is needed as these config values won't be used in the linker script anyway.
Not allowed in ld files macros with spaces, like MACRO={0, 2, 3} or MACRO=(4 * 2000).
Directories that start with special prefixes (TARGET_, FEATURE_, COMPONENT_) are added to the build based on Mbed target configuration from targets.json instead of calling utility function mbed_add_cmake_directory_if_labels().
Aside from the core mbed-os CMake target, a number of targets have been created so they can optionally be included by application executables that require them using `target_link_libraries()`.
Co-authored-by: Martin Kojtal <martin.kojtal@arm.com>
Co-authored-by: Rajkumar Kanagaraj <rajkumar.kanagaraj@arm.com>