On Mar 24, 2016, at 11:17 AM, Guenter Roeck <[email protected]> wrote: > >>> Why isn't TZ configuring the bark time to what it wants? I'm lost >>> why we have to do this for them. >> >> So it was done like this to ensure we had a valid upgrade. The bootloader is >> using the watchdog to ensure the system is bootable and if not it will >> revert back to the working images. >> >> Bottom line is, for some versions of TZ out there, if we enable watchdog >> coming out of boot the bark time is already configured by the boot loader >> and TZ is configured to intercept this interrupt and do some register saving >> (for crashdump) and we end up getting a watchdog reset during boot. >> >> It’s even a little more complex, because in order for the TZ to save the >> registers you need to pad the BITE time a bit higher than the BARK time, but >> I was leaving that for another day. >> > Sounds like an op[timal target for using pretimeout ?
So the bark is basically a pretimeout, sure I think that will work. We can configure it to be off by default. Thanks for the heads up, I’ll take a look. -M
