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 USER CODE BEGIN failure

Other Parts Discussed in Thread: HALCOGEN

Hello HalCoGen-Team

I have just installed and generated code with the newest version of HalCogen v. 3.06.00

Unfortunately it through away some of my USER CODE!!!

In the file sys_startup.c I had in my previous version of HalCoGen the USER CODE BEGIN (76)

In the newest version (76) does not exist in this file and all my code from the old (76) is not included!

I have seen the same problem more places in the generated code! This is a NO GO as our code is thrown away or is moved.

Please do not throw away or move user numbers!

Best regards
   Michael c".)

  • Michael,

    Thanks for this feedback and sorry for your difficult experience.

    I'm assigning this thread to the halcogen team lead for a response.

  • Hi Michael

    Sorry for the inconvenience caused.

    There are couple of changes in HALCoGen driver code after MISRA fix and code review. You may also notice that selftest and startup code has changed quite a bit.

    We overlooked sys_startup.c and this one usercode slipped through our test. Unfortunately there is no workaround other than manual copy. 

    But Selftest.c is completely new and we recommend all customers to use this version since it has more bug fixes and code clarity.

    You should not see any issue with other driver files.

    Again sorry for the inconvenience, please do let us know if you need our help. 

    Regards
    Prathap

  • Hello Prathap,

    Thank you  for your quick response.

    HalCoGen is great tool that I have missed so many times on other processors.

    Just to inform you and other users of the forum, I can see that the following files has changed some USER-CODE-numbers to:
    emif.c
    i2c.c
    spi.c

    My code is up working again, - no harm done but some debug and looking through the version control system.

    Best regards

        Michael c".)