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

N2HET 'Lib'

John Westmoreland43
Guru 13945 points


Hello,

After working with the HET IDE briefly; it would seem there would be more routines available as library(ies) - yet I don't see that; or at least I can't find something like that.

Is there such a thing as an HET LIB someplace?  I realize there may not be a proper librarian; but it would seem people would have developed some routines for the more common sensor interfaces.

Thanks In Advance,
johnw

  • 0
    TI__Guru 68940 points
    Hi John,

    We took a first pass at this with a 'What the HET?" email that went out last year...
    www.ti.com/.../spny009 is a whitepaper and on the http://www.ti.com/tool/HET_IDE download page the associated appnotes
    & example code are posted. and are especially to thank.

    There is *soooo* much more we can do w. HET ... if you have ideas let us know. I think in fact I'll make a sticky post for people to post requests...
  • 0 in reply to Anthony F. Seely
    Guru 13945 points
    Anthony,

    Thanks - I guess I have been somewhat naive looking at this previously; the HET I/F here is another processing engine and impressive. I have one capture input and three PWM's operational now. This is great.

    (In my defense - I did look at this previously - I just have had bigger 'bugs' to fry before I really got to play with the 'real' HET stuff. ;))

    Thanks Again!
    John W.
  • 0 in reply to John Westmoreland43
    Guru 13945 points

    Anthony,

    Once the N2HET has been programmed - is it OK to change variables during run-time to change capture and/or PWM characteristics - or do you have to restart the N2HET?  What is the proper way to restart the N2HET during runtime?  

    Thanks,

    John W.

  • 0 in reply to John Westmoreland43
    TI__Guru 68940 points
    Hi John,

    Yes, the host CPU can change the control and data fields at runtime.
    However, synchronization is part of the design problem it's not handled automatically by the N2HET.

    For example, if you use the CPU to write directly to an ECMP instruction - this is akin to an asynchronous or unbuffered compare register update.

    On the other hand if you have your program designed with a MOV64 instruction [copies both data and control fields to target, hence name 64] this is akin to a 'buffer'. If you design the program so that on an ECMP match or counter reset (whichever is appropriate) the MOV64 updates the ECMP, then the CPU may make asynchronous updates to the MOV64 instruction and the N2HET will then synchronously copy the MOV64 contents to the ECMP on an ECMP event.

    Hope that brief explanation helps. In a nutshell.... yes, control and data are designed to be updated on the fly by the host CPU; but there is a burden on the N2HET program design to handle the updates 'correctly' as well.

    -Anthony
  • 0 in reply to Anthony F. Seely
    Guru 13945 points
    Anthony,

    I see I didn't thank you for this answer - so, thanks for this answer!

    Regards,
    John