RSS Bot

Boufallo Lab BL616/BL618 is a 32-bit RISC-V wireless microcontroller with support for 2.4 GHz WiFi 6, Bluetooth 5.2 dual-mode, and an 802.15.4 radio for Zigbee, Thread, and Matter designed for IoT applications. We first spotted the BL616 RISC-V IoT MCU during the BL602/BL606 announcement in November 2020, but we had virtually no additional information about it so far. It appears both BL616 and BL618 will be launched next month with the main difference between the two being that BL616 has 19 GPIOs and BL618 comes with 35 GPIOs. Bouffalo Lab BL616 and BL618 specifications: MCU core – 32-bit RISC-V CPU (RV32GCP) @ up to 384 MHz (datasheet says 320 MHz) with FPU and DSP, 32KB instruction cache & 16KB data cache VPU – MJPEG video encoder Memory – 480KB SRAM, 4KB HBN RAM, embedded 4 or 8MB pSRAM (optional) Storage – 128KB ROM, 4Kb eFuse, embedded 2, 4, or 8MB [...] The post Boufallo Lab BL616/BL618 RISC-V MCU supports WiFi 6, Bluetooth 5.2, and Zigbee appeared first on CNX Software - Embedded Systems News. View the full article

iWave Sytems iW-RainboW-G50M is an NXP i.MX 93 OSM-L compliant LGA module with up to 2GB RAM, WiFi 5 and Bluetooth 5.2 module that is found in the company’s iW-RainboW-G50S Pico-ITX SBC designed for industrial applications. The NXP i.MX 93 single and dual-core Cortex-A55 processor with an Ethos U65 microNPU was announced in November 2021, but we had yet to see any hardware based on the new NXP i.MX 9 processor family. The iW-RainboW-G50M and iW-RainboW-G50S change that with a system-on-module and single board computer. iW-RainboW-G50M NXP i.MX 93 system-on-module Specifications: SoC (one or the other) NXP i.MX 9352 dual-core Cortex-A55 processor @ up to 1.7 GHz with Arm Cortex-M33 @ 250 MHz, 0.5 TOPS NPU NXP i.MX 9351 single-core Cortex-A55 processor @ up to 1.7 GHz with Arm Cortex-M33 @ 250 MHz, 0.5 TOPS NPU NXP i.MX 9332 dual-core Cortex-A55 processor @ up to 1.7 GHz Arm Cortex-M33 @ [...] The post Pico-ITX SBC features NXP i.MX 93 LGA system-on-module appeared first on CNX Software - Embedded Systems News. View the full article

Description The current xradio patch causes the wifi mac address to randomize after every reboot on kernel 5.13+ Modified it to use the updated of_get_mac_address function on kernel 5.13+ and get a stable mac address How Has This Been Tested? Tested patch with 5.15.85 kernel on 3 aw-h6-tv boards. The wifi mac address is now stable/unique and not randomized after every reboot 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 [X] Any dependent changes have been merged and published in downstream modules View the full article

