Serial number mismatch

Hi,

I have different serial numbers in system and on board. I saw similar topic, but the latest software still has this problem.

Every utility has the same s/n:

$ sudo lshw | grep serial
    serial: 1422019082094
...
$ cat /proc/device-tree/serial-number 
1422019082094
$ sudo i2cdump -f -y 2 0x50
No size specified (using byte-data access)
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 01 00 fc 00 78 0d 00 00 02 46 00 00 00 00 00 00    ?.?.x?..?F......
10: 00 00 00 00 36 39 39 2d 31 33 34 34 38 2d 30 30    ....699-13448-00
20: 30 30 2d 32 30 30 20 46 2e 30 00 00 00 00 00 00    00-200 F.0......
30: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
40: ff ff ff ff 31 58 e5 4b 04 00 31 34 32 32 30 31    ....1X?K?.142201
50: 39 30 38 32 30 39 34 00 00 00 00 00 00 00 00 00    9082094.........
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 4e 56 43 42 1c 00 4d 31 00 00    ......NVCB?.M1..
a0: ff ff ff ff ff ff ff ff ff ff ff ff 31 58 e5 4b    ............1X?K
b0: 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ?...............
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0    ...............?

But the board has: 1422019103203

Jetson board photo with s/n

Please could you suggest how can I get the same s/n in system?

hello a1ezh,

had you tired to include no-tnid-sn; into Nano device tree for confirmation?
please also refer to Topic 77503 for details. thanks

Hello, @JerryChang

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.

What else сan I do?

I’m not sure of this, but there is a chance that apply_binaries.sh will overwrite your device tree. Try running apply_binaries.sh prior to adding your content.

hello a1ezh,

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,

# Module (p3448)
$ sudo i2cdump -f -y 2 0x50
serial number: 1422919085224

# Baseboard (p3449)
$ sudo i2cdump -f -y 2 0x57
serial number: 1422919047285

@JerryChang

Ok, there are:
1422019082094
1422019110311

But still they don’t match
1422019103203

sudo i2cdump -f -y 2 0x50
No size specified (using byte-data access)
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 01 00 fc 00 78 0d 00 00 02 46 00 00 00 00 00 00    ?.?.x?..?F......
10: 00 00 00 00 36 39 39 2d 31 33 34 34 38 2d 30 30    ....699-13448-00
20: 30 30 2d 32 30 30 20 46 2e 30 00 00 00 00 00 00    00-200 F.0......
30: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
40: ff ff ff ff 31 58 e5 4b 04 00 31 34 32 32 30 31    ....1X?K?.142201
50: 39 30 38 32 30 39 34 00 00 00 00 00 00 00 00 00    9082094.........
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 4e 56 43 42 1c 00 4d 31 00 00    ......NVCB?.M1..
a0: ff ff ff ff ff ff ff ff ff ff ff ff 31 58 e5 4b    ............1X?K
b0: 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ?...............
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0    ...............?

$ sudo i2cdump -f -y 2 0x57
No size specified (using byte-data access)
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 01 00 fc 00 79 0d 00 00 02 4a 00 00 00 00 00 00    ?.?.y?..?J......
10: 00 00 00 00 36 39 39 2d 31 33 34 34 39 2d 30 30    ....699-13449-00
20: 30 30 2d 32 30 30 20 4a 2e 30 00 00 00 00 00 00    00-200 J.0......
30: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
40: ff ff ff ff ff ff ff ff ff ff 31 34 32 32 30 31    ..........142201
50: 39 31 31 30 33 31 31 00 00 00 00 00 00 00 00 00    9110311.........
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 4e 56 43 42 1c 00 4d 31 00 00    ......NVCB?.M1..
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b3    ...............?

hello a1ezh,

that serial number from the sticker is the S/N number of Jetson Nano Developer Kit (p3450),
you may also refer to Jetson part numbers for the details.

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.

Thank you for response.

I’ve just tried to run apply_binaries.sh prior to replacing image and dtb directory. But I have the same results. Serial numbers stays the same.

Please tell me who else can I contact with this problem? Is there any bug tracker?

hello a1ezh,

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

Hello @JerryChang

Thank you for reply. I’ll be waiting for the conclusion.

Hi, JerryChang!

Do you have any news about the problem?

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?

Hi John,

Please help to open a new topic for your issue. Thanks

hi all,

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

1 Like