I tested on my XC-1 using the Windows IDE.Which errors did you got and on which board did you test?
I changed the definition of vParTestSetLED in partest.h to
Code: Select all
int vParTestSetLED( unsigned portBASE_TYPE xValue );
Code: Select all
int vParTestInitialise( void );
I saw the earlier posts and don't see any benefit in running multiple kernel threads on a single core, apart from the curiosity, and agree you should leave the shared code intact. What I mean though is when you have a single bootable image to be loaded onto multiple cores; so on one core you would have 1 freeRtos thread and 7 real-time threads, and independently on another core (and another memory space) you would have a similar arrangement, but with different configuration entries in the common FreeRTOSConfig.h for the two (or more) cores - then #if sections would be useful. Another solution would provide a FreeRTOSConfig.h per core and specify different include search paths for them.A more important issue is the use of global variables by the kernel which makes running multiple kernels next to each other without modifying all references impossible. I tried to leave as much of the shared code intact as possible.
I look forward to seeing your new design, and the task-to-thread communication method.