New approaches for embedded development

The idea for this posting started when I read New approaches to dominate in embedded development article. Then I found some ther related articles and here is the result: long article.

Embedded devices, or embedded systems, are specialized computer systems that constitute components of larger electromechanical systems with which they interface. The advent of low-cost wireless connectivity is altering many things in embedded development: With a connection to the Internet, an embedded device can gain access to essentially unlimited processing power and memory in cloud service – and at the same time you need to worry about communication issues like breaks connections, latency and security issues.

Those issues are espcecially in the center of the development of popular Internet of Things device and adding connectivity to existing embedded systems. All this means that the whole nature of the embedded development effort is going to change. A new generation of programmers are already making more and more embedded systems. Rather than living and breathing C/C++, the new generation prefers more high-level, abstract languages (like Java, Python, JavaScript etc.). Instead of trying to craft each design to optimize for cost, code size, and performance, the new generation wants to create application code that is separate from an underlying platform that handles all the routine details. Memory is cheap, so code size is only a minor issue in many applications.

Historically, a typical embedded system has been designed as a control-dominated system using only a state-oriented model, such as FSMs. However, the trend in embedded systems design in recent years has been towards highly distributed architectures with support for concurrency, data and control flow, and scalable distributed computations. For example computer networks, modern industrial control systems, electronics in modern car,Internet of Things system fall to this category. This implies that a different approach is necessary.

Companies are also marketing to embedded developers in new ways. Ultra-low cost development boards to woo makers, hobbyists, students, and entrepreneurs on a shoestring budget to a processor architecture for prototyping and experimentation have already become common.If you look under the hood of any connected embedded consumer or mobile device, in addition to the OS you will find a variety of middleware applications. As hardware becomes powerful and cheap enough that the inefficiencies of platform-based products become moot. Leaders with Embedded systems development lifecycle management solutions speak out on new approaches available today in developing advanced products and systems.

Traditional approaches

C/C++

Tradionally embedded developers have been living and breathing C/C++. For a variety of reasons, the vast majority of embedded toolchains are designed to support C as the primary language. If you want to write embedded software for more than just a few hobbyist platforms, your going to need to learn C. Very many embedded systems operating systems, including Linux Kernel, are written using C language. C can be translated very easily and literally to assembly, which allows programmers to do low level things without the restrictions of assembly. When you need to optimize for cost, code size, and performance the typical choice of language is C. Still C is today used for maximum efficiency instead of C++.

C++ is very much alike C, with more features, and lots of good stuff, while not having many drawbacks, except fror it complexity. The had been for years suspicion C++ is somehow unsuitable for use in small embedded systems. At some time many 8- and 16-bit processors were lacking a C++ compiler, that may be a concern, but there are now 32-bit microcontrollers available for under a dollar supported by mature C++ compilers.Today C++ is used a lot more in embedded systems. There are many factors that may contribute to this, including more powerful processors, more challenging applications, and more familiarity with object-oriented languages.

And if you use suitable C++ subset for coding, you can make applications that work even on quite tiny processors, let the Arduino system be an example of that: You’re writing in C/C++, using a library of functions with a fairly consistent API. There is no “Arduino language” and your “.ino” files are three lines away from being standard C++.

Today C++ has not displaced C. Both of the languages are widely used, sometimes even within one system – for example in embedded Linux system that runs C++ application. When you write a C or C++ programs for modern Embedded Linux you typically use GCC compiler toolchain to do compilation and make file to manage compilation process.

Most organization put considerable focus on software quality, but software security is different. When the security is very much talked about topic todays embedded systems, the security of the programs written using C/C++ becomes sometimes a debated subject. Embedded development presents the challenge of coding in a language that’s inherently insecure; and quality assurance does little to ensure security. The truth is that majority of today’s Internet connected systems have their networking fuctionality written using C even of the actual application layer is written using some other methods.

Java

Java is a general-purpose computer programming language that is concurrent, class-based and object-oriented.The language derives much of its syntax from C and C++, but it has fewer low-level facilities than either of them. Java is intended to let application developers “write once, run anywhere” (WORA), meaning that compiled Java code can run on all platforms that support Java without the need for recompilation.Java applications are typically compiled to bytecode that can run on any Java virtual machine (JVM) regardless of computer architecture. Java is one of the most popular programming languages in use, particularly for client-server web applications. In addition to those it is widely used in mobile phones (Java apps in feature phones,) and some embedded applications. Some common examples include SIM cards, VOIP phones, Blu-ray Disc players, televisions, utility meters, healthcare gateways, industrial controls, and countless other devices.

Some experts point out that Java is still a viable option for IoT programming. Think of the industrial Internet as the merger of embedded software development and the enterprise. In that area, Java has a number of key advantages: first is skills – there are lots of Java developers out there, and that is an important factor when selecting technology. Second is maturity and stability – when you have devices which are going to be remotely managed and provisioned for a decade, Java’s stability and care about backwards compatibility become very important. Third is the scale of the Java ecosystem – thousands of companies already base their business on Java, ranging from Gemalto using JavaCard on their SIM cards to the largest of the enterprise software vendors.

Although in the past some differences existed between embedded Java and traditional PC based Java solutions, the only difference now is that embedded Java code in these embedded systems is mainly contained in constrained memory, such as flash memory. A complete convergence has taken place since 2010, and now Java software components running on large systems can run directly with no recompilation at all on design-to-cost mass-production devices (consumers, industrial, white goods, healthcare, metering, smart markets in general,…) Java for embedded devices (Java Embedded) is generally integrated by the device manufacturers. It is NOT available for download or installation by consumers. Originally Java was tightly controlled by Sun (now Oracle), but in 2007 Sun relicensed most of its Java technologies under the GNU General Public License. Others have also developed alternative implementations of these Sun technologies, such as the GNU Compiler for Java (bytecode compiler), GNU Classpath (standard libraries), and IcedTea-Web (browser plugin for applets).

My feelings with Java is that if your embedded systems platform supports Java and you know hot to code Java, then it could be a good tool. If your platform does not have ready Java support, adding it could be quite a bit of work.

 

Increasing trends

Databases

Embedded databases are coming more and more to the embedded devices. If you look under the hood of any connected embedded consumer or mobile device, in addition to the OS you will find a variety of middleware applications. One of the most important and most ubiquitous of these is the embedded database. An embedded database system is a database management system (DBMS) which is tightly integrated with an application software that requires access to stored data, such that the database system is “hidden” from the application’s end-user and requires little or no ongoing maintenance.

There are many possible databases. First choice is what kind of database you need. The main choices are SQL databases and simpler key-storage databases (also called NoSQL).

