martinayotte

Are you wish to use RTS as RS485 HalfDuplex control pin ? In such case, you will need another patch since the dw8250 driver doesn't support it. This patch will add RS485 emulation ... rs485-8250_dw.patch

Some answers could be found here : https://linux-sunxi.org/SPIdev Maybe you could details what you wish to accomplish ...

hummm ! Trying to prepare for commit my previous work, I faced a huge git merge conflict ... I had to do a new "git clone" to get rid of the conflict ... I'm now working on redoing every fixes one by one ... Maybe it will take few days ...

This thread reveal some bug present in fixup scripts that were not be updated since introduction of 5.x.y : I've done some fixes and committed this morning. You can either wait for new images, or build yourself a new image, or try to fix the sun8i-h3-fixup.scr yourself manually.

Right ! Good catch ! I seems that dashes/underscores issue appeared when we switched from 4.20.y to 5.0.y and still unfixed in 5.5.y . I will try to fix that in the following days ... In the meantime, Yes, you need to fix the overlay along the fixup script ... EDIT: During a second look, it seems that /proc/device-tree/__symbols__/ has underscores. So, maybe both are working. I will try to figure out ... EDIT2: Here is the commit : https://github.com/armbian/build/commit/281c8546954c7e6ec993c03632d701490464c36f

On my side, I'm planning to commit my work for Allwinner 5.6.y, since it now without RCs ...

Although hardware is "slave" capable, the linux kernel driver is not capable.

by executing this command "uname -a" ...

SPINOR flash could be setup to have U-Boot inside which will allows to boot from and having RootFS on a USB drive, while no SDCard needed anymore ...

... and check the partition layout of this image to figure out why it try to mount /dev/mmcblk1p2 ...

I don't think so, because eMMC is /dev/mmcblk2 ... But /dev/mmcblk1p2 means second partition, where ususally Armbian have a single partition. What image are you using ?

Maybe around 5-6 secs after releasing the "reset" button. In other words, it until you see "Starting Kernel" on Serial Debug port...

eMMC has boot priority on RK3399. So, You need to temporarily disable it byt pressing "boot" button and kept it pressed for few second while pressing "reset" button ...

Ah ! Ok ! I didn't have HDMI connected, so it wasn't emergency mode, but plain console on Serial without login prompt ... EDIT: Right ! The KODI interface is there and working, at least the few setups I've done ...

No, since all Allwinner's SoC has boot priority on SD. I know it is a bit weird, but in my case, HDMI is working ...

Ok ! I've downloaded RK3399, copied its boot.scr and placed it on the SD, it got a bit further : there was a reboot in the middle of the process, then it booted in some kind of emergency mode without login prompt. And here is the "dmesg" :

OPi3 has eMMC while OPiLite2 doesn't . HDMI is working fine on my OPi3 using 5.6.0-rc3, although I don´t have "desktop" and stay at "headless". So, maybe try another HDMI monitor ...

