Kinetis processorexpert code generation bug?

[BenFan]

I have a project using 3 ExtInt components (INT_PORTB, INT_PORTC and INT_PORTD) on MK10DN128VLF5.

When ProcessorExpert generates code the ISR for INT_PORTD is duplicated CPU.c

PE_ISR(Cpu_ivINT_PORTD)

{

  ExtIntLdd3_Interrupt();              /* Call the service routine */

}

PE_ISR(Cpu_ivINT_PORTD)

{

  /* This code can be changed using the CPU component property "Build Options / Unhandled int code" */

  PE_DEBUGHALT();

}

Clean build etc. did not help.

I also created new project to confirm it's always the same problem.

How can I prevent this from happening?

It's really annoying, every time I build the project I have to go delete the second dummy ISR and build it again.

I use CW10.4 b. id 130425

br,b

[vfilip]

Hello,

I was not able to reproduce it. Could you please post here ProcessorExpert.pe file from your project in order to reproduce it on our side?

For future questions related to PEx please use our forum: https://community.freescale.com/community/pex

Best regards

Vojtech Filip

Processor Expert Support Team

[BenFan]

I'm sorry for posting in wrong forum.

Can you move it to PE forum?

I think I found the problem.

It's only when you also use AsynchroSerial (UART) component with RTS/CTS flow control enabled.

In my case, RTS signal is PTD0 and that could be problem source.

pe file is attached.

br,b

[vfilip]

Hello,

I have reproduce it and classified it as a bug in PEx for CW V10.4. However seems that issue was already fixed in CW V10.5.

Could you please try to move to this version or would you rather prefer hot-fix for CW V10.4?

Best regards

Vojtech Filip

Processor Expert Support Team

[BenFan]

No good news with CW 10.5

Cpu_ivINT_PORTD() redefinition is reoccurring in Cpu.c file.

Can you check it on your CW 10.5 setup?

Br,

Ben

[vfilip]

Hello,

When I switch the "Unhandled vectors" property from "One handler for every" to "One handler for all" on build options tab in CPU component I am able to build the project. Could you please use this as a temporary workaround till the hot-fix will be ready? I was not able to reproduce it originally due to importing only ProcessorExpert.pe file instead of whole project.

Best regards

Vojtech Filip

Processor Expert Support Team