2010-07-30 14:29:19 u-boot problem with live sources

Adam Rosenberg (UNITED STATES)

Message: 91935

I am trying to checkout the new features that will be in the next uClinux release for the BF537. I got the latest code from SVN trunk by following the directions here

docs.blackfin.uclinux.org/doku.php?id=developing_with_blackfin_live_sources

Everything compiled without error and I was able to load the new u-boot. This is where I ran into my first problem because u-boot was selecting an ethaddr value of "f9:03:f9:03:f9:03" that does not work. I tried to workaround this problem by doing the following to modify the ethaddr:

bfin> setenv ethaddr 00:00:00:00:01:01

bfin> saveenv

bfin> reset

Normally the saveenv command would make this change permanent but it reverts back to the previous value. I have to do the following each time the system boots to workaround this problem:

bfin> setenv ethaddr 00:00:00:00:01:01

bfin> run ramboot

Does anyone know how to make the ethaddr stick?

Using this workaound I was able to load the linux kernel using the default BF537-STAMP settings. To make this work on my custom board I had to copy the new stamp.c board configuration and manually merge my old board configuration into it. I have to admit, I was surprised at the huge amount of change between the 2009 release and the current SVN trunk.

-Adam

QuoteReplyEditDelete

2010-07-30 14:40:46 Re: u-boot problem with live sources

Mike Frysinger (UNITED STATES)

Message: 91937

for Blackfin boards using bfin_mac, it's on the head of every board implementer to handle their MAC address setup. my guess is you're still using an older method and you didnt update when moving to trunk.

look at the bf537-stamp boards file and in particular, the misc_init_r()/ethaddr/board_init_enetaddr() logic. chances are, you can simply copy & paste those pieces into your own board file and drop whatever you have.

QuoteReplyEditDelete

2010-07-30 14:59:31 Re: u-boot problem with live sources

Adam Rosenberg (UNITED STATES)

Message: 91939 Mike,

I am pretty sure I used the bf537 stamp files for the u-boot

configuration and the kernel configuration because I first tried this

on the stamp board. Still, I will need this to work on my custom

board eventually so I will check out the board_init_enetaddr you

mentioned. Thanks!

-Adam

P.S. Isn't it annoying when kernel configuration options change their

name? I see AT24 is now EEPROM_AT24. It must be hard to keep up with