Skip to contentSkip to conversation

Missing ethernet

U-Boot Gary Thomas 2 participants 4 messages Apr 19, 2012

lore
Share & tools
lore
#0 lore raw

I'm trying to update U-boot on my board from v2011.06 to v2011.12 It's an OMAP 3530, much like the BeagleBoard, with SMSC911x networking. U-Boot is working fine on this board, but when I boot Linux, it can no longer find the SMSC device. If I boot the same kernel with the older U-Boot, the SMSC device works perfectly.

I've looked through the 'bootm' path and I can't see what might have changed that would cause such behaviour. As far as I can tell, everything else is working in Linux with the new U-Boot, just not the SMSC device.

Any clues?

Thanks

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 6 lines · Gary Thomas

I'm trying to update U-boot on my board from v2011.06 to v2011.12 It's an OMAP 3530, much like the BeagleBoard, with SMSC911x networking. U-Boot is working fine on this board, but when I boot Linux, it can no longer find the SMSC device. If I boot the same kernel with the older U-Boot, the SMSC device works perfectly.

Quoted 9 lines

I've looked through the 'bootm' path and I can't see what might have changed that would cause such behaviour. As far as I can tell, everything else is working in Linux with the new U-Boot, just not the SMSC device.

Any clues?

Thanks

Note: I've verified that it's also not working in v2012.04-rc1

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#2 lore raw
In reply to Gary Thomas

Gary wrote...

Quoted 2 lines

I'm trying to update U-boot on my board from v2011.06 to v2011.12 It's an OMAP 3530, much like the BeagleBoard, with SMSC911x networking.

So not a BeagleBoard then but something different.

Is the board you are using one of the boards supported in the mainline U-Boot tree or is it an out-of-tree port? If it is in mainline then have you chosen the correct configuration to use?

Quoted 4 lines

I've looked through the 'bootm' path and I can't see what might have changed that would cause such behaviour. As far as I can tell, everything else is working in Linux with the new U-Boot, just not the SMSC device.

If you try to use TFTP in U-Boot does that work? If not then I would guess there is a configuration issue with the devices that you have enabled in U-Boot rather than it being an issue with the bootm command.

Regards,

Andy.

#3 lore raw
Quoted 10 lines · Andy Pont

Gary wrote...

Quoted 2 lines

I'm trying to update U-boot on my board from v2011.06 to v2011.12 It's an OMAP 3530, much like the BeagleBoard, with SMSC911x networking.

So not a BeagleBoard then but something different.

Is the board you are using one of the boards supported in the mainline U-Boot tree or is it an out-of-tree port? If it is in mainline then have you chosen the correct configuration to use?

It's my own board, not in the mainline.

Quoted 9 lines
Quoted 5 lines

I've looked through the 'bootm' path and I can't see what might have changed that would cause such behaviour. As far as I can tell, everything else is working in Linux with the new U-Boot, just not the SMSC device.

If you try to use TFTP in U-Boot does that work? If not then I would guess there is a configuration issue with the devices that you have enabled in U-Boot rather than it being an issue with the bootm command.

As I said, U-Boot works fine. The problem comes when Linux boots.

I've bisected it down to this change:
commit 81bdc155c72ef9e093b388b90c58d8134d870976
Author: Sanjeev Premi <[email protected]>
Date: Thu Sep 8 10:47:25 2011 -0400

omap: gpio: Use generic API

That let me figure out the problem - I had to modify my board code for the new GPIO functions and somehow that's where the problem is. Still working out the details, but now I know where to look.

Thanks for the help

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------