search

edison-fw / meta-intel-edison

Here is the meta-intel-edison that builds, tries to stay up to date. Master is based on Yocto Poky Gatesgarth LTS 5.10.yy vanilla kernels. It builds a 32bit kernel (Gatesgarth branch 64bit) with ACPI enabled and corresponding rootfs. Telegram group: https://t.me/IntelEdison Web-site:
https://edison-fw.github.io/meta-intel-edison/
MIT License
60 stars 37 forks source link

btrfs support issue #122

Closed sideralis closed 3 years ago

sideralis commented 3 years ago

I compiled zeus branch on Ubuntu 20.04. This is working. I then tried to flash using the new btrfs support. Flashing is working but after reset it can't boot. U-Boot is starting but then I am getting this error message:

*** Ready to receive application ***

U-Boot 2020.10 (Feb 17 2021 - 17:06:16 +0000)

CPU:   Genuine Intel(R) CPU   4000  @  500MHz
DRAM:  980.6 MiB
WDT:   Started with servicing (60s timeout)
MMC:   mmc@ff3fc000: 0, mmc@ff3fa000: 1
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0
Target:btrfs
Partitioning already done...
Flashing already done...
Cannot lookup file /@boot/bzImage
Failed to load '/@boot/bzImage'
Cannot lookup file /@boot/initrd
Failed to load '/@boot/initrd'
Error: Invalid Boot Flag (found 0xffef, expected 0xaa55)
## Kernel loading failed ...
zboot - Boot bzImage

Usage:
zboot [addr] [size] [initrd addr] [initrd size]
      addr -        The optional starting address of the bzimage.
                    If not set it defaults to the environment
                    variable "fileaddr".
      size -        The optional size of the bzimage. Defaults to
                    zero.
      initrd addr - The address of the initrd image to use, if any.
      initrd size - The size of the initrd image to use, if any.

Unknown boot mode: boot
## Error: Can't force access to "bootargs_mode"
Saving Environment to MMC... Writing to MMC(0)... OK
Resetting to default boot mode and reboot...
resetting ...

Here is the output of sudo toFlash/flashall.sh --btrfs

Using U-Boot target: edison-btrfs
Now waiting for dfu device 8087:0a99
Please plug and reboot the board
Flashing IFWI
Download    [=========================] 100%      4194304 bytes
Download    [=========================] 100%      4194304 bytes
Flashing U-Boot
Download    [=========================] 100%       536576 bytes
Flashing U-Boot Environment
Download    [=========================] 100%        65536 bytes
Flashing U-Boot Environment Backup
Download    [=========================] 100%        65536 bytes
Rebooting to apply partition changes
Now waiting for dfu device 8087:0a99
Flashing boot partition (kernel)
Download    [=========================] 100%     20448256 bytes
Flashing home, (it can take up to 10 minutes... but you only have to do this once)
After this you can do fast over-the-air updates.
Download    [=========================] 100%   2068840448 bytes
Rebooting
U-boot & Kernel System Flash Success...
Your board needs to reboot to complete the flashing procedure, please do not unplug it for 2 minutes.

Any idea, anything I can check?

htot commented 3 years ago

That is strange. The first thing you can do is interrupt U-Boot by pressing escape. U-Boot allows you to ls the file system, you should be able to find /@boot/bzImage and /@boot/initrd, which is failing in the boot script. The question is of course, why does it fail?

It will also allow you to run do_rescue, this will take you into an initrd environment. Here you can see the mounted filesystems and inspect or repair them.

sideralis commented 3 years ago

In the meantime I flashed the normal image (without btrfs) to see if it was booting then reflash with btrfs and this is now working. So don't know what happened...

htot commented 3 years ago

Getting stranger then..

htot commented 3 years ago

Have you resolved this?

sideralis commented 3 years ago

Yes, you can close.