• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 360 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.

HALcogen v04.0.00 not generating complete het.c for TMDXRM48HDK

Jamie Wardlaw
Expert 1895 points

Other Parts Discussed in Thread: HALCOGEN

I have just started to work on our latest software iteration for our Hercules RM48L952PGE based product.


As I am starting on the next complete development lifecycle I have upgraded to the latest versions of HALcogen (v04.0.00) and CCS v6.0.0.00190; I have also migrated to ARM compiler 5.1.6

On generating an empty build for the eval board to work up some prototype functions before moving to our production boards I have found that het.c is not being generated completely. It ends with the opening brace of the hetInit() function.

The only driver I have enabled in HALcogen is het2

Has anyone else experienced these issues?

Without resolution I will need to roll back to the CCS, HALcogen and ARM compiler versions of our previous development cycle.


Thanks

Jamie

  • 0
    Expert 1895 points

    Curiously, if I also enable the HET1 driver I appear to get the complete het.c generated. With only HET1 enabled I also get the complete het.c generated.


    So this looks like a HALcogen v04 bug, if you only have het2 driver enabled you will not get a complete het.c generated.


    Perhaps this can be moved to the HALcogen team for resolution.

  • 0 in reply to Jamie Wardlaw
    TI__Mastermind 22375 points

    Jamie,

    I confirm your finding with Halcogen 4.00 and Driver for HET2.

    I've forwarded your question to our HalcoGen team. 
    We will be back to you as soon as possible.

  • 0 in reply to Jean-Marc Mifsud
    TI__Genius 14205 points

    Hi Jamie,

    Sorry for the inconvenience, it's a bug even in the older version ( 3.9.x) of HALCoGen. It's a minor issue in the HALCoGen template file.

    Workaround 1: Enable HET1 and HET2 together always. Incase you do not want HET1 you can disable it outside HETInit using GCR register.

    Workaround 2: Close HALCoGen. Replace the attached het.c ( template file) in following folder.. C:\ti\Hercules\HALCoGen\v04.00.00\drivers\TMS570LS3137ZWT\HET570v000\het.c. ( Note: Take a backup of existing het.c , just in case..).. Now open HALCogen and generate the code with only HET2 Enabled, it should work.  8176.het.c