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.

Seeking Efficient Team Project Methodology to share a 6678EVM board

Hi, All.

We are using 6678EVM for our wireless team project. Each guy is in charge of individual core among 8 cores in order to develop individual function block.

Each of them is really wanting to get a dedicated CCS window and Debugging window such as Log service window on their desktop with sharing single 6678EVM board simultaneously. Unfortunetly as of now, we cannot find out the way to sharing a board simultaneously for our team project.

I'd really appreciate it if you give me the way to solve the problem.

Thanks in advancd.

 

  • Hello Sangchul,

    If I understand correctly, you have one 6678 EVM and you want to set it up so that up to 8 different people can each access/control a CPU via their own CCS GUI interface at the same time. If that is correct, then it it is tricky (and probably not possible)

    There can only be one Debug Server instance for a target. If there is one CCS instance that has successfully started a debug server instance with the board, then it is not possible for another CCS instance to also try to access the same target.

    now it is possible to open multiple CCS GUI windows for the same CCS instance.

    http://processors.wiki.ti.com/index.php/Multi-Core_Debug_with_CCSv5#Using_Multiple_Workbench_Windows

    This will allow visibility into multiple cores (debug context) at the same time.

    But actions done in one window will impact the other. For example, if you halt the CPU in one window, the other window will always switch context to the halted CPU. And terminating the debug session in one window will terminate the debug session for all.

    And also you need to be using the same machine to access the windows (you can't have one CCS GUI window for core 1 on one PC and another CCS GUI window for core 2 on another PC).

    This functionality was not designed for simultaneous multiple users, but more for a single user wanting to see information for multiple cores at the same time.

    So unless the above limitations are fine with you, it is unlikely that you can do what you wish regarding simultaneous access with CCS. Sorry.

    ki

  • Thank you for your kind and obvious answer, Ki Soo.

    Well...It seems like that there is no possibilty to do team project we want with a 6678 EVM.

    Do you know whether or not TI has a plan to make multi-user development environment with a 6678 EVM or the other multi-core board?

     

  • There is no specific plan to implement the functionality you are looking for.

    There is one workaround that perhaps may work for you. There is a DSS example called the Test Server. This would allow multiple users to remotely send commands to a single running instance of DSS that is connected to the one EVM. However this is strictly console based, you would not have GUI visibility. Do you need GUI visibility?

  • If it is possible to send their own command such as loading or executing their own *.out and receive their own debugging information on their own desktop PC console simultaneously and independently, we can consider it.

    The developer in charge of own core is likely to perform everything on their dedicated PC individually.

    Moreover I have a concern about restricted debugging information when we use a console. Our system should be performed in less than 1 ms realtime system, so that we cannot use printf(), System_printf().  I think we consequently need a GUI visibility of CCS in order to use a Log Service.

    Thank you.

  • Sangchul Oh said:
    If it is possible to send their own command such as loading or executing their own *.out and receive their own debugging information on their own desktop PC console simultaneously and independently, we can consider it.

    Yes. Basically there is one remote debug instance for the target with multiple debug sessions - one for each core. Separate developers can send remote commands to a particular debug session.

    See the readme.txt in the Test Server directory for more details:

    <CCS INSTALL DIR>\ccsv5\ccs_base\scripting\examples\TestServer

    Sangchul Oh said:
    Moreover I have a concern about restricted debugging information when we use a console. Our system should be performed in less than 1 ms realtime system, so that we cannot use printf(), System_printf().

    My usage of the term "console" for the Test Server is regarding a terminal console (like DOS window), not a C I/O console.

    Sangchul Oh said:
     I think we consequently need a GUI visibility of CCS in order to use a Log Service.

    The example I mention has no GUI debug visibility. If GUI visibility is needed, you will need your own solution outside of what is supported by CCS.

    Thanks

    ki

  • Thank you for the answer.

    I would appreciate it if you trigger the necessity regarding multi-user development environment with CCS GUI visibility for the single EVM in TI, if you can later.

    I really look forward to seeing the CCS, and I will expect to hear good news from you.