Description This patch breaks Bluetooth. Before patch disable: root@rockpi-4b:~# dmesg | grep -E 'brcm|Blue|ieee' [ 8.488266] Bluetooth: Core ver 2.22 [ 8.488355] Bluetooth: HCI device and connection manager initialized [ 8.488367] Bluetooth: HCI socket layer initialized [ 8.488372] Bluetooth: L2CAP socket layer initialized [ 8.488385] Bluetooth: SCO socket layer initialized [ 8.594739] Bluetooth: HCI UART driver ver 2.3 [ 8.594761] Bluetooth: HCI UART protocol H4 registered [ 8.594766] Bluetooth: HCI UART protocol BCSP registered [ 8.594868] Bluetooth: HCI UART protocol LL registered [ 8.594875] Bluetooth: HCI UART protocol ATH3K registered [ 8.606072] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 8.606460] Bluetooth: HCI UART protocol Intel registered [ 8.608127] Bluetooth: HCI UART protocol Broadcom registered [ 8.608203] Bluetooth: HCI UART protocol QCA registered [ 8.608209] Bluetooth: HCI UART protocol AG6XX registered [ 8.608266] Bluetooth: HCI UART protocol Marvell registered [ 8.705945] brcmfmac: F1 signature read @0x18000000=0x15294345 [ 8.763547] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 [ 8.792519] usbcore: registered new interface driver brcmfmac [ 8.895010] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 [ 8.902046] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Jun 16 2017 12:38:26 version 7.45.96.2 (66c4e21@sh-git) (r) FWID 01-1813af84 [ 9.156475] systemd[1]: Reached target Bluetooth. [ 10.879382] Bluetooth: hci0: command 0x0c03 tx timeout [ 18.911324] Bluetooth: hci0: BCM: Reset failed (-110) [ 119.493183] brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -110 [ 119.493929] brcmfmac: brcmf_sdio_dpc: failed backplane access over SDIO, halting operation After patch disable: root@rockpi-4b:~# dmesg | grep -E 'brcm|Blue|ieee' [ 8.472541] Bluetooth: Core ver 2.22 [ 8.472677] Bluetooth: HCI device and connection manager initialized [ 8.472696] Bluetooth: HCI socket layer initialized [ 8.472706] Bluetooth: L2CAP socket layer initialized [ 8.472724] Bluetooth: SCO socket layer initialized [ 8.666875] brcmfmac: F1 signature read @0x18000000=0x15294345 [ 8.679608] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 [ 8.716907] usbcore: registered new interface driver brcmfmac [ 8.744207] Bluetooth: HCI UART driver ver 2.3 [ 8.744233] Bluetooth: HCI UART protocol H4 registered [ 8.744238] Bluetooth: HCI UART protocol BCSP registered [ 8.744340] Bluetooth: HCI UART protocol LL registered [ 8.744346] Bluetooth: HCI UART protocol ATH3K registered [ 8.744401] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 8.744687] Bluetooth: HCI UART protocol Intel registered [ 8.744930] Bluetooth: HCI UART protocol Broadcom registered [ 8.744988] Bluetooth: HCI UART protocol QCA registered [ 8.744993] Bluetooth: HCI UART protocol AG6XX registered [ 8.745043] Bluetooth: HCI UART protocol Marvell registered [ 8.819294] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9 [ 8.826630] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Jun 16 2017 12:38:26 version 7.45.96.2 (66c4e21@sh-git) (r) FWID 01-1813af84 [ 9.044867] systemd[1]: Reached target Bluetooth. [ 9.132055] Bluetooth: hci0: BCM: chip id 130 [ 9.134426] Bluetooth: hci0: BCM: features 0x0f [ 9.157625] Bluetooth: hci0: BCM4345C5 [ 9.157659] Bluetooth: hci0: BCM4345C5 (003.006.006) build 0000 [ 9.160790] Bluetooth: hci0: BCM4345C5 'brcm/BCM4345C5.hcd' Patch [ 14.345213] Bluetooth: hci0: BCM4345C5 Ampak_CL1 UART 37.4 MHz BT 5.0 [Version: Version: 0039.0089] [ 14.345242] Bluetooth: hci0: BCM4345C5 (003.006.006) build 0089 Also see this MR: https://github.com/armbian/build/pull/4609 and thread on forum: https://forum.armbian.com/topic/24869-bluetoothap6256-with-kernel-6011-dose-not-work/ How Has This Been Tested? [x] Rock Pi 4 Model B 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 [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Banana Pi BPI-Pico-RP2040 is basically a clone of the original Raspberry Pi Pico, but with the addition of an RGB LED and a 4-pin I2C connector, and the company replaced the micro USB port with a Type-C connector. The rest of the board, also called Banana Pi Pico, is exactly the same up to the through holes and castellated holes for the I/Os, and has a similar form factor as the Banana Pi BPI-PicoW-S3 that adds WiFi and Bluetooth through the ESP32-S3 wireless microcontroller. Banana Pi BPI-Pico-RP2040 specifications: MCU – Raspberry Pi RP2040 dual-core Cortex-M0+ microcontroller @ up to 133 MHz with 264KB SRAM Storage – 2MB QSPI flash USB – 1x USB 1.1 Type-C port used for power and programming Expansion 2x 20-pin 2.54mm pitch header and castellated holes with 26 GPIOs, 3x 12-bit ADC up to 500 Kbps, 2x UART, 2x I2C, 2x SPI, 16x PWM, 2x programmable [...] The post Banana Pi BPI-Pico-RP2040 – Raspberry Pi Pico replica gets USB-C port, I2C connector, and RGB LED appeared first on CNX Software - Embedded Systems News. View the full article

