Additionally i would start generating the project again using the latest
version of CubeMX using the original ioc file. It contains LwIP 2.0.0 with
adopted EthernetIf.c already. A migration starting there to 2.0.2 should be
straight forward.
Regardless, check if your co-worker has made any changes to the original
sources.
Am 13. März 2017 22:59:39 MEZ schrieb "Wormsley, Jeffrey (Jeff)"
<[email protected]>:
>I'm trying to upgrade a project from 1.4.x to 2.0.2. The project is on
>STM32F417 generated from CubeMX using IAR, FreeRTOS and wolfSSL. It's
>the demo WolfMQTT app if anyone has that to compare to.
>
>I've managed to build all of the search paths and file structure for
>2.0.2 ok, and the project compiles, but then fails to link. At issue
>is changes revolving around etharp.c, ethernet.c and ethernetif.c. The
>original project apparently uses etharp.c and a function called
>etharp_send_ip() in multiple places for sending packets, but the 2.0.2
>code expects this to be done from ethernet_output(), which my project
>doesn't even have. Other missing bits include ethzero, ethbroadcast
>and ethernet_input(). I think ethzero and ethbroadcast could be copied
>from the sample ethernet.c that came with 2.0.2. Or is that code
>expected to be the only ethernet.c in the project, and the ethernet.c
>that CubeMX generated should be renamed or something?
>
>Not being the person who originally built this project, I'm somewhat at
>a loss as to where to proceed. Anyone have any pointers for moving
>from 1.4.x to 2.0.2 in a CubeMX STM32F4xx environment?
>
>Thanks,
> Jeff.
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
