fraz0815

Same problem, uboot show no usb error on these images but also fails to boot. edit: could a connected nvme drive cause this? I did not open the case und dismount it physically

Armbian_22.08.0-trunk_Nanopct4_sid_edge_5.19.0.img.xz from your link works fine. Sorry, no UART yet, I should get one 😕

I built Armbian_22.08.2_Nanopct4_jammy_edge_5.19.10.img with following command, no changes made: ./compile.sh BOARD=nanopct4 BRANCH=edge RELEASE=jammy BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img Same error, see screenshot. As mentioned earlier when changing boardfamily to rockchip64, so their patch directories (kernel+uboot) are used to build the image instead of media, it works fine. Maybe some patch is missing? I also made a build from master branch, Armbian_22.11.0-trunk_Nanopct4_jammy_edge_5.19.10.img which also does not get beyond uboot.

Hmm, i deleted mmcblk2 to be sure to have no remaining stuff on it, booting with any 5.18 image like Armbian_22.08.1_Nanopct4_jammy_current_5.18.19.img and dd it. sudo dd if=/dev/zero of=/dev/mmcblk2 bs=1M Then tried Armbian_22.08.1_Nanopct4_sid_edge_5.19.5.img again, here is a screenshot of uboot, after that the screen loses signal and device does not boot (checked through dhcp on router).

I planned to upgrade and skip current 5.18 (EOL) with edge 5.19 or just use LTS 5.15. Offcial images 5.19/edge (e.g. Armbian_22.08.1_Nanopct4_sid_edge_5.19.5.img.xz) won't boot at all, maybe a short uboot screen. Using uboot v22.04 like other rk3399 boards did not fix it. SInce the nanopct4.conf is boardfamily=media but also works with rockchip64 (which was changed some time ago), building with boardfamily=rockchip64 current 5.15 or edge 5.19 works fine, the cli builds boot as expected. Maybe a general question, which bordfamily fits now best to nanopct4. I remember exactly problems which were fixed bei 150balbes maintainer when pulling it to media. Thankfully all patches found their way to rockchip64, which seems to be more active for rk3399 in general. Do you have any plans to combine them again?