• Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
    Sydney, AUS

Recent Profile Visitors

1123 profile views

phelum's Achievements

  1. Granted it's not a very attractive suggestion. It does involve purchasing a specialised device and then learning how to use it. And it won't actually provide a solution, just some clues hopefully. Can you download the software release again and try with a different uSD card ? Or just try some other release to verify that the hardware is okay ? Cheers, Steven
  2. Hi, The M=/sr/src/... looks wrong to me. Shouldn't it be M=/usr/src/... ? Update: I think that this make has to be done on the system that built the kernel. This was the case with the old Realtek drivers I built for RPi kernels. The make needs a valid "build" softlink in the modules directory. This softlink is only valid where the modules were created. Cheers, Steven
  3. Hi, I think you need a serial cable connected to the UART0 port (try 115200 8N1). This will show you the U-Boot output. The U-Boot output should end with "Starting kernel ...". If you see nothing after this then either the kernel isn't starting or its bootargs are specifying the wrong console for output. The primary console in the bootargs should be "ttyS0,115200". I hope this helps. I don't know the board and are assuming it uses the standard Armbian boot script. Cheers, Steven
  4. Hi, Thanks for the pointer to the patches. I've applied some to the Denx master and it now works. I suspect the clock patches were the critical ones. Cheers, Steven
  5. Hi, I'm trying to generate a U-Boot for my OrangePi Plus board (H3). I'm using the Denx 2021.10 release and have tried the standard defconfig for this board and also variations of this config. Starting the kernel is fine but the kernel crashes/hangs when starting if I'm using HYP (nonsec) mode. Starting in sec mode works but this only enables one of the four CPU cores. The kernel crash/hang occurs while executing "udevadm trigger --action=add" but I can't determine exactly what is being enabled when the error occurs. Trying different kernels (including the Armbian 5.10 version) show no difference. The Armbian U-Boot (2021-10 dated August 2021) does work but I can't get a similar version even when I use the Armbian config from Can anyone provide a link to the Armbian source so I can find out what has been fixed for this H3 board. Perhaps a board_init function has been added. Thanks, Steven
  6. To enable U-Boot to boot an old kernel the U-Boot option CONFIG_ARMV7_NONSEC must NOT be selected. I suspect it is selected in the Armbian U-Boot. There is also the CONFIG_OLD_SUNXI_KERNEL_COMPAT option that apparently slows DRAM access and is sub-optimal for new kernels. I've tested with this option not selected and the OrangePi A20 board here works fine with both old and new kernels booting with this new U-Boot. Cheers, Steven
  7. Hi, I'm trying to boot a legacy 3.4 kernel using the current Armbian U-Boot but progress stops after U-Boot starts the kernel. The last line displayed is "Starting kernel ...". I believe the kernel (uImage) is being loaded at 0x48000000 and the script.bin is being loaded at 0x43000000. These values seem correct to me. Does anybody know if booting these old kernels is still supported with newer U-Boot ? I'd like to have one U-Boot that can handle both old and new. Thanks, Steven
  8. I've now made U-Boot from the latest release (2021.10-rc4) and it works.
  9. When I saw your original log listing all the failed overlay loads I assumed your "overlay=" line would be a long list containing all of them. But it's not and your single entry there looks fine to me. Can you try booting with no overlays and if it works then add entries to your "ovelays=" line one by one ?
  10. Hi, An "fdt" is a flattened device tree (e.g. sun7i-a20-bananapi.dtb) which will be in your /boot/dtb directory. The "-@" option is used when running dtc (the devicetree compiler) to create the fdt. It tells the compiler to include symbols details in the .dtb. These are needed so overlays can be applied. But you'll need the source files and compiler to create the .dtb and this shouldn't be necessary. I'm wondering if the first overlay (analogue-codec) is causing the problem. Can you try deleting it from your "overlays=" line in armbianEnv.txt to see what happens ? The fact that the "can.dtbo" overlay is not found might cause a problem. Does it exist ? Can you try deleting it from the "overlays=" line and see what happens ? Hopefully someone with more knowledge will chip in here and help. Cheers, Steven
  11. My slightly less clumsy solution is to modify the Makefile for each of these RTL drivers so the "src" variable is loaded correctly. The patch line is: export src := $(abspath $(srctree)/$(src)) This line must precede the "EXTRA_CFLAGS += -I$(src)/include" line near the start of each Makefile. Cheers, Steven
  12. Hi, Recently I generated a U-boot with SPL for an A20 OrangePi board but couldn't get it to boot. I've tried to debug this and the best I could do is find the SPL hangs/waits in a function called dread. The last display is "Trying to boot from MMC1". The U-boot version is 2021.10-rc3 from the site. After I overwrote the SPL on the SD-card with an older SPL everything is fine. I've tried changing various config options but just can't get the new SPL to work. Has anybody made a U-boot from this latest release and got the SPL to work ? Or can anybody tell me the .config settings used when building the Armbian version so I can compare them to mine ? Thanks, Steven
  13. Hi Igor, My problem is that making a kernel with your kernel (linux-source-current-sunxi_21.05.1_all.deb) is that the make fails when I make the RTL8189es driver. In the makefile for this driver there is the following line: EXTRA_CFLAGS += -I$(src)/include The "src" variable should be loaded with the path for the driver but instead it is being loaded with the base path for the kernel. The incorrect value means that the compiles fail because the driver specific include files aren't found. The same problem occurs with all the extra Realtek drivers you've added to the standard kernel. My clumsy solution here is to modify the makefiles to correctly load the "src" variable. But I'm thinking a better solution will be to make the driver separately after I've built the kernel and then add the driver module to it. Thanks for including these extra drivers in your kernels. A nice addition. Cheers, Steven
  14. Hi Werner, Is the source to the 5.10 kernel (with sunxi extras) available ? I've looked on github/armbian but couldn't find it. I'd much rather get the Armbian fork rather than the base version. With 5.8 for instance it had some nice improvements for my A20 cards. Thanks, Steven
  15. Thanks for your reply. Can you tell me where I can get the current kernel ?