MCUXpresso Config Tools - Keil - Multiple Target

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

MCUXpresso Config Tools - Keil - Multiple Target

1,733件の閲覧回数
EnzoBonnard
Contributor I

Hi,

I've created a "Multi-Projects" with Keil µVision 5, each "Project Targets" correspond to a specific package of a LPC54606 mcu. In the project folder I want a specific MCUXpresso Config Tools file (.mex) which match each "Project Targets" (so each package of the LPC54606 mcu).

Is it possible, if yes how to do it ?

Best regards

Enzo Bonnard

0 件の賞賛
返信
5 返答(返信)

1,699件の閲覧回数
EnzoBonnard
Contributor I

Hi,

Sure, I can ask to Keil support too.

In fact, I've tryed to implement 2 .mex file in the my Keil folder project, and it didn't work because of 2 two reasons :

-> the .mex file which match the target (LPC54606BD100) created for the first time work well, but with the second .mex file which match the target (LPC54606BD208) created for the second time, I've got this error from MCUXpresso Config Tools :

EnzoBonnard_0-1689060491244.png

And if I open the .uvprojx of my project (file that describe the MDK uVision project) the first target declared in the <Target> tag is the LPC54606J512BD100 :

EnzoBonnard_1-1689060884042.png

The LPC54606J512BD208 is declared in a second <Target> tag later in the file.

I think the MCUXpresso Config Tools don't check for the complete .uvprojx file but only for the first <Target> tag found...

 

-> The second issue is also with the second .mex file (the first one works properly). When I try to update the code with MCUXpresso Config Tools I can see the path of the file it trying to update : 

EnzoBonnard_2-1689061513985.png

For the clock the path is good (.\RTE\Board_Support\LPC54606J512BD208) but for the Pins and Peripherals it's the wrong one...

So there's a way to override these 2 issues ?

Best regards

Enzo Bonnard

0 件の賞賛
返信

1,685件の閲覧回数
ZhangJennie
NXP TechSupport
NXP TechSupport

Hi

Could you please provide the detailed steps of how to produce this error in configuration tool?

ZhangJennie_1-1689153305067.png

What's the configuration tool version?

Thanks,

Jun Zhang

 

0 件の賞賛
返信

1,675件の閲覧回数
EnzoBonnard
Contributor I

Hi,

Step 1 : Create a Keil project under uVision5. Create a project target named "LPC54606J512BD100 Release" for LPC54606J512BD100 MCU => OK

Step 2 : Create LPC54606J512BD100.mex and save it in the Keil project folder. When modifying LPC54606J512BD100.mex with MCUXpresso Config Tools synchronization with clock_config.h, peripherals.h, pin_mux.h,... (path : .\RTE\Board_Support\LPC54606J512BD100) is working => OK

Step 3 : Create a project target named "LPC54606J512BD208 Release" for LPC54606J512BD208 MCU => OK

Step 4 : Create LPC54606J512BD208.mex and save it in the Keil project folder. When modifying LPC54606J512BD208.mex with MCUXpresso Config Tools synchronization with clock_config.h, peripherals.h, pin_mux.h,... (path : .\RTE\Board_Support\LPC54606J512BD208) is NOT working and this error appear => NOK

 

MCUXpresso Config Tools Version 13.1

 

Best regards

Enzo Bonnard

0 件の賞賛
返信

1,639件の閲覧回数
ZhangJennie
NXP TechSupport
NXP TechSupport

So the error is produced by Keil IDE, right?

Did you check with Keil ? Can Keil IDE correctly identify mex file in different target?

0 件の賞賛
返信

1,712件の閲覧回数
ZhangJennie
NXP TechSupport
NXP TechSupport

Hi EnzoBonnard 

This is more a Keil IDE function query. I suggest you contacting Keil support forum

https://community.arm.com/support-forums/f/keil-forum

Thanks,

Jun Zhang

0 件の賞賛
返信