Description This code was added to the source data from the kernel version 5.10.x, possibly even earlier. Accordingly, this patch is not needed. https://github.com/torvalds/linux/blob/v5.10/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi#L188 https://github.com/torvalds/linux/blob/v5.15/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi#L189 https://github.com/torvalds/linux/blob/v6.1/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi#L230 Before disable path: &hdmi_sound { status = "okay"; }; &hdmi_sound { status = "okay"; }; After disable path: &hdmi_sound { status = "okay"; }; How Has This Been Tested? [x] Rock Pi 4 Model B 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

DshanMCU Pitaya Lite is an MCU development board based on yet another STM32 alternative: MindMotion MM32 Arm Cortex-M3 microcontroller that is said to be compatible with STM32. The MCU can be clocked at up to 120 MHz, embeds 128KB SRAM, 512KB flash, and the board offers two USB Type-C ports for USB and DAP debugging, a MicroSD card slot, a few buttons, I/Os are routed via through holes as well as a mini PCIe connector that can be used to connect a display. Pitaya Lite specifications: MCU – MindMotion Microelectronics MM32F3273G8P Arm Cortex-M3 microcontroller @ 96MHz (standard) to 120MHz (max) with 128KB SRAM, 512kB Flash; LQFP100 package Storage – MicroSD card Display – Via mini PCIe port with FSMC (Flexible Static Memory Controller), supports Intel 8080 LCDs USB – 2x USB Type-C ports, including one for DAPLink and serial access Expansion – 2x 25-pin GPIO headers and Mini PCIe connector [...] The post $4 DshanMCU Pitaya Lite board comes with MM32 Arm Cortex-M3 microcontroller appeared first on CNX Software - Embedded Systems News. View the full article

In researching a post in the forums, I found that the meson64-edge kernel config doesn't include rtl8822cs (which apparently some TV boxes use). This is enabled in most kernel configs: linux-bcm2711-current.config:CONFIG_RTL8822CS=m linux-bcm2711-edge.config:CONFIG_RTL8822CS=m linux-imx6-current.config:CONFIG_RTL8822CS=m linux-imx6-edge.config:CONFIG_RTL8822CS=m linux-media-current.config:CONFIG_RTL8822CS=m linux-media-edge.config:CONFIG_RTL8822CS=m linux-media-legacy.config:# CONFIG_RTL8822CS is not set linux-meson64-current.config:CONFIG_RTL8822CS=m linux-meson64-edge.config:# CONFIG_RTL8822CS is not set linux-mvebu64-current.config:CONFIG_RTL8822CS=m linux-mvebu64-edge.config:CONFIG_RTL8822CS=m linux-mvebu-current.config:CONFIG_RTL8822CS=m linux-mvebu-edge.config:CONFIG_RTL8822CS=m linux-odroidxu4-edge.config:CONFIG_RTL8822CS=m linux-rk322x-current.config:CONFIG_RTL8822CS=m linux-rk322x-edge.config:CONFIG_RTL8822CS=m linux-rockchip64-current.config:CONFIG_RTL8822CS=m linux-rockchip64-edge.config:CONFIG_RTL8822CS=m linux-rockchip-current.config:CONFIG_RTL8822CS=m linux-rockchip-edge.config:# CONFIG_RTL8822CS is not set linux-rockchip-rk3588-legacy.config:# CONFIG_RTL8822CS is not set linux-sunxi64-current.config:CONFIG_RTL8822CS=m linux-sunxi64-edge.config:CONFIG_RTL8822CS=m linux-sunxi64-legacy.config:CONFIG_RTL8822CS=m linux-sunxi-current.config:CONFIG_RTL8822CS=m linux-sunxi-edge.config:CONFIG_RTL8822CS=m linux-sunxi-legacy.config:CONFIG_RTL8822CS=m linux-uefi-arm64-current.config:CONFIG_RTL8822CS=m linux-uefi-arm64-edge.config:# CONFIG_RTL8822CS is not set linux-uefi-riscv64-current.config:# CONFIG_RTL8822CS is not set linux-uefi-riscv64-edge.config:# CONFIG_RTL8822CS is not set linux-uefi-x86-current.config:CONFIG_RTL8822CS=m linux-uefi-x86-edge.config:CONFIG_RTL8822CS=m This commit enables this for just the meson64-edge kernel as that resolves the issue I was researching, but I suspect it probably should also be enabled for rockchip-edge as well, but I don't have any such devices. On branch rtl8822cs_meson64_edge Changes to be committed: modified: ../kernel/linux-meson64-edge.config Description 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] Successfully built meson64-edge kernel and installed on a box View the full article

