[U-Boot] U-Boot Loop

[James Chargin]

Dang,

On 04/14/2014 03:11 PM, Tran, Dang wrote:
> Jim,
>
> I'm using TeraTerm version 2.3.

I've also occasionally used TeraTerm successfully. Usually, I use the 
Linux "cu".

> I can send Ctrl-C the board. However when I'm in this looping mode I can't.

I have no other ideas for you to try, I'm sorry.

Perhaps, looking at the networking retry code for your version will 
reveal if it watches for interruption.

>>From what you descried, version 2010.12 works and maybe I should update to a later version and see if that fixes my issue.

The common advice given on the mailing list is to update to a later 
version. Once you are running a relatively recent version, help is more 
likely to be available.

Since most developers on the mailing list are running something very 
recent, it can be difficult to help with older versions.

If you are going to update, choose something more recent than 2010.12, 
maybe something from 2013 or 2014.

Perhaps, as you hope, a newer version will fix your problem.

>
> Thanks
> Dang

Good luck.

Jim
-- 
Jim Chargin
AJA Video Systems                       jimc at aja.com
(530) 271-3334                          http://www.aja.com
>
> -----Original Message-----
> From: James Chargin [mailto:jimccrown at gmail.com]
> Sent: Monday, April 14, 2014 2:10 PM
> To: Tran, Dang; u-boot at lists.denx.de
> Subject: Re: [U-Boot] U-Boot Loop
>
>
>
> On 04/14/2014 01:11 PM, Tran, Dang wrote:
>> Hi James,
>>
>> I'm using U-Boot 2010.06 (Jun 18 2013 - 14:03:16)
>
> This is a version of U-Boot that is even older than the version I used for my demonstration that ctrl-c works. (I used 2010.12)
>
> You should make efforts towards using a more recent version.
>
> What information can you provide as to the settings of your serial terminal emulator? Is it known to send your ctrl-c to the target device?
>
> Jim
> --
> Jim Chargin
> AJA Video Systems                       jimc at aja.com
> (530) 271-3334                          http://www.aja.com
>
>
>>
>> Thanks
>> Dang
>>
>> -----Original Message-----
>> From: James Chargin [mailto:jimccrown at gmail.com]
>> Sent: Friday, April 11, 2014 9:46 AM
>> To: u-boot at lists.denx.de; Tran, Dang
>> Subject: Re: [U-Boot] U-Boot Loop
>>
>> Greetings,
>>
>> On 04/11/2014 09:23 AM, Tran, Dang wrote:
>>> Hi,
>>>
>>> I'm running a PowerPC board that uses U-Boot and I get into this loop (see terminal output below).
>>> It doesn't matter how I get into this loop. What I really care about is how to break out of it without manually resetting the board.
>>> Is there a way to break out of this loop and reset the system via the terminal? Ctrl-X and Ctrl-C doesn't seem to do anything.
>>>
>>
>> It might be helpful to know which version of U-Boot you are using.
>>
>>>
>>>
>>> TERMINAL OUTPUT
>>> Waiting for PHY auto negotiation to complete...... TIMEOUT !
>>> eTSEC1: No link.
>>> Speed: 1000, full duplex
>>> Using eTSEC2 device
>>> TFTP from server 192.168.128.127; our IP address is 192.168.128.128 Filename 'oe/bsp/mvme2500/vxWorks'.
>>> Load address: 0x1000000
>>> Loading: T T T T T T T T T T
>>> Retry count exceeded; starting again
>>> Waiting for PHY auto negotiation to complete...... TIMEOUT !
>>
>> For U-Boot builds made from official sources, ctrl-C works for me to terminate the retry TFTP, as shown
>>
>> => # with no Ethernet connection...
>> => tftp 500000 test.txt
>> Waiting for PHY auto negotiation to complete....user interrupt!
>> eTSEC1: No link.
>> show_boot_progress(-81) boot fail
>> => # in the above, "user interrupt!" was the response to ^C => => # 10.10.0.10 is known to not exist => setenv serverip 10.10.0.10 => tftp 500000 test.txt
>> Speed: 1000, full duplex
>> Using eTSEC1 device
>> TFTP from server 10.10.0.10; our IP address is 10.10.0.15 Filename 'test.txt'.
>> Load address: 0x500000
>> Loading: T T
>> Abort
>> show_boot_progress(-81) boot fail
>> => # in the above, "Abort" was the response to ^C =>
>>
>>
>> Please make sure your serial communication terminal emulator correctly transmits the ctrl-C when you type it. To see if this works, get to a U-Boot prompt and type ctrl-C, you should see <INTERRUPT>
>>
>>> ...
>>
>>>
>>> ...