This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/MSP430FR2355: Delayed MSP Application UART1 output with CCS Debug operation

Part Number: MSP430FR2355
Other Parts Discussed in Thread: MSP-EXP430FR2355, MSP430F5528, MSP-EXP430FR2311, ENERGYTRACE

Tool/software: Code Composer Studio

OutOfBox_MSP-EXP430FR2355.zip

While using the USB backchannel UART (MSP Application UART) connection, output to hterm is delayed while running in CCS debug mode.  I observe immediate UART traffic from the MSP430FR2355 to the MSP430F5528 on the MSP-EXP430FR2355, but output to the PC over the USB connection is delayed.  In some cases, the latency is up to 7-8s.  Is there priority between the MSP Debug Interface and MSP Application UART that is causing the buffering delay.  Operation runs normally when the device is in free-running mode. 

Is there any way to get real-time updates over the MSP Application UART while using the Debugger?

I have attached example code based off of the OutOfBox demo.  Pressing S1 should initiate an MSP Application UART transmission at 115200 baud.

Thanks,

Robb

  • Hey Robb,

    I am looking into this further and will provide info as soon as I can.

    Thank you!

    -Mitch
  • Hi Robb,

    Please try Tera Term osdn.net/.../ .

    Ling
  • Hi Mitch,

    I observe the same behavior if I also use the MSP-EXP430FR2311.  Attached CCS project as well.

    Regards,

    Robb

    UART_MSP-EXP430FR2311.zip

  • Hi Ling,

    The issue is independent of serial terminal tool. The issue occurs with Tera Term, Hterm, Terminal integrated in CCS. Operation is normal outside of CCS in debug mode.

    Regards,
    Robb
  • I just encountered this with an MSP320FR2433 Launchpad and CCS 7.4.0. I see the delays only when debugging.

    The bursts appear to be about 64 bytes each (4-5 seconds). My scope says the USCI is putting the data out in a timely fashion, so the "stuttering" is upstream somewhere.

    Sometime between "apparently working" and "apparently not" CCS updated the board's ezFET firmware. It wasn't the only thing that happened in between, but I suspect it's relevant. Is there a way to find out what (revision, e.g.) firmware it put in there?
  • Hey Robb,

    After reaching out to the appropriate contacts, I have learned that the single USB channel bandwidth is divided between the backchannel UART and Debug and EnergyTrace data. UART communication has the lowest priority. These observations are from the perspective of the F5528 device (the eZ-FET emulator on the Launchpad). This explains why delays are only seen while debugging, and why the issue is independent of the serial terminal tool. Unfortunately, there doesn't seem to be a way to get real-time updates over the MSP application UART channel while also using the debugger.

    Thanks,

    Mitch
  • Is there a way to stop the EnergyTrace data? (I only need it sometimes.)
    and/or
    Can I back-level the ezFET firmware? This used to work fine.
  • Hey Bruce,

    Could you clarify a bit more what you mean by back-level the ezFET firmware? I am looking further into these questions.

    -Mitch
  • I was just wondering if I can go back to the ezFET firmware I was using before this change. I didn't see this symptom before CCS upgraded it.
  • Hey Bruce,

    Sorry for the delay.

    So it looks like this is possible to do, but reverting back to older ezFET firmare isn't recommended.

    You will want to navigate to the drivers folder in your CCS installation folder. Mine happens to be C > ti > ccsv7 (you may be using a different ccs version) > ccs_base > DebugServer > drivers. Here you will find the MSP430.dll file.

    If you right click on this and go to properties > details, you will see the file version (might be good to note which version doesn't work for you).

    Next, you will want to install an older CCS version (whichever one previously worked for you) and replace the current .dll file with the older .dll file.

    Please let me know how this works out.

    Thanks,

    Mitch

**Attention** This is a public forum