iprintf in dspi.cpp

Discussion to talk about software related topics only.
Post Reply
SeeCwriter
Posts: 630
Joined: Mon May 12, 2008 10:55 am

iprintf in dspi.cpp

Post by SeeCwriter »

There are 2 iprintf() statements in the Start() function in dspi.cpp. It seems to me these should be wrapped within
a #ifdef __DEBUG_DSPI statement. Does that seem reasonable? Seeing these outputs mingled among my own debug statements can be confusing.
User avatar
dciliske
Posts: 624
Joined: Mon Feb 06, 2012 9:37 am
Location: San Diego, CA
Contact:

Re: iprintf in dspi.cpp

Post by dciliske »

Yea, those shouldn't be there. They're removed in the current checkins. I'll be looking to write some commit checks that prevent this from slipping through.

-Dan
Dan Ciliske
Project Engineer
Netburner, Inc
SeeCwriter
Posts: 630
Joined: Mon May 12, 2008 10:55 am

Re: iprintf in dspi.cpp

Post by SeeCwriter »

I wrapped the iprintf()'s in #ifdef __DEBUG_DSPI statements, did a make on the Nano System directory which recompiled
dspi.cpp, yet the iprintf() statements are still active. Do I need to do something more than compile the file?
User avatar
pbreed
Posts: 1088
Joined: Thu Apr 24, 2008 3:58 pm

Re: iprintf in dspi.cpp

Post by pbreed »

rebuild all your project?

Also make sure your rebuilding release/debug the same as your project release/debug....

Its possible to rebuild the release library and then compile a debug project or <-> other way around..
ecasey
Posts: 164
Joined: Sat Mar 26, 2011 9:34 pm

Re: iprintf in dspi.cpp

Post by ecasey »

Also make sure that the project for the module you want is open and selected.

Look at the Console window at the beginning of the process to see that the files have the MODXXXX (where XXXX is the module number you want the rebuild for) in the name, otherwise you may have rebuilt the files for the wrong module, causing no end of frustration when the changes don't have any effect in the project.
Post Reply