tftp download of uImage onto beagleboard xm possible?

[Peter Thompson]

I am building u-boot-2013.10  using omap3_beagle_config for my Beagleboard xm (without any changes to the configuration).   The /include/configs/omap3_beagle.h file says "Configuration settings for the TI OMAP3530 Beagle board" but I am assuming it also works for the Beagleboard xm 3730. 


The commands (see below)
usb start
tftp 0x80000000 uImage

don't work on this setup.  I know my host Ubuntu machine is set up correctly since I can get get tftp working on an igepv2 board. 

I have read both:   that tftp in u-boot does work and doesn't work on the beagleboard xm.



My question is - does tftp on u-boot work on the beagleboard xm?
If yes, what am I missing?

my uboot log is below

U-Boot 2013.10 (Nov 24 2013 - 21:50:38)

OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
DRAM:  512 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

In:    serial
Out:   serial
Err:   serial
Beagle xM Rev C
No EEPROM on expansion board
Die ID #3eb200229ff8000001469c631502302d
Net:   usb_ether
Hit any key to stop autoboot:  0
OMAP3 beagleboard.org #   

   
OMAP3 beagleboard.org # usb start
(Re)start USB...
USB0:   ULPI: ulpi_reset: failed writing reset bit
ULPI: ulpi_reset: failed writing reset bit
USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... Warning: failed to set MAC address
1 Ethernet Device(s) found


OMAP3 beagleboard.org # tftp 0x80000000 uImage
ERROR: Need valid 'usbnet_devaddr' to be set
at ether.c:2358/usb_eth_init()

[Nizamov Shawkat]

Hi,

Just a hint - the error message means that you have to set the mac-address of the network card. So you need something like "usbnet_devaddr=c8:a0:30:ac:e0:ef". You have to figure out where to put it.

Best regards,

[Peter Thompson]

Nizamov
Thanks for your response.   Your hint and some more pointed error messages  means tftp now works.   For others I got tftp working by manually setting up my environment.

setenv usbnet_devaddr   c8:a0:30:ac:e0:ef  ( from hint above )
setenv usbnet_hostaddr  bc:ae:c5:e0:b0:bd  ( from ifconfig on my host machine )
setenv usbethaddr          00:12:34:56:78:9a  ( I made this up - is an arbitrary number )
setenv ipaddr                 192.168.0.100
setenv serverip              192.168.0.1

usb start

 My only remaining question is where did the numbers c8:a0:30:ac:e0:ef come from?   Are they arbitrary - ie any numbers will work?


Peter       

[Nizamov Shawkat]

Hi,

Glad to hear that your problem solved. The number mentioned is a MAC address of ethernet card, it has to be unique at least in your environment. Normally it is written in some kind of EEPROM but BB-xm lacks it that's why  mac-address has to be generated randomly (well, almost randomly).

http://en.wikipedia.org/wiki/MAC_address

Best regards,