Hi.
I'm trying to use the FM1 DTSEC4 interface in RGMII mode configured as 10Mb half duplex to transfer a big data file (180MB) in U-Boot, but the transfer fails with the error "FM1@DTSEC4: Rx error" and the interface will only recover after a processor reset. An initial analysis on the reason for the error shows that the "Frame Size Error" flag of a faulty RxBD caused the problem.
Shouldn't the U-Boot FMAN driver recover in such situations?
Solved! Go to Solution.
The problem seems to be fixes with the commit http://git.freescale.com/git/cgit.cgi/ppc/sdk/u-boot.git/commit/?id=466f775e02bcde5ea7454cd73ecf1a0f.... As we found this issue in the U-Boot NXP SDK 1.9 we decided to upgrade to U-Boot NXP SDK 2.0 that contains the fix.
Thanks.
Hello Tiago Brusamarello,
It looks that the current u-boot doesn't support JUMBO Frame, we need to set the FIFO SIZE correctly in the FMBM_PFS register. The parameter is [IFSZ]. This is located at XF048_A204. IFSZ seems to be set to a value of x14 which means that the total FIFO size is 21buffers x 256B = 5376 Bytes. The total FIFO size should be greater than or equal to: (frame size rounded up to 256B) + (4*256) Bytes.
Have a great day,
TIC
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
The problem seems to be fixes with the commit http://git.freescale.com/git/cgit.cgi/ppc/sdk/u-boot.git/commit/?id=466f775e02bcde5ea7454cd73ecf1a0f.... As we found this issue in the U-Boot NXP SDK 1.9 we decided to upgrade to U-Boot NXP SDK 2.0 that contains the fix.
Thanks.
Thanks for the clarification yipingwang.
But I don't understand how this can affect U-Boot operation when the ethernet port is configured @ 10 Mbps Half duplex. When configured in other speeds/duplexes the problem doesn't show up.