12/26/2023 0 Comments Nrf segger embedded studio![]() ![]() In many scenarios this is not compatible with the real time requirements of the original program. Setting up and using a UART connection requires lots of resources and processing time from the hardware platform. You can print to the UART port/connection whatever you want: text, numeric values, variables, line numbers, etc. UART logging removes the limitations of LED debugging. However it is difficult if not impossible to see what the value of a variable is or what the actual flow of the code is. In practise, you can use a LED to indicate when the code passes by a certain point or when the internal state of the program changes to a given value. Unfortunately the information that a LED can provide is very limited: you can only play with the number of blinks and the duration of those blinks. ![]() Using LEDs to debug code is easy (you just have to change on/off state of an output PIN). The simplest techniques used in embedded debugging are blinking LEDs and UART logging. Engineers need to implement smart mechanisms to visualise the flow of their code and spot errors without impacting the performance and functionality of the original software. There is no terminal to display what is going on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |