ebin-dev

Members
  • Content Count

    143
  • Joined

  • Last visited

2 Followers

About ebin-dev

  • Rank
    Elite member

Recent Profile Visitors

649 profile views
  1. Could you post the output of U-Boot 18.12.3 ? Does it recognise your SPI flash now ?
  2. The new 18.12 bootloader should also support issi flash (see the parallel thread).
  3. ebin-dev

    Update uboot is invalid

    @nasbdh9 @JDL : the new boot loader 18.12 is available now. See the parallel thread.
  4. Thank you for the update @kostap. I built all images for the EspressoBin bootloader (download links: flash-images, sata-images and uart-images). The bootloader is now updated to the following versions: U-Boot 2018.03-devel-18.12.3 atf-v1.5 Marvell-devel-18.12.2 WTMI-devel-18.12.0 SPI Flash supported: stmicro, winbond, gigadevice, issi V7 EspressoBins are supported - but Armbian Stretch and Bionic images have to be adapted to them. DDR3 images are for V3-V5 EspressoBins (i.e. V5, 1g-2cs, see log) and DDR4 images are for V7 EspressoBins. Please flash the images according to the instructions on the EspressoBin download page - just insert 'DDR3' or 'DDR4' into the bubt command string. EDIT: download links changed to dl..armbian.com
  5. ebin-dev

    I can not switch channels other than 36 and 44

    You can try to boot Armbian Stretch or Armbian Bionic with kernel 4.18.x and your preinstalled u-boot 17.x on your V7 EspressoBin based on the following environment settings (to be entered at the Marvell>> prompt): #boot from SD: env default -a setenv boot_interface mmc setenv image_name boot/Image setenv fdt_name boot/dtb/marvell/armada-3720-espressobin.dtb setenv fdt_high "0xffffffffffffffff" setenv rootdev "/dev/mmcblk1p1" setenv root root=/dev/mmcblk1p1 rw setenv rootfstype "ext4" setenv verbosity "1" setenv initrd_addr "0x1100000" setenv initrd_image "boot/uInitrd" 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_a;ext4load mmc 0:1 $fdt_addr $fdt_name_b;setenv bootargs $console root=$rootdev rw rootwait; booti $kernel_addr $initrd_addr $fdt_addr' saveenv #OR boot from SCSI: env default -a setenv boot_interface scsi setenv image_name boot/Image setenv fdt_name boot/dtb/marvell/armada-3720-espressobin.dtb setenv fdt_high "0xffffffffffffffff" setenv rootdev "/dev/sda1" setenv root root=/dev/sda1 rw setenv rootfstype "ext4" setenv verbosity "1" setenv initrd_addr "0x1100000" setenv initrd_image "boot/uInitrd" 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' saveenv
  6. ebin-dev

    Update uboot is invalid

    GlobalScale has published some stuff for the V7 EspressoBin here and here (based on the version 17.x bootloader). May be that is useful for you. Armbian uses the 18.x branch of the bootloader and the environment settings are adapted to it. Updated sources of the 18.x bootloader with support for the V7 EspressoBin are expected to be published by Marvell some time soon and updated versions of Armbian and the corresponding bootloader images for V7 EspressoBins will follow.
  7. ebin-dev

    Not getting gigabit speeds from lan to wan?

    You need to have a look at the distribution of tasks while the EspressoBin is being stressed. Do you use the latest bootloader flash-image? If you do not use a 1000_800 image you need to adapt the settings of /etc/default/cpufrequtils to available values output by 'cpufreq-info'. Otherwise the ondemand governor does not ramp up correctly. Such an issue was described some time ago here.
  8. Hi there, if you wish to support the yet another unexpected and undocumented change to SPI then you need to patch some files (see i.e. here and here). It should not be too difficult. Do you own a V7 EspressoBin ? I am waiting for Marvell to update their bootloader sources on Github. Support for the V7 EspressoBin is expected. Hopefully the above issue will also be solved.
  9. ebin-dev

    Not getting gigabit speeds from lan to wan?

    You don`t use the default network configuration. Masquerading is expensive and reduces bandwidth. You could try to redistribute tasks among CPU cores and to offload networking as far as possible.
  10. ebin-dev

    Looking for an enclosure for espressobin

    Globalscale is offering plastic and metal housings for the EspressoBin now ( see here ). They do not seem to use thermal coupling to the metal housing (separate heatsinks instead) - but you could implement it yourself with a suitable aluminium spacer.
  11. Please double check if any of your boards is equipped with DDR4 DRAM (not expected). You never know what kind of changes are suddenly introduced by GlobalScale these days ... If there are just DDR3 DRAM chips - then you can safely use the flash-images-18.09 (Macronix SPI is supported).
  12. The first board is a normal 2g-2cs board with Winbond SPI (Board version V5_0_1). You should be able to flash it as described on the EspressoBin download page. Armbian also supports EspressoBins equipped with Macronix SPI - but currently not yet V7_0-2 EspressoBins ! Just have a look at the board version indicated on the PCB. EDIT: board version corrected
  13. ebin-dev

    Update uboot is invalid

    Bingo! It is an 8gb DDR4 chip with 2400 Mbps (see here). All current Armbian flash-images-18.09 are for EspressoBins with DDR3 DRAM only.
  14. ebin-dev

    Update uboot is invalid

    @nasbdh9 It would appear that your 1g-1cs EspressoBin (V7_0-2) is equipped with DDR4 RAM. Could you post an image of the RAM chip ?
  15. ebin-dev

    Update uboot is invalid

    Yes - it was confirmed at least by FoodGenius in the parallel thread (see here - below the EDIT).