All Activity

I got into the same situation - I recorded my test u-boot in MTD and got a brick. I managed to restore the startup - close the lower right contact (5) to the ground and turn on the power (an SD card with a working system is connected). When the output appears on the UART, the contacts are released. After starting the system, immediately erased MTD (dd if=dev/zero of=/dev/mtdblock0). Question - who has information about the u-boot structure for MTD in OPI5?

@roykWell done! I've just uploaded a new version of ffmpeg to my ppa.

Those builds are at least daily. We keep last 32 releases as makes little point in keep them all ... I changed link to release download page.

@amazingfate HDR problem is solved by https://github.com/JeffyCN/FFmpeg/commit/2e578b9ce6f46c4e2ab7f5bc3e066a7be1d586bc

Thanks, I will try this image in the next days.

https://linux-hardware.org/?id=usb:148f-5370 check if modules are present in kernel config.

https://forum.armbian.com/terms

Machine model: Banana Pi M2 Berry Linux bpi08 6.2.7-sunxi #3 SMP Fri Mar 17 07:58:04 UTC 2023 armv7l GNU/Linux (armbian@next) Mir ist es nicht möglich eine interne Temperatur auszulesen. Brauche dringend Hilfe! Der Link“/etc/armbianmonitor/datasources/soctemp “ exitiert zwar, nur die Datei / das Verzeichnis existiert nicht: nicht vorhanden → /sys/devices/virtual/thermal/thermal_zone0/temp nicht vorhanden → /sys/class/thermal/thermal_zone1/temp Wo soll diese Dateien überhaupt erstellt werden? Anmerkung Es wäre schön, wenn es für den Banana Pi M2 Berry eigene Tags geben würde. Er unterscheidet sich von dem Banana Pi M2+.

Avnet RASynBoard is a tiny board that packs a lot of features in a 30x25mm form factor with a Renesas RA6M4 Cortex-M33 microcontroller, a Syntiant NDP120 Neural Decision Processor, a Renesas (Previously Dialog Semi) DA16600 Wi-Fi 4 & Bluetooth 5.1 combo module, and a 6-axis inertial measurement unit (IMU) and digital microphone from TDK. The RASynBoard is offered as part of an EVK with the Core Board described above plus an IO board with headers, a Pmod connector, a MikroE Shuttle Click header, a microSD card slot for storage, and a built-in debugger, plus two buttons and an RGB LED. RASynBoard specifications: Main microcontroller – Renesas RA6M4 Arm Cortex-M33 microcontroller @ 200 MHz with 1 MB flash memory, 256 KB SRAM ML accelerator – Syntiant NDP120 Neural Engine based on Syntiant Core 2 Deep Neural Network, Arm Cortex M0 and HiFi 3 DSP Wireless module – Renesas DA16600 2.4 [...] The post Tiny RASynBoard combines Renesas RA6M4 MCU with Syntiant NDP120 ML accelerator, WiFi & BLE module, and some sensors appeared first on CNX Software - Embedded Systems News. View the full article

Hi, I have the board connected by HDMI to a TV but when I start I have no sound, I have to go to the speaker icon, configuration and the option is always selected "Speakers - internal audio" but if I want to have sound I have to choose the output option "Analogic ouput- internal audio" and if I restart I have to do the process again. According to the fine adjustment guide of ARMBIAN I must execute the command pacmd list-sinks | less And should be marked with * the selected card but none appears with that symbol. I attach the terminal output after selecting the right output on the desktop to have sound to see if someone is so kind to help me solve my problem. Thanks a lot. 2 sink(s) available. index: 1 name: <alsa_output.platform-es8388-sound.stereo-fallback> driver: <module-alsa-card.c> flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY state: SUSPENDED suspend cause: IDLE priority: 9000 volume: front-left: 33482 / 51% / -17.50 dB, front-right: 33482 / 51% / -17.50 dB balance 0.00 base volume: 65536 / 100% / 0.00 dB volume steps: 65537 muted: no current latency: 0.00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 1 sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Estéreo used by: 0 linked by: 0 fixed latency: 99.95 ms card: 1 <alsa_card.platform-es8388-sound> module: 8 properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "dailink-multicodecs ES8323.6-0010-0" alsa.id = "dailink-multicodecs ES8323.6-0010-0" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "2" alsa.card_name = "rockchip-es8388" alsa.long_card_name = "rockchip-es8388" device.bus_path = "platform-es8388-sound" sysfs.path = "/devices/platform/es8388-sound/sound/card2" device.form_factor = "internal" device.string = "hw:2" device.buffering.buffer_size = "17632" device.buffering.fragment_size = "4408" device.access_mode = "mmap" device.profile.name = "stereo-fallback"

