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

Developer

Forums

Forums:

Hi.
I'm running into issues with watch dog on LGE VX6100.
I have a test application that fills address book with 500 records. Each record has 5 data fields. Of course, this process takes a while to complete, so - I'm using ISHELL_Resume to return control to BREW after each record creation. This way the control is returned to BREW each 1 second at least. But it looks like the watch dog still is not really happy about this solution - the device still occasionaly reboots/turns off.
I've tried another way of breaking long cycles to smaller steps - ISHELL_SetTimer with a 100ms timer interval. And it makes the watch dog completely happy - no reboots.
So, the question is - what is the difference between those 2 methods from watch dog point of view? Why using ISHELL_Resume is not calming down the dog, while ISHELL_SetTimer does?
Excuse me for being a little abstract with my question, no code samples etc. I'll provide those if needed, I just hope that some of the gurus can just pop up with an answer like "Yeah, it's easy... The problem is..." :)
Maybe it's a device issue? Is ISHELL_Resume suppose to work with watch dog?

ISHELL_Resume is for registering callbacks. From the API...
Quote:This function allows a callback to be registered with the AEE Shell. It adds the callback to the AEE Shell's list of pending operations. The AEE Shell invokes the callback function the next time the event loop is called, allowing an application or object to cooperatively multitask. If the callback has already been registered, it is cancelled (de-registered) and then re-registered.
Your probably setting off the watchdog because there are no other callbacks in the queue so your making a tight loop. ISHELL_SetTimerEx makes sure that the application is not in a tight loop by delaying each function call by a specified interval.

ISHELL_Resume is for registering callbacks. From the API...
Quote:This function allows a callback to be registered with the AEE Shell. It adds the callback to the AEE Shell's list of pending operations. The AEE Shell invokes the callback function the next time the event loop is called, allowing an application or object to cooperatively multitask. If the callback has already been registered, it is cancelled (de-registered) and then re-registered.
Your probably setting off the watchdog because there are no other callbacks in the queue so your making a tight loop. ISHELL_SetTimerEx makes sure that the application is not in a tight loop by delaying each function call by a specified interval.