[U-Boot] NetConsole & TFTP
Hi all,
I am trying to use the NetConsole to configure the U-Boot and to send command to it. Everything works fine, but I also need to transfer files via TFTP. It looks like that is a problem and I hope the members of this mailing list can give me some answers and maybe solutions.
Is it possible to use NetConsole and TFTP parallel at one Ethernet interface? My fist thoughts were that this could be possible, because TFTP and NetConsole use different ports. But out of the box the behavior is different. In my tests TFTP tries to use another Ethernet interface (eTSEC1) as the NetConsole (eTSEC0), but the final Hardware has only one Ethernet and no serial interface. By the way, I tried the functionality with a second Ethernet interface and it also does not work. I see only less character at the NetConsole and it seems that the communication is going wrong and after a short time the communication is dead.
Therefore I need a possibility to communicate with a target (via NetConsole) and transfer the flash images (via TFTP). Has anybody experiences with this? Is this possible with U-Boot? Maybe I am doing something wrong?
Thank you for helping.
Regards, Thomas
SICK AG - Sitz: Waldkirch i. Br. - Handelsregister: Freiburg i. Br. HRB 280355 Vorstand: Dr. Robert Bauer (Vorsitzender) - Reinhard Bösl - Markus Paschmann - Markus Vatter Aufsichtsrat: Gisela Sick (Ehrenvorsitzende) - Klaus M. Bukenberger (Vorsitzender)
Dear Thomas,
In message OF0B4B1E6C.B54B0C2D-ONC12579CA.0038E059-C12579CA.0038F311@sick.de you wrote:
Is it possible to use NetConsole and TFTP parallel at one Ethernet interface? My fist thoughts were that this could be possible, because TFTP
Yes, this is supposed to work. We've even seen running TFTP and Netconsole over Ethernet over USB...
and NetConsole use different ports. But out of the box the behavior is different. In my tests TFTP tries to use another Ethernet interface (eTSEC1) as the NetConsole (eTSEC0), but the final Hardware has only one
Hm... you are not running mainline code, right? Because we always have a single network interface active at any time.
Therefore I need a possibility to communicate with a target (via NetConsole) and transfer the flash images (via TFTP). Has anybody experiences with this? Is this possible with U-Boot? Maybe I am doing something wrong?
I recommend you undo any modifications made to the network stack, and/or try plain mainline code instead.
Best regards,
Wolfgang Denk
Dear Wolfgang,
Hm... you are not running mainline code, right? Because we always have a single network interface active at any time.
I am using mainline code (u-boot v2011.12) with P2020RDB-PC_SPIFLASH_config. Unfortunately it does not work as I thought, but fortunately we may have a solution (patch) to solve the problem.
Best regards,
Thomas Pohl
Von: Wolfgang Denk wd@denx.de An: Thomas Pohl Thomas.Pohl@sick.de Kopie: u-boot@lists.denx.de Datum: 23.03.2012 20:47 Betreff: Re: [U-Boot] NetConsole & TFTP Gesendet von: u-boot-bounces@lists.denx.de
Dear Thomas,
In message OF0B4B1E6C.B54B0C2D-ONC12579CA.0038E059-C12579CA.0038F311@sick.de you wrote:
Is it possible to use NetConsole and TFTP parallel at one Ethernet interface? My fist thoughts were that this could be possible, because
TFTP
Yes, this is supposed to work. We've even seen running TFTP and Netconsole over Ethernet over USB...
and NetConsole use different ports. But out of the box the behavior is different. In my tests TFTP tries to use another Ethernet interface (eTSEC1) as the NetConsole (eTSEC0), but the final Hardware has only one
Hm... you are not running mainline code, right? Because we always have a single network interface active at any time.
Therefore I need a possibility to communicate with a target (via NetConsole) and transfer the flash images (via TFTP). Has anybody experiences with this? Is this possible with U-Boot? Maybe I am doing something wrong?
I recommend you undo any modifications made to the network stack, and/or try plain mainline code instead.
Best regards,
Wolfgang Denk
Hi Thomas,
On Mon, Mar 26, 2012 at 5:24 AM, Thomas Pohl Thomas.Pohl@sick.de wrote:
Dear Wolfgang,
Hm... you are not running mainline code, right? Because we always have a single network interface active at any time.
I am using mainline code (u-boot v2011.12) with P2020RDB-PC_SPIFLASH_config. Unfortunately it does not work as I thought, but fortunately we may have a solution (patch) to solve the problem.
Please share your results with us. What was the problem and how did you fix it?
Thanks, -Joe
participants (3)
-
Joe Hershberger -
Thomas Pohl -
Wolfgang Denk