Recent Posts
Enabling WPA3 on Raspberry Pi
Introduction After getting the Raspberry Pi 5 it was very disappointing to see that it does not support WPA3 for WiFi connections.
$ iw list Wiphy phy0 wiphy index: 0 ... Supported extended features: * [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records * [ 4WAY_HANDSHAKE_STA_PSK ]: 4-way handshake with PSK in station mode * [ 4WAY_HANDSHAKE_STA_1X ]: 4-way handshake with 802.1X in station mode * [ DFS_OFFLOAD ]: DFS offload There is even a ticket open open on Github and besides a lot of comments, it seems nobody really cares.
Read more about this entry
Connecting Matter - Part 1
Overview The Connectivity Standards Alliance just released the Matter 1.2 specification and with that it might be a good start to look into the inner workings of this standard and how things actually work.
Matter tries to unify the Smart Home between all the ecosystems from Apple, Google, Amazon, Samsung and others. If you use one of these ecosystems, then the expierence seems to be unchanged and you are most likely don’t see any difference using a Matter device and hopefully things just work.
Read more about this entry
Laird BL654 USB Bluetooth Dongle
Overview The Laird BL654 dongle is an alternative to using the Nordic nRF52 dongle for a Bluetooth controller as described in this post.
One big advantage is that the Laird dongle has case around it and it less likely to be damaged. So it can be nicely used in multiple use cases where using a logic board without a case is not a good idea.
The Zephyr documentation has a separate page for the BL654 dongle, but it is essentially just a nRF52 dongle in a nice package.
Read more about this entry
Creating Bluetooth dongle using Zephyr
Overview The Zephyr RTOS includes support for Bluetooth controller and the lower-layer HCI interface. This allows building a Bluetooth dongle using the Nordic nRF52 dongle and the connecting to any machines as a standard Bluetooth HCI dongle.
Zephyr requirements The quickest path to setup a Zehyr environment is to follow the Getting Started Guide.
When it comes to Linux, I am defaulting to Fedora Linux and my installation of a Fedora 38 has all required development components already installed.
Read more about this entry
Looking into linenoise
Motivation Linenoise is an editing library for command line input. It is written in C and aims to be minimal, permissively licensed and used as GNU readline replacement. After GNU readline switched to GPLv3 or later as its license, looking at alternative editing libraries became a necessity for some project. It is time to explore Linenoise as an alternative.
Introduction The project lists following features:
Single and multi line editing mode with the usual key bindings History handling Completion Hints (suggestions at the right of the prompt as you type) Multiplexing mode, with prompt hiding/restoring for asynchronous output About ~850 lines (comments and spaces excluded) of BSD license source code Only uses a subset of VT100 escapes (ANSI.
Read more about this entry
Using SPDX-License-Identifier
Background SPDX is an open standard for communicating software bill of material and license information (and some other information).
The work started in February of 2010 and published the SPDX 1.0 specification in August of 2011. Any open source project started before that adopted its own method of providing license information in its source code.
If projects haven’t moved over to use the SPDX-License-Identifier it might a good time to switch and look at how other major open source projects have utilized it.
Read more about this entry