Hi, On Thursday 25 November 2010 08:40:33 Adam Wang wrote: > I got msg below. My question: Is it ok about ID? > > *** Running tests in category: Ethernet > MDIO: > Unexpected PHY ID: 0045
The expected value is 0x0022 and 0x0045 = (0x0022 << 1) | 0x0001. I also get this problem intermittently, and I'm pretty sure this only has to do with the bit banging code sampling the serial MDIO data at the wrong moment. Until this bug is fixed in libhal, you can take 0x0045 as a "passed PCB test" as well. This problem doesn't impede regular packet transmission or reception, so it's not a priority for me to pour my limited time on it. MDIO is only here to check link status (not an absolute must-have) and reconfigure the PHY (the default configuration works). > In order to make sure if USB Port A or Port B hardware connection is good > during production, I can just plug-in and plug-out as shown below to > verify: > > USB: HC: Device disconnect on port A > USB: HC: Low speed device on port A > USB: HC: VID: 04F2, PID: 0402 > USB: HC: Found keyboard > USB: HC: Device disconnect on port A > > Agreed? Yes. With the current softusb firmware, keyboard/mouse events from both ports are multiplexed on the same channel and the test program cannot tell which port they are coming from. So it just runs the test twice so you can try the ports one by one. You can also use those debug messages from the softusb firmware. S. _______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkym...@freenode Twitter: www.twitter.com/milkymistvj Ideas? http://milkymist.uservoice.com
