[Problem booting rock pi 4 se]

weird thing. nmcli dev wifi sees all networks but armbian-config doesn't think i have wifi.

 

weirder. After installing network-manager armbian-config started seeing wifi. 

[Problem booting rock pi 4 se]

Board says: ROCK PI 4 SE

 

trying Armbian_community_24.11.0-trunk.130_Rock-4se_bookworm_current_6.6.51_minimal.img.xz

 

boots via console, no hdmi no wifi. Detected as Radxa ROCK Pi 4A (should be 8b according to doc). HDMI works if forced to fullhd (monitor 4k)

 

U-Boot 2023.10-rc2-armbian-2023.10-rc2-Sa169-P0000-H8c72-Va6f9-Bda0a-R448a (Jul 22 2024 - 17:36:28 +0000)

SoC: Rockchip rk3399
Reset cause: RST
Model: Radxa ROCK Pi 4A
DRAM:  4 GiB (effective 3.9 GiB)
PMIC:  RK808
Core:  288 devices, 30 uclasses, devicetree: separate
MMC:   mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... Card did not respond to voltage select! : -110
*** Warning - No block device, using default environment

 

trying Armbian_community_24.11.0-trunk.130_Rockpi-4b_bookworm_current_6.6.51_minimal.img.xz

 

boots via console. no hdmi no wifi on startup or via armbian-config. iwconfig lists wlan0. ethernet works. Detected as 4B. hdmi works if forced to fullhd. the old official radxa image successfully detects and uses 4k out of box 

 

U-Boot 2022.07-armbian-2022.07-Se092-Pfa03-H8c72-V70f2-Bda0a-R448a (Jul 22 2024 - 17:36:01 +0000)

SoC: Rockchip rk3399
Reset cause: POR
Model: Radxa ROCK Pi 4B
DRAM:  3.9 GiB
PMIC:  RK808
Core:  285 devices, 31 uclasses, devicetree: separate
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from SPIFlash... jedec_spi_nor flash@0: unrecognized JEDEC id bytes: ff, ff, ff
*** Warning - spi_flash_probe_bus_cs() failed, using default environment

 

[Problem booting rock pi 4 se]

Tried installing rock 4se image and rockpi 4b image. Both blink the blue led but none gives me hdmi output or network connection. 

 

 

 

What is the correct image for this sbc? The silkscreen says rockpi 4 SE

 

Thanks

[1wire sensors]

I managed to make it work. The nightly i'm using was trying to load the overlay but with the wrong name and from the wrong folder:

/boot/dtb/allwinner/overlay/sun50i-h5-w1-gpio.dtbo <--- location of file on mmc

/boot/dtb/allwinner/overlays/-sun50i-h5-w1-gpio.dtbo <--- place from where the OS was trying to read

 

I made a symbolic link to /dtb (that's also read at boot although not used on the stock image) with the folder and name altered.  Maybe it will even survive a kernel update!

The only think I could not do was change the parameters (in this case port) as using the correct parameter inside armbianEnv.txt wasnt changin anything so I just physically changed the cable on the header

 

 

Thanks all!

[1wire sensors]

The problem is that I can't activate overlays. Tried to activate uart1 and got nothing. 

 

Thanks anyway I guess I'll have to reinstall a newer image

[1wire sensors]

1 hour ago, zador.blood.stained said:

Why do you think that? None of sunxi boards supported by Armbian have HW 1-Wire controller, so w1-gpio must be used.

On Orange Pi PC2 1-wire should work by activating "w1-gpio" overlay, but it requires a fresh image (not an older image updated with apt upgrade)

Are you sure? From what I remember on the pi pc it wouldn't work without w1-sunxi (plain Debian, not armbian) 

 

I'm using the following nighty, is that one new enough for it to work? 

 

ARMBIAN 5.27.170522 nightly Ubuntu 16.04.2 LTS 4.11.1-sun50iw2 

[1wire sensors]

Hi. I'm trying to change the setup I have running on a pi pc to my new pi pc2 running latest version of nightly (at least latest version of the packages)

 

Every kernel version I tried does include the w1-gpio and w1_therm but it's missing the w1-sunxi that's required for it to work. 

 

Is it missing from the kernel or am I the one missing something?