RSS Bot

Texas Instruments has unveiled the SimpleLink CC33xx family of Wi-Fi 6 companion IC with optional Bluetooth 5.3 Low Energy designed to be connected to a microcontroller (MCU) or a microprocessor (MPU) for secure and power-efficient IoT devices, The SimpleLink CC3000 supports 2.4 GHz WiFi 6, and interfaces over SDIO, SPI, and/or UART to the host system, while the SimpleLink CC3301 also adds support for Bluetooth 5.3 LE. Both chips can operate in high-temperature environments up to 105ºC. Texas Instruments CC3300/CC3301 specifications: Wireless 2.4 GHz WiFi 6 (802.11ax) up to 50 Mbps; Support for TWT and OFDMA, multirole (Access Point and Station) CC3301 only – Bluetooth 5.3 Low Energy up to 2 Mbps WiFi and Bluetooth COEX Host interface – 4-bit SDIO or SPI, and UART to external MCU or MPU Security – FW authentication and anti-rollback protection, WPA2/WPA3, Secured host interface Pacakge – 40-pin QFN package (5×5 mm) Temperature range [...] The post TI launches Simplelink CC3300/CC3301 WiFi 6, Bluetooth 5.3 LE companion IC for IoT applications appeared first on CNX Software - Embedded Systems News. View the full article

Disable config_ion for better compatibility with modern android containers like redroid Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number [AR-9999] How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [ ] Test A [ ] Test B Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

rootfs/image: avoid apt junk leftover by debootstrap; always cleanup apt cache on target Thanks to @amazingfate for raising this in https://github.com/armbian/build/pull/5063 - this will save us some 2Tb of storage, not to mention a lot of bandwidth. rootfs: rootfs-create: show a summary of the 20 biggest dirs, right before tarring the rootfs (for debugging) rootfs: rootfs-create: show usage of caches between first and second stages rootfs: rootfs-create: cleanup junk left by debootstrap after second stage rootfs: rootfs-create: always clean apt stuff at the end rename apt_purge_unneeded_packages() to apt_purge_unneeded_packages_and_clean_apt_caches() for clarity image: apt_purge_unneeded_packages_and_clean_apt_caches(): warn if apt caches not empty; clean them off, always. host-utils: local_apt_deb_cache_prepare(): also test the target, warn if not empty extension: cleanup-space-final-image: do NOT clean apt stuff. done in core now the metric sh*t-ton of debugs added should help the next person who faces this in the future View the full article

Want to develop your Meson project in a modern IDE? Make sure to install Meson VSCode extension which is now fully functional with the recent release of Meson 1.1.0! View the full article

BLIKVM is an open-source KVM over IP software that helps you manage servers or workstations remotely regardless of the health of the target system, and currently working with Raspberry Pi CM4 hardware, a Raspberry Pi HAT, or a PCIe board, and a new model based on MangoPi’s Allwinner H616 CPU module is coming soon. We’ve previously written about the Raspberry Pi-based PiKVM DIY project, followed by the PiKVM v3 Raspberry Pi HAT from the same project, and now I can see there’s a CM4-based PiKVM V4 that was on Kickstarter last month and raised over $800,000… You’d think this kind of system would be rather a niche market, but there’s even demand to have a similar open-source project called BLIKVM offering many of the same features since it’s based on PiKVM, except for the option to use a PCIE card fitted with a CM4 module. Highlights of the BLIKVM project: [...] The post BLIKVM open-source KVM over IP works with Raspberry Pi CM4, Raspberry Pi HAT, PCIe card, and soon Allwinner H616 appeared first on CNX Software - Embedded Systems News. View the full article

PicoMQTT is a lightweight MQTT library for Arduino/PlatformIO optimized for ESP8266 and ESP32. It not only supports the MQTT Client mode like most existing solutions but also the MQTT Broker mode which transforms an ESP8266 or ESP32 board into an MQTT gateway replacing a Raspberry Pi board or an IoT gateway typically used for this task. The library follows MQTT 3.1.1 specification, supports the publishing and consuming of arbitrary-sized messages, can deliver thousands of messages per second, and supports easy integration with the ArduinoJson library to publish and consume JSON messages. MQTT Broker code example: [crayon-643e4a00948d8570550725/] There are some limitations to the implementation due to constrained resources in the ESP8266 and ESP32, notably: Client only supports MQTT QoS levels 0 and 1 Broker only supports MQTT QoS level 0, ignores will and retained messages. Another downside highlighted by the developer is that only ESP8266 and ESP32 boards are supported. Developer [...] The post PicoMQTT – An MQTT Client/Broker library for ESP8266 and ESP32 appeared first on CNX Software - Embedded Systems News. View the full article