SQLite is the Database chosen by virtually all mobile operating systems. For example Android and iOS ship with SQLite. It is also built into for example Firefox web browser. It is also often used with PHP. So SQLite is probably a pretty safe bet if you need relational database for an embedded system that needs to support SQL commands and does not need to store huge amounts of data (no need to modify database with millions of lines of data).

If you do not need relational database and you need very high performance, you need probably to look somewhere else.Berkeley DB (BDB) is a software library intended to provide a high-performance embedded database for key/value data. Berkeley DB is written in Cwith API bindings for many languages. BDB stores arbitrary key/data pairs as byte arrays. There also many other key/value database systems.

RTA (Run Time Access) gives easy runtime access to your program’s internal structures, arrays, and linked-lists as tables in a database. When using RTA, your UI programs think they are talking to a PostgreSQL database (PostgreSQL bindings for C and PHP work, as does command line tool psql), but instead of normal database file you are actually accessing internals of your software.

Software quality

Building quality into embedded software doesn’t happen by accident. Quality must be built-in from the beginning. Software startup checklist gives quality a head start article is a checklist for embedded software developers to make sure they kick-off their embedded software implementation phase the right way, with quality in mind

Safety

Traditional methods for achieving safety properties mostly originate from hardware-dominated systems. Nowdays more and more functionality is built using software – including safety critical functions. Software-intensive embedded systems require new approaches for safety. Embedded Software Can Kill But Are We Designing Safely?

IEC, FDA, FAA, NHTSA, SAE, IEEE, MISRA, and other professional agencies and societies work to create safety standards for engineering design. But are we following them? A survey of embedded design practices leads to some disturbing inferences about safety.Barr Group’s recent annual Embedded Systems Safety & Security Survey indicate that we all need to be concerned: Only 67 percent are designing to relevant safety standards, while 22 percent stated that they are not—and 11 percent did not even know if they were designing to a standard or not.

If you were the user of a safety-critical embedded device and learned that the designers had not followed best practices and safety standards in the design of the device, how worried would you be? I know I would be anxious, and quite frankly. This is quite disturbing.

Security

The advent of low-cost wireless connectivity is altering many things in embedded development – it has added to your list of worries need to worry about communication issues like breaks connections, latency and security issues. Understanding security is one thing; applying that understanding in a complete and consistent fashion to meet security goals is quite another. Embedded development presents the challenge of coding in a language that’s inherently insecure; and quality assurance does little to ensure security.

Developing Secure Embedded Software white paper  explains why some commonly used approaches to security typically fail:

MISCONCEPTION 1: SECURITY BY OBSCURITY IS A VALID STRATEGY
MISCONCEPTION 2: SECURITY FEATURES EQUAL SECURE SOFTWARE
MISCONCEPTION 3: RELIABILITY AND SAFETY EQUAL SECURITY
MISCONCEPTION 4: DEFENSIVE PROGRAMMING GUARANTEES SECURITY

Many organizations are only now becoming aware of the need to incorporate security into their software development lifecycle.

Some techniques for building security to embedded systems:

Use secure communications protocols and use VPN to secure communications
The use of Public Key Infrastructure (PKI) for boot-time and code authentication
Establishing a “chain of trust”
Process separation to partition critical code and memory spaces
Leveraging safety-certified code
Hardware enforced system partitioning with a trusted execution environment
Plan the system so that it can be easily and safely upgraded when needed

Flood of new languages

Rather than living and breathing C/C++, the new generation prefers more high-level, abstract languages (like Java, Python, JavaScript etc.). So there is a huge push to use interpreted and scripting also in embedded systems. Increased hardware performance on embedded devices combined with embedded Linux has made the use of many scripting languages good tools for implementing different parts of embedded applications (for example web user interface). Nowadays it is common to find embedded hardware devices, based on Raspberry Pi for instance, that are accessible via a network, run Linux and come with Apache and PHP installed on the device.  There are also many other relevant languages

One workable solution, especially for embedded Linux systems is that part of the activities organized by totetuettu is a C program instead of scripting languages ​​(Scripting). This enables editing operation simply script files by editing without the need to turn the whole system software again.  Scripting languages ​​are also tools that can be implemented, for example, a Web user interface more easily than with C / C ++ language. An empirical study found scripting languages (such as Python) more productive than conventional languages (such as C and Java) for a programming problem involving string manipulation and search in a dictionary.

Scripting languages ​​have been around for a couple of decades Linux and Unix server world standard tools. the proliferation of embedded Linux and resources to merge systems (memory, processor power) growth has made them a very viable tool for many embedded systems – for example, industrial systems, telecommunications equipment, IoT gateway, etc . Some of the command language is suitable for up well even in quite small embedded environments.
I have used with embedded systems successfully mm. Bash, AWK, PHP, Python and Lua scripting languages. It works really well and is really easy to make custom code quickly .It doesn’t require a complicated IDE; all you really need is a terminal – but if you want there are many IDEs that can be used.
High-level, dynamically typed languages, such as Python, Ruby and JavaScript. They’re easy—and even fun—to use. They lend themselves to code that easily can be reused and maintained.

There are some thing that needs to be considered when using scripting languages. Sometimes lack of static checking vs a regular compiler can cause problems to be thrown at run-time. But it is better off practicing “strong testing” than relying on strong typing. Other ownsides of these languages is that they tend to execute more slowly than static languages like C/C++, but for very many aplications they are more than adequate. Once you know your way around dynamic languages, as well the frameworks built in them, you get a sense of what runs quickly and what doesn’t.

Bash and other shell scipting

Shell commands are the native language of any Linux system. With the thousands of commands available for the command line user, how can you remember them all? The answer is, you don’t. The real power of the computer is its ability to do the work for you – the power of the shell script is the way to easily to automate things by writing scripts. Shell scripts are collections of Linux command line commands that are stored in a file. The shell can read this file and act on the commands as if they were typed at the keyboard.In addition to that shell also provides a variety of useful programming features that you are familar on other programming langauge (if, for, regex, etc..). Your scripts can be truly powerful. Creating a script extremely straight forward: It can be created by opening a separate editor such or you can do it through a terminal editor such as VI (or preferably some else more user friendly terminal editor). Many things on modern Linux systems rely on using scripts (for example starting and stopping different Linux services at right way).

One of the most useful tools when developing from within a Linux environment is the use of shell scripting. Scripting can help aid in setting up environment variables, performing repetitive and complex tasks and ensuring that errors are kept to a minimum. Since scripts are ran from within the terminal, any command or function that can be performed manually from a terminal can also be automated!

