Unable to bypass fault exception about chipshouter HOT 4 CLOSED

bummer! i think it is already listed in the issues.

from chipshouter.

We're still investigating a few of these - when you say it's latched do you mean now it's in the "hv error" state and won't clear at all?

Or does it work for a few pulses (after power cycle) and then happen?

What's the firmware version of your device? We have some updates (and are working on a few new issues), the FW are per-device so we have to build it for the boardid.

from chipshouter.

HI Colin,

I tweak a bit on the code after posting the issue and sorted most of issue and paid a lot of time delay to cool down the caps.

Issue is because of diff between set/measured V and the fault generated is not cleared even after sending the clr_fault. I need to power cycle it to make it work again.

from chipshouter.

Got it! So if it does clear and then comes back after a few pulses this is likely a firmware fixable issue - we adjusted the "allowable mismatch" range on newer builds, as we had just empirically set some limit between "set and measured". During discharge the measured is somewhat off, and if you are changing the settings a lot it doesn't catch up.

The only "hard" errors we've seen will fault immediately when you attempt to arm (hard meaning we had to swap the unit).

We also changed the way the parameter storage is done - on older FW the EEPROM is written too often (see https://github.com/newaetech/ChipSHOUTER/blob/master/documentation/ERRATA_NAEER02.md). This can cause weird fault modes.

@alex-dewar has been building them on request as we didn't have an easy way to post them yet - easiest solution is to email [email protected], or post your board ID here if you prefer (or on discord https://discord.gg/chipwhisperer as can easily send DM). This includes some debug features to print the actual voltage delta which can make it more obvious what's going on.

from chipshouter.