Hardware issues with Rock64

[t4_4t]

As far as I know, '0.9.16: gitlab-ci-linux-build-163' is the last version of 'u-boot' with the correct implementation of 'efuse' support.
The so-called 'main-line' ' u-boot', does not have the 'efuse' support function correctly implemented.
(* It may be more accurate to say that the'efuse'support feature itself has been removed.)

Try the following image,
https://github.com/ayufan-rock64/linux-b...m64.img.xz

If this still gives the same result, your claim (In fact the efuse is empty) is correct.
On the other hand, if you get a reasonable value, it's just a 'u-boot' problem.

---

For reference, below is an example of my execution.
From the same board, I get a completely different reaction.
And one of the outputs is the same value you got.

@ buster-minimal-rock64-0.10.12-1184-arm64.img.xz

Code:

u-boot:
cpuid # = 300bf2fc000000008c79f4fe00000000

buster:
# xxd / sys / bus / nvmem / devices / rockchip-efuse0 / nvmem
00000000: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................

@ buster-minimal-rock64-0.9.16-1163-arm64.img.xz

Code:

u-boot:
cpuid # = 55524b50303930303800000000xxxxxx

buster:
# xxd / sys / bus / nvmem / devices / rockchip-efuse0 / nvmem
00000000: 524b 3382 00fe 2155 524b 5030 3930 3038 RK3 ...! URKP09008
00000010: 0000 0000 xxxx xxxx xxxx xxxx 0000 0000 ................

* 'xxxx' is hidden for security reasons.