Re: [lwip-users] fragmentation failure with stm32 if length > 1704

[Harrold Spier]

It might be a platform issue. I had a fragmentation problem using the standard CubeMx stm32h7 ethernet driver some time ago, but the error message was different. It was easy reproducible by sending large sized pings. See for more info:

I may have found an error in the STM32H7 Ethernet Driver when receiving multiple frames

https://community.st.com/s/question/0D50X00009q5WkDSAU/i-may-have-found-an-error-in-the-stm32h7-ethernet-driver-when-receiving-multiple-frames 

(Click on the link More Answers at the bottom to complete conversation)

Regards,

Harrold

 

On Wed, Dec 11, 2019 at 10:25 PM address@hidden <address@hidden> wrote:

Am 11.12.2019 um 18:55 schrieb Ranran:
> Hello,
>
> I use a simple echo udp example for STM32 Hal , with stm32h743 EVAL.
> I encounter exception (it shows as unaligned exception, but the
> address is not anything we allocated.
>
> This failure happen if I increase the packet size from 1704 to 1744 !
>
> tcip_thread->tcip_timeouts_mbox_fetch->sys_check_timeouts->lwip_cyclic_timer->ip_reass_timr->ip_reass_free_complete_datagram
> exception error of type unaligned access.
>
> I tried to increase various  size in lwipopts.h but nothing helps.
>
> Is it stm32 issue ?
> Any idea ?

Doesn't ring a bell. Last time I tested, fragmentation/reassembly worked
just fine, so I expect this is a platform/config specific issue.

Regards,
Simon

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users