LAUNCHXL-F28P65X: Unable to scan for the device by TwinCAT

Hi,

Have you already tried following the steps in sections 4.1, 4.2, and 4.3 with the HAL Test project? 

I have personally used the f28p65x_cpu1_echoback_solution with our f28p65x controlCard, but not the launchpad. I know it has been tested, but I will need to check if there are any settings that you need to change.

Best Regards,

Ben Collier

Hi Ben,

Yes, I have followed the steps in sections 4.1, 4.2, and 4.3 with the HAL Test project. However, the situation is similar and I can't scan the device. Therefore, I can not program the EEPROM based on section 4.4. Here is what I did:

1. Import f28p65x_cpu1_pdi_hal_test_app project and switch to LAUNCHXL_RAM configuration. After compiling, the following errors and warnings appear:

It seems that the cmd file is not included in this configuration. Also, c2000ware_libraries.cmd.genlibs could not be found, which seems to be related to syscfg. Meanwhile, C2000WARE_ROOT could not be resolved, but this path did not seem to work. Therefore, I added the cmd file and removed c2000ware_libraries.cmd.genlibs. 

2. Compiling again, the following warnings were obtained and the program was burned into RAM of the DSP, and after clicking Run, the same phenomenon occurred, i.e., only the D11 red RED was blinking, and TwinCAT was unable to scan the device.

3. To eliminate the warning about "C2000WARE_ROOT", new variable has been added and only one warning remains.

However, after burning to the DSP, the same phenomenon occurs ( the D11 red RED was blinking and TwinCAT was unable to scan the device ).

In summary, we are unable to perform any EhterCAT related tests. In addition, we have used the 28388D control card for EhterCAT related tests before and had no problems with that DSP, so the TwinCAT part should works fine. 

If possible, maybe you can have a test with this LaunchPAD  and the issue should be easy to reproduce. FYI, the LaunchPAD we used is a brand new development board and this is the first time it is being tested.

Any help would be greatly appreciated! Thanks!

Best regards,

Huanli Liu

Hi Huanli,

Thank you for providing these details. I will be discussing this with coworkers tomorrow, please expect a detailed response then.

Best Regards,

Ben Collier

Hi Ben,

Is there any progress on this?

We would like to update our test results a little further. After debugging the f28p65x_cpu1_echoback_solution step-by-step, we found that the D11 red light starts blinking at the ESC reset, i.e. when the following instruction is executed:

After checking the datasheet, we learned that this reset is required during initialization.

Best regards,

Huanli Liu

Hi Huanli,

I am able to replicate your issue, I will need some more time to try to find out what is going on.

Best Regards,

Ben Collier

Hi Ben,

Thanks! 

Once this issue is resolved, please update so that we can continue to test the EtherCAT.

Best regards,

Huanli Liu

Hi Huanli, 

Can you try running the RAM (not LAUNCHXL_RAM) build configuration and report back if you face any issues in that case? You can use this example for testing purposes for the time being. 

There seems to be an issue with the FLASH configuration. We are looking into it and will come up with a resolution soon. 

Thanks. 

Correction: The FLASH (not LAUNCHXL_FLASH) configuration works as expected as well. 

Please try running the same and report back in case of any errors. 

Thanks. 

Hi Sahil,

Yes, in fact when the issue was first raised, the project used was RAM (not LAUNCHXL_RAM)  build configuration. As Benjamin said, he reproduced our issue as well. Also, as you suggested, we tried again with FLASH build configuration and still got the same result: the D11 red LED was blinking and TwinCAT could not scan to the device.

The experimental steps we did were the same as in the problem description, adding the _LAUNCHXL_F28P65X macro definition, along with the code generated by SSC, as shown below:

If possible, could you please have further discussions with Benjamin to help resolve this issue?

Best regards,

Huanli Liu

Huanli, 

My apologies, I was just sent this thread so might have missed a few details. 

I have a planned call with Benjamin, where we will debug the issue and come up with a resolution. (I am able to have both RAM and FLASH versions running perfectly, with the same version of C2000ware and CCS, so my guess it is that the issue lies in the initial configuration)

Huanli Liu said:

Using the sample project f28p65x_cpu1_echoback_solution, copy the code generated by the SSC to this project directory, and thereafter import the project into CCS and add the _LAUNCHXL_F28P65X macro definition as well as the path to the EtherCAT stack, as shown below:

In the SSC tool, the instructions in the guide mentioned to change (only) the Source Folder directory to /examples/f28p65x_cpu1_echoback_solution. I see that the folder structure is different in the images you have attached and that may be causing you to add the extra path for Ethercat stack.  

Thanks. 

Huanli,

We have two different revisions of these Launchpads, and it seems that there is an issue with using EtherCAT on one of the revisions. We are not sure what the root cause of this is, but we are currently debugging this. Since there is an upcoming holiday, it may take a few weeks to determine the root cause, as many of our engineers will be out of office. 

I apologize for this inconvenience.

Best Regards,

Ben Collier

Hi Sahil,

Thanks for your help. Hope we can resolve this issue successfully.

Best regards,

Huanli Liu

Hi Ben,

Thanks. We can keep updating on this issue if there is any progress.

Best regards,

Huanli Liu

Ok Huanli, I will keep this thread updated as we find out more. 

Hi Ben,

I was wondering if you could share the schematic or design files of another version of the Launchpad? Maybe we can analyze and test it simultaneously on our side as well.

Best regards,

Huanli Liu

Hi Huanli,

Schematic and Design Files for the production version of LAUNCHXL-F28P65X (Rev A) are linked in the EVM User Guide: https://www.ti.com/lit/ug/spruj71/spruj71.pdf 

We have performed some testing and have verified that Revision A of the LaunchPad does not have functional etherCAT, and Revision E1 (our initial engineering prototype build) does. You can find the E1 design files at the below link (I will update the user guide link to contain these E1 design files at a later date)

https://tidrive.ext.ti.com/u/oYLRLCoC0RyzgtEl/2f704c7a-3f2b-416c-9bf3-a2d33188cfba?l

Access Code: *MJU96f4

You are free to analyze the two designs and look for any differences between the two builds, though I am fairly certain there should be no changes between the designs. This largely looks to be a manufacturing issue so I am working closely with our manufacturers to debug this issue and will provide an update when we find root cause. This issue will be resolved in Rev B of this device.

Regards,

Peter

Hi Peter,

Thanks for your sharing. We checked both versions and didn't see any difference. Also we further checked our Launchpad and there seems to be no soldering issues visually either. That's pretty odd.

By the way, Merry Christmas to you all !

Best regards,

Huanli Liu

Merry Christmas Huanli! Please expect more updates in January. 

Hi Ben,

Thanks for the update! That's a good news! 

Based on your reply, can we restore EtherCAT functionality with the following options?

1. Waiting for your software update;

2. Purchasing a new DP83826E from the TI website to replace the old version on the launchpad;

If option 2 is possible, do I need to replace anything other than the chip? How should we identify the version of the DP83826E to make sure the updated chip is the latest version?

By searching the datasheet of DP83826E, it is found that only PHYIDR1 and PHYIDR2 registers are related to the version, is it possible to determine the version of the chip from here? If it is the latest version, what should their current values be?

Best regards,

Huanli Liu

Huanli,

Huanli Liu said:

Based on your reply, can we restore EtherCAT functionality with the following options?

1. Waiting for your software update;

2. Purchasing a new DP83826E from the TI website to replace the old version on the launchpad;

This is correct. 

Once you have the PHY, you will be able to read the PHY registers to confirm which revision you have. To make sure that the right revision is shipped to you, I think you will just need to confirm with your distributor that you are getting the latest revision.

TI should now only be shipping the latest revision, so you should be good ordering from TI.com

Best Regards,

Ben Collier

Hi Ben,

Thanks for your help. Considering the time consumption, maybe it's a better idea to try replacing it with the latest chip first.

Best regards,

Huanli

I understand. I will still update this page with the software solution when possible. 

Huanli,

Glad to hear that your issue is resolved. I will provide the software fix as soon as possible.

Best Regards,

Ben Collier

Hi Ben,

Many thanks for your hard work! 

Best regards,

Huanli Liu

Hi Ben,

Many thanks, for sharing the document. Now it works.

great and regards

Reiner