FRDM-MCXN947 Ethernet Wired Connectivity

[Fpetersen]

Greetings, I'm new with NXP development Kits and I've trying to understand it better.  Since I'm new, I've been using the examples from the Application Hub and I most of the times don't even change it. Well let's get to the point, I've been trying to enable the interface of a shield (NAFE13388) but nothing works. Here is the link from application hub of NAFE13388 universal analog sensing module with wired connectivity:   https://mcuxpresso.nxp.com/appcodehub?_gl=1*vpq9re*_ga*NzgzOTM2MjAxLjE3NjMxNDQ2MjY.*_ga_WM5LE0KMSH*c...

I followed the tutorial step by step but the computer never recognized the FRDM-MCXN947 ethernet port, I tried to ping it, tried to see if the ip address appeared in the CMD, but it never worked, even when I tried to use a router the computer wouldn't recognized it. The terminal in the IDE always showed normally:

Transport: Network (TCP/IP)
NAFE device PN: 13388b40, rev. c2   NAFE device SN:   7f5c60521b
Static IP address configured for board:
IP address: 192.168.0.2
   Netmask: 255.255.255.0
   Gateway: 192.168.0.1
Initializing PHY...
Link UP."                  

If I tried to change the IP address in the app.h it would change in the terminal and link it up, but never get recognized by the computer. I tried to use another code to see if it was a code problem (I used frdmmcxn947_lwip_ping_freertos_cm33 that is from sdk examples) and had the same issue. There was no physical problem since the sensors would work when I tried other examples by delivering messages by the serial and the ethernet cables were working just fine. I don't know if it as problem with the board itself or it's me. But I would be very thankful if someone could help me with that 

[RomanVR]

Hello @Fpetersen, hope you are doing well.

I have tried the "frdmmcxn947_lwip_ping_freertos_cm33" example from the SDK (version 25.09 and MCUXpresso 25.6.136) and it worked properly, as I received in my computer the pings from the FRDM board. Could you please share the steps that you followed in order to test the ping example?

[Fpetersen]

Hello, how are you today??

Well, I followed the normal steps, I imported the example from the MCUXpresso as a SDK example, connected the USB Cable and the ethernet Cable. Built the project and debugged, sent to the board and got in the terminal the normal message:
************************************************
PING example
************************************************
IPv4 Address : 192.168.0.102
IPv4 Subnet mask : 255.255.255.0
IPv4 Gateway : 192.168.0.1
************************************************
ping: send 192.168.0.1
ping: send 192.168.0.1

Turned off my Wifi board (Thinking that maybe was the problem) and set a static IP in the ethernet board on the computer to receive the IPV4 from the NXP board, and didn't matter how many times I ping or if I tried to change the IPV4 address from the NXP board, it always got the  same message from CMD: "Destination host unreachable" or "timed out", tried the same board with another computer but got the same results 

[RomanVR]

Hello @Fpetersen, I'm doing good, thank you.

Could you please also share with me which MCUXpresso and SDK you are using? Additionally, since the "frdmmcxn947_lwip_ping_freertos_cm33" example is meant to be used with static IP assignment, could you please confirm if you are setting your PC IP to the one used in the example and the subnet mask to "255.255.255.0"?

If you have not changed your PC IP and subnet mask, please try by changing these parameters. If you have changed them, please try to do a mass erase (you should be able to do it in MCUXpresso with the GUI Flash Tool) and let me know if the behavior persists.

[Fpetersen]

Hello, nice to read that you have been doing well @RomanVR , I'm glad!

Well for your questions, I've been using the MCUXpresso IDE v25.6.136 and the sdk is SDK_2x._FRDM-MCXN947 v25.9.000 . Yes im using the subnet mask as  you told "255.255.255.0" and for the board from frdm IP I'm letting the standard from the code as the one, but for the board in the computer I'm chaging to put as 192.168.0.200 to not ping the PC board by mistake instead of ping the FRDM board. 
I did check the mass erase as you asked, It was already selected, so that its not the problem and the behavior does persist, I sent some prints from my screen (As you can see I'm also using CMD as adm) 

[Fpetersen]

Sorry, just said something wrong and I don't wanna to make things more confusing, the FRDM board is the 192.168.0.200 (I change it to try to see if the ip was the problem, but it has the same result if it was 192.168.0.102) and the computer board ethernet is 192.168.0.100 (and the ehternet computer works by cable so thats not a port problem) sorry for the mistake @RomanVR

[RomanVR]

Hello @Fpetersen, no problem at all!

I'm not being able to reproduce your issue, I have tried also changing the FRDM IP to yours (192.168.1.200) and I also see that in your serial terminal, you are pinging to an IP 192.168.1.1, however you told me that you configured your computer to 192.168.1.100.

Could you please help me to confirm that you are setting your computer static IP properly as well as your subnet mask? Also, is there any possibility of having a firewall that may be blocking the communication?

[Fpetersen]

Thank you for being so kind!! Sorry for the delay, I changed my windows language to help you out too. Maybe send you that prints in portuguese would not helpful 

As for IP, I changed mine to exactly the same as yours in the last message and couldn't find it in CMD commands as ping or arp -a. As you can see also sent in my prints I tried it offline and didn't work. I sent the screenshot of my static configuration and for last I don't think would be firewall problem since I used in two different computers who doesn't have the same configuration nor the same intention as how to be used, so both of them are not related.

I'm starting to think that maybe is a faulty part, I really don't know how to progress. 

And thank you for being patient and for the assistance!! @RomanVR 
Best wishes!

[RomanVR]

Hi @Fpetersen, thank you too for your collaboration.

Could you please help me by importing again the ping example to your workspace just to have a clean example with no modifications and load it to the board? I'll share with you the procedure I followed to run the example:

1. Imported the frdmmcxn947_lwip_ping_freertos_cm3 example from the SDK.
2. Built and flashed the example to the board.
3. Changed testing PC's IP to static 192.168.1.100 and the subnet mask to 255.255.255.0
4. Checked and disabled for any firewall limitation.
5. Connected the Ethernet cable and waited for PC to identify the connection.
6. Received pings from the board and was able to ping the board by cmd.

Additionally, do you happen have another FRDM board to test the example with? Just to discard any issue with the current board.

[Fpetersen]

Sorry for the late response, I forgot my notebook at work and everything was there

Answering your last message, I tried to reinstall everything and tried it out the way you said to do. I got the same results as you can see from the prints. I disable my wifi board and the ethernet board says "unidentified network" but it recognize the board (the one inside the computer) and the ping is fine. Still, the frdm doesn't seems to work at all and I don't have another similar to this one, maybe the board is the problem???

Thank you for your patience, 
best regards

[RomanVR]

Hello @Fpetersen.

It is an expected behavior for the board to appear as an "Unidentified Network" when connected to the PC.

Could you please share a detailed picture of your FRDM board? The purpose of this picture is to check the jumper configuration and other details that may be causing this issue.

[Fpetersen]

Surely, I took some random pictures and if you want more just tell me

thank you for the support!!

[RomanVR]

Hi @Fpetersen, hope you are doing well.

I have seen your images and everything seems in order within the board. Could you please help us by testing the example on a personal PC? Since all of the tests done on our side have been generating the proper results.

Please let me know if you are able to do these tests.

[Fpetersen]

Hello @RomanVR, sorry for my late response, the end of the year was kinda messy

Well, I tried in my personal PC, even formatted it, but still the same problems, I guess maybe the board came faulty. I thank you a lot for the help and all the test you made! It made me understand even better the board and coding, but sadly it was just not meant to work. 

I hope you have a great year and we maybe see each other another time,
My Greatest Regards,
Felipe