• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 32 subscribers
  • Views 333 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.

TMDSCNCD263: WDT SysConfig GUI vs CLI inconsistencies

Tobias Jäggi
Prodigy 50 points

Part Number: TMDSCNCD263
Other Parts Discussed in Thread: SYSCONFIG

In SysConfig GUI, I configured the WDT Input Clock frequency to 10 MHz.
The GUI does not report any error and generates code.

Using the same .syscfg file with SysConfig CLI to generate code fails. The CLI tool reports WDT input clock frequecy to be 100MHz, 10x more than what was configured in the GUI. As a result, the expirationTime is not within the required interval, thus code generation fails.

I used

  • AM263Px control card
  • SysConfig 1.25.0
  • MCU+ SDK for AM263P 11.0.0.19

 

wdt_config.png

clock_tree.png

tobi@fedora ~/D/syscfg_testing> ~/ti/sysconfig_1.25.0/sysconfig_cli.sh --script test.syscfg --context r5fss0-1 --output generated --product ~/ti/mcu_plus_sdk_am263x_11_00_00_19/.metadata/product.json --part AM263x --package ZCZ --compiler ticlang
Running script...
Validating...
error: CONFIG_WDT0(/drivers/watchdog/watchdog) expirationTime: (Expiration time * WDT input clock frequency) = 100000000 has to be within 8192 to 33554432
1 error(s), 0 warning(s)
  • 0
    TI__Mastermind 33633 points

    Hello,

    This thread has been assigned to the expert for further review and action. Please note that our team's response times may be slower than usual due to the holiday season. We will get back to you as soon as possible and appreciate your understanding in this matter.
    Thank you for your inquiry and we look forward to assisting you soon.

    Best regards,
    Zackary Fleenor

  • 0
    TI__Mastermind 23102 points

    Hi,

    Let me try to reproduce this and get back

    Regards,
    Shaunak

  • 0 in reply to Shaunak Deshpande
    Prodigy 50 points

    Hi Shaunak,
    Here is the syscfg file i used:

    /**
 * These arguments were used when this file was generated. They will be automatically applied on subsequent loads
 * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments.
 * @cliArgs --board "/board/am263x-cc" --device "AM263x_beta" --part "AM263x" --package "ZCZ" --context "r5fss0-0" --product "MCU_PLUS_SDK_AM263x@11.00.00"
 * @v2CliArgs --board "/board/am263x-cc" --device "AM2634" --package "NFBGA (ZCZ)" --context "r5fss0-0" --product "MCU_PLUS_SDK_AM263x@11.00.00"
 * @versions {"tool":"1.25.0+4268"}
 */

/**
 * Import the modules used in this configuration.
 */
const watchdog  = scripting.addModule("/drivers/watchdog/watchdog", {}, false);
const watchdog1 = watchdog.addInstance();

/**
 * Write custom configuration values to the imported modules.
 */
const mux41       = system.clockTree["WDT0_CLK_GCM_CLKSRC_SEL"];
mux41.inputSelect = "RCCLK10M";

watchdog1.$name          = "CONFIG_WDT0";
watchdog1.expirationTime = 500;

  • +1 in reply to Tobias Jäggi
    TI__Mastermind 23102 points

    Hi Tobias,

    I used your syscfg above and tried running the syscfg-cli build:

    I don't see any errors.

    Do you see errors even with standard SDK examples? Or those just build fine with syscfg-cli (i tried these and they worked too).

    Regards,
    Shaunak

  • 0 in reply to Shaunak Deshpande
    Prodigy 50 points

    Hi Shaunak
    With your screenshots, I figured out that I used the wrong argument for the --context flag. The sysconfig file was setup for r5fss0-0 but i specified r5fss0-1 when calling syscfg-cli. With the correct --context flag it works.
    Thank you for your help!