This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Ping failure by the change of 10M to 100Mbps

Hi!

I'm developing a project and it's working well at 10Mbps (_10MBIT_ define at LPC23_EMAC.c) with TCP protocol. The ping response is perfect:

ping 10.0.0.180

Disparando 10.0.0.180 com 32 bytes de dados:
Resposta de 10.0.0.180: bytes=32 tempo<1ms TTL=128
Resposta de 10.0.0.180: bytes=32 tempo<1ms TTL=128
Resposta de 10.0.0.180: bytes=32 tempo<1ms TTL=128
Resposta de 10.0.0.180: bytes=32 tempo<1ms TTL=128

Estatísticas do Ping para 10.0.0.180:
    Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
             perda),
Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 0ms, Máximo = 0ms, Média = 0ms


Code:

/* The following macro definitions may be used to select the speed
   of the physical link:

  _10MBIT_   - connect at 10 MBit only
  _100MBIT_  - connect at 100 MBit only

  By default an autonegotiation of the link speed is used. This may take
  longer to connect, but it works for 10MBit and 100MBit physical links.     */

#define _10MBIT_
//#define _100MBIT_

When I enable the auto negotiation or _100MBIT_ define only, I got ping failure:

ping 10.0.0.180

Disparando 10.0.0.180 com 32 bytes de dados:
Resposta de 10.0.0.80: Host de destino inacessível.
Resposta de 10.0.0.80: Host de destino inacessível.
Resposta de 10.0.0.180: bytes=32 tempo=999ms TTL=128
Resposta de 10.0.0.180: bytes=32 tempo<1ms TTL=128

Estatísticas do Ping para 10.0.0.180:
    Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
             perda),
Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 0ms, Máximo = 999ms, Média = 499ms

---

Disparando 10.0.0.180 com 32 bytes de dados:
Resposta de 10.0.0.180: bytes=32 tempo<1ms TTL=128
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.

Estatísticas do Ping para 10.0.0.180:
    Pacotes: Enviados = 4, Recebidos = 1, Perdidos = 3 (75% de
             perda),
Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 0ms, Máximo = 0ms, Média = 0ms

---

Disparando 10.0.0.180 com 32 bytes de dados:
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.
Resposta de 10.0.0.180: bytes=32 tempo<1ms TTL=128
Esgotado o tempo limite do pedido.

Estatísticas do Ping para 10.0.0.180:
    Pacotes: Enviados = 4, Recebidos = 1, Perdidos = 3 (75% de
             perda),
Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 0ms, Máximo = 0ms, Média = 0ms

---

Disparando 10.0.0.180 com 32 bytes de dados:
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.

Estatísticas do Ping para 10.0.0.180:
    Pacotes: Enviados = 4, Recebidos = 0, Perdidos = 4 (100% de
             perda),


Code:

//#define _10MBIT_
//#define _100MBIT_


or

//#define _10MBIT_
#define _100MBIT_

How can I solve this problem? Does anybody can help me, please?

I need to work at 100Mbps to increase my network performance. My RL-ARM TCPnet library version is the 4.12.

Thanks,
Rafael.

Parents
  • Thanks, Mike!

    My project hardware is based at MCB2300 hardware and has a DP83848, which works with 10/100Mbps speeds.

    I have verified that with the same firmware running at 100Mbps worked only in MCB2300.

    At my project hardware, the RJ-45 connector was away from the DP83848. The circuit at page 33 from the DP83848 datasheet (pdf1.alldatasheet.com/.../DP83848C.html) gives the following recomendation: "place registers and capacitors close to device". At my circuit, this registers and capacitors were close to RJ-45, they weren't close to DP83848.

    Now "the registers and capacitors" are close to DP83848 at my project hardware and the same firmware running at 100Mbps is working well on it.

    My hardware is responding to all pings request now. :-)

Reply
  • Thanks, Mike!

    My project hardware is based at MCB2300 hardware and has a DP83848, which works with 10/100Mbps speeds.

    I have verified that with the same firmware running at 100Mbps worked only in MCB2300.

    At my project hardware, the RJ-45 connector was away from the DP83848. The circuit at page 33 from the DP83848 datasheet (pdf1.alldatasheet.com/.../DP83848C.html) gives the following recomendation: "place registers and capacitors close to device". At my circuit, this registers and capacitors were close to RJ-45, they weren't close to DP83848.

    Now "the registers and capacitors" are close to DP83848 at my project hardware and the same firmware running at 100Mbps is working well on it.

    My hardware is responding to all pings request now. :-)

Children