umiddelb

Members
  • Content Count

    116
  • Joined

  • Last visited

About umiddelb

  • Rank
    Elite member

Recent Profile Visitors

1354 profile views
  1. Hm, there are two ways to do that: You can try to chainload the u-boot binary from SD card with the help of the SPI u-boot. The SPL may check the presence of a SD card and try to load the u-boot binary from there instead of SPI flash. The first option requires some u-boot script hacking but should work with the existing firmware while the second option needs a modified SPL.
  2. I assume that you want to start Linux from SD card instead of SATA, right? This is different from loading the board firmware form SD card instead of SPI flash. The firmware should be able to boot Linux from any device, no matter where the firmware is actually stored. You may post the u-boot environment (the output of `printenv`) here.
  3. IMHO some of the recent mainline u-boot versions had difficulties to save the u-boot environment, which means that `saveenv´ will override not only the environment itself but also code-parts nearby, rendering the firmware unusable. Therefore changes to the u-boot environment can only performed at build time for some boards.
  4. You need to add the relevant executables echo \ '#!/bin/sh . /usr/share/initramfs-tools/hook-functions copy_exec /sbin/e2fsck /sbin copy_exec /sbin/fsck /sbin copy_exec /sbin/fsck.ext2 /sbin copy_exec /sbin/fsck.ext4 /sbin copy_exec /sbin/logsave /sbin' \ | sudo dd of=/etc/initramfs-tools/hooks/e2fsck.sh sudo chmod +x /etc/initramfs-tools/hooks/e2fsck.sh before building the initrd sudo update-initramfs -c -k ${kver}
  5. You may try to load an uImage instead of the vmlinuz image. This incorporates with the vendor u-boot firmware.
  6. This is the pin layout of the serial console adapter for all Odroid models. The Amlogic and Rockchip boards run the serial console with a 3.3 V UART therefore ...
  7. I can get in touch with the odroid guys to change this situation if you want.
  8. I've talked to some Turris people at FOSDEM 2019, they are using the same SoC and they've published the kernel source code and u-boot source code. Chances are that the EspressoBin might benefit from the MOX kernel, as the Turris people have added support for some additional hardware the SoC comes with.
  9. There is a similar issue here: "... Figured it out. Two kernel configuration options were in play: CONFIG_COMPAT=y CONFIG_LSM_MMAP_MIN_ADDR=32768 Above is what is required to run armv5tel and armv7hl chroots on aarch64. Default for the latter option is 65535, which prevents 32-bit binaries from running. Up and running with 4.9.153 now. ..."
  10. Here's a reference for an open source project using jira ...
  11. Atlassian offers free-of-charge licenses for Open Source projects ...
  12. Any 3.3 V level UART USB dongle will do the job (for the C0/C1/C1+/C2), you can even use standard breadboard female cables to connect to the Odroid serial console pins:
  13. I plan to attend FOSDEM 2019, anyone else too?