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.

LAUNCHXL-F28P65X: LAUNCHXL-F28P65X: Cannot fix the EtherCAT

Part Number: LAUNCHXL-F28P65X
Other Parts Discussed in Thread: C2000WARE

Hello,

I am following the FAQ to be able to fix the EtherCAT issue, but I can't get it to work. I am not able to see the slave in TwinCAT.

First, I plugged in my F28388D slave to make sure my TwinCAT setup is working:



For the program_i2c_ESC_eeprom_F28P65, I build it for FLASH. Then, in debug mode, I run the code, observe some values updating in the RX_MsgBuffer, and then it reaches ESTOP0:

After that I import f28p65x_cpu1_pdi_hal_test_app, I add ethercat_slave_cpu1_hal_PHY_check.c:

I right click on the original ethercat_subdevice_cpu1_hal.c file and exclude it from build.
Should I build in FLASH or LAUNCHXL_FLASH?

If I try FLASH, then in Twincat I try to scan for devices, nothing. I try PORT0 and PORT 1, power cycle...

If I try to build in LAUNCHXL_FLASH I get the error:


I don't get the FAQ: d. Build and load the program to CPU1. There will be a few ‘ESTOP0’ commands, click resume until the code runs without stopping

When I run the debug, it seems to be stuck in:

    if(initStatus == ESC_HW_INIT_FAIL)
    {
        while(1)
        {
            //
            // Toggle Error
            //
            ESC_signalFail();
        }
    }

Thank you

  • Hi,

    The expert is on leave. Please expect an answer by 18th March.

    Thanks & Regards,

    Sinchita

  • Hi,

    I will add this to the FAQ since there is a bug with the LAUNCHXL_FLASH build configuration in C2000WARE version 5.01.

    I right click on the original ethercat_subdevice_cpu1_hal.c file and exclude it from build.
    Should I build in FLASH or LAUNCHXL_FLASH?

    You should use the FLASH build configuration. You will also need to define '_LAUNCHXL_F28P65X' at the top of your ethercat_slave_cpu1_hal_PHY_check.c file, or add it to your predefined symbols for your project. 

    I don't get the FAQ: d. Build and load the program to CPU1. There will be a few ‘ESTOP0’ commands, click resume until the code runs without stopping

    When I run the debug, it seems to be stuck in:

    Please let me know if you are still having this issue after doing the above. I apologize for the inconvenience.

    Best Regards,

    Ben Collier