[Bug 1847500] Re: Full RAM on Pi4 isn't accessible when using u-boot

[Hui Wang]

The uboot of armhf and configs I used for testing are:

https://github.com/agherzan/u-boot.git commit
a671dabc696fc9505641b418f473ce6c6792af93 (HEAD -> v2019.07-rpi4-wip,
origin/ag/v2019.07-rpi4-wip)

hwang4 at hwang4-Vostro-5390:~/work/uboot/u-boot$ cat boot.cmd 
setenv fdt_addr_r 0x03000000
fdt addr ${fdt_addr_r}
fdt get value bootargs /chosen bootargs
setenv bootargs "coherent_pool=1M 8250.nr_uarts=1 cma=64M bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:0E:9B:C4 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.fiq_fix_enable=2 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 fsck.repair=yes rootwait rootflags=noload net.ifnames=0"
setenv kernel_addr_r 0x01000000
setenv ramdisk_addr_r 0x03100000
fatload mmc 0:1 ${kernel_addr_r} Image
fatload mmc 0:1 ${ramdisk_addr_r} initrd.img
setenv initrdsize $filesize
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${initrdsize} ${fdt_addr_r}


hwang4 at hwang4-Vostro-5390:~/work/uboot/u-boot$ cat /media/hwang4/system-boot/config.txt
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2


enable_uart=1
#kernel=Image
kernel=u-boot.bin
device_tree_address=0x03000000
dtparam=i2c_arm=on
dtparam=spi=on
ramfsfile=initrd.img
ramfsaddr=0x3100000
#total_mem=2048

# Enable audio (loads snd_bcm2835)
dtparam=audio=on
disable_audio_dither=on


hwang4 at hwang4-Vostro-5390:~/work/uboot/u-boot$ cat /media/hwang4/system-boot/cmdline.txt
dwc_otg.fiq_fix_enable=2 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait rootflags=noload net.ifnames=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_compat_alsa=1 initrd=0x3100000,0x13c540b

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

Title:
  Full RAM on Pi4 isn't accessible when using u-boot

Status in u-boot package in Ubuntu:
  Confirmed

Bug description:
  Booting the latest eoan daily on a Pi4 with >1Gb of RAM, only the
  first 1Gb of RAM appears accessible:

      ubuntu at ubuntu:~$ free
                    total        used        free      shared  buff/cache   available
      Mem:         931920      185484      504748        3664      241688      723820
      Swap:             0           0           0

  However, adjusting the config.txt so that the kernel is booted
  directly without u-boot in between results in the full 4Gb being
  accessible:

      ubuntu at ubuntu:~$ free
                    total        used        free      shared  buff/cache   available
      Mem:        3884464      189852     3457504        3656      237108     3636004
      Swap:             0           0           0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1847500/+subscriptions