FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project.

[ClarkS]

I am attempting to follow this tutorial which explains how to use the Config tool with VSCode. . (https://community.nxp.com/t5/MCUXpresso-Training-Hub/MCUXpresso-for-VS-Code-Getting-started-with-Con...) 

Here' is how to quickly reproduce the problem I am having:

1. Install VS Code, the MCUXpresso extension, and the SDK for the MCXN947 board. (I'm running it on an intel iMac.) 

2. Import, built, and run the led_blinky example project. This works fine. 

3. From VSCode, right click on led_blinky and start using the config tool.

4. As soon as it opens, the Config tool is reporting many errors in Clocks and Pins. (around 20 errors). I'm new with NXP, MCUXpresso, and VSCode so I don't know how to proceed. 

I've searched the web for the errors I'm getting and haven't found anything useful.

Thank you for your help!

Also, I am very impressed with the MCUXpresso VS Code extension. You guys rock! And I'm pretty sure I will say the same thing about the Config tool once I learn it better. 

[ClarkS]

Well, this time it worked. You will see the screenshots above. 

I do see that your Configuration Overview does not show the errors that I am getting. I wish my Overview screen looked like yours does!

I don't know how to confirm Config tools is successfully installed. As far as I can tell, it appears to be working. I do get a Config Tools Overview screen which is similar to yours, but there are still a lot of difference. I hope when you see the differences between the Config Tools Overview screens, it will help you determine what is going wrong. In the mean time, I will uninstall my Config Tools program and reinstall it from your web site. 

[ClarkS]

@Celeste_Liu 

I deleted my Config Tools app, downloaded a new copy from your web site, deleted my led_blinky example, re-imported it from my repo, and relaunched the new copy of Config Tools. It still shows the errors. 

I did notice that the errors do not appear until I acknowledge a warning message complaining about the version of the configuration. I will attach two screen shots, the first one showing the warning message, and the second showing the next screen shot.

Do you get the version warning? If not, what would explain that? Are we using different led_blinky versions?

[Celeste_Liu]

Hello ClarkS,

On my end, there was indeed a version warning, but after I closed it, I didn't encounter any problems.

Let me list the versions of my tests:

Config Tools: v16.1

SDK: 24_12_00, SDK_2_16_100

I've tried the led_blinky in both versions of the SDK, and there were no issues.

BRs,

Celeste

[ClarkS]

@Celeste_Liu 

We have different versions of Config Tools. 

I have 24.12. You have 16.1. 

I got mine from here: https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools... 

Would you be able to test with the later version? 

My SDK is 24.12.10. You have both SDK: 24_12_00 and SDK_2_16_100.

When I import my repo for the MCXN947 board I see these two choices.

What's the difference between the two.? Which one should I select? I'm pretty sure I picked the 2nd one. 

Here is another view of my configuration. 

Thank you for your help!

Clark

[Celeste_Liu · Accepted solution]

Hello @ClarkS ,

Thanks for your information. I have tried the Config Tools v24.12. The problem you mentioned still hasn't occurred.

However, I've found that the SDKs we're using are indeed different. You're using the one from GitHub, while mine is from a local repository. I tried using the one from GitHub, but I keep failing to import it. So, I'm wondering if you could try the method of local import to see if it works.

1. Download the 24.12 SDK from Select Board | MCUXpresso SDK Builder

2. After the download is completed, place the SDK in the created directory C:\MCUXpresso_for_vscode. 

3. Select the "LOCAL ARCHIVE" method to import the repository.  

Choose "Import Repository" -> "LOCAL ARCHIVE" -> "Archive" -> "Browse", then locate the SDK folder downloaded from the SDK Builder. Select the built "SDK_24_12_00_FRDM - MCXN947". 

4. Create a new empty folder and name it "MCXN947". Click "Destination" -> "Browse" and select the newly created "MCXN947" folder. Then click "Import", and the SDK will be automatically imported.

5. Click "Import Example from Repository" to import the project "led_blinky" and create a new project.

 

Hope it can help you.

BRs,

Celeste

[ClarkS]

@Celeste_Liu 

Congratulations! The repo you advised me to obtain does not show any Config errors! Thank you for spending as much time as you did to help me with this problem! 

Is it always best to obtain archives from the SDK builder rather than Github? I'm pretty sure the IDE recommended Github. Perhaps it should recommend the SDK builder. 

Now I've got a lot to learn about how to use the Config tool. Right now It's pretty confusing to me. I've no doubt I'll figure it out pretty quickly now that you've solved this problem..

[ClarkS]

@Celeste_Liu 

I'm having trouble adding the screen shots. Whenever I do I get an error message below the CAPTCHA that says that verification failed. 

[Celeste_Liu]

Hello @ClarkS ,

Thank you for your interest in our products.

I have tried it on my end, but I haven't reproduced your problem.

The configuration tools can be opened normally.

I have checked the Quick Start Guide of the MCUXpresso configuration tools and found that it supports iMac.

Could you please confirm whether you have successfully installed the MCUXpresso configuration tools on your Intel iMac?

You can also send me a screenshot of the error message that appears when you try to open it.

BRs,

Celeste

[ClarkS]

I've added a couple screen shots. I've marked the various error related areas on each screen shot. 

Two types of errors are shown.

1. The Device Configuration error which seems to say the Config tool does not support the processor used on the MCNX947. I think I misunderstand the meaning of this error.

2. Missing driver errors.  I cannot find those drivers in my SDK repo. Maybe those file names (COMMON, PORTR, CLOCK, etc) are generic names and not actual file names. If that is the case, I have no idea how to find the actual file name, nor is it clear to me how to add drivers to the project using VS Code or the Config tool.