Search the Community

Hi, I programmed the latest image Armbian_26.2.0-trunk.197_Beagley-ai_plucky_vendor_6.12.49_minimal.img.xz on my beagle Y AI, and connected the power and HDMI and inserted a Dell USB HID for keyboard and mouse, but in initial boot I am not able to use the keyboard and due to this not able to configure the device. Any help will be appreciated. Thanks, Ankit

Hi folks, I was looking to activate the NPU on my beagley-AI chip, running armbian, and I couldn't find how. This chip as a NPU (AM67A) on the SOC from TexasInstruments (https://api.pageplace.de/preview/DT0400.9783895766572_A50990365/preview-9783895766572_A50990365.pdf). The loading of the NPU seems to have failed: mesg | grep remoteproc [ 8.461511] k3-dsp-rproc 7e000000.dsp: configured DSP for remoteproc mode [ 8.461728] remoteproc remoteproc0: 7e000000.dsp is available [ 8.461868] k3-dsp-rproc 7e000000.dsp: register pm nitifiers in remoteproc mode [ 8.464448] k3-dsp-rproc 7e200000.dsp: configured DSP for remoteproc mode [ 8.465124] remoteproc remoteproc0: Direct firmware load for j722s-c71_0-fw failed with error -2 [ 8.465164] remoteproc remoteproc0: powering up 7e000000.dsp [ 8.465271] remoteproc remoteproc0: Direct firmware load for j722s-c71_0-fw failed with error -2 [ 8.465285] remoteproc remoteproc0: request_firmware failed: -2 [ 8.480524] remoteproc remoteproc1: 7e200000.dsp is available [ 8.480658] k3-dsp-rproc 7e200000.dsp: register pm nitifiers in remoteproc mode [ 8.482329] remoteproc remoteproc1: Direct firmware load for j722s-c71_1-fw failed with error -2 [ 8.482375] remoteproc remoteproc1: powering up 7e200000.dsp [ 8.482488] remoteproc remoteproc1: Direct firmware load for j722s-c71_1-fw failed with error -2 [ 8.482501] remoteproc remoteproc1: request_firmware failed: -2 [ 8.964763] platform 79000000.r5f: configured R5F for remoteproc mode [ 9.047514] remoteproc remoteproc2: 79000000.r5f is available [ 9.048055] remoteproc remoteproc2: Direct firmware load for j722s-mcu-r5f0_0-fw failed with error -2 [ 9.048099] remoteproc remoteproc2: powering up 79000000.r5f [ 9.048222] remoteproc remoteproc2: Direct firmware load for j722s-mcu-r5f0_0-fw failed with error -2 [ 9.048241] remoteproc remoteproc2: request_firmware failed: -2 [ 9.234391] remoteproc remoteproc3: 78000000.r5f is available [ 9.234578] remoteproc remoteproc3: attaching to 78000000.r5f [ 9.402138] remoteproc remoteproc3: remote processor 78000000.r5f is now attached [ 9.505240] platform 78400000.r5f: configured R5F for remoteproc mode [ 9.547946] remoteproc remoteproc4: 78400000.r5f is available [ 9.548359] remoteproc remoteproc4: Direct firmware load for j722s-main-r5f0_0-fw failed with error -2 [ 9.548400] remoteproc remoteproc4: powering up 78400000.r5f [ 9.548505] remoteproc remoteproc4: Direct firmware load for j722s-main-r5f0_0-fw failed with error -2 [ 9.548521] remoteproc remoteproc4: request_firmware failed: -2 [ 15.281722] Modules linked in: algif_aead rpmsg_ctrl rpmsg_char cc33xx mac80211 libarc4 snd_soc_simple_card cc33xx_sdio snd_soc_simple_card_utils crct10dif_ce panel_simple pci_endpoint_test e5010_jpeg_enc cpufreq_dt pvrsrvkm(O) pwm_fan at24 rti_wdt cfg80211 ti_k3_r5_remoteproc btti_uart bluetooth snd_soc_davinci_mcasp snd_soc_ti_udma wave5 rpi_panel_attiny_regulator snd_soc_ti_edma snd_soc_hdmi_codec snd_soc_ti_sdma videobuf2_dma_contig v4l2_mem2mem videobuf2_memops videobuf2_v4l2 videobuf2_common snd_soc_core snd_pcm_dmaengine tc358762 snd_pcm videodev ti_k3_dsp_remoteproc ti_k3_common mc snd_timer snd omap_mailbox optee_rng efi_pstore nfnetlink [ 15.285991] Modules linked in: algif_aead rpmsg_ctrl rpmsg_char cc33xx mac80211 libarc4 snd_soc_simple_card cc33xx_sdio snd_soc_simple_card_utils crct10dif_ce panel_simple pci_endpoint_test e5010_jpeg_enc cpufreq_dt pvrsrvkm(O) pwm_fan at24 rti_wdt cfg80211 ti_k3_r5_remoteproc btti_uart bluetooth snd_soc_davinci_mcasp snd_soc_ti_udma wave5 rpi_panel_attiny_regulator snd_soc_ti_edma snd_soc_hdmi_codec snd_soc_ti_sdma videobuf2_dma_contig v4l2_mem2mem videobuf2_memops videobuf2_v4l2 videobuf2_common snd_soc_core snd_pcm_dmaengine tc358762 snd_pcm videodev ti_k3_dsp_remoteproc ti_k3_common mc snd_timer snd omap_mailbox optee_rng efi_pstore nfnetlink The usual lspci doesn't contain much: lspci 00:00.0 PCI bridge: Texas Instruments Device b010 How should I proceed to make it work? Thanks!

Hi, I wanted to report an issue with the currently available Armbian images for the PocketBeagle 2 (all of them from what I can tell), that stops them from booting up. I attempted to go through the bug reporting form, but it seems to only point you to the forum, so here I am. I couldn't find a location to post about the PocketBeagle 2 board specifically, so I am putting this under the Beagle Y board (they have the same maintainer listed). Please move this to the right place (or maybe create it if it doesn't exist?) or tell me how I should do this myself. The issue is in the file "/boot/extlinux/extlinux.conf", where a ".dts" file is being referenced from the directory "/boot/dtb/ti/", which contains only ".dtb" files. U-Boot fails to find the device tree file and fails to boot. Changing the file extension of the device tree in "extlinux.conf" to ".dtb" fixes the boot up issue and everything else seems to be working fine. If this is not the right place to be reporting this issue, please direct me to the correct place, so this can be brought to the attention of the appropriate maintainer. It should be a quick fix, but the images currently available to download are likely unusable for inexperienced users. Many Thanks, Paul

I'm thinking of getting https://www.beagleboard.org/boards/beagley-ai I see there is this page for it https://www.armbian.com/beagley-ai/ I also see references to it in the code: https://github.com/search?q=org%3Aarmbian+beagley&type=code Are there any pre-built images available for it? Or would I have to build one?