infineon4engineers Facebook

infineon@google+ Google+

infineon@linkedin linkedin

infineon4engi@twitter twitter

infineon@youtube youtube

+ Reply to Thread
Results 1 to 2 of 2

Thread: XMC ECAT0 Alias

  1. #1
    New Member New Member motionics is on a distinguished road
    Join Date
    Jun 2018
    Posts
    1
    Points
    30

    XMC ECAT0 Alias

    I want to check or change the Station Alias.
    However, it seems that the correct information can not be read or changed through the defined ECAT0.
    Are there other conditions or procedures for use?

    ECAT0 is defined in "XMC4300.h" as follows.
    #define ECAT0 ((ECAT_Type *) ECAT0_BASE)

    I read the information below but it is different from what I actually run on Ethercat.
    ECAT_Type* pECAT_Reg = ECAT0;
    nReadStation = pECAT_Reg->STATION_ADR;
    nReadAlias = pECAT_Reg->STATION_ALIAS;

    Of course, there is no change even if you input the following values ​​at various timings.
    pECAT_Reg->STATION_ALIAS = (uint16_t)nSetAlias;

  2. #2
    Beginner Beginner
    Infineon Employee
    Infineon Employee
    MichaelIFX is on a distinguished road
    Join Date
    Mar 2016
    Posts
    30
    Points
    198.125
    Hi motionics,
    inside the function HW_Init which is implemented inside generated code of ECAT_APP (xmc_eschw.c) two pointers to callback-functions are defined:
    pAPPL_EEPROM_Reload = HW_EepromReload;
    pAPPL_EEPROM_Write = HW_EepromWrite;

    Since SSC 5.12 these callback pointers are set to zero inside SSC initialization when MainInit is called.
    Therefore since SSC 5.12 it is obligatory to set these callback pointers after (and not before) MainInit of SSC is called.

    We will fix that in short term and release an update of the APP.

    If this does not fit your schedule and you need assistance in short term before this release, please feel free to get in contact with me via PN.

    Kind Regards

    MichaelIFX
    The views expressed here are my personal opinions, have not been reviewed or authorized by Infineon and do not necessarily represent the views of Infineon.

+ Reply to Thread

Tags for this Thread

Disclaimer

All content and materials on this site are provided “as is“. Infineon makes no warranties or representations with regard to this content and these materials of any kind, whether express or implied, including without limitation, warranties or representations of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, whether express or implied, is granted by Infineon. Use of the information on this site may require a license from a third party, or a license from Infineon.


Infineon accepts no liability for the content and materials on this site being accurate, complete or up- to-date or for the contents of external links. Infineon distances itself expressly from the contents of the linked pages, over the structure of which Infineon has no control.


Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Usage Terms of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Usage Terms of this site. Infineon reserves the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.