SONOFF ZBMINI Extreme (aka ZBMINI-L2) is an ultra-compact Zigbee smart switch that can control home appliances and lights without a neutral wire and can fit into almost any mounting box. The tiny wireless switch can fit into the smallest EU-type/86-type/120-type mounting box, and works with gateways supporting the Zigbee 3.0 protocol such as ZBBridge Pro, NSPanel Pro, SmartThings Hub, Amazon Alexa Echo speaker, and so on. It also supports external switches, voice control, eWelink app control, and other features. SONOFF ZBMINI Extreme (ZBMINI-L2) specifications: MCU – Silicon Labs EFR32MG22 Arm Cortex-M33 @ 76.8 MHz Zigbee microcontroller with up to 512 kB flash, up to 32 kB RAM Connectivity – Zigbee 3.0 Input – 100-240V ~ 56/60Hz 6A Max Output – 100-240V ~ 56/60Hz 6A Max Dimensions – 39.5 x 32 x 18.4mm Casing material – PC V0 As mentioned in the introduction, the SONOFF ZBMINI-L2 does not need a neutral [...] The post SONOFF ZBMINI Extreme tiny Zigbee smart switch does not require a neutral wire appeared first on CNX Software - Embedded Systems News. View the full article

AAEON RTC-710AP is a 7-inch rugged tablet powered by an Intel Celeron N3350 or Pentium N4200 Apollo Lake processor with up to 8GB LPDDR4 memory, 128GB eMMC flash, WiFi, Bluetooth, and optional 4G LTE connectivity. as well as GNSS supports. The IP65-rated tablet also comes with five physical function keys, an NFC reader, a 2MP front-facing camera, an 8MP rear camera, and an I/O expansion module for a 2D barcode scanner, LAN, UART, and other options. It also features a master battery and a hot-swappable slave battery to ensure continuous operation. AAEON RTC-710AP specifications: SoC (one or the other) Intel Celeron N3350 dual-core processor @ 1.1GHz / 2.4GHz with Intel HD Graphics 500; 6W TDP Intel Pentium N4200 quad-core processor @ 1.1GHz / 2.5GHz with Intel HD Graphics 505; 6W TDP Memory – 4GB LPDDR4 (default), up to 8GB as an option Storage 64GB eMMC flash (default), up to 128GB [...] The post AAEON RTC-710AP rugged tablet features hot-swappable battery for continuous operation appeared first on CNX Software - Embedded Systems News. View the full article

Fixes the build of DEB packages after changing files in the shared GIT. Switching the LEGACY kernel from RK BSP 4.4 to RK BSP 5.10. View the full article

