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.

Issue with new version of HALCoGen 04.03.00

Other Parts Discussed in Thread: HALCOGEN

Hi,

I saw that the new release of HALCoGen (04.03.00) includes support of FreeRTOS source code generation.

Unfortunately I tried to recompile my project with it and it did not work.

After investigating, there are some bad initialization variables in the file TMS570LS1224PGE_FREERTOS.cnf

Actual values:

VAR.FLASH_BANK_LINK_BASE_ADDRESS_0.DEFAULT=0x00000020

VAR.FLASH_BANK_LINK_LENGTH_0.DEFAULT=0x0013FFE0

Correct values:

VAR.FLASH_BANK_LINK_BASE_ADDRESS_0.DEFAULT=0x00008020

VAR.FLASH_BANK_LINK_LENGTH_0.DEFAULT=0x00137FE0

  • Hi Eddy,
    where did you find 04.03.00?? I only see 04.02.00 when I open the HALCoGen page. :O

    Kind regards,
    Lars von Wachenfeldt
  • They may not have posted it yet... but you should be able to check for updates from within Halcogen (under help) or run the check yourself, located somewhere like

    C:\ti\Hercules\HALCoGen\v04.02.00\HCG_updater.exe

    David
  • One of our Halcogen folks will help you with this.
  • Hi Eddy,

    We put it on Hold, since there will be 4.03.01 release coming soon.

    4.03.00 had a compile error for two of our devices(TMS570LC4357ZWT and RM57L843ZWT) due to HALCoGen Engine issue.

    If you already have 4.02.00 Installed in your PC, when you open 4.02.00 it will popup for the update 4.03.00 download, you can download and Install. 

  • Hi Prathap,

    Do not forget to verify the TMS570LS1224PGE with FreeRTOS, as it does not generate a code that can be compiled.
    It need the modifications I wrote in my initial post.
    All this thanks to Anthony F. Seely who initially modified HALCoGen configuration files in order to generate a FreeRTOS compliant version.
    BTW, I love your tools. Powerful and easy.

    Regards,

    Eddy
  • Hi Eddy,

    Yes we are aware and already taken care. This is the main reason our web release was put on Hold 4.03.00.
    Unfortunately Autoupdate uses an other Server drop, This time by mistake it was pushed during testing. We know why it happened and taken necessary steps to avoid such scenarios in future.

    Thanks for the feedback!
  • Thanks for the reply prathap.

    Eddy, can you pls close this thread if prathap had answered you questions. Thanks.