Bluetooth serial programming

liam.zbasic · Post by **liam.zbasic** » 24 February 2010, 7:57 AM

An Application Note on this subject would be very useful.

GTBecker · Post by **GTBecker** » 27 February 2010, 17:00 PM

ZXCmdMode, whether invoked by code or by OS ATN character (Pesistent&H13=ATNCharcode) capture, succumbs to the watchdog. Downloads via ZXCmdMode fail if the watchdog is running.

That makes the watchdog and the OS-captured ATN character download mutually exclusive. And, if captured by code (Pesistent&H13=0), the watchdog can and must be closed before calling ZXCmdMode - but that leaves the machine, um, unwatched. ZXCmdMode could disable the watchdog but, again, leaving it unwatched.

Don, can ZXCmdMode, instead, hit the watchdog often in its control loop? That would solve both: ZXCmdMode could run with the watchdog running, and that mode would have the protection of the watchdog even after the application handed over control.

Post by **dkinzer** » 27 February 2010, 20:15 PM

GTBecker wrote:[C]an ZXCmdMode, instead, hit the watchdog often in its control loop?

Perhaps. Some careful analysis is needed to determine the places where it would need to be done. If this were implemented, it wouldn't be available in devices already in the field since the code changes would be in the bootloader that we install during manufacturing. If needed, existing devices would need to be sent back to be re-programmed.