Page 1 of 1
iprintf in dspi.cpp
Posted: Wed Feb 04, 2015 3:19 pm
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.
Re: iprintf in dspi.cpp
Posted: Wed Feb 04, 2015 3:25 pm
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
Re: iprintf in dspi.cpp
Posted: Thu Feb 05, 2015 9:28 am
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?
Re: iprintf in dspi.cpp
Posted: Thu Feb 05, 2015 2:52 pm
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..
Re: iprintf in dspi.cpp
Posted: Thu Feb 05, 2015 3:20 pm
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.