The most common type of shell script is a bash script. Bash is a commonly used scripting language for shell scripts. In BASH scripts (shell scripts written in BASH) users can use more than just BASH to write the script. There are commands that allow users to embed other scripting languages into a BASH script.

There are also other shells. For example many small embedded systems use BusyBox. BusyBox providesis software that provides several stripped-down Unix tools in a single executable file (more than 300 common command). It runs in a variety of POSIX environments such as Linux, Android and FreeeBSD. BusyBox become the de facto standard core user space toolset for embedded Linux devices and Linux distribution installers.

Shell scripting is a very powerful tool that I used a lot in Linux systems, both embedded systems and servers.

Lua

Lua is a lightweight  cross-platform multi-paradigm programming language designed primarily for embedded systems and clients. Lua was originally designed in 1993 as a language for extending software applications to meet the increasing demand for customization at the time. It provided the basic facilities of most procedural programming languages. Lua is intended to be embedded into other applications, and provides a C API for this purpose.

Lua has found many uses in many fields. For example in video game development, Lua is widely used as a scripting language by game programmers. Wireshark network packet analyzer allows protocol dissectors and post-dissector taps to be written in Lua – this is a good way to analyze your custom protocols.

There are also many embedded applications. LuCI, the default web interface for OpenWrt, is written primarily in Lua. NodeMCU is an open source hardware platform, which can run Lua directly on the ESP8266 Wi-Fi SoC. I have tested NodeMcu and found it very nice system.

PHP

PHP is a server-side HTML embedded scripting language. It provides web developers with a full suite of tools for building dynamic websites but can also be used as a general-purpose programming language. Nowadays it is common to find embedded hardware devices, based on Raspberry Pi for instance, that are accessible via a network, run Linux and come with Apache and PHP installed on the device. So on such enviroment is a good idea to take advantage of those built-in features for the applications they are good – for building web user interface. PHP is often embedded into HTML code, or it can be used in combination with various web template systems, web content management system and web frameworks. PHP code is usually processed by a PHP interpreter implemented as a module in the web server or as a Common Gateway Interface (CGI) executable.

Python

Python is a widely used high-level, general-purpose, interpreted, dynamic programming language. Its design philosophy emphasizes code readability. Python interpreters are available for installation on many operating systems, allowing Python code execution on a wide variety of systems. Many operating systems include Python as a standard component; the language ships for example with most Linux distributions.

Python is a multi-paradigm programming language: object-oriented programming and structured programming are fully supported, and there are a number of language features which support functional programming and aspect-oriented programming,  Many other paradigms are supported using extensions, including design by contract and logic programming.

Python is a remarkably powerful dynamic programming language that is used in a wide variety of application domains. Since 2003, Python has consistently ranked in the top ten most popular programming languages as measured by the TIOBE Programming Community Index. Large organizations that make use of Python include Google, Yahoo!, CERN, NASA. Python is used successfully in thousands of real world business applications around globally, including many large and mission-critical systems such as YouTube.com and Google.com.

Python was designed to be highly extensible. Libraries like NumPy, SciPy and Matplotlib allow the effective use of Python in scientific computing. Python is intended to be a highly readable language. Python can also be embedded in existing applications and hasbeen successfully embedded in a number of software products as a scripting language. Python can serve as a scripting language for web applications, e.g., via mod_wsgi for the Apache web server.

Python can be used in embedded, small or minimal hardware devices. Some modern embedded devices have enough memory and a fast enough CPU to run a typical Linux-based environment, for example, and running CPython on such devices is mostly a matter of compilation (or cross-compilation) and tuning. Various efforts have been made to make CPython more usable for embedded applications.

For more limited embedded devices, a re-engineered or adapted version of CPython, might be appropriateExamples of such implementations include the following: PyMite, Tiny Python, Viper. Sometimes the embedded environment is just too restrictive to support a Python virtual machine. In such cases, various Python tools can be employed for prototyping, with the eventual application or system code being generated and deployed on the device. Also MicroPython and tinypy have been ported Python to various small microcontrollers and architectures. Real world applications include Telit GSM/GPRS modules that allow writing the controlling application directly in a high-level open-sourced language: Python.

Python on embedded platforms? It is quick to develop apps, quick to debug – really easy to make custom code quickly. Sometimes lack of static checking vs a regular compiler can cause problems to be thrown at run-time. To avoid those try to have 100% test coverage. pychecker is a very useful too also which will catch quite a lot of common errors. The only downsides for embedded work is that sometimes python can be slow and sometimes it uses a lot of memory (relatively speaking). An empirical study found scripting languages (such as Python) more productive than conventional languages (such as C and Java) for a programming problem involving string manipulation and search in a dictionary. Memory consumption was often “better than Java and not much worse than C or C++”.

JavaScript and node.js

JavaScript is a very popular high-level language. Love it or hate it, JavaScript is a popular programming language for many, mainly because it’s so incredibly easy to learn. JavaScript’s reputation for providing users with beautiful, interactive websites isn’t where its usefulness ends. Nowadays, it’s also used to create mobile applications, cross-platform desktop software, and thanks to Node.js, it’s even capable of creating and running servers and databases!  There is huge community of developers. JavaScript is a high-level language.

Its event-driven architecture fits perfectly with how the world operates – we live in an event-driven world. This event-driven modality is also efficient when it comes to sensors.

Regardless of the obvious benefits, there is still, understandably, some debate as to whether JavaScript is really up to the task to replace traditional C/C++ software in Internet connected embedded systems.

It doesn’t require a complicated IDE; all you really need is a terminal.

JavaScript is a high-level language. While this usually means that it’s more human-readable and therefore more user-friendly, the downside is that this can also make it somewhat slower. Being slower definitely means that it may not be suitable for situations where timing and speed are critical.

JavaScript is already in embedded boards. You can run JavaScipt on Raspberry Pi and BeagleBone. There are also severa other popular JavaScript-enabled development boards to help get you started: The Espruino is a small microcontroller that runs JavaScript. The Tessel 2 is a development board that comes with integrated wi-fi, an ethernet port, two USB ports, and companion source library downloadable via the Node Package Manager. The Kinoma Create, dubbed the “JavaScript powered Internet of Things construction kit.”The best part is that, depending on the needs of your device, you can even compile your JavaScript code into C!

