printf

Thank you, I`ll try this

Hi,

I`ve created new hello world project and new configuration project with a simple configuration.

stack = 8192 heap=8192

My target is OMAPL137EVM, I use CCSv4.2 and xdc+bios6+codegen that go with the installation.

I use internal emulator.

My host is Win XP professional SP3 + Sun Java machine

printf("hello world") doesn`t print anything to the console window of the CCS

On the other machine with the same software configuration hello world works fine.

Is there any ideas?

Yuriy Kubasov said:

printf("hello world") doesn`t print anything to the console window of the CCS

Did you include stdio.h?  Try printf("hello world\n") since stdout stream is line buffered by default and will not be flushed to the output until end of line.

Yuriy Kubasov said:

printf("hello world") doesn`t print anything to the console window of the CCS

Another thing to check is that you are in the correct console mode. You can toggle between the various consoles using the 'Display Selected Console' drop-down menu.

The below url shows how to get to the GEL console. The one below that option in the drop down menu is for CIO.

http://processors.wiki.ti.com/index.php/FAQ_-_CCSv4#Q:_How_come_my_GEL_expressions_are_not_being_evaluated_when_I_enter_them_in_the_.27Console.27_view.3F

I think the console mode should switch automatically to the last used console.

It`s not a console problem.

I used the same project with the OMAPL138 experimenter kit with the built-in XDS100-USB emulator - the printf works fine

The cfg project of the SYS/BIOS  is the same (despite of the platform type)

Maybe it`s a emulator problem?

Best regards,

Yuriy

Can you attach your failing project?  Go to "options" to add a file attachment to a post.

Normal 0 false false false MicrosoftInternetExplorer4

I have the same console problem. printf("hello world\n); it prints nothing. I use MSP-FET430UIF and processor I try to program is MSP430F149

^{If the program compiles and loads correctly, then printf problems on MSP430 are almost always due to insufficient heap and/or stack sizes. Please try increasing these.}