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.

GCC for TMDSRM48HDK

Other Parts Discussed in Thread: HALCOGEN

Hi,


I am trying to build using GNU tool chain version of 4.9.3 using the Code Composer Studio IDE. I don't see any output if I run the code on the board. I also don't see any errors while building.

I have generated board setup code using Halcogen.

If I build using TI tools, I am able to get the output.

What I am doing wrong with GCC?

Thanks and Regards

 sridhar artham

  • Sridhar,

    Need to know a lot more specific details.

    1) what type of output are you getting / not getting?  (LED blinking, console IO, etc.)

    2) Do you get any error messages when compiling or downloading?

    3) when you download the code, does it get to your main() successfully?

    4) what does it do after that?  if it just 'runs' and does nothing, when you pause are you stuck at an exception vector?

  • Hi,


    I am not getting the output displayed on the console.

    Examples/demos are working fine on the board.

    I don't get any error messages while building as well as downloading.

    After downloading, successfully I can enter in to the main function.


    It runs, but it will not functions according to the expectation. Like printf, will not produce any output on the console, I am unable to create any files etc.

  • Sridhar,

    Ok then that's about as good as I would expect.  I wouldn't expect printf to work unless you customize the io device in the runtime lib.

    We don't supply this with CCS.  (EDIT:  with gcc that ships with CCS for Cortex R..  gcc it is mainly included for Cortex A and M.   The TI compiler fully supports console IO through a breakpoint mechanism)

  • Sridhar,

    BTW - have you considered checking w. Code Red for GCC support. Aren't they part of the same company?

    TI has always had it's own very strong compile expertise in house - so we've focused on the in house compiler rather than GCC for MCUs.
    If you switch to the TI compiler then I think these issues would disappear. But if you need support for GCC you'd be better going to a commercially supported GCC company (like Code Red or Atollic)..