Starterware/AM4377: EtherCAT issue with ESC EEPROM

Yong-kyoung Kim

Intellectual 470 points

Part Number: AM4377

Tool/software: Starterware

Hi, I'm trying to run EtherCAT application on customized AM4377 board.

I wanted to use QSPI flash ROM as EEPROM of ESC, so I defined EEPROM_SPI.

Running application, an abort occurs, then I found an error in 'board_support.c' file.

the line number 570 in 'board_support.c', you're using "mcspiLock", but I think it has to be "qspiLock".

When I think wrong, please give me some how-to/instructions to fix it.

Thank you.

over 8 years ago

0 Biser Gatchev-XID over 8 years ago

TI__Guru**** 393215 points

The EtherCAT experts have been notified. They will respond here.

0 Paula Carrillo over 8 years ago

TI__Mastermind 39080 points

Hi Yong-Kyoung, how did you upload your ESI to QSPI? using TwinCAT?. Also, just for reference, which master are you using for testing ? and which Industrial SDK version?. Please give us more details of your test setup.

thank you,

Paula

0 Yong-kyoung Kim over 8 years ago in reply to Paula Carrillo

Intellectual 470 points

No, I didn't download ESI file by EtherCAT.
I just defined EEPROM_SPI, SYS/BIOS crashes after few minues.
Well, I'm testing SDK version 2.1.3.2, but I checked 2.1.2.2, and found 2.1.2.2 has same error, too.
Thank you.

0 Paula Carrillo over 8 years ago in reply to Yong-kyoung Kim

TI__Mastermind 39080 points

Hi Yong-Kyoung, a question, did you build full-fledged EtherCAT slave? below link with steps for your reference:

The reason for my question is that from Industrial SDK user guide EtherCAT section we have:

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 Paula Carrillo over 8 years ago in reply to Paula Carrillo

TI__Mastermind 39080 points

Hi Yong-Kyoung, from the EtherCAT developers I got that "qspiLock" and "mcspiLock" are just semaphore defines. In the code even though we are defining "qspiLock" we are not using it anywhere. Everywhere only "mcspiLock" is used, so this shouldn’t cause a crash.

So, a couple of questions:
- Could you please elaborate which are the "flash" differences between your customized board and our AM437x IDK? Maybe different APIs?

- Also, are you using "qspilock" in your code?.

Thank you,

Paula

0 Yong-kyoung Kim over 8 years ago in reply to Paula Carrillo

Intellectual 470 points

Well, I'm not using "qspiLock" in my code.
When I defined "EEPROM_SPI", the date abort occurs in the sample code(full EtherCAT slave) at the time checking "mcspiLock", but I don't use mcspi on my board(QSPI flash is same as IDK_AM437X).

I wanted to say that the sample code should use "qspiLock" in the code.

Thank you.

0 Paula Carrillo over 8 years ago in reply to Yong-kyoung Kim

TI__Mastermind 39080 points

Thanks for your observation, I will send a note to our industrial protocol developers team. Please let us know if the issue gets resolved.

Paula

Processors

Processors forum

Starterware/AM4377: EtherCAT issue with ESC EEPROM