Issues with checksum since ESP_S3 last image release

[belem2050]

After updating my chip with the latest image, I encountered a checksum mismatch between the target chip and the version of the code I built. It seemed like the issue was related to the nanoFrame.CoreLibrary, which needed to be updated. I made the necessary changes, but now I'm facing this new issue, and I'm not sure why. Does anyone have an explanation?

Thanks!

[josesimoes]

There was indeed a new release of the mscorlib and all the others. Which requires an update of the firmware too.
The image above is not showing any error... care to elaborate?

Also make sure that all nuget packages are updated to the latest versions.

[belem2050]

Yeah sure
Sorry for the late reply. I've updated all nuget packages of my project and the mismatch seemed to have disappeared.
But what I was then encountering was the console output unexpected command=0x.... which leads to a disconnection of the chip in visual studio and subsequently losing the debugger. I don't know if the issue was specific to the chip I was using but I downgraded to the previous image and got it to work.
Unfortunately, when downgrading, I had to stick to old versions of some of the nuget packages I am using.

[josesimoes]

Those unexpected commands that you are seeing are result of garbled packets or unexpected state from the device.
Most of the times you can safely ignore them.

[belem2050]

Alright! Thanks so much for all what you've done and are doing for the community.

[networkfusion]

It might be worth running the --masserase command when flashing the new firmware to the device as an extra hint (if you have not done so).