RSS Bot

…indicate the installation occurs on host not in container. 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? removed uuid package, ran ./compile.sh docker-shell RELEASE=jammy BOARD=rockpro64 BRANCH=edge output was [ .... ] Updating and installing basic packages on host [ uuid uuid-runtime ] Selecting previously unselected package uuid. (Reading database ... 391502 files and directories currently installed.) Preparing to unpack .../uuid_1.6.2-1.5build7_amd64.deb ... Unpacking uuid (1.6.2-1.5build7) ... Setting up uuid (1.6.2-1.5build7) ... Processing triggers for man-db (2.9.1-1) . 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 Improving Allwinner u-boot patches maintainability. Jira reference number AR-1389 On halfway done: Before: https://github.com/armbian/build/tree/master/patch/u-boot/u-boot-sunxi After: https://github.com/armbian/build/tree/AR-1389/patch/u-boot/u-boot-sunxi @150balbes When this step is done, we can discuss other variants. I expect to need another 2-3h to get this done alongside with build testings. How Has This Been Tested? [ ] Build all u-boots for boards that has been altered 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 Add meson-gx mmc driver patches for use phase clock settings from dts add read amlogic,mmc-phase values from dts files update meson-axg.dtsi to use 270, 0, 0 phases disable old patch for axg phase change to 270 Jira reference number AR-1394 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] JetHub J100 (axg) boots ok [X] JetHub J80 (gxl) boots ok View the full article

Making our grand debut, Collabora will be attending electronica in Munich for the first time! Diving into the world of electronics alongside the leading examples of the industry, we're excited to partake on all fronts. View the full article

build work for kernel 6.0 View the full article

Info name patch https://github.com/armbian/build/pull/4404 View the full article

No descriptionView the full article

Weibu is a B2B company offering total solutions and OEM/ODM services. Their target clients are computer manufacturers like Acer and Hisense as they don’t sell directly to end users. With their products both the specifications and accessories can be customized according to their customer’s requirements. One of their product lines is mini PCs and they have sent a pre-production sample of their N10 design to showcase their capabilities. In this review, I will look at the various options available for the N10 and briefly look at performance running both Windows and Ubuntu. Weibu N10 hardware overview The key selling feature of this mini PC is the wide range of ports suitable for commercial/industrial usage together with various options for the processor. The N10 is an actively cooled mini PC and the device is 145 x 128 x 54mm (5.71 x 5.04 x 2.13 inches) large with a metal top that [...] The post Weibu N10 Review – An OEM Mini PC tested with Ubuntu 22.04, Windows 11 appeared first on CNX Software - Embedded Systems News. View the full article

MediaTek has just launched the Dimensity 9200 octa-core flagship 5G mobile processor with one Cortex-X3 core, two Cortex-A710 cores, and four Cortex-A510 cores, as well as the latest Arm Immortalis-G715 GPU. Manufactured for a TSMC 4nm processor for efficiency, the new flagship processor supports mmWave 5G and sub-6GHz cellular connectivity, LPDDR5x 8,533 Mbps memory, UFS 4.0 storage, and embeds a faster MediaTek APU 690 AI processor MediaTek Dimensity 9200 specifications: Octa-core CPU subsystem 1x Arm Cortex-X3 core at up to 3.05 GHz 3x Arm Cortex-A710 cores at up to 2.85 GHz 4x Arm Cortex-A510 cores up to 1.80GHz 8MB L3 cache 6MB system cache GPU – Arm Immortalis-G715 with support for Vulkan 1.3, hardware-based ray tracing engine AI Accelerator – MediaTek APU 690 AI processor with MDLA (MediaTek Deep Learning Accelerator), MVPU (MediaTek Vision Processing Unit), SME (I don’t know what that is), and DMA Memory I/F – LPDRR5x 8,533 [...] The post MediaTek unveils Dimensity 9200 Octa-core Cortex-X3/A710/A510 5G mobile processor appeared first on CNX Software - Embedded Systems News. View the full article

