![]() ![]() This occurs whether just powered up or under control by CCS7. I have to assume that one or more individual bytes, with its start and single stop period, has been interrupted so the terminal cannot get back in synchronisation. By corrupted, the debug output, on TeraTerm is repeated garbage. However, if I send a block of bytes using TeraTerm macro, the output stream must be being corrupted in some fashion, although an oscilloscope view looks no different. I can send single return bytes, which are handled via the high priority interrupt, without apparently affecting the output stream. ![]() I can see this on the UART debug port of the Launchxl-TMS570004. I have a design which continuously outputs serial data at 1MBd (no inter-byte gap) using the low priority interrupt to send data, re-loading the message once complete.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |