Hi Steve - While not exactly your challenge, I recently had to update an
LwIP 2.x to the latest,
on an ST project (easier change than from 1.x).
I've attached my notes below; perhaps they will help,
Best Regards, Dave
ST distributes a lwip 2.x version which is not up-to-date and cleverly
has all version notes and change logs stripped.
To use the latest distributed lwip safe release:
1.
Download latest lwip
2.
Copy into project using different directory name lwip-2.1.2 so
CubeMX does not over-write it.
3.
Copy the lwip\system tree into lwip-2.1.2
4.
In project, mark Resouce Configurations → Exclude From Build (for
all configurations):
1.
CubeMX-generated lwip tree
2.
lwip-2.1.2\src\apps\http\fsdata.c (this C file is included in fs.c)
3.
lwip-2.1.2\src\apps\http\makefsdata tree (utility needs to be
built in Visual Studio)
4.
lwip-2.1.2\src\apps any unused apps (SMTP, etc.)
5.
lwip-2.1.2\src\test tree
5.
Update, for all configurations, change C compiler include paths from
lwip to lwip-2.1.2
On 2/8/2019 12:39 AM, goldsimon wrote:
Am 8. Februar 2019 00:27:58 MEZ schrieb Stephen Cowell
<s.cow...@plasmability.com>:
>I'm attempting to update the SAM4E example project
>THIRDPARTY_LWIP_BASIC_HTTP_EXAMPLE1 from 1.4.1 to 2.1.2. The dev
>system is Atmel Studio 7 using ARM/GNU Common toolchain. I have
NO_SYS =1....
>this is the bare-metal implementation.
>
>I've partway through the directory problems... it seems that the
>directory structure has changed, but the files I have have not been
>updated. Is this normal? Does everyone have to go through and edit
>the header file includes to reflect the new structure? I can't see why
>this is not fixed in the release.
>
>Now I'm getting #error "<dirent.h> not supported". Does this mean that
>I'll have to go to a different toolchain? Do I have to have tinydir for
>the stack to work? My eventual target (we've been selling our product
>with lwip 1.4.1 for years) has FatFS already, I'd rather not do the
>filesystem over as well. Also getting "#error makefsdata not supported
>
>on this platform"... how do I carve up lwIP? I've already deleted the
>'api' folder, referring to this link:
>
>https://www.nongnu.org/lwip/2_0_x/group__lwip__opts__nosys.html
>
>This link was a great help, but I'm not sure if these guys are running
>bare-metal or not...
>
>https://community.atmel.com/forum/upgrading-lwip-141-200-pbuf-issue
>
>Perhaps someone could throw me a bone? Do I need an RTOS to move
>forward? Do I need a different toolchain?
>__
>Steve
>--
>
>Stephen Cowell
>Project Manager/Engineer
>Plasmability LLC
>Office (512) 267-7087
>Cell (512) 632-8593
>www.plasmability.com
>
>_______________________________________________
>lwip-users mailing list
>lwip-users@nongnu.org
>https://lists.nongnu.org/mailman/listinfo/lwip-users
--
Dave Nadler, USA East Coast voice (978) 263-0097, d...@nadler.com, Skype
Dave.Nadler1
_______________________________________________
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
