AM57x EtherCAT Slave demo EEPROM

carolyn zhang

Other Parts Discussed in Thread: AM5728, TLK110, TLK105

Hi,

I am debugging EtherCAT slave mode using PRU-ICSS-EtherCAT_Slave_01.00.00.00. The main chip is AM5728.

The EEPROM on my board is controlled by I2C. Could somebody tell me that is SPI EEPROM necessary for EtherCAT slave demo? Or is EEPROM necessary for EtherCAT slave demo if I boot the board using MMCSD mode?

Thanks.

over 9 years ago

0 Biser Gatchev-XID over 9 years ago

TI__Guru**** 393215 points

I will ask the industrial team to comment.

0 Paula Carrillo over 9 years ago

TI__Mastermind 40580 points

Hi Carolyn, I don't think it is, as far as I know we use a header file instead (protocols\ethercat_slave\ecat_appl\EcatStack\tiesc_eeprom.h) but I will ask the devolopers for confirmation.

thank you,
Paula

0 Paula Carrillo over 9 years ago in reply to Paula Carrillo

TI__Mastermind 40580 points

Carolyn, I confirmed with the developers that We do not use board EEPROM but SPI flash (QSPI or SPI flash depending on the platform). However, as mentioned before, header (tiesc_eeprom.h) can be used instead for debugging/development purpose. In other words, If EEPROM (in flash) is not present or header CRC is incorrect then the application will use header instead. Please see below E2E and wiki for more details:
e2e.ti.com/.../314782
processors.wiki.ti.com/.../PRU_ICSS_EtherCAT_firmware_API_guide

thank you,
Paula

0 carolyn zhang over 9 years ago in reply to Paula Carrillo

Expert 1020 points

Hi, Paula,
I would like to debug firmware function 'bsp_init', could you tell me how to compile the firmware? Thanks.

0 carolyn zhang over 9 years ago in reply to Paula Carrillo

Expert 1020 points

Hi, Paula,

There is no SPI flash on my board, I use MMCSD to boot. So I don't want to use EEPEOM or SPI flash, I just want to usd header(tiesc_eeprom.h) directly, may I? I had comment "EEPROM_SPI" in 'tiescbsp.h', it seems useless.

Thanks.

0 Paula Carrillo over 9 years ago in reply to carolyn zhang

TI__Mastermind 40580 points

Hi Carolyn, yes I think if it is commented you will be working with the header file. So you should be good... one quick test is having a backup copy and change tiesc_eeprom.h if your changes are reflected. Maybe it stops working =) but you will be sure you are using this header file

Thank you,
Paula

0 Paula Carrillo over 9 years ago in reply to carolyn zhang

TI__Mastermind 40580 points

Hi Carolyn, unfortunately we don't share source code for our EtherCAT PRU firmware .. for several reasons, one is due to protocols certifications.
Thanks,
Paula

0 carolyn zhang over 9 years ago in reply to Paula Carrillo

Expert 1020 points

Hi, Paula,

I know IDK5728 use TLK105 as phy, and SPI flash for boot. Could you please tell me whether I need to change EtherCAT PRU firmware or not if I use TLK110 as phy, and MMCSD for boot.

And could you please tell me what is phy interrupt for?

Thanks.

0 David Zaucha over 9 years ago in reply to carolyn zhang

TI__Expert 7570 points

Hi Carolyn

On the Sitara boards there is a I2C EEPROM which contains a description of the components on the EVM. During initialization Board_getIDInfo is used (I believe in two places Common_main and Task1) to populate a structure with the values that are read from the I2C eeprom on the board. This information is used (in part) to initialize and configure the SOC and Board. For a custom board - one solution is to rebuild the application with a API that populate the structure with the desired values.
Do you have a IDK5728 to use as a reference for your analysis?

Board_init is contained in C:\ti\pdk_am57xx_1_0_2\packages\ti\board\src\evmAM572x\evmAM572x.c. When debugging it is often easiest to simply add the file into the project and recompile.
The application configures the phy. The initialization and runtime APIs for the TLK110 and TLK105C phys will be somewhat different. You can get a rough comparison by looking at the implementation of the AM335x EtherCAT slave in the ISDKversus the AM57x ethercat implementation in the as the PRU_ICSS_EtherCAT slave in the Processor SDK. There will be a little different because of the present difference in the to industrial SDK packages.

We will have to inquire as to which phy interrupts are enabled.

0 carolyn zhang over 9 years ago in reply to David Zaucha

Expert 1020 points

Hi, David,

I have commented 'EEPROM_SPI' in tiescbsp.h. However, when I run 'Ecat_Open' in tsk1, it called firmware API 'bsp_init'. Then the function 'bsp_init' called firmware API 'bsp_eeprom_emulation_init', in which 'EEPROM_SPI' would be judged.

void bsp_eeprom_emulation_init(void)
{
Uint32 itr = 0;

    #ifdef EEPROM_SPI
    Uint16 u16Crc = 0x00FF, i, j;
    int invalid_crc_flag = 0;

......

}

Since I could not compile firmware, 'EEPROM_SPI' is commented or not will not change anything. The 'Ecat_Open' still consider 'EEPROM_SPI' is defined. And I got error 'CortexA15_0: Unhandled ADP_Stopped exception 0x20023' at last.

Could you give me some advices about this? Thanks.

0 Paula Carrillo over 9 years ago in reply to carolyn zhang

TI__Mastermind 40580 points

Hi Carolyn, did you commented defined EEPROM_SPI inside tiescbsp.h?
#if (!CiA402_DEVICE )
#define EEPROM_SPI /*Comment this to enable volatile EEPROM support for debug*/ /* TODO Enable later */
#endif

thank you,
Paula

0 carolyn zhang over 9 years ago in reply to Paula Carrillo

Expert 1020 points

Hi, Paula,

Yes, I did. And I rebuilt the ethercat slave demo project.

0 Paula Carrillo over 9 years ago in reply to carolyn zhang

TI__Mastermind 40580 points

Carolyn, another quick question did you create "full" application (projectCreate.bat AM571x ethercat_slave_full) or limited demo (projectCreate.bat AM572x ethercat_slave_demo)

If it is the second case, please check below note from processors.wiki.ti.com/.../PRU_ICSS_EtherCAT
NOTE 2: Both EtherCAT applications support non-volatile storage of ESI EEPROM. The application writes the data into non-volatile QSPI memory only in INIT and PREOP states. This can be disabled or enabled on full featured application by defining/undefining EEPROM_SPI macro in tiescbsp.h. This feature cannot be modified in limited demo

Thank you,
Paula

0 carolyn zhang over 9 years ago in reply to Paula Carrillo

Expert 1020 points

Hi, Paula,

I am debugging limited demo. I think you are right, that might be the problem. Thanks.

0 Paula Carrillo over 9 years ago in reply to carolyn zhang

TI__Mastermind 40580 points

Hi Carolyn, please let us know how things go with "full demo" version. I think it should be OK, but if not, please try bringing tiescbsp.c file into the project.

thank you,

Paula

0 carolyn zhang over 9 years ago in reply to Paula Carrillo

Expert 1020 points

Hi, Paula,

I will. Thanks.

Processors

Processors forum

AM57x EtherCAT Slave demo EEPROM