RSS Bot

Spring is in bloom in the northern hemisphere, and with it comes three tech events we'll be attending - PyCon US, Shell & Display Next Hackfest, and Linaro Connect! View the full article

The 100ASK-V853-Pro board is a development kit consisting of an Allwinner V853 system-on-module board (SoM) and a feature-rich carrier board with a large number of interfaces. Allwinner V853 supports up to 1TOPS of NPU computing power and is mainly for AI vision application development. The core board contains a DDR and eMMC as well as a PMU chip (AXP2101) and is connected to the carrier board through a board-to-board connector. All the functional resources of the V853 are drawn out through the carrier board. The carrier board comes with 2-channels CSI camera interfaces as well as RGB and MIPI DSI display interfaces. Although 1 TOPS of AI computing power is not outstanding, the NPU can still be used to accelerate AI vision applications at the edge. The board also comes with four USB 2.0 ports (two Type-A, two Type-C), an 100Mbps Ethernet port, a 22-pin header for expansion, and five [...] The post 100ASK-V853-Pro – A feature-rich Allwinner V853 board designed for AI vision applications appeared first on CNX Software - Embedded Systems News. View the full article

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

Description There are several small problems / corner cases that needs to be addressed. Any help is appriciated. 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

Description When we try to install a new kernel. All files under /boot will be removed. This PR will keep them until the special version kernel was removed. How Has This Been Tested? Need to be tested on other devices. [ ] Test A [ ] Test B Checklist: [ ] 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

AAEON BOXER-8224AI is a thin and lightweight AI edge embedded system solution based on NVIDIA Jetson Nano system-on-module and designed for drones, or other space-constrained applications such as robotics. AAEON BOXER products are usually Embedded Box PCs with an enclosure, but the BOXER-8224AI is quite different as it’s a compact and 22mm thin board with MIPI CSI interfaces designed to add computer vision capability to unmanned areal vehicles (UAV), as well as several wafers for dual GbE, USB, and other I/Os. BOXER-8224AI specifications: AI Accelerator – NVIDIA Jetson Nano CPU – Arm Cortex-A57 quad-core processor System Memory – 4GB LPDDR4 Storage Device – 16GB eMMC 5.1 flash Dimensions – 70 x 45 mm Storage – microSD slot Display Interface – 1x Mini HDMI 2.0 port Camera interface – 2x MIPI CSI connectors Networking 2x Gigabit Ethernet via wafer connector (1x NVIDIA, 1x Intel i210) Optional WiFi, Bluetooth, and/or cellular connectivity [...] The post AAEON BOXER-8224AI – An NVIDIA Jetson Nano AI Edge embedded system for drones appeared first on CNX Software - Embedded Systems News. View the full article

Description After today's complete stall of primary Ubuntu infrastructure I switched to mirrors in order to rebuild caches. First problem is that often mirrors for amd64 and others are placed on different locations. This part is covered but it fails for riscv64 architecture. In order to cover that too, its better to have more generic variable CUSTOM_UBUNTU_MIRROR_PORTS and have everything that is not amd64 there. By quick research - if mirror hosts arm64 it also hosts risv64 and vice versa. Second problem - if caches are re-generated with 3rd party mirrors, release lists remain with those values. How to approach to that problem? We want that - at least our builds - are always shipped with generic entries. How Has This Been Tested? [ ] Generated rootfs with two mirrors that are fast in EU: CUSTOM_UBUNTU_MIRROR_PORTS="ftp.tu-chemnitz.de/pub/linux/ubuntu-ports/" CUSTOM_UBUNTU_MIRROR="mirrors.dotsrc.org/ubuntu/" 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

EVerest is a software project initiated by PIONIX GmbH, but now part of the Linux Foundation’s LFEnergy initiative, whose primary goal is to develop and maintain an open-source software stack for EV charging infrastructure. EVerest supports multiple standards and it will run on any device from AC home chargers to public DC charging stations. I noticed the EVerest project in an upcoming talk at the Embedded Open Source Summit 2023 entitled ” EVerest: Electric Vehicle Chargers With Open Hardware and Software” and whose abstract reads in part: You will learn how to build your own electric vehicle charger using open hardware designs in combination with the EVerest open-source software stack for EV charging infrastructure. Following a quick introduction to EV charging technology, with explanations of the standards, protocols, and complexities involved, the talk will go into a deep dive into how you can build your own AC charging station. Reference [...] The post EVerest is an open-source software stack for car charging stations appeared first on CNX Software - Embedded Systems News. View the full article

Description https://github.com/armbian/build/pull/4917#issuecomment-1513450111 @prahal 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 ghproxy url is something like https://ghproxy.com/https://gtihub.com/armbian/build, which contains https://gtihub.com. Without this patch git will fetch from https://ghproxy.com/https://ghproxy.com/https://gtihub.com/armbian/build. Just skip modifying the url when ghproxy is set. 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 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

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