FRDM-K64F with MQX and RTCS don't always reply on ping commands

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

FRDM-K64F with MQX and RTCS don't always reply on ping commands

Jump to solution
943 Views
arnoudvanriesse
Contributor II

Hi,

 

I use a FRDM-K64F with MQX and RTCS for network communication. However the boards don't reply on ping commands from my PC. When sending data from the FRDM board the board sometimes reply on a ping but mostly don't. I use KSDK-1.3.

 

The same applies when I send a UDP packet to the FRDM board. The data is send from the PC (logged with Wireshark) but the FRDM board don't react on it, however when I send lots of data from the FRDM board, the board mostly see the received data.

 

Changing the priority of the RTCS task higher then the other tasks makes not difference.

 

Has anyone encountered this problem? Or has a solution, or any advice for this?

Labels (1)
0 Kudos
1 Solution
630 Views
arnoudvanriesse
Contributor II

I found the problem. The FRDM-K64F boards all have the same default MAC address.

This caused that data was send to both boards and the mac/ip combination in the PC tcp/ip stack got mixed up.

The framework I use was set-up by a external party that did set-up the MAC address only the variable used for this was never initialized.

See also this thread howto set a unique MAC address.

Thanks for the help any way..

View solution in original post

0 Kudos
5 Replies
630 Views
mjbcswitzerland
Specialist V

Hi

Load a reference binary for the FRDM-K64F from http://www.utasker.com/kinetis/FRDM-K64F.html to check that it is not a HW issue. It has FTP, Telnet and web server at 192.168.0.3 (or NetBios "KINETIS") by default but can be configured as required in the LAN menu on the OpenSDA virtual COM connection at 115'200 Baud.

Note that the PHY on the on the FRDM-K64F doesn't have an interrupt line so the SW should poll its state to ensure that the PHY and EMAC are synchronised to the same settings - incorrect synchronisation will cause loss of data and possible loss due to collisions if in half-duplex mode.

Regards

Mark

0 Kudos
630 Views
arnoudvanriesse
Contributor II

Hi Mark,

Thanks for the reply. With the utasker program everything works fine, see also my reply on the reply from Iva.

Best Regards,

Arnoud

0 Kudos
630 Views
ivadorazinova
NXP Employee
NXP Employee

Hi Arnoud,

please, what is your connection? Directly from computer or through router?

Thank you.

Best Regards,

Iva

0 Kudos
630 Views
arnoudvanriesse
Contributor II

Hi Iva,

I use a switch. The actual configuration i use no to solve this is as follow:

2 FRDM boards connected to a switch (In final setup i need 18 FRDM boards) and a PC connected to the switch.

When both boards are idle I can ping both board. When I ping board B cont. I receive the replies when in the mean time board A starts to send data to the PC, board B is not answering the ping messages anymore. When board A stops sending data, board B will answer the ping messages after a while.

Board A sends about 7Kbyte of data at 20 Hz (every 50ms).

I have a MQX task that does the data sampling. When I remove that task (on board B) then board B replies on the ping messages when board A start sending data.

Note that board B is not doing the actual data sampling, only board A.

I can also see the lights on the switch blink on each ping command, but the light on the ETH connector on the board don't blink. So I don't think this a switch related problem since I have tried 3 different brand of switches(MOXA, Applied Telesis, and a consumer cheap one) and the problem persists.

Hope that this will help.

Arnoud

0 Kudos
631 Views
arnoudvanriesse
Contributor II

I found the problem. The FRDM-K64F boards all have the same default MAC address.

This caused that data was send to both boards and the mac/ip combination in the PC tcp/ip stack got mixed up.

The framework I use was set-up by a external party that did set-up the MAC address only the variable used for this was never initialized.

See also this thread howto set a unique MAC address.

Thanks for the help any way..

0 Kudos