KDS ,fsl_clock_manager ,code not generated for any "device specific" and "common" methods

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

KDS ,fsl_clock_manager ,code not generated for any "device specific" and "common" methods

2,049 Views
diegocolombo
Contributor IV

Hi
please can you check what could be wrong?

i'm using MKV11 with KDS with KSDK 1.3.0 

the fsl_clock_manager component works and generates code ,for example
CLOCK_HAL_GetFtmFixFreqClkSrc  is present

Instead,the generated code of any method in "device" or "common" folder is missing

in Properties->ProcessorExpert->Kinetis SDK Specific Options the Library Modes flags "platform_lib" and "startup_lib" are flagged
ksdk_statrtup_lib_KV11Z7 is present and compiled in workspace and its "\debug" folder path was added
in Library  search path.

Thanks for your help or time
Diego

Path startup libraries.png


 

Tags (2)
0 Kudos
2 Replies

1,865 Views
diegocolombo
Contributor IV

Hello Vicente.
In years i neved had the time to learn it properly.I've tried,but i was not able to obtain much from MCUXpresso,so i got back to KDS ,being aware that KDS is considered old,if not obsolete .
Just an example, using MCUXpresso with a very small processor as MKL03Z8 ,shows that there is not a peripheral configuration tool(it exists in KDS),and the code generated for an almost empty project almost fills the available Flash.


Have a nice weekend

Diego

0 Kudos

2,023 Views
vicentegomez
NXP TechSupport
NXP TechSupport

Would be possible that you move to MCUXpresso?

 

regards

Vicente 

0 Kudos