Radxa rock-pi-3a
Richard Kojedzinszky
richard at kojedz.in
Sat Apr 9 06:56:55 CEST 2022
Hi Kever,
Thanks for your reply! I greatly appreciate your work, really.
Additionally, can you please provide me sources of documentations, on
which you base your work? I am totally blind in this area, and I would
be interested in reading such kind of documentation of the SoCs.
Many thanks,
Richard
2022-04-09 04:28 időpontban Kever Yang ezt írta:
> Hi Richard,
>
> The ATAGs to pass the parameters is not available on the mainline
> U-Boot, and only use os_regs for the ram size for now, it do have the
> limitation for max 4GB now.
>
> There is a fix for this on the list, you can try it:
>
> https://patchwork.ozlabs.org/project/uboot/patch/20220222013131.3114990-12-pgwipeout@gmail.com/
>
>
>
> Thanks,
>
> - Kever
>
> On 2022/4/8 15:44, Richard Kojedzinszky wrote:
>> Dear community,
>>
>> I own a rock-pi-3a board with 8G ram. Right now, radxa's u-boot is
>> capable of detecting the whole amount during boot. Upstream u-boot
>> shows 1G of dram installed.
>>
>> I've started with evb-rk3568_defconfig.
>>
>> What I would like to achieve is that u-boot load grub-efi, to finally
>> boot the operating system. Howewer, with radxa uboot, and using
>> grub-efi, the kernel sees 4G only. If I boot the kernel image directly
>> from radxa u-boot, the whole 8G is visible. I assume that efi is
>> broken somehow, as I get multiple warnings from kernel regarding EFI
>> firmware.
>>
>>
>> Reading radxa's u-boot, it seems that it uses ATAGs do detect memory
>> size. Am I in the right way?
>>
>> Would it be beneficial to port some of that code to upstream u-boot,
>> or are there other solutions to detect correct memory size?
>>
>>
>> Thanks in advance,
>> Richard
More information about the U-Boot
mailing list