Thank you for response. I’ve downloaded the latest sources and they already include no-tnid-sn; line. Do I still need to build a kernel without changes and flash Jetson? Doesn’t the last image contain these changes?
Anyway I decided to build kernel and flash Jetson.
I checked hardware/nvidia/platform/t210/porg/kernel-dts/tegra210-porg-p3448-common.dtsi and it already had no-tnid-sn; line. So I simply built the kernel and replaced image and dtb directory at <release_package> directory. Ran apply_binaries.sh and flashed in recovery mode. Serial number remains the same.
I’m not sure of this, but there is a chance that apply_binaries.sh will overwrite your device tree. Try running apply_binaries.shprior to adding your content.
there are two possible serial numbers on a Nano devkit, one for the Nano module and the other for the baseboard.
you should enable i2cdump to dump these serial numbers for confirmation,
for example,
Ok, now I understood. There are 3 different serial: module, board and kit. Is there a way to get the serial number of kit (from the sticker) in Ubuntu?
We use device serial numbers to register them in our cloud system. User can see only the sticker on the board.
from the software side, there’s no approaches to check devkit serial number since that did not saved in EEPROM.
we’re having internal discussion, will update the conclusion.
thanks
I am running into a similar issue just trying to find the exact version of the module, when it is on a custom carrier. I took a dev kit and put the module from it on a custom carrier to test, and now need to confirm what version of the module it was. Can you advise how to decode the results from i2cdump into something that indicates something like B00 vs B01 to me?
we’re having software approaches to read CVB (p3449) and CVM (p3448) S/N,
since there’s no approaches to check devkit (p3450) serial number since that did not saved in EEPROM.
suggest you might have combination of CVB and CVM to name a board.
thanks