tonyw wrote: ↑Sat Feb 01, 2020 12:49 am
OK, so that is my SDVersion. No problem, I don't mind it being distributed or used.
That said, the version of U-Boot in my other X5k (the 5040) has one of the later versions of U-Boot (SDVersion says 23-Mar-2018). I just tried it (by clearing the ethaddr and eth1addr settings) and it also regenerates the MAC addresses properly on reboot.
The version I have now is "8-Mar-2018", probably close to the one you have.
So what is the problem on your machine? I can't think of a hardware setting or env-variable that could prevent it from working. I don't have access to the U-Boot code, so I can't help you debug it.
As the addresses can also be input manually and saved, it is not a big issue... But it is still worrying, as it suggest there may be some hardware problem on my board.
There used to be on this forum a representat from Varisys... If you read this, could you please comment this issue?
So, once again, the facts:
If you change the stored values of "ethaddr" and "eth1addr" in the SD-RAM variables (listed by "printenv"), they will appear "changed" in the list when you type "printenv" again.
If you then type "saveenv" while the SD-RAM variables are "wrong", they will be saved wrong (I think, impossible to prove).
It doesn't seem to matter what is already in the "ethaddr/eth1addr" variables, they are *always* rewritten on reboot.
I tried setting "ethaddr" to "00:01:02:03:04:05", listing it to verify the change, then saving it with "saveenv", then listing it again to be sure, then rebooting. The original, correct value reappeared after a reboot.
I now tested it the same way, setting a 'fake' address and saved it with 'Saveenv'. The wrong address stays there after reboots, it is not replaced automatically! So, this definitely shows that the autowriting is not working in my machine...
Silly question: You ARE doing a case reset, aren't you?
Yes, I have tried both case reset and power off/on. No difference...
But so far other users has not commented this matter... Could you please test whether this 'autorestoring' works in your X5000? Thank you!