Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

I tried to get the watchdog to trigger on a V3C with the following code

while(i++ < cnt)
{
DBGPRINTF("test");

and timing the loop out of interest.

I failed to trigger the watchdog, even when cnt was so high that the loop took over 40 seconds to run. I have triggered a watchdog on another device in the past with excessive debug output, so I am surprised that I could not trigger the V3C.

Are there any details about the watchdog for this device (or any others)? I assume the watchdog code is very much implement by the OEMs rather than being part of the BREW reference source.

yeah its handset /oem dependant, some don't appear to have one at all, others do, it could also be a lot longer than 40 seconds.. I've seen strange ones where it only triggers the watchdog after repeated runs of the same long function, rather than stalling the function for a long time.
Also if pre coffee memory serves, some functions like DBGPRINTF will satisfy the watchdog function, i vaguely remember coming across something like that before.

yeah its handset /oem dependant, some don't appear to have one at all, others do, it could also be a lot longer than 40 seconds.. I've seen strange ones where it only triggers the watchdog after repeated runs of the same long function, rather than stalling the function for a long time.
Also if pre coffee memory serves, some functions like DBGPRINTF will satisfy the watchdog function, i vaguely remember coming across something like that before.

In many phones sold in US has watch dog timer settings around 50 - 60 seconds, however in Japan (KDDI network) they are mostly set to 2 - 4 seconds

In many phones sold in US has watch dog timer settings around 50 - 60 seconds, however in Japan (KDDI network) they are mostly set to 2 - 4 seconds