Is it possible to relate the BR_CID value that can be seen on the host when flashing the Jetson in recovery mode, to a value that can be read by a script that is running on the jetson itself afterwards? I have looked at the sysfs files exposed by the tegra-fuse kernel module, but I don’t see a directly link between that and the BR_CID. It would be very helpful for us to automate our mass flashing and system bring up.
Another unrelated question which might also solve our problem, is it possible to dump the EEPROM contents of the module by using the tools in the mass flashing archive? In that way we could also use the identifier of the module or it’s mac address.
It would make configuration after flashing easier. The Jetson could then fetch its configuration directly from one of our internal databases without having to communicate with the host. (Any unique ID would work for this like MAC address, Jetson SoM ID, but for those I haven’t found an easy way to read them on the flashing host when the jetson is in recovery mode using tools from the massflash archive).
The approach would be more or less. 1) Connect unit to flashing host. 2) Scan barcode on unit. 3) Store a link between barcode and BR_CID. 4) Flash Jetson. 5) When Jetson boots it can retrieve the barcode of the unit it is installed in together with all required metadata based on this BR_CID.