• Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 240 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Problem on executing a simple program on wince device.

Lazy Donkey
Prodigy 170 points
Other Parts Discussed in Thread: OMAP-L137

 

Hi,

I am using OMAP-L137 and MPC-Data wince600, I used the SDK which I created and run a very small program, just print out a message in the _tmain(), However there is no output at all. The previous version of OS I built worked, and I forget what options I have changed on this version of OS).  I can see the pogram was deployed(saw it on remote process viewer)  But it just not executed or stop somewhere before _tmain(), any idea?

 

Thank you for your help!

-kc

 

 

  • TI__Intellectual 1640 points

    Do you mean the print does not show in termnial nor on Visual Studio?

    Did you accidentally enabled one of the Third Party > BSP > OMAP137_AM17X > Device Drivers > Serials in your OS?

    Can you set break point in your test app to make sure the print statement is executed?

    Regards,

    WM

  • in reply to WMK
    Prodigy 170 points

    Hi WM,

    1. I meant neither shown in the Visual Studio for Application nor on Visual Studio for Platform to attach the device. I opened two Visual stdio.

    2. The "Third Party > BSP > OMAP137_AM17X > Device Drivers > Serials" is on all the time (we will use serial port later), however I disabled it and clean and rebuild still no help.

    3. I tried put a break point as you said, it did stop there, however there is no output.

    Thanks.

    -kc


  • in reply to Lazy Donkey
    Mastermind 9310 points

    _tprintf does not output on the debug window as you expect it but rather on the standard output which you get when you open a command window. If you want to see your trace output in the debug window, use RETAILMSG instead of _tprintf. In another hand, if you telnet your board and launch your program from the command, you should see your _tprintf output, as telnet redirects the standard output to your remote console.

  • in reply to Adeneo Embedded support team
    Prodigy 170 points

     

    I didn't use the telnet or open a command window in CE, I was using two visual studio 2005 on developing computer, one for debugging the CE application program(which just print out a  message), and another one to attach to CE OS Kitl to receive messages from CE image.  The messages were print out from  both the visual studio output windows(the "show output from windows CE Debug") , it was working fine, till I changed options in Catalog Items View, and redownload the OS image.

    -kc