going

Please decipher what you want to get in the end? You came up with the idea. And it is not included in my immediate plans. I just added your links to my browser bookmarks for the future. The idea is as follows: Today, in order to test the process of downloading a new image, I have to attach a UART-USB adapter cable to the device and to the desktop computer, run minicom in the terminal and read the running line. It seems to me it will be very convenient if the UART traffic from a specific device is routed to a specific Ethernet port and ends up in a log file.

Thanks for the links. This should be pretty easy to set up.

I understood. We can ask Alistair @ALIGMSTEN. He seems to have this device.

The first thing that came to mind was the DTB for this device. On the u-boot and kernel side.

I just put together an image with this new u-boot: linux-u-boot-bananapim64-edge (2023.07.02) The device is loading. The difference: 1) the build was done in my branch. My branch is in an unbalanced state, but it allows me to build almost any package. The assembly of images is unstable. 2) ATF : ATFBRANCH='commit:0cf5f08a205e4877c9daef5d90e1086643590226' - This v2.9.0 + 440 commits

No. On the contrary, we'll just fix the build process. I have found what needs to be done. @Gunjan Gupta I did not find in the build system the correct export of parameters when building with SCP: export SCP=/src/crust/build/scp/scp.bin and without using it. If SCP is not used, pass the parameter to ignore. export SCP=/dev/null It is necessary to add somewhere in this place or I do not know lib/functions/compilation/uboot.sh#L151

how-to-run-scripts-on-start-up run-script-boot-up-debian

In order for a doctor to make a diagnosis, he needs a patient. Tell us the build parameters. To narrow down the search, you need to know at least the version of the kernel that will be built.

Do you want to make an external power switch in this way? Do you want to send a signal to one of the pins of connector 40? Do you want the device to turn off? But at the same time, will the 5V power supply to the device be sold? There are pitfalls here. Are you interested in knowing them? And how will the external activation of the device be carried out?

I am a bad advisor in this kernel subsystem. But in dts from manufacturers, I have seen lines that reserve a certain amount of memory in a fixed region for a specific purpose. Check the processor's data sheet. Maybe it's a hardware limitation?

Maybe you can keep your blog here and interested people will join. I'm one of them.

What is the kernel version in ?

I didn't see any obvious crime in your changes. The question of why they are not applied is still open. The only assumption is that the dtb is already in the kernel or in initramfs. Show the contents of the file in the extlinux folder.

@Something Name The image you are using is something previously from the author Oleg @balbes150. This is some kind of early work. There is no support for allwinner D1 in the upstream kernel 5.19. Support starts with kernel version 6.3 riscv/boot/dts/allwinner/sun20i-d1-nezha.dts I don't think he will want to go back to the old images and support them. Try to use the last option on the 6.5 kernel: Nezha_D1/ArmbianTV/20230710-edge The author will be available soon. He's on vacation today. He will be able to help faster. By the way, it uses the extlinux mechanism to load the kernel. The /boot folder should have a directory of the same name with a boot configuration file.

Attach the archive of this received file to the message. highlight the changes with comments. I'll just look at it.

Are you trying to enable UART2? This is the source code: uart2: serial@2500800 { compatible = "snps,dw-apb-uart"; reg = <0x2500800 0x400>; reg-io-width = <4>; reg-shift = <2>; interrupts = <SOC_PERIPHERAL_IRQ(4) IRQ_TYPE_LEVEL_HIGH>; clocks = <&ccu CLK_BUS_UART2>; resets = <&ccu RST_BUS_UART2>; dmas = <&dma 16>, <&dma 16>; dma-names = "tx", "rx"; status = "disabled"; }; Somewhere at the bottom of the text of the dts you need to add something like this: &uart2 { pinctrl-0 = <&uart2_pb_pins>; pinctrl-names = "default"; status = "okay"; };

Describe in more detail the sequence of actions. Show what is in the /boot/armbianEnv file. Show under the spoiler the file before the changes, what has changed. And see how the dtb was applied directly on a working device: dtc --sort -I fs -O dts /sys/firmware/devicetree/base > $HOME/device_tree.txt

And please post your working overlay here when you finish successfully checking.

The overlay is not described quite correctly. Make in the image and likeness with this: This should be described in a separate fragment pinctrl-0 = <&spi0_pc_pins>; pinctrl-1 = <&spi0_cs0_pc_pin>;

Good! The driver is loaded. After you try to connect, no error messages appear in dmesg?

This is an interrupt for SPI But I don't see the mcp251x driver here. This line should cause the driver to load. Check the presence of the module in the kernel: grep -n CONFIG_CAN_MCP251X /boot/conf* Check the correct application of the overlay in the dts: dtc --sort -I fs -O dts /sys/firmware/devicetree/base > $HOME/device_tree.txt

OV5640_datasheet.pdf support for output formats: RAW RGB, RGB565/555/444, CCIR656, YUV422/420, YCbCr422, and compression maximum image transfer rate: QSXGA (2592x1944): 15 fps 1080p: 30 fps 1280x960: 45 fps 720p: 60 fps VGA (640x480): 90 fps QVGA (320x240): 120 fps And if you change the frequency, it is possible to increase the resolution. And how to do it?

Check the kernels available for installation directly on the device sudo apt update apt search linux-image | grep sunxi

Just build EDGE or install the EDGE kernel ready to confirm or refute my assumptions. P.S. BRANCH=edge Today it is the core v6.4.8

@Gunjan Gupta The problem may already be solved on the latest kernels. It may be enough to pull down some patches from megouse. Compare: megous-linux> gitk -100 origin/cam-6.1 megous-linux> gitk -100 origin/cam-6.4 And accept compliments in your address. You work very carefully. I adore.