[Bug 1806813] Re: Add Pi Compute Module 3 Support

[Łukasz Zemczak]

So actually the only thing we're missing for basic CM3 support is the
.dtb file. Apparently the linux-raspi2 kernel for arm64 does not provide
the .dtb due to misconfiguration. I have reported that to the kernel
team and they have prepared a fix for the next kernel cycle (ETA in some
weeks). In the meantime, for the upcoming .2 point-release, I'll work-
around it temporarily by using the armhf CM3 dtb through the gadget tree
configuration (as the rule is all binaries have to come from the
archive, so I can't just jam in a binary that's not built in official
repos). This way at least we'll have the images booting, before we can
get the right dtbs from the kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to flash-kernel in Ubuntu.
https://bugs.launchpad.net/bugs/1806813

Title:
  Add Pi Compute Module 3 Support

Status in flash-kernel package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in u-boot package in Ubuntu:
  Confirmed

Bug description:
  Hi all,

  Apologies if this is not the proper location for reporting this bug /
  feature request.  If there is a more applicable place for it, please
  just let me know.

  I have been doing some testing on the newly released Raspberry Pi 3
  64-bit ARM preinstalled server image located here:
  http://cdimage.ubuntu.com/releases/18.04/beta/

  I am particularly interested in running this image on the Raspberry Pi
  Compute Module 3 (the model that has 4gb of eMMC onboard, located
  here:  https://www.raspberrypi.org/products/compute-module-3).
  However, after flashing this Ubuntu Server image to the Compute Module
  3, U-boot is unable to locate a device tree and proceed with booting.

  The serial console output is:

  
  U-Boot 2018.03+dfsg1-2ubuntu1.1~18.04.1~test1 (Nov 20 2018 - 11:50:30 +0000)

  DRAM:  948 MiB
  RPI: Board rev 0xa unknown
  RPI Unknown model (0xa020a0)
  MMC:   mmc at 7e202000: 0, sdhci at 7e300000: 1
  Loading Environment from FAT... WARNING at /build/u-boot-B3y2jo/u-boot-2018.03+dfsg1/drivers/mmc/bcm2835_sdhost.c:437/bcm2835_send_command()!
  WARNING at /build/u-boot-B3y2jo/u-boot-2018.03+dfsg1/drivers/mmc/bcm2835_sdhost.c:437/bcm2835_send_command()!
  OK
  In:    serial
  Out:   serial
  Err:   serial
  Net:   No ethernet found.
  Hit any key to stop autoboot:  0
  libfdt fdt_check_header(): FDT_ERR_BADMAGIC
  No FDT memory address configured. Please configure
  the FDT address via "fdt addr <address>" command.
  Aborting!
  23914504 bytes read in 817 ms (27.9 MiB/s)
  18931168 bytes read in 648 ms (27.9 MiB/s)
  ERROR: Did not find a cmdline Flattened Device Tree
  Could not find a valid device tree
  U-Boot>

  
  I can flash and boot a default Raspbian image fine on this Compute Module 3, so, the hardware is functional.  I made a few attempts at configuring an FDT address as the error indicates, but was unsuccessful.  I also copied over a Compute Module 3 .dtb from Raspbian and placed it the boot partition of this Ubuntu image, but that was also a failure.  As you can tell, U-boot is not my area of expertise.

  It would be great if the CM3 was able to be supported out of the box,
  with no additional input or configuration needed by the user (such as
  is currently the case in Raspbian).

  Thanks in advance for any efforts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1806813/+subscriptions