Just a few comments regarding what I’ve seen thus far getting the port to run on the TI Cortex R4F Family with the latest IAR tools:
*) I had to do a slight fix-up on the LR register to make sure it was calculating its offset from the tasks’ stack frame. It seems to work and was the only way I was able to get around a prefetch abort vector error I was getting. I wasn’t quite sure why that offset was 8 bytes from the bottom (or maybe the top, depending on how you look at it) of the tasks’ stack in the instruction that does the #+60. I ‘emulated’ that - meaning I did a fix up to make sure the behavior matched the existing port under CCS (6.x). I thought just doing the calculation without the 8 bytes difference was OK too - meaning at the first word in the stack being the demarcation of the fix-up - which seemed to work OK too - but I am running with the 8 offset now (calculation comes out to 56 bytes right now I think).
*) I had configUSE_TICK_HOOK defined with an empty tick hook handler - xTickCount counted to 1 and then the uxPendedTicks happily ticked away as if it was xTickCount. Not sure if that is the intended operation or not when the handler is empty but just wanted to mention that.
I’m not sure just yet if this port is 100% stable at this point; seems to be running but I would like to test it for awhile.
Thanks and Regards,