martinayotte

Members
  • Content Count

    3746
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Calendar

Everything posted by martinayotte

  1. /boot/boot.env is only present if a u-boot "saveenv" has been executed. The 230454 file read is the /boot//boot.bmp logo ...
  2. DTBO loaded by U-Boot is always difficult to debug. Maybe you leave it out from U-Boot and try to load it dynamically using /sys/kernel/config/device-tree/overlays/ ? mkdir /sys/kernel/config/device-tree/overlays/myoverlay cat myoverlay.dtbo > /sys/kernel/config/device-tree/overlays/myoverlay/dtbo Then check any errors in "dmesg" ... "verbosity=7" would help, but only for kernel errors, not U-Boot errors ...
  3. You should not having touched the "garbage" chars, they are binary header of compiled script. To revert it as before, use this command : mkimage -C none -A arm -T script -d rockchip-fixup.scr-without-garbage-chars rockchip-fixup.scr Also, looking at your first screenshot of /boot/armbianEnv.txt, the "overlay_prefix=rockchip" should be on a single line, not the same line as "verbosity=1" ...
  4. It should work ! But be aware that variable doesn't include /boot/dtb path, but you still need to provide allwinner/ subpath, so it should be "fdtfile=allwinner/sun50i-h6-orangepi-lite2.dtb" ...
  5. Is there any reason for that ? Because there are images dedicated for OPiOne+ ...
  6. On all Rockchip SoCs, eMMC has boot priority over SDCard. If you wish to boot from SDCard, you need to stop U-Boot from eMMC by pressing <spacebar> multiple during early boot process, then you get into U-Boot command prompt. You can then tell U-Boot you wish to boot from SDCard by giving the "setenv devnum 1" command followed by "run mmc_boot" ...
  7. I will start working on that soon ...
  8. you should look here in cache/sources/linux-mainline/linux-5.4.y/Documentation/devicetree/bindings/display/
  9. I doubt since even "screenfetch" isn't part of Armbian images ...
  10. Nothing special, but maybe ‘struct rw_semaphore’ has changed across kernel versions and ‘owner’ has been removed. To get AUFS working, maybe it require a fix to RT patches to match that change.
  11. It looks like you try to achieve interfacing a 26 bits Wiegand keyfob reader ... Right ? In such case, I would rather dedicate a small MCU such Atmel328 doing this decoding job, and report the result over serial port to the BananaPi.
  12. Rockchip SoCs always have eMMC as boot priority. So, to boot from SDCard, you need to stop U-Boot from eMMC by pressing <spacebar> several times during startup. Then, at U-Boot command line, you can type "setenv devnum 1" followed with "run mmc_boot", it will then boot from SD.
  13. If it been seen on the I2C bus, you can try some library such as the one from Adafruit ...
  14. "Merge Request", equivalent to PR which is "Pull Request" ...
  15. Probably those dtbo were never been part of the build. Feel free to send a PR for this Makefile correction ...
  16. Then, maybe it is I2C speed issue ...
  17. Did you checked the presence of the device with "i2cdetect" ? Did you checked the permissions of /dev/i2c-1 and running your test script under proper user/group ?
  18. Sorry, I don't see any things which could be obviously wrong ...
  19. Are you using UART2 ? Because UART2 also use PA0/PA1 if enabled ...
  20. Which patch ? The one I've post on Dec 6th ? ... Sure !
  21. Not at all ! You are trying to build something that is not own by Armbian ... BTW, Jessie is now End-of-Life ...
  22. This <0> means to use default hardware spi-cs0, while the second argument to cs-gpios is the new gpio for CS1 ...
  23. The RAM chip needs an additional address line from the H3 SoC to decide if it is addressing the upper or lower bank of the memory. If the OPiPC PCB was designed in function to use 1GB, and didn't provided this additional address line to be compatible with 2GB chips, then this line will be left floating on the chip and can even not be limited to the first 1GB bank, but can even give random memory data depending of if the floating line will be treat as LOW or HIGH depending of the EFI, it will return the wrong data.