I mean in that use case, you could just offload the work to the Raspi and just let the cortex act as a controller board (for your motor outputs and sensor inputs). I have had better success with this venture in RobotC and PROS (though not on a PIC). But your issues might be a question for EasyC support.
You also have bluetooth on the Raspi - so changes could be made from a laptop (w/bluetooth) and the code run autonomously from the Raspi with a webserver running to keep you in the loop on your robots progress.
I assume it would be possible to use the Raspi and the program port on the cortex in order to push periodic code updates to the cortex - assuming you could parse the communications and reverse engineer the required commands and interface.
Some further reading: