Partition table change - Device not booting

[tirankas]

Hey Guys,
I had to change the partition table for our Nano based module (EMMC).
I was relying on a previous build, just changed the size and rebuilt.
Flash via USB went fine, device looks ok and layout seems correct.
Doing mender update for the exact same device (that is actually running with the same SW) --> Device no longer powers up.
I know mender has its custom flash layout and the table is using the APP_SIZE (derived from ROOTFS_SIZE), so I clean this recipe for the build...

My guess is that mender is not aware of the new flash layout and it is happening in a recipe I probably had to clean but not sure which recipe....

Doing a full build from scratch is currently ongoing but would also like to understand how mender processes a partition table, does it updates partition table?

Thanks

[tirankas]

Maybe I should clarify:
I changed the root FS partition size.
Built from scratch.
Flashing via USB, works fine...
Flashing afterwards using the same mender created in the build (on the same device that I flashed via USB, same build), device doesn't boot, it doesn't find lnx partition.
Is there anything I should be aware of when changing partition size?

[tirankas]

Some more insights...
Here is the powerup log of the device before mender running:

Table works
[0000.226] Processing in cold boot mode Bootloader 2
[0000.230] A02 Bootrom Patch rev = 1023
[0000.234] Power-up reason: pmc por
[0000.237] No Battery Present
[0000.240] pmic max77620 reset reason
[0000.243] pmic max77620 NVERC : 0x40
[0000.246] RamCode = 0
[0000.249] Platform has DDR4 type RAM
[0000.252] max77620 disabling SD1 Remote Sense
[0000.256] Setting DDR voltage to 1125mv
[0000.260] Serial Number of Pmic Max77663: 0x329c6
[0000.268] Entering ramdump check
[0000.271] Get RamDumpCarveOut = 0x0
[0000.274] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.279] Last reboot was clean, booting normally!
[0000.284] Sdram initialization is successful
[0000.288] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.294] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.300] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.306] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.311] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.317] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.323] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.329] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.345] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.351] Platform-DebugCarveout: 0
[0000.354] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.360] Non secure mode, and RB not enabled.
[0000.377] Csd NumOfBlocks=0
[0000.572] *** Booting BFS0.
[0000.575] Read PT from (0:3)
[0000.581] Using BFS PT to query partitions
[0000.585] PT: Partition LNX NOT found !
[0001.190] *** Booting KFS0.
[0001.192] BoardID = 3448, SKU = 0x2
[0001.196] Not Nano-SD or !QSPI-ONLY, check GPT table first ...
[0001.201] Read GPT from (0:3)
[0001.209] Using GPT Primary to query partitions
[0001.214] Loading Tboot-CPU binary
[0001.221] Verifying TBC in OdmNonSecureSBK mode
[0001.231] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0001.238] Bootloader downloaded successfully.
[0001.242] Downloaded Tboot-CPU binary to 0xa0000258
[0001.247] MAX77620_GPIO5 configured
[0001.251] CPU power rail is up
[0001.254] CPU clock enabled
[0001.257] Performing RAM repair
[0001.260] Updating A64 Warmreset Address to 0xa00002e9
[0001.265] BoardID = 3448, SKU = 0x2
[0001.269] Not Nano-SD or !QSPI-ONLY, check GPT table first ...
[0001.275] Loading NvTbootBootloaderDTB
[0001.292] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode
[0001.367] Bootloader DTB Load Address: 0x83000000
[0001.371] BoardID = 3448, SKU = 0x2
[0001.375] Not Nano-SD or !QSPI-ONLY, check GPT table first ...
[0001.380] Loading NvTbootKernelDTB
[0001.397] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode
[0001.472] Kernel DTB Load Address: 0x83100000
[0001.476] BoardID = 3448, SKU = 0x2
[0001.479] Not Nano-SD or !QSPI-ONLY, check GPT table first ...
[0001.486] Loading cboot binary
[0001.497] Verifying EBT in OdmNonSecureSBK mode
[0001.539] Bootloader load address is 0x92c00000, entry address is 0x92c00258
[0001.546] Bootloader downloaded successfully.
[0001.550] BoardID = 3448, SKU = 0x2
[0001.553] Not Nano-SD or !QSPI-ONLY, check GPT table first ...
[0001.560] PT: Partition NCT NOT found !
[0001.563] Warning: Find Partition via PT Failed
[0001.568] Next binary entry address: 0x92c00258
[0001.572] BoardId: 3448
[0001.577] Overriding pmu board id with proc board id
[0001.581] Display board id is not available
[0001.586] BoardID = 3448, SKU = 0x2
[0001.589] Not Nano-SD or !QSPI-ONLY, check GPT table first ...
[0001.602] Verifying SC7EntryFw in OdmNonSecureSBK mode
[0001.660] /bpmp deleted
[0001.662] SC7EntryFw header found loaded at 0xff700000
[0001.860] OVR2 PMIC
[0001.862] Bpmp FW successfully loaded
[0001.865] BoardID = 3448, SKU = 0x2
[0001.869] Not Nano-SD or !QSPI-ONLY, check GPT table first ...
[0001.876] WB0 init successfully at 0xff780000
[0001.880] Set NvDecSticky Bits
[0001.884] GSC2 address ff53fffc value c0edbbcc
[0001.890] GSC MC Settings done
[0001.893] BoardID = 3448, SKU = 0x2
[0001.896] Not Nano-SD or !QSPI-ONLY, check GPT table first ...
[0001.903] TOS Image length 53680
[0001.906] Monitor size 53680
[0001.909] OS size 0
[0001.914] Secure Os AES-CMAC Verification Success!
[0001.919] TOS image cipher info: plaintext
[0001.923] Loading and Validation of Secure OS Successful
[0001.938] SC7 Entry Firmware - 0xff700000, 0x4000
[0001.943] NvTbootPackSdramParams: start.
[0001.948] NvTbootPackSdramParams: done.
[0001.952] Tegraboot started after 149551 us
[0001.956] Basic modules init took 1484426 us
[0001.960] Sec Bootdevice Read Time = 563 ms, Read Size = 14699 KB
[0001.966] Sec Bootdevice Write Time = 0 ms, Write Size = 0 KB
[0001.971] Next stage binary read took 7387 us
[0001.976] Carveout took -28698 us
[0001.979] CPU initialization took 386546 us
[0001.983] Total time taken by TegraBoot 1849661 us

And this is the log afterwards:
[0000.205] [L4T TegraBoot] (version 00.00.2018.01-l4t-dd84d362)
[0000.210] Processing in cold boot mode Bootloader 2
[0000.215] A02 Bootrom Patch rev = 1023
[0000.219] Power-up reason: software reset
[0000.222] No Battery Present
[0000.225] pmic max77620 reset reason
[0000.228] pmic max77620 NVERC : 0x0
[0000.232] RamCode = 0
[0000.234] Platform has DDR4 type RAM
[0000.237] max77620 disabling SD1 Remote Sense
[0000.241] Setting DDR voltage to 1125mv
[0000.245] Serial Number of Pmic Max77663: 0x329c6
[0000.253] Entering ramdump check
[0000.256] Get RamDumpCarveOut = 0x0
[0000.259] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.264] Last reboot was clean, booting normally!
[0000.269] Sdram initialization is successful
[0000.273] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.279] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.285] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.291] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.297] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.303] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.308] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.314] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.330] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.336] Platform-DebugCarveout: 0
[0000.340] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.345] Non secure mode, and RB not enabled.
[0000.362] Csd NumOfBlocks=0
[0000.568] *** Booting BFS0.
[0000.570] Read PT from (0:3)
[0000.577] Using BFS PT to query partitions
[0000.581] PT: Partition LNX NOT found !
[0001.268] *** Failing over to KFS1.
[0000.297] [L4T TegraBoot] (version 00.00.2018.01-l4t-dd84d362)
[0000.302] Processing in cold boot mode Bootloader 2
[0000.307] A02 Bootrom Patch rev = 1023
[0000.310] Power-up reason: software reset
[0000.314] No Battery Present
[0000.317] pmic max77620 reset reason
[0000.320] pmic max77620 NVERC : 0x0
[0000.323] RamCode = 0
[0000.326] Platform has DDR4 type RAM
[0000.329] max77620 disabling SD1 Remote Sense
[0000.333] Setting DDR voltage to 1125mv
[0000.337] Serial Number of Pmic Max77663: 0x329c6
[0000.345] Entering ramdump check
[0000.348] Get RamDumpCarveOut = 0x0
[0000.351] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.356] Last reboot was clean, booting normally!
[0000.361] Sdram initialization is successful
[0000.365] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.371] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.377] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.383] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.389] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.394] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.400] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.406] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.422] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.428] Platform-DebugCarveout: 0
[0000.432] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.437] Non secure mode, and RB not enabled.
[0000.454] Csd NumOfBlocks=0
[0000.709] *** Booting BFS1.
[0000.712] Read PT from (0:3)
[0000.718] Using BFS PT to query partitions
[0000.723] PT: Partition LNX NOT found !
[0001.416] *** Failing over to KFS2.

[madisongh]

The bootloader isn't finding the partition that contains U-Boot, which implies that something got modified incorrectly during the Mender update to cause that.

You say that the unit boots OK after flashing. Does it continue to boot OK if you reboot it (without doing any Mender updates)?
If so, and it's only the Mender update that's causing the issue, then you should trace what changes that update is applying (before the unit is rebooted, of course) and see what got changed that might be causing the problem.

It's something different about your particular setup (as we've been through several discussions that have boiled down to differences in your custom distro vs. the demo distro), the flash layout change you made, or the way you made it. Maybe you should go back to the configuration that you had working, re-verify that it still works with Mender updates, then change just one thing at a time until a problem occurs, just to try and zero in on the specific change that caused the problem? If that doesn't help you identify the solution, then post the exact change you made in as much detail as possible, and hopefully we can help point you in the right direction.

[tirankas]

Hi Matt,
I have checked 100 times but will check again because it does indeed sounds like own layer issue...
In fact, I have a machine that is almost identical to the problematic machine and works fine, so I am clueless....
My main question is theoretical: mender relies on root and data partition numbers provided during build. Boot is different I understand so I might be missing something related to boot location somewhere ..

For your question: after USB flashing it works good even after cold boot...

[tirankas]

Hi Matt,
Can you please explain what is this for:
MACHINEOVERRIDES = "jetson-nano-devkit-emmc:cot:${MACHINE}"

I found a mistake in my machine, not sure what that means...

[madisongh]

Take a look at this wiki page for some info on how you might approach the problem.

[tirankas]

Hi @madisongh,
Thanks for the info.
I have built this, using the mender integration instructions.
I believe u-boot (Jetson Nano) is different since it would need to know that initrd is used and not emmc for rootfs, i.e. command line is different...

Also, Trying to update the 32.5.0 original device with the mender I just created (with the provided guidelines), I fail on the ArtifactInstall_Leave_80_bl-update. Running this (ArtifactInstall_Leave_80_bl-update) manually returns success, any idea?

Thanks

[madisongh]

I believe u-boot (Jetson Nano) is different since it would need to know that initrd is used and not emmc for rootfs, i.e. command line is different...

Yes, I haven't been through the exercise with a U-Boot platform, so I don't have details handy for that. The principle would be the same, though - having the reformatter + installer running entirely within the initrd.

