Jump to content

lsartory

Members
  • Posts

    7
  • Joined

  • Last visited

  1. @ebin-dev, thanks for the clarification. That explains how the previous images were built, and where the error was made. I hope my changes will help prevent it from happening again in future builds.
  2. The change was merged. Hopefully it will help. It's a pity that no one maintains this, because the Espressobin has really nice hardware (when it works)!
  3. Indeed, the configuration in the mvebu64.conf script is wrong. The 2 CS 2 GB image is compiled with the same DDR topology parameter as the 2 CS 1 GB image (DDR_TOPOLOGY=2). It appears that the configuration for the 2 CS 512 MB version is also wrong, as it points to the same topology file as the 1 CS version. I guess this is not really a problem, because I'm not even sure that this variant actually exists. So to answer my previous question: What is used is only 512 MB from each chip. If anyone needs it, here is the bootloader (U-Boot 2018.03-18.12) compiled with the correct topology (DDR_TOPOLOGY=7): flash-image-ddr3-2g-2cs-1000_800.bin Note that only changing the DDR_TOPOLOGY from 2 to 7 was not enough, because this configuration is also missing from the Marvell sources, even though that's the parameter used in the build examples. The correct topology exists in the Armbian tree, but with the wrong name: https://github.com/armbian/build/blob/master/packages/blobs/espressobin/DDR_TOPOLOGY_2-2g.txt The A3700-utils-marvell/script/buildtim.sh script must also be adapted to accept a DDR_TOPOLOGY value higher than 6.
  4. Thanks for the log, shadow. I couldn't copy / paste it myself as I did not expect the issue. Which version were you using before ? Did you roll back ? Also, are the Espressobin U-Boot sources / configuration available somewhere so that we can build it ourselves ? I did not find anything in the Armbian GitHub, and the stuff on the Marvell GitHub is very obsolete.
  5. Yes, sorry, I forgot to mention it. I'm actually not entirely sure which hardware revision it is. I bought it in December of 2017, so it's clearly not a v7. Could it be a v4? It has indeed one DDR3 chip on each side.
  6. Hi everyone, I updated the Linux kernel on my Espressobin to the latest version (5.6.2) and had some issues booting from SATA as my SSD was not detected properly after boot. Using the device tree from an older kernel version did help, but I also read somewhere that updating to the latest Armbian U-Boot would solve the issue. So I downloaded the version that matches my hardware (flash-image-ddr3-2g-2cs-1000_800.bin) and flashed it. It indeed fixed the boot issues, but now only 1 GB of RAM is detected instead of 2 GB. This happens as soon as the board is powered on, in U-Boot: DRAM: 1 GiB Before that, I was using the U-Boot version from espressobin.net, and the 2 GB were detected and usable. I'm sure of it, because before downloading the Armbian U-Boot I checked the output to make sure that I indeed had the 2 GB version. I cannot do a downgrade to verify this right now, because the espressobin.net website is broken; most pages report a 404 error, including the one where the U-Boot files were located. I tried different versions, like the slower flash-image-ddr3-2g-2cs-800_800.bin or the version in the https://dl.armbian.com/espressobin/u-boot/archive/10/ folder, with similar results. I also tried the 1200 MHz version out of curiosity, and had to recover the SPI flash using the SATA rescue image. In any case, I would prefer to continue using the Armbian U-Boot version, since it is more up to date and works with the current mainline kernel and device tree. I did not find any answer for this in the forums or using Google. I actually find it very odd that it works at all. What is then used? Only one RAM chip? Or 512 MB from each? Did I install the wrong image, or did I miss a step when migrating U-Boot?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines