30-10-2024, 10:57 AM
Thats perfect news.
Yes, I think it is inevitable to generate these double ECC errors when reading virgin flash.
But I think it is still neccessary to examine these addresses, sometimes. For me personally, this problem is solved if I can use the GDB commands.
For watches, my idea would be to allow the user to set up these addresses and have the user deal with the double ECC errors.
The user would have to make sure the addresses are never virgin flash when the debugger is halted(and the watches are updated).
I think in the scenario where you would want to look into the contents of the high cycle flash, you are able to ensure this, i guess.
But memory view and live watches are indeed probably not a good idea for high cycle flash.
Yes, I think it is inevitable to generate these double ECC errors when reading virgin flash.
But I think it is still neccessary to examine these addresses, sometimes. For me personally, this problem is solved if I can use the GDB commands.
For watches, my idea would be to allow the user to set up these addresses and have the user deal with the double ECC errors.
The user would have to make sure the addresses are never virgin flash when the debugger is halted(and the watches are updated).
I think in the scenario where you would want to look into the contents of the high cycle flash, you are able to ensure this, i guess.
But memory view and live watches are indeed probably not a good idea for high cycle flash.