Nrf54h20dk mcuboot aliases #3369
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Do not select CONFIG_SYS_MEM_BLOCKS when enabling the Atmel SAM0 USB device controller driver as the implementation does not use the system memory blocks allocator. Signed-off-by: Henrik Brix Andersen <[email protected]>
Fix the issue reported by Coverity CID 487708. The LL_ASSERT was performed on lll->ptc, which is a 4-bit bitfield and therefore always succeeds. Instead, the computation (lll->nse - nse) should be checked to ensure it falls within the 4-bit value range before assigning it to lll->ptc. Signed-off-by: Loic Domaigne <[email protected]>
- Tested with BeagleConnect Freedom. - Also enable building in CI. Signed-off-by: Ayush Singh <[email protected]>
- Tested with BeagleConnect Freedom. - Also enable build in CI similar to echo_server/client Signed-off-by: Ayush Singh <[email protected]>
Fix the incorrect usage of Kconfig symbols and revert back the default behavior to allow for non-active slot confirmation. Signed-off-by: Tomasz Chyrowicz <[email protected]>
It is essential for the overwrite mode to allow confirming the secondary slot to provide the permanent update. This types of updates is the only mode in which the application may be upgraded. Signed-off-by: Tomasz Chyrowicz <[email protected]>
Add gpio_dt_spec based helpers for easier access to: * gpio_emul_input_set * gpio_emul_output_get * gpio_emul_flags_get Signed-off-by: Maximilian Werner <[email protected]>
The ZMS backend for Settings uses the `flash_area` API, which means it requires CONFIG_FLASH_MAP to be enabled, so update Kconfig accordingly. Note that ZMS itself does not depend on this. Signed-off-by: Grzegorz Swiderski <[email protected]>
This reverts commit 77f19eb. This dependency was misplaced. See the parent commit. Signed-off-by: Grzegorz Swiderski <[email protected]>
Add bindings for SF32LB RTC. Signed-off-by: Gerard Marull-Paretas <[email protected]>
Add node for RTC peripheral. Signed-off-by: Gerard Marull-Paretas <[email protected]>
Add binding for the SiFli SF32LB RTC backup registers. Signed-off-by: Gerard Marull-Paretas <[email protected]>
Define RTC backup registers. Signed-off-by: Gerard Marull-Paretas <[email protected]>
Boot ROM will by default set on/off delays to 0ms before jumping to firmware. This patch adds an option to to configure the on/off delays to non-zero values. A flash power cycle guarantees to put the external flash into a known state before executing code from it. This is required if using 4-byte address mode in the external flash, as the boot ROM will always use 3-byte address mode when reading from external flash, causing a potential deadlock situation requiring a power-cycle (known errata). Signed-off-by: Gerard Marull-Paretas <[email protected]>
Refactor a bit the RX FIFO handling to prevent RX transfers performed in Single IO mode from getting stuck when they are suspended due to the empty TX FIFO and cannot be resumed because there is no further interrupt in which the TX FIFO could be filled properly with dummy bytes above its transfer start level. Signed-off-by: Andrzej Głąbek <[email protected]>
Full CMUX frames are way too much to fill the debug log so disable those by default. Sometimes it is enough to see the CMD and response types, without hexdump. Added also debug messages for opening and closing events. Signed-off-by: Seppo Takalo <[email protected]>
Update hal_nordic to pull mdk 8.72.4 with mdk changes for nRF7120. Signed-off-by: Robert Robinson <[email protected]>
- Adds frdm_mcxn236.conf board configuration for ZMS sample and ZMS test. - Its Flash write-size is 128, which requires special configuration. Signed-off-by: Andrej Butok <[email protected]>
Adjust CONFIG_STEPPER_TEST_TIMING_TIMEOUT_TOLERANCE_PCT in order to pass the tests Signed-off-by: Jilay Pandya <[email protected]>
During testing with teensy 4.0 it was discoverd that toggling at high frequencies led to missed steps. As per the datasheets of step-dir drivers an active edge needs to be maintained for a certain timerperiod, for a step to be executed. Instead of toggling pin twice instantaneously, the current fix halves the step period and the step-pin is toggled on the timeout of the respective timing source. rework stepper stepper stop set step pin to low if the driver does not support dual edge and increment/decrement the actual position by one Signed-off-by: Jilay Pandya <[email protected]>
To prepare for further patches and separation of interrupt/DMA modes from polled, this commit introduces two helpers for starting and stopping DMA transfers Finsishing DMA transfers are also moved from interrupt handlers to thread after beeing wokenen by semaphore Signed-off-by: Erik Andersson <[email protected]>
- Rework transaction flow to better match reference manual and errata sheet for STM32 I2Cv2 peripheral - Handle message transactions larger than 255 bytes in isr - Combine stm32_i2c_msg_write and stm32_i2c_msg_read into one common function stm32_i2c_irq_xfer when using interrupts Signed-off-by: Erik Andersson <[email protected]>
stm32_i2c_msg_read and stm32_i2c_msg_write for interrupt mode is replaced by a common function: stm32_i2c_irq_xfer Signed-off-by: Erik Andersson <[email protected]>
Adapt DMA implementation to match changes introduced by new interrupt handler Signed-off-by: Erik Andersson <[email protected]>
Don't abort transaction on bus error in master mode according to errata sheet Signed-off-by: Erik Andersson <[email protected]>
The stm32_i2c_master_mode_end function can be replaced with a simple irq disable and giving to the device sync semaphore Signed-off-by: Erik Andersson <[email protected]>
If configuration of DMA is unsuccessful then abort transaction and return with an error code Signed-off-by: Erik Andersson <[email protected]>
Fixes #91045 Adding NO_SPLIT in the TOOLCHAIN_LD_FLAGS list caused every flags in the list to be checked together by the linker. This caused issues where incompatible flags was passed together, and the result was that none was propagated to the linker. By using separate variables, we can achieve the initial goal of NO_SPLIT to only group a sub-set of flags. Signed-off-by: Pierrick Guillaume <[email protected]>
Add 'ax' flags for .sof_entry ELF section so it merges properly with .z_xtensa_vectors ELF section Signed-off-by: Andrew Perepech <[email protected]>
On MT8188 platform timer interrupts must also be enabled/disabled in MTK_ADSP_IRQ_EN register in addition to xtensa_irq_enable(), xtensa_irq_disable() Signed-off-by: Andrew Perepech <[email protected]>
The connection using EAP-PEAP-TLS with Cisco AP is failed for IW610, and the console log shows 'Memory allocation failed (-0x3f80)'. Increase the MBEDTLS_HEAP_SIZE for 10K can fix this issue. Signed-off-by: Maochen Wang <[email protected]>
Add .resource_table section to the linker script for the Cortex-A core of i.MX series. Signed-off-by: Hou Zhiqiang <[email protected]>
Deletes special LittleFS configuration for the FRDM-MCXA156 board. It's not required after MCXA156 flash write-program-size was reduced from 128 to 16 bytes. Signed-off-by: Andrej Butok <[email protected]>
The NRFX SAADC device driver needs to implement PM DEVICE for it to work with power domains, which is required for some SoCs. Inline PM device runtime "self get/put" pm has been implemented for the normal sync read API. Signed-off-by: Bjarki Arge Andreasen <[email protected]>
The ADC and COMP on the nrf54h20 both have all of their analog inputs routed to pads in different power domains than themselves, this means the device drivers for both of them need to request the pads to be resumed when active to allow any reading of the pads. To keep the drivers simple, we can rely on HW to keep the power domain the COMP and ADC are in powered, which happens automatically when the ADC or COMP is ENABLED. We can then place them on the power domain of their pads in the devicetree. This ensures the pads are powered and not retained while the devices are RESUMED. Signed-off-by: Bjarki Arge Andreasen <[email protected]>
Zephyr crashes when a new websocket connection is refused by the user supplied callback function. This is caused by multiple calls of close_client_connection(). After the first call the file handle and the client->service pointer are invalid. This fix checks if the file handle is valid. Signed-off-by: Andreas Schweigstill <[email protected]>
`file(COPY_FILE ...)` is from CMake 3.21. Zephyr still supports CMake 3.20, so use zephyr_file_copy(...) instead of `file(COPY_FILE ...)`. Signed-off-by: Torsten Rasmussen <[email protected]>
Remove all function calls for functions that are defined in the stm32xxxx_ll_rtc.c and replaces them by simpler calls from the header file. Also remove the use of LL_RTC_AlarmTypeDef since no functions from the header file uses it. Signed-off-by: Guillaume Gautier <[email protected]>
Remove the calls to LL_RTC_Init, LL_RTC_DeInit and LL_RTC_ALMA_Init in the RTC counter driver. This avoids calling functions from stm32xxxx_ll_rtc.c. They are replaced by a set of simpler functions from the header file. Signed-off-by: Guillaume Gautier <[email protected]>
Usage of stm32xxxx_ll_tim.c has been removed so we can also remove the selection of USE_STM32_LL_TIM from the Kconfig. Signed-off-by: Guillaume Gautier <[email protected]>
Usage of stm32xxxx_ll_tim.c has been removed so we can also remove the selection of USE_STM32_LL_TIM from the Kconfig. Also remove the LL_RCC that plays no part in the driver. Signed-off-by: Guillaume Gautier <[email protected]>
REQUEST_QUEUE was passed as queue_num to virtio_init_virtqueues where REQUEST_QUEUE+1 was required Signed-off-by: Jakub Michalski <[email protected]>
virtio_pci_init_virtqueues was allocating more virtqueues than specified by num_queues param if data->common_cfg->num_queues was greater than num_queues Signed-off-by: Jakub Michalski <[email protected]>
Fix the check in dwc2_unset_dedicated_fifo() that wrongly included the current endpoint when testing for higher FIFOs. This caused false warnings and early returns. Use ~BIT_MASK(ep_idx + 1) to only test FIFOs above the current EP. Signed-off-by: Sylvio Alves <[email protected]>
A column was missing Signed-off-by: Alberto Escolar Piedras <[email protected]>
If the process does an exec() (or fork, or..) all descriptors are kept open by default, unless O_CLOEXEC is set for them. (This default behaviour is usefull for stdin/out/err so that new process is kept connected to them, but it is very rare for it to be usefull for any other descriptor) In general this leads to descriptors being kept open unnecessarily, which either will block other process from using them (for example if the child survives the parent but it does something else while keeping a port open). Or for a "leak" which unnecessarily uses descriptors and memory in the child process. Let's ensure we do not leak it for this component as we do not need it. Signed-off-by: Alberto Escolar Piedras <[email protected]>
If the process does an exec() (or fork, or..) all descriptors are kept open by default, unless O_CLOEXEC is set when opening them. This is usefull for stdin/out/err so that new process is connected to them, but it is very rare for it to be usefull for any other descriptor. In general this leads to descriptors being kept open unnecessarily, which either will block other process from getting them (for example if the child survives the parent but it does something else). Or for a "leak" which unnecessarily uses descriptors and memory in the child process. Let's ensure we do not leak it for this component as we do not need it. Signed-off-by: Alberto Escolar Piedras <[email protected]>
If the process does an exec() (or fork, or..) all descriptors are kept open by default, unless O_CLOEXEC is set when opening them. This is usefull for stdin/out/err so that new process is connected to them, but it is very rare for it to be usefull for any other descriptor. In general this leads to descriptors being kept open unnecessarily, which either will block other process from getting them (for example if the child survives the parent but it does something else). Or for a "leak" which unnecessarily uses descriptors and memory in the child process. Let's ensure we do not leak it for this component as we do not need it. Signed-off-by: Alberto Escolar Piedras <[email protected]>
If the process does an exec() (or fork, or..) all descriptors are kept open by default, unless O_CLOEXEC is set when opening them. This is usefull for stdin/out/err so that new process is connected to them, but it is very rare for it to be usefull for any other descriptor. In general this leads to descriptors being kept open unnecessarily, which either will block other process from getting them (for example if the child survives the parent but it does something else). Or for a "leak" which unnecessarily uses descriptors and memory in the child process. Let's ensure we do not leak it for this component as we do not need it. Signed-off-by: Alberto Escolar Piedras <[email protected]>
If the process does an exec() (or fork, or..) all descriptors are kept open by default, unless O_CLOEXEC is set when opening them. This is usefull for stdin/out/err so that new process is connected to them, but it is very rare for it to be usefull for any other descriptor. In general this leads to descriptors being kept open unnecessarily, which either will block other process from getting them (for example if the child survives the parent but it does something else). Or for a "leak" which unnecessarily uses descriptors and memory in the child process. Let's ensure we do not leak it for this component as we do not need it. Signed-off-by: Alberto Escolar Piedras <[email protected]>
If the process does an exec() (or fork, or..) all descriptors are kept open by default, unless O_CLOEXEC is set when opening them. This is usefull for stdin/out/err so that new process is connected to them, but it is very rare for it to be usefull for any other descriptor. In general this leads to descriptors being kept open unnecessarily, which either will block other process from getting them (for example if the child survives the parent but it does something else). Or for a "leak" which unnecessarily uses descriptors and memory in the child process. Let's ensure we do not leak it for this component as we do not need it. Signed-off-by: Alberto Escolar Piedras <[email protected]>
If the process does an exec() (or fork, or..) all descriptors are kept open by default, unless O_CLOEXEC is set when opening them. This is usefull for stdin/out/err so that new process is connected to them, but it is very rare for it to be usefull for any other descriptor. In general this leads to descriptors being kept open unnecessarily, which either will block other process from getting them (for example if the child survives the parent but it does something else). Or for a "leak" which unnecessarily uses descriptors and memory in the child process. Let's ensure we do not leak it for this component as we do not need it. Signed-off-by: Alberto Escolar Piedras <[email protected]>
If the process does an exec() (or fork, or..) all descriptors are kept open by default, unless O_CLOEXEC is set when opening them. This is usefull for stdin/out/err so that new process is connected to them, but it is very rare for it to be usefull for any other descriptor. In general this leads to descriptors being kept open unnecessarily, which either will block other process from getting them (for example if the child survives the parent but it does something else). Or for a "leak" which unnecessarily uses descriptors and memory in the child process. Let's ensure we do not leak it for this component as we do not need it. Signed-off-by: Alberto Escolar Piedras <[email protected]>
If the process does an exec() (or fork, or..) all descriptors are kept open by default, unless O_CLOEXEC is set when opening them. This is usefull for stdin/out/err so that new process is connected to them, but it is very rare for it to be usefull for any other descriptor. In general this leads to descriptors being kept open unnecessarily, which either will block other process from getting them (for example if the child survives the parent but it does something else). Or for a "leak" which unnecessarily uses descriptors and memory in the child process. Let's ensure we do not leak it for this component as we do not need it. Note glibc fopen supports the "e" modifier as an extension to pass O_CLOEXEC to the open syscall. Signed-off-by: Alberto Escolar Piedras <[email protected]>
commands should not have spaces around hyphens: version - extended --> version-extended build - version --> build-version Fixes: zephyrproject-rtos/zephyr#96591 Signed-off-by: Benjamin Cabé <[email protected]>
Add description of new LVGL Kconfig options to specify the zephyr regions used by LVGL. Signed-off-by: Alain Volmat <[email protected]>
Added aliases so that nrf54h20dk/nrf54h20/cpuapp can use MCUboot serial recovery. Signed-off-by: Andrzej Puzdrowski <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
85 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.