Other Parts Discussed in Thread: SYSCONFIG
Tool/software:
Hello TI,
I have a strange problem with the clock configuration in two projects. One is a custom project based off the empty_driverlib_project example. The second is the sci_ex3_echoback example project.
When configuring SCI there is a function call to SCI_setConfig().
The lspclkHz parameter for this function call is evaluated differently in the two projects.
In the empty_driverlib_project DEVICE_LSPCLK_FREQ evaluates to (((10000000 * 24) / (1 * 1 * 2)) / 2) => 60000000. This evaluation is incorrect and will improperly set the baudrate. So running the example at 38400 with the incorrect DEVICE_LSPCLK_FREQ will force a baudrate of 19200.
In the sci_ex3_echoback example the clock configuration evaluates to (((10000000 * 48) / (1 * 4 * 1)) / 4) => 30000000. This evaluation is correct and will work properly.
The problem I am running into is how DEVICE_LSPCLK_FREQ is set.
In the empty_driverlib_project the clock is configured with the SysConfig utility, and in the sci_ex3_echoback example the clock configuration is configured a different way without the SysConfig tool as the c2000.syscfg file is blank.
How do I correct the clock configuration in the empty_driverlib_project so it has the correct clock configuration?
The c2000.SysCfg config file for the empty_driverlib_project is attached.
/**
* 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 --device "F280013x" --part "F280013x_64PM" --package "64PM" --context "system" --product "C2000WARE@6.00.00.00"
* @v2CliArgs --device "TMS320F2800137" --package "64PM" --context "system" --product "C2000WARE@6.00.00.00"
* @versions {"tool":"1.24.0+4110"}
*/
Thanks,
Allan
