ebin-dev

Members
  • Content Count

    124
  • Joined

  • Last visited

1 Follower

About ebin-dev

  • Rank
    Elite member

Recent Profile Visitors

444 profile views
  1. ebin-dev

    Recovery from espressobin installation mistakes

    You can try these settings to boot from SD or sata into 4.18.y (at the Marvell>> prompt) - no boot script is used in this case. If you intend to use the boot script you need to adapt /boot/boot.cmd (i.e. if you boot from sd into 4.18.y you should specify 'setenv rootdev "/dev/mmcblk1p1" ' and recompile boot.scr with 'mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr' on the command line within your OS)
  2. Have you seen this https://github.com/armbian/build/commit/9c7ce48f2b6cef71080ee6f04cca6f521f98df96 ? Have you tried # cat /sys/devices/system/cpu/cpu1/cpufreq/stats/trans_table ? I do remember that you should have returned your broken board.
  3. "Updated u-boot needs new default boot environment and new boot script (overwrite the one on your /boot media – needed only if you upgrade from < v5.59)". (see the EspressoBin download page)
  4. May be you did a reset while the 17.10 image was still loaded. Anyway - you can now also use the adapted environment settings on the EspressoBin download page (just changed by Igor). Boot priority with the load_script is: 1. USB, 2. SATA, 3. SD card, 4. eMMC
  5. The new 18.09 bootloader flash images are now available through the EspressoBin downoad page. Please remember that it is mandatory to reset the environment settings once the 18.09 image is loaded the first time (Marvell>> env default -a). Then the updated environment settings as shown on the EspressoBin download page should be used.
  6. Did you reset your environment settings ? Please use the new ones: setenv default -a setenv verbosity "2" setenv boot_interface mmc setenv image_name boot/Image setenv initrd_image "boot/uInitrd" setenv fdt_name boot/dtb/marvell/armada-3720-espressobin.dtb setenv fdt_high "0xffffffffffffffff" setenv rootdev "/dev/mmcblk1p1" setenv rootfstype "ext4" setenv initrd_addr "0x1100000" setenv usbstoragequirks "0x2537:0x1066:u,0x2537:0x1068:u" setenv fdt_addr "0x6000000" setenv kernel_addr "0x7000000" setenv loadaddr "0x8000000" setenv initrd_size "0x2000000" setenv bootcmd 'mmc dev 0; ext4load mmc 0:1 $kernel_addr $image_name;ext4load mmc 0:1 $initrd_addr $initrd_image; ext4load mmc 0:1 $fdt_addr $fdt_name; setenv bootargs $console root=$rootdev rw rootwait; booti $kernel_addr $initrd_addr $fdt_addr' setenv ethaddr F0:AD:4E:..... setenv eth1addr F0:AD:4E:..... setenv eth2addr F0:AD:4E:..... setenv eth3addr F0:AD:4E:..... env save
  7. @jrtaylor You are using the official 17.10 image: U-Boot 2017.03-armada-17.10.3-g06ad760 (Aug 26 2018 - 19:00:03 +0200). You need to set the environment settings as specified on the EspressoBin download page (bootloader script). (Before you apply the settings you can reset your environment to default values with Marvell>> env default -a ) The new 18.09 images as linked in my previous posting (not yet official) currently do not work with that script since load addresses were moved - therefore you need to use the environment settings shown above - only for those 18.09 images.
  8. There are some new bootloader flash images for the EspressoBin (see the parallel thread). U-Boot 2017.03-armada-18.09.1-ga92bd86-armbian WTMI-devel-18.07.0-6050fd5 atfv1.5(release):711ecd3 (Marvell-armada-18.09.4) It is mandatory to reset the environment settings and to use the new ones (load addresses have changed). Edit: 18.09 images with slightly improved performance: sbc-bench/17.10 vs. sbc-bench/18.09
  9. The current 18.09 bootloader images (compiled Sept. 5th, 21:49) do work fine with the adapted address ranges. (u-boot 2017.03-18.09 used, macronix support confirmed by @FoodGenius, 1g-2cs images tested) Booting from SD into the current Armbian Stretch 4.18.y image works fine with these environment settings: setenv default -a setenv verbosity "2" setenv boot_interface mmc setenv image_name boot/Image setenv initrd_image "boot/uInitrd" setenv fdt_name boot/dtb/marvell/armada-3720-espressobin.dtb setenv fdt_high "0xffffffffffffffff" setenv rootdev "/dev/mmcblk1p1" setenv rootfstype "ext4" setenv initrd_addr "0x1100000" setenv usbstoragequirks "0x2537:0x1066:u,0x2537:0x1068:u" setenv fdt_addr "0x6000000" setenv kernel_addr "0x7000000" setenv loadaddr "0x8000000" setenv initrd_size "0x2000000" setenv bootcmd 'mmc dev 0; ext4load mmc 0:1 $kernel_addr $image_name;ext4load mmc 0:1 $initrd_addr $initrd_image; ext4load mmc 0:1 $fdt_addr $fdt_name; setenv bootargs $console root=$rootdev rw rootwait; booti $kernel_addr $initrd_addr $fdt_addr' setenv ethaddr F0:AD:4E:..... setenv eth1addr F0:AD:4E:..... setenv eth2addr F0:AD:4E:..... setenv eth3addr F0:AD:4E:..... env save ... and the environment to boot from SCSI into a current Armbian Stretch 4.18.y image: setenv default -a setenv verbosity "2" setenv boot_interface scsi setenv image_name boot/Image setenv initrd_image "boot/uInitrd" setenv fdt_name boot/dtb/marvell/armada-3720-espressobin.dtb setenv fdt_high "0xffffffffffffffff" setenv rootdev "/dev/sda1" setenv rootfstype "ext4" setenv initrd_addr "0x1100000" setenv usbstoragequirks "0x2537:0x1066:u,0x2537:0x1068:u" setenv fdt_addr "0x6000000" setenv kernel_addr "0x7000000" setenv loadaddr "0x8000000" setenv initrd_size "0x2000000" setenv bootcmd 'scsi scan; scsi dev 0; ext4load scsi 0:1 $kernel_addr $image_name;ext4load scsi 0:1 $initrd_addr $initrd_image; ext4load scsi 0:1 $fdt_addr $fdt_name; setenv bootargs $console root=$rootdev rw rootwait; booti $kernel_addr $initrd_addr $fdt_addr' setenv ethaddr F0:AD:4E:..... setenv eth1addr F0:AD:4E:..... setenv eth2addr F0:AD:4E:..... setenv eth3addr F0:AD:4E:..... env save Edit: SCSI environment added Edit: Linked to https://dl.armbian.com/espressobin/u-boot/
  10. @kostap I have made available firmware images compiled with u-boot 2017.03-18.09 in my previous post. @FoodGenius now you have something worth trying.
  11. So here there is finally a set of new flash-images-18.09 (with u-boot 2017.03-18.09 and with macronix support - not tested) (patch provided by @kostap - thanks!). The official Armbian flash images are still version 17.10 as compiled on Aug. 26th (without macronix support). Edit: 18.09 images compiled with u-boot 2017.03-18.09, macronix support Edit: 18.09 images are confirmed to work on the 1g-2cs EspressoBin, but changes to the Armbian bootscript are necessary in order to boot Armbian images with the environment settings shown on the EspressoBin download page.
  12. Thank you for making public the issue with the unsupported Macronix chip. There is a corresponding warning on the EspressoBin download page. I have a reason to assume that this issue is already being dealt with. We have reverted back the flash-images to 17.10 as compiled on Aug. 26th since there still seem to exist some issues with the new 18.09 images that need to be resolved.
  13. The issue with your Macronix chip needs to be dealt with by the manufacturer - unannounced board changes leading to unsupported systems are not very pleasant.
  14. If I am compiling all of the images in one go and in parallel - indeed this time the file size of one or two images differ - I haven't noticed that. This would appear to be an effect of the compilers and/or OS used and could simply be avoided by compiling the images in sets of 4 - without any other changes. You can find the current images here. The 1g-2cs images are confirmed to be working. I have changed by build scripts so that this does not happen anymore. Sorry for the inconvenience.