For my project, we are using a small network stack to communicate between different systems. I have flashed the network code, RTOS etc. to my TMS570lc4357 Hercules Development board with the XDS100v2 debug probe. I wish to run an instance of the network stack on my windows computer and send packets to the development board VIA USB using the SCI drivers.
I've written some driver code that should be pretty close to working for both the micro-controller, and for windows. I've tested that the SCI interrupts work on the board using CCS by sending data to the correct COM port in CCS terminal and setting a break point in my interrupt routine - all looks okay.
However, I wrote (modified) some code to send packets to the device VIA USB from windows, and when I compile the code in the windows CMD terminal and run it, pointing to the same COM port I used in CCS, which is also the COM port that corresponds to the XDS100 device in the Windows 'device manager'. However, nothing is received on the board (or perhaps nothing is sent from my USB), and that is clear when looking at the blue light that lights up when data arrives on the SCI driver.
The code for the Windows side is a slightly modified version of this code (I only changed some of the data structures to work with the receiving end on the board): https://github.com/libcsp/libcsp/blob/master/src/drivers/usart/usart_windows.c
And, although this isn't the root of my problems, the code for the board is here: https://github.com/AlbertaSat/libcsp/blob/master/src/drivers/usart/usart_m3.c
When the Windows code is run, it should be continuously sending data. The code says that it is sending but that seems not to be the case: at the same time I have the debug Window open in CCS. I'm not sure if this is just beyond the usefulness of the XDS100 probe, but if someone can point out what I'm overlooking that would be very helpful!
Another note: I ran similar code in Linux, and it looked like the data was being recieved, but I had trouble importing my CCS project to the linux version.
