The below table lists com­pil­ers, which winIDEA sup­ports in terms of load­ing the exe­cutable code and then debug­ging and test­ing it on the tar­get micro­con­troller via the TASKING Blue­box.

Proces­sor Fam­i­ly - 32-bit	Com­pil­er Ven­dor
Power Archi­tec­ture	Ada­Core, Cos­mic, Wind River Diab, GHS, GCC, NXP, MetaWare/MQX, Task­ing, High­Tec
ARM7, ARM9, Cor­tex-M, Cor­tex-R, Cor­tex-A	ARM, Code Sourcery, Wind River Diab, GHS, GCC, IAR, Keil, MetaWare/MQX, Task­ing, TI
V850, RH850	IAR, GHS, Rene­sas, Wind River Diab
Tri­Core, AURIX	Task­ing, GCC, High­Tec, GHS (TC2xx)

If your com­pil­er in use is not list­ed, just get in touch with us.

testIDEA’s inter­nal test engine doesn’t depend on the micro­con­troller archi­tec­ture only but also on a par­tic­u­lar com­pil­er and com­pil­er ver­sion being used. testIDEA must be fully aware of the call­ing con­ven­tion used by the com­pil­er. In case the com­pil­er ven­dor changes the call­ing con­ven­tion from one ver­sion to anoth­er, it will break testIDEA oper­a­tion too. Still, once a spe­cif­ic com­pil­er is sup­port­ed by a par­tic­u­lar archi­tec­ture, TASKING can quick­ly adjust the testIDEA engine when nec­es­sary.

The below table lists the sup­port­ed archi­tec­tures and com­pil­ers. A par­tic­u­lar com­pil­er ver­sion is also stat­ed for test­ed com­bi­na­tions.

Proces­sor Fam­i­ly	Com­pil­er
Power Archi­tec­ture	GCC 4.4.0 4.8.0, Code­War­rior 2-5, DIAB 5.7.0.0.
ARM7, ARM9, Cor­tex-M, Cor­tex-R, Cor­tex-A	ARM, Code Sourcery 4.6.1, Wind River Diab, GHS, GCC 4.8.0 4.6.0, IAR 6.70.1.5641, Keil, MetaWare/MQX, Task­ing, TI 4.6.4
V850, RH850	IAR 3.80 (RH850)1.10, GHS 201315, Rene­sas 3.45, Wind River Diab 5.9.3.0
Tri­Core, AURIX	Task­ing 3.0r1, 3.5r1

If your com­pil­er in use is not list­ed, just get in touch with us.