Changes in the name of patch files. two mandatory fields are used - a digital index that strictly fixes the position of the patch during the overlay process, the last character in the initial state is 0, this will allow you to add new patches to the right place at any time without having to rename all patches. The second required field is the name (nickname) of the user on GIT who added (is responsible for supporting) this patch in the build system. The rest of the patch file name is at the discretion of the person who adds it and it is desirable to have a description of the purpose of the patch. Please note that this name is not synonymous with the one who CREATED the patch, it is the name of the one who ADDED it to the build system. Using this field, it will be easy to find (notify) the maintainer of this patch in case of problems with its imposition during the operation of the build system. In the future, this will allow you to immediately automatically send a notification to the patch maintainer if the patch causes problems (cannot be properly applied). Thus, each patch that is added to the build system will have an author (maintainer) who is responsible for this patch. I propose to extend this format to all patches in the build system. View the full article

The fourth prize of Giveaway Week 2022 is the Sonoff NSPanel Pro control panel with four Zigbee modules including a temperature & humidity sensor, a door/window sensor, a switch, and a PIR motion sensor. The controller is based on a Rockchip PX30 quad-core Cortex-A35 processor running Android 8.1 and acts as a Zigbee 3.0 gateway allowing users to add all sorts of Zigbee modules. It also works with the eWelink app to add security cameras which can be some of your old smartphones. We reviewed the SONOFF NSPanel Pro control panel & Zigbee gateway last month together with Zigbee modules and the SONOFF Slim Cam indoor security camera and found it worked reasonably well, although some advanced features required us to use the eWelink app in our phones instead of the touchscreen on the display. We also found one bug with the Zigbee switch that the company promised to fix [...] The post Giveaway Week 2022 – Sonoff NSPanel Pro and Zigbee modules appeared first on CNX Software - Embedded Systems News. View the full article

Description Since upgrading u-boot on sunxi to 2022.07 we lost key mapping for breaking the boot sequence. The former working patch has been updated to work for U-Boot v2022.07 now again to let U-Boot Autoboot being interrupted by pressing the -key as it was working for U-Boot 2021.10 before. This fix resolves Jira reference number AR-1322 Tested: [x] The current Armbian build includes the patch with success [x] Tested booting a Cubietruck board 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

This fix is provided by mainline U-Boot since v2022.10. For any details refer to: https://github.com/u-boot/u-boot/commit/5fd30ed78539e11c2c155001a88f483441a96ebd fixes #4401 Tested: [x] Current Armbian build includes the patch with success [x] Has been tested on a Cubietruck board 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 (s. U-Boot mainline reference above) [ ] 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

The Brume 2 security gateway/router is powered by a MediaTek MT7981B (Filogic 820) dual-core processor @ 1.3 GHz and is available as the GL-MT2500A with a metal enclosure or the GL-MT2500 with a plastic case. GL.iNet sent me the GL-MT2500A for review. In the first of the review, we’ll have a look at the device and accessories, and tear it down to check out the hardware design and main components. I’ll then need some time to test OpenWrt 21.02 and features such as WireGuard and OpenVPN, AdGuard Home, Tor Anonymity, and soon. GL.iNet GL-MT2500A (Brume 2) unboxing The router ships with a short Ethernet cable, a 5V/2A USB Type-C power supply with EU, US, and UK plug adapters, and some minimal documentation that points to the users to more detailed online documentation and support on the company’s Facebook page. There’s not much too see on the front panel and right [...] The post GL.iNet GL-MT2500A security gateway review – Part 1: Unboxing and teardown appeared first on CNX Software - Embedded Systems News. View the full article

Description Jira reference number AR-1393 How Has This Been Tested? [x] Build test 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

