Page 2,231 of 3,183 pages ...
Quote:
The WDOG module has user-accessible, 16-bit registers used to configure, operate, and monitor the state of the watchdog timer.
. . . .
A 32-bit access should be avoided as the system might go to an unknown state.
|
Will have to look at the asm output of gcc to be certain, but that "watchdog_service" function quoted in an above post sure looks to me like it will generate 32-bit write operations.
And in contrast to that opening description, the watchdog service register, service keys are specified as the 32-bit writes used in the quoted bit of service code.
The test in the service code is testing if the watchdog has been enabled.
What is not (yet) exposed in the quoted code is the time period.
The range of time periods is from 0.5 to 128 seconds in 0.5 second increments based on a clock feed that does not change with core clock speed settings.
It is hard to imagine that USB can't transfer 32 packets in even the 1/2 second minimum time setting.
Grumble,
Will have to dig further into this RAM Kernel code to learn why it is failing.