• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map





Everything posted by martinayotte

  1. Did you rebooted after adding "spi-jedec-nor" overlay ? Doing "cat /proc/mtd" command, is it reporting the presence of SPI partitions ?
  2. My "delete" commit was due to duplicate nodes already present in @megous branch, but I didn't check if his commits was coming from mainstream and were healthy ... It maybe not only DT issue, but from thermal driver, see here activities in his branch :
  3. I think you will save a lot of time if you restart from scratch : fresh SD image, make sure you add "spi-jedec-nor" overlay, and then reboot before doing a new "nand-sata-install" with "Boot from SPI, RootFS on USB".
  4. I've some OPiPC+ that still at RC3, and the bug is not present, while some other with RC6, the issue is there ... So, maybe @megous has committed something related to that ...
  5. This means your /boot directory of your USB drive is empty ... Copy the /boot from SDCard into the USB drive and tweak the /boot/armbianEnv.txt of this USB copy so that "rootdev" is pointing to proper UUID found by "blkid". EDIT: The issue of having empty /boot on USB is probably due to the fact that when you've ran the "nand-sata-install" you choose "boot from SD with USB rootfs". If you have added "spi-jedec-nor" overlay, "nand-sata-install" would have show you an additional option named "boot from SPI with USB rootfs", which would not caused the issue.
  6. I've 2x OPiZero booting from USB without issue ! I don't see where your setup is choking, but I would recommend to check it step by step : - stop U-Boot for getting command prompt. - do "usb start" for the scanning. - check your USB boot partition with "ls usb 0 /boot" to verify that everything is present. - finally, try to boot using "run usb_boot"
  7. It is not "fsk" but "fsck" ...
  8. No, I've an M2U and don't have the issue, as I've said it is probably that yours has a defective AP6212. You can avoid DTB updates using "apt-mark hold linux-dtb-dev-meson64_5.94_arm64.deb" for example.
  9. In the pull request, you mentioned : That is probably the reason ... My OPi3 is powered using the barrel connector with PSU 3.0A, never got any issue. It is well know, and also mentioned in a lot of posts on Armbian forum, that MicroUSB connector itself produce a lot of voltage drop on the contacts themselves when huge current is present, even if PSU is strong enough, you can see a 5.0V dropping around 4.5V on board side.
  10. Which commands ? To edit /etc/systemd/resolved.conf ? nano /etc/systemd/resolved.conf
  11. Reading "man resolved.conf" will help you to figure out, /etc/resolved.conf is created during boot using defaults from /etc/systemd/resolved.conf ...
  12. This MMC2 is for the WiFi, maybe the AP6212 is defective ... If you don't mind loosing WiFi, maybe you can decompile DTB into DTS, changing MMC2 node "status" to "disabled", and then recompile DTB from this edited DTS and reboot ! With luck, boot will maybe go further ...
  13. Writing directly to /dev/mmcblk1 (not mmcblk1p1) should erase partition table with a new one coming from eMMC. So, for your both cases, if SDCards is bigger than eMMC and still not able to write into it, this means those SDCards are crappy, maybe even fake ones, says for example they are 32GB but actually fails after only first few GBs ... You will then need to purchase good ones, well known brands, from trusted sellers !
  14. Your SDCard needs to be bigger than your eMMC !
  15. No ! The double needs to be around the whole command exucuted by the SSH, so "dd if=/dev/mmcblk2" or in your case "dd if=/dev/mmcblk1" , but let forget this first solution and stick with the second one : You should not use "/dev/mmcblk1p1" since it is only the first partition without partition table. With USB-SDCard adaptor plugged, it should be : dd if=/dev/mmcblk1 of=/dev/sda bs=100M
  16. Did you try using "nand-sata-install" ?
  17. Maybe I missled you : you need to do that command from a Linux PC shell, and I forgot the double quote around the first "dd" command (corrected in above post), it should be : ssh root@<ip_board_to_be_backup> "dd if=/dev/mmcblk2" | dd of=backup_image.img bs=100M The second "dd" command will make the writing of the backup_image.img locally on your Linux PC, so no needs to do a "wincp". If you are on Windows, that won't work ... Another way to do that backup would be to plug your USB-SDCard reader directly into the USB port of the SBC and doing the backup directly : dd if=/dev/mmcblk2 of=/dev/sda bs=100M But, in any case, you need to have a SDCard bigger than the eMMC size ...
  18. Right ! But maybe also with another reason : on my A20-Micro, both USBs are already enabled by the Main DT ... But I don't know for Cubietruck ... What "lsusb" is reporting ?
  19. I've my OPi3 with 5.3.0-rc3, and watchdog is compiled inside kernel, not as a module. Therefore, I've the /dev/watchdog and "dmesg | grep -i watchdog" is reporting the following : [ 1.830851] sunxi-wdt 7020400.watchdog: Watchdog enabled (timeout=16 sec, nowayout=0)
  20. Please, change /boot/armbianEnv.txt to have "verbosity=7" and "console=serial", you will then get more details after kernel been uncompressed ...
  21. I've my BananaPiM2Ultra running fine with 5.3.0-rc3-sunxi image built myself few weeks ago ...