Cypress Perform

Home > Design Support > Cypress Developer CommunityTM > Cypress Forums > PSoC® 5 > Problem with Interupt

Bookmark and Share
Cypress Developer CommunityTM
Forums | Videos | Blogs | Training | Rewards Program | Community Components



Problem with Interupt
Moderator:
ANCY

Post Reply
Follow this topic



Problem with Interupt

andyds11 posted on 18 Jun 2012 10:35 PM PST
Member
4 Forum Posts

 I have a program that stopped working. When I build it I get two warnings:

Tech mapping ...

Info: mpr.M0037: Unused pieces of the design have been optimized out. See the Tech mapping section of the report file for details. (App=cydsfit)

Analog Placement ...

Info: apr.M0002: Analog signal "\ADC_DelSig:Net_690\" is connected to one terminal only. (App=cydsfit)

Analog Routing ...

 

When I place a breakpoint in my interupt routine it is disabled and I can't enable it. Breakpoints elsewhere in my code work fine. The interupt routine is connected to the DMA. This used to work just fine. Any suggestions?

 

Andy Silber

 




Re: Problem with Interupt

srim posted on 18 Jun 2012 02:48 AM PST
Cypress Employee
121 Forum Posts

 Could you please attach your design so that we can have a look? To do so, go to 

File--> create workspace bundle -->archive -->attach the zip file



Re: Problem with Interupt

andyds11 posted on 19 Jun 2012 10:57 PM PST
Member
4 Forum Posts

I'm getting this warning

"Warning: Cannot set breakpoint: 'C:\Users\Andy\Documents\PSoC Creator\AA_PP1.cydsn\Generated_Source\PSoC3\ISR_DMA_Done.c:136'.  Encountered error (No debug symobols for file 'C:\Users\Andy\Documents\PSoC Creator\AA_PP1.cydsn\Generated_Source\PSoC3\ISR_DMA_Done.c'.)."

 

I've included the bundle of my code. I removed some of the files, but the problem persists.

 

Andy

 


 



Re: Problem with Interupt

anir posted on 11 Jul 2012 11:07 PM PST
Top Contributor
24 Forum Posts

 Hi Andy,

I had issues in opening your project, hence created a new one and added your files to this new project. Also since I had issues in building the project, I had to modified your files (moved functions on top in fft_main.c file and local declaration on top in main.c file). When I tried to debug by adding the breakpoint at line 136 (which is not valid; it moves to line 141), I did not find any issues. Please try with the updated project attached (AA_PP1-000.Bundle01_updated.zip).

Thanks, Aniruddha 

 



Re: Problem with Interupt

anir posted on 11 Jul 2012 11:09 PM PST
Top Contributor
24 Forum Posts

 Sorry, project did not get attached.



Re: Problem with Interupt

srim posted on 11 Jul 2012 11:14 PM PST
Cypress Employee
121 Forum Posts

 Attaching the project on behalf of anir.



Re: Problem with Interupt

Bob Marlowe posted on 11 Jul 2012 11:39 PM PST
Top Contributor
1768 Forum Posts

Are you sure?

Bob



Re: Problem with Interupt

srim posted on 11 Jul 2012 11:58 PM PST
Cypress Employee
121 Forum Posts


Re: Problem with Interupt

srim posted on 11 Jul 2012 11:59 PM PST
Cypress Employee
121 Forum Posts

 n the touble of attaching project continues!!!! :(



Re: Problem with Interupt

Bob Marlowe posted on 11 Jul 2012 12:05 AM PST
Top Contributor
1768 Forum Posts

Byte your teeth! Hold on!!!



Re: Problem with Interupt

Bob Marlowe posted on 11 Jul 2012 12:06 AM PST
Top Contributor
1768 Forum Posts

A (small) hint: Before achiving the project, run a "Clean Project"

 

Bob



Re: Problem with Interupt

anir posted on 11 Jul 2012 12:24 AM PST
Top Contributor
24 Forum Posts

Attaching the project after cleaning.



Re: Problem with Interupt

anir posted on 11 Jul 2012 12:24 AM PST
Top Contributor
24 Forum Posts

Thanks Bob. It worked.



Re: Problem with Interupt

Bob Marlowe posted on 11 Jul 2012 12:27 AM PST
Top Contributor
1768 Forum Posts

Yes... those small hints...

 



Re: Problem with Interupt

Bob Marlowe posted on 11 Jul 2012 12:49 AM PST
Top Contributor
1768 Forum Posts

I had a look into the project and there is NO code in the DMA_Done interrupt! So there is no place to put a breakpoint to.

I STRONGLY(!!!) recomend to use a different approach for ISRs: Use the ISR_StartEx(MyIntRoutine) API and have declared

CY_ISR_PROTO(MyIntRoutine);

and defined

CY_ISR(MyIntRoutine)

{

   // Routine Body

}

 

This always gives you full control and the ISRs are residing in one of YOUR files (main.c) and not buried deep in one of the generated ones.

 

Happy coding

Bob



Re: Problem with Interupt

sachinbvp posted on 11 Jul 2012 05:26 AM PST
Top Contributor
139 Forum Posts

CY_ISR will help you out in solving and framing code of interrupts

for example:

CY_ISR(sw_interrupt)
  {
  // blink led here
  }






ALL CONTENT AND MATERIALS ON THIS SITE ARE PROVIDED "AS IS". CYPRESS SEMICONDUCTOR AND ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THESE MATERIALS FOR ANY PURPOSE AND DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THESE MATERIALS, INCLUDING BUT NOT LIMITED TO, ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EITHER EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, IS GRANTED BY CYPRESS SEMICONDUCTOR. USE OF THE INFORMATION ON THIS SITE MAY REQUIRE A LICENSE FROM A THIRD PARTY, OR A LICENSE FROM CYPRESS SEMICONDUCTOR.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms and Conditions of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms and Conditions of this site. Cypress Semiconductor and its suppliers reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Spec No: None; Sunset Owner: GRAA; Secondary Owner: RAIK; Sunset Date: 01/01/20