• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 804 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.

AM6442: SYSconfig : how to modify generated files in MCU SDK

Colombo Carlo
Mastermind 24070 points
Part Number: AM6442
Other Parts Discussed in Thread: SYSCONFIG

Hi Everybody , 

I m using  gpio_led_blink_am64x-evm_m4fss0-0_nortos_ti-arm-clang    to understand and work on the MUC side .

now  I m  using SYSconfig   and ideally would like to create file then be able to modify ( imagine I have my repository separated in the future and not maybe even not using CCS once code / files generated ).

     Questions : Files generated  looks to be locked  by SYSCONFIG    :  how could you edit  ?     these files  seem to be locked , I can edit but when compile modifications are lost  ( like SYSconfig is cleaning them up )

   thank you 

BR
Carlo

  • 0
    TI__Genius 9101 points

    Few options, depending on if you are using SysConfig from CCS project or makefile

    Option 1: Use SysConfig to generate code by adding modules and configuring them, but once done copy the generated code lines to your file and remove the module from sysconfig. This way you can use SysConfig more as a code snippet generator. However wherever you feel you can use the generate code without modification, leave the module in the syscfg. This will be convenient to change the module config in future.via SysCfg. Note, adding a module generates code in multiples files to check each file to see what code a module addition generated

    Option 2: Generate all the code, and then stop sysconfig invocation in the project as below.

    when using SysConfig, remove the .syscfg file from CCS project and add the SysConfig generated .c files to the CCS project.

    Now the files wont be generated again and you can safely modify them

    When using makefile, comment the below to stop invocation of syscfg and therefore stop generation of code files.

    syscfg: ../example.syscfg
    #    @echo Generating SysConfig files ...
    #    $(SYSCFG_NODE) $(SYSCFG_CLI_PATH)/dist/cli.js --product $(SYSCFG_SDKPRODUCT) --context r5fss0-1 --part Default --package ALV --output generated/ ../example.syscfg