ADLINK Ampere Altra Dev Kit is an “IoT prototyping kit” based on an ATX motherboard fitted with a COM-HPC-ALT Server Type Size E module powered by an Ampere Altra 32, 64, or 80-core Arm Neoverse N1 server processor, and supporting up to 768GB DDR4 memory. It’s basically the same hardware as found in the Ampere Altra Developer Platform (AADP), but without the tower and power supply, nor optional features like liquid cooling or 10GbE interfaces. Ampere Altra Dev Kit (AADK) specifications and content: Computer-on-Module – COM-HPC Server Type Size E Ampere Altra module with Ampere Altra 32 to 80-core 64-bit Arm Neoverse N1 processor up to 1.7/2.2/2.6 GHz (32/64/80 cores, TPD: 60W to 175W), up to 768 DDR4 ECC memory Mainboard – COM-HPC Server Base carrier board Storage – 2x M.2 slot for NVMe SSD Video – VGA port Audio – 3.5mm audio jack Networking – 1x Gigabit Ethernet Expansion [...] The post ADLINK Ampere Altra Dev Kit features ATX motherboard with 32 to 80-core Arm COM-HPC CPU module appeared first on CNX Software - Embedded Systems News. View the full article

Description Whenever something is changed in the config/boards/ folder execute rebuild of board build list GitHub action. This simplify board images re-build process as one can only select image from the list. Version is bumped automatic, build list variant is predefined. Jira reference number AR-1664 How Has This Been Tested? [x] Manual execute from another repository Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description https://forum.armbian.com/topic/27917-wireguard-module-in-default-kernel-configuration/#comment-163826 tl;dr: Add wireguard to sunxi-current Jira reference number [AR-9999] How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Build kernel Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

