Hello Malcolm,

Can you confirm that your application works without the LED threads running?

I too am working on an application using the K64F and the EthernetInterface library. I am currently running into an issue whereby the connect() function is always reporting an error (-1). If I disable both of your led threads I see the same problem with your application.

Cameron

Hi Cameron,

I'm not actually checking the result of the connect() call - I can check this evening when I get back from work; but when I comment out both LED threads the application runs and I can telnet into it and get the dual-echoes back. I've also confirmed correct behavior using Wireshark to monitor the traffic.

Have you checked with Wireshark to see if your board sends an ARP packet advertising its presence?

- Malcolm

Malcolm,

The fact that you are getting the double echo you are expecting tells me that EthernetInterface would appear to be working just fine on your K64F.

I will have to fire up Wireshark this evening and check for the ARP advertisement packet.

Hard to imagine that I have two broken K64F's, but stranger things have happened. Will have to have an associate run my application on his boards later.

Thanks, Cameron

Between a co-worker and myself, we have a total of 5 FRDM-K64F boards...all of which were received in Dallas during FTF.

All 5 of our devices have the same behavior. The connect() function returns -1, regardless of whether using DHCP or static addressing.

I am beginning to wonder if those having success have a newer revision of the device. The 2 boards I have are based on the revision C schematic, which is known to have a I2C connection problem.

Malcolm - I appreciate you taking the time to respond to my posts. Sorry for not being able to help address your issue, however. I will let you know if I do come across any information.

- Cameron

Hi Cameron,

Unfortunately I didn't get a chance to do the test last night - I need to trade in my toddler due to noise issues!

The FRDM-K64F I have came from Arrow Electronics, and looks like its schematic revision D1. If you're interested I could run your code on my board to confirm success/failure.

- Malcolm

Hi Cameron,

It turns out I'm also getting a connect() return of -1 despite the network appearing to function (sends the ARP packet). In addition I found out my crash/lockup is occurring in the EthernetInterface::init() call.

Unfortunately even with all LED blink threads turned off, adding the Serial object to the application has consumed all "Room" (the unknown resource that's limiting any of my FRDM-K64F network applications from doing anything useful). In other words I can't bring up the network with TCP echo, and simultaneously print any data about it. Heisenberg anyone?

- Malcolm

mbed build version 83 was recently released which fixes a memory configuration issue on the K64F platform. I had similar thread crash issue (system was hard faulting) and updating fixed the problem. Just click on "mbed" in your project tree. On the right of the window, you'll see a notification that says "A newer version is available". Then click on the "Update" button below that notification.

Alas no joy - I even tried switching to the mbed-src to get the "bleeding edge" latest, but it's still not working there either. Still crashing in EthernetInterface::init().