ECAT_Slave_in_ПЧ2П_c402  0.8
Реализация EtherCAT Slave для CM TMS320F28388D
Файл ecatfoe.c

Implementation This file contains the FoE mailbox interface. Подробнее...

#include "ecat_def.h"
#include "ecatslv.h"
#include "ecatfoe.h"
#include "foeappl.h"
Граф включаемых заголовочных файлов для ecatfoe.c:

См. исходные тексты.

Макросы

#define _ECATFOE_   1
 
#define _ECATFOE_   0
 

Функции

void FOE_Init (void)
 This function initialize the FoE Interface. Подробнее...
 
UINT8 FOE_ServiceInd (TFOEMBX MBXMEM *pFoeInd)
 This function is called when a FoE (File Access over EtherCAT) service is received from the master. Подробнее...
 
void FOE_ContinueInd (TMBX MBXMEM *pMbx)
 This function is called when the next mailbox fragment can be sent. Подробнее...
 

Подробное описание

Implementation This file contains the FoE mailbox interface.

Автор
Ether.nosp@m.catS.nosp@m.SC@be.nosp@m.ckho.nosp@m.ff.co.nosp@m.m
Версия
5.13


Changes to version V5.12:
V5.13 EOE1:
V5.13 FOE1: handle failure on continue indication

Changes to version V5.11:
V5.12 FOE2: handle 16bit only access
V5.12 MBX4: in case of a disable mailbox queue and two consecutive foe uploads the mailbox receive handler is blocked

Changes to version V5.10:
V5.11 FOE1: handle busy on a read request, change OPMode to OPCode (same terms as in the spec)

Changes to version V5.0:
V5.10 MBX1: Remove multiple swapping of length filed in mailbox header

Changes to version V4.40:
V5.0 FOE1: Free memory if FoE_ServciceInd() is left.
V5.0 FOE2: Update error code (Bit 15 shall not be set).
V5.0 FOE3: Update byte swapping for big endian and big endian 16 configurations.
V5.0 FOE4: Update Error text handling for 16Bit operations.

Changes to version V4.11:
V4.40 FOE1: correct FoE busy values
V4.40 MBX2: HW_CopyToSendMailbox merge to a generic function (new: MBX_CopyToSendMailbox)

Changes to version V4.10:
V4.11 FOE 1 fixed a problem with a huge FOE_MADATA define
V4.11 FOE 2 u16PacketNo is now a 32bit variable (u32PacketNo) to conform with the spec

Changes to version V4.00:
V4.10 FOE 1-3 when downloading the firmware the FoE state machine was not set to FOE_READY
when the last data segment was downloaded so that the next FoE service failed

Changes to version V3.20:
V4.00 FOE 1 - if a FoE Error service is received it should not be acknowledged
V4.00 FOE 2 - if a FoE service response could not be sent because the mailbox is full
it has to be re-transmit otherwise the response get lost

См. определение в файле ecatfoe.c