The current way of setting the public address using
`bt_hci_driver_api::setup` does not work well in split builds
where host and controller runs on different cores/socs/boards.
This approach requires each HCI driver and each `hci_<transport>`
application to implement the setup and pass the information on
to the next layer.
Zephyr already defines a vendor-specific command that can be used
to set the public address (`bt_hci_cp_vs_write_bd_addr`).
Use this in `bt_enable` after opening the HCI transport and before
initializing the id module. This makes the setup independent of
hci transport and only depends on a controller that implements the
Zephyr HCI VS commands.
Signed-off-by: Herman Berget <herman.berget@nordicsemi.no>
Fixes the dts files to properly use addresses, also reduces the
number of files by using SoC files instead of (duplicate) board
overlay files
Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Add board overlay file for pic32cx_sg41_cult
to enable adc test cases to run on this board
Signed-off-by: Farsin Nasar V A <farsin.nasarva@microchip.com>
Add ADC0 and ADC1 pinctrl definitions and update the board metadata
to list ADC as a supported feature on the pic32cx_sg61_cult board.
Signed-off-by: Farsin Nasar V A <farsin.nasarva@microchip.com>
Add ADC0 and ADC1 pinctrl definitions and update the board metadata
to list ADC as a supported feature on the pic32cx_sg41_cult board.
Signed-off-by: Farsin Nasar V A <farsin.nasarva@microchip.com>
Remove QEMU DTS-based support for the versal2_rpu board. The QEMU
devicetree configuration files do not conform to the devicetree
specification and use non-standard properties and conventions
specific to AMD/Xilinx QEMU.
As discussed in PR #100254 and PR #103535, QEMU DTS files should
not reside in the Zephyr tree since they are not valid devicetree
files per the DTS specification. These files serve as QEMU
configuration and will be maintained separately.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.kedareswara.rao@amd.com>
Update the C++ language support documentation to require applications
to return 0 from main(), matching the C language support page.
Signed-off-by: Somil Gupta <somil24559@iiitd.ac.in>
Move the Kconfig template to configure the number of instances in, for
example, functions or class drivers, to a common directory.
This makes it less confusing when used in host support.
Template was not used in CDC ECM function and can be removed.
Signed-off-by: Johann Fischer <johann.fischer@nordicsemi.no>
Replaces the previous static bearer registration with a dynamic
runtime registration flow driven by Auto-PTS. This allows the
tester to create GTBS and TBS instances at runtime with complete
metadata in the correct registration orders.
Signed-off-by: Alex Ciascai <ciascai.alexandru@gmail.com>
Some of the peripherals might be used in the bootloader
and not cleaned up properly for the next image in the boot chain.
Ensure that affected registers are always cleaned up before use.
Signed-off-by: Nikodem Kastelik <nikodem.kastelik@nordicsemi.no>
Now able to be used both by nRF54LM20A and nRF54LM20B.
Also, removed Eng A naming and aligned board.yml
to memory described in common DTS.
Signed-off-by: Michał Stasiak <michal.stasiak@nordicsemi.no>
Move the external memory chip definition from the CPUAPP-specific to the
common DTS.
The existence of the external chip is not APP-specific, but a
characteristic of the DK itself.
Signed-off-by: Tomasz Chyrowicz <tomasz.chyrowicz@nordicsemi.no>
- Adds the common dtsi files based on memory configuration and pin
configuration
- Adds the gpio nodes in pic32cm_pl10 series
- Adds the list of supported socs
Signed-off-by: Mohamed Azhar <mohamed.azhar@microchip.com>
Signed-off-by: Muhammed Asif <muhammed.asif@microchip.com>
With introduction of Key-Value Storage Systems subsystem, NVS and ZMS
have been moved outside of VFS and require update in interface header
paths.
Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
As the TDTxR registers reset value is undefined they must be fully
initialized when used.
Without full initialization, the TGT bit might be inadvertently set,
causing the 16-bit timestamp to be sent as the last two data bytes
when CONFIG_CAN_RX_TIMESTAMP is enabled.
Fixes: #98768
Signed-off-by: Giuseppe Iellamo <giellamo@gmail.com>
