Other Parts Discussed in Thread: DP83869, SYSCONFIG
Tool/software:
Dear TI team,
we're trying to work with the Profinet device example from the Industrial Communications SDK 09.02.00.15.
On some of our EVM boards the application is stuck in PNIO_device_open while polling for pnpb_get_state, similar to an issue we and others observed a couple of months ago in the linked thread.
At that time we were testing with a particular AM64x EVM, and observed the same issue as that thread's OP. Laxman Chinnannavar provided a pre-compiled binary of a fixed version that we successfully verified on that AM64x board. I'm not 100% sure if we ever tested that AM64x EVM with a binary built from SDK 09.02.00.15, and unfortunately that board is now "electrically" dead, so I can't verify.
Our current issue (stuck in PNIO_device_open) is that we're now seeing exactly the same issue with one AM24x EVM whereas the same binary works on a different AM24x EVM.
The hardware itself should be fine, as it works e.g. with an EtherCAT slave or an Ethernet/IP slave.
Laxman mentioned in the referenced thread that you "found out that there are few causes for the application getting stuck".
- What could cause the application to get stuck in PNIO_device_open?
- Are there any known issues left in 09.02.00.15?
- When we can expect a newer version of the industrial communications SDK?
- How can we debug this issue?
Our ultimate goal is to port the profinet device stack to a third-party SoM & board, and it would really help to understand how to debug issues in binary-only parts of the stack (the application just calls "PN_API_IOD_startup", and then gets stuck "somewhere" in there).
Regards,
Dominic