I am using twr-MK60N512D on IAR, i have my own enet drivers as well as Fnet 2.6.3 Shell project. But as of now, I am using fnet shell proj and trying to ping the ip configured on my k60 target to see if my test set up is fine, but even thats not happening.
I did all following recommended jumper settings on my twr-ser and k60 card,
J2 Ethernet PHY Clock Select - 50 MHz
J3 CLOCKIN0 Driver Select - Route 50 MHz clock to CLOCKIN0
J12 Ethernet PHY Config - only Pull-up CONFIG0; RMII Select
For the K60: J6 Clock Input Source Select - Connect EXTAL to CLKIN0
I can see the ping transmit on the wireshark but the reply request is timing out. Am i missing something here??
Also I read this from uTasker, is this necessary?
You will need first to configure the PC’s NIC (Network Interface Card) that it should use for
mapping the Kinetis Ethernet controller to – do this in the “LAN” menu with “Select Working
NIC”. This setting will also be saved and thus needs only be entered once.
Then use the bat file, as described in the chapter “Ethernet”, to transfer the web pages to the
simulated device via FTP. After this has been done, connect to its IP address using a
standard browser and see the project in operation!
That was exactly the issue. I was aware of this jumper setting and thought I did it correctly, but apparently not. The J6 pin numbering was a bit confusing on the board that it is from right to left for J6 and left to right for others.
And also, I had to sync my nic card to K60 ethernet controller.
Check the jumpers on the K60 board too. J6 2-3 should be on to select the clock from the Ethernet board.
If you have no success you can check the HW by loading a pre-built project from µTasker Test Software and Demos (IP address = 192.168.0.3) which allows you to check PING, Web server, FTP, TELNET and some other things like the SD card and the USB interface.
The instructions from the uTasker project that you reference refer to when running the uTasker simulator and have nothing to do with the hardware. The simulator allows a virtual Kinetis to be operated on the PC and run the Kintis code - its EMAC can be hooked up to the PC's NIC in order to allow it to be contacted from the LAN; eg. for testing and debugging the EMAC driver and any SW working with it (eg. the TCP/IP stack and application layers such as the web server).