zhhyu7 commented on PR #18011:
URL: https://github.com/apache/nuttx/pull/18011#issuecomment-3782818891

   > @zhhyu7 I just tried this commit and the one before but compared to NuttX 
12.12 the network regressed competely where it's not working anymore on the NXP 
i.MXRT.
   > 
   > ```
   > eth0    Link encap:Ethernet HWaddr 0a:0e:82:92:b3:7f at UP mtu 1504
   >         inet addr:192.168.2.133 DRaddr:192.168.2.1 Mask:255.255.255.0
   > 
   > can0    Link encap:UNSPEC at DOWN mtu 72
   >         inet addr:0.0.0.0 DRaddr:0.0.0.0 Mask:0.0.0.0
   > 
   > can1    Link encap:UNSPEC at DOWN mtu 72
   >         inet addr:0.0.0.0 DRaddr:0.0.0.0 Mask:0.0.0.0
   > 
   > can2    Link encap:UNSPEC at DOWN mtu 72
   >         inet addr:0.0.0.0 DRaddr:0.0.0.0 Mask:0.0.0.0
   > 
   >              IPv4   TCP   UDP  ICMP CAN
   > Received     0002  0000  0002  0000  0000
   > Dropped      0000  0000  0000  0000  0000
   >   IPv4        VHL: 0000   Frg: 0000
   >   Checksum   0000  0000  0000  ----  ----
   >   TCP         ACK: 0000   SYN: 0000
   >               RST: 0000  0000
   >   Type       0000  ----  ----  0000  ----
   > Sent         0000  0000  0000  0000  0000
   >   Rexmit     ----  0000  ----  ----  ----
   > nsh> arp_send: ERROR: Unreachable: ff02a8c0
   > psock_udp_sendto: ERROR: Not reachable
   > arp_send: ERROR: Unreachable: ff02a8c0
   > psock_udp_sendto: ERROR: Not reachable
   > arp_send: ERROR: Unreachable: ff02a8c0
   > psock_udp_sendto: ERROR: Not reachable
   > arp_send: ERROR: Unreachable: ff02a8c0
   > ```
   
   eth0    Link encap:Ethernet HWaddr 0a:0e:82:92:b3:7f at **UP** mtu 1504
   
   @PetervdPerk-NXP It seems to be related to the network card not entering the 
RUNNING state, the protocol stack will check the RUNNING flag when selecting 
the sending network card.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to