Thread history

Fragment of a discussion from Talk:R-Car/Boards/Kingfisher
Viewing a history listing
Jump to: navigation, search
Time User Activity Comment
No results

Hello,


I confirmed that Yocto v3.21.0 is booted on H3ULCB(ES2.0 8GB) + KF(M04).

I checked your boot log, and noticed IPL and U-boot is old.

So, please update IPL and U-boot, then try to boot again.


Best regards.

01:01, 27 March 2020

Thanks for your help!

I have to admit that the boot log from the link above is not mine (just the error was the same).

My u-boot and IPL is newer, here is my full log of the kernel Oops: https://pastebin.com/wiXmDzxz

It is a dual-boot system which can also boot Android (for development), so the bootloader is from the Android build. I hope that's not the problem?

Here is my u-boot environment: https://pastebin.com/qqw8cJJS

01:59, 27 March 2020

Sorry, I have never used android on H3ULCB + KF.

But, I tested Yocto v3.21.0 on H3ULCB(ES2.0 4GB) + KF(M04) again.

And I confirmed that it works.


How about using yocto bootloader ?

if yocto can be booted, android bootloder may not be good for yocto...


Best regards.

03:18, 27 March 2020

Thanks for your help Y.H. With the Yocto-Firmware it boots as expected.

How I need to get the Android part working again, but boota is not supported in the Yocto's u-boot. But that's a different story now.

07:44, 30 March 2020

Hello,


I prepared android 9 for H3ULCB(ES2.0 4GB) + KF(M4), and tested for booting yocto.

In my environment, yocto was booted with android's IPL and U-boot.


If you use old version of android, how about updating it ?

23:26, 1 April 2020

Thank you, this is very valuable feedback! I also used Android 9 with the same hardware as you have but for me it didn't work.


Would you mind posting the output of the full boot process including the u-boot environment varibles?

06:30, 3 April 2020