Українською
  In English
Feed aggregator
Ground penetrating radar: How RF waves map the unseen world

Beneath every road, field, or foundation lies a hidden story of layers and boundaries. Engineers, archaeologists, and surveyors have long sought ways to uncover these subsurface details without disturbing the ground itself.
That’s where ground penetrating radar (GPR) steps in, an elegant blend of physics and practicality, turning invisible transitions beneath our feet into readable signals.
GPR isn’t a magical “x‑ray vision for the ground”—it’s far more precise. Think of it as an RF boundary‑detector, a tool that listens for echoes not in sound but in electromagnetic waves. Just as a shout in an alleyway bounces back when it strikes a wall, GPR pulses return when they encounter a shift in material properties beneath the surface.
The key is that GPR doesn’t reflect off objects themselves; it responds to dielectric discontinuities—the invisible boundaries where one material’s permittivity changes to another, revealing hidden layers and structures without ever breaking the ground.
The physics of wave travel
At the heart of GPR lies the concept of dielectric permittivity—a property that tells us how easily a material allows electromagnetic fields to pass through. Different soils, rocks, and man‑made materials each have their own relative permittivity, and this directly controls how fast radar waves move within them.
In simple terms, the higher the permittivity, the slower the wave travels. This change in speed is what creates the echoes GPR listens for, turning invisible boundaries underground into detectable signals.

Figure 1 See the Radiodetection LMX200 GPR system equipped with a high-resolution display screen and integrated GPS antenna. Source: Sensors & Software
As a quick aside, integrating GPS into GPR systems transforms isolated subsurface radar profiles into precise, geographically-referenced 3D spatial models by linking every emitted radar pulse directly to real-world latitude, longitude, and elevation coordinates. While traditional GPR setups rely on mechanical measuring wheels that are prone to slippage and drift on rough terrain, high-precision GPS—particularly real-time kinematic (RTK) systems—enables survey teams to walk or drive freeform paths without painting manual grid lines on the ground.
That automatically corrects radar depth profiles for uneven ground topography and allows operators to export exact utility locations directly into GIS, CAD, or Google Earth for accurate long-term relocation and excavation safety.
Materials and their echoes
Different ground materials shape radar signals in strikingly different ways. Air offers almost no resistance, so waves travel at full speed. Dry soil or concrete slows them moderately, with values that vary depending on density and composition.
Water, however, is a dramatic case; its high permittivity means radar waves crawl through it, creating strong reflections and explaining why wet soil can overwhelm a survey. And when waves meet metal, the contrast is so extreme that the signal is completely reflected, producing a sharp boundary echo.
Choosing the right frequency is a balancing act. High‑frequency radar (in the gigahertz range) delivers fine detail, capable of spotting millimeter‑scale features, perfect for scanning rebar in concrete or mapping shallow structures. But those same waves are quickly absorbed, limiting penetration to less than a meter.
Low‑frequency radar, on the other hand, can reach tens of meters into the ground, revealing large formations like bedrock layers. The trade‑off is resolution: small pipes or fine details blur away, leaving only the bigger picture.
Hardware architecture and RF front‑end
An impulse GPR system is built around a few critical segments, each designed to handle the unique challenges of probing beneath the surface.
- Transmitter: At the front-end, the transmitter fires sub‑nanosecond, high‑voltage pulses into an ultrawideband antenna, often bow‑tie or tapered slot designs. The challenge here is pulse purity: any “ringing” or lingering oscillation can blur the radar’s timing, so engineers work hard to shape clean, sharp impulses.
- Receiver: On the other side, the receiver must be remarkably versatile. Soil attenuation is exponential, meaning shallow reflections can be overwhelmingly strong while deep echoes may arrive as faint microvolt signals. A high‑dynamic‑range front‑end ensures both extremes are captured without distortion.
- Time‑domain sampling: Capturing these fleeting pulses requires clever timing. Techniques like equivalent time sampling (ETS) allow picosecond‑scale events to be reconstructed using manageable hardware budgets, while high‑speed ADCs paired with MCUs or DSPs provide direct digitization for modern designs.
- Frequency domain (SFCW): Not all GPR systems rely on impulses. Stepped‑frequency continuous wave (SFCW) radar takes a different approach, sweeping through frequencies with direct digital synthesizers (DDS). While impulse systems excel at sharp time resolution, SFCW offers fine frequency control and can be easier to process digitally, making it a strong alternative in certain applications.
Data and signal processing: Why everything looks like a hyperbola
GPR data begins with the A‑scan, a single trace of signal amplitude versus time delay at one position, and expands into the B‑scan, where multiple A‑scans are stacked as the antenna moves to form a two‑dimensional cross‑section. Within these B‑scans, point targets such as buried pipes consistently appear as upside‑down hyperbolas.
This familiar curve isn’t a flaw but the natural result of geometry: as the antenna approaches the target, the travel path shortens; directly above it, the path is at its minimum; and as the antenna moves past, the path lengthens again. The changing slant‑range distance produces the hyperbolic signature that surveyors rely on to distinguish compact objects from broader subsurface layers.

