Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Using the Keil Debugger with a program that uses the other serial port
Question: Is it possible to use the Keil Debugger with a firmware that uses the other serial port? Does the serial interrupt that halts the debugger affect the serial transmissions of the other UART?
The limitation in this method of debugging any interrupt based firmware is that the debug environment is not real-time. Whereas the firmware will be running in real-time. So the interrupt may not get serviced or reach completion in time since the firmware is being stepped through or held at a particular line (to analyze the variables). Hence the process based on the interrupt may fail though it would have succeeded if the firmware was running in real-time. The debugger is a good tool for debugging code flow but may not be as useful when working with interrupts.