• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 801 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.

Use of HetPort without HET enabled

Andy Worsley89
Intellectual 670 points
Other Parts Discussed in Thread: HALCOGEN

Hi,

can somebody settle an argument please.

We are using the TMS570LS04 and we want to use the hetPort as GIO, but not use the het module. To drive the hetport we need the defines in reg_het.h and het.h. It has been found that these files are generated by HalCoGen regardless of whether the Het driver is enabled (in the Driver Enable tab) and the Peripheral Enable is enable (in PinMux).

One engineer says that this is a fluke and shouldn't be relied upon and the driver should always be enabled, regardless of the unused code that is generated (het.c)

The other engineer says that this isn't a fluke, it's deliberate so that the hetport can be driven as GIO without the Het being activated and we shouldn't generate unnecessary code.

Who is right?

Regards

Andy

  • 0
    TI__Guru 67600 points
    Andy,

    Yes you can use the HET GIO without enabling the HET (timer functions). For this at least I think you need the HET register level
    header file as this is where the port is defined.

    The het.h and het.c though should mainly be for the HET application code that implements a simple / generic timing functions as exposed
    through the halcogen gui. So you definitely could trim something here if they are generated; but anything beyond what is already trimmed out by the tool you'd need to trim out manually.
  • 0
    Intellectual 670 points
    Hi Anthony,
    thanks for your reply.

    So, this feature: that reg_het.h and het.h are produced without the HET module being enabled, is not something that is likely to be deleted from future iterations of the HalCoGen tool?

    Regards
    Andy
  • 0 in reply to Andy Worsley89
    TI__Guru 67600 points
    Andy,

    No I don't think so; but I can't guarantee that.
    In any case the files can be generated so if they ever stopped being generated you could still generate them once and then use them from your project's include folder. But I really doubt this would ever happen.