[U-Boot] RK3399 boards (rockpi4 and rockpro64) kernel SError using upstream U-boot

Qu Wenruo quwenruo.btrfs at gmx.com
Mon Nov 18 07:37:07 UTC 2019



On 2019/11/18 上午10:51, Kever Yang wrote:
> Hi Qu Wenruo,
> 
> 
>     Please try with latest u-boot-rockchip with dram and board fix merged:
> 
> https://gitlab.denx.de/u-boot/custodians/u-boot-rockchip.git master branch

Compiled and installed, and still the same SError trying "memtest 3584M"
on my RockPi4 (4G RAM variant)

I guess now it's time to blame the rkbin I used?

The rkbin files I'm using is:
rk3399_ddr_800MHz_v1.23.bin
rk3399_miniloader_v1.19.bin

And for the trust.ini, it's
---
[VERSION]
MAJOR=1
MINOR=0
[BL30_OPTION]
SEC=0
[BL31_OPTION]
SEC=1
PATH=../rkbin/bin/rk33/rk3399_bl31_v1.29.elf
ADDR=0x00010000
[BL32_OPTION]
SEC=1
PATH=../rkbin/bin/rk33/rk3399_bl32_v1.20.bin
ADDR=0x08400000
[BL33_OPTION]
SEC=0
[OUTPUT]
PATH=trust.img
---

Since I'm completely new to the rk3399 boot sequence, would it be
possible that above binary files caused the problem?

Thanks,
Qu
> 
> 
>     Did you try with rkbin ddr.bin instead of TPL and keep other
> firmware(SPL, U-Boot, ATF),
> 
> this can confirm if there is something wrong in TPL dram driver or not.
> 
> 
> Thanks,
> 
> - Kever
> 
> On 2019/11/16 下午1:39, Qu Wenruo wrote:
>> On 2019/11/16 下午1:16, Qu Wenruo wrote:
>>> On 2019/11/15 下午10:59, Anand Moon wrote:
>>>> Hi Qu Wenruo,
>>>>
>>>> On Fri, 15 Nov 2019 at 17:27, Qu Wenruo <quwenruo.btrfs at gmx.com> wrote:
>>>>>
>>>>> On 2019/11/15 下午6:37, Qu Wenruo wrote:
>>>>>> A small update to this bug.
>>>>>>
>>>>>> I'm using mem=3584M kernel cmdline, to sacrifice 512M memory.
>>>>>>
>>>>>> And then surprise, memtest 3G works. (Originally it's 4G physical ram
>>>>>> and 3584M memtest.
>>>>>>
>>>>>> Hopes this could provide some clue.
>>>>> Oh no, with 3187M, it still crashes with SError.
>>>>>
>>>>> So still no luck.
>>>>>
>>>>> Thanks,
>>>>> Qu
>>>> Please this following series of patches for fix this error.
>>>> It fixed issue of SError on my board.
>>> Would you mind to share which commit it is based?
>>>
>>> For v2019.10 tag, it fails at the 13th patch.
>>> The same happened for current master.
>> Well, manually solved the conflicts.
>>
>> If anyone is interested in using that, I have uploaded it to github,
>> which is based on v2019.10 tag:
>>
>> https://github.com/adam900710/u-boot/tree/serror_fixes
>>
>> Unfortunately, still crashed for memtester 3584M.
>>
>> Thanks,
>> Qu
>>
>>> Thanks,
>>> Qu
>>>> [0] https://patchwork.ozlabs.org/cover/1195284/
>>>>
>>>> Best Regards
>>>> -Anand
>>>>
>>> _______________________________________________
>>> U-Boot mailing list
>>> U-Boot at lists.denx.de
>>> https://lists.denx.de/listinfo/u-boot
>>>
>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> https://lists.denx.de/listinfo/u-boot

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191118/4b828e34/attachment.sig>


More information about the U-Boot mailing list