EMAC DMA stuck after first transmission

Hi,

    Are you getting any error message in the console window after DMA stuck? Or where the code stucks in the disassembly window?
    Please ensure that you are following the steps mentioned in the “EMAC Programming Model” available in the HRM.
    Can you please confirm whether the clock is configured as per the spec mentioned in the datasheet.

Regards,
Divya.P

Hi Divya,

I'm not getting any error messages in the console window. 

In terms of clock rate, it's using 25MHz clock for both PHY ICs as per datasheet.

Yep, the steps mentioned in the "EMAC Programming Model" is implemented in the GEMAC driver ADI provides. Following the stack trace of the GEMAC driver, we can see that it's doing the steps described in the manual.

----

Upon further investigation. We found that the first transmit descriptor doesn't have an ownership problem as the GEMAC driver correctly sets the OWN bit.
 

Instead, after the EMAC_DMA0_TXDSC_CUR points to the first descriptor and we write to 

we get .

it looks like we get some errors from the receiver side, specifically a buffer overflow and receive buffer unavailable. These error bits then gets handled by the void EMACInterruptHandler(uint32_t IID, void *pCBParm), which does the following:

Since TU and RU bit is set, it will call the transfer_queued_bufs function. which just tries to send/receive again by setting the tx/rx poll registers.

I'm not sure where to go from here. Since there are separate FIFO buffers for TX and RX, one can reasonably assume that a buffer overflow in the RX buffer shouldn't affect the TX buffer? or am i incorrect in that assumption?

Please advise what I can do next to further debug this. 

Cheers