• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 81 subscribers
  • Views 468 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.

TMS320F28379D: EtherCAT communication - target connection issue

electrocc
Expert 2450 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: CONTROLSUITE, TMDSCNCD28379D,

Hi,

Using the app notes spruig9.pdf, I want to test communication between a F28379D and an EtherCAT board (SPI communication).

I have to use example TMDSECATCNCD379D_EtherCAT_Reference found in ControlSuite (C:\ti\controlSUITE\development_kits\TMDSECATCND379D_V1.0)

After following all the procedure, I have to connect the target to load the program ; but I cannot, this message is displayed :

But I have no issue with the cable or anything, I can load another program without issue. This issue appears only with this program.

Do you have an idea ? 

Thank you,

Regards

  • 0
    TI__Mastermind 29421 points

    Hi,

    I am assuming you are using the TMDSCNCD28379D control card + TMDSECATCNCD379D adaptor board with your setup, is this correct? Are you using any other boards in your setup?

    Does you error only happen when you attach the TMDSECATCNCD379D adaptor board? If you are using CCS, can you try to test the connection with and without the adaptor board attached to debug the problem further?

    More JTAG debugging tips are included at this link.

  • 0 in reply to Gus Martinez
    Expert 2450 points

    Hi Gus,

    I'm using the TMDSCNCD28379D control card, but not the TMDSECATCNCD379D. I'm using an EtherCAT controller board from Beckhoff (FB111-0141) which will communicate in SPI with the 28379D.

    I think the issue is linked to the software ; I've tried different software's and configurations :

    • TMDSECATCNCD379D_EtherCAT_Solution_Ref with Ethercat Controller board : cannot connect with CCS
    • TMDSECATCNCD379D_EtherCAT_Solution_Ref without Ethercat Controller board : cannot connect with CCS

    • TMDSECATCNCD379D_PDI_HAL_API with Ethercat Controller board : can connect with CCS
    • TMDSECATCNCD379D_PDI_HAL_API without Ethercat Controller board : can connect with CCS

    Regards

  • 0 in reply to Gus Martinez
    Expert 2450 points

    Other question, do you know someone who can help with TwinCAT software ? 

    Following procedures spruig9.pdf or spruif9.pdf of TI, I cannot communicate between my DSP and the EtherCAT controller board (exactly same function than TMDSECATCNCD379D )

    Thanks

  • 0 in reply to Gus Martinez
    Expert 2450 points

    Other question concerning hardware : 

    Is this mandatory to connect /IRQ and EEPROM_Loaded from the ET1100 ? I've read on Piggyback datasheet that it wasn't mandatory..

    If yes, on which GPIO have I to connect these 2 signals ? 

    Currently, these signals are available on TMDSCNCD28379D, but I'll use later a TMS320F28379D in PTP package, so GPIO119 & GPIO136 won't be available.

    Thank you,

  • 0 in reply to electrocc
    TI__Mastermind 29421 points

    Hello,

    Regarding the connection issues:

    In the document I linked to on my previous post, there are some steps to verify the target configuration file used by CCS is correct. This is step 9 (Check Target Configuration) under the JTAG Debug Flow section. Can you follow those steps to test the JTAG connection using CCS? Please post the log if it stills fails.

    Regarding your other questions, I would suggest you create new forum threads on the subject (and any other new questions). Somebody more familiar with EtherCAT can better answer your questions. I can also split this thread for you. Let me know if you want me to do that.

  • 0 in reply to Gus Martinez
    Expert 2450 points

    Hello,

    There were two target configuration in the project :

    • When I use CCARD_F2837xD_XDS100v2.ccxml, I cannot connect to the MCU ; this is the report error :

      [Start: Texas Instruments XDS100v2 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\perriflo\AppData\Local\TEXASI~1\
    CCS\ti\1\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.

An error occurred while soft opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-151' (0xffffff69).
The title is 'SC_ERR_FTDI_OPEN'.

The explanation is:
One of the FTDI driver functions used during the connect
returned bad status or an error. The cause may be one or
more of: no XDS100 is plugged in, invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.

[End: Texas Instruments XDS100v2 USB Debug Probe_0]

    • When I use F2837xD.ccxml, I can connect to the MCU

    I will create a new topic, thank you.

    Regards,

  • 0 in reply to electrocc
    TI__Mastermind 29421 points

    That is very strange. I would have expected the CCARD_F2837xD_XDS100v2.ccxml to work given that the control card you are using has an embedded XDS100v2 on it. If you require further assistance please post a screenshot of both target configs for comparison.

  • 0 in reply to Gus Martinez
    Expert 2450 points

    It's very strange, I compared both configurations, there're identical.

    Regards,