My BBB is still working great, wireless and all, after the RMA repair. But one silly detail has been bothering me...
The ifconfig-reported MAC address of the usb0 port changed after the repair: usb0 Link encap:Ethernet HWaddr 6E:5A:F6:F0:F3:45 After RMA repair: usb0 Link encap:Ethernet HWaddr 06:57:23:9E:EA:C7 Both of those are locally administered addresses, so they probably aren't read from any hardware, and thus probably don't suggest anything about what was done to my board during the RMA repair. But why the change? <http://processors.wiki.ti.com/index.php/AMSDK_u-boot_User's_Guide> ----- When using a USB-Ethernet dongle a valid MAC address must be set in the environment. To create a valid address please read this page. Then issue the following command: U-Boot # setenv usbethaddr value:from:link:above ----- I guess that "dongle" setting doesn't apply to the usb0 "Linux USB Ethernet/RNDIS Gadget", because none of my environments have ever included it. What I do find in printenv, before and after repair, is: usbnet_devaddr=90:59:af:4d:71:eb Which is = eth0! The usb0 MACs shown by ifconfig don't appear in any printenv or boot log, only in ifconfig! They also don't show in externally connected systems: Ethernet - 140120: Windows ipconfig /all --- Ethernet adapter Local Area Connection 5: Description . . . . . . . . . . . : Linux USB Ethernet/RNDIS Gadget Physical Address. . . . . . . . . : 90-59-AF-4D-71-ED --- That is one of the two MAC addresses stored in BBB hardware. It, and the ifconfig eth0 MAC address, stayed the same after the repair: <http://e2e.ti.com/support/arm/sitara_arm/f/791/t/199705.aspx> ----- The values read from Control Module (Base address 0x44E1_0000) MAC_ID0_LO register (Offset 0x630), MAC_ID0_HI register (Offset 0x634), MAC_ID1_LO register (Offset 0x638), and MAC_ID1_HI register (Offset 0x63C) represent unique MAC addresses assigned to each AM335x device. The values in these registers are programmed into each AM335x device by TI and can not be changed. Software can be configured to read and use the MAC addresses programmed into the AM335x device or non-volatile memory devices attached to AM335x. ----- <https://groups.google.com/forum/#!topic/beagleboard/J-5mDkI8p0Q> ----- You can read them out by using devmem2: root@beaglebone:/dev# devmem2 0x44e10630 [and 34/38/3C] These values are read out in am33xx_cpsw_init() in arch/arm/mach-omap2/devices.c. ----- --> Mine show the eth0 address, and another just two bits higher that Windows shows as the usb0 port. So... Where do the usb0 MAC addresses reported by ifconfig come from? Why did they change after the repair? Why do ifconfig and Windows disagree about the usb0 MAC, when they agree about the eth0 MAC? On Tuesday, January 21, 2014 3:01:18 PM UTC-8, Loren Amelang wrote: > > My board is back from RMA, with what looks like a new ethernet chip. It is > ever so slightly raised up along one edge, though the pin alignment and > soldering job are perfect. I guess it could have been that way before, but > usually that's a sign of manual replacement. The only info I was able to > get from the RMA Team was: > --- > After running the diagnostic tests, we found that there was a Ethernet > malfunction. We have fixed the issue and everything is properly working. > > >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
