Rebuilding the Kernel Debian Package for TX2 and install

repack/
    debian/
           changelog
           compat
           control
           copyright
           install
          postinst
          rules
         source/
               format
         triggers
         out/
               usr/
                     ...
   boot/
           Image
   lib/
          ...

Hi,

You should put boot/Image and modules under “out” instead of current location.

ok,I will be try.
Which deb file does pinmux (tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg) correspond to?Are there related help documents?

It should be included as the bootloader one and it is not the pinmux file directly.

We use bootloader binary which includes all bootloader conponents.

1 Like

the nvidia-l4t-bootloader_32.4.3-20200625213407_arm64.deb?I unzipped the deb file and saw that the file is bl_update_payload. How do I generate a new file? Is there an instruction manual or operation steps?

please search " Generating the Bootloader Payload Update (BUP)" in the developer guide.

ok,Thanks.Okay thank you. Solved about the kernel debian package. I will take a look at the later part of BL, and if you have any questions, I will contact you.

1 Like

hello,
I read the chapter Generating the Bootloader Payload Update (BUP).

Run on host pc

sudo FAB=C04 BOARDID=3310 FUSELEVEL=fuselevel_production ./build_l4t_bup.sh jetson-tx2 mmcblk0p1

Output display:
signing images succeeded

Creating update payloads for Jetson-3310-C04---1-0-jetson-tx2-mmcblk0p1 board ...
Unsupported tegra soc: tx
bootloader update payload creation failed

Please share us below info.

cat /etc/nv_boot_control.conf

TNSPEC 3310-D02-1000-K.0-1-0-realtimes/rtso-9001-usb3-mmcblk0p1
TEGRA_CHIP 0x18
TEGRA_OTA_BOOT_DEVICE /dev/mmcblk0boot0
TEGRA_OTA_GPT_DEVICE /dev/mmcblk0boot1

Hi,

Please directly rename your board config to jetson-tx2.conf and use “sudo ./flash.sh jetson-tx2 mmcblk0p1” to flash it.

sudo FAB=C04 BOARDID=3310 FUSELEVEL=fuselevel_production ./build_l4t_bup.sh jetson-tx2 mmcblk0p1

Is the command executed on the host pc?

Yes. This command has to run on host PC.

I renamed it with jetson-tx2 and re-flash the system. The result of running the above command is the same.

What is the result now?

cat /etc/nv_boot_control.conf

TNSPEC 3310-D02-1000-K.0-1-0-jetson-tx2-mmcblk0p1
TEGRA_CHIP 0x18
TEGRA_OTA_BOOT_DEVICE /dev/mmcblk0boot0
TEGRA_OTA_GPT_DEVICE /dev/mmcblk0boot1

Try the method to let the board read the eeprom directly.

Put your device into recovery mode and then use this command.

sudo ./build_l4t_bup.sh jetson-tx2 mmcblk0p1

If I use realtimes/rtso-9001-usb3, I can’t use deb to upgrade the bootloader, right?

yes.

Then I edit and generate a customized deb file, it will become meaningless