topic Re: MCC Cpu-to-CPU interrupt cycle time in Vybrid Processors

MCC Cpu-to-CPU interrupt cycle time

hjk — Tue, 24 May 2016 02:49:58 GMT

Hi,

I am now using TWR-VF65SG10, and I try to measure the cycle time of MCC cpu-to-cpu interrupt,

How much cycle it takes between M4 triggers an interrupt and A5 receives an event?

Since I can't use Streamline, and SSH into the target board, is there any way I could measure the cycle time or can some provide me a number ?

Thank you

Re: MCC Cpu-to-CPU interrupt cycle time

karina_valencia — Mon, 30 May 2016 16:44:59 GMT

timesyssupport can you help to review this case?

Re: MCC Cpu-to-CPU interrupt cycle time

timesyssupport — Thu, 02 Jun 2016 07:17:00 GMT

Hi,
As far as I checked the reference manual contains no information regarding the CPU to CPU cycle time. And I am not aware other than streamline how to find the cycle time. To make us understand the problem could you please tell us why you looking for cycle time?

Thanks,
Timesys support.

Re: MCC Cpu-to-CPU interrupt cycle time

hjk — Mon, 06 Jun 2016 07:07:03 GMT

Hi,

I want to know the overhead of CPU to CPU interrupt, when one core tries to use the MCC API to trigger the interrupt to the other core.

Is the overhead of triggering hardware interrupt is too small to be neglected, then I can just calculate the API execution cycle time?

Thanks

Re: MCC Cpu-to-CPU interrupt cycle time

timesyssupport — Mon, 06 Jun 2016 17:26:28 GMT

Hi,

Unfortunately, I do not know the time it takes on the hardware side for the CPU-to-CPU interrupt to trigger. karinavalencia, can the NXP Vybrid hardware team comment here?

Thanks,

Timesys Support

Re: MCC Cpu-to-CPU interrupt cycle time

karina_valencia — Mon, 06 Jun 2016 17:51:46 GMT

jiri-b36968 can you comment here?

Re: MCC Cpu-to-CPU interrupt cycle time

jiri-b36968 — Tue, 07 Jun 2016 11:26:43 GMT

Hello

please look here

https://community.nxp.com/thread/384093#comment-611114

https://community.nxp.com/thread/384093#comment-612762

/Jiri

Re: MCC Cpu-to-CPU interrupt cycle time

hjk — Wed, 08 Jun 2016 06:58:00 GMT

Hi jiri-b36968,

I've read your comments, I have a few question

1. Are those number of first comment from AN4947 ?

2. You mentioned that the conclusion of 664 MB/s is based on theory, is that the result of calculation of those number mentioned above?

3. How did you get the number of 7MB/s ? is that a real target board's result ?

Thanks,

Re: MCC Cpu-to-CPU interrupt cycle time

jiri-b36968 — Wed, 08 Jun 2016 07:15:59 GMT

Hello a a,

1. Yes. Also those numbers come from designers.

2. Yes. It is theoretical throughput of HW - more in the thread.

3. It was real test on real board (debug target, release can be faster as mentioned in the thread).

/Jiri

Re: MCC Cpu-to-CPU interrupt cycle time

hjk — Sun, 12 Jun 2016 09:14:45 GMT

Hi jiri-b36968,

For third question, can I get more detailed information?

Like how much time does it spend on semaphore locking, and interrupt handling?

If I have only ARM energy probe and CMSIS-DAP from board, how can I do in DS-5 to get that more information?

Thanks,

Re: MCC Cpu-to-CPU interrupt cycle time

jiri-b36968 — Tue, 14 Jun 2016 07:14:11 GMT

Hello a a,

the test details are here https://community.nxp.com/thread/384093#comment-612762

Semaphore is peripheral like any other. Please check AN4947. For interrupt handling please look at ARM Information Center

To measure event you can use internal timers of ARM or you can use GPIO toggling + oscilloscope.

/Jiri

This an automatic process. We are marking this post as s...

CommunityBot — Thu, 03 Sep 2020 18:48:55 GMT

This an automatic process.

We are marking this post as solved, due to the either low activity or any reply marked as correct.

If you have additional questions, please create a new post and reference to this closed post.

NXP Community!