xavier
1
Which system do you use? Android, Ubuntu, OOWOW or others?
Android, Ubuntu, OOWOW
Which version of system do you use? Khadas official images, self built images, or others?
Khadas official images, latest available via OOWOW
Please describe your issue below:
Some VIM4 devices report serialno 000000000. This is observed in OOWOW, uboot and in the kernel cmdline in Android.
Typically in uboot for VIM4 with missing serialno:
kvim4# echo $usid
0000000000
In uboot for other product with working serialno
kvim4# echo $usid
2cb0000327
Why is this so and can we correct this on the affected VIM4s?
xavier
2
Referring to u-boot’s cmd/efuse.c:cmd_efuse() is should be possible to set the serialno with this command:
kvim4# efuse write 18 10 1234567890
Is this correct?
After we confirm, we will give you the appropriate method.
1 Like
xavier
4
FYI: I have tested two VIM4 boards that have serialno 0000000000, both are CPU rev C, i.e kvim4n
numbqq
5
Have you checked on oowow or ubuntu?
Could you provide the output of the commands below?
cat /sys/class/efuse/mac
cat /sys/class/efuse/usid
cat /sys/class/efuse/userdata
xavier
6
I previously checked in OOWOW and in uboot. Now in Android:
VIM4:/ $ cat /sys/class/efuse/mac
0x00: c8 63 14 74 1f 24
VIM4:/ $ cat /sys/class/efuse/usid
0x00: 00 00 00 00 00 00 00 00 00 00
VIM4:/ $ cat /sys/class/efuse/userdata
0x00: c8 63 14 74 1f 24 00 00 00 00 00 00 00 00 00 00
0x10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00