public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Ethernet persistence
Date: Fri, 28 Feb 2014 11:22:35 +0100	[thread overview]
Message-ID: <5310636B.4070908@monstr.eu> (raw)
In-Reply-To: <1393517355694-174934.post@n7.nabble.com>

On 02/27/2014 05:09 PM, Anthony Mahar wrote:
> How can I make the ethernet connection persistent (after first use), rather
> than reconnecting/re initializing on each reuse? 
> 
> I'm working with a Xilinx Zynq zc706 board and am up and running u-boot
> quite successfully.  My main use case is to store u-boot in on-board flash,
> and have u-boot tftp get / boot the bitstream, kernel image, devicetree, and
> ramdisk image.  The following script functions well:
> 	"qspiboot=echo Configure PL and booting Linux from TFTP... && " \
> 		"fpga info 0;"						    \
> 		"tftp 0x1000000 system.bin;"				    \
> 		"fpga load 0 0x1000000 cb44bc;" \
> 		"tftp 0x3000000 ${kernel_image};" \
> 		"tftp 0x2A00000 ${devicetree_image};" \
> 		"tftp 0x2000000 ${ramdisk_image};" \
> 		"bootm 0x3000000 0x2000000 0x2A00000\0" \
> 
> 
> The ethernet (Zynq's gem.e000b000) will get initialized on first use, as
> appropriate, however the Ethernet is reinitialized and auto negotiated again
> for each subsequent tftp request which shouldn't be necessary.  A snippet is
> listed below.  Each 'reconnection' takes several seconds... a few to auto
> negotiate, then a few more for the Windows based TFTP server to recognize
> the connection and allow connections to the server.  Multiply this by the
> number of transfers and it takes a very long time to transfer a very little
> amount of data.
> 
> Snippet:
> 
> Xilinx Device
> Descriptor @ 0x3ffbaf78
> Family:         Zynq PL
> Interface type: Device configuration interface (Zynq)
> Device Size:    13321404 bytes
> Cookie:         0x45 (69)
> Device name:    7z045
> No Device Function Table.
> Gem.e000b000 Waiting for PHY auto negotiation to complete....... done
> Using Gem.e000b000 device
> TFTP from server 192.168.2.1; our IP address is 192.168.2.10
> Filename 'system.bin'.
> Load address: 0x1000000
> Loading: T #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          #################################################################
>          ###############################################################
>          953.1 KiB/s
> done
> Bytes transferred = 13321404 (cb44bc hex)
> Gem.e000b000:7 is connected to Gem.e000b000.  Reconnecting to Gem.e000b000
> Gem.e000b000 Waiting for PHY auto negotiation to complete....... done
> Using Gem.e000b000 device
> TFTP from server 192.168.2.1; our IP address is 192.168.2.10
> Filename 'uImage'.
> Load address: 0x3000000
> Loading: T #################################################################
>          #################################################################
>          #################################################################
>          ################
>          429.7 KiB/s
> done
> 

I am not sure if this is intention with phylib but this was bring up
with phylib. I still support non-phylib version in xilinx u-boot git version
(but it is not regularly tested).

Not sure what your system.bin is but if you use FIT then you can just download
one image.

Thanks
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140228/8eb09d47/attachment.pgp>

  reply	other threads:[~2014-02-28 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 16:09 [U-Boot] Ethernet persistence Anthony Mahar
2014-02-28 10:22 ` Michal Simek [this message]
2014-02-28 14:24 ` Simon Glass
2014-02-28 14:33   ` Michal Simek
2014-02-28 17:33   ` Scott Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5310636B.4070908@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox