Jump to content

Search the Community

Showing results for tags 'rockpi-s'.

  • Search By Tags

    Type tags separated by commas.

  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...


Date Created

  • Start

    End

Last Updated

  • Start

    End

Filter by number of...

Joined

  • Start

    End

Group

Matrix

Mastodon

IRC

Website URL

XMPP/Jabber

Skype

Github

Discord

Location

Interests

Found 35 results

  1. Meestor_X
    Currently running 24.8.3 and have copied it to the eMMC, working fine on both the µSD image and eMMC. (On the Rock-Pi-S, if you have a bootable image on the µSD card, it boots from that. If not, it boots from the eMMC.) Today, running from the µSD, I did an apt update and apt upgrade, and it updated a few packages (here's the list): # apt list --upgradeable Listing... Done armbian-config/unknown 25.2.0-trunk.154.1212.080011 all [upgradable from: 24.11.1] armbian-firmware/bookworm,bookworm 24.11.2 all [upgradable from: 24.11.1] base-files/bookworm 24.11.2-12.4+deb12u8-bookworm arm64 [upgradable from: 24.11.1-12.4+deb12u8-bookworm] linux-dtb-current-rockchip64/bookworm 24.11.1 arm64 [upgradable from: 24.11.1] linux-image-current-rockchip64/bookworm 24.11.1 arm64 [upgradable from: 24.11.1] tzdata/stable-updates 2024b-0+deb12u1 all [upgradable from: 2024a-0+deb12u1] Now, it no longer boots from the µSD card. So I assume it's done something catastrophic to the image on that card?
  2. Jorropo
    armbianmonitor -u https://paste.next.armbian.com/hoyonuruye I installed the newest fresh debian minimal image for the RockPi-S and no matter what I do overlays do not apply. I've followed and compiled spi1 and spi2 rk3308. I've also tested the external antenna device tree as I have installed an external antenna: However neither the external antenna is being used nor spidev are present. I have diffed dtc -I fs -O dts /proc/device-tree and they are identical before and after enabling the overlays in armbian-config and rebooting. I was able to confirm the "overlays" work by manually copypasting their changes in linux's source dts and generating a patch file, placing it in armbian's linux patch folder and recompiling from scratch, so if I do change the options spidev works, just I somehow can only do this by editing the source. Here is the `/boot/armbianEnv.txt` file generated: verbosity=1 bootlogo=false console=serial overlay_prefix=rk3308 fdtfile=rockchip/rk3308-rock-pi-s.dtb extraargs=cma=16M rootdev=UUID=036c1484-611d-470e-b2ef-775fe550149b rootfstype=ext4 fdt_overlays=rk3308-s0-ext-antenna rk3308-spi1-spidev rk3308-spi2-spidev usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Also after editing the overlays in armbian-config this error pops up: /boot/armbianEnv.txt: line 9: rk3308-spi1-spidev: command not found
  3. Meestor_X
    running 24.8.3, and Armbian-install's screen looks like this: Current root: UUID=117b851b-2be0-4bb7-8572-7edce1ef7375 SD card (/dev/mmcblk1) 1 Boot from SD - system on SATA, USB or NVMe 2 Boot from - system on 3 Boot from - system on SATA, USB or NVMe 5 Install/Update the bootloader on SD card (/dev/mmcblk1) I have a µSD card inserted and a 4gb eMMC, but it looks like the names of these devices are missing?
  4. Meestor_X
    I get the following result when trying to run armbianmonitor -u. Is it broken or am I doing something wrong? Armbian 24.8.3 Bookworm CLI on a Rock-Pi S # armbianmonitor -u Collecting info and sending to paste.armbian.com, wait... /usr/bin/armbianmonitor: line 976: iostat: command not found <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Error</title> </head> <body> <pre>Cannot POST /log</pre> </body> </html> Please post the URL in the forum where you've been asked for.
  5. grixm
    I have installed Armbian on my Rock Pi S, done some setup, and then taken an image of the disk to be duplicated to other devices. The problem is that each of these devices get the same permanent MAC address on the ethernet port as the first device. I don't know how Armbian gets the MAC address from the interface but it doesn't seem to depend on unique hardware, or if it does then the hardware ID isn't actually unique between boards. This leads to problems because my device is meant to be used several in the same network, causing collisions in DHCP assignment etc. I have tried multiple workarounds and none have worked well. I tried spoofing the MAC addr by changing the cloned-mac-address setting in NetworkManager. This worked at changing the MAC address, however it caused an entirely different problem, namely that a fallback connection with a link-local address never gets activated. It previously worked but after changing only this setting, it no longer works. I have no idea why but I have tried for days now to fix this issue and I'm out of new ideas. The other thing I tried was adding ethaddr=[some mac address] in the armbianEnv.txt file, as found in another forum thread. This didn't seem to do anything, the same duplicate MAC address was still used. I also tried using macchanger, but it was difficult to get to work nicely with NetworkManager, I don't think this is a good solution... What else can I try?
  6. PHLAK
    I've been using a few Rock Pi S devices as snapcast clients and after updating them to Armbian 24.8.2 audio does not work anymore. This seems similar to this old post (fix PR). Also, this PR may be a relevant to the issue. https://paste.armbian.com/aziwayelen $ snapclient --host [REDACTED] 2024-09-17 09-28-10.435 [Error] (Snapclient) PCM device "default" not found 2024-09-17 09-28-10.436 [Info] (Snapclient) Version 0.26.0 2024-09-17 09-28-10.437 [Info] (Connection) Resolving host IP for: [REDACTED] 2024-09-17 09-28-10.440 [Info] (Connection) Connecting 2024-09-17 09-28-10.442 [Notice] (Connection) Connected to 192.168.0.100 2024-09-17 09-28-10.442 [Info] (Connection) My MAC: "42:00:00:00:80:30", socket: 8 2024-09-17 09-28-10.518 [Info] (Controller) ServerSettings - buffer: 1000, latency: 0, volume: 75, muted: 0 2024-09-17 09-28-10.519 [Info] (Controller) Codec: flac, sampleformat: 48000:16:2 2024-09-17 09-28-10.520 [Info] (Player) Player name: alsa, device: default, description: <none>, idx: -1, sharing mode: unspecified, parameters: <none> 2024-09-17 09-28-10.520 [Info] (Player) Mixer mode: software, parameters: <none> 2024-09-17 09-28-10.520 [Info] (Player) Sampleformat: 48000:16:2, stream: 48000:16:2 2024-09-17 09-28-10.520 [Info] (Alsa) Using default buffer_time: 80 ms, default fragments: 4 ALSA lib confmisc.c:855:(parse_card) cannot find card '0' ALSA lib conf.c:5180:(_snd_config_evaluate) function snd_func_card_inum returned error: No such file or directory ALSA lib confmisc.c:422:(snd_func_concat) error evaluating strings ALSA lib conf.c:5180:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1334:(snd_func_refer) error evaluating name ALSA lib conf.c:5180:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:5703:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM default 2024-09-17 09-28-10.528 [Error] (Alsa) Exception: Can't open default, error: No such file or directory, code: -2 2024-09-17 09-28-10.530 [Fatal] (Snapclient) Exception: Can't open default, error: No such file or directory 2024-09-17 09-28-10.530 [Notice] (Snapclient) Snapclient terminated. $ aplay -l aplay: device_list:274: no soundcards found... When following the instructions on the official wiki to enable the audio jack I get a `Permission denied` error echoing a value to the `/sys/class/gpio/export` (but not gpio15). $ sudo echo 15 > /sys/class/gpio/export -bash: /sys/class/gpio/export: Permission denied $ sudo cat /sys/class/gpio/export cat: /sys/class/gpio/export: Permission denied $ ls -Al /sys/class/gpio/ total 0 --w------- 1 root root 4096 Sep 17 09:16 export lrwxrwxrwx 1 root root 0 Sep 17 09:16 gpio15 -> ../../devices/platform/pinctrl/ff220000.gpio/gpiochip0/gpio/gpio15 lrwxrwxrwx 1 root root 0 Dec 31 1969 gpiochip0 -> ../../devices/platform/pinctrl/ff220000.gpio/gpio/gpiochip0 lrwxrwxrwx 1 root root 0 Dec 31 1969 gpiochip128 -> ../../devices/platform/pinctrl/ff260000.gpio/gpio/gpiochip128 lrwxrwxrwx 1 root root 0 Dec 31 1969 gpiochip32 -> ../../devices/platform/pinctrl/ff230000.gpio/gpio/gpiochip32 lrwxrwxrwx 1 root root 0 Dec 31 1969 gpiochip64 -> ../../devices/platform/pinctrl/ff240000.gpio/gpio/gpiochip64 lrwxrwxrwx 1 root root 0 Dec 31 1969 gpiochip96 -> ../../devices/platform/pinctrl/ff250000.gpio/gpio/gpiochip96 --w------- 1 root root 4096 Sep 17 09:36 unexport
  7. grixm
    Hi, I'm trying to build an image on Windows. But when running compile.sh, I get the following error: [💲|💥] Problem detected [ WSL2 Terminal does not support UTF-8 ] Full log: https://paste.armbian.com/zopitumatu I don't know why this is happening, I've tried both cmd, powershell 5, powershell 7, all with the same result. The log mentions the Windows Terminal in the Microsoft Store should support it, but that already is installed and seems to just open the same Powershell 5, with the same error. Any idea on how to fix this?
  8. Виктор Хомченко
    Hello everybody! I need help: I can't turn on the SPI interface in any way so that /dev/spidev0 or /dev/spidev1 appears. In armbian-config, there are generally only 7 lines in the hardware section, in which there is nothing interesting, an attempt to register spidev in armbianEnv.txt it also does not help, in dmesg and journalctl - silence... Where did the interface go?
  9. PHLAK
    I have Armbian up and running on a Rock Pi S with a PoE HAT. To enable the audio jack on the PoE HAT I had to run the following commands as mentioned on the official Rock Pi S PoE Hat wiki. # echo 15 > /sys/class/gpio/export # echo out > /sys/class/gpio/gpio15/direction # echo 1 > /sys/class/gpio/gpio15/value Once enabled, the audio works as needed. However, every time the device is rebooted I have to SSH in and run these commands again to re-enable audio out which is obviously not ideal. How can I persist these changes between reboots?
  10. dg4gg8cb9s
    Hello! I’m trying to get a RockPi S connected by a slow ethernet connection with 10mbps (half or full duplex) but it doesn’t seem to work. If I test with a 100mbps connection, everything works fine and as expected. Using 10mbps, it seems to look fine, e.g. ethtool shows a link with 10mpbs, advertised modes look fine but the RockPi S doesn’t even retrieve an IP via DHCP. If configuring a static IP, no ping to any address beside the own IP address is possible. I’m using latest debian-based armbian 23.8.1 stable and performed apt-get update & upgrade. Anyone encountered the same problem and has some hints? Unfortunately I’m not a linux pro so unfortunately I’m a bit stuck but I’m happy to provide any missing information or execute commands on the RockPi S and post the results here. Cheers
  11. bonedaddy4538
    On a fresh install from the website on kernel 6.1 bookworm/Jammy when rebooting the board a kernel panic occurs and the device will not boot unless power cycled. This was not the case even a few months ago on a 6.6 edge kernel. I also tried the current edge 6.7 kernel and the board wouldn't boot at all not that I expected it to. The board says 3308B on the chip(samsung memory) and ive also tried two different micro sd. Anyone else having this issue? Serial output is below of the relevant failure Thanks for anyone willing to look. Update: Reboot works fine on rockpi-s ordered more recently late 2023 with non-samsung ram module. I wonder if that is a reason. I will try the last 5.15 firmware created for this board and see if that works.
  12. grixm
    Hi. For my application it would be very advantageous to speed up the boot time of the device as much as possible. The application depends on the network, and unfortunately it seems it takes a while for the interface to establish a connection. After plugging in the device, I count that it takes about 25-30 seconds until my application starts (which is set to start on reboot by cron). However, at that time, the network is still not up, so it matters little that the application has started. It takes another 20 seconds or so until the device is reachable by the network. So total 45-50 seconds from boot. Why is this? I see in systemd-analyze that NetworkManager.service starts at around 30 seconds, same as cron. So what is the holdup? The IP is static and it is plugged in with Ethernet, so I don't understand what takes time when it comes to connecting to the network, after the network manager has started. How can I troubleshoot this or make it connect faster? Bonus question. Another thing that takes a lot of time in the boot is armbian-ramlog.service, at nearly 8 seconds long. See attachment for full boot chart. Is there a way to shorten this too, without disabling ram logging entirely? bootanalyze.svg
  13. solaris3308
    I have add user dtbo with "armbian-add-overlay rk3308-w1-gpio.dts" but it's NOT work.Some message is shown as below: pi@Pi-S:/boot/overlay-user$ dmesg | grep gpio [ 0.063257] OF: /onewire@0: could not get #gpio-cells for /usb@ff400000 [ 0.096538] rockchip-gpio ff220000.gpio: probed /pinctrl/gpio@ff220000 [ 0.097838] rockchip-gpio ff230000.gpio: probed /pinctrl/gpio@ff230000 [ 0.099097] rockchip-gpio ff240000.gpio: probed /pinctrl/gpio@ff240000 [ 0.100300] rockchip-gpio ff250000.gpio: probed /pinctrl/gpio@ff250000 [ 0.101462] rockchip-gpio ff260000.gpio: probed /pinctrl/gpio@ff260000 [ 8.818566] gpio-17 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 8.818683] OF: /onewire@0: could not get #gpio-cells for /usb@ff400000 [ 8.818731] w1-gpio onewire@0: gpio_request_one (ext_pullup_enable_pin) failed [ 8.818742] w1-gpio: probe of onewire@0 failed with error -22 [ 8.872897] rk3308-acodec ff560000.acodec: Don't need hp-ctl gpio [ 8.872955] rk3308-acodec ff560000.acodec: Don't need spk-ctl gpio [ 8.872984] rk3308-acodec ff560000.acodec: Don't need pa-drv gpio [ 8.873096] rk3308-acodec ff560000.acodec: Don't need micbias-en gpio What should I do to ?
  14. danj
    Hi everyone! I am struggling with audio input. Output audio from LINEOUT pins works fine out-of-the-box! What about the audio input? To begin with I have tested the arecord command with these error messages… TEST 1 root@rockpi-s:~# arecord -f S16_LE -d 10 -r 16000 --device=“hw:0,0” test-mic.wav Recording WAVE ‘test-mic.wav’ : Signed 16 bit Little Endian, Rate 16000 Hz, Mono arecord: set_params:1358: Channels count non available TEST 2 root@rockpi-s:~# arecord -f S16_LE -c 2 -d 10 -r 16000 --device=“hw:0,0” test-mic.wav Recording WAVE ‘test-mic.wav’ : Signed 16 bit Little Endian, Rate 16000 Hz, Stereo arecord: set_params:1416: Unable to install hw params: ACCESS: RW_INTERLEAVED FORMAT: S16_LE SUBFORMAT: STD SAMPLE_BITS: 16 FRAME_BITS: 32 CHANNELS: 2 RATE: 16000 PERIOD_TIME: 125000 PERIOD_SIZE: 2000 PERIOD_BYTES: 8000 PERIODS: 4 BUFFER_TIME: 500000 BUFFER_SIZE: 8000 BUFFER_BYTES: 32000 TICK_TIME: 0 Any suggestions?
  15. kolsi
    Hello, I have Rock Pi S V13 and Armbian 23.8.1 Bookworm with Linux 6.1.50-current-rockchip64. When I change CPU settings (min frequency, max frequency, scaling governor) using armbian-config, the change works correctly as expected. However, these settings are lost on reboot. When I check the status of cpufrequtils service, it seems that it does not load correctly as it is not able to find the requested governor: But if I start it manually later, it seems to load all my settings correctly: Any ideas to fix the problem except manually reloading it later? armbianmonitor: https://paste.armbian.com/owolufawif
  16. NaK
    Per Radxa here, it is possible to obtain CPU temperature via "sudo cat /sys/class/thermal/thermal_zone0/temp". But the following paths do not exist on Armbian 23.05.1 Bookworm with Linux 6.1.30-rockchip64: /etc/armbianmonitor/datasources/soctemp /sys/devices/virtual/thermal/thermal_zone0/temp Running armbianmonitor -M, also does not show the temp: Time CPU load %cpu %sys %usr %nice %io %irq C.St. 22:29:52 408 MHz 0.02 0% 0% 0% 0% 0% 0% 0/6
  17. gudvinr
    None of the images from https://www.armbian.com/rockpi-s/ work (neither minimal nor cli). I tried writing minimal image onto SD NAND and tried booting both cli and minimal from SD card. I tried 2 different SD cards too. Board was connected through UART0 to PC and while I get output when I use rkdeveloptool, there is no output when trying to boot normally. However, latest image from https://github.com/radxa/rock-pi-s-images-released/releases works (rockpis_debian_buster_server_arm64_20210924_0412-gpt.img) does boot if I write it to SD NAND or SD card. I have V1.3 with RK3308 and 1GB SD NAND.
  18. DavidJS
    I am using the rockpi-s board(with rockchip rk3308 soc), and want to change the console serial of the uboot. According to https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-patches, I tried: rm userpatches/u-boot/u-boot-rockchip64-v2022.04/u-boot-rockchip64-edge.patch ./compile.sh uboot-patch BOARD=rockpi-s BRANCH=edge RELEASE=bullseye BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,img EXTRAWIFI=n After I modified what I want in the uboot source code, I continue to copy the path to the userpatches path: cp output/patch/u-boot-rockchip64-edge.patch userpatches/u-boot/u-boot-rockchip64-v2022.04/ And compile the whole image: ./compile.sh BOARD=rockpi-s BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes COMPRESS_OUTPUTIMAGE=sha,img EXTRAWIFI=no KERNEL_CONFIGURE=no RELEASE=bullseye Everything seems to be fine, after compiled, I flashed the image to my EMMC flash, but it could not boot. And even if I don't make any meaningful changes, as long as I use this method to patch u-boot, the system will not start. As long as there is no this patch, it can be started. So I wonder if there is something wrong with this method?
  19. AlexanderG
    Hi there, I've been using ARMbian for a couple of years now under a Rock Pi S board. I'm using an ARMbian OS image based on kernel 4.4x because it have a virtual wlan interface called P2P0, this allow me to use the board as WiFi repeater, I've written a post about it here. However, in recent ARMbian OS images with kernel 5.x and 6.x that virtual interface isn't there. I see in ARMbian OS image with kernel 6.x that the WiFi Hotspot set up menu in the armbian-config tool show an interface called p2p0-dev, but it doesn't work. My question: why? these newer kernels have limitations on this board? or maybe need to compile the kernel with custom modifications?. Any lead will be appreciated it.
  20. tim oberle
    I tested boot time and node-red-reboot time and noticed that boot-time is with bookworm ~2 sec and node-red-reboot got from 14sec to 20sec. I hope you can improve performance so I can upgrade. https://paste.armbian.com/uhocorarad
  21. Tomas77
    Is there any existing solution how to use SPI2 on Radxa Rock Pi S? In dmesg I found these messages: [ 1.619008] rockchip-pinctrl pinctrl: pin gpio1-22 already requested by ff0c0000.serial; cannot claim for ff140000.spi [ 1.619046] rockchip-pinctrl pinctrl: pin-54 (ff140000.spi) status -22 [ 1.619065] rockchip-pinctrl pinctrl: could not request pin 54 (gpio1-22) from group spi2-miso on device rockchip-pinctrl [ 1.619082] rockchip-spi ff140000.spi: Error applying setting, reverse things back Is it somehow possible to disable the serial port which is in collision with the SPI? There is a log from armbian monitor: http://ix.io/4yF8
  22. boi
    I am working with a Rock Pi S v1.3 and thus far the only image I have been able to get to boot is Armbian 21.05.9 Focal with Linux 4.4.247-rockpis. I have tried the recent Arabian Bookworm, Armbian Jammy and a few other variations I have come across on various forum posts here. With the above working image I can communicate with it via UART and get to the terminal. With everything else I don't even get the blinking blue LED; just two solid green LEDs. I have a few of these boards and have confirmed this issue across all of them. I am not sure what next steps to take so any pointers would be greatly appreciated. Thank you very much in advance.
  23. NaK
    For the Rock PI S, what is the recommended gpio library? I tried using Radxa libmraa but encountered the following errors (using bullseye-stable): $ sudo apt-get install -y libmraa ... The following packages have unmet dependencies: libmraa : Depends: libjson-c3 but it is not installable Depends: python but it is not installable Depends: python2.7 but it is not installable Depends: libpython2.7 but it is not installable Depends: python3.7 but it is not installable Depends: libpython3.7 but it is not installable E: Unable to correct problems, you have held broken packages.
  24. node.js
    Im stubmeld accros armbian while search for a ARM distribution for my RockPi S. I started successful with writing it to a SD Card and run it from there. Now i want to write it to the internal storage and start it from there. So far so got, everything "worked". But it stucks in a boot loop. I attached a Serial/TTL to USB converter and noticed the same output over and over again. Willkommen zu minicom 2.7.1 Optionen: I18n Übersetzt am Aug 13 2017, 15:25:34. Port /dev/ttyUSB0, 15:37:49 Drücken Sie CTRL-A Z für Hilfe zu speziellen Tasten DDR Version V2.06 20211109 CHIP ID = 0x00003308 REG2C: 0x00000033, 0x00000034 In 589MHz DDR3 Col=10 Bank=3 Row=15 Size=512MB OUT: sdram_init finish. Boot1 Release Time: Mar 24 2022 08:28:57, version: 1.36 ROM VER:0x56323030, 19 chip_id:330800,0 ChipType = 0x13, 511 DPLL = 1300 MHz ...nandc_flash_init enter... No.1 FLASH ID:ff ff ff ff ff ff DPLL = 1300 MHz sfc nor id: ff ff ff DPLL = 1300 MHz sfc_nand id: ff ff ff NeedKHz=200KHz,clock=12000KHz NeedKHz=200KHz,clock=12000KHz NeedKHz=200KHz,clock=12000KHz mmc2:cmd5,20 DPLL = 1300 MHz NeedKHz=24000KHz,clock=650000KHz DPLL = 1300 MHz NeedKHz=40000KHz,clock=650000KHz SdmmcInit=2 0 BootCapSize=0 UserCapSize=3696MB FwPartOffset=2000 , 0 SdmmcInit=0 NOT PRESENT StorageInit ok = 19304 SecureMode = 0 Secure read PBA: 0x4 Secure read PBA: 0x404 Secure read PBA: 0x804 Secure read PBA: 0xc04 Secure read PBA: 0x1004 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3306530 signature is wrong recovery gpt... GPT 0x3306530 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x600000, size=0x994c8 RunBL31 0x40000 @ 96576 us INFO: Preloader serial: 0 NOTICE: BL31: v1.3(release):30f1405 NOTICE: BL31: Built : 17:08:28, Sep 23 2019 INFO: Lastlog: last=0x100000, realtime=0x102000, size=0x2000 INFO: ARM GICv2 driver initialized INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 1 INFO: plat_rockchip_pmu_init: pd status 0xe b INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x600000 INFO: SPSR = 0x3c9 U-Boot 2022.04-armbian (May 27 2023 - 19:27:05 +0000) Model: Radxa ROCK Pi S DRAM: 510 MiB Core: 276 devices, 20 uclasses, devicetree: separate MMC: dwmmc@ff480000: 1, dwmmc@ff490000: 0 Loading Environment from nowhere... OK In: serial Out: serial Err: serial Model: Radxa ROCK Pi S rockchip_dnl_key_pressed read board id failed Net: eth0: ethernet@ff4e0000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3045 bytes read in 5 ms (594.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 176 bytes read in 4 ms (43 KiB/s) 14086333 bytes read in 597 ms (22.5 MiB/s) 29331968 bytes read in 1238 ms (22.6 MiB/s) 54770 bytes read in 10 ms (5.2 MiB/s) Failed to load '/boot/dtb/rockchip/overlay/rk3308-fixup.scr' Moving Image from 0x680000 to 0x800000, end=2490000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14086269 Bytes = 13.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02800000 Booting using the fdt blob at 0x2800000 Loading Ramdisk to 1d1b7000, end 1df2607d ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) Loading Device Tree to 000000001d141000, end 000000001d1b6fff ... OK Starting kernel ... Loading, please wait... Starting systemd-udevd version 252.6-1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Will now check root file system ... fsck from util-linux 2.38.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 armbi_root: clean, 29764/73296 files, 263864/292864 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Armbian 23.05.1 bookworm! [ OK ] Created slice system-modpr��…lice - Slice /system/modprobe. [ OK ] Created slice system-seria��… - Slice /system/serial-getty. [ OK ] Created slice user.slice - User and Session Slice. [ OK ] Started systemd-ask-passwo��…quests to Console Directory Watch. [ OK ] Started systemd-ask-passwo��… Requests to Wall Directory Watch. [ OK ] Set up automount proc-sys-��…rmats File System Automount Point. [ OK ] Reached target cryptsetup.��…get - Local Encrypted Volumes. DDR Version V2.06 20211109 CHIP ID = 0x00003308 REG2C: 0x00000033, 0x00000034 In 589MHz DDR3 Col=10 Bank=3 Row=15 Size=512MB OUT: sdram_init finish. Boot1 Release Time: Mar 24 2022 08:28:57, version: 1.36 ROM VER:0x56323030, 19 chip_id:330800,0 ChipType = 0x13, 512 DPLL = 1300 MHz ...nandc_flash_init enter... No.1 FLASH ID:ff ff ff ff ff ff DPLL = 1300 MHz sfc nor id: ff ff ff DPLL = 1300 MHz sfc_nand id: ff ff ff NeedKHz=200KHz,clock=12000KHz NeedKHz=200KHz,clock=12000KHz NeedKHz=200KHz,clock=12000KHz mmc2:cmd5,20 DPLL = 1300 MHz NeedKHz=24000KHz,clock=650000KHz DPLL = 1300 MHz NeedKHz=40000KHz,clock=650000KHz SdmmcInit=2 0 BootCapSize=0 UserCapSize=3696MB FwPartOffset=2000 , 0 SdmmcInit=0 NOT PRESENT StorageInit ok = 19297 SecureMode = 0 Secure read PBA: 0x4 Secure read PBA: 0x404 Secure read PBA: 0x804 Secure read PBA: 0xc04 Secure read PBA: 0x1004 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3306530 signature is wrong recovery gpt... GPT 0x3306530 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x600000, size=0x994c8 RunBL31 0x40000 @ 96630 us INFO: Preloader serial: 0 NOTICE: BL31: v1.3(release):30f1405 NOTICE: BL31: Built : 17:08:28, Sep 23 2019 INFO: Lastlog: last=0x100000, realtime=0x102000, size=0x2000 INFO: ARM GICv2 driver initialized INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 1 INFO: plat_rockchip_pmu_init: pd status 0xe b INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x600000 INFO: SPSR = 0x3c9 U-Boot 2022.04-armbian (May 27 2023 - 19:27:05 +0000) Model: Radxa ROCK Pi S DRAM: 510 MiB Core: 276 devices, 20 uclasses, devicetree: separate MMC: dwmmc@ff480000: 1, dwmmc@ff490000: 0 Loading Environment from nowhere... OK In: serial Out: serial Err: serial Model: Radxa ROCK Pi S rockchip_dnl_key_pressed read board id failed Net: eth0: ethernet@ff4e0000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3045 bytes read in 5 ms (594.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 176 bytes read in 5 ms (34.2 KiB/s) 14086333 bytes read in 597 ms (22.5 MiB/s) 29331968 bytes read in 1238 ms (22.6 MiB/s) 54770 bytes read in 10 ms (5.2 MiB/s) Failed to load '/boot/dtb/rockchip/overlay/rk3308-fixup.scr' Moving Image from 0x680000 to 0x800000, end=2490000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14086269 Bytes = 13.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02800000 Booting using the fdt blob at 0x2800000 Loading Ramdisk to 1d1b7000, end 1df2607d ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) Loading Device Tree to 000000001d141000, end 000000001d1b6fff ... OK Starting kernel ... Loading, please wait... Starting systemd-udevd version 252.6-1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Will now check root file system ... fsck from util-linux 2.38.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 armbi_root: clean, 29764/73296 files, 263864/292864 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Armbian 23.05.1 bookworm! [ OK ] Created slice system-modpr��…lice - Slice /system/modprobe. [ OK ] Created slice system-seria��… - Slice /system/serial-getty. [ OK ] Created slice user.slice - User and Session Slice. [ OK ] Started systemd-ask-passwo��…quests to Console Directory Watch. [ OK ] Started systemd-ask-passwo��… Requests to Wall Directory Watch. DDR Version V2.06 20211109 CHIP ID = 0x00003308 REG2C: 0x00000033, 0x00000034 In 589MHz DDR3 Col=10 Bank=3 Row=15 Size=512MB OUT: sdram_init finish. Boot1 Release Time: Mar 24 2022 08:28:57, version: 1.36 ROM VER:0x56323030, 19 chip_id:330800,0 ChipType = 0x13, 511 DPLL = 1300 MHz ...nandc_flash_init enter... No.1 FLASH ID:ff ff ff ff ff ff DPLL = 1300 MHz sfc nor id: ff ff ff DPLL = 1300 MHz sfc_nand id: ff ff ff NeedKHz=200KHz,clock=12000KHz NeedKHz=200KHz,clock=12000KHz NeedKHz=200KHz,clock=12000KHz mmc2:cmd5,20 DPLL = 1300 MHz NeedKHz=24000KHz,clock=650000KHz DPLL = 1300 MHz NeedKHz=40000KHz,clock=650000KHz SdmmcInit=2 0 BootCapSize=0 UserCapSize=3696MB FwPartOffset=2000 , 0 SdmmcInit=0 NOT PRESENT StorageInit ok = 19338 SecureMode = 0 Secure read PBA: 0x4 Secure read PBA: 0x404 Secure read PBA: 0x804 Secure read PBA: 0xc04 Secure read PBA: 0x1004 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3306530 signature is wrong recovery gpt... GPT 0x3306530 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x600000, size=0x994c8 RunBL31 0x40000 @ 96666 us INFO: Preloader serial: 0 NOTICE: BL31: v1.3(release):30f1405 NOTICE: BL31: Built : 17:08:28, Sep 23 2019 INFO: Lastlog: last=0x100000, realtime=0x102000, size=0x2000 INFO: ARM GICv2 driver initialized INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 1 INFO: plat_rockchip_pmu_init: pd status 0xe b INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x600000 INFO: SPSR = 0x3c9 U-Boot 2022.04-armbian (May 27 2023 - 19:27:05 +0000) Model: Radxa ROCK Pi S DRAM: 510 MiB Core: 276 devices, 20 uclasses, devicetree: separate MMC: dwmmc@ff480000: 1, dwmmc@ff490000: 0 Loading Environment from nowhere... OK In: serial Out: serial Err: serial Model: Radxa ROCK Pi S rockchip_dnl_key_pressed read board id failed Net: eth0: ethernet@ff4e0000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3045 bytes read in 5 ms (594.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 176 bytes read in 4 ms (43 KiB/s) 14086333 bytes read in 597 ms (22.5 MiB/s) 29331968 bytes read in 1238 ms (22.6 MiB/s) 54770 bytes read in 10 ms (5.2 MiB/s) Failed to load '/boot/dtb/rockchip/overlay/rk3308-fixup.scr' Moving Image from 0x680000 to 0x800000, end=2490000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14086269 Bytes = 13.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02800000 Booting using the fdt blob at 0x2800000 Loading Ramdisk to 1d1b7000, end 1df2607d ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) Loading Device Tree to 000000001d141000, end 000000001d1b6fff ... OK Starting kernel ... Loading, please wait... Starting systemd-udevd version 252.6-1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Will now check root file system ... fsck from util-linux 2.38.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 armbi_root: clean, 29764/73296 files, 263864/292864 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Armbian 23.05.1 bookworm! I followed this tutorials: - https://www.armbian.com/rockpi-s - https://wiki.radxa.com/RockpiS/dev/sdnand-install - https://wiki.radxa.com/RockpiS/dev/serial-console Unfotunatly some of the links are broken and i need to find the file (rk3308_loader_uart0_m0_emmc_port_support_sd_20190717.bin) via google: https://forum.radxa.com/t/where-can-i-find-the-rk3308-loader-binary/2769 As i found it, i extracted the armbian image (Armbian_23.5.1_Rockpi-s_bookworm_current_6.1.30_minimal.img) and proceeded with the flasing progress. It worked, but as said, its stucks in a boot loop. Can any one help me and point out where to start debugging? Im not very familiar with embedded linux/hardware. Thanks in advance and for the awesome work!
  25. d0pefish
    armbianmonitor output: http://ix.io/4s3z I'm testing Armbian 23.02 Jammy on a Rock Pi S with its matching "PoE HAT" (which provides a 3.5mm headphone jack). No sound cards are available despite the device tree evidently containing sound devices/codecs [1, 2]. aplay output: rockpi-s:~:% aplay -l aplay: device_list:274: no soundcards found... The armbianmonitor/dmesg output contains the following suspicious lines: [ 24.551148] platform acodec-sound: deferred probe pending [ 24.551191] platform sound: deferred probe pending Digging into this a bit further, I found this root@rockpi-s:/home/dale# cat /sys/kernel/debug/devices_deferred acodec-sound asoc-simple-card: parse error sound asoc-simple-card: parse error If I were to guess, it looks like a devicetree issue, but unfortunately I have no idea how to debug devicetree issues. If anyone can provide any pointers on how to capture more detailed devicetree logs to try and figure out this "parse error", I'd appreciate it. Thanks!
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept