I do not know that. I’m just suggesting that if you cannot find out (since any kind of flash can involve multiple partitions) that all partitions except the first are possibly in need of update.
During flash I see that the flash program starts by finding the boot control table, and in my R28.1 TX1 this is “bootloader/t210ref/BCT/P2180_A00_LP4_DSC_204Mhz.cfg”. The very next file read is “bootloader/t210ref/cboot.bin”, and then it shows write operations, but fails to say which partition is being written to. No clue is available from the BCT, so what I did was run “strings” on cboot.bin to see if there is anything unique there…and there is. Within this is “welcome to cboot”.
Next, on a running R28.1 TX1, I ran this on each partition (change the number from 2 through 18):
sudo cat /dev/mmcblk0p2 | strings | egrep 'welcome to cboot'
mmcblk0p3 matches. “blkid” reveals this has label “EBT” (which is what the flash software probably refers to this as).
This should give you a procedure to guarantee finding the information if you know some content to compare. My thought is that although this is probably the partition you are interested in, it is also possible that another partition is simply pointing to the wrong place and that this partition still matches.
Considering how hard you are trying to get this working remotely I am guessing there is something important beyond just the cost of a Jetson, so I hope you get it to work.