Dear Sriram,
if FreeMASTER was working earlier, you need to focus at the changes you made in the application code. It is out of scope of this forum to analyze your code, I can only give you some general comments. You can also send more information about your customization of the motor control application to the dedicated motor-control community.
General reasons why FreeMASTER can become un-responsive when using a serial line:
- Application main-loop gets too busy and FreeMASTER operates in a polled mode (FMSTR_POLL_DRIVEN). A solution may be to use interrupt-driven communication or to lower the communication baudrate.
- System overload - if application is spending too much time in interrupts, not leaving enough of run time to communication processing.
- FreeMASTER reads a different ELF file than actually running in the MCU. This would cause the variables to be read from different addresses. A solution would be to reload proper ELF file or use the TSA runtime symbolic tables.
- System clock, pins or other configuration changes, resulting in UART becomes misconfigured.
- Physical damage of the chip (?) Does the FreeMASTER work better if you try your "yesterday's" version? If not, then a physical damage could be relevant.
Regards,
Michal
