Nabih Estefan writes:
> Recent CDMSK Watchdog changes (eff9dc5660fad3a610171c56a5ec3fada245e519)
> updated the CDMSK APB Watchdog to not free run out of reset. That led to
> this test failing since it never triggers the watchdog to start running.
> No watchdog running means that the timer and cou
Nabih Estefan writes:
> From what I can tell this is the same issue Thomas was looking at yes.
>
> I saw the failure on the master branch at the v9.2.0 tag (ae35f033) and just
> re-tested it against (83aaec1d) and still see it. I haven't seen it be an
> intermittent failure, it has failed 100% of
>From what I can tell this is the same issue Thomas was looking at yes.
I saw the failure on the master branch at the v9.2.0 tag (ae35f033) and just
re-tested it against (83aaec1d) and still see it. I haven't seen it be an
intermittent failure, it has failed 100% of the time that I have tested it
Thomas Huth writes:
> On 13/12/2024 01.26, Nabih Estefan wrote:
>> Recent CDMSK Watchdog changes (eff9dc5660fad3a610171c56a5ec3fada245e519)
>> updated the CDMSK APB Watchdog to not free run out of reset. That led to
>> this test failing since it never triggers the watchdog to start running.
>> No
On 13/12/2024 01.26, Nabih Estefan wrote:
Recent CDMSK Watchdog changes (eff9dc5660fad3a610171c56a5ec3fada245e519)
updated the CDMSK APB Watchdog to not free run out of reset. That led to
this test failing since it never triggers the watchdog to start running.
No watchdog running means that the t
