• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 32 subscribers
  • Views 1816 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 3.01.01 have many Problems

Rolf Timm
Prodigy 60 points

Other Parts Discussed in Thread: HALCOGEN

Hi,

I use the The HalCoGen 2.11 and 3.00.01 and now the 3.01.01. The update from HalCoGen 3.00.01 to 3.01.01 have a lot Problemes.

The Notivication.c is not good, the "while(1);" is a great Problem, when I change this in "return;" and "generated code" new the write the same "while(1);" in the code, this is poor.

Next problem is "_memoryInit_" is defined in sys_memory.asm without parameters, when I compile the project is the "_memoryInit_" the double defined, in the sys_memory module and in the sys_selfttest module.

Then I create the GCM become I the windows with VCLK1 and VCLK2 is the zero! and the VCLK1 Config and VCLK2 Config can't change? ups? Look in HalCoGen 3.00.01 is the VCLK's adjustment correct.

Can Your fixed this Problem? please betimes

Your HalCoGen is amazing, just important function lost such as those DMA....

Best Regards

Rolf Timm

  • 0
    TI__Intellectual 1325 points

    Hello Rolf,

    Thanks for posting. I am forwarding this to our HalCoGen expert who can comment on this.

    Best regards,

    TI Forum Support

  • 0 in reply to Diwakar Bansal
    Prodigy 60 points

    Hi,

    I have reconize the third Error, hi generated by transfer from project from HalCoGen Version 3.00.01 to Version 3.01.01. Solution is create new project in the HalCoGen Version 3.01.01 and import the Dil-file in the project or make the same adjustments in the project and the VCLK 1 +2 is correct.

    The same reson is for the error with "_memoryInit_", when create new project in the HalCoGen Version 3.01.01 dont no exist this error.

     Only, the error with "while(1)" in the "notification.c", when new generated code.

    Best regards

    Rolf Timm

     

     

  • 0 in reply to Rolf Timm
    TI__Genius 14205 points

    Hi Rolf,

    Issue 1:

    Thanks for using HALCoGen, Your problems are caused due to the pjt portability from 3.00.01 to 03.01.01.
    There are close to 10 Parameters in total which has this portability problems. See the attached XLS which has the list,6204.HCG_PJT_Incompatibility_Analysis&Solution.xlsx

    Two ways to address this,
    1) Create new project in 3.01.01 and redo the GUI setting you made on 03.00.01. ( I will recommend this) 
    2) Open the DIL file and do the changes as mentioned in the XLS sheet attached.  

    By default these issues are addressed already in upcoming 03.02.00 release planned Mid Sep. Any version 3.x Pjt can be ported to latest HALCoGen.

    Issue 2: 
    - notification.c must be provided by the User, the one generated by HALCoGen is for reference, since it is application dependent. While(1) is placed to warn users that this function is to be replaced, Since many users wants to use notification.c our next version will have the while(1) removed and the user must take care of servicing it correctly. In Earlier version of HALCoGen we never provided notification.c. 

    Regards

    Prathap

  • 0 in reply to Prathap
    Prodigy 60 points

    Hi Prathap,

    Thanks for Your immediate answer.

    To issue 1, I do on this way.

    To issue 2, to allusion in the sourcecode from notification.c should be under the name from interrupt one

    /* USER CODE BEGIN (1) */

    /* USER CODE END */  be included. The user can insert around the while(1) one #ifdef(0) and #endif, this bracket the while(1) out and by next generated the code no change this effect.

    I'm looking forward to next Version from HalCoGen.

     

    Best regards

    Rolf Timm

  • 0 in reply to Rolf Timm
    TI__Genius 14205 points

    Hi Rolf,

    On notification.c I understand your problem, but TI strongly recommends User to provide notification functions. The one generated by HALCoGen is for reference only.As I mentioned while(1) in notification functions will be removed from next version.

    Best Regards
    Prathap