Tree:
ec80ab5bb6
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 }
168 Commits (ec80ab5bb60180c2235bfc22c6ca49d1ef83496d)
| Author | SHA1 | Message | Date |
|---|---|---|---|
Francois Ramu
|
45ce78adf0 |
samples: code_relocation_nocopy: update macro for flash size and address
In case of the st,stm32-qspi-nor compatible new property and node definitions will requires new macro to get the external NOR flash base address and size Add the config for running the sample on stm32l475 disco kit Signed-off-by: Francois Ramu <francois.ramu@st.com> |
2 weeks ago |
|
Francois Ramu
|
5a4326e8ce |
samples: appli dev: code reloc running on stm32h7rs target boards
Samples to execute code in external memory in Memory mapped mode on the stm32h7s3l8 nucleo or stm32h7s78 disco kit Signed-off-by: Francois Ramu <francois.ramu@st.com> |
2 weeks ago |
|
Francois Ramu
|
11d3b45648 |
samples: code_relocation_nocopy: update macro for flash size and address
In case of the st,stm32-ospi-nor compatible new property and node definitions will requires new macro to get the external NOR flash base address and size Signed-off-by: Francois Ramu <francois.ramu@st.com> |
3 weeks ago |
|
Francois Ramu
|
95d95dc82c |
samples: code_relocation_nocopy: update macro for flash size and address
In case of the st,stm32-xspi-nor compatible new property and node definitions will requires new macro to get the external NOR flash base address and size Signed-off-by: Francois Ramu <francois.ramu@st.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 |
Etienne Carriere
|
cc28f5072b |
samples: code_relocation_nocopy: fix stm32 flash size info
Fix typos in stm32 flash sizes value introduced by commit |
3 months ago |
Fabrice DJIATSA
|
0e1ffc7beb |
samples: code_relocation_nocopy: update macro to get flash size
The flash size is the second part (size) of the first reg value, not the first part (address) of a nonexistent second reg value. DT_REG_SIZE get a node's (only) register block size instead DT_REG_ADDR_BY_IDX . Signed-off-by: Fabrice DJIATSA <fabrice.djiatsa-ext@st.com> |
4 months ago |
|
Francois Ramu
|
1f3ffc3111 |
samples: code relocation for the stm32f746 disco kit
Add the configuration for using the external FLASh Memory and execute the samples/application_development/code_relocation_nocopy/ on the stm32f746g_disco board Signed-off-by: Francois Ramu <francois.ramu@st.com> |
4 months ago |
Andrzej Głąbek
|
ac3355ab97 |
samples: code_relocation_nocopy: Add configuration for nRF54H20 DK
Add nRF54H20 DK specific entries to allow using the sample on this board. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no> |
4 months ago |
Torsten Rasmussen
|
35625c146a |
boards: samples: remove CONFIG_BUILD_NO_GAP_FILL=y and similar
Gap filling in hex files are now disabled per default, and therefore there is no reason to explicitly disable gap filling. It has never been possible to disable gap filling in binary files. Disabling gap filling would just result in the binary file to be gap filled with the tool's default value, objcopy=0x00. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> |
7 months ago |
Benjamin Cabé
|
1db9b009a7 |
doc: samples: Adopt code-sample-category across tree
This commit uses the new .. zephyr:code-sample-category directive to categorize code samples across the tree. Updates existing legacy references to manually defined targets to now use :zephyr:code-sample-category: role instead. Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org> |
10 months ago |
|
Benjamin Cabé
|
9902eec01b |
samples: application_development: use zephyr:code-sample directive
Describe the samples using code-sample directive in preparation for upcoming changes to the Zephyr documentation that will be leveraging the provided description and metadata. Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org> |
11 months ago |
Jonathon Penix
|
4ddd3ebd51 |
samples: external_lib: Include `--target` in exported build flags
Appropriately setting the `--target` flag is necessary when using clang and building for a target other than the default. Zephyr generally accomplishes this by setting the CMAKE_<LANG>_COMPILER_TARGET variables and allowing cmake to automatically provide the `--target` flag when building. For the external_lib sample, however, cmake can't add the flag and it was not otherwise exported. As such, clang typically threw errors when building this sample for any non-default targets due to mismatches between target-specific flags and the default target. To fix this, ensure we select the correct target by checking if CMAKE_C_COMPILER_TARGET has been defined and adding `--target=<triple>` to the list of flags that are exported if so. Signed-off-by: Jonathon Penix <jpenix@quicinc.com> |
11 months ago |
|
Francois Ramu
|
2f0dd2c66f |
samples: code relocation in external memory of stm32h5 disco kit
Define the configuration to run the code_relocation application on the external memory xspi flash of the stm32h573i_dk disco kit in XIP Signed-off-by: Francois Ramu <francois.ramu@st.com> |
1 year ago |
|
Francois Ramu
|
a9be65bec5 |
samples: code relocation in external memory of stm32H7 disco kit
Define the configuration to run the code_relocation application on the external memory dual quad flash of the stm32h745i/stm32h750b disco kits in XIP Signed-off-by: Francois Ramu <francois.ramu@st.com> |
1 year ago |
|
Francois Ramu
|
4101948082 |
samples: code relocation in external memory of stm32 disco kit
Define the configuration to run the code_relocation application on the external memory octo flash of the stm32u585 or stm32h7b3i disco kit in XIP Signed-off-by: Francois Ramu <francois.ramu@st.com> |
1 year ago |
Armin Brauns
|
e7a53cf03b |
samples: code_relocation_nocopy: add stm32f769i_disco board
This board has memory-mapped QSPI flash. Signed-off-by: Armin Brauns <armin.brauns@embedded-solutions.at> |
1 year ago |
Gerard Marull-Paretas
|
8120bd7519 |
samples: move with_mcuboot sample to samples/sysbuild
This creates a new category of samples that demonstrate certain features of sysbuild. "application development" was a very generic name. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com> |
1 year 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 |
Keith Packard
|
6c95f23d81 |
samples/code_relocation_nocopy: Increase fake flash size
When linking with the 0.16.3 SDK version of picolibc, using long long cbprintf support pulls in the full floating point printf which is much larger than the integer-only version. This ends up overflowing the memory region available for it. Increase the size of that by bumping the start of the fake region by 8kB. Signed-off-by: Keith Packard <keithp@keithp.com> |
2 years ago |
Alberto Escolar Piedras
|
196341c18b |
samples: Switch integration_platforms from native_posix to native_sim
For all remaining samples which now set their integration platform as native_posix(_64) switch them to native_sim(_64) Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no> |
2 years ago |
|
Andrzej Głąbek
|
e3ee5c09f2 |
samples: code_relocation_nocopy: Make linker script more generic
Instead of depending on the nRF5340 DK, use a path specific to just the nRF5340 SoC and get the size of the external flash in this case from devicetree so that the sample could be easily run on other boards based on the nRF5340 SoC (after just adding proper overlays). On the occasion, correct the attributes of the EXTFLASH memory region. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no> |
2 years ago |
|
Andrzej Głąbek
|
6bd6f4be65 |
samples: code_relocation_nocopy: Use nrf_qspi_nor driver to init XIP
Use the Nordic QSPI NOR flash driver instead of the specific code for the nRF5340 DK to initialize the external flash chip for XIP. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no> |
2 years ago |
Huifeng Zhang
|
2c22e83dfb |
include: arch: arm: Remove aarch32 directory
This commit follows the parent commit work.
This commit introduces the following major changes.
1. Move all directories and files in 'include/zephyr/arch/arm/aarch32'
to the 'include/zephyr/arch/arm' directory.
2. Change the path string which is influenced by the changement 1.
Signed-off-by: Huifeng Zhang <Huifeng.Zhang@arm.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 |
|
Gerard Marull-Paretas
|
2f18ee0664 |
samples: application_development: drop oot board/driver samples
Because there are more comprehensive examples in the Zephyr's example-application repository. Application development samples page now points to example-application as well. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com> |
2 years ago |
|
Gerard Marull-Paretas
|
f08a652fed |
samples: application_development: add link to example-application
Because example-application contains relevant sample code related to application development. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com> |
2 years ago |
|
Torsten Rasmussen
|
a88502783b |
cmake: align Zephyr module variable to EXTRA_ZEPHYR_MODULES
Align Zephyr modules with other user facing variables where settings can be defined or extended, meaning Zephyr modules now supports: ZEPHYR_MODULES and EXTRA_ZEPHYR_MODULES. Support for ZEPHYR_EXTRA_MODULES is kept foir backward compatibility. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> |
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 Leung
|
c4565ad5b6 |
samples: out_of_tree_driver: fix kconfig dependency
The out_of_tree_driver sample defines syscall functions, and thus requiring CONFIG_APPLICATION_DEFINED_SYSCALL to be enabled even if no userspace is involved. This is due to the function generation for the syscall stubs. Fixes #56946 Signed-off-by: Daniel Leung <daniel.leung@intel.com> |
2 years ago |
|
Keith Packard
|
0b90fd5adf |
samples, tests, boards: Switch main return type from void to int
As both C and C++ standards require applications running under an OS to
return 'int', adapt that for Zephyr to align with those standard. This also
eliminates errors when building with clang when not using -ffreestanding,
and reduces the need for compiler flags to silence warnings for both clang
and gcc.
Most of these changes were automated using coccinelle with the following
script:
@@
@@
- void
+ int
main(...) {
...
- return;
+ return 0;
...
}
Approximately 40 files had to be edited by hand as coccinelle was unable to
fix them.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
2 years ago |
|
Gerard Marull-Paretas
|
a5fd0d184a |
init: remove the need for a dummy device pointer in SYS_INIT functions
The init infrastructure, found in `init.h`, is currently used by:
- `SYS_INIT`: to call functions before `main`
- `DEVICE_*`: to initialize devices
They are all sorted according to an initialization level + a priority.
`SYS_INIT` calls are really orthogonal to devices, however, the required
function signature requires a `const struct device *dev` as a first
argument. The only reason for that is because the same init machinery is
used by devices, so we have something like:
```c
struct init_entry {
int (*init)(const struct device *dev);
/* only set by DEVICE_*, otherwise NULL */
const struct device *dev;
}
```
As a result, we end up with such weird/ugly pattern:
```c
static int my_init(const struct device *dev)
{
/* always NULL! add ARG_UNUSED to avoid compiler warning */
ARG_UNUSED(dev);
...
}
```
This is really a result of poor internals isolation. This patch proposes
a to make init entries more flexible so that they can accept sytem
initialization calls like this:
```c
static int my_init(void)
{
...
}
```
This is achieved using a union:
```c
union init_function {
/* for SYS_INIT, used when init_entry.dev == NULL */
int (*sys)(void);
/* for DEVICE*, used when init_entry.dev != NULL */
int (*dev)(const struct device *dev);
};
struct init_entry {
/* stores init function (either for SYS_INIT or DEVICE*)
union init_function init_fn;
/* stores device pointer for DEVICE*, NULL for SYS_INIT. Allows
* to know which union entry to call.
*/
const struct device *dev;
}
```
This solution **does not increase ROM usage**, and allows to offer clean
public APIs for both SYS_INIT and DEVICE*. Note that however, init
machinery keeps a coupling with devices.
**NOTE**: This is a breaking change! All `SYS_INIT` functions will need
to be converted to the new signature. See the script offered in the
following commit.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
init: convert SYS_INIT functions to the new signature
Conversion scripted using scripts/utils/migrate_sys_init.py.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
manifest: update projects for SYS_INIT changes
Update modules with updated SYS_INIT calls:
- hal_ti
- lvgl
- sof
- TraceRecorderSource
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
tests: devicetree: devices: adjust test
Adjust test according to the recently introduced SYS_INIT
infrastructure.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
tests: kernel: threads: adjust SYS_INIT call
Adjust to the new signature: int (*init_fn)(void);
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
|
2 years ago |
Jamie McCrae
|
d1b40013d4 |
samples: out_of_tree_board: Fix board name
Fixes a missed file when the board was renamed that prevented this sample from working. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no> |
2 years ago |
|
Jamie McCrae
|
e534da007d |
samples/tests: Add empty prj.conf files
Adds empty prj.conf files as this file is required to configure a build. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no> |
2 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 |
Tom Burdick
|
36d8c1b7f7 |
samples: Remove platform filters for external_lib
Instead prefer to add the tag to ignored tags in the board yaml where its clearer for both cavs25 and other cavs/ace boards what to ignore even if duplicated. Signed-off-by: Tom Burdick <thomas.burdick@intel.com> |
3 years ago |
Fabio Baltieri
|
792469aae9 |
yamllint: indentation: fix files in samples/
Fix the YAML files indentation for files in samples/. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com> |
3 years ago |
|
Fabio Baltieri
|
5c32300861 |
yamllint: fix all yamllint truthy errors
Fix all thruthy errors detected by yamllint: yamllint -f parsable -c .yamllint $( find -regex '.*\.y[a]*ml' ) | \ grep '(truthy)' This only accepts true/false for boolean properties. Seems like python takes all sort of formats: https://github.com/yaml/pyyaml/blob/master/lib/yaml/constructor.py#L224-L235 But the current specs only mention "true" or "false" https://yaml.org/spec/1.2.2/#10212-boolean Which is the standard yamllint config. Excluding codeconv and workflow files, as some are using yes/no instead in the respective documentation. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com> |
3 years ago |
|
Jamie McCrae
|
cb50f2fb16 |
samples: external_lib: Add building on windows support
Adds support for building the external_lib sample application on a windows host operating system. Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no> |
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 |
|
Torsten Rasmussen
|
36ea41fad3 |
samples: introduce 'with_mcuboot' sample to show sysbuild feature
This sample is intended to show users how they can create a sample which has dedicated configuration files for extra images included in a build. MCUboot is used as example on how its default can be adjusted and MCUboot itself automatically be included in the build when using sysbuild. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> |
3 years ago |
|
Gerard Marull-Paretas
|
3976ccd5f7 |
include: add missing sys/printk.h include
Some files were using the printk API without including sys/printk.h Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> |
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 |
|
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 |
Kumar Gala
|
3f8ba07b90 |
usb_device: remove Kconfig.defconfig* setting of usb device drivers
Now that usb device drivers are enabled based on devicetree we need to remove any cases of them getting enabled by Kconfig.defconfig* files as this can lead to errors. Signed-off-by: Kumar Gala <galak@kernel.org> |
3 years ago |
|
Gerard Marull-Paretas
|
e2e9155dd5 |
boards: remove unused tag from supported list
All IEEE 802.15.4 tests/samples use DT-based filter now, so the ieee802154 tag can be deleted. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> |
3 years ago |
Hake Huang
|
cedc99b8ed |
samples: application_development: remove the code_relocation sample
covert this sample to a test cases Signed-off-by: Hake Huang <hake.huang@oss.nxp.com> |
3 years ago |
Benjamin Björnsson
|
ab4a926c27 |
boards: Add alias to boards with watchdog enabled
Add alias to boards with watchdog enabled to facilitate the move of samples/drivers/watchdog to use DT_ALIAS. Signed-off-by: Benjamin Björnsson <benjamin.bjornsson@gmail.com> |
3 years ago |
|
Andrzej Głąbek
|
800b086908 |
samples: code_relocation_nocopy: Update documentation
Extra steps for programming the external memory on nRF5340 DK are no longer needed. Now west is capable of handling this itself. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no> |
3 years ago |
|
Andrzej Głąbek
|
788fe5b4bf |
samples: code_relocation_nocopy: Fix initialization of external memory
Despite the comment it contains, the initialization procedure for the external memory chip on nRF5340 DK does not enable the High Performance Mode in the chip, so communication using a frequency higher than 8 MHz fails and the sample crashes (it works only right after programming the chip with nrfjprog, which enables the High Performance Mode, but the chip returns to the Low Power mode after the board is power-cycled). This commit fixes the initialization procedure and performs some additional clean-up. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no> |
3 years ago |