2363182_en-US

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

2363182_en-US

2363182_en-US

Migration Guide of NXP-NCI 2.0 SPI examples with PN7160 for MCXW23 in Visual Studio Code

Hi NXP,

First of all, thank you to Roman @RomanVRfor providing the migration guide for frdm-mcxw71 with pn7160:
NXP Community Migration Guide

It would be very helpful if there could also be a guide specifically for using the NXP-NCI driver with Visual Studio Code on the MCXW23 platform. Unfortunately, the MCXW23 currently does not have support in MCUXpresso IDE, so many developers are using Visual Studio Code instead.

A dedicated setup and migration guide for PN7160 SPI integration, driver configuration, SDK setup, and build/debug workflow in Visual Studio Code would greatly help developers working with visual studio code with nxp-nci 2.0 driver.

mcxw23 with pn7160.jpg

Best Regards,

Shakir Salam

Development BoardFRDM-TrainingRe: Migration Guide of NXP-NCI 2.0 SPI examples with PN7160 for MCXW23 in Visual Studio Code

Hello @S_Salam555, hope you are doing well.

Thank you for your feedback, however there is currently no guide that covers the migration on MCUXpresso for VS Code.

Although, the guide done in MCUXpresso IDE should provide the overall essential steps to do the migration, the only steps that change are the ones that imply file addition and manipulation of your project, which in VS Code should be done via CMake files as stated on the following guide: Add Files to Project/ Remove Files from Project.

Hope this helps!

Re: Migration Guide of NXP-NCI 2.0 SPI examples with PN7160 for MCXW23 in Visual Studio Code

Hello @S_Salam555.

The option that you have selected is the appropriate for the port.


Re: Migration Guide of NXP-NCI 2.0 SPI examples with PN7160 for MCXW23 in Visual Studio Code

Hi Roman,

Thank you for the feedback and the information.

Regarding the Manage Component section, could you please advise which option I should choose? This is currently my project structure for reference. No Rush :))

Best regards,
Shakir Salam


spi_config.jpgmcuxpresso.jpg

Re: Migration Guide of NXP-NCI 2.0 SPI examples with PN7160 for MCXW23 in Visual Studio Code

Hi @S_Salam555.

Since this is a custom implementation, the support path would be very limited to analyze specific behaviors or issues within your implementation, therefore all of the development would have to be on your own.

Providing a more specific approach to the behavior that you are observing would be very helpful to be able to provide a better support.

Re: Migration Guide of NXP-NCI 2.0 SPI examples with PN7160 for MCXW23 in Visual Studio Code

Hello Roman,

Hope you’re doing well. Thank you for the suggestion.

How does my CMake configuration look so far?

Below is an overall visual illustration of my project structure for the MCXW23 build.

Best regards,
Shakir Salam

1. Board.h

board_h.jpg

2. hardware_init.c

hardware_init_c.jpg

3. pinmux.c

pinmux_c.jpg

pinmux_c_2.jpg

pinmux_c_3.jpg

4. tml.c

tml_c_1.jpg

tml_c_2.jpg

tml_c_3.jpg

tml_c_4.jpg

5. main.c

main.c.jpg

6. CMakeLists.txt 

cmake_1.jpg

cmake_2.jpg

7. Build Error Output

cmake.jpg

Re: Migration Guide of NXP-NCI 2.0 SPI examples with PN7160 for MCXW23 in Visual Studio Code

Hi Roman,

Just wanted to share a quick progress update. I’m able to successfully build the project, and now I just need to configure the correct SPI settings.

I’ve attached the latest CMakeLists.txt and the error console log for your reference.

Best regards,
Shakir Salam

cmake.txt.jpg

console.jpg

Re: Migration Guide of NXP-NCI 2.0 SPI examples with PN7160 for MCXW23 in Visual Studio Code

Hello @S_Salam555, thank you for the update.

Please notice that the SPI driver name changes between the MCXW71 and MCXW23, while MCXW71 SPI driver APIs are called "LPSPI....", on MCXW23 the APIs and instances are just called "SPI....".

Hope this helps!

Tags (1)
No ratings
Version history
Last update:
Saturday
Updated by: