rtel wrote on Friday, February 28, 2014:
Hmm. I presume as you are updating a previous project to V8.0.0 you are not using any of the new features in V8.0.0, so there must be something in the pre-existing features that is causing your application to behave differently. Other than the changes in the type names there are not too many differences in the pre V8 features so that will help narrow this down.
So one step at a time - in your original post you noted you had changed your application to use the new type names, then turned off the backward compatibility. Did you try compiling and running your application before you did this - so with your application completely unmodified and only FreeRTOS source files changed (so the old type names in your application were #defined to the new type names by the macros at the bottom of FreeRTOSConfig.h which are removed when configENABLE_BACKWARD_COMPATIBILITY is set to 0)?
If that does make a difference then we can concentrate on that line of enquiry, if that doesn’t make a difference (i.e. the issue still exists) then the next thing to look at is the code that should be kicking the watchdog to determine why it is not being kicked…Is your application kicking the watchdog from several locations, or do you have one task/function/whatever that is monitoring the whole system before the watchdog is kicked. If you have a central watchdog function then we need to determine why it is deciding not to kick the watchdog - is the task/function deciding not to kick the watchdog because a test is failing or it the task/function failing to kick the watchdog in time simply because it is never being called?