sprintf,printf and %f,%g,%e not working

Douglas Corarito

Intellectual 300 points

I'm using sprinf and printf in multiple threads in my app. RTS functions appeared to be working fine until

I called:

char[128] buffer = { '\0' };

float fpVar = 1.0;

sprintf( buffer, "%f", fpVar );

Which did nothing. Has anyone gotten %f,%g,%e format specifiers to work on C6455 with DSP/BIOS?

PS - I'm NOT calling this withing SWI or HWI, and like I mentioned the other specifiers are working fine.

over 16 years ago

0 TimHarron over 16 years ago

TI__Mastermind 18130 points

Can you try adding a \n to the end of the sprintf to flush the buffer?

char[128] buffer = { '\0' };

float fpVar = 1.0;

sprintf( buffer, "%f\n", fpVar );

*edit* Also, you may want to try upping your stack and/or heap sizes if this does not help.

0 Brad Griffis over 16 years ago in reply to TimHarron

TI__Guru*** 125430 points

http://tiexpressdsp.com/wiki/index.php?title=DSP_BIOS_FAQ#Q:_Why_the_standard_printf.28.29_does_not_work_anymore.3F

0 Douglas Corarito over 16 years ago in reply to TimHarron

Intellectual 300 points

Gave the '/n' a try and it still does not work.

Thanks.

0 Douglas Corarito over 16 years ago in reply to Brad Griffis

Intellectual 300 points

Thanks for that page Brad, really useful.

After going through each point, I'm still not able to get %f,%g,%e to work with sprintf or printf.

Just to reiterate, if I use %d, things work fine.

Anybody have any other ideas for me to try?

0 Douglas Corarito over 16 years ago in reply to Douglas Corarito

Intellectual 300 points

I just went and tried %f with the example project DSK6455....and it worked.

So, obviously, I've got some configuration issue somewhere.

0 Mariana over 16 years ago in reply to Douglas Corarito

TI__Mastermind 24340 points

The article that Brad suggested would be a good way to figure out what configuration you are missing...

0 TimHarron over 16 years ago in reply to Mariana

TI__Mastermind 18130 points

Did you increase the heap and/or stack?

0 Douglas Corarito over 16 years ago in reply to Mariana

Intellectual 300 points

This is from the FAQs page;

Note: Make sure that in linker command file you have properly allocated the .sysmem and .esysmem sections to valid memory of sufficient size. The heap gets allocated to the .sysmem section.

Step 3: Make sure you have allocated the .cio section to valid memory:

This section is used by the C I/O functions and needs to be allocated to valid data memory (PAGE 1) in the linker command file. It usually requires ~0x120 words but may be dependent on device family.

I though I had a grasp on the build process...but, nowI have a question.

I've got two .cmd files in my project - client.cmd and dsk6455cfg.cmd. The first doesn't have anything in it (all lines commented out) but the second looks like its created from .tcf and/or .cdb. However, neither of them have the .cio, .sysmem or .esysmem sections allocated.

Can someone explain if I need to add a linker.cmd file to my project, or is there somewhere (else) to specify these memory sections?

...and don't even know if this is problem. I've got external DDR memory set for malloc's the rest of the sections are all set for IRAM.

0 Douglas Corarito over 16 years ago in reply to TimHarron

Intellectual 300 points

Yes, heap and stack both set at 0x1000

No difference.

0 Brad Griffis over 16 years ago in reply to Douglas Corarito

TI__Guru*** 125430 points

Doug,

Make sure you're setting the stack/heap through BIOS and not through your project properties. In the bios config GUI you should go to MEM -> Properties. Your stack should be specified there and you should make sure to uncheck the box "no dynamic memory heaps" if it is not already unchecked. The two drop-boxes should then be configured to point to one of your heaps (e.g. DDR or IRAM). If you had not defined your heap through BIOS then you will have to do that on the individual memory segments. For example, you could go to DDR2 -> Properties and click the box "create a heap in this memory" and set its size. I also recommend that you check the box "enter a user defined heap label" and enter something like _DDR2. By doing so the corresponding extern statement gets placed automatically into the bioscfg.h file.

Brad

0 Douglas Corarito over 16 years ago in reply to Brad Griffis

Intellectual 300 points

Brad,

Thanks for the info. Still not working. Here's my .tcf

0 Brad Griffis over 16 years ago in reply to Douglas Corarito

TI__Guru*** 125430 points

Based on the fact that you were able to make it work with a simple example, but it doesn't work in your real application, you may have some kind of stability issue. There are many specific suggestions for debugging unstable code with BIOS here:

http://wiki.davincidsp.com/index.php?title=DSP_BIOS_Debugging_Tips

Please go through some of those suggestions, in particular see if anything looks wrong in KOV and double-check that you don't have any calls to BIOS APIs from the wrong context.

It seems like things are configured ok from what you've shown me. The only other thought I have is to try increasing your DDR heap size or else to start stripping out code from your project to see where the "offender" is at.

Brad

0 Douglas Corarito over 16 years ago in reply to Brad Griffis

Intellectual 300 points

Brad,

From FAQs:

Note: Make sure that in linker command file you have properly allocated the .sysmem and .esysmem sections to valid memory of sufficient size. The heap gets allocated to the .sysmem section.

Step 3: Make sure you have allocated the .cio section to valid memory:

This section is used by the C I/O functions and needs to be allocated to valid data memory (PAGE 1) in the linker command file. It usually requires ~0x120 words but may be dependent on device family.

I see .cio in the .tcf file, but, can you tell me how the SIZE is set? Is there an example somewhere? same for .sysmem and esysmem - how do I set the size?

0 Mariana over 16 years ago in reply to Douglas Corarito

TI__Mastermind 24340 points

If you are using NDK, please see section 5.7 (page 72) of the document:

http://focus.ti.com/general/docs/techdocsabstract.tsp?abstractName=spru523g

In order to guarantee a better performance a reduced version of printf was made for NDK that does not have floating point. You can use the regular version of printf by removing the miniPrintf.lib library from your project - but you can have performance issues.

Processors

Processors forum

sprintf,printf and %f,%g,%e not working

Note: Make sure that in linker command file you have properly allocated the .sysmem and .esysmem sections to valid memory of sufficient size. The heap gets allocated to the .sysmem section.

Step 3: Make sure you have allocated the .cio section to valid memory:

This section is used by the C I/O functions and needs to be allocated to valid data memory (PAGE 1) in the linker command file. It usually requires ~0x120 words but may be dependent on device family.