Rockchip RK3399 (ROCKPro64) boots to multiuser

[Ganbold Tsagaankhuu]

On Tue, Aug 14, 2018 at 12:08 AM, Ganbold Tsagaankhuu <ganbold at gmail.com>
wrote:

>
>
> On Sun, Aug 12, 2018 at 4:48 AM, Greg V <greg at unrelenting.technology>
> wrote:
>
>>
>>
>> On Sat, Aug 11, 2018 at 3:09 PM, Ganbold Tsagaankhuu <ganbold at gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Tue, Aug 7, 2018 at 1:48 AM, Greg V <greg at unrelenting.technology>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I managed to boot FreeBSD on the Rockchip RK3399 SoC (Pine64 ROCKPro64
>>>> board):
>>>>
>>>> https://gist.github.com/myfreeweb/5f5b9e56f9a0fd1d63a46c34886f5ad1
>>>>
>>>>
>>> Very nice. I have NanoPC-T4 board and will test your patch.
>>> Did you try to load kernel via tftp at u-boot prompt? like:
>>>
>>> tftpboot 0x02000000 kernel.bin, go 0x02000000
>>>
>>> Does it work for you that way?
>>>
>>
>> kernel.bin?? EFI has always been the way to go with aarch64 (and I think
>> it's even recommended on armv7/6 too).
>>
>> I do it like this:
>>
>> env set serverip 192.168.1.2
>> env set bootargs boot.nfsroot.server=${serverip}
>> boot.nfsroot.path=/some/path comconsole_speed=${baudrate}
>> tftpboot ${kernel_addr_r} loader.efi
>> tftpboot ${fdt_addr_r} dtb/rockchip/rk3328-rock64.dtb
>> bootefi ${kernel_addr_r} ${fdt_addr_r}
>>
>> But the more-automated way (fully configured by dhcp) should work too, at
>> least if you don't have dhcp and tftp on different servers
>>
>
>
> Thank you.
> I've managed to boot NanoPC-T4 board with your patches using loader.efi on
> fat partition on SD card:
>
> http://dpaste.com/0Y00M4B
>
> I used rk3399-rockpro64.dtb, as rk3399-nanopi4-rev00.dtb is somehow not
> working for me.
>

Finally managed to do network boot to multiuser:

http://dpaste.com/2573EV8

Maybe will try again rk3399-nanopi4-rev00.dtb.

Ganbold



>
> Ganbold
>
>
>
>
>
>