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.

DSS scripting for multiple boards

hi,

While trying to modify the DSS script (javascript version provided in wiki) for multi board and I am getting stuck trying to answer the following questions.

The requirement is to initialize one particular board from the DSS script with some parameters and then initiate the other board, with different configuration, with the same parameters from the same DSS script.

The problem I am facing is to initiate two different debug Server from the same scripting environment. Is this possible. If so can you quote any examples how to accomplish this?

And also how do I get the control back to the DSS script while the program is still running on the target board ie, session.target.run() returning while the program is still running?

Thanks in advance,

- Murali.

  • Are you trying to control two different boards connected to the same PC via two different emulators with one DSS script at the same time? If so, this is possible. You can control them both with the same debug server instance. Just open a debug session for each one like the multi-core example on the wiki. You will also need to create a custom target configuration so that you have both boards in one config file.

    Muralidhar Raju Gangaraju said:
    And also how do I get the control back to the DSS script while the program is still running on the target board ie, session.target.run() returning while the program is still running?

    Use: session.target.runAsynch();

    Thanks

    ki

  • Thanks lee for the quick Response.

    I still couldn't get  the script working and after analysis I find the following issue.

    I have connected two different boards ( which have different board configuration files ie, ccxml) using two emulators. 

    Both the emulators are connected to the PC using USB.

    The problem I am facing is I am unable to connect to both the boards as both the configuration files point to USB PORT 0.

    I could have used ETH and USB but apparently I see this to be the test infrastructure, so trying USB/USB connection method.

    The question is how do I map the board configuration files to the respective ports?

    How do I discover which emulator is connected to which port and mention the same in the advanced properties of the target configuration?

    Thanks in advance,

    - Murali.

  • What emulators are you using? Provide the vendor and model number.

    ki

  • I am using Spectrum Digital XDS560V2 emulators.

    - Murali.

  • Muralidhar Raju Gangaraju said:
    The problem I am facing is I am unable to connect to both the boards as both the configuration files point to USB PORT 0.

    Set the second emulator to port 1. I believe that the one that is port 1 is the second emulator that got enumerated.

  • ki,

    I have tried changing the port ID to 1 through IDE and it worked.

    But when I use the same saved .ccxml files from the script to connect and load the programs, I am getting the memory write error while loading on to the second CPU on the other board.

    I suspect the program is getting loaded to the 1st board CPU which is same ie C64XP_0.

    When the same script is run with debugsession.terminate(), it loads perfectly.

    The issue which was seen was the setConfig which is run on the second .ccxml file. It is observed that the setConfig is not being effective and while trying to resolve for the CPU's during target connect, it resolves the CPU's of previously configured board. correct me if I am doing anything wrong.

    Is there any way where I can switch to the other board without terminating the previous debug sessions and debug in parallel through dss script?

    It would be really helpful if you could provide me any sample scripts for multiboard configuration connected with emulators.

    Thanks in advance,

    - Murali.

  • Murali,

    You should only have one ccxml file. The one file should define both targets. You should be able to then open debug sessions for both of them and debug in parallel.

    Please provide your script and ccxml files so I can see.

    Thanks

    ki