Hi Stefano,
On Monday, December 3, 2012 10:03:22 AM, Stefano Babic wrote:
I am thinking about if we need some kind of protection to avoid to destroy very easy the SOC. Running a fuse command can be much more dangerous as scrubbing NAND or erasing flash.
What about to add at least a "-y" option when we write the fuses, in the same way we have for the "nand scrub command" ? This does not forbid to use the command in scripts, but it can maybe avoid to destroy the SOC when the command is wrong tipped on the console.
What do you think ?
That makes sense. There could be the same kind of warning confirmation defaulting to no that would repeat which fuse is about to be programmed.
As to the value passed for fuse row programming or overriding, do you think that it's fine to force it to be hex, or that choice should be given with '0x'? I don't really like implicit base selection, but it's clear in the help message, and it is handy for writing MAC addresses without repeating the '0x' for each byte.
Best regards, Benoît