Hello,
Since MDK 5.35, Xtal is greyed out as <undefined> in Options for target -> Target.
There was no problem in the version 5.33.
How do you set the value of the external oscillator?
Thank you.
5.34 is also OK. I don't have 5.35.
Yes but with the evaluation version it is not possible to download the previous versions...
I was just supplying the information for completeness (bug tracking), I wasn't suggesting a downgrade.
Sorry. Thank you for your contribution.
FYI, this value is only used for the On-PC Simulation - if you are debugging on hardware this value is not used.
It looks like you are using this device in your project:
www.keil.com/.../4231.htm
Do you have the Legacy support PACK for Arm Cortex-M devices (v 5.25) installed on your PC? See
www2.keil.com/.../legacy
If so, does this project work for you?
C:\Keil_v5\ARM\Examples\Blinky\Blinky.uvproj
(I assume your test project hass a .uvproj, not uvprojx extension)
===============
As a workaround, there are Virtual Simulation Registers (VTREGs) called XTAL
www.keil.com/.../uv4_db_exp_periphlvar.htm
It initially gets populated by the value on the Project -> Options For Target -> Target tab.
When debugging, from the command window
www.keil.com/.../uv4_db_dbg_outputwin.htm
Type
> XTAL
...to see the current value.
To Change the XTAL value, type
> XTAL=0x00999999
See also:
community.arm.com/.../what-does-the-xtal-directive-really-mean