• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 82 subscribers
  • Views 511 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.

CCS/TMDSCNCD28379D: Losing connection with the computer

Renato Amorim Torres
Intellectual 260 points
Part Number: TMDSCNCD28379D


Tool/software: Code Composer Studio

Hello everyone,

I am currently facing some problems with the connection between the DSP and my computer. The environment that I am running the DSP is quite noisy (EMI), however, I was wondering if there is anything that I can do regarding communication settings that may make the communication more immune to noise, even if it means a slower communication. Additionally, every time that I lose connection I am not able to connect back again unless I reload the code. Is it possible to reconnect to the DSP without having to reload the code?

Does anyone know how the DSP loses connection? Is that because of a series of packages that are corrupted? Is it because of the communication clock gets messed up? I have no clue how it works.

Right now, I generally use the dual graph to plot some data while running the code. Do you know if plotting too much data while the system is running can make the communication more susceptible to noise? 

I apologize for the number of questions, but I appreciate any help even if it does not cover all of them.

Thank you,

Renato

  • 0
    TI__Guru** 115881 points

    Hi Renato,

    I did not understand below point in your query -

     Additionally, every time that I lose connection I am not able to connect back again unless I reload the code. Is it possible to reconnect to the DSP without having to reload the code?

    How are you reloading the code if there is no CCS connection?

    Also in system with high noise, it is difficult to point what has caused the issue. It could be because of the noise on reset pin, or noise on one of the JTAG signal. High data log means more toggle on IOs which can make the noise issue more prominent but just that alone should not cause this issue.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Intellectual 260 points

    Hi Vivek,

    Thank you for your response.

    I was not clear regarding  "Additionally, every time that I lose connection I am not able to connect back again unless I reload the code. Is it possible to reconnect to the DSP without having to reload the code?". I will try to clarify that.

    When I am running my system I can see all my variables in real-time in the Expressions window. I can also see some waveforms plotted in the Graph Window. At a given moment my connection is lost due to EMI and I cannot see any variable or waveform anymore. However, my system is running fine which means that the problem is just in the connection between DSP and computer. I was wondering if that is possible to re-establish the connection between the computer and the DSP without stopping the system so that I can see again my variables and waveforms. In order to do that, I tried clicking on "Connect target", but it does not work. In the end, I have to shut down the system, reload the code and start everything over again.

    I was wondering if it is possible to do be able to see my variables again after the connection is lost. I hope I was clear now.

    Thank you for clarifying that a high data log means more toggle on IOs which can make the noise issue more prominent but just that alone should not cause this issue.

    Finally, I do not think the problem is in the reset pin since the system keeps running fine.

    Thank you,

    Renato

  • 0 in reply to Renato Amorim Torres
    Intellectual 260 points

    Summarizing my question: If I have a running debug session running, but my connection with the board gets interrupted either by EMI or some connection issue, is it possible to re-attach the debugger to the currently running code at the board without starting a new debug session?

  • 0 in reply to Renato Amorim Torres
    TI__Guru** 115881 points

    Hi,

    Yes, you should be able to do by removing the Gel file from your target configuration file. Double click on target configuration file and then select "Advanced" view and select the C28x. Now delete the gel file and click on "Save". Now you can use this configuration file for CCS connection and you should be able to re-connect to target without resetting the device.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Intellectual 260 points

    Hi Vivek,

    Now I am having another problem. I am not being able to load the program to CPU2 with this new target configuration. Do you know what should I do?

    Is there any material that explains what exactly are the target configurations, how is it related to the debugger. I feel that I need to better understand the basics of it.

    Thank you,

    Renato

  • 0 in reply to Renato Amorim Torres
    TI__Guru** 115881 points

    Hi,

    It's because CPU2 is in reset. Gel file has code to release CPU2 from reset which is not there now. Gel file is needed to initialize the setup to make debug environment easy for customer. Now you need to run the CPU1 BOOT code before loading the code on CPU2. Just connect to CPU1, issue reset and the click on run icon. After that try to load the CPU2 code.

    Regards,

    Vivek Singh 

  • 0 in reply to Vivek Singh
    Intellectual 260 points

    Hi Vivek,

    I finally got it working as I wanted. Right now I can reconnect to both CPUs in case the connection is lost.

    Your last answer helped me, but by doing what you said I was losing connection of CPU1 when resetting it and not being able to reestablish it. What I did in the end was:

    1- Removed initialization script from CPU1

    2- Just modified the file f28377d_cpu2.gel by removing all the content in the OnTargetConnect() callback.

    Let me know if you think it can result in side effects when running the DSP. So far, it seems to be working fine.

    Thank you