• Content Count

  • Joined

  • Last visited

  1. My Cubox i4pro is running Armbian. I'm using Apticron to notify me of package updates that are available for my system. Apticron usually tells me a short summary of what has changed with a certain newer version. Somehow, the armbian-firmware never shows this information. Is it available somewhere online? I would like to be able to verify what I'm updating so I can assess if there's a risk that something breaks...
  2. Well, good news: my Cubox is booting again! Thanks again for the support, Igor. Here's what I did: I looked at the definition of autodetectfdt that I mentioned earlier. I saw it sets two other variables: fdt_prefix and fdt_file. I figured out their values based on the results of printenv cpu and printenv board. Then I booted the Cubox with a micro-USB cable attached and stopped autoboot. I gave the following commands: setenv fdt_prefix imx6q setenv fdt_file ${fdt_prefix}-cubox-i.dtb setenv autodetectfdt "if test ${cpu} = 6SOLO || test ${cpu} = 6DL; then setenv fdt_prefix i
  3. Well, this is interesting... The autodetectfdt-related error is gone, but now I have this: Found U-Boot script /boot/boot.scr 907 bytes read in 98 ms (8.8 KiB/s) ## Executing script at 12000000 ** File not found /boot/dtb/-hummingboard.dtb ** ** Unrecognized filesystem type ** ** File not found /dtb/-hummingboard.dtb ** 5783761 bytes read in 483 ms (11.4 MiB/s) 5546904 bytes read in 427 ms (12.4 MiB/s) ## Loading init Ramdisk from Legacy Image at 14800000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5783697 Bytes = 5.5 MiB Load
  4. It might be completely wrong... But I noticed a definition for autodetect on GitHub. Imagine I would do the following: drop to the U-Boot prompt give this command: setenv autodetectfdt "if test ${cpu} = 6SOLO || test ${cpu} = 6DL; then setenv fdt_prefix imx6dl; else setenv fdt_prefix imx6q; fi; if test ${board} = mx6-cubox-i; then setenv fdt_file ${fdt_prefix}-cubox-i.dtb; else setenv fdt_file ${fdt_prefix}-hummingboard.dtb; fi;" give this command: saveenv reboot ... would that work? Or would it just completely mess up my U-Boot? ;-)
  5. Thanks for the reply! I've modified the commands a bit since the version of dd on my Macbook doesn't know/support them: sudo dd if=SPL of=/dev/disk3 bs=512 seek=2 78+0 records in 78+0 records out 39936 bytes transferred in 0.004992 secs (7999987 bytes/sec) sudo dd if=u-boot.img of=/dev/disk3 bs=1024 seek=42 235+1 records in 235+1 records out 240776 bytes transferred in 0.019943 secs (12073209 bytes/sec) But to no avail... Re-inserting the microSD in the Cubox, I still have ## Executing script at 12000000 ## Error: "autodetectfdt" not defined ** File not found /boot/dtb/ ** *
  6. Hi all, After years of running Armbian on my Cubox i4 without problems, I am suddenly in a situation that I don't understand. For some reason, I decided to reboot it, and now it doesn't work anymore. Using a micro-USB cable and my Macbook, I connected to the serial line to grab some logging: U-Boot SPL 2017.11-armbian (Jan 24 2018 - 22:39:16) Trying to boot from MMC1 U-Boot 2017.11-armbian (Jan 24 2018 - 22:39:16 +0100) CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz) CPU: Extended Commercial temperature grade (-20C to 105C) at 41C Reset cause: POR Boa