• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map





Everything posted by Igor

  1. If they are not in archive, you have to build them.
  2. If you get this working, send a PR (to dev and next) and you don't need to worry about In case board works well, we could also add an image ... we have it for some other CSC targets as well.
  3. This looks like you have boot loader compiled for eMMC ... or your hardware has eMMC and SD card wired the other way around (have seen that before). Try booting this image on a clean SD card: https://dl.armbian.com/cubox-i/archive/Armbian_5.94_Cubox-i_Ubuntu_bionic_default_4.9.179.7z
  4. I assume you now understand the fundamental change between legacy and mainline. Perhaps asking authors of this document @sgjava @5kft @Adrian Cuzman ... if they know how to solve https://opi-gpio.readthedocs.io/en/latest/install.html#non-root-access under mainline kernel?
  5. Each of those SPL's is prepared for different targets. I didn't experiment much with those. Apparently its possible to boot directly from SATA drive, but I never tried and I am not sure if boot scripts are capable to handle this without adjustements. BTW. Can you boot fresh image from the download section?
  6. https://docs.armbian.com/Developer-Guide_Build-Options/ add KERNEL_CONFIGURE="yes" to the build config or as a parameter to ./compile
  7. Yes of course. I completely forgot about Here is the recipe: https://github.com/armbian/build/blob/master/config/sources/cubox.conf#L48-L52 Sometimes order is also important ...
  8. 1234 https://github.com/armbian/config/blob/master/debian-software#L426
  9. https://docs.armbian.com/Developer-Guide_Build-Preparation/ kernel + dtb and u-boot come out deb packaged. You install them on the target and that's it. Only u-boot needs a special treatment - it used to update this way in the past but due to the problems we move it under manual update -> armbian-config -> system -> install/update boot loader ... for this case you don't need to update boot loader. Just remember to install image and dtb package. This is essential.
  10. USB is working under Buster but not your Z-Wave dongle? If that is the case, that is solvable by digging into the kernel config. You can do that on your own by recompiling kernel ... when you find out what is missing. Or just enable everything that looks related. Modern kernel for C1 needs to meet with developers/users. We are too small to cover this. Debian Stretch has troubles working with prehistoric kernels. Stock 3.10.y that comes with C1 is too old / on the edge. EOL Jessie is the only way. Or Xenial which is also on the way to become EOL. You will be alone fixing troubles there ...
  11. No. This is the way you flash boot loader to the SD card. For doing this you need some Linux computer where you will be attaching SD card for repair/boot loader flash. No. Especially if your boot script is identical to the one from Github. You probably don't need to touch boot scripts. You need to alter /boot/armbianEnv.txt and change /dev/sda1 for its UUID version.
  12. The problem is kernel. Modern kernel (in Buster image) is on experimental level, things are improving slowly - amateur development, while old is not supported anymore. And also not recommended to be used for something like that. I ran my Z-WAVE stuff on Allwinner H5 board, kernel 4.19.y To my knowing, USB should work, but not hot plugging. You have to boot with attached device. Make sure you read text on the download pages, especially "kernel issues".
  13. Type "how to extract a deb file" into the google then look for u-boot.img.sdhc $1/ = path of u-boot.img.sdhc file $2 = /dev/yourSDcard device ... usually /dev/sda (be sure that this is not your Linux system drive)
  14. boot binary are packed into deb files - extract them and DD to sdcard as noted previously. https://apt.armbian.com/pool/main/l/linux-u-boot-cubox-i-default/ boot.cmd and boot.scr (compiled version - how to is written in the end of the boot.cmd file). You need both. https://github.com/armbian/build/blob/master/config/bootscripts/boot-cubox.cmd
  15. Do you use Armbian? We do have an "universe" repository where this package come from: https://github.com/armbian/build/blob/master/lib/general.sh#L153-L163 https://packages.ubuntu.com/bionic/usbmount
  16. I did. Once again: You are referring to a wrong documentation and asking why it doesn't work. It is expected to fail and I told you that. (now the 3rd time and last time) Read this to understand background: https://linux-sunxi.org/GPIO Step by step documentation? I don't know if it exists. I will not search it nor make it for you - you have to invest your own time with the essential information which you got here.
  17. You have this? On which boards? Do we need to create a debug tool for our debugger?
  18. IIRC AXP driver in modern kernel has limited functionality. Not on the level as legacy ... but nevertheless you can communicate with AXP via I2C ... there are some manuals for this (Google) I would say this is simply a bug. But where? There are no logs, we don't have this hardware, we don't use this kernel ... This is how you check if you run official Armbian which we can try to support: https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity
  19. https://github.com/armbian/build/commits/master/config/sources/cubox.conf There were some major changes during this summer ... and we are very limited with testings changes on hardware. I am the only one dealing with this. Boot loader and kernel was updated which both represent major change. If your kernel was upgreaded and your u-boot not, this could explain the problem you are facing. Possible solutions: - updating u-boot manually https://github.com/armbian/build/blob/master/config/sources/cubox.conf#L51 - change kernel from next to default or vice versa This could be helpful: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-unbrick-the-system It could only be the problem of changing rootdev=UUID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  20. I believe its this change: https://github.com/armbian/build/commit/bea1df9ed6e4d1661c981ed488cd17dc2cf3d0e2#diff-4e3f23ec46130644ad2268eda44b6e3eR3356
  21. Most of the existing documentation is valid only for legacy 3.4.y kernel. Also on the one you are reffering to. On modern kernel, fundaments are changed (most likely to align with some standards). Kernel 3.4.y had Allwinner "standards".
  22. I think @selfbg from Olimex prepared overlays or/and instructions how to use their displays. Armbian does not support 3rd party hardware unless specially noted. Perhaps they are already present info at their images? Have you checked content of /boot/ directory?
  23. Noticed a week ago and its already fixed. Waiting that somebody checks/approves https://github.com/armbian/build/pull/1549