Jacob Beningo’s Post

What microservices and modular monoliths have in common with IoT applications, (lack) of memory isolation and concept of remote procedure calling? Quite a lot... No, it is not just the MQTT which connects them both. In recent posts on #cmrxrtos I've drawn a picture of embedded development platform, where parts of the applications are isolated from each other by mandatory memory isolation, device drivers are demoted to be yet another userspace applications and the only way they can talk to each other are remote procedure calls. This concept looks pretty similar to what modular monolith is supposed to do. Why do we even crave for modular monoliths? Compared to good old monolith which is portable like Rocky Mountains and everyone can do everything, modular monoliths offer lines at which there is possibility to split it into multiple pieces. Unlike microservices, the split is not really there until you need it. And unlike monoliths, you don't need to use explosives once you are in a need of it. One of architectural problems of embedded applications, as pointed out also by Rosmianto Aji Saputro is lack of layering and separation. Many, if not vast majority of embedded applications are rigid monoliths. Now, the environment with enforced memory isolation does not allow you to do so. It enforces you to use remote procedure calling for which you have to create interfaces. That's very modular monolith-alike. Why would you bother? Two main advantages are: 1) where safety is relevant, the holy grail of developers is to have the code formally verified. Yet, monoliths are usually too big for this to be even theoretically possible. State space is simply too large. Here the isolated components have much smaller state space allowing their formal verification. Interface limits ability of external actors to influence the internal component state. 2) interfaces hide what is beneath them. You can swap the implementation without users realizing it happened. This gives you as loose coupling as technically permissible. Good news for portability. It is hard to write non-portable modular software unless you do extremely poor job designing your interfaces. What about you? Do you see potential of modular monolith approach in embedded systems? Do you feel that contemporary architecture of embedded systems has drawbacks? Do you find this to be the solution to these problems? Give me your thoughts in comments. Prove me wrong! #embeddedsoftware #rtos #softwareengineering #softwarearchitecture

RISC-V, a pioneering open-source and adaptable instruction set architecture (ISA), is revolutionizing the microprocessor industry. Its unparalleled adaptability allows developers to tailor-make processors that perfectly fit their requirements, establishing it as the preferred option for a wide variety of devices, from low-power IoT devices to high-performance servers. The RISC-V architecture, pronounced as "risk-five," is an open-source instruction set architecture (ISA) that has captured significant interest for its flexibility, modularity, and the ability to be extended. This contrasts with proprietary architectures by offering access to its foundational designs, allowing for extensive customization. As an open-source ISA, RISC-V presents numerous customization opportunities, empowering developers to engineer processors that are meticulously tailored for specific applications and scenarios. Its versatility has facilitated its adoption across multiple sectors, including embedded systems, IoT devices, high-performance computing, and artificial intelligence. Key advantages of RISC-V include the creation of cost-effective custom processors, the enablement of innovative applications, and the provision of strong security features. Regarded as the future of processing technology, RISC-V places unparalleled customization at your fingertips. The RISC-V instruction set is a collection of instructions that define the operations a RISC-V processor can perform. These instructions are designed to be simple, efficient, and easily extensible, allowing for a high degree of customization and optimization. The instruction set is organized into a base integer instruction set and a set of optional extensions, which provide specialized functionality for specific applications or domains. RISC-V instructions are encoded using a fixed-length 32-bit format, which simplifies decoding and execution. The instruction formats are categorized into six types: R, I, S, B, U, and J. Each format serves a specific purpose and has a unique encoding structure.

𝐓𝐲𝐩𝐞𝐬 𝐨𝐟 𝐄𝐦𝐛𝐞𝐝𝐝𝐞𝐝 𝐒𝐲𝐬𝐭𝐞𝐦𝐬, 𝐚𝐧𝐝 𝐇𝐨𝐰 𝐃𝐨 𝐓𝐡𝐞𝐲 𝐖𝐨𝐫𝐤? An #embeddedsystem refers to a specialized #computersystem designed to perform specific #functions within a #largermechanical or #electricalsystem. These systems are #embedded into devices like #consumerelectronics, #automotivesystems, #medicaldevices, #industrialmachines, and more. They typically have dedicated #hardware and #software tailored to their specific tasks, often operating in real-time with constraints such as power, size, and processing capabilities. Embedded systems play a crucial role in #automation, control systems, #IoTdevices, and various other #applications requiring reliable, efficient, and task-specific computing capabilities. 𝑹𝑬𝑨𝑫 𝑯𝑬𝑹𝑬- https://lnkd.in/eawduPnu #embeddedengineer #iot #software #embedddedsoftware #softwaredevelopment

🌟 𝐄𝐦𝐛𝐞𝐝𝐝𝐞𝐝 𝐜𝐨𝐦𝐩𝐮𝐭𝐞𝐫𝐬: 𝐡𝐢𝐝𝐝𝐞𝐧 𝐩𝐨𝐰𝐞𝐫 𝐚𝐭 𝐭𝐡𝐞 𝐬𝐞𝐫𝐯𝐢𝐜𝐞 𝐨𝐟 𝐛𝐮𝐬𝐢𝐧𝐞𝐬𝐬 🌟 📝 In our latest blogpost we talk about how #embedded computers are revolutionizing #industries with their compact design and robust performance, enhancing efficiency and precision in business processes 📊 Discover how these innovative solutions can transform your business: 🔹 HW/SW #integration for faster time to market 🔹 Rugged #design for challenging #environments 🔹 #Scalability and #modularity for specific needs 🔹 Automation and real-time #monitoring for increased productivity 🚀 Ready to harness this technology? Read the full blog post on SECO and learn more! https://lnkd.in/dV3Eecf4 #SECOTrends #EmbeddedComputers #IndustrialAutomation #IoT #BusinessEfficiency