Lichee Pi 4A is a single board computer (SBC) powered by Alibaba T-Head TH1520 quad-core RISC-V Xuantie C910 processor @ 1.8 GHz with an Imagination GPU and a 4 TOPS NPU for AI that can compete against the Raspberry Pi 4 in terms of performance and features. We previously mentioned the Lichee Pi 4A (LPi4A) in our article about the Sipeed LM4A RISC-V system-on-module, but at the time we only had some benchmarks for the board and no photos and specifications about the SBC. Sipeed has now released photos and more detailed specifications and is taking “pre-orders”. So let’s have a look. Lichee Pi 4A specifications against the ones for Raspberry Pi 4. The TH1520 used to be advertised at up to 2.5 GHz, but it seems to have now come down to 1.8 GHz. Software support will include Debian, OpenWrt, and Android in Q1 2023, and more operating [...] The post Lichee Pi 4A RISC-V SBC takes on Raspberry Pi 4 with TH1520 processor appeared first on CNX Software - Embedded Systems News. View the full article

Description runs when PR is opened and kernel config is changed it never fails, just making a report adjust run conditions on lint action Jira reference number AR-1457 How Has This Been Tested? [x] Tested in forked branch 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] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Geniatech DS-3566 is a board based on Rockchip RK3566 designed for digital signage applications with a low-profile, multiple video interfaces such as HDMI, LVDS, eDP, and MIPI DSI, and plenty of headers and connectors for expansion. The single board computer ships with up to 8GB RAM, 128GB eMMC flash, and supports Gigabit Ethernet, WiFi 5, Bluetooth 4.1, as well as cellular connectivity as an option. Some of the interfaces available through connectors include RS232, RS485, CAN Bus, I2C, SPI, etc… Geniatech DS-3566 specifications: SoC – Rockchip RK3566 quad-core Arm Cortex-A55 processor @ 1.8 GHz with Arm Mali-G52 EE GPU, 0.8 TOPS NPU System Memory – 2GB to 8GB LPDDR4 Storage – 16GB to 128GB eMMC flash, MicroSD card slot Video Interfaces 1x HDMI 2.1 up to 4Kp60 1x LVDS header and backlight header 1x eDP header and backlight header 1x 4-lane MIPI DSI connector Camera – 1x 4-lane MIPI CSI [...] The post Geniatech DS-3566 digital signage board is powered by a Rockchip RK3566 SoC appeared first on CNX Software - Embedded Systems News. View the full article

Description We need to pre-install the necessary dependencies if the INSTALL_HEADERS=yes key has been selected. We have to pass the architecture value to the "make" command in the kernel header compilation script. Issues reference number #4589 How Has This Been Tested? This is how the log looks with the debug code enabled: For sunxi64: Unpacking linux-headers-current-sunxi64 (23.02.0-trunk) ... Setting up flex (2.6.4-8build2) ... Setting up libssl-dev:arm64 (3.0.2-0ubuntu1.7) ... Setting up bison (2:3.8.2+dfsg-1build1) ... update-alternatives: using /usr/bin/bison.yacc to provide /usr/bin/yacc (yacc) in auto mode Setting up linux-headers-current-sunxi64 (23.02.0-trunk) ... Compiling headers - please wait ... SUBARCH= ARCH=arm64 SRCARCH=arm64 UTS_MACHINE=aarch64 DEB_BUILD_ARCH=amd64 DEB_HOST_ARCH=arm64 Processing triggers for man-db (2.10.2-1) ... It is the same for sunxi. Checklist: [x] Test build image for bananapim3 [x] Test build image for bananapim64 View the full article

