- 【Conclusion 】odmfuse.sh NOT works directly, there several fix need add/take care
【problem1】odmfuse.sh is ONE-Step burning command, when running without “–noburn”, it call get_board_version which will reboot xavier into recovery mode, but it failed some how. ---- then you will see Boot Rom Communication Failed
【solution1】using TWO-Step burn as L4T Official Doc also advices，first run BOARDID=2888 FAB=400 BOARDSKU=0004 BOARDREV=K.0 ./odmfuse.sh --noburn …(other paras). ， secondly untar fuseblob.tbz2 and run fusecmd.sh.
【problem2】some wrong like “Stat for RECFILE failed”
【solution2】this is because odmfuse.sh miss some recover config, you need patch/add “CFGCONV+=”-e /RECDTB-FILE/d “” command. Reference: From ilies.chergui patch, From DaneLLL Patch. These Fix are include in odmfuse.sh of R32.4.2 release.
【problem3】odmfuse.sh does not support “-c NC”
【solution3】odmfuse.sh add “PkcDisbale” fusename when using “-c NC”, but later not recognize by BOM? Reference Patch: From ilies.chergui patch delete which will delte “PkcDisbale” from odmfuse_pkc.xml
Here are the Board-B successful fuse log:
Step 1 burn log：Board-B-burn-step1.log (4.4 KB)
Step 2 burn log：Board-B-burn-step2.log (27.1 KB)
Fuse Read Verify log: Board-B-fuse-read.log (2.6 KB)
ofmfuse.sh(based R34.4.2 version) used in R32.3.1 package : odmfuse-3242-disable-pkc.sh.log (41.7 KB)
odmfuse_pkc.xml used in step2: Board-B-burn-step2-odmfuse_pkc.xml.log (189 Bytes)
Board-B-kernel-boot log(seems nothing special with fuse？)：Board-B-kernel-boot.log (71.0 KB)