Different value between fuse ECID and board ECID

Hi all,

Is anyone know why the result of

sudo nv_fuse_read.sh ecid

in a live system and the read_ecid ()function in nvautoflash.sh output different values ?

And not even the same size ?

Thanks in advance,

Related:

But for 36.X

hello Alex15000,

it’s tegra flash to have boot rom communication to obtain BR_CID.
for instance,

[   0.5627 ] Boot Rom communication
[   0.5637 ] tegrarcm_v2 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[   0.5646 ] BR_CID: 0x80012344705E35DE2C0000000B018100

BR_CID it’s 128-bit which compose by four 32-bit ECIDs.
it’s looks like following BR_CID = 0x{ECID3}{ECID2}{ECID1}{ECID0}
it’s python script to convert BR_CID into ECID (internally), which used by BR-BCT

Thanks for your answer ! Do you have a pointer to which python script used to convert BR_CID into ECID ?

Thanks again !

hello Alex15000,

sorry, it’s not a public release python script file.
BR_CID it equals to ECID, it’s due to nv_fuse_read.sh it’s defined as 64-bit.
you may running below to obtain BR_CID directly.
for example,

$ sudo ./tegrarcm_v2 --new_session --chip 0x23 --uid
BR_CID: 0x80012344705DD504740000000BFE01C0

you may refer to developer guide, Enabling Debugging Features Through the BCT Configuration File as see-also.

Hi, thanks for the answer! So I have no way to match ecid from a running board to br_cid from a board in recovery mode ?

hi Alex15000,

may I also know the actual use-case for reference?

Hi,

identify a recovery board already identify by it’s ECID in order to flash the right software automatically…

hello Alex15000,

please give it a try with the attached python script. ecid-to-uid-test.py (1.5 KB)
for instance,

$ echo 0x80012344705DD504740000000BFE01C0 > br_cid
$ python ecid-to-uid-test.py -t t234 -d br_cid 
t234
br_cid
0x80012344705DD504740000000BFE01C0

uid(10):
9543798871594891271
uid(16):
0x847262822d2ff807

It seems to work, thank you very much !