Empowering tomorrow and making innovations in the IT industry. full article below:- https://lnkd.in/dWbAAFqr #software #power #technology #innovation #IT #multicoresoftware #TreadBinaryTechnologies #IOT #machinelearning #technologically #Futureishere

My book 'IoT Edge Computing with MicroK8s' and other 500 best titles are available for $10 each.Time to grab your ebook and advance your career. #packt #kubernetes #MicroK8s #iot https://lnkd.in/dVJxkGT5

𝐓𝐲𝐩𝐞𝐬 𝐨𝐟 𝐄𝐦𝐛𝐞𝐝𝐝𝐞𝐝 𝐒𝐲𝐬𝐭𝐞𝐦𝐬, 𝐚𝐧𝐝 𝐇𝐨𝐰 𝐃𝐨 𝐓𝐡𝐞𝐲 𝐖𝐨𝐫𝐤? An #embeddedsystem refers to a specialized #computersystem designed to perform specific #functions within a #largermechanical or #electricalsystem. These systems are #embedded into devices like #consumerelectronics, #automotivesystems, #medicaldevices, #industrialmachines, and more. They typically have dedicated #hardware and #software tailored to their specific tasks, often operating in real-time with constraints such as power, size, and processing capabilities. Embedded systems play a crucial role in #automation, control systems, #IoTdevices, and various other #applications requiring reliable, efficient, and task-specific computing capabilities. 𝑹𝑬𝑨𝑫 𝑯𝑬𝑹𝑬- https://lnkd.in/epHcVFtx #embeddedengineer #iot #software #embedddedsoftware #softwaredevelopment

As 5G technology rolls out globally, it is having a major impact on the software development landscape. Offering unprecedented speed, low latency, and increased connectivity, 5G enables applications and services that were previously impossible or impractical. At Polyrhythm, we leverage these advancements in our projects and observe an impact on how we develop software. The transition to 5G fundamentally alters software architecture, particularly in adopting microservices and modular design. Microservices architecture enhances scalability and flexibility, allowing developers to build and deploy components independently. This approach is well-suited to the high-speed, low-latency environment. The development of 5G applications requires various programming languages for frontend, backend, and embedded systems. Frontend Development: JavaScript, React, and Vue.js will continue to be popular for building high-performance, responsive interfaces that can leverage 5G’s capabilities. Backend Development: Node.js, Python, and Go are well-suited for handling increased data throughput and lower latency, making them ideal for backend services. Embedded Systems: C and C++ remain crucial for developing efficient and robust embedded systems in IoT devices that utilize this enhanced connectivity. Read more about 5G's impact on software engineering on our blog: https://lnkd.in/gJgMaRUq #5g #softwareengineering #gamedev #dod

a)Servant as the baseline system architecture for Flex-RV The Servant core is a minimal, open-source RISC-V CPU core typically used as a baseline or starting point for implementing more complex RISC-V systems, such as Flex-RV. Flex-RV often refers to a flexible implementation of the RISC-V architecture, which can be tailored for specific applications such as IoT devices or embedded systems. Servant as the baseline system architecture means that the Servant core provides the foundational RISC-V compliant architecture, upon which additional features or optimizations (such as custom extensions for flexibility) are built. The Servant core's simplicity makes it ideal for resource-constrained environments while supporting flexibility in the design. Key aspects include: 1. Minimalistic Design: Servant is designed to be as small and efficient as possible, making it an excellent choice for environments with limited resources (e.g., IoT devices). 2. RISC-V Compliance: It follows the RISC-V specification, allowing for compatibility with a wide range of RISC-V software and tools. 3. Customizability: By using Servant as the baseline, Flex-RV systems can introduce custom hardware features while retaining the core RISC-V architecture, allowing flexibility in handling different workloads or optimizations. By leveraging Servant's lightweight nature, Flex-RV architectures can scale from simple applications to more complex, custom systems. b) Modified Servant and additional blocks added to Servant to create Flex-RV. GPRs, general-purpose registers; CSRs, control and status registers; CLK, clock; RST, reset; Dbus, data bus; Ibus, instruction bus; Mux, multiplexer. Sony Semicon India Foxconn Samsung Semiconductor HP

NXP Semiconductors has announced the NXP Platform Accelerator, developed in collaboration with MicroEJ. The NXP Platform Accelerator leverages MICROEJ VEE software containers with standard APIs to bring a smartphone-like software design process experience to the industrial and IoT edge. The use of MICROEJ VEE enables software portability across NXP’s broad portfolio of RTOS-based MCUs and Linux-based Applications Processors, enabling manufacturers to significantly accelerate new product development and reduce costs. Furthermore, the NXP Platform Accelerator provides dedicated APIs to create easy access to advanced functionalities integrated in NXP’s processor portfolio, such as power management and 3D/2D graphics. Smart devices across industrial and IoT markets are challenging to develop and deploy. Many are designed for a single purpose, with fixed functionality and limited computing capability that may be insufficient to support the evolving needs of an increasingly automated environment. Scaling product capability requires redeveloping and integrating low-level software, RTOS or higher-level OS, and middleware, which can create major development challenges and significantly slow product development. Read more: https://lnkd.in/gJuN7nKW #IndiaTechnologyNews #NXP #MicroEJ #EmbeddedDevelopment #SoftwareContainers #IoTDevelopment #EmbeddedSystems #TechCollaboration #IoTInnovation #EmbeddedTech