Re: How to write u-boot bootloader for Jetson TX1

[Jared McNeill <jmcneill%invisible.ca@localhost>]

Can you try the following patch?

Index: arch/evbarm/include/bootconfig.h

===================================================================

RCS file: /cvsroot/src/sys/arch/evbarm/include/bootconfig.h,v

retrieving revision 1.9

diff -u -p -r1.9 bootconfig.h

--- arch/evbarm/include/bootconfig.h 1 Apr 2018 04:35:04 -0000 1.9

+++ arch/evbarm/include/bootconfig.h 17 Jun 2018 00:43:50 -0000

@@ -41,6 +41,7 @@

 

 #ifdef _KERNEL_OPT

 #include "opt_machdep.h"

+#include "opt_bootconfig.h"

 #endif

 

 #include <arm/bootconfig.h>

On Jun 16, 2018, at 9:40 PM, Gmail TM <takeshi.mutoh%gmail.com@localhost> wrote:

Hi!!

2018/06/16 1:33、Jared McNeill <jmcneill%invisible.ca@localhost>のメール:

Can you try an older version (R23.x) of L4T's flash tools? ISTR having trouble with the new version.

This weekend, I install JetPack 2.1 (R23.2), and I can install pkgsrc u-boot successfully with flash.sh -k EBT.
https://sacraya.610t.org/TX1/boot/flash.sh_NetBSD-uboot-dtb.bin.EBTwithR23.2.20180617.txt

I think that it works fine,
https://sacraya.610t.org/TX1/boot/dmesg_NetBSD.NetBSD_u-boot.EBTwithR23.2.20180617.txt
 but I can’t boot NetBSD yet because of "bootconfig.dramblocks <= DRAM_BLOCKS” problem.

[   1.0000000] panic: kernel debugging assertion "bootconfig.dramblocks <= DRAM_BLOCKS" failed: file "/home/source/ab/HEAD/src/sys/arch/aarch64/aarch64/aarch64_machdep.c", line 198
[   1.0000000] cpu0: Begin traceback...
[   1.0000000] trace fp ffffffc00000ab80
address 0xffffffc00000ab80 is invalid
address 0xffffffc00000ab88 is invalid
[   1.0000000] cpu0: End traceback...
Stopped in pid 0.1 (system) at  ffffffc000055098:       address 0xffffffc000055098 is invalid
.insn   0x00000000      # undefined

This problem is same as when I used original u-boot.

Which does it mean ...
I must set some more u-boot environment correctly?
I must create more appropriate kernel config and use it?

Thanks.

On Fri, 15 Jun 2018, Gmail TM wrote:

Thank you for your reply, Jared.

2018/06/12 21:54、Jared McNeill <jmcneill%invisible.ca@localhost>のメール:

I think if you are just updating U-Boot, you need to specify '-k LNX' on the flash.sh command-line. Let me know if that helps..

I try flash.sh with -k LNK option, but it stop at "Updating BCT with signature”
https://sacraya.610t.org/TX1/boot/flash.sh.LNX.20180613.txt

$ sudo ./flash.sh  -k LNX -L ~/u-boot-dtb.bin jetson-tx1 mmcblk0p1
(snip)
[   3.7436 ] Signing BCT
[   3.7489 ] tegrasign --key None --list bct_list.xml --pubkeyhash pub_key.key
[   3.7568 ] Assuming zero filled SBK key
[   3.7878 ]
[   3.7878 ] Updating BCT with signature
[   3.7892 ] tegrabct --bct P2180_A00_LP4_DSC_204Mhz.bct --chip 0x21 --updatesig bct_list_signed.xml

I think that when I want to update bootloader only, I must use -k EBT option.
The flash.sh comment says
# ./flash.sh -k EBT <target_board> mmcblk1p1            - update <target_board> bootloader
# ./flash.sh -k LNX <target_board> mmcblk1p1            - update <target_board> kernel

I can write u-boot-dtb.bin with -k EBT,
https://sacraya.610t.org/TX1/boot/flash.sh.NetBSD-uboot-dtb.bin.EBT.20180614.txt
but it doesn’t work now.
https://sacraya.610t.org/TX1/boot/dmesg.NetBSD_u-boot.EBT.20180614.txt

By the way, pkgsrc/sysutils/u-boot-jetson-tx1 has two bootloaders, u-boot and u-boot-dtb.bin.
Which bootloader should I use?

Thanks.