martinayotte

  • Content Count

    3887
  • Joined

  • Last visited

Everything posted by martinayotte

  1. In this specific case, since it is for exynos5420 which doesn't have any overlay mecanism yet, I will leave your PR as is ...
  2. Here is a quick/not-tested/incomplete overlay sources named gpio-line-names.dts : /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@1 { target = <&pio>; __overlay__ { gpio-line-names = "", "", "", "", "TX", "RX", "", "", "", "", "", "", "", "", "", "STATUS-LED", "MUTE", "SPDIF-OUT", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", "", ""; }; }; }; Then, compile it as DTB with this command : dtc -O dtb -I dts -o gpio-line-names.dtbo gpio
  3. Do you mean how to write an overlay ? Or do you mean how "gpio-line-names" is used ? Here is a general example from https://elixir.bootlin.com/linux/v4.7/source/Documentation/devicetree/bindings/gpio/gpio.txt gpio-controller@00000000 { compatible = "foo"; reg = <0x00000000 0x1000>; gpio-controller; #gpio-cells = <2>; ngpios = <18>; gpio-line-names = "MMC-CD", "MMC-WP", "VDD eth", "RST eth", "LED R", "LED G", "LED B", "Col A", "Col B", "Col C", "Col D", "Row A", "Row B", "Row C", "Row D", "NMI button", "poweroff", "reset"; }
  4. I don't see much other ways than doing it using overlays ...
  5. As I said months ago, you need to execute the backup using SSH ... ssh root@<ip_board_to_be_backup> "dd if=/dev/mmcblk1" | dd of=backup_image.img bs=100M
  6. The PCF8523 chip is a good one since it can trigger an alarm interrupt ...
  7. That is because "sun50i-h6-fixup.scr" doesn't handle "L" bank (and "H" bank as well) as you can see here : setenv decompose_pin 'setexpr tmp_bank sub "P(A|C|D|G)\\d+" "\\1"; setexpr tmp_pin sub "P\\S(\\d+)" "\\1"; test "${tmp_bank}" = "A" && setenv tmp_bank 0; test "${tmp_bank}" = "C" && setenv tmp_bank 2; test "${tmp_bank}" = "D" && setenv tmp_bank 3; test "${tmp_bank}" = "G" && setenv tmp_bank 6' Feel free to tweak that script and submit the fix in a PR... EDIT : adding "H" bank should be pretty easy, but for "L" bank, it would be a b
  8. But the ".config" I've provided is "default = no i2c", you need to turn most of those to "=y" instead of "is not set" ...
  9. Did you checked all the possible configs in your cache/source/u-boot/v2019.04/.config By default, "grep -i i2c" is showing : # CONFIG_I2C0_ENABLE is not set # CONFIG_I2C1_ENABLE is not set # CONFIG_I2C2_ENABLE is not set # CONFIG_SPL_I2C_SUPPORT is not set # CONFIG_CMD_I2C is not set # I2C support # CONFIG_DM_I2C is not set # CONFIG_SYS_I2C_DW is not set # CONFIG_SYS_I2C_IMX_LPI2C is not set # CONFIG_SYS_I2C_MXC is not set # CONFIG_I2C_EDID is not set
  10. Stop U-Boot using <spacebar> during USB can, then do "printenv" command and check the value of "fdtfile"
  11. 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 ...
  12. 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
  13. 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
  14. 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)
  15. Did you added also CONFIG_CMD_I2C=y to recompile U-Boot with I2C related commands ?
  16. Upgrade done ! No side effect seen until now ...
  17. Try using external 4K7 pullup instead of internal one ... BTW, which kernel are you using ?
  18. This line looks strange ... Can you try PA7 (pin 12) instead, and look again at /sys/kernel/debug/gpio ?
  19. 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 ?
  20. 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...
  21. 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...
  22. 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