martinayotte

  • Content Count

    3850
  • Joined

  • Last visited

Everything posted by martinayotte

  1. Stop U-Boot using <spacebar> during USB can, then do "printenv" command and check the value of "fdtfile"
  2. Be aware that U-Boot and Kernel don't use the same DT file, you need to verify the one used in U-Boot build ...
  3. I've checked on my second OPi0 where I didn't upgrade firmware, so still previous version, and the issue is also present : [ 14.824376] xradio: XR819 device discovered [ 15.056442] xradio: hardware vers. 7.9 [ 15.056457] xradio: firmware vers. 8 (WSM), build 43, api 1060, cap 0x0003 [ 15.056460] xradio: Config USE_EXTENSIONS [ 40.809788] xradio TXRX-WRN: received frame has no key status [ 40.809802] xradio TXRX-WRN: dropped received frame [ 3653.654011] xradio WRN: BH: missed 4 consecutive interrupts! [ 5423.670767] xradio WRN: BH: missed 5 consecutive interrupts! [ 7584.760350
  4. After hours of investigation, and after having figured out that SPI for H6 wasn't working since 5.7.x, I've found why : missing SPI pins in DT ... https://github.com/armbian/build/commit/e3ade9e9f4292c6b257ad10f676edc4055106d2a
  5. I will try my best, but "time is the missing ingredient" as usual ... (I'm currently chasing why SPI0 doesn't work properly on OPiOne+ while it was with few earlier kernel versions)
  6. Did you added also CONFIG_CMD_I2C=y to recompile U-Boot with I2C related commands ?
  7. Upgrade done ! No side effect seen until now ...
  8. Try using external 4K7 pullup instead of internal one ... BTW, which kernel are you using ?
  9. This line looks strange ... Can you try PA7 (pin 12) instead, and look again at /sys/kernel/debug/gpio ?
  10. Is this still present ? Because 110 is wrong ... It is like you still have the default pin which is PD14 ... What "dmesg | grep w1" command is giving you ?
  11. BTW, I've found another glitch : I've built a 5.9.8 DEV Pinebook-Pro Desktop image and I didn't have WiFi working. I've figured out that no firmware were present in the image, I've copied them from previous 5.8.1 image...
  12. During my latest tests for Pinebook-a64, if I remember correctly, I've took from latest working build 5.7.6 the DTB and I tried to boot in either 5.8.0 or 5.9.1 images, screen is working during first phase of the boot, but then it switch to blank screen, either if it is a desktop or plain text image. So, it is not a DTB issue, but probably a kernel issue ... I tried to compare ".config" between 5.7.6 and other builds, but I didn't figure out what is missing, It maybe also be in the kernel code itself too...
  13. Ok ! I've never try this over on Rock64, but I did for some other Rockchip boards. So, I've just tried and figured out that U-Boot version was not supporting "setexpr" function, so fixup script failed : ## Executing script at 0900Unknown command 'setexpr' - try 'help' Unknown command 'setexpr' - try 'help' Unknown command 'setexpr' - try 'help' Unknown ' Unknown command 'setexpr' - tlibfdt fdt_getprop(): FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_BADPATH I will check to see if doing new builds will provided newer U-Boot for this board ... A
  14. No needs to do any modprobe since it is the overlay that will load them ... You need to specify GPIO1_D4 with "param_w1_pin" in /boot/armbianEnv.txt
  15. Just to avoid issue, please, add a git tag on DEV 5.9.x before doing any change for 5.10.x, this way it will make things easier to switch CURRENT to 5.9.x ...
  16. Glad to see that you figured it out !
  17. I suggest to decompile both DTB into DTS and compare them with "meld" ... Overlays are added using this patch : https://github.com/armbian/build/blob/master/patch/kernel/sunxi-current/general-sunxi-overlays.patch But looking at patches, I saw this patch, so maybe related : https://github.com/armbian/build/blob/master/patch/kernel/sunxi-current/board-cubietruck-enable-uart2.patch
  18. Those settings should be in /boot/armbianEnv.txt using an Armbian image ...
  19. Personally, I would not drive a 4 digits 7 segments display directly from SBC GPIOs, I would rather use a small MCU like Atmel328 or STM32F103 which will do all the scanning easily and would attach it to SBC using I2C bus for example ...
  20. Is there someone who did some builds for Pinebook-A64 recently ? Last build I've done recently are not bringing X11 desktop, neither 5.9.1 or older 5.8.0, the last one that still work on my Pinebook is 5.7.6 ...
  21. This error is there because you tried to compile original DTS outside kernel tree. You should rather decompile existing/working DTB into temporary DTS, edit this one, and recompile it into new DTB.
  22. I not very familiar with libgpiod and how gpio names are coming from the kernel. It seems that all gpios are uname on both Allwinner and Rockchip SoC, but seems that some are present in AmLogic. But looking at some of my AmLogic boards, it seems pretty dependent of pin headers of the specific boards by using "gpio-line-names" property in "pinctrl" node in DT. This is why Allwinner and Rockchip don't have names, there is no "gpio-line-names" property present in the DT ... EDIT: BTW, my AmLogic boards are NanoPi-K2 and Odroid-N2 ...
  23. You can turn it off by setting "PermitRootLogin no" in /etc/ssh/sshd_config ...
  24. At the end of the builds, the image files are written into output/images directory ...