devn-mpc85xx driver detect wrong speed

QNX Newsgroups (Archives) qnx.bsp
1

I’m using the “devn-mpc85xx.so Driver for Motorola MPC85XX TSEC Ethernet
controllers”, from the mpc85x0ads BSP, with a custom board.

Here is how I start the driver in the boot script:
io-net -dmpc85xx mac=0001af079b8b,verbose -ptcpip
waitfor /dev/io-net/en0 4
ifconfig en0 192.168.1.40
The Ethernet PHY is a Marvell 88E1111 rev B1.

Everything works fine except if I unplug the cable for some minutes, then:

  • If a I connect a “100MBit cable”, the leds and the driver (sloginfo,
    nicinfo) indicate 10Mbit half duplex instead of 100Mbit full duplex.
  • If I connect a “1Gbit cable” the leds and the driver indicate 1Gbit
    and full duplex as expected.

When I stop the boot at the boot loader prompt (u-boot) and do the
experiments the leds always show the right speed and duplex state.

From the above tests I expect a bug in the QNX driver.

Does anybody knows something about such a problem?

Regards,

Armand

2

Hi Armand:

There’s been a number of bug fixes to that driver since the initial
release (one of which sounds suspiciously like your problem). I’d
recommend contacting support to get an updated binary (or source if
that’s what you have).

Robert Craig.

Armand C. wrote:

I’m using the “devn-mpc85xx.so Driver for Motorola MPC85XX TSEC Ethernet
controllers”, from the mpc85x0ads BSP, with a custom board.

Here is how I start the driver in the boot script:
io-net -dmpc85xx mac=0001af079b8b,verbose -ptcpip
waitfor /dev/io-net/en0 4
ifconfig en0 192.168.1.40
The Ethernet PHY is a Marvell 88E1111 rev B1.

Everything works fine except if I unplug the cable for some minutes, then:

  • If a I connect a “100MBit cable”, the leds and the driver (sloginfo,
    nicinfo) indicate 10Mbit half duplex instead of 100Mbit full duplex.
  • If I connect a “1Gbit cable” the leds and the driver indicate 1Gbit
    and full duplex as expected.

When I stop the boot at the boot loader prompt (u-boot) and do the
experiments the leds always show the right speed and duplex state.

From the above tests I expect a bug in the QNX driver.

Does anybody knows something about such a problem?

Regards,

Armand