FreeRTOS+TCP demo Win32 build fails

Kernel
1

dpederick wrote on Monday, November 03, 2014:

I’ve just installed MSVC Express 2010 and loaded the solution as specified here:
http://www.freertos.org/FreeRTOS-Plus/FreeRTOS_Plus_TCP/examples_FreeRTOS_simulator.html

The source code compiles but the build fails with this message:
1> Generating Code…
1>LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

I’m sorry if this is basic, but I was expecting the demo to work out of the box…
I’m on windows 7 (x64), btw.

Thanks

2

heinbali01 wrote on Monday, November 03, 2014:

Hi,

This looks like a good solution:

http://stackoverflow.com/questions/10888391/error-link-fatal-error-lnk1123-failure-during-conversion-to-coff-file-inval

but I haven’t come across this problem yet.

Regards

3

rtel wrote on Monday, November 03, 2014:

Just to satisfy myself, on a Win7 64-bit host and Visual Studio Express 2010 with service packs I tried downloading a clean FreeRTOS+TCP zip file and this is the build output I got:

1>------ Build started: Project: RTOSDemo, Configuration: Debug Win32 ------
1> DemoIPTrace.c
1> Run-time-stats-utils.c
1> main.c
1> demo_logging.c
1> UDPCommandServer.c
1> SimpleTCPEchoServer.c
1> SimpleUDPClientAndServer.c
1> UDPSelectServer.c
1> TwoUDPEchoClients.c
1> TCPEchoClient_SingleTasks.c
1> TCPEchoClient_SeparateTasks.c
1> CLI-commands.c
1> NetworkInterface.c
1> BufferAllocation_2.c
1> FreeRTOS_UDP_IP.c
1> FreeRTOS_TCP_WIN.c
1> FreeRTOS_TCP_IP.c
1> FreeRTOS_Stream_Buffer.c
1> FreeRTOS_Sockets.c
1> FreeRTOS_IP.c
1> Generating Code…
1> Compiling…
1> FreeRTOS_DNS.c
1> FreeRTOS_DHCP.c
1> FreeRTOS_ARP.c
1> FreeRTOS_CLI.c
1> timers.c
1> tasks.c
1> queue.c
1> port.c
1> heap_4.c
1> list.c
1> event_groups.c
1> Generating Code…
1> WIN32.vcxproj -> C:\temp\FreeRTOS+TCP_141019\FreeRTOS+TCP_141019\FreeRTOS-Plus\Demo\FreeRTOS_Plus_TCP_and_CLI_Windows_Simulator.\Debug\RTOSDemo.exe
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

Regards.

4

dpederick wrote on Monday, November 03, 2014:

Thanks for the posts!
Applying the service pack fixed it.