- 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
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- Wireless Connectivity
- 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
-
- 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
- MCUXpresso Training Hub
-
- 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
-
I had a very difficult time getting my lwIP application to work. It took a little bit of luck in addition to great help from Marek Neuzil in my thread Assistance needed with lwIP + PEx + KSDK to get it actually working.
The problem is, with the release of KDS 3.0 and KSDK 1.2, I had to create my project from scratch, and after following what I believe to be the same steps, my application does not work again.
The basic steps include:
- adding MQX and setting it to MQX Standard
- disabling DbgCs1 and adding a new fsl_uart shared component to MQX
- assigning fsl_uart to a random UART I don't need (as I am using semihosting)
- assigning pins to the ENET component in pin_init
- setting the RMII_MDIO pin to open drain, pulled up, and enabled
- adding the necessary header file include directories
- adding a link to fsl_phy_driver.c to my Source folder
(hopefully I didn't miss anything above)
Even after going through all of those steps again, my lwIP application runs and waits for an incoming connection, verified by single stepping through each line and checking for unhandled returned errors. It all checks out fine, but I still cannot ping or connect. However, the lwip demo application that comes with KSDK 1.2 works just fine.
Can anyone offer any assistance or advise? I've also attached my sample project here. Thank you!
Original Attachment has been moved to: KDS3_lwip_mqx_pex_test.zip
已解决！ 转到解答。
I'm closing this question for now. I'm not 100% sure of what the issue was, but the hardfault I was originally encountering was solved by increasing the TCP task's stack size. I would love to learn how to debug this properly, rather than guessing at solutions and being happy when everything starts working.
I'm closing this question for now. I'm not 100% sure of what the issue was, but the hardfault I was originally encountering was solved by increasing the TCP task's stack size. I would love to learn how to debug this properly, rather than guessing at solutions and being happy when everything starts working.
MarekNeuzil by any chance would you be able to look at my project and see if there's anything missing this time around? This is a port of my lwIP / KDS2 / KSDK 1.1 project that was working. Thank you!
