AM2434: [AM243x EtherCAT SubDevice]: CoE Complete Access data alignment issue

Part Number: AM2434

Dear TI experts,

we are using the EtherCAT Subdevice software stack from the AM243x Industrial Communications 2026 SDK for the development of a EtherCAT subdevice. I am currently trying to solve all problems found by the EtherCAT conformance test and now I am facing an issue with the "Complete Access" feature for CoE record entries.

Following examplary situation: I have a record, which consists of four entries with the following data types:

Subindex 1: DEFTYPE_BOOLEAN 
Subindex 2: DEFTYPE_UNSIGNED8
Subindex 3: DEFTYPE_BOOLEAN 
Subindex 4: DEFTYPE_UNSIGNED8

For BOOLEAN, the bitlength of the record subindex is defined as 1 bit. Reading the total length of the record using EC_API_SLV_CoE_getObjectLength(..), i get a total size of 5 byte (incl. subindex 0, which uses 2 bytes). So it is 3 byte for my data. It looks like the data would be packed bitwise? Subindex 1 starts at bit 16, Subdindex 2 starts at bit 17, ... ?

I run into trouble with the EtherCAT conformance test, if I define an BitOffs of 17 for Subindex 2 in the ESI file. It is obviously not allowed, that the UNSIGNED8 crosses the byte boarder.
So I defined an additional alignment offset, such that Subindex 2 starts at bit 24. In total, this results in a length of 48 Bit with additional alignment for the BOOLEANs. This is obviously 8 bit more, than the record uses on the subdevice. Due to this, I than run into trouble using Complete Access: Our subdevice only returns 40 bit, but the conformance test tool expects 48 bit. 

I have currently no idea how to solve this. What is the correct way of handling the data alignment in this case?

 

One further question: How can the Complete Access feature be disabled on the subdevice? I found a 
#define COE_SDO_COMPLETE_ACCESS_SUPPORTED 0x20,
but I am not sure what to do with it, as I could not find any reference, where this macro is used.

 

Thank you a lot in advance for your help!

Best regards
Christian

  • Hello Christian,

    I will try to reproduce the issue you described and provide you the feedback.

    You can disable the complete access with the macro defined in project,h file.

    #define COE_SDO_COMPLETE_ACCESS_SUPPORTED   0x00

    This define shall be used to configure the 'CoE Details' Bit 5: Enable SDO completeAccess under the SII General category.

    Make sure that the EEPROM is erased and reconfigured with latest configurations. To reinitialize the EEPROM, please change the macro 'EEPROM_MAGIC_KEY' value in the project.h file.

    Please disable the complete access flag in the SubDevice ESI file as well. 

    Kind Regards,