Hi, I would like to use my usb wifi adapter from my old Raspi 3. `lsusb` shows: `Bus 007 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter` `ip a` shows: ``` 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 76:ac:9a:1c:50:76 brd ff:ff:ff:ff:ff:ff inet 192.168.18.213/24 brd 192.168.18.255 scope global dynamic noprefixroute eth0 valid_lft 1953sec preferred_lft 1953sec inet6 fe80::4450:f4d8:e15a:12c/64 scope link noprefixroute valid_lft forever preferred_lft forever ``` and `lsmod` shows: ``` Module Size Used by bnep 24576 2 zstd 16384 8 sch_fq_codel 20480 3 fuse 110592 1 ip_tables 28672 0 ipv6 434176 82 panfrost 57344 0 gpu_sched 28672 1 panfrost ```

Hi @IMakeTheQuestions, with @jock we have noticed some special cases in which the boot from sd does not happen. They are hard to fix without any logs (which in your case are hard to recover without uart). Can you please try to see if booting from sd works with my build of libreelec?(https://ilmich.libreelec.tv/libreelec-10/). Thank you

Hello! Im trying to get a program called Jetadvice to run on Armbian Bullseye Minimal CLI. I have installed xfce-desktop on the system. Banana Pi BPI-M5 I have installed the required libs linux-libc-dev:armhf and install libc6:armhf. I have added the --add-architecture armhf. But when i start the systemctl processes for the program they stop after a while. I have manage to install the program on the system one time but i have no idea how i manage to get it to work. Did not document it. The EF.JA.Edge.Installer.InstallService fail. It looks okay but the JetAdvice-Edge.service stops after a few seconds. Here is a link to the program and the commands to install it. https://app.jetadvice.com/install/edge/jetadvice-edge-linux-arm.tar If everything works. You should be able to get access to http://localhost:33322 on the computer. Give the program access: sudo chmod +x Installer Run the installation: sudo ./Installer install Starta the following services. JetAdvice-Edge: systemctl start JetAdvice-Edge.service JetAdvice-Updater: systemctl start JetAdvice-Updater.service JetAdvice-Edge-Ui: systemctl start JetAdvice-Edge-UI.service

Ideally check if this issue with that disk happens also on some x86 computer. In any case, you can report this issue to the linux-nvme at lists.infradead.org address and ask for help there.

the driver does not receive a response and sets an arbitrary resolution. add a fixed value of the output setting to the extlinux.conf command line (search the forum for how to do this).

Rockchip RK3588M is an automotive-grade variant of the Rockchip RK3588 octa-core Cortex-A76/A55 SoC that supports at least 6 Full HD displays and 16 camera inputs and can simultaneously run the car dashboard, in-vehicle infotainment, a digital rearview mirror, headrest monitors, ADAS system, and more. The frequency of the Cortex-A76 cores is limited to 2.1 GHz, and the Cortex-A55 cores to 1.7 GHz, against 2.4 and 1.8 GHz for RK3588, probably to operate in a larger temperature range required by the automotive market. I could not find any RK3588M datasheet yet, but we can find more details through the Firefly AIO-3588MQ automotive mainboard built around the RK3588M processor. Firefly AIO-3588MQ specifications: SoC – Rockchip RK3588M octa-core processor with CPU 4x Cortex-A76 cores @ up to 2.1 GHz, 4x Cortex-A55 cores @ up to 1.7 GHz Arm Mali-G610 MP4 GPU with OpenGL ES 3.2, OpenCL 2.2, Vulkan 1.1 support 6 TOPS AI [...] The post Rockchip RK3588M automotive-grade AI SoC supports up to 16 camera inputs appeared first on CNX Software - Embedded Systems News. View the full article

Sorry for stupid question. I tried install the instruction on my rock 3a (different board, but similar). rock-3a:~:% uname -r 6.1.11-rk35xx rock-3a:~:% ls /dev/mtdblock0 /dev/mtdblock0 I choose option: "Boot from MTD Flash - system on SATA, USB or NVMe". It does not work. (solved usb-flash bug)

After the better part of a year being unable to use this device, I am pleased to announce my first successful boot into Armbian. I accomplished this by installing tow-boot to the SPI. If you check their instructions for the PineBook Pro, it says to install some 'installer' version first to an SD card, and then boot that, and use it to install to the SPI chip (or other media). I did not want to do that for a few reasons: I don't understand why all the faffing about with an indirect installation method via SD card? I don't seem to be able to boot via SD card anyway. I am really not interested in removing all those $#%^# screws from the back case again, just so I can flip a switch, then put them all back.[0] So what I did was dig around a little more until I found this issue from last year where people were saying just to do the following, essentially: dd if=Tow-boot.spi.bin of=/dev/mtd0 So I downloaded latest release of tow-boot, which comes as an xz compressed tar archive. After opening that up the usual way with: tar -xf pine64-pinebookPro-2021.10-005.tar.xz Under the binaries folder I found the Tow-Boot.spi.bin file. I copied that over to PBP and then executed the above mentioned 'dd' command (via sudo). I powered off and then back on, I knew it was successful because I saw the Tow Boot logo. So I powered off and then inserted SD card I had prepared a while back with Armbian on it. And yet it still booted into Manjaro on the eMMC. So once Manjaro finished booting, I powered back down, then back on, this time pressing <ESC> to bring up tow-boot's boot menu. After selecting 'SD card' I was able to boot into Armbian image on the SD card, which did the normal expansion and first run setup (entering passwords, locale, etc.). Now this is interesting, because I had tried to boot this very same SD card before, without any luck. Even turning the (previously mentioned) 'eMMC switch' to both positions[0], I could never get it to work. So maybe there is something to the 'switch is broken on the new batch' theory? Anyway, I guess that's it, as I finally have Armbian running on here. It's a minimal/CLI image, so I still have my work cut out for me getting this all set up, but hopefully I can just install my preferred desktop packages and we will see how it goes. But that's another project for another day. [0] Which involves removing quite a number of tiny little screws and removal of the entire back cover. And then putting them all back. In the meantime you can't really use the keyboard or anything, so you pretty much have to do the whole %&#@%# process every time. After doing this a few times, it starts turning into a hassle.

Armbianmonitor: I had use armbian-config to change the dts for change pin start status. it worked. but just work when kernel load. it don't effect the uboot. did i missing some step? or it's because my uboot is too old? Thanks, mika

I decided to continue my investigation in a new thread.

I slowly convinced myself that I wanted a PineBook Pro, some time after the first production run. But then COVID, parts shortages, etc. happened and they were not available again until about mid-2022. But when they were, I decided to snap one up. And since then I have not been able to get it to boot Armbian. It came from the factory with Manjaro, which for me being a Debian guy, might as well be useless. So the PBP sat around collecting dust. Since then I have tried a few times to get it to work. I read many forum posts, tried some things. I won't document all that in detail. In this post, I will continue from where I left off here. However to summarize, that was about comparing DTB/DTS files to Kali, which supposedly works. That may become useful later, but I don't think that's the main problem. I think that the main problem is that this new batch came from the factory with no bootloader flashed to the included SPI flash chip. This is a problem on PineBook Pro because the RK3399 has a kind of weird boot order: SPI, eMMC, SD card. Therefore, if you just put in some SD card you flashed, it still boots from the factory Manjaro from the eMMC. Now, because of the weird boot situation, there is supposed to be a switch to turn off eMMC. However this did not work for me. Which means one of 2 things: The switch does not work. I read at least one other person saying this. Also on the new revision, it's in a slightly different place than the old revision (may be a clue, maybe not). I simply had a bad Armbian image (which I had burned to sd card) that would not boot for whatever reason. But let's put that aside for a moment. As I still think the main problem is the (empty) SPI. And that will be the easiest/best path forward. I confirmed the 'blank SPI' theory 2 different ways. First, as mentioned in a follow-up to the linked post (4 paragraphs above): As Martijn Braam states here: Of course, I like to beat a horse until it's really dead be thorough in my investigations, so today I wasted a lot of time[0] verifying that this indeed was the case. I did so by dd'ing the /dev/mtd0 block device into a file[1]. When I examined the file, it contained all FF, and also it is about 16 MiB in size. To me this confirms that indeed, the SPI on the new batch comes from the factory empty. So what is next? I keep reading that the only people who had success first had to install something like tow-boot to the SPI. That will be my next step. But before I flashed anything to SPI, I wanted to see what really came from the factory (which I did above). I will continue to document my progress whenever time allows for me to work on this. [0] In the end the solution was simple. But first I wasted a lot of time trying to get rkdeveloptool working in Manjaro on the PBP. Only to realize it's intended to be used from a second machine to read the SPI flash via USB in maskrom mode. Anyway, lesson learned. [1] I tried to attach it but maybe it's too big.

Thanks a lot @Pali! Actually I have bought another drive (SK hynix BC711 256Gb NVMe PCIe M.2 2242 (HFM256GD3HX015N)) and it is working flawlessly.

Description Jira reference number AR-1639 How Has This Been Tested? [🐳|🔨] dpkg-deb: building package 'armbian-config' in '/armbian/.tmp/work-c83920b4-8982-4007-933f-d08866c61443/tmp.Qoc0Tbqyxh/armbian-config_23.05.0-trunk_all.deb'. [🐳|💥] error! [ Artifact file /armbian/output/debs/armbian-config_23.05.0-trunk--1-SAce33-B21b2_all.deb did not exist, after artifact_build_from_sources(). ] [ ] 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

To summarize some discussion from IRC yesterday: A couple people (rpardini and c0rneliuis) looked into the above and said that the Kali DTS seems to be closer to upstream. And also that perhaps a plain vanilla mainline DTS/DTB might work for booting PBP at this point. Today I plan to continue to look into the SPI issue, as I am pretty sure it came empty from the factory on the new batch. I am referring to the following (as well as having read this several other places): https://blog.brixit.nl/why-i-left-pine64/