Here it is : => printenv arch=arm baudrate=115200 board=p200 board_name=p200 boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr} boot_efi_binary=if fdt addr ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr ${fdtcontroladdr};fi;load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootaa64.efi; if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_syslinux_conf} boot_prefixes=/ /boot/ boot_script_dhcp=boot.scr.uimg boot_scripts=boot.scr.uimg boot.scr boot_source=sd boot_syslinux_conf=extlinux/extlinux.conf boot_targets=romusb mmc0 mmc1 mmc2 pxe dhcp bootcmd=run distro_bootcmd bootcmd_dhcp=if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;setenv efi_fdtfile ${fdtfile}; setenv efi_old_vci ${bootp_vci};setenv efi_old_arch ${bootp_arch};setenv bootp_vci PXEClient:Arch:00011:UNDI:003000;setenv bootp_arch 0xb;if dhcp ${kernel_addr_r}; then tftpboot ${fdt_addr_r} dtb/${efi_fdtfile};if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r}; else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi;fi;setenv bootp_vci ${efi_old_vci};setenv bootp_arch ${efi_old_arch};setenv efi_fdtfile;setenv efi_old_arch;setenv efi_old_vci; bootcmd_mmc0=devnum=0; run mmc_boot bootcmd_mmc1=devnum=1; run mmc_boot bootcmd_mmc2=devnum=2; run mmc_boot bootcmd_pxe=dhcp; if pxe get; then pxe boot; fi bootcmd_romusb=if test "${boot_source}" = "usb" && test -n "${scriptaddr}"; then echo '(ROM USB boot)'; source ${scriptaddr}; fi bootdelay=2 cpu=armv8 distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done efi_dtb_prefixes=/ /dtb/ /dtb/current/ fdt_addr_r=0x08008000 fdtcontroladdr=7df63e38 fdtfile=amlogic/meson-gxbb-nanopi-k2.dtb kernel_addr_r=0x08080000 load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile} mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi pxefile_addr_r=0x01080000 ramdisk_addr_r=0x13000000 scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;run scan_dev_for_efi; scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done; setenv devplist scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${efi_fdtfile}; then run load_efi_dtb; fi;done;if test -e ${devtype} ${devnum}:${distro_bootpart} efi/boot/bootaa64.efi; then echo Found EFI removable media binary efi/boot/bootaa64.efi; run boot_efi_binary; echo EFI LOAD FAILED: continuing...; fi; setenv efi_fdtfile scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${boot_syslinux_conf}; then echo Found ${prefix}${boot_syslinux_conf}; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done scriptaddr=0x08000000 soc=meson stderr=serial@4c0 stdin=serial@4c0 stdout=serial@4c0 vendor=amlogic Environment size: 3591/8188 bytes => I don't have any RK image, only Armbian, so I will try this one . Still, that image looks strange to me since ROOTFS is empty ... EDIT: With the Armbian boot.scr, it try to executed it and fail (because Armbian is looking for Image), and continuing with same earlier fail : switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot.scr 3056 bytes read in 3 ms (994.1 KiB/s) ## Executing script at 08000000 26660 bytes read in 7 ms (3.6 MiB/s) Bad Linux ARM64 Image magic! SCRIPT FAILED: continuing... 26660 bytes read in 7 ms (3.6 MiB/s) MMC Device 2 not found no mmc device at slot 2

Right ! I'm struggling to figure out how to make it boot, looking at "printenv" don't shows me why it try to boot from "mmc 2" where it is supposed to be 1. => fatls mmc 1 dtb/ 175 uEnv.txt 224 android_disable.sh 223 android_enable.sh 1732 ddbr-backup.sh 1710 ddbr-restore.sh 3433 install2emmc.sh 26386440 KERNEL 124035072 SYSTEM 48 KERNEL.md5 48 SYSTEM.md5 10 file(s), 1 dir(s) => ext4ls mmc 1:2 <DIR> 1024 . <DIR> 1024 .. <DIR> 12288 lost+found 0 .please_resize_me => As you can see, the second partition is empty, and during startup, it seems to wish to load something from partition 2 after successfully loaded the DTB, although kernel is on partition 1: Scanning mmc 1:1... 26660 bytes read in 6 ms (4.2 MiB/s) // <--- DTB loaded successfully MMC Device 2 not found no mmc device at slot 2

Good suggestion !

It doesn't boot with SDCard alone : http://ix.io/2faw

Change verbosity=7 in /boot/armbianEnv.txt and redo a capture of the serial log ...

In my case, I got it working by disabling NetworkManager and used the "old school" /etc/network/interfaces.

Did you try to use the same SDCard from the working one into the other one ? Yes, there is a SPINOR flash, but since SPI isn't enable, it should not interfere ... BTW, the whole thing remind me a 2 years old thread here : Do you have UART3 overlay in /boot/armbianEnv.txt ? The PA13/PA14 pins would be in-use if UART3 is enabled ...

It should show something, but without newline, only at left of command prompt, it must be either "okay" or "disabled" Are both boards are identical, same revision number ? I don't understand the question ... I doubt, i says "already in use" ...