Posted on March 23, 2013 at 12:02Seems like you should be using a different timeout methodology, resetting a modem/system would be a last resort if no AT commands, or progress in the upload/download were occurring.
There are other areas where the network/carrier side commands might take 150 seconds (2:30) to get a responses from the modem, but this isn't an issue with the CPU crashing.
The watchdog is more about your code on the CPU dying and not completing tasks, this can be done by kicking the time if all tasks flag themselves as active/functioning.
Doing standard timeout behaviour for peripherals can be achieved with software timers/counters running off SysTick or TIMx units, and should be part of any coding excercise, not just having end less while() loops, and resetting the system if the world isn't perfect.
