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.

CC3200 Debug port error occured

Other Parts Discussed in Thread: CC3200-LAUNCHXL, CC3200, LAUNCHXL-F28069M, UNIFLASH

Hi,

I am using CC3200-LAUNCHXL, acting as an MQTT client, to send messages received from the cloud via UART to another MCU. In order to accomplish this, I simply expanded upon the mqtt_client project found in the examples folder of the SDK. I am using CCS 6.1.1.

 

However, I ran into problems with “Debug Port Error” messages. The errors seem random so they’re a tad hard to describe. Most of the time, the project loads onto the device fine. The problems occur when the project is ran. The debugger sometimes pauses the execution of the code and the console will display some cortex error. The confusing part is that the error messages that are displayed are often different. The screenshots below display some of the different messages I’ve encountered. Furthermore, sometimes the errors don’t occur at all. I’ll terminate the debug session, rebuild and reload (and also hit the reset button on the device), and the code will run, seemingly forever, just fine. I’ll repeat the same process again, but this time the errors will halt the execution of the code as described. I’ll hit run again to resume the execution, but shortly after another debug port error occurs.

 

I thought perhaps I did something wrong, so I reverted back to the original mqtt_client, but the problems persisted. I tried other simpler projects such as blinky, and still ran into the same issues. At times, the project executes without any halts, other times it is stopped multiple times as I attempt to resume. I am not sure why the behavior is different as I am changing nothing in between these attempts. I literally just build, reset the device, and load again. The project that I am running seems to have no effect on the behavior.

One thing I have noticed, is that these errors seem to happen a lot more frequently and quicker when I have the other MCU also connected to my machine. I am aware that only one FTDI device can be connected to the PC when loading. What I do is first load the CC3200 code, and begin running, then connect the other MCU, load its code, and run it. The errors seem to happen very frequently when in this configuration. On the other hand, when only the CC3200 is connected, the debug port errors typically occur less frequently, and sometimes they don’t occur at all.

I have the jumpers connected as shown in the Getting Started guide, including the SOP2 jumper. I did change the UART jumpers to the BP configuration when I was trying to communicate with the other MCU.  I’ve read through some of the posts on E2E, and haven’t really found a solution that has worked as of yet. Perhaps, I haven’t found the right post yet. 

Any help would be greatly appreciated, thanks.

Kevin

  • Hi Kevin!

    Here are a couple questions that might help us guide you:

    • What is the other MCU that you are programming and communicating to?
    • Are you using the UART pins that are normally used to print debug messages to connect to the other MCU? / Did you remove all UART_PRINTs that were used for writing debug messages to the console?
    • Are you connecting the grounds between the boards?
    • Can you check to see if the same issue occurs with an updated version of CCS?

    If the problem is made worse by using additional ports on your machine, it would make me lean toward thinking this is a CCS or PC issue. If your changes allow for testing it, I would also be interested in seeing if the problem occurs with the UART jumpers in the Flash position instead of the BP position.

    Best Regards,

    Ben

  • Hi Ben,

    Thank you for the response. I am communicating with a C2000 (LAUNCHXL-F28069M). I'm just connecting jumpers between P55 and P57 to the corresponding UART pins on the F28069M launchpad, so no I am not connecting the grounds between the boards.

    I am using UARTA0_BASE to communicate to the other MCU, but I changed the console definition in uart_if.h to UARTA1_BASE and that is where I have the UART_PRINT messages being sent to, but I am not viewing these messages.

    I will try testing on an updated version of CCS. I was using the older one due to a bug on the C2000 side which required use of the older CCS.

    As far as the UART jumper configuration goes, I had them set in the Flash position when testing all of the other labs and even when using the mqtt_client lab before connecting to the C2000, and I did also see these problems when in this configuration.

    Thanks,

    Kevin

  • I have tested on an updated version of CCS and no luck. I am still facing the same issues. I'm going to have to guess that it's got something with the way I'm configuring the environment, not too sure.

    I tried running my code using uniflash to flash it onto the device and then just running out of the boot, and that worked fine. I've tested it several times now, and the code executes as expected.
  • Kevin,

    Were all tests performed with the same PC? Can you try with a different one just as a sanity check?

    Will using UniFlash for long-term execution work for you during development?

    Best Regards,
    Ben
  • Ben,

    Yes, all tests have been performed on the same PC. I will try to get my hands on another for further testing.

    I do believe using UniFlash will be okay. I will have to do some minor changes such as switching UARTA0 back to the console and use UARTA1 for communication with the C2000 for debugging purposes.

    Thanks,
    Kevin
  • Hi Kevin,

    Try, close all applications that uses the same COM port as your CC3200 Launchpad, before starting CCS debug.

    - kel