LAUNCHXL-F28379D: Using the MCU Signal Sight Plugin

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi all,

         I am trying to use the MCU Signal Sight plugin on my launchxl-f28379d. I am able to get it running with data being captured every 1 ms (using a Timer interrupt and SCIA). I have the following doubts:

  1. If I wish to capture data every 10 us, then the required Baud rate becomes high - almost 4 Mbps. I can achieve this by increasing LSPCLK. But, is this supported in SCI? If not, then what other alternatives are available?
  2. Can Signal Sight be used simultaneously to capture data in both CPU1 and 2? If yes, then can the same SCIA be used to capture data in both CPU1 and CPU2? 

Thank you

  • Hello,

    Great to hear you have been using our new MCU Signal Sight tool! Below are the answers to your questions:

    If I wish to capture data every 10 us, then the required Baud rate becomes high - almost 4 Mbps. I can achieve this by increasing LSPCLK. But, is this supported in SCI? If not, then what other alternatives are available?

    If using the XDS 110 (present on the LAUNCHXL-F28379D) as a UART-to-USB bridge, I don't believe this high a baud rate is achievable, the XDS only allows for around 1Mbps without dropped packets in my experience. However, another option is increasing the buffer size that Signal Sight uses on the target, especially since F2837xD has a large amount of memory available to it.  

    See the third bullet in the Troubleshooting guide here for how to avoid skipping data.

    Can Signal Sight be used simultaneously to capture data in both CPU1 and 2? If yes, then can the same SCIA be used to capture data in both CPU1 and CPU2? 

    Since CPU2 has its own project and Sysconfig file, MCU Signal Sight support could be added for CPU2 as well. The SCIA peripheral is also accessible via CPU1 or CPU2, but having both CPUs access the SCIA simultaneously would require some sort of an arbitration scheme. Let me loop in the multi-core expert to comment further.

    Best Regards,

    Delaney