• Content Count

  • Joined

  • Last visited

About umiddelb

  • Rank
    Elite member

Recent Profile Visitors

1859 profile views
  1. I don't know if you have already read an article which I've written for ODROID Magazine a couple of years ago ("Das-U-Boot") .
  2. You may test the following approach: - have a look with `fdisk -l /dev/<sd card>` and find out where the first (and only) partition starts - copy with `dd bs=512 if=/dev/<sd card> of=<imagefile> count=<start sector of first partition> - copy the contents of /boot to a different location - look which file system features have been enabled for / (`tune2fs -l /dev/<sd card>`) - write the image file to a different sd card - delete and recreate on the different sd card the first partition according to the space requirements of /boot, make sure that your starting sector count stays the same - create a filesystem for the newly created partition and make sure that the features match the information you have gathered before, some bootloaders cannot deal with journaling nor with 64bit filesystems which are switched on by default - copy the contents of /boot back to your different sd card
  3. Where do you load the kernel image, dtb and initrd from, from sd card or from a network device as well?
  4. umiddelb

    Pinebook Pro

    With a different (and well known working at 3,3V) adapter, the PBP boots up fine. I can intercept the boot sequence and play around with the u-boot console. Next thing is to fix the serial console speed mismatch.
  5. umiddelb

    Pinebook Pro

    As the adapter is working when connected to a booted PBP, I suppose that the automatic voltage detection in the TTL adaptor does not work reliably and switches to 5V when connected to a switched off PBP.
  6. umiddelb

    Pinebook Pro

    You can have mine. But things might be complicated. I've seen that my PBP stopped booting when the serial cable was connected during boot. When the PBP has came up properly and I have then connected the serial adapter, everything looked fine and I've got a working console login.
  7. You might want to watch this talk here, Andre is explaining his ideas how to create a single generic firmware image.
  8. 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.
  9. 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.
  10. 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.
  11. 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/ sudo chmod +x /etc/initramfs-tools/hooks/ before building the initrd sudo update-initramfs -c -k ${kver}
  12. You may try to load an uImage instead of the vmlinuz image. This incorporates with the vendor u-boot firmware.
  13. 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 ...
  14. I can get in touch with the odroid guys to change this situation if you want.