JavaScript for embedded systems is still in its infancy, but we suspect that some major advancements are on the horizon.We for example see a surprising amount of projects using Node.js.Node.js is an open-source, cross-platform runtime environment for developing server-side Web applications. Node.js has an event-driven architecture capable of asynchronous I/O that allows highly scalable servers without using threading, by using a simplified model of event-driven programming that uses callbacks to signal the completion of a task. The runtime environment interprets JavaScript using Google‘s V8 JavaScript engine.Node.js allows the creation of Web servers and networking tools using JavaScript and a collection of “modules” that handle various core functionality. Node.js’ package ecosystem, npm, is the largest ecosystem of open source libraries in the world. Modern desktop IDEs provide editing and debugging features specifically for Node.js applications

JXcore is a fork of Node.js targeting mobile devices and IoTs. JXcore is a framework for developing applications for mobile and embedded devices using JavaScript and leveraging the Node ecosystem (110,000 modules and counting)!

Why is it worth exploring node.js development in an embedded environment? JavaScript is a widely known language that was designed to deal with user interaction in a browser.The reasons to use Node.js for hardware are simple: it’s standardized, event driven, and has very high productivity: it’s dynamically typed, which makes it faster to write — perfectly suited for getting a hardware prototype out the door. For building a complete end-to-end IoT system, JavaScript is very portable programming system. Typically an IoT projects require “things” to communicate with other “things” or applications. The huge number of modules available in Node.js makes it easier to generate interfaces – For example, the HTTP module allows you to create easily an HTTP server that can easily map the GET method specific URLs to your software function calls. If your embedded platform has ready made Node.js support available, you should definately consider using it.

Future trends

According to New approaches to dominate in embedded development article there will be several camps of embedded development in the future:

One camp will be the traditional embedded developer, working as always to craft designs for specific applications that require the fine tuning. These are most likely to be high-performance, low-volume systems or else fixed-function, high-volume systems where cost is everything.

Another camp might be the embedded developer who is creating a platform on which other developers will build applications. These platforms might be general-purpose designs like the Arduino, or specialty designs such as a virtual PLC system.

This third camp is likely to become huge: Traditional embedded development cannot produce new designs in the quantities and at the rate needed to deliver the 50 billion IoT devices predicted by 2020.

Transition will take time. The enviroment is different than computer and mobile world. There are too many application areas with too widely varying requirements for a one-size-fits-all platform to arise.

But the shift will happen as hardware becomes powerful and cheap enough that the inefficiencies of platform-based products become moot.

 

Sources

Most important information sources:

New approaches to dominate in embedded development

A New Approach for Distributed Computing in Embedded Systems

New Approaches to Systems Engineering and Embedded Software Development

Lua (programming language)

Embracing Java for the Internet of Things

Node.js

Wikipedia Node.js

Writing Shell Scripts

Embedded Linux – Shell Scripting 101

Embedded Linux – Shell Scripting 102

Embedding Other Languages in BASH Scripts

PHP Integration with Embedded Hardware Device Sensors – PHP Classes blog

PHP

Python (programming language)

JavaScript: The Perfect Language for the Internet of Things (IoT)

Node.js for Embedded Systems

Embedded Python

MicroPython – Embedded Pytho

Anyone using Python for embedded projects?

Telit Programming Python

JavaScript: The Perfect Language for the Internet of Things (IoT)

MICROCONTROLLERS AND NODE.JS, NATURALLY

Node.js for Embedded Systems

Why node.js?

Node.JS Appliances on Embedded Linux Devices

The smartest way to program smart things: Node.js

Embedded Software Can Kill But Are We Designing Safely?

DEVELOPING SECURE EMBEDDED SOFTWARE

 

 

 

