- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 1884355_en-US
1884355_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
1884355_en-US
1884355_en-US
I am working on an S32G3 board and able to ping from u-boot to the PC connected.
However, it doesn't work the other way around.
Using pfe2 device
host 192.168.19.5 is alive
=> ping 192.168.19.5
Using pfe2 device
host 192.168.19.5 is alive
=> ping 192.168.19.5
Using pfe2 device
host 192.168.19.5 is alive
=> ping 192.168.19.5
Using pfe2 device
host 192.168.19.5 is alive
=> ping 192.168.19.5
Using pfe2 device
host 192.168.19.5 is alive
=> ping 192.168.19.5
Using pfe2 device
host 192.168.19.5 is alive
=> ping 192.168.19.5
Using pfe2 device
host 192.168.19.5 is alive
From the PC when I try to ping there is no response.
The icmp packet was sent on the correct interface as observed using Wireshark.
BSP-S32
@chenyin_h
Thanks for your response. Yes I also observed that u-boot responded to the ping requests received while u-boot was trying to ping the pc. It makes sense now.
Hello, @yeshasyesodharan
Thanks for the questions
It is correct for the results, u-boot only starts the network driver when it needs to use it (i.e. to send a ping). After it has finished the network driver is stopped. then Any traffic on the network will be ignored, as a result, no ICMP reply would be sent to the PC.
Best Regards
Chenyin