[coreboot] How to check if DRAM init is OK?

ron minnich rminnich at gmail.com
Tue Aug 4 17:10:22 CEST 2015


it's an ARM. There was a primitive memory test in the early days of our ARM
ports that might be useful. It was simple but it caught our problems.



On Tue, Aug 4, 2015 at 7:18 AM WANG FEI <wangfei.jimei at gmail.com> wrote:

> How about MemTest86? See this link http://www.coreboot.org/Memtest86, I
> never use it before.
>
>
> On Tue, Aug 4, 2015 at 6:16 AM, Iru Cai <mytbk920423 at gmail.com> wrote:
>
>> Hi,
>>
>> I'm now porting coreboot to CubieTruck, a development board with an
>> Allwinner A20 SoC. I use Mr.Nuke's code[1] and Allwinner's user manual for
>> reference.However, when I modified the code and tested with the board, the
>> console gave only two lines of message and it get stuck. So I thought DRAM
>> init failed. I put some printks at bootblock_media.c, and found the bug
>> occurs at line 118[2], which showed the access of a certain memory space
>> caused the error. So I need to know how to check if the DRAM init works.
>>
>> Thanks
>> Iru Cai
>>
>> [1] https://github.com/mrnuke/coreboot/tree/cubie_mmc
>> [2]
>> https://github.com/mrnuke/coreboot/blob/cubie_mmc/src/cpu/allwinner/a10/bootblock_media.c#L118
>>
>> --
>> coreboot mailing list: coreboot at coreboot.org
>> http://www.coreboot.org/mailman/listinfo/coreboot
>>
>
> --
> coreboot mailing list: coreboot at coreboot.org
> http://www.coreboot.org/mailman/listinfo/coreboot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20150804/15186716/attachment.html>


More information about the coreboot mailing list