does anyone have problems with rowley crossworks 1.6 and vTaskDelay? same code compiles fine with crossworks 1.5

failed to mention:

vTaskDelay compiles in both crossworks versions but in 1.6 calling the function seem to hang the OS not the processor. while with 1.5, same code is running nicely.

Just waiting for my V1.6 licence, then I will give it a try.

Regards.

I have:

+ Installed V1.6.
+ Installed the SAM7 package.
+ Build and executed the lwIP demo.

What I am finding:

+ With optimisation on level 2 the demo executes fine until I make an HTTP request, at which point is hangs.
+ With optimisation off and debug info included it executes with *no problems*.

I need to take a look through the changes between V1.5 and V1.6 to see what is up when the optimisation is on. There may be an option that needs turning off - GCC can be very aggressive in its optimisation.

Regards.

1.5 version

gcc (GCC) 3.4.4
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


1.6 version

gcc (GCC) 3.4.4 (release) (CodeSourcery ARM 2005q3-2)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


both 3.4.4 but different builds.

have you had a chance to see what's going on with the lwip crash?

It seems that their might be a code gen problem at the higher optimisation level. Rowley are looking into this and hopefully will report back soon.

I am about to do a new release (V4.0.3) that includes a new port. In this release I have lowered the optimisation to 1. At this level it has been running for more than a day with no problem so far.

Regards.

any news from rowley?

Many apologies - I forgot to update the thread.

There does indeed appear to be a code generation issue at optimisation level 2. I don't fully understand the issue so it is possible that it also occurs at lower optimisation.

FreeRTOS.org V4.0.3 has the lwIP project defaulted to optimisation level 1 and this seems to work well.

Rowley did provide me with a fix within a couple of days which I have tested at optimisation level 3 and this also seems to work well.

To get the fix you need CrossWorks V1.6 build 3. I think this should be available for download from Rowley already, and if not it will be very shortly.

Regards.