Figure 2 Line scan GPR display showing signal amplitude versus depth and position. Conical radar emission creates a characteristic hyperbolic reflection for point targets (pipes, rocks, roots) with the target’s true location marked by the apex of the hyperbola. Source: Author
Practical engineering takeaway and workbench experiment
Modern radar technology has become accessible enough that even hobbyists and bench engineers can explore its principles. Compact ultrawideband (UWB) radar chips, low‑cost vector network analyzer modules like the NanoVNA, and software‑defined radios (SDRs) make it possible to experiment with frequency‑modulated continuous wave (FMCW) or stepped‑frequency continuous wave (SFCW) radar on a workbench. These tools allow hands‑on exploration of how signals reflect, attenuate, and reveal boundaries—without the need for industrial‑scale equipment.

Figure 3 VNA6000 (NanoVNA V3) delivers two-port 6 GHz vector network analyzer performance comparable to higher-end professional instruments in a small, portable form factor. Source: NanoRFE
But GPR isn’t invincible. Certain ground conditions can break its effectiveness. High clay content soils absorb signals aggressively, saltwater intrusion creates strong conductive losses, and hyper‑conductive soils scatter energy so severely that useful echoes vanish. These edge cases remind engineers that while GPR is powerful, its success depends on the physics of the medium it probes.
Beyond the basics
A few practical realities complete the picture for engineers working with GPR. Antenna choice is critical: ground‑coupled designs dig deeper into the soil, while air‑coupled antennas favor resolution and portability. Calibration and clutter removal—through baseline subtraction and background filtering—help suppress system ringing and surface noise.
Modern systems also extend beyond simple B‑scans, building C‑scans or even full 3D reconstructions with migration algorithms. Because GPR operates in ultrawideband ranges, spectrum regulations and licensing must be considered before deployment.
In the field, sensor fusion is common, with GPS adding georeferencing and magnetometers to provide complementary subsurface data. And interpretation always demands caution: tree roots, voids, or soil heterogeneity can mimic hyperbolic signatures, reminding us that while GPR is powerful, its results must be read with care.
GPR reminds us that the world beneath our feet is full of hidden boundaries waiting to be revealed. From professional surveyors mapping infrastructure to hobbyists experimenting with SDRs on a workbench, the same principles of echoes and discontinuities apply. The challenge is real—wet soils, clays, and conductive layers can frustrate even the best systems—but the opportunity is greater: to explore, to innovate, and to make the invisible visible.
Well, whether you’re an engineer, a student, or simply curious, take the next step. Try a bench‑scale experiment, dive into open‑source SDR projects, or look at your environment with new eyes. GPR isn’t just about scanning the ground; it’s about cultivating the mindset to uncover what lies beneath.
T. K. Hareendran is a self-taught electronics enthusiast with a strong passion for innovative circuit design and hands-on technology. He develops both experimental and practical electronic projects, documenting and sharing his work to support fellow tinkerers and learners. Beyond the workbench, he dedicates time to technical writing and hardware evaluations to contribute meaningfully to the maker community.
Related Content
- Radar Essentials
- Ultrawideband radar system design
- Radar Basics: Range, Pulse, Frequency, and More
- Challenges in designing automotive radar systems
- 3-D radar data-capture innovation makes IEDs easier to spot
The post Ground penetrating radar: How RF waves map the unseen world appeared first on EDN.
Free form fan fun.
| Went through a few designs on this. Eventually, simplified the final one. Plant buddies need more air flow. A 12 dollar bucks Target fan would work but that’s SO BORING. Wanted something fun to look at and practical. Played off free form style. Improvised a lot. Made it work. Originally had an arduino powering a driver with a servo moving the fan. Worked but was foo complicated. Plus powering a driver and a microcontroller was unnecessarily complicated. Stripped it down to a mosfet driver with pot to control speed. Put it on a 9v. Done. Easy. Aesthetically fun and practical. Love it. Will definitely do another one. [link] [comments] |
Old tubes (older than even me) - Moose Jaw, Saskatchewan
| submitted by /u/1Davide [link] [comments] |
Latest issue of Semiconductor Today now available
Mouser Launches Alternative Energy Resource Hub for Decentralised Systems
Mouser Electronics, Inc., a leading distributor in new product introduction (NPI) that drives innovation, supports designers with its online resource centre dedicated to alternative energy sources, providing technical content and practical insight for the development of cleaner, more efficient, sustainable and decentralised energy systems. The Resource Centre promotes advances in renewable energy generation, energy harvesting and smart grids, bringing together emerging concepts in the energy sector with the components and design approaches needed to implement them.
From the grid to the device: technologies for a decentralised energy ecosystemRenewable energy is moving from an emerging technology to a central element in the design of components and systems. Mouser’s Alternative Energy Resource Centre gives designers insight into the electronics and infrastructure needed to make energy generation systems more reliable, sustainable and scalable, with content dedicated to energy storage systems, smart grids, sensors, power electronics, IoT and artificial intelligence.
New forms of energy rely on an interconnected ecosystem of technologies working in synergy. From next-generation solar cells to self-powered IoT devices, that ecosystem is becoming increasingly decentralised. Perovskite-silicon tandem solar cells could make renewable energy generation more efficient and versatile, while decentralised power grids can help integrate energy generated by homes, businesses and local systems. At device level, energy harvesting carries this transformation forward, letting IoT sensors capture energy from sources such as light, heat and vibration. Together, these technologies show how energy generation and management are moving closer to the places where the energy is needed.
Technical content and new products for alternative energyMouser’s technical team and trusted manufacturing partners regularly update the Resource Centre with articles, blogs, eBooks and new products for alternative energy solutions, offered by the sector’s leading manufacturers. These resources let designers understand how energy technology development is evolving and how emerging energy systems can support scalable solutions that work in the real world.
Mouser offers the industry’s widest selection of semiconductors and electronic components, including the latest solutions for alternative energy applications. Here are a few examples of new products:
- The AEM13921 PMIC for ultra-high-efficiency power management from e-peas harvests and manages energy from several sources, including photovoltaic, RF, vibration and pulse sources. The PMIC acquires, stores and delivers power to support low-power IoT applications, smart building systems and industrial sensing.
- The HC-STAK 35 high-voltage interconnection system from TE Connectivity transfers high-voltage power between batteries, inverters, motors and power distribution systems, reducing resistance and power losses in electric and hybrid vehicle architectures.
- The TLE9012DQU integrated circuit (IC) from Infineon Technologies for lithium-ion battery monitoring and balancing is designed to monitor and balance lithium-ion battery cells by measuring their voltage and temperature and coordinating cell balancing. In this way, the IC helps optimise battery performance and reliability in electric vehicles and energy storage systems.
- The Altivar
ATV320 solar variable speed drives (VSD) from Schneider Electric convert and manage solar energy to power motors directly in applications such as pumping and irrigation, switching to the grid when the available solar energy is not enough to meet demand.
To learn more, visit the Alternative Energy Resource Centre page. For further news about Mouser and the latest product news, visit the Mouser newsroom.
Mouser’s support for designersAs an authorised global distributor, Mouser offers the widest selection of semiconductors, latest-generation electronic components and the newest products for industrial automation. Mouser customers can count on genuine products, 100% certified and fully traceable, for each of their partner manufacturers. To help speed up customer projects, Mouser’s website hosts a vast library of technical resources, including a Technical Resource Centre, and offers product datasheets, supplier-specific reference designs, application notes, design technical data, engineering tools and other useful information.
Mouser offers thousands of industrial automation products, available in stock and ready for immediate shipment. From predictive maintenance devices and control panels to a complete range of industrial power products, sensors and safety devices, Mouser’s portfolio is available to customers to help them design, build and maintain complete automation solutions. For more information, visit Mouser’s industrial automation solutions page.
For more information about Mouser Electronics, visit www.mouser.it.
The post Mouser Launches Alternative Energy Resource Hub for Decentralised Systems appeared first on Open Electronics.
A Digital Electronic Sieve Built with Thirty ATtiny412 Chips
This electronic number sieve recreates a 1982 project using modern microcontrollers. The principle is simple: discard the candidates that are impossible for a quadratic equation by using arithmetic modulo small primes. Thirty ATtiny412 chips, one per modulus, filter the numbers, while a Raspberry Pi Pico clocks them and verifies the survivors. The author is KB Sriram.
The idea of filtering numbers with hardware is far older than software. The first number sieve, built in 1928 by the mathematician D. H. Lehmer, used 19 bicycle chains mounted on a common shaft. The gear sieve of 1932 is outperformed by the modern version by roughly 100 times.
How the sieve with thirty ATtiny412 chips worksEach ATtiny412 handles a single modulus and keeps in memory a repeating accept-or-reject pattern. All the chips share an open-drain line: any chip that rejects pulls it low, so the line stays high only when no chip has rejected. The Raspberry Pi Pico generates the shared clock and advances all thirty microcontrollers simultaneously through their patterns.
A module based on the ATtiny412.
Only when all the microcontrollers stay silent does the Pico run the mathematical test, which is much slower. The system spends almost all its time rejecting numbers quickly instead of computing them. At full speed the modern hardware evaluates about 500,000 candidates per second.
- Each ATtiny412 handles a single prime modulus.
- The chips share an open-drain line for rejection.
- The Raspberry Pi Pico generates the shared clock.
- The slow mathematical test only runs on the survivors.
- The moduli are loaded over I2C.
The ATtiny412 firmware is written in C and compiled with avr-gcc, in the avr/ folder of each build. The host code for the Pico lives in the rpi/ folder. Build 01 uses a CircuitPython runtime and solves the equation y^2 – 2x^2 = 4001, with three hardcoded moduli, advanced by a button and a buzzer on the shared line.
Build 02 moves to MicroPython, loads the moduli over I2C and clocks them at 50 kHz from the Pico’s PIO. With this build the sieve factored the number 5,283,065,753,709,209. Build 04 qualifies the moduli before shipping, with a diagnostic image and a check of the header pins from the Pico.
Build 05 mounts thirty boards on a stripboard backplane, runs a self-check over I2C before a run, and measures the REQ-to-VOTE timing with all thirty fitted. Build 06 stays on the stripboard backplane and adds the historical benchmarks: 1928 bicycle chains, the 1932 gear machine, the 1970 DLS-127, up to 500 kHz. The thirty ATtiny412 chips are clocked up to 500 kHz.
For anyone who wants to rebuild the project, KB Sriram’s repository collects the code for the builds, with the avr-gcc firmware and the host code for the Pico. The mini development board based on the RP2040 covers the role of the Pico, with a dual-core RP2040 microcontroller, USB-C and multiple GPIO. Mounting on stripboard requires the thirty ATtiny412 chips and the backplane.
In 2001 Daniel J. Bernstein described an algorithm that directly generates the surviving candidates. The original 1982 sieve used banks of ROM and counters to reject candidates. The same architecture, a fast filter plus a slow verification, has survived for decades.
Source: https://github.com/kbsriram/a-tiny-sieve
The post A Digital Electronic Sieve Built with Thirty ATtiny412 Chips appeared first on Open Electronics.
XGO Duck: the open source robot duck that walks with neural policies
XGO Duck is an open source, 3D-printable robot duck that Luwu Dynamics built starting from Pollen Robotics’ Microduck. From the original project it keeps the body, the layout of the 15 servos and the joint order, but replaces all of the electronics. In place of the Pollen Robotics board there is an Arduino UNO Q, which runs neural policies for walking, getting up from the ground and picking. So there is no need to wait for a commercial robot: anyone with a 3D printer can build one.
The heart of the system is the Arduino UNO Q itself, which hosts two computers on a single board. On one side there is a host with a Qualcomm processor running Linux, on the other an STM32U585 MCU running Zephyr. This division of tasks is the most interesting architectural choice in the project. The host handles the neural policies, the MCU handles real-time motor control. On top of that, the link between the two is a 2 Mbps Bridge, so the two worlds stay synchronised without Linux ever having to wait on the servo bus.
Two computers, two loops: 50 Hz for the policies and 100 Hz for the busThe host runs the ONNX policies at 50 Hz on a dedicated thread, with the web UI listening on port 9527. The MCU, on the other hand, runs a 100 Hz bus loop and does not wait for Linux. It publishes a 240-byte duck_state snapshot at 100 Hz; the host filters every snapshot on arrival and the 50 Hz thread reads the latest available one, skipping late cycles. That way the robot does not stall if the host is busy.
The servo bus always addresses all 15 servos in the order ID 10-14, 20-24, 30-34. The order in action 14-D of the policy is instead 10-14, 30-33, 20-24. The servo bus is on Serial1 at 1 Mbps, while the QMI8658 IMU is on Wire at 400 kHz, with I2C address 0x6A then 0x6B. Servo positions are saturated to the encoder range 0-4095, with a raw centre position of 2047.
- 15 FeeTech 1910 servos on a serial bus
- Arduino UNO Q with Qualcomm host and STM32U585 MCU
- QMI8658 IMU on the Wire bus at 400 kHz
- Bridge host-MCU link at 2 Mbps
- servo bus on Serial1 at 1 Mbps
The policies expect an observation [1, 61] and output an action [1, 14]. There are three: xgoduck_walk.onnx for walking, xgoduck_getup.onnx for getting up from the ground and xgoduck_pick.onnx for the pick, which lasts 4 s. A tilt above 55° for 0.15 s triggers the get-up model, then the action is forced to 0 for 1 s. When the tilt drops below 15° for 1 s, the robot goes back to walking.
The home pose has hip and ankle at ±24°, knee at 0°, hip roll at ±5°, neck and head pitch at 20°, mouth at 0°. The action_scale is 1. The walking commands are vx ±0.4, vy ±0.3 and ωz ±1.0, with a joystick dead zone of 0.1. The four head channels sit within ±1 radian. The mouth is driven from the web UI from 0° to 30°, and in the pick cycle it opens to 30° and closes when φ ≥ 0.4.
Action smoothing uses α = 0.45 on the slices [0:5], [5:10] and [10:14], yaw smoothing uses α = 0.5 and joint speed smoothing uses α = 0.4. The gravity complementary filter uses τ = 0.3 s, with accelerometer correction dropping when the norm deviates from 1 g by more than about 20%. Position control stops if commands are missing for 250 ms or if the IMU is missing for 100 ms; a host feedback older than 150 ms disarms it.
The Zephyr firmware, servo calibration and the web UI on port 9527The firmware is a CLI app built with Arduino Zephyr core 1.0.0, on top of RouterBridge 0.4.3, RPClite 0.3.1 and MsgPack 0.4.2. A patch to RouterBridge 0.4.3 raises the RPC thread stack from 500 to 4096 bytes, and the serial router is set to 2 Mbps. Calibration and servo setup use a 2 s heartbeat. The temporary gains for the centring movement are KP = 6 and KD = 20, with a temporary KP = 10 for the servo with ID 34. During calibration the gains become KP = 3 and KD = 0, and every servo is commanded to 2047.
The servo setup page starts with default values KP = 5 and KD = 20. Writing the ID unlocks register 0x37 and then writes 0x05; writing KP/KD unlocks 0x37 and stores both bytes at 0x15. The duck_command sent by the host is 80 bytes. Closing the page or leaving it in the background for more than 1 s disables position control, so the web UI is not just a convenience panel.
The Luwu Dynamics repository collects the project code: sketch, configurations, ONNX models and support scripts. Among the tools are tools/prepare-bridge.py, tools/router-2m.sh, tools/reuse-toolchain.py, tools/verify-elf.py and tools/measure.py, which measures for 60 seconds. There are also python/rl_core.py, python/requirements.txt, sketch/sketch.yaml, app.yaml, data/zero_pos.json and sketch/duck_config.h. Anyone who wants to rebuild it will find everything needed to get started there.
The host needs a Linux environment with ONNX Runtime and Python, while the MCU runs on Zephyr. The UNO Q loader error in case of a tail-call is ENOEXEC (−8), a detail familiar to anyone who compiles firmware. The default rate of Bridge.begin() in another app is 115200, so it has to be raised to 2 Mbps to run the bus as needed. If you want to start with the right hardware, an Arduino UNO Q with a complete accessory kit covers the host and MCU side on a single board.
Source: https://github.com/LuwuDynamics/xgoduck_runtime_arduino
Related productsThe post XGO Duck: the open source robot duck that walks with neural policies appeared first on Open Electronics.
Cool Piece of History: Glass Capacitors
| Ever heard of glass dielectric capacitors? These were manufactured by Corning Glass Works (and later under AVX), and they are the most ideal capacitors in the 20th century. They have Extremely low leakage current (>100gigaohms), near zero dielectric absorption (~0.02%), excellent temperature stability (30ppm/C), no microphonics, and are very rare due to their complexity and price. These capacitors are largely superseded by modern ceramic capacitors such as NP0 or C0G. [link] [comments] |
This is how they made scrolling displays back then
I made a gimmick auto router
| I always liked the look of one hand made PCB designs but I have my own family and no time for that. So I tried to make an auto router that imitates it. Not trying to create anything productive just a fancy look for my hobby projects [link] [comments] |
This is how we made Arbitrary Waveform Generators back then.
| submitted by /u/1Davide [link] [comments] |
Hey everyone! I wanted to share a project I built for students like me who were tired of just memorizing formulas. It’s an educational software that emulates Experiment with transistor circuits - BJT / MOSFET as switches and amplifiers, biasing, etc. •...
| submitted by /u/IslandImaginary6776 [link] [comments] |
Weekly discussion, complaint, and rant thread
Open to anything, including discussions, complaints, and rants.
Sub rules do not apply, so don't bother reporting incivility, off-topic, or spam.
Reddit-wide rules do apply.
To see the newest posts, sort the comments by "new" (instead of "best" or "top").
[link] [comments]
TI brings Zephyr RTOS to its entire embedded range: MCUs, MPUs and wireless
Texas Instruments (TI) has announced the extension of Zephyr RTOS support across its entire range of embedded solutions, giving developers a unified, production-ready platform that spans MCUs, MPUs and wireless connectivity devices.
TI expands Zephyr RTOS support across its embedded rangeA unified, production-ready platform covering TI’s MCUs, MPUs and wireless connectivity solutions, able to remove migration obstacles and cut time to market for Zephyr developers around the world.
The Zephyr project now supports TI’s broad range of embedded products, which includes MCUs, MPUs and wireless connectivity devices.
What’s newTexas Instruments (TI) today announced support for its broad range of embedded solutions by the Zephyr Project, the open source real-time operating system (RTOS). This integration makes a unified, production-ready development experience possible across TI’s entire range of microcontrollers (MCUs), microprocessors (MPUs) and wireless connectivity devices, designed specifically for embedded developers looking for ways to shorten development times and for a system compliant with the Cyber Resilience Act (CRA).
Fragmented software ecosystems often force developers to rewrite code when they change semiconductor vendors: TI’s Zephyr-based platform, by contrast, offers a single, consistent development experience. Developers can therefore migrate to TI without compromising their existing open source workflows while gaining access to a complete, high-performance hardware range.
Why it mattersThe collaboration between TI and the Zephyr Project lets developers at every level, from hobbyists to design engineers, build a wide range of systems on a single, simplified platform. Thanks to long-term support from the Linux Foundation, TI is able to periodically update its Zephyr-based software development kits (SDKs) to address security vulnerabilities and to let developers create reliable, compliant products for years and years.
“Thanks to TI and Zephyr, developers have everything they need to design, scalably and easily, with our entire range of MCUs, MPUs and wireless connectivity solutions,” said Marian Kost, vice president and general manager of Wireless Connectivity at TI. “They can therefore keep using the open source workflow they already have and use the TI chips they already know, as well as take advantage of the broad hardware choice, software support and supply reliability needed to carry projects from prototype to production.”
“A vendor-independent RTOS only works if its realization is the fruit of collaboration between companies: Texas Instruments’ choice to make its broad range available on Zephyr is a clear example of that commitment,” said Kate Stewart, vice president for Dependable Embedded Systems at the Linux Foundation. “Developers can therefore build their projects with a choice of TI MCUs, MPUs and wireless devices using a common platform, based on third-party products and backed by a community that takes security and long-term maintenance seriously.”
Further detailsEmbedded developers increasingly rely on the Zephyr Project not only as a real-time operating system (RTOS), but also for its lively and neutral open source community, in which real development experience defines the roadmaps and drives adoption.
By actively contributing code and reference designs to the Zephyr community, TI lets developers keep their existing codebase, access a broader range of high-performance hardware and reduce long-term security risks. For developers, all of this translates into the following benefits:
- No workflow disruption: existing Zephyr codebases and toolchains are kept intact during migration to TI chips.
- Upstream code review first: the Zephyr community reviews TI code before every SDK release, giving developers a stable codebase that is not modified during the product ramp-up phase.
- Public repository and continuous integration/continuous deployment (CI/CD): continuous integration and deployment on public GitHub pages provides early, immediate access to resources and new features well before they are included in the final SDK.
- Greater hardware choice: design a complete system with TI’s rich embedded and analog solutions without leaving the Zephyr RTOS environment.
- Lower long-term risk: complete resources, including validated releases, migration guides and backward-compatibility notes, help reduce maintenance burdens for a product based on TI chips with lifecycles of more than 10 years.
- Regulatory compliance: CRA compliance removes a significant obstacle for developers targeting European Union (EU) markets.
Further information is available at TI.com.
FAQWhich TI devices are included in the Zephyr ecosystem?
The ecosystem covers TI’s embedded product range, including MCUs ranging from ultra-low-power M0 devices up to high-performance M33 cores, as well as MPUs and wireless connectivity devices. The Zephyr platform is designed to adapt to different use cases, from simple sensing to complex connected embedded systems.
How does this expansion help developers who already use Zephyr?
Developers who already use Zephyr on other platforms can migrate to TI chips without having to recreate their codebase or abandon their current workflow. TI’s integration is designed to minimize migration friction while offering access to a broader hardware range.
What does EU CRA compliance mean from a developer’s point of view?
The CRA is an EU regulation that sets out cybersecurity requirements for products with digital elements. TI’s Zephyr platform is CRA compliant, so developers targeting EU markets can use TI’s platform knowing they meet the applicable regulatory requirements, thereby reducing their compliance burden.
Where can developers access the platform and how can they learn more?
Complete documentation, SDKs and reference designs are available at TI.com.
The post TI brings Zephyr RTOS to its entire embedded range: MCUs, MPUs and wireless appeared first on Open Electronics.
Suutari20: a modular macro keyboard built on 3.5 mm audio jacks
Suutari20 is a modular macro keyboard that uses 3.5 mm audio jacks instead of dedicated connectors. The project comes from Squalius and relies on a Raspberry Pi Pico with an RP2040 microcontroller. Each jack can handle up to three keys, so the hub ends up supporting 18 different keys. Analog devices fit in there too, for example a volume knob or a jog controller.
The underlying idea combines simplicity and low cost. 3.5 mm jacks are found everywhere and cost little, while a proprietary connector would force you to hunt down a specific supplier. On top of that, every key has its own microcontroller built into the module, so the hub doesn’t have to drive the button matrix directly. As a result the wiring stays simple and each module can be swapped on its own.
How the hub works with the socketsThe link between hub and modules goes through TRRS sockets and 3.5 mm jacks, from TS to TRRS types. The jack carries the key signals, so a single audio cable is enough for three buttons. The firmware is based on QMK with Vial, so keymaps can be reconfigured in software. Anyone who wants to rebuild the project will find the code in the Squalius repository.
Power and logic need an RP2040 microcontroller, mounted on a Raspberry Pi Pico. The board handles the module inputs and talks to the computer over USB.
What you need for the build and the bill of materials- Raspberry Pi Pico as the hub with an RP2040 microcontroller
- 8 PJ-320A audio sockets for the 3.5 mm jacks
- 4 M2xL3xOD3 heatset inserts
- 4 M2 bolts
- 3.5 mm jacks from TS to TRRS types for the modules
The numbers in the bill of materials are modest: 8 PJ-320A audio sockets, 4 M2xL3xOD3 heatset inserts and 4 M2 bolts. The heatset inserts are sunk into the 3D-printed body and give the screws a sturdy thread. Then the M2 bolts close everything up without stripping the plastic after a few teardowns. Finally the 3.5 mm jacks complete the modules and make them interchangeable.
The analog side is what sets the project apart from a plain macropad. A jack can carry the signal of a volume knob or a jog controller, so the module isn’t limited to switches. However, a bit of care is needed in the wiring, because the analog signal shares the same connector with the key contacts.
The build stays within reach of anyone who has already soldered a few boards. You print the module and hub bodies, sink the heatset inserts, solder the PJ-320A sockets and connect the Pico. Then you load the QMK firmware with Vial and assign the keys. Thanks to the standard jacks, replacing a broken module costs a few cents and doesn’t require redoing everything.
Source: https://github.com/Squalius-cephalus/suutari20
The post Suutari20: a modular macro keyboard built on 3.5 mm audio jacks appeared first on Open Electronics.
Planning to etch first pcb.
| So I decided i wanted to try to etch my very first pcb, and the only thing that comes to mind is my upcomming capacitance multiplier with current limiter for my linear cc/cv power supply that i'm planning to build and this was the result. I'm thinking i'll save as mutch copper as possible to save on the solution so that I can use it more times and realised that i don't really need mutch of either rails or free space for this, I know it's not many components but somehow i thought it would look like, more, you know? It's a dual pole RC with 100 ohms in series with 1000uf in parallel 100 ohms in series 1000uf in parallel + 12k ohms in parallel, with a bd139 driver and two tip35c power transistors with 0.22 ohms emitter resistors, 0.12 ohm shunt and bc547 Current Limiter [link] [comments] |
Rust no_std on the XIAO ESP32-C6: nine Grove examples with esp-hal
Nine no_std Rust examples that connect Grove sensors, displays and actuators to the Seeed Studio XIAO ESP32-C6. That is the heart of the work by Mariusz Jurgielewicz, who chose esp-hal 1.0.0 as the base for every sketch. Each example drives a single module from the Grove Beginner Kit for Arduino, from blinking a LED to reading an accelerometer, pressure and humidity. So the learning path stays linear: you start with GPIO and end up at the I2C bus.
The board exposes 14 castellated pins, brought out by the Grove Base for XIAO. The shield turns them into labelled Grove connectors (analog, digital, I2C), with a keyed housing that prevents the cable from being plugged in the wrong way. On top of that, USB-JTAG is integrated into the chip: cargo run -release flashes and opens the monitor on the same port, with no external probe. If something goes wrong, esp-backtrace prints a real stack trace on a panic.
The firmware: esp-hal, embedded-hal and drivers behind the traitsAll the examples compile for the riscv32imac-unknown-none-elf target and rely on esp-hal 1.0.0, esp-backtrace and esp-println for serial logging without defmt. The peripheral drivers sit behind the embedded-hal traits, so the pattern of every example is always the same: take a GPIO or I2C peripheral from the HAL, hand it to the driver, loop. Mariusz Jurgielewicz’s project page on Hackster.io collects the nine examples with the drivers used, from ssd1306 to bme280, from tm1637-embedded-hal to esp-hal-smartled.
- Rust, no_std, riscv32imac-unknown-none-elf target
- esp-hal 1.0.0, esp-backtrace, esp-println
- embedded-graphics and ssd1306 for the OLED
- bme280 for pressure and humidity
- tm1637-embedded-hal for the 4-digit display
- esp-hal-smartled for the RGB stick
The OLED, BME280 and AHT20 share the same I2C bus on D4/D5 without conflicts. The reason is simple: the Grove connector fixes the wiring and each driver owns its own I2C address. So no multiplexer is needed, nor a second pair of pins.
5 V supply for the TM1637 and the WS2813 RGB stickTwo modules need extra wiring because the shield only provides 3.3 V. The TM1637 display and the WS2813 RGB stick must be powered from the 5V and GND pins of the XIAO, with the signal lines (CLK/DIO on D2/D1, DIN on a signal pin) going to the shield. The stick holds 15 addressable WS2813 Mini LEDs, so the firmware has to handle a chain of 15 elements. The 3.3 V modules, by contrast, plug straight into the Grove connector, with no soldering.
The numbers in the examples help you grasp the rhythm of the code. The LED in the grove_led example blinks with 250 ms on and 1000 ms off. The Grove potentiometer adjusts the LED blink period from 50 ms to 1000 ms. So the analog read cycle and the digital output cycle live together in the same loop, with no dedicated timers. Then come the three-axis LIS3DHTR accelerometer and the pressure sensor BME280, both read over I2C.
To rebuild the project you need the XIAO ESP32-C6, the Grove Shield for Seeeduino XIAO and the Grove Beginner Kit for Arduino. It also helps to keep a Grove cable within reach for each module, so you can move one example at a time without unplugging everything. The Rust toolchain is installed with rustup, then the riscv32imac-unknown-none-elf target is added. Finally you run cargo run -release and watch the serial monitor.
Source: https://www.hackster.io/melastmohican/grove-sensors-with-rust-on-esp32-c6-9f7d62
Related productsThe post Rust no_std on the XIAO ESP32-C6: nine Grove examples with esp-hal appeared first on Open Electronics.