The third prize of this year’s giveaway week comes courtesy of ELECFREAKS which offers a Cutebot Pico:ed kit based on the Pico:ed board with a Raspberry Pi RP2040 microcontroller and following BBC Micro:bit form factor. The kit also includes two high-speed motors to drive two wheels, ultrasonic & distance sensors, two RGB LED lights and clearance lamps on the bottom, two line-tracking probes, and an active buzzer used as a horn. It is powered by three AAA batteries. The company initially me asked me if I wanted to review the board/robot, but since I may not have the time to do so, I asked whether they wanted to be included in our yearly giveaway week which they accepted. The company provides instructions to program the robot with “Micro block” visual programming IDE, C++, and CircuitPython. You’ll find resources to get started and eight projects for the robot in the Wiki. [...] The post Giveaway Week 2022 – Pico:ed Smart Cutebot Kit appeared first on CNX Software - Embedded Systems News. View the full article

AXERA AX620A is a high-performance, low-power AI SoC with a quad-core Arm Cortex-A7 processor and a 14.4TOPs @ INT4 or 3.6TOPs @ INT8’s NPU that is slightly inferior to the Amlogic A311D, and mainly used for AI vision applications. With high computing power and built-in image processing capabilities, the AX620A can support a wide range of AI workloads. It also offers low power consumption with low standby power and fast wake-up, so the chip can be integrated into battery-powered products. AXERA AX620A specifications: CPU – Quad-core Arm Cortex-A7 @ 1.0 GHz with 32KB L1 I-cache + 32KB L1 D-cache per core, 256KB L2 cache, FPU and NEON NPU – 4 TOPS @ INT4, 3.6 TOPS @ INT8 with support for Imagenet, AlexNet, VGG, ResNet, GoogLeNet, Faster R-CNN, SSD, FPN, Yolo V3, and other neural networks. ISP Proton AI-ISP up to 4Kp30 4 channels of camera support up to 4x 1080p30 Support [...] The post AXERA AX620A 4K AI SoC delivers up to 14.4 TOPS for computer vision applications appeared first on CNX Software - Embedded Systems News. View the full article