1,686 Comments

  1. Tomi Engdahl says:

    https://electronics.stackexchange.com/questions/482643/is-there-an-open-source-io-link-stack-available
    https://github.com/unref-ptr/lwIOLink

    This library reduces the complexity of the IO-Link communication to send (PDIn) and receive data (PDOut) over an IO-Link Master. The reason the library is called “light weight” is because it simplifies the communication and some of the “complex” features are missing. It must be noted that the aim of this library was not to follow the spec. but to simplify the communication by “dumbing down” the protocol. Hence this library can be used to understand how IO-Link works in a basic way, for commercial development please look for commercial alternatives as this library will not scale and is not optimized for production environments.

    Reply
  2. Tomi Engdahl says:

    Unlocking the Potential of Cheap Hardware
    This open source Python client retrieves real-time data from the COLMI R02 Smart Ring’s sensors so it can be incorporated into new projects.
    https://www.hackster.io/news/unlocking-the-potential-of-cheap-hardware-f02f20797794?fbclid=IwY2xjawF7Bb1leHRuA2FlbQIxMQABHRtRfqSf-8DLYPbA8UHvaett1eGhja926NH5UbY4PtM4D5BfJ9K-_XNBpA_aem_R-8IbjzBrj2dC3wBhj-zIw

    Inexpensive electronic devices, of the sort commonly found on sites like AliExpress, can be a lot of fun to play with. But the hacking potential of their hardware often outweighs the benefits of any intended use cases. Let’s be honest — a lot of corners are cut by the device manufacturers to keep costs down. And those cuts are likely to be in areas like supporting software, which makes certain devices clunky to use, or even artificially limits what can be done with them.

    Hardware hacker Wesley Ellis has been playing with the COLMI R02 Smart Ring, which has garnered a lot of attention lately due to its low price tag and a number of reverse engineering efforts targeted at the device.

    Ellis has developed an open source Python client that can read data produced by the COLMI R02’s onboard sensors.

    The smart rings can be purchased for under $20, and come equipped with an accelerometer as well as heart rate and blood oxygen sensors in a compact and attractive package. The ring also has a Bluetooth transceiver, and by using Ellis’ Python utility, one can easily retrieve measurements from these sensors wirelessly in real-time by running a command line utility.

    https://tahnok.github.io/colmi_r02_client/colmi_r02_client.html

    colmi_r02_client
    Open source python client to read your data from the Colmi R02 family of Smart Rings. 100% open source, 100% offline.

    It’s a cheap (as in $20) “smart ring” / fitness wearable that includes the following sensors:

    Accelerometer
    step tracking
    sleep tracking
    gestures (maybe…?)
    Heart Rate (HR)
    Blood Oxygen (SPO2)

    Reply
  3. Tomi Engdahl says:

    ANTIRTOS: No RTOS Needed
    https://hackaday.com/2024/10/15/antirtos-no-rtos-needed/

    Embedded programming is a tricky task that looks straightforward to the uninitiated, but those with a few decades of experience know differently. Getting what you want to work predictably or even fit into the target can be challenging. When you get to a certain level of complexity, breaking code down into multiple tasks can become necessary, and then most of us will reach for a real-time operating system (RTOS), and the real fun begins. [Aleksei Tertychnyi] clearly understands such issues but instead came up with an alternative they call ANTIRTOS.

    The idea behind the project is not to use an RTOS at all but to manage tasks deterministically by utilizing multiple queues of function pointers. The work results in an ultra-lightweight task management library targeting embedded platforms, whether Arduino-based or otherwise. It’s pure C++, so it generally doesn’t matter. The emphasis is on rapid interrupt response, which is, we know, critical to a good embedded design. Implemented as a single header file that is less than 350 lines long, it is not hard to understand (provided you know C++ templates!) and easy to extend to add needed features as they arise. A small code base also makes debugging easier.

    https://hackaday.io/project/196816-antirtos-no-any-rtos-needed-you-will-see

    Reply
  4. Tomi Engdahl says:

    Taoglas Cuts the Footprint of Wi-Fi, Bluetooth Integration — By Piggybacking an Antenna Onto RJ45
    Clever dipole antenna saves space by piggybacking onto an RJ45 socket — and can be used to quickly add multiple antennas to routers.
    https://www.hackster.io/news/taoglas-cuts-the-footprint-of-wi-fi-bluetooth-integration-by-piggybacking-an-antenna-onto-rj45-1be6c30b5f6f

    Reply
  5. Tomi Engdahl says:

    UNIT Electronics’ Cocket Nova Is a Breadboard-Friendly WCH CH552-Based Eight-Bit Dev Board
    Designed around an enhanced version of Intel’s classic 8051 architecture, this $6 eight-bit board packs in the features.
    https://www.hackster.io/news/unit-electronics-cocket-nova-is-a-breadboard-friendly-wch-ch552-based-eight-bit-dev-board-fa602c2f87fa

    Reply
  6. Tomi Engdahl says:

    Tekoälytehoa moduulissa verkon reunalle
    https://etn.fi/index.php/new-products/16736-tekoaelytehoa-moduulissa-verkon-reunalle

    Tekoälylaskentaa halutaan tehdä yhä lähempänä verkon reunaa, mutta se vaatii nykyistä suorituskykyisempiä, vähemmän tehoa kuluttavia moduuleja. Saksalainen congatec vastaa huutoon uusilla COM Express -moduuleillaan.

    Korteilla on AMD Ryzen Embedded 8000 -sarjan prosessorit. Moduuleissa on jopa kahdeksan Zen 4 -ydintä, innovatiivinen XDNA-neuroprosessori ja tehokas Radeon RDNA 3 -grafiikka. AI-laskennassa AMD:n suoritin tuottaa tekoälypäättelyyn 39 biljoonan operaation (TOPS) suorituskyvyn sekunnissa.

    https://www.congatec.com/en/products/com-express-type-6/conga-tcr8/

    Reply
  7. Tomi Engdahl says:

    Arduinos That See, Hear, Think: A Tour of the Avnet Arduino Pro Edge AI/ML Vision and Speech Kit
    Edge AI bundle includes the Arduino Portenta H7 with Vision Shield, Nicla Vision, and more, plus the software to get you started.
    https://www.hackster.io/news/arduinos-that-see-hear-think-a-tour-of-the-avnet-arduino-pro-edge-ai-ml-vision-and-speech-kit-32ec122f05bc?fbclid=IwY2xjawGEz4hleHRuA2FlbQIxMQABHRC9Vm20Syw6LTGXoPIVDNrzE5UL8ZOu6LxjDszuYfDmbVQDJVK0fE1mig_aem_J8X6iVFGVoyheUN4A7ZpWQ

    Reply
  8. Tomi Engdahl says:

    Rust nousee tasaisen varmasti suosituimpien kielten listalla
    https://etn.fi/index.php/13-news/16764-rust-nousee-tasaisen-varmasti-suosituimpien-kielten-listalla

    Suosituin kieli on tällä hetkellä Python, joka on helppo oppia ja turvallinen, mutta ei nopea. Siksi insinöörit etsivät kiihkeästi nopeita vaihtoehtoja Pythonille. C++ on ilmeinen ehdokas, mutta sitä ei pidetä “turvallisena” sen nimenomaisen muistinhallinnan vuoksi. Rust on toinen ehdokas, vaikkakaan sitä ei ole helppo oppia. Ruoste on turvallisuuden ja nopeuden painottamisen ansiosta matkalla TIOBE-indeksin top 10:een.

    Reply
  9. Tomi Engdahl says:

    Hardware is hard
    Software is soft
    Firmware is firm.

    Reply
  10. Tomi Engdahl says:

    https://etn.fi/index.php/98-in-focus/16761-pieni-radiomoduuli-tekee-katuvalosta-aelykkaeaen-iot-laitteen

    ObiWANin kehittämä älyvalaistusjärjestelmä käyttää mobiili-IoT-yhteyttä etävalvontaan ja -ohjaukseen. Nordic Semiconductorin nRF9160-moduuli muuttaa tavalliset LED-valaisimet IoT-ominaisuuksilla varustetuiksi älylaitteiksi.

    Reply
  11. Tomi Engdahl says:

    https://etn.fi/index.php/13-news/16823-tyoekalu-maeaerittaeae-taeydellisen-antennin

    Antenneja ja IoT-komponentteja kehittävä Taoglas esittelee Electronica-messuilla AntennaXpert-työkaluja, jotka on suunniteltu helpottamaan antennien suunnittelua ja integrointia käyttäjäystävällisillä digitaalisilla työkaluilla. Taoglasin verkkosivuilta ladattava työkalupaketti sisältää Taoglas Antenna Integratorin, Antenna Builderin ja Cable Builderin.

    Reply
  12. Tomi Engdahl says:

    Making Sense Of Real-Time Operating Systems In 2024
    https://hackaday.com/2024/11/13/making-sense-of-real-time-operating-systems-in-2024/

    The best part about real-time OS (RTOS) availability in 2024 is that we developers are positively spoiled for choice, but as a corollary this also makes it a complete pain to determine what the optimal choice for a project is. Beyond simply opting for a safe choice like FreeRTOS for an MCU project and figuring out any implications later during the development process, it can pay off massively to invest some time up-front matching the project requirements with the features offered by these various RTOSes.

    Answering Some Questions

    A crucial distinction when looking at operating systems for embedded systems is the kind of platform it is. If it’s something along the lines of an x86, Cortex-A ARM or similar, you’re likely looking at a desktop-like system, where a real-time OS such as VxWorks, QNX, a BSD or Linux (with or without real-time patches) is probably the best choice, if only due to hardware support concerns. For situations where hard real-time considerations are the most essential, an FPGA/CPLD-based solution might instead be worth it, but this is of course less flexible than an MCU-based solution.

    If at this point an MCU-based solution seems the most sensible one, the next logical question is ‘which one RTOS?’. The answer to this is hidden somewhere in long lists of RTOSes, such as the one found over at Wikipedia, or the one over at the OSRTOS website. Assuming for a moment that we are looking only at open source RTOSes here that are seeing active development, we can narrow it down somewhat to the following list:

    Contiki-NG
    OpenERIKA
    FreeRTOS
    MicroC/OS (Micrium OS)
    Nano-RK (Atmel Firefly, MicaZ motes, MSP430; GPL or commercial)
    NuttX
    RIOT
    Rodos
    RT-Thread
    TI-RTOS
    TizenRT (NuttX fork by Samsung)
    Zephyr (formerly Rocket)
    ChibiOS/RT
    Apache Mynewt

    Of note is that the popular Mbed project was abandoned in July of 2024, rendering the future of this RTOS highly uncertain. Even with that one taken out of the picture, we are still left with an impressive list.

    Perhaps the most important questions here pertain to issues such as:

    Build system requirements
    Demands on a specific compiler (version)
    Programming languages one can use with the OS
    Whether direct hardware access to peripherals is allowed or require going through a HAL of some description.
    Support availability when something inevitably doesn’t work as expected.
    Accessibility of the source code when reading through it (readability, documentation, etc.)

    Baseline Expectations

    The baseline for the build environment demands and supported features is set here at FreeRTOS. It runs on a wide range of (MCU) platforms, provides a number of schedulers, SMP support, happily compiles with just about any compiler toolchain and is C-based so can be used with any programming language that can cooperate with C APIs. Direct hardware access is the standard way for peripherals and the OS generally gets out of your way beyond scheduling and multi-tasking matters. This ‘stay out of the way’ approach persists with developer tools and configuration, which works as easily in Vim as in any oth

    Reply
  13. Tomi Engdahl says:

    Seuraavan sukupolven autosi on huipputehokas tietokone
    https://etn.fi/index.php/13-news/16834-seuraavan-sukupolven-autosi-on-huipputehokas-tietokone

    Autoista on aiemminkin puhuttu ”tietokoneena pyörillä”, mutta Renesasin uuden viidennen sukupolven R-Car-prosessorin myötä hehkutuksesta on tulossa todellisuutta. Autoista tulee tiekoneita, joiden keskusprosessori kykenee ohjaamaan eri laitteita, huolehtimaan turvallisuudesta ja jopa prosessoimaan tekoälyä hyvällä suorituskyvyllä.

    Viiden polven autoprosessoria on kehitetty usean vuoden ajan, sillä Renesas on puhunut siitä ainakin vuodesta 2019 lähtien. Nyt julkistettu X5H-järjestelmäpiiri on autojen ensimmäinen monialuepiiri (multidomain), joka on valmistettu 3 nanometrin prosessissa.

    X5H-piiri yhdistää useita autojen toimintoalueita, kuten kehittyneet kuljettajaa avustavat järjestelmät (ADAS), ajoneuvon viihdejärjestelmät (IVI) sekä gateway-ratkaisut yhdelle sirulle. Se vie osaltaan kehitystä kohti keskitettyjä elektronisia ohjausyksiköitä eli ECUja, jotka ovat korvaamassa vanhoja jaettuja ja nyt suosittuja vyöhyke- eli zonal-ratkaisuja autoissa.

    X5H perustuu innovatiiviseen laitteistopohjaiseen eristystekniikkaan, joka varmistaa turvallisuuden ja tehokkuuden vaativissa ajoneuvosovelluksissa. Eri osa-alueiden (domain) eristys voidaan tehdä joko laitteistopohjaisena eli raudalla, ohjelmallisesti eli hypervisor-pohjaisesti tai hybridimallisesti näiden yhdistelmänä. Idea on tarjota valmistajalle alusta, jolla valita, miten eristää kriittiset ADAS-toiminnot vaikka ohjaamon viihdejärjestelmästä. Niitä voidaan kuitenkin ajaa yhdellä ja samalla SoC-piirillä.

    Seuraavan sukupolven autosi on huipputehokas tietokone

    Julkaistu: 14.11.2024

    Devices Embedded

    Autoista on aiemminkin puhuttu ”tietokoneena pyörillä”, mutta Renesasin uuden viidennen sukupolven R-Car-prosessorin myötä hehkutuksesta on tulossa todellisuutta. Autoista tulee tiekoneita, joiden keskusprosessori kykenee ohjaamaan eri laitteita, huolehtimaan turvallisuudesta ja jopa prosessoimaan tekoälyä hyvällä suorituskyvyllä.

    Viiden polven autoprosessoria on kehitetty usean vuoden ajan, sillä Renesas on puhunut siitä ainakin vuodesta 2019 lähtien. Nyt julkistettu X5H-järjestelmäpiiri on autojen ensimmäinen monialuepiiri (multidomain), joka on valmistettu 3 nanometrin prosessissa.

    X5H-piiri yhdistää useita autojen toimintoalueita, kuten kehittyneet kuljettajaa avustavat järjestelmät (ADAS), ajoneuvon viihdejärjestelmät (IVI) sekä gateway-ratkaisut yhdelle sirulle. Se vie osaltaan kehitystä kohti keskitettyjä elektronisia ohjausyksiköitä eli ECUja, jotka ovat korvaamassa vanhoja jaettuja ja nyt suosittuja vyöhyke- eli zonal-ratkaisuja autoissa.

    X5H perustuu innovatiiviseen laitteistopohjaiseen eristystekniikkaan, joka varmistaa turvallisuuden ja tehokkuuden vaativissa ajoneuvosovelluksissa. Eri osa-alueiden (domain) eristys voidaan tehdä joko laitteistopohjaisena eli raudalla, ohjelmallisesti eli hypervisor-pohjaisesti tai hybridimallisesti näiden yhdistelmänä. Idea on tarjota valmistajalle alusta, jolla valita, miten eristää kriittiset ADAS-toiminnot vaikka ohjaamon viihdejärjestelmästä. Niitä voidaan kuitenkin ajaa yhdellä ja samalla SoC-piirillä.

    Uudella piirillä on myös mahdollisuus laajentaa tekoälyn ja grafiikkaprosessoinnin suorituskykyä chiplet- eli ns. sirpale-teknologian avulla. X5H tukee UCIe-protokollaa sirpaleiden liittämiseen järjestelmään ja Renesasin mukaan näin voidaan tehdä ja samalla huolehtia siitä, että autojen toiminnallisen turvallisuuden FuSa-vaatimukset täyttyvät.

    R-Car X5H yhdistää sovellusten prosessoinnin, reaaliaikaisen prosessoinnin, GPU- ja tekoälylaskennan, suurien näyttöjen tuen ja anturiyhteydet yhdelle sirulle. Tekoälyn kiihdytys NPU-prosessorilla saavuttaa jopa 400 TOPS:n suorituskyvyn. GPU-prosessointi yltää jopa 4 teraflopsin suorituskykyyn. Lukemat ovat ennennäkemättömiä autojen järjestelmäpiireissä.

    Reply
  14. Tomi Engdahl says:

    https://etn.fi/index.php/13-news/16835-jo-ensimmaeinen-paristonvaihto-tekee-energiankeruusta-kannattavaa

    Belgialainen e-peas tunnetaan energiankeruun piirejä kehittävänä yrityksenä. Energiankeruun päätavoite on poistaa asennuskustannukset, jotka liittyvät paristojen käyttöön. Toimitusjohtaja Geoffroy Gossetin mukaan monissa tapauksissa jo ensimmäinen paristonvaihto tekee energiankeruusta kannattavaa.

    Energiankeruussa voidaan hyödyntää monia lähteinä IoT-laitteiden pyörittämiseen. E-peas tukee aurinkoenergia (ja sisällä valoa), tärinää, lämpöä, induktiota, ilma- ja vesivirtauksia sekä RF-aaltoja. Electronica-messuilla oli useita demoja, joissa virtaa kerättiin esimerkiksi suoraan virtajohdosta induktion avulla.

    Energiankeruu tarjoaa kestävän vaihtoehdon perinteisille paristoratkaisuille. Vaikka alkuinvestointi energiankeruulaitteistoon voi olla korkeampi, energiankeruu osoittautuu kustannustehokkaammaksi heti, kun ensimmäinen paristonvaihto tulee ajankohtaiseksi. Paristot, joita tällaisiin järjestelmiin käytetään, eivät ole vain muutaman sentin hintaisia, vaan yksittäinen paristo voi maksaa jopa 2–3 dollaria.

    Teollisuus oli energiankeruun ja myös e-peasin ensimmäinen tavoite, sillä siellä siitä olisi ollut eniten hyötyä. Koronapandemia kuitenkin suuntasi kehityksen enemmän kuluttajasovelluksiin, ja nykyään energiankeruun sovellukset ovat yhä enemmän kuluttajien käytössä. Älykotiratkaisuissa energiankeruu on looginen valinta mille tahansa laitteelle, joka voi vähentää kaapeloinnin tarvetta ja tehdä rakennuksista älykkäämpiä. Esimerkiksi ovikello, joka kerää energiansa katkaisimen liikkeestä (kineettinen energia), on yksi tällaisista sovelluksista.

    E-peas pyrkii rakentamaan ekosysteemiä, jossa se tarjoaa asiakkailleen kumppaneita sekä teholähteen kuten pienen aurinkokennon ja energian varastoinnin ratkaisussa. Itse PMIC-piiri on kuitenkin aivan keskeisessä osassa. Tehonhallintapiirin tehtävänä on löytää lähteen optimipiste kerättävälle energialle, se sovittaa jännitteen varastoratkaisulle ja optimoi energian purkua sovelluksen käyttöön. Paristoon ei voi muodostua ylijännitettä, eikä sitä voida ladata tai purkaa liian korkeissa lämpötiloissa.

    IoT-laitteissa ei puhuta isoista tehoista. Sisällä alhaiset virrat ovat milliwattiluokkaa, ulkonakin jäädään yleensä alle watin tehoihin

    Reply
  15. Tomi Engdahl says:

    20 System Design Concepts Explained in 10 Minutes
    https://www.youtube.com/watch?v=i53Gi_K3o7I

    A brief overview of 20 system design concepts for system design interviews.

    0:00 – Intro
    0:22 – Vertical Scaling
    0:39 – Horizontal Scaling
    1:05 – Load Balancers
    1:50 – Content Delivery Networks
    2:25 – Caching
    2:52 – IP Address
    3:05 – TCP / IP
    2:52 – IP Address
    3:58 – Domain Name System
    4:41 – HTTP
    5:45 – REST
    6:05 – GraphQL
    6:35 – gRPC
    7:22 – WebSockets
    7:58 – SQL
    8:25 – ACID
    8:55 – NoSQL
    9:20 – Sharding
    9:45 – Replication
    10:20 – CAP Theorem
    10:50 – Message Queues

    Reply
  16. Tomi Engdahl says:

    Nordicin uusimmat vievät esimerkiksi älysormukset uudelle tasolle
    https://etn.fi/index.php/13-news/16853-nordicin-uusimmat-vievaet-esimerkiksi-aelysormukset-uudelle-tasolle

    Nordic Semiconductor lanseerasi viime viikon Electronica-messuilla uuden sukupolven langattomat järjestelmäpiirinsä, jotka perustuvat nRF54-alustaan. Sarjaan kuuluvat nRF54L15, nRF54L10 ja nRF54L05, jotka tarjoavat huippuluokan tehokkuutta, suorituskykyä ja joustavuutta Bluetooth LE- ja IoT-sovelluksiin.

    Uudet piirit yhdistävät 2,4 GHz radion ja MCU:n muistin ja oheislaitteet yhteen vähävirtaiseen komponenttiin. Tämä tekee niistä ihanteellisia monenlaisiin käyttökohteisiin, kuten älysormuksiin, peliohjaimiin, terveydenhuollon laitteisiin, älykoteihin ja teollisuuden IoT-tuotteisiin.

    Siruista nRF54L15 on suunniteltu vaativiin sovelluksiin, kun taas nRF54L10 ja nRF54L05 on kohdistettu kustannusherkkiin käyttötarkoituksiin, kuten älylappuihin ja omaisuuden seurantaan.

    Reply
  17. Tomi Engdahl says:

    Käyttöliittymälle tulee uusi rooli verkon reunalla
    https://etn.fi/index.php/tekniset-artikkelit/16878-kaeyttoeliittymaelle-tulee-uusi-rooli-verkon-reunalla

    Kun verkkojen välisten yhdyskäytävien toteuttamisessa ollaan siirtymässä enenevässä määrin yhdessä tapahtuvaan reunalaskennan ja tekoälyn hyödyntämiseen, yksi järjestelmäkomponentti tahtoo jäädä turhan vähälle huomiolle: ihmisen ja koneen välisen rajapinnan toteuttava laite. Näin voi käydä esimerkiksi käytettäessä laitekehikkoja tai tietokonekoteloita järjestelmäarkkitehtuuriin kuuluvien edge-solmujen tekoälytoimintojen sijoituspaikkoina, kirjoittaa Advantech artikkelissaan.

    Vastaavasti maantieteellisesti jakautuneissa arkkitehtuureissa käytetään älykkäitä matkapuhelinreitittimiä reunalaskennan toteuttamisessa. Nämä reitittimet voivat toimia isäntinä sovellusohjelmistoille kuten protokollakääntäjille tai tekoälypäättelijöille. Monissa näissä toteutuksissa arkkitehtuuriin kuuluu myös visuaalisuuteen liittyviä vaatimuksia joko paikallisesti konetasolla tuotantolinjan tai koko järjestelmän toiminnan valvonnassa.

    Ihmisen ja koneen rajapinnan toteuttavat HMI-laitteet nähdään usein muissa laitteissa olevan tai niissä syntyvän datan paikallisina päätepisteinä. Tällöin kuitenkin menetetään mahdollisuus yksinkertaistaa koko järjestelmän suunnittelua verrattuna siihen, jos sen sijaan käytettäisiinkin HMI-laitetta älykkäänä edge-yhdyskäytävänä omalla tavallaan.

    Automaation HMI-ohjelmistot

    Automaation arkkitehtuureissa olennaisen tärkeitä komponentteja ovat HMI-ohjelmistot, jotka toimitetaan joko integroituna osana näyttölaitetta tai erillisenä sovellusohjelmistona asennettavaksi näyttölaitteeseen tai teollisuus-PC:hen ja joiden tehtävänä on esittää tietoa insinööreille ja käyttöhenkilöstölle sekä mahdollistaa heidän vuorovaikutuksen käynnissä olevaan prosessiin ja laitteisiin.

    Jopa tämän päivän yhä verkottuneemmassa maailmassa törmätään vielä tapauksiin, joissa prosessilaitoksen käyttöhenkilökunta ei joko osaa tai ei halua tulla yhdistetyksi ulkoisiin järjestelmiin ja laitteisiin. Tyypillisenä esimerkkinä voisi olla vanhemman tai perinteisen PLC-tyylisen laitteen käyttäminen koneessa tai tuotantolinjalla. Kuitenkin on tarpeen, että insinöörit ja käyttöhenkilöstö ovat vuorovaikutuksessa järjestelmän kanssa, vaikka käytössä olevat PLC:t eivät tukisikaan alueverkon pilviyhteyttä.

    Graafinen päätepiste

    Tässä käyttötapauksessa HMI-paneeli toimii visualisointivälineenä teollisuus-PC:lle tai vastaavalle, joka tarjoaa yhdistettyä reunalaskentaa ja tekoälyä koneille, tuotantolinjoille tai prosesseille.

    HMI yhdyskäytävänä

    Konsepti, jossa HMI-laitetta käytetään järjestelmän yhdyskäytävänä, on järkevää. Arkkitehtuurin kannalta yhdyskäytävä toimii pisteenä, jossa data konvergoidaan alemman tason laitteille sopivaksi, ja näinhän tapahtuu missä tahansa HMI-toteutuksen pisteessä.

    Reply
  18. Tomi Engdahl says:

    Embedded C is the same language as C, you just use it a bit differently/more carefully – some stuff that is correct on a “full” computer is a bad idea in embedded and vice-versa.

    In general, dynamic memory allocation is not good in embedded systems. They often run for years without a restart and memory leaks are completely unacceptable

    https://www.reddit.com/r/embedded/comments/wj3m0i/embedded_development_language_selection/

    Reply
  19. Tomi Engdahl says:

    Embedded C usually does not terminate (return from main), and will typically be doing a lot of fairly direct hardware access. Often there is no operating system as such. Sometimes the function signature for main can be VERY non standard, sometimes there is no floating point unit or no floating point at all.

    Lots of interrupt handlers (which usually either need very non standard compiler support or you need to write stubs in assembler), hand configured DMA and suchlike, sometimes pointer games with memory mapped peripherals, that kind of thing. Volatile and friends are commonly seen in embedded code, but are rare outside the embedded scene.

    Typically STM32 stuff would absolutely be embedded C, possibly with something like freertos, and of course STs joke of a HAL upon occasion.

    Often things like file system access will often not exist, and printf may require you to write a stub for the low level character output to whatever interface you are using.

    Language is MOSTLY the same, but available libraries tend to be very different, and the style changes, often embedded code does not for example do dynamic memory at all, because the risks of memory fragmentation in a system expected to run for years at a time are just too great.

    https://www.reddit.com/r/embedded/comments/16nnn07/i_just_dont_understand_the_difference_between/

    Reply
  20. Tomi Engdahl says:

    Top 10 Best Embedded Systems Programming Languages in 2025
    Last Updated : 23 Oct, 2024
    https://www.geeksforgeeks.org/embedded-systems-programming-languages/

    Reply
  21. Tomi Engdahl says:

    Halvalla radio Raspberry Pi -pikokorttiin
    https://etn.fi/index.php/13-news/16883-halvalla-radio-raspberry-pi-pikokorttiin

    Raspberry Pi -perhe sai uuden jäsenen, kun Raspberry Pi Pico 2 W julkaistiin tänään. Uutuus on varustettu integroiduilla langattomilla ominaisuuksilla, kuten 2,4 GHz Wi-Fi:llä (Wi-Fi 4) ja Bluetooth 5.2:lla. Tämä tekee siitä houkuttelevan vaihtoehdon erityisesti IoT-projekteihin ja langattomiin sovelluksiin.

    Vain 7 dollarin hintalapullaan Pico 2 W tarjoaa runsaasti vastinetta rahoille. Kortti on suunniteltu samaan muottiin kuin edeltäjänsä, Raspberry Pi Pico, ja se tukee laajasti lisävarusteita ja kehitystyökaluja.

    Suoritin on uusittu RP2350-siru, joka yhdistää Arm Cortex-M33- ja RISC-V Hazard3 -arkkitehtuurit. Rortilla on 520 KB SRAM-muistia ja 4 MB flash-muistia. Radiomoduuli on Infineonin CYW43439 -moduuli, joka mahdollistaa Wi-Fi 4:n ja Bluetooth 5.2:n.

    Kortilla on 26 GPIO-nastaa ja se tukee esimerkiksi UART-, SPI-, I2C-, PWM- ja ADC-yhteyksiä.

    Raspberry Pi Pico 2 W on sale now at $7
    https://www.raspberrypi.com/news/raspberry-pi-pico-2-w-on-sale-now/

    Reply

Leave a Reply to Tomi Engdahl Cancel reply

Your email address will not be published. Required fields are marked *

*

*