Free tools Windows power users keep installed
One-click scans. No signup required.
The usual way to use a silicon-vendor HAL in Zephyr is to consume the HAL repository as a Zephyr module, then decide separately whether your target SoC and board already have Zephyr platform support. A HAL module supplies reusable driver or library code and its CMake/Kconfig integration; SoC and board definitions supply the hardware description that makes an image build for a target. You may need one, the other, or both.
Start by separating the HAL from platform support
Zephyr treats silicon-vendor Hardware Abstraction Layers as a normal module category. A module is a repository described by zephyr/module.yml. That metadata connects the repository to Zephyr’s build system and can expose CMake, Kconfig, Devicetree, board, or SoC content.
A west project is not automatically a Zephyr module. West is commonly used to fetch repositories, while module.yml tells Zephyr how a repository participates in a build. A vendor repository can therefore be fetched by west without being usable as a module until its integration metadata exists.
| Question | HAL repository answers | Platform definitions answer |
|---|---|---|
| What code implements vendor peripherals or services? | Vendor source, headers, libraries and adaptation code | Not necessarily |
| How does Zephyr compile and configure that code? | module.yml, CMake and Kconfig integration |
May add SoC-level defaults |
| What SoC, peripherals and register ranges exist? | Only if the repository also owns platform data | Devicetree and SoC definitions |
Which board can be selected with -b? |
Only if board definitions are supplied | Board and SoC support |
Choose the integration shape
HAL-only module
Use this shape when Zephyr already supports the SoC and board. The module contributes vendor code, include paths, and software options, while the existing Zephyr platform description remains authoritative. Do not create a second SoC definition merely because the HAL repository contains register headers or startup code.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute#1 Best Overall
- 2.4GHz Dual Mode WiFi + Bluetooth Development Board
- Support LWIP protocol, Freertos
- SupportThree Modes: AP, STA, and AP+STA
- Ultra-Low power consumption, Compatible with Arduino IDE
- ESP32 is a safe, reliable, and scalable to a variety of applications
Module with platform definitions
Some repositories also provide SoC families, series metadata, Devicetree sources, or boards. In that case, the module can declare additional roots such as soc_root and dts_root. Add those roots only for definitions the module actually owns. A HAL library alone is not evidence that it should redefine an already-supported SoC.
In-tree versus out-of-tree platform work
| Approach | Best fit | Maintenance consequence |
|---|---|---|
| In-tree | Support intended for upstream Zephyr | Must follow Zephyr’s review, naming and maintenance expectations |
| Out-of-tree | Early development, private hardware or a staged upstream port | Your application or dedicated repository must keep custom board, DTS and SoC roots working across the pinned Zephyr release |
For modules included in Zephyr’s default manifest, the Zephyr documentation says: “They should also have a Zephyr developer that is committed to maintain the module codebase.” That expectation applies to default-manifest modules, not every private repository consumed by an application.
Check whether Zephyr already supports the target
- Name the exact target. Record the vendor, SoC part, series, board and pinned Zephyr release. HAL compatibility cannot be inferred from the family name alone.
- Search existing Zephyr support. Confirm whether the SoC and board definitions already exist. If you add a port, use the vendor’s official SoC name and avoid colliding with a name already in use.
- Decide ownership. If platform files are already present, consume the HAL without replacing them. If they are absent, plan a SoC and board port in addition to the HAL integration.
Make the vendor repository a usable module
Place or fetch the repository so the Zephyr build can discover it, then provide a zephyr/module.yml that describes the integration actually needed by that repository. CMake and Kconfig solve different problems and should be reviewed independently.
Rank #2
- Original ATmega328P CH340 chip is used. Improved new version CH340G Replace FT232RL.
- LAFVIN Nano V3.0 card is 100% compatible with the Nano card, and fully compatible with Windows, Mac and Linux operating system.
- Works the same as original Nano, runs perfectly on programming software.
- Using Atmel Atmega328P-AU MCU, Support ISP download; Support USB download and Power.
- LAFVIN Nano CH340 controller is a compact board similar to the R3 board, smaller and breadboard-friendly than Diecimila.
CMake responsibilities
- Add the HAL’s source files to the appropriate Zephyr targets.
- Expose vendor include directories and any generated headers.
- Add source files conditionally when a Kconfig option enables a feature.
- For a SoC port, expose additional sources and establish the baseline linker script where required.
Kconfig responsibilities
- Define software features that can be selected at build time.
- Express dependencies and defaults for the HAL integration.
- Keep software policy separate from the inventory of hardware peripherals.
Optional binary blobs
Some vendor HAL modules reference optional binary blobs. Declare and retrieve a blob only when the specific module requires it, and verify its licensing, provenance, version and reproducibility requirements. The existence of blob support in Zephyr modules does not mean a particular vendor HAL uses blobs or that its terms are acceptable for your product.
Build the SoC and board support when it is missing
A Zephyr SoC directory has distinct responsibilities. The porting guide identifies these core files:
| File | Purpose |
|---|---|
soc.yml |
Describes SoC family and series metadata. |
soc.h |
Provides SoC configuration macros where needed. |
Kconfig.soc |
Defines the SoC’s base software configuration. |
CMakeLists.txt |
Adds include paths and sources and can define the baseline linker script. |
SoC .dtsi |
Describes the hardware used by boards based on that SoC. |
Boards then include the SoC description and add board-specific hardware, chosen nodes and configuration. Keep the official vendor part name consistent across metadata, directory names and compatible strings.
Rank #3
- START CODING WITH THE ELEGOO UNO R3: Connect the included USB cable, upload your first sketch, and build sensor, motor, display, and automation projects, making it a practical controller for maker desks, classrooms, coding clubs, and robotics labs
- ATMEGA328P CORE FOR EVERYDAY PROJECTS: A 16 MHz clock, 32 KB flash, 14 digital I/O pins with 6 PWM outputs and 6 analog inputs provide a versatile foundation for LEDs, buttons, relays, servos, displays and sensors
- RELIABLE USB PROGRAMMING AND CLEAR WIRING: The ATmega16U2 USB interface supports sketch uploads and serial communication, while clearly labeled headers help simplify connections to jumper wires, shields and modules
- POWER AND EXPAND YOUR WAY: Run the board from USB or a recommended 7-12 V external supply, then add compatible shields and modules for data logging, automation, robotics, test fixtures and custom electronics projects
- BOARD AND USB CABLE INCLUDED: Comes with 1 ELEGOO UNO R3 development board and 1 USB-A to USB-B data cable; breadboard, sensors, shields and power adapter are not included, and younger learners should work with an experienced adult
Keep Devicetree and Kconfig boundaries clear
Put hardware facts in Devicetree
Devicetree describes peripherals, register ranges, interrupts, clocks, buses and boot-time hardware configuration. The final hardware description is assembled from the board files, SoC includes and overlays.
Put software choices in Kconfig
Kconfig selects features compiled into the image, such as whether a vendor library or driver is enabled. Zephyr can generate Kconfig symbols from Devicetree binding compatibles, allowing a driver to depend on an enabled hardware description without duplicating the entire hardware inventory in hand-written Kconfig.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Use module roots for out-of-tree definitions
If the module supplies custom platform data, its metadata can add board, Devicetree and SoC roots. An application or dedicated repository can therefore carry an out-of-tree platform while development proceeds before upstreaming. Use soc_root for SoC definitions and dts_root for additional architecture or SoC-family Devicetree content; do not set either root simply to make a HAL library visible.
Rank #4
- Powerful ESP-32 Board: Unlock the world of Internet of Things (IoT) and advanced electronics with the heart of this kit: the ESP-32 board. It features a powerful dual-core processor, integrated Wi-Fi and Bluetooth 4.2, making it perfect for building connected, smart devices that communicate with your phone or the cloud. It's fully compatible with the Arduino IDE for easy programming.
- Super Starter Kit: This kit contains over 35 different modules and electronic components, including sensors, displays, motors, and input devices. From LEDs and buttons to an OLED screen, servo motor, and keypad, you have everything needed to explore a vast range of projects in one box.
- Step by Step Online Tutorial: Jump right in with our detailed, beginner-friendly tutorial. Access 30+ projects with complete code, clear circuit diagrams, and step-by-step instructions. Learn the fundamentals of electronics, coding, and how to utilize the ESP-32's unique capabilities without any prior experience.
- Hands-on Learning for All Skill Levels: Perfect for students, makers, engineers, and hobbyists. Start with basic circuits and coding, then progress to intermediate and advanced IoT applications. Build practical projects like weather stations, smart home controllers, remote-controlled devices, and interactive gadgets. The skills you learn are the foundation for real-world innovation.
- Quality & Great Support: Elegoo is committed to quality. We provide a clear, detailed tutorial guide, refined code, and a well-organized component kit. All modules are carefully selected for reliability and ease of use. Our dedicated technical support team and active online community are ready to help you succeed in your learning journey.
Verify configuration, then validate behavior
- Configure a build for the intended board and release using the project’s normal west or CMake workflow.
- Inspect the generated
zephyr.dtsin the build directory. It is the resolved tree after board includes and overlays have been processed. - Check that the expected compatible nodes, register addresses, interrupts, clocks and chosen settings appear in that file.
- Review the generated configuration and build output to confirm that the intended HAL sources and Kconfig options were selected.
- Run target-specific tests on the real hardware: reset behavior, clocks, interrupts, peripheral transfers, power states and any vendor service that the application uses.
A correct zephyr.dts proves that configuration resolved as intended; it does not prove that the HAL behaves correctly on silicon. Runtime validation still depends on the exact vendor API, SoC revision, board wiring, toolchain and Zephyr release.
Common failure modes
- The repository is fetched but no HAL code builds: it may be a west project without
module.yml, or its CMake integration may not add the selected sources. - Kconfig symbols are missing: inspect the module’s Kconfig integration and whether the relevant menu is reachable for the selected board and SoC.
- Nodes are absent from
zephyr.dts: check the board include chain, overlays and whether the module’sdts_rootis active. - Two definitions conflict: remove the parallel SoC or compatible definition and determine which repository owns the platform data.
- The image links but hardware fails: treat this as a runtime or HAL adaptation problem, not proof that the module or Devicetree wiring is correct.
- A binary dependency blocks release: review the module’s blob metadata, retrieval process, verification and license before committing to that integration.
What must be pinned before you document a recipe
The title alone does not identify a universal vendor procedure. Before writing release-specific steps, pin the Zephyr version, HAL repository and revision, vendor and SoC, board, toolchain, compatibility requirements, API adaptation layer, license and any blob policy. Compare those details with the actual zephyr/module.yml, CMake, Kconfig, Devicetree and compatibility files in the chosen repository; the latest Zephyr documentation can change between releases.
Frequently Asked Questions
Do I have to copy a vendor HAL into the Zephyr tree?
No. A vendor HAL can remain in an external repository and be consumed as a Zephyr module. Copying it into the Zephyr tree is not implied by using the HAL.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- Dual-Core Performance Up to 240 MHz: Run sensor processing, wireless communication, automation logic and connected-device tasks on a 32-bit dual-core ESP32 platform designed for responsive embedded and IoT projects
- Built-in Wi-Fi and Bluetooth 4.2: Connect to 2.4 GHz Wi-Fi networks or use Bluetooth Classic and BLE for wireless sensors, smart devices, remote controls, home automation and other connected projects
- Flexible Power-Saving Modes: ESP32 power-management features support dynamic clock scaling and low-power operating modes, helping developers reduce energy use in compatible sensing, monitoring and connected-device applications, suitable for battery-powered Internet of Things (IoT) devices.
- USB-C Programming with CP2102: Connect through USB-C for power, sketch uploads and serial monitoring, while GPIO, UART, SPI and I2C interfaces support sensors, displays, motor drivers and other modules (USB-C cable not included)
- Over-the-Air Update Support: Configure OTA functionality through a compatible ESP-32 software framework to update deployed firmware over Wi-Fi without reconnecting the board by USB for every revision
When should a HAL module define soc_root or dts_root?
Only when that module owns the corresponding SoC or Devicetree definitions. A library-only HAL should not redefine an already-supported platform.
Does a generated zephyr.dts prove the HAL works?
No. It verifies the resolved hardware description after configuration. Peripheral operation, interrupts, clocks and vendor-library behavior still require target-specific runtime tests.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