Description Setting the display mode in armbianEnv.txt no longer worked, probably because it used an old, sunxi-specific interface. See the commit message (also shown below) for details about this. I'm marking this as draft, because: I'm not sure if we should reuse the disp_mode variable, or maybe use a different name (video_mode?) to make it clearer that the values it accepts are of a slightly different format (would also help to see that older documentation does not apply to this option). This fixes just sunxi, which I've been able to test only on a single board (Orange Pi PC). I'm not sure if similar changes are needed elsewhere (see last point in commit message). 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] Run original image for Orange Pi PC, set disp_mode=1280x720p60 and see that the monitor input stays at the default 1920x1080. [x] Run the modified image for Orange Pi PC, set disp_mode=1280x720p60 and see that the monitor input changes to 1280x720 as expected. 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 - seems disp_mode is not really documented? [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules N/A Commit message: The disp_mode variable can be set in armbianEnv.txt and boot-sunxi.cmd (boot.scr on the final image) takes care of putting its value in the disp.screen0_output_mode variable on the kernel commandline. However, it seems that this variable is no not actually used by the kernel, probably because it applied to the sunxi video driver from the sunxi-3.x legacy kernels. On newer kernels, it seems that the standard way to force drm/kms to use a specific mode is through the "video=" kernel argument, as documented here: https://wiki.archlinux.org/title/kernel_mode_setting#Forcing_modes This commit adopts to this new way, by updating the boot script to pass the disp_mode variable to the kernel's video= parameter now. Some additional notes: The format of the variable did slightly change, exchanging the "p" for progressive with an @ to indicate the refresh rate, and the video= parameter also allows some additional details (like specifying a specific video connect, bit depth and other info). This means that existing configs are not going to end up work as-is (tried, didn't work), but that seems ok. This comments out the forced 1920x1080 mode (and removes it from the boot script), leaving the default to just autodetect the resolution (which is already the current behavior, given the old option did not work). This also removes the hdmi.audio option from the commandline, which was probably also specific to the old video driver (without it HDMI audio still works normally on an Orange Pi PC). Note that the mode passed to video= is actually added to the list of supported modes (from EDID) as a userdef mode (shown in drm_info output), possibly replacing an existing mode, or adding a new mode if the display does not advertise support for it (no guarantee that the display can actually use the mode, of course). All current sunxi kernel branches, including legacy, seem to use mainline kernels now, so supporting the old way of setting the video mode should no longer be needed. The old "disp.screen0_output_mode" commandline is still used by nfs-boot.cmd.template and the armbian-install and nand-sata-install commands. Additionally, the screenx_output_mode variable is also still used by various (mostly sun50i) DTS files and FEX scripts. These might need a similar treatment, but I cannot oversee the consequences (and have no hardware to test). View the full article

Without this, when mkimage fails (for example because the boot partition is too small), install.log shows an error like: mkimage: Write only 16310208/17794920 bytes, probably no space left on the device But this does not terminate the build, so the compile script shows no error and an image is generated, but it is unbootable. This runs the script with -e, so when mkimage fails, the script fails, which makes update-initramfs fail, which makes the build fail. 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 image for Orange Pi PC with BOOTFS_TYPE="fat" and BOOTSIZE="64" to generate a separate boot partition that is just big enough for the regular initrd, but too small to also contain the uInitrd. Check that this build fails. [x] Build same image, but with BOOTSIZE="96" and check that the build completes and starts. 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 [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules N/A View the full article

Description 33% probability of showing, just like for the armbian-config How Has This Been Tested? ___ ____ _ _ _ / _ \| _ \(_) | || | | | | | |_) | | | || |_ | |_| | __/| | |__ _| \___/|_| |_| |_| Welcome to Armbian 22.11.0-trunk Jammy with Linux 5.15.76-rockchip64 No end-user support: built from trunk System load: 2% Up time: 2:03 Memory usage: 4% of 3.77G IP: 10.0.30.157 CPU temp: 50°C Usage of /: 12% of 15G RX today: 4.0 GiB Tip of the day: do u want 2 use armbian powered snap-free Intel / AMD build? https://www.armbian.com/uefi-x86/ [ 1 security updates available, 1 updates total: apt upgrade [ General system configuration (beta): armbian-config ] 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

ODROID-N2L SBC is a smaller and cheaper version of the ODROID-N2+ single board computer powered by an Amlogic S922X hexa-core Cortex-A73/A53 processor and offered with 2GB or 4GB single-chip LPDDR4X memory. While the ODROID-N2+ is the most popular board from Hardkernel, it’s also fairly larger than most hobbyist SBCs on the market, and following requests from customers, the company designed the ODROID-N2L with a compact form factor that is smaller than Raspberry Pi Model B SBCs and sold at a lower price at the cost of missing some of the features of its big brother. ODROID-N2L specifications: SoC – Amlogic S922X hexa-core big.LITTLE processor with 4x Arm Cortex A73 cores @ up to 2,208/2,400 MHz, 2x Arm Cortex A53 cores @ 1,908/2,016GHz, Arm Mali-G52 GPU @ 846MHz; 12nm manufacturing process System Memory – 2GB or 4GB LPDDR4 @ 3216 MT/s Storage – eMMC flash module socket up to 128GB, microSD [...] The post ODROID-N2L is a smaller, low-cost variant of ODROID-N2+ Arm SBC appeared first on CNX Software - Embedded Systems News. View the full article

T8-Pro is a low-cost mini PC powered by an Intel Celeron N5095 Jasper Lake processor that offers features such as triple 4K HDMI output and dual Gigabit Ethernet usually found in more expensive models for the industrial/embedded market. The actively-cooled mini PC is equipped with 8GB RAM and an M.2 2242 SSD of 128GB to 1TB capacity. It also comes with a WiFi 5 and Bluetooth 4.2 module, three USB 3.0 ports, and a 3.5mm audio jack. T8-Pro mini PC specifications: SoC – Intel Celeron N5095 quad-core Jasper Lake processor @ 2.0GHz / 2.9GHz (Turbo) with 4MB cache, 16EU Intel UHD Graphics; 15W TDP System Memory – 8GB LPDDR4X (Up to 16GB, but not offered for sale) Storage – 128GB to 1TB M.2 2242 NVMe SSD Video Output – 3x HDMI 2.0 ports up to 4Kp60 Audio – 3.5mm audio jack (headphone & microphone) jack, digital audio via HDMI Connectivity [...] The post T8-Pro Celeron N5095 mini PC offers triple HDMI output, dual Gigabit Ethernet appeared first on CNX Software - Embedded Systems News. View the full article

Today, we’re giving away the e-con Systems e-CAM20_CURB is a 2.3MP color camera with a global shutter that is designed to work with Raspberry Pi 4 SBC. The camera is based on ON Semiconductor AR0234CS CMOS sensor and supports uncompressed video at 1920 x 1200 (2.3MP) up to 60 fps, 1920 x 1080 (Full HD) up to 65 fps, and 1280 x 720 (HD) up to 120 fps. I just completed the e-CAM20_CURB camera review with Raspberry Pi 4 last weekend and found the video smoothness and quality to be much better than most cameras I’ve tried when there is motion, even in relatively dark scenes, since motion blur and artifacts are reduced. The company provides Yocto Linux and Raspbian/Raspberry Pi OS images with V4L2 drivers and Gstreamer tools, and the camera was fairly easy to use with the Yocto image thanks to the useful documentation provided with the kit. [...] The post Giveaway Week – e-con Systems e-CAM20_CURB camera appeared first on CNX Software - Embedded Systems News. View the full article

4K HDMI to USB 3.0 dongles based on Macrosilicon MS2130 video and audio acquisition chip are starting to show up on Aliexpress for around $19 with free shipping. We first discovered the MS2130 chip in the YuzukiLOHCC PRO open-source hardware board that claims to have a bills-of-material cost of about $10. But you have to build it and source the components yourself, so it’s not for everyone. Now USB 3.0 adapters capable of recording or streaming up to 1080p60 uncompressed video from an HDMI input up to 4Kp30 are available to anyone with around $20. “Mini U3” HDMI to USB 3.0 video capture dongle specfications: Main chip – MacroSilicon/UltraSemi MS2130 USB 3.2 Gen 1 high-definition video and audio acquisition chip HDMI input up to 4Kp30, 24/30/36-bit depth color Video Output up to 1080p60 in YUV or JPEG output format Audio – L-PCM codec Input cable length – Up to 15 [...] The post MS2130 based “4K” HDMI to USB 3.0 video capture dongle sells for $19 appeared first on CNX Software - Embedded Systems News. View the full article

Nicolai Electronics’ rp2040-ic2-interface open-source firmware for the Raspberry Pi Pico (or other Raspberry Pi RP2040 boards) converts the board into an I2C to USB bridge to connect any I2C sensor or module to a PC or other hardware without GPIOs. The firmware implements the USB protocol expected by the I2C-Tiny-USB kernel driver used by the original I2C-Tiny-USB project for Microchip ATMega 8-bit AVR microcontrollers. The RP2040 is however not a fork of the original project, but instead a complete re-implementation of the firmware. You’ll need to connect your I2C sensor, display, or another module to the SDA (GPIO 2) and SCL (GPIO 3) pins of the Raspberry Pi RP2040 microcontroller and flash the “pre-release” firmware to the board. You’ll find it together with the source code written in C language on GitHub. Note the project has a “proof of concept status” and more testing is needed to make sure that [...] The post RP2040 firmware converts Raspberry Pi Pico into a an I2C to USB bridge appeared first on CNX Software - Embedded Systems News. View the full article