Looks that if I set the break withing interrupt I should put : "ignore break_num 2" That way I am able to see what variables changed between interrupts, like i.e. execution speed
robert On Tuesday 22 of June 2004 03:23, Steve Underwood wrote: > Chris Liechti wrote: > > Robert Seczkowski wrote: > >> And Do You know why break withing wdt interrupt doesn't execute main > >> loop. > >> I type "c" and break is caught once again but meantime main loop is > >> not executed even once. WDT timer is set to 32ms. > > > > yes, and while your wathcing the memory dump in gdb, the WDT continues > > to count down. after an other 32ms is the WDTIFG set, but not executed > > as you have still stoped it. after releasing, it contniues with the > > highest priority interrupt that is pending. > > > > in short: breakpoints only stop the CPU core, an NO peripherals. > > This depends on the particular MSP430 you are using. Some have a clock > cotnrol register which can be used to alter this behaviour. I have not > yet added control of that to msp430-gdbprixy. I really should do. The > default behaviour is as you said. > > Regards, > Steve > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users -- Regards Robert Seczkowski robert.seczkow...@sz.onet.pl //\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\//\\
