Sonsivri
 
*
Welcome, Guest. Please login or register.
Did you miss your activation email?
July 21, 2017, 02:49:38 14:49


Login with username, password and session length


Pages: [1]
Print
Author Topic: Interrupt Log Feature in IAR not Working with SAMC20 Micro-controller  (Read 218 times)
0 Members and 1 Guest are viewing this topic.
xpress_embedo
Active Member
***
Offline Offline

Posts: 165

Thank You
-Given: 114
-Receive: 196


WWW
« on: July 04, 2017, 07:25:43 07:25 »

Hello Everyone,

I am working on a project and unfortunately there is some problem with the timer interrupt, when complete code is enabled this interrupt doesn't triggered at the rate programmed by me.
It looks that some other interrupt or some other piece of code (in which i disabled the interrupt) is causing this behavior.
So my main aim is to find the problem, so for that i thought i will use "Interrupt Log" feature present in IAR Embedded Workbench for ARM.

https://www.iar.com/support/resources/articles/interrupt-logging/

I am using ATSAMC20J18A micro-controller and J-Link Plus as Debugger in IAR 7.60

But when i debug my code, and try to open the interrupt log window, everything is disabled here, please see the snapshot below.


Even i read about ETM trace feature and it looks using this i can figure out the problem in my code.
And these settings are also enabled in my code, but again when i tried to use them i get error which is as follow:


I checked the ETM Trace Setting and it looks it has nothing that i can change.


I am assuming that i can't use ETM Trace using the J-Link and for that i need J-Trace, but other things should work, like Interrupt Log, Timeline but nothing is working.
Please suggest how can i enable this interrupt log feature or any other way to debug the problem.
Logged
h0nk
Active Member
***
Offline Offline

Posts: 137

Thank You
-Given: 99
-Receive: 91



« Reply #1 on: July 04, 2017, 09:28:14 21:28 »


Hello xpress_embedo,

a simple way to log interrupt activity is to build a simple DA-converter
with some unused GPIO's.
At every interrupt entry point, put out a value corresponding to the
priority of that routine.
Before the routine ends, put out a zero value, representing main().
On an connected scope You will get a picture of what is going on.


Good luck, and

Best Regards
Logged
xpress_embedo
Active Member
***
Offline Offline

Posts: 165

Thank You
-Given: 114
-Receive: 196


WWW
« Reply #2 on: July 05, 2017, 04:50:51 04:50 »

Hello xpress_embedo,

a simple way to log interrupt activity is to build a simple DA-converter
with some unused GPIO's.
At every interrupt entry point, put out a value corresponding to the
priority of that routine.
Before the routine ends, put out a zero value, representing main().
On an connected scope You will get a picture of what is going on.


Good luck, and

Best Regards


Thanks for your suggestion h0nk.
But to pass emi/emc tests hardware designers had grounded all the free/unused pins, so i can't test this thing.

If someone can tell me the reason for why interrupt log feature is not working than that will be very helpful for me, as i think this is the only thing i can try, rest all things which i am trying are hit and trial.
I have a development board on lpc1343, in this board interrupt log works fine, but strange it's not working on SAMC20
Logged
Pages: [1]
Print
Jump to:  


DISCLAIMER
WE DONT HOST ANY ILLEGAL FILES ON THE SERVER
USE CONTACT US TO REPORT ILLEGAL FILES
ADMINISTRATORS CANNOT BE HELD RESPONSIBLE FOR USERS POSTS AND LINKS

... Copyright 2003-2999 Sonsivri.to ...
Powered by SMF 1.1.18 | SMF © 2006-2009, Simple Machines LLC | HarzeM Dilber MC