Jump to content


  • Posts

  • Joined

  • Last visited

Reputation Activity

  1. Like
    ManoftheSea got a reaction from barish in Making EspressoBin V7 work in 2022 ...   
    Ensign's Log, stardate... uh, today.
    I've contributed changes that build the FIT image as part of /etc/initramfs/post-update.d/99-uboot-fit, which means it'll be updated when new kernels are installed.
    I've also contributed changes that modify the boot.scr.uimg to use the FIT image rather than the legacy images, and which allows setting "board_version" in armbianEnv.txt to identify which FDT to use from the FIT image.  Options are "v5" and "v7", and the only known difference is the ordering of the ethernet ports.
  2. Like
    ManoftheSea reacted to FredK in Upgrade to 22.05   
    System successfully upgraded. No problems detected (so far).
    Thanks to the team.
  3. Like
    ManoftheSea got a reaction from lampra in stuck trying to flash uboot - "not allowed from main input shell"   
    Also, the "new bootscript" is no longer required with u-boot 2022.04.  They include the distro_boot method which finds the boot.scr, and that loads the kernel. 
    env default -a
  4. Like
    ManoftheSea reacted to usual user in The boot process and various devices   
    Now I would also like to dream:
    When commissioning a new system, I imagine that I will be offered a menu at the first boot in which all configurations available for selection are displayed. Since the SBC can't read my mind, at least I hope so, I choose the one I want. The system then starts and performs its first boot routine. At the next start of the system I wish for a dedicated menu of my previously selected boot option.
    I'll leave it up to you to explore what changes you think are necessary.
    Nevertheless, let's see how I would approach the matter in my dream. First, I would create a numbered extlinux.conf for each configuration selection with the following naming scheme: extlinux.conf-xx  with xx=01, 02, ...
    The initial extlinux.conf contains only the fail save boot options of the available configurations. In addition, I append a boot parameter of the following form to each append line: bootoption=xx with xx=01, 02, ...
    Then I write a shell script that searches /proc/cmdline for bootoption= and then copies the corresponding extlinux.conf-xx to extlinux.conf depending on the value found. Now I make sure that the script is executed as part of the first boot routine, and my dream should come true.
    Wait, do I have just developed a method how distro-boot can communicate to the running system which boot option for the successful boot has been used. Am I still dreaming now or is all this already really feasible?
  5. Like
    ManoftheSea got a reaction from Werner in Armbian 22.05 (Jade) Release Thread   
    22.05.1_espressobin_bullseye_current_5.15.35.img.xz - no issues on ebin v5
    22.05.1_espressobin_jammy_edge_5.17.5.img.xz - no issues on ebin v5
  6. Like
    ManoftheSea reacted to usual user in The boot process and various devices   
    Congratulations, now we are in business.
    It uses exactly what is described in your quote (https://www.kernel.org/doc/Documentation/arm64/booting.txt). The kernel is build with the Image.gz target and the firmware (uboot) decompresses it. And, surprise, uboot can automatically detect at what kind of kernel the extelinux.conf kernel key points. I have so much more to elaborate about what has been achieved so far, but no time right now. So I have to put you off on a follow-up post, please stay tuned.
  7. Like
    ManoftheSea reacted to usual user in The boot process and various devices   
    Please do not do this, it will prevent the usability of kernels installed at the same time.
    In the end, we won't use anything in /boot.
    Firmware (uboot) is the only device specific code and is dedicated to each SBC. Having it on the SD card prevents it usability for different devices. The best is if you can offload it in a SPI flash. There is not one uboot that suits everyone.
  8. Like
    ManoftheSea got a reaction from StarSurfer in Espressobin wont boot.   
    Hello, @StarSurfer,
    This is my fault, and something I'll need to repair for release.  I believe the fastest solution for you would be to mount your image and rename the file boot.scr.uimg to boot.scr .   This won't work because the boot.cmd was changed to use the newer u-boot default parameters.  Follow the directions below.
    Alternately, if you flash the latest u-boot (2022.04) and wipe the environment variables according to instructions I haven't posted to the espressobin page yet, the u-boot 2022.04 default boot looks for the boot.scr.uimg file.
    An initial pass of those instructions looks like, from the u-boot serial console:
    - env default -a
    - setenv ethaddr <YOUR_ADDR_HERE>
    - saveenv
  9. Like
    ManoftheSea got a reaction from StarSurfer in Espressobin wont boot.   
    Since we build our own kernel instead of using Debian's upstream, sometimes the kernels are tuned to the device, and sometimes the kernels are detuned through mistake or optimization.  For instance, my own kernel builds have turned off a LOT of device drivers, it's the difference between a 180 minute build and a 25 minute build.
    If you would like the Armbian builder to build modules that you use, please submit a PR against https://github.com/armbian/build/blob/master/config/kernel/linux-mvebu64-current.config or linux-mvebu64-edge.config.
  10. Like
    ManoftheSea reacted to Pali in Making EspressoBin V7 work in 2022 ...   
    There are Espressobin variants with just 512MB of memory. So if your image needs to be compatible with more variants, ensure that you place all parts in first 512 MB of RAM. I'm not sure where is running U-Boot after relocation and where it is malloc area. So choose address which does not conflict with it.
    You can look at RAM layout used on A3720 CPU:
  11. Like
    ManoftheSea reacted to Pali in Making EspressoBin V7 work in 2022 ...   
    USB 3.0 is 5Gbps, PCIe 2.1 is 5Gbps and SATA is 6Gbps.
    For loading you should use some unused space in RAM. Default value of of those variables should contain appropriate values. And they may change between releases, that is why addresses are in variables.
  12. Like
    ManoftheSea reacted to Pali in Making EspressoBin V7 work in 2022 ...   
    I have tested it on two different A3720 devices and on both it worked. And yes, it is clean U-Boot 2022.04 without any additional patches. So really do not know what can trigger this issue. There can be memory corruption or any other issue which could depend on linker layout, memory usage, etc... But as I cannot reproduce it, it is really hard for me to debug.
  13. Like
    ManoftheSea reacted to Myron in Is Ubuntu 22.04 LTS going to be a supported userspace environment when released on the 21st April?   
    Well...  In that case I have a space 32Gb SD card. I shall clone the working SD card, try and upgrade on the copy.  If it works, great.  If it does not, well....   Boo!!!
    I shall report back here with my findings.
  14. Like
    ManoftheSea got a reaction from Matthijs Kooijman in Improving / simplifying first-run services using systemd features   
  15. Like
    ManoftheSea got a reaction from lanefu in Improving / simplifying first-run services using systemd features   
    Sounds like a great use of available features.
  16. Like
    ManoftheSea reacted to Shirohige in Load U-Boot from SD card on Espressobin v5   
    @ManoftheSea Yes, as mentioned in my previous post, I came to the same conclusion. It seems that v5 cannot do it, but v7 can. I have already bought the v7 and now I am trying to get it to download the bootloader from from SD card. So far no luck.
    Also you are correct, my links are not applicable to the problem. However, I have no better links. I am unable to find any link with a description of how to download the bootoader from SD card, be it with espressobin v5 or with v7.
    The depictions and tables from the link you posted (http://wiki.espressobin.net/tiki-index.php?page=Ports+and+Interfaces#Boot_selection) also seems to be weird. If you look at the table for v7, all the boot modes (other than NOR)  seem to have the same jumper setting. This cannot be correct. Also the order of jumpers for v7 is wrong in the table. The order on the real board is J3, J11, J10, which is quite irritating when using the table to check your settings. This goes further, the depictions and tables for the v5 are flat out wrong. The table says that "NOR boot" is J11=1, J3=0, J10=0, but to get it to boot from NOR flash I actually have to sett it to J11=0, J3=0, J10=1. This sucks and took some time to figure out.
    Long story short: I cannot find any source with a description of how to download the bootloader from SD card with espressobin v7. Maybe I should open a new thread for that.
  17. Like
    ManoftheSea reacted to dasbee in espressobin: Update to 5.85 results in kernel panic   
    Fair enough.  It depends on how I configure the routing, to be sure.  This is going to be much more capable than a raspberry PI in a like configuration which was the other likely candidate.  While I could configure a PI4 as a single-armed router, the EB design provides for more direct routing configuration.
  18. Like
    ManoftheSea reacted to Jbobspants in Espressobin - etherchannel?   
    Yes, like @ManoftheSea pointed out above, we are aware that the three onboard ports have a 1gig bottleneck at the SoC. However, with a 1gbps mPCIE card in addition to one of the built-int ports, there is a theoretical 2gbps path. I was only testing the lan0 + lan1 etherchannel group with the sole purpose of trying to get any of the built-in ports to show up in an etherchannel/bond interface (unsuccessfully, so far).
    @lanefu, I appreciate your experience and insight, and I'd say you're right-on with your assessment of "typical" traffic going to a home fileserver. You have a good point to level-set for anyone coming across this thread, and this most certainly wouldn't be a great option for a HTPC or home media server. From my perspective, however, the Espressobin has a [theoretical] 6gbps path to SATA, but it's a shame the network bottlenecks to 1gbps. In my hypothetical use-case, there would be several hosts simultaneously accessing data on this server. Each of those hosts would have a single 1gig NIC, so of course there would be no point in going above that speed for any single connection. However, as more and more hosts try to access this share a the same time, a handful of 1gig clients could easily exceed a single interface, so an etherchannel would make sense.
    Also, my experience comes from a work environment where a single link is a potential single point of failure. We don't install anything without redundant links, and an etherchannel is a great way to allow for automated failover in the even of one link failing without having to run some additional heartbeat software. I realize that's probably not something your typical home user is concerned with, but IMO it would be cool to have.
    One final note along the lines of @lanefu's post, I should mention that in all my tests so far with dual 1gig links to the Espressobin, I am hitting a CPU bottleneck before ever getting close to 2gbps network speed. Obviously I don't have an etherchannel working yet (and I really don't know how that will affect CPU utilization for network throughput), but with one of the built-in ports on VLAN A, and the mPCIE port on VLAN B, using four other test boxes (2 on VLAN B, 2 on VLAN A), all doing reads, writes, or simultaneous reads and writes, I have been unable to achieve much over 100MB/sec total before the Espressobin cores both peg at 100%. I've done a few tests with NFS exports, and a few with NBD exports, but all my tests so far have been limited by the CPU on the server. I'll continue to test and tweak my setup, but at this point, I'm not sure this is the right platform for a high speed NAS server.
    All that said, I'm still trying to figure out how to add one of the built-in ports to a bond interface... Any suggestions would be greatly appreciated!
    Edit: Just to clarify, 1gbps (gigabits per second) is about 125MB/sec, minus overhead. 2gbps would be about 250MB/sec, give or take.
  19. Like
    ManoftheSea reacted to FlashBurn in Espressobin support development efforts   
    This is getting annoying. The deeper I look the more errors I find
    My fix seems to work. I tried my fix with the current uboot firmware´s supplied by armbian and these are my findings:
    - 1200 MHz: working fine, sbc-bench: http://ix.io/1BQ9
    - 1000 MHz: I´m still trying to find out why this wont work for me
    - 800 MHz: working fine, sbc-bench: http://ix.io/1BQr
    - 600 MHz: could work fine, if the cpufreq init code would not mess up; at the moment it is just running at 300 MHz, sbc-bench: http://ix.io/1BQF
    The problem with the 600 MHz is, that the parent clocks are running at 1200 MHz and a divider by 2 is used, but this is a problem for the cpufreq init code, because the cpu core frequency is 600 MHz and the cpu frequency which gets reported to the kernel is 600 MHz divided by the divider found in the dvfs which is 2.
    So to fix this problem, the parent frequency has to be taken to report the right frequency to the kernel. As I don´t intend to run at 600 MHz I will ignore this problem, but regard it as reported with this post. If someone wants to fix it and needs more information just ask.
    When I found out what the problem with 1000 MHz is and I fixed it, I will post the needed patches for fixing the cpu frequency for 800, 1000 and 1200 MHz.
  20. Like
    ManoftheSea got a reaction from Spemerchina in Is ESPRESSObin v7 Supported?   
    I have an EspressoBINv7, I'm running Armbian 5.72 (Stretch) with kernel 4.19.  It appears to be supported.
  21. Like
    ManoftheSea got a reaction from PlayingMuted in Is ESPRESSObin v7 Supported?   
    I have an EspressoBINv7, I'm running Armbian 5.72 (Stretch) with kernel 4.19.  It appears to be supported.
  • Create New...