From owner-freebsd-arm@freebsd.org Mon Aug 13 16:08:20 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E14010767C5 for ; Mon, 13 Aug 2018 16:08:20 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B2B2A80118 for ; Mon, 13 Aug 2018 16:08:19 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: by mail-qt0-x230.google.com with SMTP id c15-v6so17977741qtp.0 for ; Mon, 13 Aug 2018 09:08:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2WZCibrTN0pxPibXSfEQ1HCxtyxM8lTflNc49D+ttOk=; b=VGSB2altUW6T6qK3vSe21Rs5a2oxW5Mff3bzLTzvURHsWLK/7grpvozbJVnM+uJqC1 kh4iTwGNZHyFSd9VPglXLUyiDll8ZfglAWjZWd2DUYvvainZKQ+pEMpCQvyvyCtHKa5Q 88N8xUy8Lb3/fS8LME3rNbm/fJ6GGwzMDHJryHij8wAmDECgXWD0HPCjUfDAz5dCqEms r0DX8pNvEMEnuLS7JqFnrAJIoXZK5LCWcSbfcxtecDr6XSRONVD1J3+wHe9Ff8nbFTP2 1wRzckuYWEd1GD+yL8P2lDefEUzLd+dvpamk6/52jkKkhLGnnQsj7CHUoEC7uFNjyGeW ez/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2WZCibrTN0pxPibXSfEQ1HCxtyxM8lTflNc49D+ttOk=; b=hURHjnhiB0Tc2SwEyukeYNJtxmh9t5Y7zl5FYRdtA3tUyfViPJeSALrshoH1PsiCXL 7GNmvzxVtlN9IPlZAba0wTce0C16mnDMNTuGTfEZtaee/8hUs1L9s3ueReWnQDvb/J0Q S5EBKpRej1xwWg1F34SUqY+0nzl3lcLvg6T/O04M9T+PYtXdc8jJjaHFJjIALk6wp941 I0KKpMCgC70d2PwRBxoMMRmq4R5fEMBnW8o4IvjVXB/OdgzjQIBKXcxTw4TTY+csTTwD HaB8nDNzrCzT+aII8FSxgGlnsWkkRhGI33ikQ/JYyRcIZZtZOdMMgOe1h7a1qcOPhri8 SwZA== X-Gm-Message-State: AOUpUlGdGUcqPMC7DhSNCMjSeEmdgR0a6lGh6xLGZ5aYvt/0TvNMiA1S b0f+TASmVTB9R3v+DLPq/ayukYb1baUbqkKfuPMzp2em X-Google-Smtp-Source: AA+uWPxZ/jQxPWpUev6aZQHsHwrdryNiaFnfRqjO6nkePNd+9O0q9/cbN0dcgHG6Ew1cQkdPjfwF7L1iUKN78cbFDQM= X-Received: by 2002:a0c:c30f:: with SMTP id f15-v6mr15460536qvi.104.1534176499081; Mon, 13 Aug 2018 09:08:19 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:aed:29c3:0:0:0:0:0 with HTTP; Mon, 13 Aug 2018 09:08:18 -0700 (PDT) In-Reply-To: <1534020520.35460.1@hraggstad.unrelenting.technology> References: <1533577708.4175.0@hraggstad.unrelenting.technology> <1534020520.35460.1@hraggstad.unrelenting.technology> From: Ganbold Tsagaankhuu Date: Tue, 14 Aug 2018 00:08:18 +0800 Message-ID: Subject: Re: Rockchip RK3399 (ROCKPro64) boots to multiuser To: Greg V Cc: freebsd-arm Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2018 16:08:20 -0000 On Sun, Aug 12, 2018 at 4:48 AM, Greg V wrote: > > > On Sat, Aug 11, 2018 at 3:09 PM, Ganbold Tsagaankhuu > wrote: > >> >> >> On Tue, Aug 7, 2018 at 1:48 AM, Greg V >> 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. Ganbold