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

TMS570LS3137: Halcogen - add custom tab

Marcell Varga
Prodigy 30 points

Part Number: TMS570LS3137
Other Parts Discussed in Thread: HALCOGEN

Hello,

I am just started to use the Halcogen for HAL layer generation, and I was wondering about:

Is there any way to add a custom configuration tab to HAL code generator to these?

Thank you in advance,

  • 0
    TI__Guru 59540 points
    Hello Marcell,

    TI doesn't support or encourage the modification of the Halcogen tool outside the normal use of it to generate the drivers for the Hercules products.
  • 0 in reply to Chuck Davenport
    Prodigy 30 points

    Hello Chuck,

    Thank you for the info,

    Please let me specify the problem I have encountered with halcogen:
    I have to support many applications which has the only difference at the CAN interface configs. (Different messages IDs.)
    This caused the now I have 6 configuration files and I have to update all of it when a non CAN related change needed.
    (Which could be problematic on the long run: more applications, inconsistencies and so on.)

    Do you have any idea how to merge all of the configuration files into one?
    Is the Halcogen source code available as open-source or as licensed copy? (If yes where and how?)

    Best Regads,

    Marcell Varga

  • 0 in reply to Marcell Varga
    Guru 15740 points

    Marcell,

    The usual way to override or change HALCoGen generated settings is in the source code that HALCogen generates for your project, between the user blocks.
    That has helped me to deal with most situations where the GUI doesn't offer a particular option. You can still modify the projects with HALCoGen afterwards without losing these user sections.

  • 0 in reply to Jan Cumps
    Prodigy 30 points
    Hello Jan,
    That will do the trick I guess,
    Thank you,

    Best Regards,
    Marcell Varga
  • 0 in reply to Marcell Varga
    TI__Guru 59540 points
    Marcell,

    I can understand the issue you are describing. What I would suggest is that you keep a master project in Halcogen for all of the common modules so you only have to update these once for all your projects. For the CAN and any other project specific modules, create project specific halcogen projects. When you generate the code for the general projects, you can keep these in a common directory included in all projects (make sure you exclude/remove any non-common files). For project specific files, keep these separate in their own project related directories and include them only in the projects that need them. This way, each project will share the common source and each project will have its own custom configs for their unique content. The key is to be sure to manage so there is no overlap between the shared modules and the custom modules.