Achronix Semiconductor has recently announced the general availability of the Speedster7t AC7t1500 FPGA designed for networking, storage, and compute (AI/ML) acceleration applications. The 7nm Speedster7t FPGA family offers PCIe Gen5 ports and GDRR6 and DDR5/DDR4 memory interfaces, delivers up to 400 Gbps on the Ethernet ports, and includes a 2D network on chip (2D NoC) that can handle 20 Tbps of total bandwidth. Achronix Speedster7t highlights: Two-dimensional network on chip (2D NoC) enabling high bandwidth data flow throughout and between the FPGA fabric and hard I/O and memory controllers and interfaces MLP (Machine Learning Processors) blocks with arrays of multipliers, adder trees, accumulators, and support for both fixed and floating-point operations, including direct support for Tensorflow’s bfloat16 format and block floating-point (BFP) format. Multiple PCIe Gen5 ports High-speed SerDes transceivers, supporting 112 Gbps PAM4 and 56 Gbps PAM4/NRZ modulation, as well as lower data rates Hard Ethernet MACs that support [...] The post Achronix Speedster7t AC7t1500 FPGA is now available for high-bandwidth applications appeared first on CNX Software - Embedded Systems News. View the full article

Bumps ossf/scorecard-action from 2.1.0 to 2.1.2. Release notes Sourced from ossf/scorecard-action's releases. v2.1.2 What's Changed Fixes 🌱 Bump scorecard dependency to v4.10.2 to remove a CODEOWNERS printf statement. by @​spencerschrock in ossf/scorecard-action#1054 Full Changelog: https://github.com/ossf/scorecard-action/compare/v2.1.1...v2.1.2 v2.1.1 Scorecard version This release use Scorecard's v4.10.1 Full Changelog: https://github.com/ossf/scorecard-action/compare/v2.1.0...v2.1.1 Commits e38b190 Bump docker tag for release. (#1055) 7da02bf Bump scorecard to v4.10.2 to remove a CODEOWNERS printf statement. (#1054) 013c0f8 :seedling: Bump actions/dependency-review-action from 3.0.1 to 3.0.2 f93c094 :seedling: Bump github/codeql-action from 2.1.36 to 2.1.37 ce8978e :seedling: Bump actions/upload-artifact from 3.1.0 to 3.1.1 5ce49db :seedling: Bump actions/setup-go from 3.4.0 to 3.5.0 15c10fc Update tag to v2.1.1 (#1047) f96da1a :seedling: Update scorecard for the panic (#1045) 813a825 Complete the list of required actions (#1044) be62ea8 Update RELEASE.md (#1042) Additional commits viewable in compare view Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase. Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: @dependabot rebase will rebase this PR @dependabot recreate will recreate this PR, overwriting any edits that have been made to it @dependabot merge will merge this PR after your CI passes on it @dependabot squash and merge will squash and merge this PR after your CI passes on it @dependabot cancel merge will cancel a previously requested merge and block automerging @dependabot reopen will reopen this PR if it is closed @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) View the full article

Description When having a more complex setup, we might need to look route to get a primary device. Jira reference number AR-1450 https://github.com/armbian/build/pull/4610 How Has This Been Tested? [x] Manual run Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description I have a number of other single board computers that are connected to a kubernetes cluster running Longhorn for storage. I want to be able to add my new Rock 5B to the same cluster. I quickly found that the kernel doesn't have support for ISCSI_TCP. This support was added for all other boards in https://github.com/armbian/build/pull/2300. How Has This Been Tested? I built a custom kernel with this configuation using ``` ./compile.sh RELEASE=bullseye BOARD=rock-5b BRANCH=legacy BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=yes KERNEL_CONFIGURE=no I then installed the image and headers packages sudo dpkg -i linux-image-legacy-rockchip-rk3588_23.02.0-trunk_arm64.deb sudo dpkg -i linux-headers-legacy-rockchip-rk3588_23.02.0-trunk_arm64.deb Finally I installed open-iscsi sudo apt install open-iscsi # Checklist: - [ ] 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 We are using this: PRIMARY_INTERFACE="$(ls -1 /sys/class/net/ | grep -v lo | egrep "enp|eth" | head -1)" to detect primary interface. Sometimes it doesn't find proper one. This add additional check. Before: System load: 5% Up time: 11 minLocal users: 2 Memory usage: 14% of 982M IP: 10.0.30.126 CPU temp: 35°C Usage of /: 11% of 28G RX today: Error: No interface matching "--oneline" found in database. After: System load: 5% Up time: 15 minLocal users: 2 Memory usage: 14% of 982M IP: 10.0.30.126 CPU temp: 34°C Usage of /: 11% of 28G RX today: 62.0 MiB Jira reference number AR-1450 How Has This Been Tested? [ ] Manual 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

