• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 83 subscribers
  • Views 449 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F280049C: XDS110 serial port usage crashes the connection to target

Kustaa Nyholm
Expert 2005 points
Part Number: TMS320F280049C

I'm on macOS (Monterey 12.2) and Code Composer Studio: 11.0.0.00006 

We send some data out from our target at using an UART on the F280049C.

We capture this by opening the serieal  port at  "/dev/tty.usbmodem000000001" on macOS.

If/when we do that the connection from CCS Debugger to target will crash (become un responsive and

we get some error message in the console) within minute or so.

If we capture the same data using an external FTDI serial/usb adapter we do not have any problems.

The same problem happens with Windows too in my colleagues lap top (Win10).

cheers Kusti

  • 0
    Expert 2005 points

    Forgot to include sample error message:

    C28xx_CPU1: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU1: GEL Output: ... DCSM Initialization Start ... 
C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...
C28xx_CPU1: GEL Output: ... DCSM Initialization Start ... 
C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...
C28xx_CPU1: GEL Output: ... DCSM Initialization Start ... 
C28xx_CPU1: GEL Output: ... DCSM Initialization Done ...
C28xx_CPU1: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.4.0.00129) 
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

  • 0 in reply to Kustaa Nyholm
    TI__Mastermind 19795 points

    Hi Kusti,

    Thanks for the question.

    Just to make sure, can you list the other COM port devices that get detected when you plug in the C2000 device? The reason I say this is that this sounds like something that would happen if the wrong COM port gets used (of the potentially 2 that are available on the debugger).

    Basically, depending on the device, there can be 2 COM ports that get broadcasted to the PC. For example, here's what happens when I plug in the F28004x LaunchPad into my Windows PC:

    There's two COM ports that are available, but only the first one (User UART) can be used for serial comms.

    If you see two, please try the other one and let me know if that works.

    Regards,

    Vince

  • 0 in reply to Vince
    Expert 2005 points

    As I'm on mac the devices appear in /dev directory as 

    tty.usbmodem000000001 and  tty.usbmodem000000004

    The one ending with '1' works but crashes eventually CCS debugger connection as reported,

    the one that ends with 4 does not appear to work at all, I can open the port but no data comes through.

    I believe the same was observed on Windows as well.

  • 0 in reply to Kustaa Nyholm
    TI__Mastermind 19795 points

    Hi Kustaa,

    Thanks for the follow-up, let me request the debugger experts to take a look at this.

    Regards,

    Vince

  • 0 in reply to Kustaa Nyholm
    TI__Guru**** 463681 points

    Hello,

    Kustaa Nyholm said:
    The same problem happens with Windows too in my colleagues lap top (Win10).

    I tried running the SCI loopback example on my F280049C LaunchPad. I connected a CCS Terminal program to the XDS110 UART and was able to successfully send/receive serial data

    You colleage has the target crash when they connect to the same com port on Windows 10?

    ki

  • 0 in reply to Ki
    Expert 2005 points

    Hi, I've not tried this as at the moment I don't have F280049C LaunchPad.

    However you comment sparked an idea.

    I tried to receive the serial data with CCS Terminal and macOS 'screen' program.

    Both of those do not crash the debugger.

    Only my Java program seems to crash this.

    Which is kind of mystery making, how can a Java program reading from serial port on two different operating systems crash the debugger connection.

    cheers Kusti

  • 0 in reply to Kustaa Nyholm
    TI__Guru**** 463681 points
    Kustaa Nyholm said:

    Only my Java program seems to crash this.

    Which is kind of mystery making, how can a Java program reading from serial port on two different operating systems crash the debugger connection.

    This is indeed a mystery. Your java program likely causes some issue with the USB connection, hanging both serial and XDS connection. Other than that, I can offer no other insight.

    ki

  • 0 in reply to Ki
    Expert 2005 points

    Something like that. But it is mystifying because as far as Java is concerned it is not a USB device but just a regular serial port. I'm using PureJavaComm which under the hood (on macOS) uses select() and read() , very basic and standard Unix IO and on Windows it uses a completely different mechanism that uses Windows overlapped IO on the COM port. Beats me. I will put a few more hours into this cause I really would like to understand what is going on (especially as I'm the author PureJavaComm, which has been very successful and has been performing nicely for me and hundreds of user for more than ten years).