Something you might be interested in to help answer this is how the clone system works. On a TK1 the system is much more flexible than on the SoCs which come after this. You can clone and install individual partitions, or the eMMC as a whole. I don’t know which partition contains the RAM timing setup, but look closely at this, which was written for the TK1:
The TK1 has clone and restore operations available to it which the TX1 and newer do not have. In particular, understand this:
sudo ./nvflash --rawdeviceread 0 3849216 all.img --bl ardbeg/fastboot.bin --go
“fastboot.bin” is just used to create a bit of a micro support environment in the 3p server, e.g., it provides serial communications drivers, and does not remain after done with cloning.
Note that this uses raw bits from eMMC based on offsets and has no requirement for partitioning or file system types. This does what dd does, but does not require the TK1 to be bootable…it only requires recovery mode.
From this look at how partition naming can also be used. “all” is the entire eMMC, and if you were to clone “all”, and then use dd from your host on the “all” clone using the offsets where the partition table says a given partition exists, then clone of the individual partition would be a 100% bit-for-bit exact match of the dd of that part of “all”.
So the question is not whether the mechanism exists to fix the issue, the question is what do you have for a replacement partition? If you can determine that, then you can put it in place.
One complication is if the partition to be replaced is a different size. This can easily be worked around if you don’t mind some extra time required to do so.
Of particular importance is that you can have a backup copy before you experiment. If your partition to be tested is the same size as the partition to be replaced, then you can use dd or cloning to both read and write anywhere in eMMC you are interested in. Just make sure you have a copy of whatever you are altering, and that you protect that copy in case it isn’t what you want. If something goes wrong, then you can restore even if the Jetson won’t boot to Linux. Be sure to also clone the partition table (this is human readable text).