Description Bluetooth on PBP is currently broken and this might fix it. No hw to test but: https://github.com/armbian/build/pull/4608#issuecomment-1364484639 View the full article

Description nanopct4 rt5651 sound repeat pinctrl cause problem [ 7.395164] rockchip-pinctrl pinctrl: pin gpio4-0 already requested by ff880000.i2s; cannot claim for 1-001a [ 7.395192] rockchip-pinctrl pinctrl: could not request pin 128 (gpio4-0) from group i2s-8ch-mclk on device rockchip-pinctrl wlan-platdata,bluetooth-platdata is from legacy kernel, it not in mainline kernel (wireless,bluetooth drive by sdio,bluethooth node in dts), now remove it from dts general-add-panel-simple-dsi.patch is a general patch drive DSI lcd display pannel by dts easy, now add this to media edge for some people's need By the way, [board-pbp-fix-wonky-wifi-bt.patch] this patch cause brcm bluetooth problem as follow(I disabled it in test): [ 9.344976] Bluetooth: hci0: command 0xfc45 tx timeout [ 17.376934] Bluetooth: hci0: BCM: failed to write clock (-110) [ 17.377484] Bluetooth: hci0: Failed to set baudrate [ 19.392839] Bluetooth: hci0: command 0x0c03 tx timeout [ 27.616997] Bluetooth: hci0: BCM: Reset failed (-110) How Has This Been Tested? [x] nanopct4 rt5651 sound,wireless,bluetooth normal on linux6.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 [x] Any dependent changes have been merged and published in downstream modules View the full article

Description mipi_dsi_driver adjust function remove return void on linux6.1 (this patch also add new: orientation custom, reset level custom) How Has This Been Tested? [x] product panel_simple_dsi.ko on linux6.1 and drive my dsi lcd normal 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

M5Stack T-Lite is a Wi-Fi thermal imager with the same MLX90640 IR array thermal camera found in the M5Stack Thermal Camera 2 Unit plus a 1.14-inch color display to visualize the results on the device itself. Based on the ESP32-PICO-D4 system-in-package with WiFi and Bluetooth, the solution allows the user to access the 32×24 pixels thermal image either on the built-in display, or streamed to the local network or the cloud. M5Stack T-Lite specifications: SiP – ESP32-PICO-D4 system-in-package with ESP32 dual-core Tensilica LX6 microcontroller with 448 KB ROM and 520 KB SRAM, 2.4 GHz WiFi 4 and Bluetooth 4.2, and a 4MB SPI flash Thermal camera – Melexis MLX90640 infrared (IR) sensor with 32×24 pixels IR array, range: -40°C to 300°C with +/-1.5°C resolution, FoV: 110°x75° (See datasheet) Display – 1.14 inch color TFT LCD with 240×135 resolution, ST7789v2 driver Expansion – 4-pin Grove HY2.0-4P interface (“Port A”) with I2C, [...] The post M5Stack T-Lite Wi-Fi thermal camera integrates 1.14-inch color display appeared first on CNX Software - Embedded Systems News. View the full article

Description Support for mainline for Rock 5B. Currently working is just EMMC. There is also ethernet support, but rock 5b uses PCIe for ethernet. How Has This Been Tested? Booted my Rock 5B fine, but have no EMMC, so the init could not mount the root drive. If someone can help with the testing... 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 [ x] My changes generate no new warnings [ x] Any dependent changes have been merged and published in downstream modules View the full article