- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello!
Well, I'm facing this issue. Internichestack in superlop mode works correctly, DHCP too. The problem is this: when turning on the module, without ethernet cable connected, the DHCP client fails(obviously). But when I plug teh cable, DHCP still not works. The only solution is to connect the cable before turning on the module. Any idea to improve this?Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The behavior you are describing occurs both in superloop and RTOS mode. The stack simply only attempts DHCP discovery on initial startup. You'll have to dig into the code and use some ingenuity if you want to change this behavior.
Jake- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The application selector application, shipped with the NEEK and 3c120 dev kits, has a task which monitors the autonegotiation successful bit in the PHY. Something similar could be done in superloop mode. The concept would be to hold off stack initialization until successful PHY autonegotiation.
- slacker- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well my NEEK can do that, and I can plug and unplug the cable and the IP is detected correctly. Well I didn't know that was done in another task, I will explore the Application Selector code a little more deeply.
Thansk to both, bye bye!
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page