Also, Trying to update the 32.5.0 original device with the mender I just created (with the provided guidelines), I fail on the ArtifactInstall_Leave_80_bl-update. Running this (ArtifactInstall_Leave_80_bl-update) manually returns success, any idea?

Not off-hand... you could try adding a set -x to that script, and maybe remove some of the stderr redirections to /dev/null in it, so when it executes during the install you can find out more about what it's doing when it fails.

[tirankas]

This is the output:

• mnt=
• UBOOTVARS='bootcount mender_boot_part mender_boot_part_hex upgrade_available'
• ubvarfile=
• install_fwenv=
• echo 'Installing NVIDIA bootloader update payload'
  ++ fw_printenv -n mender_boot_part
• new_boot_part=18
  ++ mktemp -d -t nvbup.XXXXXX
• mnt=/tmp/nvbup.KQaTNw
• '[' -z /tmp/nvbup.KQaTNw -o '!' -d /tmp/nvbup.KQaTNw ']'
• mount -o ro /dev/mmcblk0p18 /tmp/nvbup.KQaTNw
• '[' '!' -d /tmp/nvbup.KQaTNw/opt/ota_package ']'
• mount --bind /sys /tmp/nvbup.KQaTNw/sys
• mount --bind /proc /tmp/nvbup.KQaTNw/proc
• mount --bind /dev /tmp/nvbup.KQaTNw/dev
• mount -t tmpfs tmpfs /tmp/nvbup.KQaTNw/run
• '[' -e /tmp/nvbup.KQaTNw/usr/share/u-boot/fw_env.config ']'
• diff -qbi /etc/fw_env.config /tmp/nvbup.KQaTNw/usr/share/u-boot/fw_env.config
• chroot /tmp/nvbup.KQaTNw /usr/bin/tegra-bootloader-update --dry-run /opt/ota_package/bl_update_payload
• grep -q 'version partitions are corrupted'
• chroot /tmp/nvbup.KQaTNw /usr/bin/tegra-bootloader-update --dry-run /opt/ota_package/bl_update_payload
• echo 'ERR: cannot perform bootloader update'
  ERR: cannot perform bootloader update

Note that if I run this manually immediately after it fails, it works fine...

[tirankas]

Hi @madisongh
Nevermind, I did a mess with this new image mixing partition tables...
I will align everything, add the initrd and hopefully make this work

[tirankas]

Hi @madisongh,
Just to make sure I follow this correctly:
I need to build an initramfs based build using the exact same partition table resides in the device to be updated. bup payload (which also must be aligned with the device partition table) will allow me to overwrite the bootloaders in the correct location because it was generated with the same tools and table as the device to update. It will also update the kernel.
This new upgrader build will be applied via mender.
Once applied (and rebooted), I will have a u-boot which will load the initramfs instead of the emmc-based rootfs.
In this initramfs I will have all the upgrade tools in place which will run as part of systemd.
These tools will need the image.tar.gz of the new 32.5.0 build I want to apply. I will probably need to propagate this image into the target to make the process automatic...

Is the above correct?

Thanks

[madisongh]

Yes, that's the basic process.

[tirankas]

Hi @madisongh,
I am seeing something weird happening, maybe you can explain.
Recently I am failing to OTA update a Nano EMMC device.
Some failures are bricking the device, I am onto getting some logs and to come up with the information that will help nailing it down.
However, there is a failure I checked and cannot understand why, here is the description:
when trying to update a version to the exact same version on a specific device, It fails with the regular boot update script.
I have put lots of logs in the tegra-bootloader-update tool sources and eventually I see it fails because the BMP partition is smaller than needed.
The length it tries to write is 149554 while the BPM partition in the device is 80K:
lsblk /dev/disk/by-partlabel/BMP -o SIZE,KNAME,PKNAME,MOUNTPOINT,FSTYPE
SIZE KNAME PKNAME MOUNTPOINT FSTYPE
80K mmcblk1p13 mmcblk1

What I don't understand is how come this happens when I know the partition size in the flash.xml file is 196608:

