When I flashing with tegrarcm, I can see “chip uid” like below.
I’d like to use this for unique id.
How can I read this from u-boot or kernel ?
where does it saved?
I try to dump many registers but can’t find it.
I try to find the header tegra210_fuse_offsets.h both on my tk1 and tx1, but nothing found. I found the folder named tegra-fuse in the path/usr/src/linux-headers-3.10.96-tegra/drivers/misc/tegra-fuse, but there is only one Makefile under this folder, tegra210_fuse_offsets.h is not found. Do you have any idea how I can use the kernel function tegra_chip_uid?
Does this mean, that I have to compile my custom kernel with a way to use that function?
Or is it sufficient if I can have some kernel modules using that function that can be inserted into an already running kernel?
Or is there a better way to get the chip UUID?
Please suggest a direction to proceed. Any starting point would help a lot.
It depends on your L4T version, but for chip ID you may check this.
For unique Chip ID you’ll have to dig into driver source for how to get it.
You may also have a look to /proc/cmdline and check value of option androidboot.serialno.
Has anybody made this work?
I made a kernel driver module which calls " tegra_chip_uid", but the module fails to load with error message “Unknown symbol tegra_chip_uid (err 0)”.
I also tried to make the module built-in but doesn’t link with the same reason.
I use R27.1 (4.4.15-tegra).
please note that l4t-r27.1 dose not support TX1 devices.
you might also check the [L4T Release Notes] from Jetson Download Center,
since we continuously public BSP releases, could you please upgrade your working environment to the latest JetPack release, thanks
Hi Jerry,
Thanks for the quick response.
I used TX2 for this experiment (we own TX1 and TK1 as well).
I don’t mind upgrading the environment to the latest, but if I do, then calling tegra_chip_uid() should work?
I used R27.1 because it was the latest at the time comment #4 was posted.