Bug 8533 - uBoot behaviour incorrect
: uBoot behaviour incorrect
Status: RESOLVED WONTFIX
Product: SB Controller
Classification: Unclassified
Component: Setup
: unspecified
: PC Windows XP
: -- normal (vote)
: Future
Assigned To: Richard Titmuss
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-22 20:08 UTC by Stein David
Modified: 2009-09-29 03:47 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stein David 2008-06-22 20:08:39 UTC
The uBoot UI is buggy.  An example: From the uBoot prompt, run "upgrade" and press 2 to upload cramfs. Once completed the prompt does not return.  Pressing the enter key to get the prompt only repeats the previous command.  I must enter a nonsense command to force an error condition and error message before a prompt is returned.
Comment 1 Chris Owens 2008-06-30 09:38:42 UTC
This only happens using USB upgrading, right?  It's not so important then.
Comment 2 Stein David 2008-07-01 07:41:44 UTC
This bug affects All serial communication with uboot.  It causes difficulty for reworking Jives, reprogramming Jives on the line.  It was pushed off many months ago and was told that it would be fixed when there was more time.  I would like to find time.  
Comment 3 Chris Owens 2008-07-07 10:28:54 UTC
Richard, is there a timeframe when you think this could be fixed?
Comment 4 Richard Titmuss 2008-07-15 04:10:56 UTC
David, I don't recall you mentioning this before.

Is the problem that return repeats the previous command? If so I think you are complaining about the default behavior of uboot, so I am reluctant to change this.

Or is the problem that the prompt is not displayed after a command is completed? I normally see the JIVE# prompt after running a command in uboot.

Or is the problem just with the 'upgrade' command. If so I have never been able to run that myself (the usb drivers crash my PC), so can't comment on it's behavior.

What's wrong with your existing work around of entering a nonsense command?
Comment 5 Richard Titmuss 2009-09-29 03:47:05 UTC
This won't get fixed, unless it's causing a problem on the production line.