TI E2E Community
Sitara Processors Forum
AM3359 IDK with EtherCAT-example
So, after changing the browser I'm lucky to ask another question... Sorry, but I can't help!
The situation: As the EtherCAT-example, delivered together with the SDK is already running fine on ICE, I'd like to test it on the IDK. An installtion-guide is provided by the AM3359IDK-flyer delivered with the board.
Thus, plugged the CAT5-cable to "PRU0 ETH/J8" on the board and getting the IDK started with the sample-application successfully, I'd expect that I can see the device on the box-scan by TwinCAT, like it has been as it was connected to the ICE - but nothing can be detected. The PHY-leds are also inactive on the IDK. If I change the plug from J8 to J9 I can see a sort of connection but still no EtherCAT-interface, so I still wonder, what's wrong.
Does anybody know, what' wrong (maybe, there's an OSI-layer#8-error)?
could you solve the issue? What code are you trying an how?
There are differences between ICE and IDK for boot. Make sure you use the binaries from the SDK 184.108.40.206 prebuild binary package. If you boot from SD this card needs to be bootable. First file needs to MLO and then APP.
Yes, I've also tried the pre-built-variant for IDK from the SW-package already present on the SD-card, but I haven't been able to solve the problem yet. The very strange behaviour of the IDK is the fact, that only on J9 a physical port (a sort of connection) could be detected and one of the activity-leds of the PHY-conn. is on. But if the cable is connected to J8 as being described not any connection could be detected. Well, however, both connections cannot be recognized by TwinCAT as being a EtherCAT-box.
Note: The application code itself seems to be started, as I can see the welcome-message on my terminal-program, which is connected to the IDK via UART-plug.
The ID-msg. of the application is: ECAT Limited Demo - 1.0.14
yes, EtherCAT has a clear definition of IN and OUT ports. J8 is IN and J9 OUT in our case. Currently we do not support redundancy mode which allows to connect a slave via OUT in the same way as IN.
Now if the application is working and you can see link and packet activity on J9 but not on J8 then it might be that the port J8 on your board is broken. Do you have an emulator now that would allow more debug using CCS?
No, we didn't obtain an emulator yet, Sorry! Thus, I'm not able to debug the application on the IDK. I will try to validate, that J8 is broken. BTW. is there any jumper-field which might or might not be configurated wrong? Or is there any other way to get more hard evidence?
I'm having the same/similar symptoms with my IDK. Application seems to be running, but cannot connect to TwinCAT.
I connect TwinCAT to J8, scan devices and get three "Device 1 (RT-Ethernet): Link lost" messages in TwinCAT. D1 on the IDK does not turn on when connecting to J8. If I connect to J9, D2 turns on as well as the green LED on J9.
I can switch back to the ICE and connect, control, etc. from TwinCAT without issue.
I have the XDS510 USB emulator.
It is pretty strange to see the issue reported twice. However I am not able to reproduce this yet.
So I need to defer to the factory for some more tests. I assume you are running the supplied pre-build binaries to avoid any tools issues.
I am using the unmodified SD card that came with the IDK.
I just tried again with our board. No issue at all using J8. Do you see the output LEDs (D20-D27) running? If not your SD didn't boot.
I asked around internally about XDS510 USB support for AM335x. I am using XDS560 here. I remember that initial releases of CCS 5.1 did not support AM335x and XDS510 combination.
Yes, the LEDs are rotating in a circular pattern.
I just tried the latest version of CCS (build 5.1.1.00031), but no difference except I am now able to test the target configuration for the XDS510 USB from within CCS instead of using SDCONFIG.
I have the same question as you. Do you konw how to slove this problem now? Would you mind helping me slove it?
I have the same problem as Thomas, I don't know how to slove this problem, Would you mind helping me slove it?
Can anyone try a crossed cable to connect between IDK and PC ?
We have observed similar issue here on IDK we solved it by using a crossed cable.
Please let us know the results. If using a crossed cable solves your problem, then PHY's auto-mdix is disabled. Enabling auto-mdix should solve the problem.
Thanks and Regards,
It's OK now, I have used the crossed cable to connect between IDK and PC. Thank you for helping me.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.