- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
During debugging I've set up the breakpoint.
When breakpoint is hit, after 1 sec or so, the chip continue execution, but psoc creator doesn't change the state.
This is the moment when Psoc Creator loose control over the chip forever.
I must connect to the chip again (yellow exclamation mark).
The same aplies to psoc4.
The same situation (brkpt hit) . When I hit continue (F5) software refresh the window, but this doesn't affect the chip.
Chip don't receive run command at all. Even after 100 hits(F5)
The same with PSOC 4.
- Labels:
-
PSoC 5LP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There can be two different problem.
1. The chip runs after breakpoint, creator lose control:
Most possible a WD reset or the xres line or power glitch.
2. Cannot run after breakpoint.
That will happen if you have interrupt while breaking. So it exeute the interrupt and come back abd break at the same address.
You can disable the interrupt (there is a button on the toolbar) after breaking and it should stop and check what you need to do. Then you should re-enable the interrupt again then run again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you falling thru main(0 in your code, not in a for(;;) or while( 1 ) loop ?
Regards, Dana.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
"Are you falling thru main(0 in your code, not in a for(;;) or while( 1 ) loop ?"
As I understood, You ask if I receive return from main.
When control is lost I don't know anything about the chip.
I can only start all over again. I'm not able to debug this state
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You would not necessarily need to debug, just look at code to see if you
ever exit your infinite loop via a mistake in coding.
Regards, Dana.