You are here

PSoC designer 5.1 debug strategies | Cypress Semiconductor

PSoC designer 5.1 debug strategies

Summary: 4 Replies, Latest post by danaaknight on 23 Mar 2013 07:24 AM PDT
Verified Answers: 0
Last post
Log in to post new comments.
user_278462884's picture
35 posts

HI Forum,


I'd like to know how to know the value of a variable after certain executions have elapsed. I tried "Add Watch" in the watch window under debugger - but the value of the variable remains as 0x0000 inspite of numerous Compile-Run iterations.

I'm sure that the increment occurs as I also toggle a LED inside the same block which I confirm using a DSO. 


Awaiting replies,


user_1377889's picture
9301 posts

RAM, do you own an ICE-Cube? Afaik only with that is it possible to inspect variables and set breakpoints with PSoC1.

Another hint is to turn off all optimization since a variable might be kept in a register.



rjvb's picture
Cypress Employee
90 posts

You need to pause the debugger to see the updated variable values or it can be invoked with a break point. 

user_278462884's picture
35 posts



Good to see you Bro! you were on a holiday ? Been some tym I got guidance from you! :) 


Alryt, coming to the point, I do have an ICE cube. Can you elaborate on how that optimization thing shud be done > ? 


Regards, RAM

user_14586677's picture
7646 posts

Optimization is a setting for the compiler that you can turn off from

optimizing code. Used in debugging, when in production release

you turn it back on to minimize FLASH used and speed up routines.

Note it can affect timing, when you turn it off, depending if your rely

on SW loops for delay, etc...


Go to Project, Settings, Compiler, to change settings.


Regards, Dana.

Log in to post new comments.