Andrea

Thank you @going, I will evaluate this.

Is it possible just to rebuild the kernel, without fetching kernel updates and reapplying patches? I would find it useful to develop kernel drivers like in a development cycle.

Any success with this? I have the same question

A custom designed board around H616.

Hi all, is it possible to flash the a board's eMMC via USB from another PC? I already checked this but could not figure out exactly how. Thanks in advance, kind regards

Thanks for the advice!

Hi all, Armbian v23.11 build fails while compiling ATF, reporting weird "cannot find cr" message: https://paste.next.armbian.com/evewilodap Can you please help? Thanks in advance!

Charge pump is a very simple topology of DC-DC switching converter, normally driven by SoC PWMs. I have checked the DT yaml, but could not find anything useful. I found a PWM driver for Allwinner H6, but it does not work (I get error -22, EINVAL when loading the driver module).

Is it possible to rebuild the kernel without reapplying all the patches?

Hi all, I would like to use the PWM1 in order to drive a charge pump, but I am struggling to enable PWM using the DTB on Armbian v23.11. Anyone succeeded in configuring PWMs in H616? Thanks in advance!

I confirm that using an updated kernel (6.7.3) the build succeds. Linux armbian 6.7.3-060703-generic #202401311935 SMP PREEMPT_DYNAMIC Thu Feb 1 00:46:47 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux Thank you very much!

Despite the fact the problem is very similar, I am not using WSL2 to build. I am using a Ubuntu VM : Ubuntu 22.04.3 LTS (GNU/Linux 5.15.0-94-generic x86_64) andrea@armbian:~$ uname -a Linux armbian 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux User adeepn confirms that it happens also on Ubuntu w/kernel 5.15. I will try to upgrade to 6.1 and let you know. Thanks for the hint

Hi @Werner, yes of course: https://paste.next.armbian.com/pakisigigu

Hello all, I am receiving this error while building the image: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on /dev/loop0 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. I am . This happens in the partitioning phase (lib/functions/image/partitioning.sh line 229, using branch "v23.11" commit bba856bb57823556e12fa180284c7490fdd3708d😞 run_host_command_logged partprobe "${LOOP}" Investigated a lot, tried to unmont the image, losetup -d the loop device but nothing helped. Can you please help me? Kind regards, Andrea

Hi @Igor, thanks for the hint. I thought PREFER_DOCKER=yes was the default, however I will give it a try. Host OS is Fedora 39, kernel 6.5.12-300.fc39.x86_64 and qemu version 2:8.1.1-1.fc39. Kind regards