FreeRTOS-7.00 -> FreeRTOS-7.30

Hello, We have some applications running based on FreeRTOS 7.0.0 without problems.
Now I would like to update to FreeRTOS 7.3.0 and I found a problem with vtaskdelay not working correctly. I made two demo projects to show you the issue. You can run them on a EVK1100.
There is only a test task which simply increments a variable every 100ms but that’s enough to show you the different behaviour of the two
FreeRTOS versions. If you set a breakpoint to vtaskdelay in function vtest and check how long it takes to come back from the vtaskdelay function you will see
That with FreeRTOS 7.0.0 it comes back after 100ms as expected but with version 7.3.0 it takes about 5 seconds to come back.
If you set a higher delay such as 500ms it never comes back. So can you please investigate on that and help me to solve this issue.
Kind regards i.A. Uwe Keppler

FreeRTOS-7.00 -> FreeRTOS-7.30

Where did you get your FreeRTOS source code from?  The AVR32 code in the FreeRTOS distribution targets the original AVR32 silicon (ES) in which there was apparently some differences in the timer hardware to the later production silicon.  Atmel distribute a version for the newer silicon as part of their Atmel Software Framework – you can download that from http://asf.atmel.com. Hope that helps. Regards.

FreeRTOS-7.00 -> FreeRTOS-7.30

Hello, I could not find a newer version  than 7.0.0 on the Atmel site.
I would appreciate if I could  send you my demo projects for investigation and you help me to solve this issue? Kind Reagrds.

FreeRTOS-7.00 -> FreeRTOS-7.30

If the Atmel site is shipping V7.0.0 then I assume you got the V7.3.0 code from the FreeRTOS distribution – in which case this is a well known issue as per my previous email the port is for an older revision of the chip.  You will probably be able to use the core V7.3.0 code and drop in the port layer (the files from FreeRTOS/Source/portable) from the V7.0.0 code. Regards.

FreeRTOS-7.00 -> FreeRTOS-7.30

Hello Richard, That works, thanks so far for this information.
By the way it would be much more convenient for all AVR32 users if you would update your port to the newer silicon. Kind regards