small batch of lib fixes (mid+/April'23) Fixing the last batch. Some stupid mistakes. revert: run kernel make through pipetty for moar colors (breaks make menuconfig) - thanks @EvilOlaf artifacts: add git SHA1 sanity checking memoize-cached: add flock locking to run_memoized() to avoid error when run in parallel lib: shellfmt & fix gen-library to match artifact: rootfs: fix artifact_rootfs_config_dump() with added rootfs pkgs (should work now, I promise) View the full article

Description pixz was invented when xz did not support multi-threading natively. Now it is pretty much obsolete. Jira reference number [AR-9999] How Has This Been Tested? Hasn't. Feel free to do testings. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Lilygo has launched yet another ESP32-S3 board with an integrated display, but the T-HMI has a larger 2.8-inch color display and a resistive touch panel suitable for HMI (Human Machine Interfaces). It is also equipped with three Grove connectors for expansion with sensors or actuators. Like all the recent ESP32-S3 boards from Lilygo, the T-HMI features the ESP32-S3NR8 WiFi 4 and Bluetooth MCU with 8MB PSRAM, as well as a 16MB SPI flash, a microSD card slot, a few buttons, and power from USB or a LiPo battery. Lilygo T-HMI board specifications: Wireless MCU – Espressif Systems ESP32-S3R8 dual-core Tensilica LX7 @ up to 240 MHz with vector instructions for AI acceleration, 512KB RAM, 8MB PSRAM, wireless connectivity Storage – 16MB SPI flash, microSD card socket Connectivity via ESP32-S3 2.4 GHz 802.11 b/g/n Wi-Fi 4 with 40 MHz bandwidth support Bluetooth Low Energy (BLE) 5.0 connectivity with long-range support, up [...] The post T-HMI ESP32-S3 board comes with an 2.8-inch touchscreen color display, three Grove expansion connectors appeared first on CNX Software - Embedded Systems News. View the full article

Description Add dockerproxy to accelerate ghcr.io. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Build with command ./compile.sh kernel COMPRESS_OUTPUTIMAGE=sha,gpg,xz DEB_COMPRESS=xz DOWNLOAD_MIRROR=china BOARD=rock-5b BRANCH=legacy GITHUB_MIRROR=ghproxy GHCR_MIRROR=dockerproxy DOCKER_ARMBIAN_BASE_COORDINATE_PREFIX="ghcr.dockerproxy.com/armbian/docker-armbian-build:armbian-" Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Apt cache is only useful in build time. Users usually don't need cache for installed packages. Removing them will save space and make images smaller. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Build with command ./compile.sh COMPRESS_OUTPUTIMAGE=sha,gpg,xz DEB_COMPRESS=xz DOWNLOAD_MIRROR=china BOARD=rock-5b BRANCH=legacy GITHUB_MIRROR=ghproxy RELEASE=jammy BUILD_MINIMAL=no BUILD_DESKTOP=yes KERNEL_CONFIGURE=no DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base DESKTOP_APPGROUPS_SELECTED="3dsupport browsers chat desktop_tools editors email internet multimedia office programming remote_desktop", saving about 300MB space. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Raspberry Pi recently received a strategic investment from Sony (Semiconductor Solutions Corporation) in order to provide a development platform for the company’s edge AI devices leveraging the AITRIOS platform. We don’t have many details about the upcoming Raspberry Pi / Sony device, so instead, I decided to look into the AITRIOS platform, and currently, there’s a single hardware platform, LUCID Vision Labs SENSAiZ SZP123S-001 smart camera based on Sony IMX500 intelligent vision sensor, designed to work with Sony AITRIOS software. LUCID SENSAiZ Smart camera SENSAiZ SZP123S-001 specifications: Imaging sensor – 12.33MP Sony IMX500 progressive scan CMOS sensor with rolling shutter, built-in DSP and dedicated on-chip SRAM to enable high-speed edge AI processing. Focal Length – 4.35 mm Camera Sensor Format – 1/2.3″ Pixels (H x V) – 4,056 x 3,040 Pixel Size, H x V – 1.55 x 1.55 μm Networking – 10/100M RJ45 port Power Supply – PoE+ via [...] The post Sony IMX500-based smart camera works with AITRIOS software appeared first on CNX Software - Embedded Systems News. View the full article

Description ghproxy is a github mirror making use of cloudflare cdn, which is ultra fast in China. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Build kernel with ./compile.sh kernel COMPRESS_OUTPUTIMAGE=sha,gpg,xz DEB_COMPRESS=xz DOWNLOAD_MIRROR=china BOARD=rock-5b BRANCH=legacy GITHUB_MIRROR=ghproxy Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description In commit 0aa61abe7 (armbian-audio-config: Massively speed up script) this script was changed to not call amixer for each control, but just once for each card, feeding commands for many controls in one invocation with the --stdin option. In that commit, two errors were introduced: Controls that were intended to be muted were turned on instead. This affects the "CD", "Mic" and "Internal Speaker" controls. This occured because there is a helper shell function whose arguments were renumbered, but the last argument kept the old numbering, keeping it always at the default value of "on", even when it should have been "mute". Controls with a space in their name would be ignored. In the original script, arguments (including these names) were quoted and passed separately to the amixer command. Now, they are quoted when passed to echo, but that produces an unstructured line with the quoting removed that can no longer be correctly parsed by amixer for names with spaces. This commit fixes both problems be correctly numbering the arguments and adding an additional layer of quoting. How Has This Been Tested? On an Orange PI PC change some controls with alsamixer, run the script and verify the controls are correct. In particular, I changed the "Line Out" control to verify spaces now work and changed the "Mic1" control to verify muting works (with a small manual changes to the script, since it normally only mutes "Mic", not "Mic1". Additionaly, run systemctl mask alsa-restore.service (to work around another issue, see below) and restart the system, see that these controls have the right value again directly after bootup. Note that I've tested this with a slightly older and customized 23.02 version, I haven't gotten time yet to test with a clean master build, but the script itself is still the same, so the change should work the same there. Issue with alsa-restore I did run into an unrelated issue: On my customized image (but I suspect a clean master will behave the same), alsa-restore.service overwrites the settings set by armbian-audio-config. I believe this issue is orthogonal to the issues fixed by this PR and probably deserves its own issue after I verify it also occurs on a clean master build. However, it does mean that the fixes made by this PR might not be directly visible (which is why I tested with alsa-restore.service masked), so I wanted to mention this here. Then, for some additional detail (to be moved to a separate issue later - just want to share this somewhere for now). The alsa-restore service might make sense once a system is in normal use (alsa-restore saves the mixer settings at shutdown and restores them on startup), but maybe armbian-audio-config would still want to supply the initial values for that process. What I've seen is that during image generation, a /var/lib/alsa/asound.state file is generated (presumably with mixer settings from the build system?), which is then restored on the first boot, overwriting some or maybe all of the settings from armbian-audio-config. I tried removing the /var/lib/alsa/asound.state file so armbian-audio-config could maybe define the intitial settings, but it seems that it then still sets default settings (the manpage says: restore loads driver state for the selected soundcard from the configuration file. If restoring fails (eventually partly), the init action is called. The default settings used by alsactl seem to be set by config files, see the alsactl_init manpage. I wonder if maybe this means that armbian-audio-config is actually redundant, and its function could be fulfilled by alsactl restore/init as well (though maybe the supplied init configs must be modified to achieve the same thing the script currently does)? One thought is that the script might be useful for systems that do not have the alsa-restore service or alsactl installed, but these come from the same package as the amixer command used by armbian-audio-config, so that's not a viable case either. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas N/A [ ] I have made corresponding changes to the documentation N/A [ ] My changes generate no new warnings N/A [ ] Any dependent changes have been merged and published in downstream modules N/A View the full article

Indiedroid Nova is another Rockchip RK3588S SBC with Raspberry Pi 4 form factor, up to 16GB RAM, with a heatsink that serves as a protective cover, fitted with a fan (if needed), and an optional swappable flash module up to 64GB capacity. The Nova board has basically the same port layout as the Raspberry Pi 4, except for one of the micro HDMI ports being replaced by a USB Type-C port with support for DisplayPort, so you’ll still get a Gigabit Ethernet port, WiFi 5 & Bluetooth 5.0 connectivity, two USB 3.0 ports, two USB 2.0 ports, MIPI CSI and DSI connectors, etc… Indiedroid Nova specifications: SoC – Rockchip RK3588S CPU – Octa-core processor with 4x Cortex-A76 cores @ up to 2.2-2.4 GHz, 4x Cortex-A55 cores @ up to 1.8 GHz GPU – Arm Mali-G610 GPU with OpenGL ES 3.2, OpenCL 2.2, and Vulkan 1.2 support VPU – 8Kp60 video [...] The post Indiedroid Nova is a Rockchip RK3588S SBC with full-body heatsink, fan, and a swappable eMMC flash appeared first on CNX Software - Embedded Systems News. View the full article

Description Add support for NanoPi R6S and R6C devices. Both devices are almostly same so we can have one image for them. Kernel PR: https://github.com/armbian/linux-rockchip/pull/15 Jira reference number AR-1663 How Has This Been Tested? [x] USB ports [x] eMMC boot [x] Ethernet ports [ ] Xorg works Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

kernel: fix for 6.3+ linux-headers pkg due to upstream dir change extra: run kernel make through pipetty for moar colors Small detour: in v6.3-rc1, in commit https://github.com/torvalds/linux/commit/799fb82aa132fa3a3886b7872997a5a84e820062, the tools/vm dir was renamed to tools/mm. Unfortunately tools/Makefile still expects it to exist, and make clean in the tools dir fails. Drop in a fake Makefile there to work around this. Should fix #4991 View the full article

In this article, we will show you how to set up a WireGuard server on Ubuntu in order to use it for remote login. Introduction to WireGuard First of all, let’s first understand, what is WireGuard? WireGuard is a very simple and fast VPN tool with state-of-the-art encryption. Its goal is to be faster, simpler, more streamlined, and easy to use than IPsec, while avoiding the hassle of large-scale configuration. WireGuard is designed as a general-purpose VPN to run on embedded interfaces and supercomputers in many different environments. Originally released for the Linux kernel, WireGuard is now widely deployed and supported across platforms (Windows, macOS, BSD, iOS, Android). WireGuard is growing rapidly and is already considered the most secure, easiest-to-use, and simplest VPN solution in the industry. Basic Concepts of WireGuard Several basic concepts are involved in WireGuard: Peer: A node in WireGuard. Private key: Each node has its own [...] The post How to setup a WireGuard server on Ubuntu for remote login appeared first on CNX Software - Embedded Systems News. View the full article

extensions: rkdevflash: simplify usage of rkdeveloptool (on Linux) only works bare Linux, not Docker. to flash Rockchip images to eMMC either during image build or separately with flash CLI command included in https://github.com/armbian/build/pull/5055 Usage: ./compile BOARD=xxx [...] EXT=rkdevflash Will build rkdeveloptool for you, and after image is built, enters a loop waiting for device. Then either uploads rkbin loader if in Maskrom mode, or straight flashes the image if in Loader mode. Finally it reboots the device after flashing. Working with rk3588's loader with changes included in https://github.com/armbian/build/pull/5056 View the full article

extensions: add v4l2loopback-dkms, very similar to the zfs extension Raison d'être: prove linux-headers work, at least, minimally View the full article

Add WiP Mekotronics R58 boards (rockchip-rk3588) mekotronics.com rockchip-rk3588: add new board mekotronics-r58-minipc.wip (Mekotronics R58 MiniPC, and variants) rockchip-rk3588: add new board mekotronics-r58x.wip (Mekotronics R58X) rockchip-rk3588: add new board mekotronics-r58x-4g.wip (Mekotronics R58X-4G); add u-boot patches rockchip-rk3588: set ROCKUSB_BLOB for RockUSB Maskrom -> Loader mode u-boot: same as Radxa Rock-5A. RockUSB and UMS works; boot from eMMC only. No USB, no NVMe. Can stop u-boot by holding Shift-M during boot on serial console. Kernel: was handled at https://github.com/armbian/linux-rockchip/pull/12 and https://github.com/armbian/linux-rockchip/pull/14 is pending. Thanks @amazingfate for the kernel reviews and @monkaBlyat for the DTS's, and @NicoD-SBC for the R58X-4G unit. Pinout is under the board. On this picture: bottom is GND, middle is RX and top is TX View the full article

rpardini's bunch of lib changes - mid-April'23 Themes: actually working JSON dumps, both for images and artifacts; also fast, via CONFIG_DEFS_ONLY actually working rootfs artifacts / remote OCI .debs per-release moar power to extensions, standardize some mechanisms fixes cli: flash: introduce flash CLI command; introduce hook post_build_image_write config: refactor calculate_image_version() out of create_image_from_sdcard_rootfs(), make more flexible, predict IMAGE_FILE_ID during config default IMAGE_INSTALLED_KERNEL_VERSION="generic" instead of "linux" artifact: rootfs: fix artifact_rootfs_config_dump() to include all inputs to aggregation logging: better logging when ANSI_COLOR=none (eg, during info collection) config/extensions: consolidate EXTRA_IMAGE_SUFFIXES array as the way to add to image filename, during configuration can add to EXTRA_IMAGE_SUFFIXES array during user_config or extension_prepare_config in the end goes into a EXTRA_IMAGE_SUFFIX global readonly this simplifies extension code we still can't "predict" image names during configuration since it includes the kernel version (6.2.11/generic) which only comes later artifacts armbian-desktop/armbian-bsp-desktop: fix artifact_base_dir to include ${RELEASE}/ -- otherwise local & remote paths don't match artifacts-obtain: add sanity check, after getting remotely, make sure it is indeed available locally artifacts: introduce PRE_PREPARED_HOST=yes: allow running pre-prepared host CLI's for artifacts that require aggregation artifacts/cli: introduce CLI command artifact-config-dump-json (alias to artifact, but sets CONFIG_DEFS_ONLY=yes) if CONFIG_DEFS_ONLY during obtain_complete_artifact(), just dump JSON to stdout after calculating version/coordinates don't prepare ORAS tooling if CONFIG_DEFS_ONLY don't run in standard build (and thus don't prepare_host()) if under CONFIG_DEFS_ONLY if CONFIG_DEFS_ONLY, don't run check_basic_host() extensions/grub: use array for pkg list also for the media-sbc clone patching: python: useful debug log with value of BASE_GIT_TAG extensions: don't export, declare -g bsp-cli/distro-agnostic: introduce KEEP_ORIGINAL_OS_RELEASE=yes so Debian/Ubuntu PRETTY_NAME is left unchanged in /etc/os-release useful when downstream software wants exact Debian OS (eg: Home Assistant Supervised) View the full article