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.h" Generated by HALCoGen 04.05.01

Other Parts Discussed in Thread: HALCOGEN

I'm using HALCoGen 04.05.01 and CCSv6.1.0.

The code "#include <string.h>" is found in "het.h".

No error is caused when it is removed and it is built.

Does it need?

Best Regards,

Satoshi Shinohara

  • Hello Satoshi,

    I am not aware of the specific reason that this header file is included in the het.h header file. Is there a specific reason why you are not able to leave it in?
  • Hello Chuck,

    Thank you for your reply.

    Our project doesn't need "string.h" file except "het.h"

    We would like to reduce the related file for the functional safety test.

    Best Regards,

    Satoshi Shinohara

  • Hello Satoshi,

    I am checking with our Halcogen team lead to see why this include is there. Once I hear back from them, I will update you on its purpose.

    In the mean time, please note that if you manually remove this from the het.h file, you will need to do the same each time you use Halcogen to regenerate your code. i.e., many customers will use Halcogen to make changes to the configuration of peripherals while in development or will regenerate code when a new version of Halcogen is released so that they can take advantage of bug fixes. When doing so, code placed within the USER CODE sections is left unchanged, but any other code is updated by Halcogen or, in this case, would be restored by Halcogen.
  • Hello Chuck,

    Thank you for your information.

    I understand that the updated code within the USER CODE sections is left unchanged when regenerated.

    I will wait for the update.

    Best Regards,

    Satoshi Shinohara

  • Hello Satoshi,

    I have yet to hear from our Halcogen team on the requirements for including the string.h header file so I cannot give any background information and it does not appear that I will be able to anytime soon.

    As always, any code generated from Halcogen is not guaranteed and requires that it be tested by the end user in their application to insure the requirements of the end application are met. I would anticipate that this requirement as well as the lack of any warnings or errors from the compiler would expose any issues with removal of this header file from your project.

    In short, I think that removal of the header file will be fine as long as you have the proper test coverage to insure you application is functioning  per your requirements.

  • Hello Chuck,

    Thank you for your reply and your thought.

    I will remove 'string.h' from our CCS project and test it.

    Best Regards,

    Satoshi Shinoha