Tree:
899b908b69
backport-73945-to-v2.7-branch
backport-78976-to-v3.7-branch
backport-80768-to-v3.7-branch
backport-81533-to-v4.0-branch
backport-82072-to-v2.7-branch
backport-83355-to-v4.0-branch
backport-84509-to-v4.0-branch
backport-84908-to-v4.0-branch
backport-84955-to-v3.7-branch
backport-85353-to-v4.0-branch
backport-85407-to-v4.0-branch
backport-86218-to-v4.1-branch
backport-86534-to-v4.1-branch
backport-86662-to-v4.0-branch
backport-86662-to-v4.1-branch
backport-87066-to-v4.0-branch
backport-87080-to-v4.1-branch
backport-87152-to-v4.1-branch
backport-87235-to-v4.0-branch
backport-87871-to-v3.7-branch
backport-88082-to-v4.0-branch
backport-88082-to-v4.1-branch
backport-88315-to-v3.7-branch
backport-88315-to-v4.0-branch
backport-88406-to-v4.0-branch
backport-88560-to-v4.0-branch
backport-88631-to-v4.0-branch
backport-88631-to-v4.1-branch
backport-88635-to-v4.0-branch
backport-88635-to-v4.1-branch
backport-89385-to-v4.1-branch
backport-89525-to-v4.1-branch
backport-89534-to-v4.1-branch
backport-89982-to-v4.0-branch
backport-89982-to-v4.1-branch
backport-90716-to-v4.0-branch
backport-90747-to-v4.1-branch
backport-90990-to-v3.7-branch
backport-90990-to-v4.1-branch
backport-91294-to-v4.1-branch
backport-91430-to-v4.1-branch
backport-91949-to-v3.7-branch
backport-91949-to-v4.0-branch
backport-91949-to-v4.1-branch
backport-92569-to-v4.1-branch
collab-hwm
collab-init
collab-mesh-subnet
collab-rust
collab-safety
collab-sdk-0.18-dev
collab-sdk-dev
main
v1.10-branch
v1.11-branch
v1.12-branch
v1.13-branch
v1.14-branch
v1.5-branch
v1.6-branch
v1.7-branch
v1.8-branch
v1.9-branch
v2.0-branch
v2.1-branch
v2.2-branch
v2.3-branch
v2.4-branch
v2.5-branch
v2.6-branch
v2.7-auditable-branch
v2.7-branch
v3.0-branch
v3.1-branch
v3.2-branch
v3.3-branch
v3.4-branch
v3.5-branch
v3.6-branch
v3.7-branch
v4.0-branch
v4.1-branch
v1.0.0
v1.1.0
v1.1.0-rc1
v1.10.0
v1.10.0-rc1
v1.10.0-rc2
v1.10.0-rc3
v1.11.0
v1.11.0-rc1
v1.11.0-rc2
v1.11.0-rc3
v1.12.0
v1.12.0-rc1
v1.12.0-rc2
v1.12.0-rc3
v1.13.0
v1.13.0-rc1
v1.13.0-rc2
v1.13.0-rc3
v1.14.0
v1.14.0-rc1
v1.14.0-rc2
v1.14.0-rc3
v1.14.1
v1.14.1-rc1
v1.14.1-rc2
v1.14.1-rc3
v1.14.2
v1.14.3
v1.14.3-rc1
v1.14.3-rc2
v1.2.0
v1.2.0-rc1
v1.2.0-rc2
v1.3.0
v1.3.0-rc1
v1.3.0-rc2
v1.4.0
v1.4.0-rc1
v1.4.0-rc2
v1.4.0-rc3
v1.5.0
v1.5.0-rc0
v1.5.0-rc1
v1.5.0-rc2
v1.5.0-rc3
v1.5.0-rc4
v1.6.0
v1.6.0-rc1
v1.6.0-rc2
v1.6.0-rc3
v1.6.0-rc4
v1.6.1
v1.6.1-rc
v1.6.99
v1.7.0
v1.7.0-rc1
v1.7.0-rc2
v1.7.0-rc3
v1.7.0-rc4
v1.7.1
v1.7.1-rc
v1.7.99
v1.8.0
v1.8.0-rc1
v1.8.0-rc2
v1.8.0-rc3
v1.8.0-rc4
v1.8.99
v1.9.0
v1.9.0-rc1
v1.9.0-rc2
v1.9.0-rc3
v1.9.0-rc4
v1.9.1
v1.9.2
v2.0.0
v2.0.0-rc1
v2.0.0-rc2
v2.0.0-rc3
v2.1.0
v2.1.0-rc1
v2.1.0-rc2
v2.1.0-rc3
v2.2.0
v2.2.0-rc1
v2.2.0-rc2
v2.2.0-rc3
v2.2.1
v2.3.0
v2.3.0-rc1
v2.3.0-rc2
v2.4.0
v2.4.0-rc1
v2.4.0-rc2
v2.4.0-rc3
v2.5.0
v2.5.0-rc1
v2.5.0-rc2
v2.5.0-rc3
v2.5.0-rc4
v2.5.1-rc1
v2.6.0
v2.6.0-rc1
v2.6.0-rc2
v2.6.0-rc3
v2.6.1-rc1
v2.6.1-rc2
v2.7.0
v2.7.0-rc1
v2.7.0-rc2
v2.7.0-rc3
v2.7.0-rc4
v2.7.0-rc5
v2.7.1
v2.7.2
v2.7.2-rc1
v2.7.3
v2.7.4
v2.7.5
v2.7.6
v2.7.99
v3.0.0
v3.0.0-rc1
v3.0.0-rc2
v3.0.0-rc3
v3.1.0
v3.1.0-rc1
v3.1.0-rc2
v3.1.0-rc3
v3.2.0
v3.2.0-rc1
v3.2.0-rc2
v3.2.0-rc3
v3.3.0
v3.3.0-rc1
v3.3.0-rc2
v3.3.0-rc3
v3.4.0
v3.4.0-rc1
v3.4.0-rc2
v3.4.0-rc3
v3.5.0
v3.5.0-rc1
v3.5.0-rc2
v3.5.0-rc3
v3.6.0
v3.6.0-rc1
v3.6.0-rc2
v3.6.0-rc3
v3.7.0
v3.7.0-rc1
v3.7.0-rc2
v3.7.0-rc3
v3.7.1
v3.7.1-rc1
v4.0.0
v4.0.0-rc1
v4.0.0-rc2
v4.0.0-rc3
v4.1.0
v4.1.0-rc1
v4.1.0-rc2
v4.1.0-rc3
v4.2.0-rc1
v4.2.0-rc2
zephyr-v1.0.0
zephyr-v1.1.0
zephyr-v1.10.0
zephyr-v1.11.0
zephyr-v1.12.0
zephyr-v1.13.0
zephyr-v1.14.0
zephyr-v1.14.1
zephyr-v1.2.0
zephyr-v1.3.0
zephyr-v1.4.0
zephyr-v1.5.0
zephyr-v1.6.0
zephyr-v1.6.1
zephyr-v1.7.0
zephyr-v1.7.1
zephyr-v1.8.0
zephyr-v1.9.0
zephyr-v1.9.1
zephyr-v1.9.2
zephyr-v2.0.0
zephyr-v2.1.0
zephyr-v2.2.0
zephyr-v2.2.1
zephyr-v2.3.0
zephyr-v2.4.0
zephyr-v2.5.0
zephyr-v2.6.0
zephyr-v2.7.0
zephyr-v2.7.1
zephyr-v2.7.2
zephyr-v2.7.3
zephyr-v3.0.0
zephyr-v3.1.0
zephyr-v3.2.0
zephyr-v3.3.0
zephyr-v3.4.0
zephyr-v3.5.0
${ noResults }
91 Commits (899b908b69a72aef1de16ba1c09dc461aa0f5415)
| Author | SHA1 | Message | Date |
|---|---|---|---|
Hake Huang
|
fe811defb2 |
tests: vector_table_relocation: fix a mis-use of SRAM_SIZE
SRAM_SIZE is given in kilobytes fixes: #92533 Signed-off-by: Hake Huang <hake.huang@nxp.com> |
4 days ago |
Shaunak saha
|
7bc5ef87cf |
tests: arch: arm: update for MPS4 Corstone315
DT config for MPS4 corstone315 boards which can be tested with simulation. Creates a custom section in the unused SRAM region. Executing code in this region in privileged mode will result in an MPU fault while, execution in unprivileged mode should work fine. Signed-off-by: Shaunak saha <ssaha@tsavoritesi.com> |
2 weeks ago |
Benjamin Cabé
|
14ea8b087b |
tests: cmake: actually test SBOM files generation
The current test was just a basic sanity check. This adds actual validation of the SPDX files being generated as being spec-compliant. Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org> |
3 weeks ago |
Sudan Landge
|
feb8f7766e |
tests: update for MPS4
MPS4, similar to MPS3 Corstone-310, splits code between DTCM and SRAM and thus requires similar handling. Signed-off-by: Sudan Landge <sudan.landge@arm.com> |
4 weeks ago |
Sreeram Tatapudi
|
968704e6b7 |
soc: cyw20829: add support of Secure LCS
Enable support of SECURE LCS stage. In this stage, the protection state is set to “secure”. A secured device will boot only when the authentication of its flash boot and application code succeeds Signed-off-by: Sreeram Tatapudi <sreeram.praveen@infineon.com> |
2 months ago |
Martin Hoff
|
64d20cf412 |
tests: vector_table_relocation: add test for vector table relocation
Add a basic test for vector table relocation to SRAM. This test verifies that the vector table can be relocated to SRAM and that the VTOR register correctly points to the SRAM address range. Signed-off-by: Martin Hoff <martin.hoff@silabs.com> |
2 months ago |
Anas Nashif
|
5c8cf1c18c |
tests: fix various test ids and use existing scheme
Fix IDs and match them to what we have in the MAINTAINERS file. Signed-off-by: Anas Nashif <anas.nashif@intel.com> |
3 months ago |
Sylvain Chouleur
|
4454734d12 |
scripts: code_relocate: support section filter
One might want to select the symbols to be relocated inside a file or a library. To do this, one can use the FILTER argument of zephyr_code_relocate which must contain a regular expression of the section names to be selected for relocation. The test_function_in_sram2 test case in `tests/application_development/code_relocation` has been updated to verify that only one function `function_in_sram()` is relocated to ram and that the function `function_not_relocated()` is not being relocated when using relocation filter. Signed-off-by: Sylvain Chouleur <sylvain.chouleur@gmail.com> Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> |
5 months ago |
Pieter De Gendt
|
5d23996361 |
tests: application_development: Add spdx SBOM test
Add a test where the software bill of materials is generated using the west spdx extension. Signed-off-by: Pieter De Gendt <pieter.degendt@basalte.be> |
6 months ago |
Declan Snyder
|
8ed80ddb37 |
boards: mimxrt1060_evk: Convert to variants
Convert qspi and hyperflash to variants instead of revisions by popular demand. And convert evkb into a revision instead of a different board. Signed-off-by: Declan Snyder <declan.snyder@nxp.com> |
7 months ago |
Manuel Argüelles
|
87798f9e16 |
arch: arm: rename CPU_HAS_NXP_MPU to align with binding
Following the binding rename to "nxp,sysmpu", update the Kconfig option to align with the binding name and to better reflect the option's purpose. Signed-off-by: Manuel Argüelles <manuel.arguelles@nxp.com> |
7 months ago |
Daniel Leung
|
84c12ab5b5 |
boards: rename qemu_xtensa to qemu_xtensa/dc233c
This is in preparation for adding another SoC where qemu_xtensa is no longer valid choice. So use qemu_xtensa/dc233c as it is the same as the old qemu_xtensa. Signed-off-by: Daniel Leung <daniel.leung@intel.com> |
9 months ago |
Pisit Sawangvonganan
|
9ae9873f12 |
style: tests: remove unnecessary `return` statements
For code clarity, remove unnecessary `return` statements in functions with a void return type they don't affect control flow. Signed-off-by: Pisit Sawangvonganan <pisit@ndrsolution.com> |
10 months ago |
Torsten Rasmussen
|
8dc3f85622 |
hwmv2: Introduce Hardware model version 2 and convert devices
This is a squash of the ``collab-hwm`` branch which converts all in-tree boards to hardware model version 2 including build system changes, board updates and soc conversions. This squash is a combination of the following commits: ca214745a1 soc: Remove soc_legacy folder and move ARM Kconfig |
1 year ago |
Grzegorz Swiderski
|
460b6ef122 |
code_relocation: Add NOKEEP option
When using the code and data relocation feature, every relocated symbol would be marked with `KEEP()` in the generated linker script. Therefore, if any input files contained unused code, then it wouldn't be discarded by the linker, even when invoked with `--gc-sections`. This can cause unexpected bloat, or other link-time issues stemming from some symbols being discarded and others not. On the other hand, this behavior has been present since the feature's introduction, so it should remain default for the users who rely on it. This patch introduces support for `zephyr_code_relocate(... NOKEEP)`. This will suppress the generation of `KEEP()` statements for all symbols in a particular library or set of files. Much like `NOCOPY`, the `NOKEEP` flag is passed to `gen_relocate_app.py` in string form. The script is now equipped to handle multiple such flags when passed from CMake as a semicolon-separated list, like so: "SRAM2:NOCOPY;NOKEEP:/path/to/file1.c;/path/to/file2.c" Documentation and tests are updated here as well. Signed-off-by: Grzegorz Swiderski <grzegorz.swiderski@nordicsemi.no> |
2 years ago |
Alberto Escolar Piedras
|
690479fc36 |
tests/*: Switch integration platform to native_sim
Swith integration_platforms from native_posix(_64) to native_sim(_64). Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no> |
2 years ago |
|
Anas Nashif
|
345735d0a8 |
tests: remove CONFIG_ZTEST_NEW_API in all tests
Remove all usage of CONFIG_ZTEST_NEW_API from tests and sample as this is now enabled by default. Signed-off-by: Anas Nashif <anas.nashif@intel.com> |
2 years ago |
|
Daniel Leung
|
7a7aeb21e2 |
boards: qemu_xtensa: use dc233c core
This changes qemu_xtensa to use dc233c core instead of sample_controller. The sample_controller uses a very basic configuration which lacks features usually needed in real world applications. Instead, use the dc233c core as the base for qemu_xtensa so we can use QEMU to cover more of our code path. Signed-off-by: Daniel Leung <daniel.leung@intel.com> |
2 years ago |
|
Manuel Argüelles
|
78cc40f4e5 |
tests: code_relocation: exclude mr_canhubk3 board
The mr_canhubk3 board enables by default an off-chip watchdog that must be serviced to avoid triggering a reset and cannot be disabled on a per-test basis. The watchdog driver make uses of a semaphore during device init and on this test the relocation of the kernel sources produces a fault. So skip this test for this board. Signed-off-by: Manuel Argüelles <manuel.arguelles@nxp.com> |
2 years ago |
|
Pieter De Gendt
|
a6d81591a2 |
tests: gen_inc_file: Add tests for optional offset/length
Add tests to validate the optional offset/length arguments for the file2hex python script. Signed-off-by: Pieter De Gendt <pieter.degendt@basalte.be> |
2 years ago |
|
Manuel Argüelles
|
62f8fd962b |
tests: code_relocation: update test filters
ITCM relocation tests depends on MINIMAL_LIBC and when using Zephyr SDK the default is PICOLIBC for mr_canhubk3 board, so explicitly select it. Also the NXP S32 platforms don't have NXP MPU, so remove it. For frdm_k64f the ITCM relocation test is not executed, so remove the unnecesary filter CONFIG_MINIMAL_LIBC. Signed-off-by: Manuel Argüelles <manuel.arguelles@nxp.com> |
2 years ago |
Gerard Marull-Paretas
|
9c961571a2 |
modules: cmsis: move glue code to modules/cmsis
The CMSIS module glue code was part of arch/ directory. Move it to modules/cmsis, and provide a single entry point for it: cmsis_core.h. This entry header will include the right CMSIS header (M or A/R). To make this change possible, CMSIS module Kconfig/CMake are declared as external, allowing us to add a new Zephyr include directory. All files including CMSIS have been updated. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> |
2 years ago |
|
Anas Nashif
|
ee73cad7a4 |
tests: remove tests. prefix from identifier
We know this is a test already. Signed-off-by: Anas Nashif <anas.nashif@intel.com> |
2 years ago |
|
Manuel Argüelles
|
bed68af489 |
tests: code_relocation: support mr_canhubk3 boards
Add test scenario for NXP S32 platforms, for now only ported to mr_canhubk3. In some platforms the MPU region used for NULL pointer detection conflicts with the ITCM region, causing access fault. Make disabling the null pointer exception detection the default behavior for this scenario. Signed-off-by: Manuel Argüelles <manuel.arguelles@nxp.com> |
2 years ago |
|
Manuel Argüelles
|
17f345780d |
tests: code_relocation: use per-SoC linker file for Arm tests
In order to support more Arm SoCs, extend the SoC-specific linker file instead of the default arch linker file. Fixes #60165 Signed-off-by: Manuel Argüelles <manuel.arguelles@nxp.com> |
2 years ago |
|
Manuel Argüelles
|
20a2e40a5e |
tests: code_relocation: restrict Arm test to NXP platforms
Currently tests.application_development.code_relocation and tests.application_development.code_relocation_kinetis scenarios are restricted to specific NXP platforms only, so make filters more strict. Also for frdm_k64f, which lacks of ITCM, relocation to ITCM must be disabled. Fixes #60167 Signed-off-by: Manuel Argüelles <manuel.arguelles@nxp.com> |
2 years ago |
Jamie McCrae
|
ff8c78154f |
tests: application_development: code_relocation: Add absolute paths
Adds some absolute paths to check that the feature is working correctly. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no> |
2 years ago |
Björn Stenberg
|
234fec579a |
scripts: gen_relocate_app.py: Give sections unique names
The code_relocation feature creates generic section names that sometimes conflict with already existing names. This patch adds a '_reloc_' word to the created names to reduce the risk of conflict. This solves #54785. Signed-off-by: Björn Stenberg <bjorn@haxx.se> |
2 years ago |
|
Gerard Marull-Paretas
|
93b63df762 |
samples, tests: convert string-based twister lists to YAML lists
Twister now supports using YAML lists for all fields that were written as space-separated lists. Used twister_to_list.py script. Some artifacts on string length are due to how ruamel dumps content. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> |
2 years ago |
Daniel DeGrasse
|
bd593bf93e |
tests: code_relocation: Add additional test cases for library and genex
Add test cases for generator expressions and library relocation to the code_relocation test, in order to verify functionality for these new API features. Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com> |
3 years ago |
|
Daniel DeGrasse
|
47271ce8be |
treewide: update usage of zephyr_code_relocate
Update usage of zephyr_code_relocate to follow new API. The old method of relocating a file was the following directive: zephyr_code_relocate(file location) The new API for zephyr_code_relocate uses the following directive: zephyr_code_relocate(FILES file LOCATION location) update in tree usage to follow this model. Also, update the NXP HAL SHA, as NXP's HAL uses this macro as well. Signed-off-by: Daniel DeGrasse <daniel.degrasse@nxp.com> |
3 years ago |
Fabio Baltieri
|
7db1d17ee3 |
yamllint: fix all yamllint line-length errors
Fix all line-length errors detected by yamllint: yamllint -f parsable -c .yamllint $( find -regex '.*\.y[a]*ml' ) | \ grep '(line-length)' Using a limit is set to 100 columns, not touching the commandlines in GitHub workflows (at least for now). Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com> |
3 years ago |
|
Anas Nashif
|
ba7d730e9b |
tests/samples: use integration_plaforms in more tests/samples
integration_platforms help us control what get built/executed in CI and for each PR submitted. They do not filter out platforms, instead they just minimize the amount of builds/testing for a particular tests/sample. Tests still run on all supported platforms when not in integration mode. Signed-off-by: Anas Nashif <anas.nashif@intel.com> |
3 years ago |
Ederson de Souza
|
8ac6f74a7d |
arch/xtensa: Enable code relocation
Besides adding ARCH_HAS_CODE_DATA_RELOCATION, this patch also adds support for the "sample_controller" SoC (used by qemu_xtensa) as demonstration. As Xtensa lacks a common linker script at the arch level, enabling it for each platform will be a piecemeal effort. This patch adds it to the `soc/xtensa/sample_controller` SoC. Basically, default RAMABLE_REGION is set to be called "RAM", and hooks are inserted so that gen_relocate_app.py can add the relevant linker bits. Also, `tests/application_developent/code_relocation` was tweaked to support the qemu_xtensa platform. Basically, add the relevant linker script and ensure that relevant memory regions have their program header (PHDR) associated. Signed-off-by: Ederson de Souza <ederson.desouza@intel.com> |
3 years ago |
Peter Marheine
|
34ca7347a2 |
tests: remove incorrect comment from code_relocation for RISCV
This was copied from the ARM version of the test's linker script, which in turn seems to have been copied from another linker script at some point. Remove the incorrect comment. Signed-off-by: Peter Marheine <pmarheine@chromium.org> |
3 years ago |
|
Peter Marheine
|
5eb75b81f7 |
arm: rename default RAM region from 'SRAM' to 'RAM'
It's useful for RAMABLE_REGION to have a uniform name when CODE_DATA_RELOCATION is supported, because otherwise the build system needs to be aware of how the region name differs between architectures. Since architectures tend to prefer one of 'SRAM' or 'RAM' for that region, prefer to use 'RAM' as the more general term. Signed-off-by: Peter Marheine <pmarheine@chromium.org> |
3 years ago |
Enjia Mai
|
44a1212bff |
tests: application_development: move the gen inc file test to new ztest
Migrate the testsuite tests/application_development/gen_inc_file to the new ztest API. Signed-off-by: Enjia Mai <enjia.mai@intel.com> |
3 years ago |
|
Gerard Marull-Paretas
|
79e6b0e0f6 |
includes: prefer <zephyr/kernel.h> over <zephyr/zephyr.h>
As of today <zephyr/zephyr.h> is 100% equivalent to <zephyr/kernel.h>. This patch proposes to then include <zephyr/kernel.h> instead of <zephyr/zephyr.h> since it is more clear that you are including the Kernel APIs and (probably) nothing else. <zephyr/zephyr.h> sounds like a catch-all header that may be confusing. Most applications need to include a bunch of other things to compile, e.g. driver headers or subsystem headers like BT, logging, etc. The idea of a catch-all header in Zephyr is probably not feasible anyway. Reason is that Zephyr is not a library, like it could be for example `libpython`. Zephyr provides many utilities nowadays: a kernel, drivers, subsystems, etc and things will likely grow. A catch-all header would be massive, difficult to keep up-to-date. It is also likely that an application will only build a small subset. Note that subsystem-level headers may use a catch-all approach to make things easier, though. NOTE: This patch is **NOT** removing the header, just removing its usage in-tree. I'd advocate for its deprecation (add a #warning on it), but I understand many people will have concerns. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> |
3 years ago |
|
Peter Marheine
|
d400b8135c |
arch/riscv: support CONFIG_CODE_DATA_RELOCATION
This implements support for relocating code to chosen memory regions via the `zephyr_code_relocate` CMake function for RISC-V SoCs. ARM-specific assumptions that were made by gen_relocate_app.py need to be corrected, in particular not assuming any particular name for the default RAM section (which is 'SRAM' for most ARM pltaforms) and not assuming 32-bit pointers (so the test works on RV64). Signed-off-by: Peter Marheine <pmarheine@chromium.org> |
3 years ago |
|
Fabio Baltieri
|
def230187b |
test: fix more legacy #include paths
Add a bunch of missing "zephyr/" prefixes to #include statements in various test and test framework files. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com> |
3 years ago |
Hake Huang
|
45daf3b448 |
tests: application_development: add code_relocation test
add code relocation test case 1. customer relocation code and data test 2. memcpy relocation Signed-off-by: Hake Huang <hake.huang@oss.nxp.com> |
3 years ago |
Carles Cufi
|
4b8f1c04ab |
kconfig: Rename the ZTEST stack size option to align with the rest
All stack sizes should end with STACK_SIZE. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> |
3 years ago |
|
Torsten Rasmussen
|
1cccc8a8fe |
cmake: increase minimal required version to 3.20.0
Move to CMake 3.20.0. At the Toolchain WG it was decided to move to CMake 3.20.0. The main reason for increasing CMake version is better toolchain support. Better toolchain support is added in the following CMake versions: - armclang, CMake 3.15 - Intel oneAPI, CMake 3.20 - IAR, CMake 3.15 and 3.20 Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> |
4 years ago |
|
Anas Nashif
|
174afccced |
tests: move cpp tests to subsys/cpp
Wrongly places under application_development. We have a CPP subsystem, so move them under tests/subsys/cpp for consistency. Signed-off-by: Anas Nashif <anas.nashif@intel.com> |
4 years ago |
Artur Lipowski
|
bc2ad24d1a |
tests: Add base test for C++ exceptions handling.
Try to throw and catch C++ exception of int type. Related to: #32448 and #34229 Signed-off-by: Artur Lipowski <Artur.Lipowski@hidglobal.com> |
4 years ago |
Kumar Gala
|
d49ae849c6 |
tests: application_development: set integration_platforms
Set integration_platforms on these samples to a single platform, we prefer native_posix, than a qemu platform mps2_an385 and finally a hardware platform. Signed-off-by: Kumar Gala <kumar.gala@linaro.org> |
4 years ago |
Watson Zeng
|
7a3f9c4e39 |
tests: add filter for some tests using newlib
some tests configured with CONFIG_NEWLIB_LIBC=y, it's better to add a filter filter: TOOLCHAIN_HAS_NEWLIB == 1 in those tests yaml file. Signed-off-by: Watson Zeng <zhiwei@synopsys.com> |
5 years ago |
Tomasz Bursztyka
|
e18fcbba5a |
device: Const-ify all device driver instance pointers
Now that device_api attribute is unmodified at runtime, as well as all the other attributes, it is possible to switch all device driver instance to be constant. A coccinelle rule is used for this: @r_const_dev_1 disable optional_qualifier @ @@ -struct device * +const struct device * @r_const_dev_2 disable optional_qualifier @ @@ -struct device * const +const struct device * Fixes #27399 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com> |
5 years ago |
|
Kumar Gala
|
a1b77fd589 |
zephyr: replace zephyr integer types with C99 types
git grep -l 'u\(8\|16\|32\|64\)_t' | \ xargs sed -i "s/u\(8\|16\|32\|64\)_t/uint\1_t/g" git grep -l 's\(8\|16\|32\|64\)_t' | \ xargs sed -i "s/s\(8\|16\|32\|64\)_t/int\1_t/g" Signed-off-by: Kumar Gala <kumar.gala@linaro.org> |
5 years ago |
Marc Herbert
|
debade9121 |
tests: make find_package(Zephyr...) REQUIRED
... because it is (required).
This makes a difference when building with CMake and forgetting
ZEPHYR_BASE or not registering Zephyr in the CMake package registry.
In this particular case, REQUIRED turns this harmless looking log
statement:
-- Could NOT find Zephyr (missing: Zephyr_DIR)
-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- Check for working C compiler: /usr/bin/cc
-- ...
-- ...
-- ...
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:8 (target_sources):
Cannot specify sources for target "app" which is not built by
this project.
... into this louder, clearer, faster and (last but not least) final
error:
CMake Error at CMakeLists.txt:5 (find_package):
Could not find a package configuration file provided by "Zephyr" with
any of the following names:
ZephyrConfig.cmake
zephyr-config.cmake
Add the installation prefix of "Zephyr" to CMAKE_PREFIX_PATH or set
"Zephyr_DIR" to a directory containing one of the above files. If
"Zephyr" provides a separate development package or SDK, be sure it
has been installed.
-- Configuring incomplete, errors occurred!
Signed-off-by: Marc Herbert <marc.herbert@intel.com>
|
5 years ago |