<allocation_policy> sequential </allocation_policy>
<filesystem_type> basic </filesystem_type>
196608
<allocation_attribute> 8 </allocation_attribute>
bmp.blob
Optional. Contains BMP images for splash screen display during
boot.

Same thing I see with RP4 partition, but other parts that are sequentially after this part are OK.

Am I missing anything?

[madisongh]

Sounds like the current partition layout was based on a SKU 0000 (SPI+SDcard) Nano. That model has smaller BMP and RP4 partitions (around 80K and 128K, respectively).

[tirankas]

Thanks Matt.
But when I flash via the USB tegra flash, and I see the partition table in my tegra flash tarball is 192k for BMP, isn't it suppose to replace it in the device?

[madisongh]

Yeah, the flash.xml.in in the tegraflash package would be used by the NVIDIA flashing tools to format the eMMC. It's unlikely to have changed since flashing, unless you flashed in an initrd-based installer that reformatted the eMMC too.

[tirankas]

No, I didn't ...
In fact, the ok is 100% reproducible. I am having 5oo many issues with Nano recently, I suspect this issue might be the easiest lead to finding the problem...
So, my tegraflash has two partitions in it's flash.xml file which are different from what is in the device after flashing. I don't understand where could this come from...

[madisongh]

No idea. What happens if you just build the BUP payload with the modified device tree, copy that onto the device, and apply the BUP manually?

[tirankas]

Hi @madisongh,
You mean the same modified but payload generated with the Yocto build and apply it manually in the target device?
If yes, I tried this and same results.
Whatever change I do in the DT I see this happening.

Thanks

[madisongh]

Weird.
You see absolutely no output on the serial console at all, not even from the bootloaders? Is the device switching immediately into recovery mode after reboot, then?
What sort of changes are you making to the device tree?

[tirankas]

It gives the output below once after the reboot and will not output again no matter what I do (even unplug the power and plug in again).
I am changing the camera type in the DT (from ECON to IMX477) but this is not related to this because I also tried moving from my ECON DT to the original tegra dtb (tegra210-p3448-0002-p3449-0000-b00.dtb) and got the same behavior.

[madisongh]

What is the "output below" ? That didn't come through.

[tirankas]

Sorry, forgot -:)

[0000.202] [L4T TegraBoot] (version 00.00.2018.01-l4t-dd84d362)
[0000.207] Processing in cold boot mode Bootloader 2
[0000.212] A02 Bootrom Patch rev = 1023
[0000.215] Power-up reason: software reset
[0000.219] No Battery Present
[0000.222] pmic max77620 reset reason
[0000.225] pmic max77620 NVERC : 0x0
[0000.228] RamCode = 0
[0000.231] Platform has DDR4 type RAM
[0000.234] max77620 disabling SD1 Remote Sense
[0000.238] Setting DDR voltage to 1125mv
[0000.242] Serial Number of Pmic Max77663: 0x329c6
[0000.250] Entering ramdump check
[0000.253] Get RamDumpCarveOut = 0x0
[0000.256] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.261] Last reboot was clean, booting normally!
[0000.266] Sdram initialization is successful
[0000.270] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.276] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.282] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.288] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.294] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.299] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.305] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.311] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.327] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.333] Platform-DebugCarveout: 0
[0000.337] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.342] Non secure mode, and RB not enabled.
[0000.359] Csd NumOfBlocks=0
[0000.568] *** Booting BFS0.
[0000.571] Read PT from (0:3)
[0000.578] Using BFS PT to query partitions
[0000.582] PT: Partition LNX NOT found !
[0001.468] *** Failing over to KFS1.
[0000.292] [L4T TegraBoot] (version 00.00.2018.01-l4t-dd84d362)
[0000.297] Processing in cold boot mode Bootloader 2
[0000.302] A02 Bootrom Patch rev = 1023
[0000.305] Power-up reason: software reset
[0000.309] No Battery Present
[0000.312] pmic max77620 reset reason
[0000.315] pmic max77620 NVERC : 0x0
[0000.318] RamCode = 0
[0000.321] Platform has DDR4 type RAM
[0000.324] max77620 disabling SD1 Remote Sense
[0000.328] Setting DDR voltage to 1125mv
[0000.332] Serial Number of Pmic Max77663: 0x329c6
[0000.340] Entering ramdump check
[0000.343] Get RamDumpCarveOut = 0x0
[0000.346] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.351] Last reboot was clean, booting normally!
[0000.356] Sdram initialization is successful
[0000.360] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.366] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.372] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.378] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.384] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.389] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.395] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.401] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.417] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.423] Platform-DebugCarveout: 0
[0000.427] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.432] Non secure mode, and RB not enabled.
[0000.449] Csd NumOfBlocks=0
[0000.659] *** Booting BFS1.
[0000.661] Read PT from (0:3)
[0000.666] Using BFS PT to query partitions
[0000.671] PT: Partition LNX NOT found !
[0001.277] *** Failing over to KFS2.

