• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 495 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

HET_IDE: avoid conflict with two programs

matteo lucarelli
Genius 3265 points

Hi,

I'm developing an application for RM48 that uses two different custom codes for the two HETs.

Both HET programs are assembled with HET_IDE and the generated .c and .h are included in the CCS code.

The problem is that both assembled codes uses the same define (HETPROGRAM0_UN, HET_INIT0_PST, ecc) causing a clear conflict in the code compilation.

There is a way to modify the HET_IDE behaviour and to change the define labels?

thank you,

Matteo

  • 0
    TI__Prodigy 710 points

    Thanks for using the Hercules forum! An engineer has been notified of your question.

  • 0 in reply to Leo Huang1
    TI__Guru 68830 points

    Matteo,

    Yes and no....

    The het assembler 'hetp' takes -hc32 -nX as an option where X is a # 0,1,2,...

    If you use -hc32 -n1 on the command line, instead of HETPROGRAM0_UN you'll get HETPROGRAM1_UN in the output.

    So that's how you assembly differently for the two different N2HETs.

    But I just tried simply adding the -hc32 -nX on the 'options' of the HET IDE where the executable path is.  It doesn't work and in fact crashes so I wouldn't try it.

    I think you may be at a point where you can consider building your programs separately - let the HET IDE build them for testing in the HET IDE, but then assemble them again in with the correct options either through CCS or through a makefile.

    CCS does let you add custom build steps so you could use this mechanism to assemble each of your HET programs before the rest of your applicaton builds.

  • 0 in reply to Anthony F. Seely
    Genius 3265 points

    Very clear, thank you.