You are not logged in.
When running the reference design with a modified OFDM core we have been having some problems with EMAC. Specifically, with bi-directional traffic, after a while, one node stops transmitting even though packets are still being injected over Ethernet (Ethernet LEDs are lit). At this point the terminal connected to that node shows a message indicating an EMAC error. I'm not still sure as to why this error happens. The aggregate traffic in two directions is only around 1Mbps. Have you ever experienced a similar problem?
Also, after the error, the only way to get it to work is to reset the terminal. I guess this is due to the way EMAC error handler is set in warpmac.c (only displaying the error code rather than reseting the EMAC), right?
Offline
Which reference design are you using? The EMAC setup changed a lot between v09 and v10. And do you know where in warpphy.c the error was caught (but not handled very well)?
Offline
Design is based v08. The function reporting the error is emacErr_int_handler defined in warpmac.c which simply displays an error code but does not reset the EMAC. We should be able to extend this handler to reset the EMAC in such cases so that we don't need a HW reset, right?
Offline
Yeah, resetting the EMAC in the handler is a good idea.
Offline