[madisongh]

What was the output from running tegra-bootloader-update or l4t_payload_updater_t210 on the update payload?

I just ran a quick test on my Nano-eMMC with a trivial change to the DTB, and everything worked fine - BUP applied correctly, rebooted no problem, and I could see the device tree change after the reboot.

[tirankas]

Here is the BUP payload contents:

BLOB HEADER:
Magic: NVIDIA__BLOB__V2
Version: 0x00020000
Blob Size: 4,607,051 bytes
Header Size: 40 bytes
Entry Count: 26 partition(s)
Type: 0 (0 for update, 1 for BMP)
Uncompressed
Blob Size: 4,607,051 bytes
Accessory: Not Present

ENTRY TABLE:
| part_name | offset | part_size | version | op_mode | tnspec |
| BCT | 3160 | 10240 | 2 | 0 | 3448-200-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| BCT | 13400 | 10240 | 2 | 0 | 3448-300-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| BCT | 23640 | 10240 | 2 | 0 | 3448-400-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| RP1 | 33880 | 249952 | 2 | 0 | 3448-200-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| RP1 | 283832 | 249952 | 2 | 0 | 3448-300-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| RP1 | 533784 | 249952 | 2 | 0 | 3448-400-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| PT | 783736 | 4671 | 2 | 0 | 3448-200-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| PT | 788407 | 4671 | 2 | 0 | 3448-300-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| PT | 793078 | 4671 | 2 | 0 | 3448-400-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| VER | 797749 | 101 | 2 | 0 | 3448-200-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| VER | 797850 | 101 | 2 | 0 | 3448-300-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| VER | 797951 | 102 | 2 | 0 | 3448-400-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| NVC | 798053 | 164176 | 2 | 0 | |
| TBC | 962229 | 65760 | 2 | 0 | |
| EBT | 1027989 | 485120 | 2 | 0 | |
| WB0 | 1513109 | 3952 | 2 | 0 | |
| BPF | 1517061 | 3376 | 2 | 0 | |
| TOS | 1520437 | 54208 | 2 | 0 | |
| EKS | 1574645 | 1028 | 2 | 0 | |
| BMP | 1575673 | 149554 | 2 | 0 | |
| DTB | 1725227 | 249952 | 2 | 0 | 3448-200-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| DTB | 1975179 | 249952 | 2 | 0 | 3448-300-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| DTB | 2225131 | 249952 | 2 | 0 | 3448-400-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| LNX | 2475083 | 710656 | 2 | 0 | 3448-200-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| LNX | 3185739 | 710656 | 2 | 0 | 3448-300-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |
| LNX | 3896395 | 710656 | 2 | 0 | 3448-400-0002--1-0-jetson-nano-esd-imx-juganu-cot-mmcblk0p1 |