How to find out where a specific setting is made in DS 3.4 Config Tools

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

How to find out where a specific setting is made in DS 3.4 Config Tools

ソリューションへジャンプ
1,555件の閲覧回数
KevinInMadison
Contributor II

Hello All.

Is there a trick for finding out where specific #define values are set while using Config Tools?

I am currently trying to find MCU_PRECOMPILE_SUPPORT, but I a more interested in growing wheat, than being offered a loaf of bread. 

Thanks.

0 件の賞賛
返信
1 解決策
1,529件の閲覧回数
NamLee
NXP Employee
NXP Employee

One more point, with DS, the driver (that you've already installed) will be found here:

Namm_0-1705406496859.png

For some action / note in DS tool, it'll link to the components of DS. So it may important to look up sometimes (as my experience)

Namm_1-1705407732029.png

Thank you,

Nam.

 

元の投稿で解決策を見る

0 件の賞賛
返信
5 返答(返信)
1,524件の閲覧回数
KevinInMadison
Contributor II

Thank you Nam!  With that info, I now have it working as desired.  I did not understand the association between MCU_PRECOMPILE_SUPPORT and IMPLEMENTATION_CONFIG_VARIANT.  Thanks again.

0 件の賞賛
返信
1,529件の閲覧回数
NamLee
NXP Employee
NXP Employee

Hi KevinInMadison,

Sure.

You find where the code part / macro be generated. For example, MCU_PRECOMPILE_SUPPORT is in the Mcu_Cfg.h file. Then you find where it be generated. The generate file should be located in module MCU (for example) and in generate_PC (due to the PRECOMPILE macro)

Namm_0-1705404367811.png

It'll take time to understand, but quite easy, i think.

Parameter "IMPLEMENTATION_CONFIG_VARIANT" needs to be 'VariantPreCompile', which configured in .xdm file of module. As the MCU module, enter the Mcu.xdm inside the "config" folder.

Namm_2-1705405950907.png

To understand this, please refer to EB development doc

Namm_1-1705404533210.png

Here is where the param IMPLEMENTATION_CONFIG_VARIANT be configured.

Namm_4-1705406069445.png

By reading the EB doc, you will understand about this variable, be located in the Mcu module, which in general define.

You will get familiar with it after reading a while.

Check into the EB, you will find the component of this. And try to configure it.

If you're using DS, it may have some small differences but overall it's quite the same.

Please let me know if you have further questions.

Thank you,

Nam.

 

0 件の賞賛
返信
1,530件の閲覧回数
NamLee
NXP Employee
NXP Employee

One more point, with DS, the driver (that you've already installed) will be found here:

Namm_0-1705406496859.png

For some action / note in DS tool, it'll link to the components of DS. So it may important to look up sometimes (as my experience)

Namm_1-1705407732029.png

Thank you,

Nam.

 

0 件の賞賛
返信
1,520件の閲覧回数
KevinInMadison
Contributor II
Thank you Nam!  That solved my problem.  I did not understand the association between IMPLEMENTATION_CONFIG_VARIANT and MCU_PRECOMPILE_SUPPORT.  Thanks again.
0 件の賞賛
返信
1,509件の閲覧回数
NamLee
NXP Employee
NXP Employee

Hi,

The IMPLEMENTATION_CONFIG_VARIANT being used for the tool configuration, which will decides the value of MCU_PRECOMPILE_SUPPORT is STD_ON or STD_OFF.

MCU_PRECOMPILE_SUPPORT is macro be generated from tool, impact in C source code, and will be compiled by GCC to create .elf execution file for running.

Thank you,

Nam.

0 件の賞賛
返信