DevHeads
@DevHeadsComm
Followers
1K
Following
114
Media
243
Statuses
282
DevHeads is a collaborative community of professional developers and engineers from across technology
Joined November 2023
In multicore embedded systems, efficient communication between cores is key to achieving performance and reliability. In the final part of this #debugging series, Bea explores how to overcome #inter_core messaging challenges in #Zephyr #RTOS using #SystemView and #Ozone. From
0
0
0
Check out this new DevHeads article by Ibtihal Ben Ali ("Bea"), diving into #MulticoreDebugging in #ZephyrRTOS โ this time tackling #CacheCoherency and how shared cache levels (L1, L2, L3) can impact system reliability. ๐ Read it here: https://t.co/A1UjkVpFcr Bea walks through
0
0
1
One of our community members recently shared a tricky issue during the SD protocol initialization stage on an #STM32F4 Discovery board using a generic SD memory shield. While sending the ACMD51 command to read the Status Card Register on the DAT0 line, the command failed with
0
0
0
Watch as Umesh demonstrates a live setup of a #TCP clientโserver using the #STM32 #microcontroller and the #W5500 #Ethernet module. Youโll see the TCP connection come to life โ from physical hardware to real-time data exchange! ๐ Watch the complete video here:
0
0
0
Join us for a hands-on live session where weโll dive deep into implementing Modbus TCP Server with STM32 Cortex-M4 MCU. ๐ What youโll learn: * Understanding Modbus TCP Data Frame * Exploring Modbus Networking Layers * How to configure Simply Modbus TCP Client * Live Demo:
0
0
0
๐๐ผ ๐ฌ๐ผ๐ ๐๐ป๐ผ๐ ๐ช๐ต๐ฒ๐ฟ๐ฒ ๐ ๐ผ๐ฑ๐ฏ๐๐ ๐๐ถ๐๐ ๐ถ๐ป ๐๐ต๐ฒ ๐ก๐ฒ๐๐๐ผ๐ฟ๐ธ ๐ฆ๐๐ฎ๐ฐ๐ธ? If youโve ever worked with Modbus TCP/IP, youโve probably seen it described as ๐ ๐ผ๐ฑ๐ฏ๐๐ ๐ผ๐๐ฒ๐ฟ ๐๐๐ต๐ฒ๐ฟ๐ป๐ฒ๐. But where exactly does it sit in the networking stack? ๐ ๐ผ๐ฑ๐ฏ๐๐
0
0
0
Join IoT expert Umesh Lokhande for a hands-on session: โEthernet Controller: Implement TCP ClientโServer using W5500 & STM32 MCU.โ Youโll learn * Choosing & using the driver library * Network config basics (IP, gateway, subnet) * SPI hookup: interfacing W5500 โ STM32 *
0
0
0
๐ก๐ผ ๐ช๐ถ๐ฟ๐ฒ๐, ๐ก๐ผ ๐๐ฎ๐๐๐น๐ฒ: ๐จ๐ฆ๐ ๐๐๐จ ๐๐ผ๐ผ๐๐น๐ผ๐ฎ๐ฑ๐ฒ๐ฟ ๐ณ๐ผ๐ฟ ๐ ๐๐จ๐ Tired of relying on external programmers or debug tools just to flash the MCU With USB DFU (Device Firmware Update) support, you can program your Microcontroller just using USB. This means
0
0
1
Weโre excited to announce two upcoming live sessions packed with practical demos and step-by-step guidance: ๐
3 October โ Ethernet Controller: Implement TCP Client-Server using W5500 & STM32 MCU ๐
17 October โ Implement MODBUS TCP Server with STM32 Cortex-M4 MCU ๐ Register
0
0
1
๐ช๐ต๐ ๐ฏ๐๐ถ๐น๐ฑ ๐ฎ ๐ฐ๐๐๐๐ผ๐บ ๐๐ผ๐ผ๐๐น๐ผ๐ฎ๐ฑ๐ฒ๐ฟ ๐ณ๐ผ๐ฟ ๐๐ผ๐๐ฟ ๐ ๐๐จ? Most microcontrollers come with a vendor-supplied bootloader (such as STM32), but these can be restrictive at times. Thatโs where a custom bootloader becomes very useful. With Flash memory
0
0
1
Wilson, a valued community member, put together and tested four different veroboard versions prior to the arrival of his custom PCB. Each one functioned partially before breaking, but every failure provided him with the knowledge needed to improve the design. By the fourth
0
0
0
Bare-Metal Embedded Series ยท Part 3 SysTick Timer on ARM Cortex-M #SysTick is a 24-bit down counter inside the core. Itโs my go-to for periodic interrupts, delays, and tiny schedulers. ๐ช๐ต๐ฎ๐ ๐ถ๐ ๐ถ๐: * 24-bit counter in the CPU * Periodic interrupts without extra
0
0
1
Normally, when multiple clients subscribe to the same topic, each one gets a copy of every message. But what if you want to balance the load between them? Thatโs where ๐ฆ๐ต๐ฎ๐ฟ๐ฒ๐ฑ ๐ฆ๐๐ฏ๐๐ฐ๐ฟ๐ถ๐ฝ๐๐ถ๐ผ๐ป๐ come in. ๐ช๐ต๐ฎ๐ ๐๐ ๐ฎ ๐ฆ๐ต๐ฎ๐ฟ๐ฒ๐ฑ ๐ฆ๐๐ฏ๐๐ฐ๐ฟ๐ถ๐ฝ๐๐ถ๐ผ๐ป?
0
0
1
Following up on this [#BLDC controller challenge ๐ https://t.co/ppA5QjaRgnโve got major progress from our maker: โIโm now controlling the 3 bridges using center-aligned complementary PWM โ it brought noticeably more motor stability compared to edge-aligned PWM with GPIO
0
0
0
In #RTOS for #IoT, ๐๐ป๐๐ฒ๐ฟ๐ฟ๐๐ฝ๐ ๐ฆ๐ฒ๐ฟ๐๐ถ๐ฐ๐ฒ ๐ฅ๐ผ๐๐๐ถ๐ป๐ฒ๐ (#ISRs) are essential for responsivenessโbut theyโre also one of the most common sources of jitter and missed deadlines when misused. Here are the key rules every embedded engineer should follow: 1๏ธโฃ ๐๐ฒ๐ฒ๐ฝ
1
0
0
IoT devices run on extreme constraintsโtiny memory, low power, heterogeneous #protocols. Yet they must handle #real-time tasks reliably. Based on ongoing research in RTOS design, here are 3 key lessons: 1๏ธโฃ ๐ ๐ฒ๐บ๐ผ๐ฟ๐ ๐ถ๐ ๐ฝ๐ฟ๐ฒ๐ฐ๐ถ๐ผ๐๐ โ Avoid dynamic allocation; static is
0
0
0
Ever tried to toggle a #GPIO and nothing happened? You double-check your #codeโฆ still nothing. If you donโt know your MCUโs memory map, youโre coding blind. Thatโs where the ๐ ๐๐จ ๐บ๐ฒ๐บ๐ผ๐ฟ๐ ๐บ๐ฎ๐ฝ comes in. Itโs basically your chipโs ๐ฎ๐ฑ๐ฑ๐ฟ๐ฒ๐๐ ๐ฏ๐ผ๐ผ๐ธ - showing
0
0
0
๐จ ๐ช๐ต๐ฒ๐ป ๐ฌ๐ผ๐๐ฟ ๐๐ผ๐ฑ๐ฒ ๐๐ฟ๐ฒ๐ฒ๐๐ฒ๐ ๐ ๐ถ๐น๐ฒ๐ ๐๐๐ฎ๐โฆ ๐ช๐ต๐ผโ๐ ๐๐ผ๐ป๐ป๐ฎ ๐ฆ๐ฎ๐๐ฒ ๐๐? Youโve got a microcontroller running in a sensor 200 miles away. Itโs been fine for monthsโฆ then one day, it hangs. No logs. No response. No way to hit reset. Unless you had a
0
0
0