Pumpkin User Forums
  TI's MSP430
  debug_printf() problem with rowley crossworks

Post New Topic  Post A Reply
profile | register | preferences | faq | search

UBBFriend: Email This Page to Someone! next newest topic | next oldest topic
Author Topic:   debug_printf() problem with rowley crossworks
ankushdesai
Junior Member
posted August 18, 2009 10:23     Click Here to See the Profile for ankushdesai     Edit/Delete Message   Reply w/Quote
Hey Thanks a lot for your Reply

IP: 210.212.55.3

aek
Moderator
posted August 18, 2009 08:06     Click Here to See the Profile for aek     Edit/Delete Message   Reply w/Quote
This is really a CrossWorks question (has nothing to do with Salvo), but I'll answer it anyway.

The debug functions that are part of CrossWorks are functions that are implemented through the JTAG port "all the way back to the host PC". I.e., if you disconnect the JTAG programmer / debugger, the code stops / crashes.

Therefore it is completely to be expected that you end up with odd runtime behavior when calling any of the debug functions. To get around that, replace debug_printf() with a real printf() that works through one of the MSP430's serial ports.

------------------

IP: 76.191.193.224

ankushdesai
Junior Member
posted August 18, 2009 02:24     Click Here to See the Profile for ankushdesai     Edit/Delete Message   Reply w/Quote
I am facing a problem with a very basic code on MSP430F2618. I am using crossworks v2 for MSp430.
I have attached a very basic code while toggles the Output of P1.3 in a while loop. The problem is whenever i put a debug_printf() statement in my code anywhere it gives a waveform, from which we can see that it performs well for some 7-8 msec and then goes blank for sometime and then again toggles the port bit. This thing happens only when in debug mode and the port toggles properly when i run the code in "build and run" mode/ "build and Debug" mode with the debug_printf() statement removed. So wat i concluded was that there is some problem in the
debug_printf() statement and in debug mode.
My question is why its goes blank after 7-8 milisecs.
The section of the waveform (7-8 ms) if expanded is the proper square waveform in which it performs properly.

Code :
void main(void)
{
int i=0;
P1DIR |= BIT3;
//Stop the Watch dog timer
WDTCTL = WDTPW + WDTHOLD;
while(1)
{
P1OUT ^= BIT3;

}


debug_printf("hello world\n");
}


Thanks,
Ankush Desai

IP: 202.3.77.133

All times are ET

next newest topic | next oldest topic

Administrative Options: Close Topic | Archive/Move | Delete Topic
Post New Topic  Post A Reply
Hop to:

Contact Us | Pumpkin Home Page

©2000-2008 Pumpkin, Inc. All Rights Reserved. Pumpkin and the Pumpkin logo, Salvo and the Salvo logo, The RTOS that runs in tiny places, CubeSat Kit and the CubeSat Kit logo are all trademarks of Pumpkin, Inc. All other trademarks are the properties of their respective owners.


Ultimate Bulletin Board 5.46a