We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I KEEP GETTING FATAL ERROR WHEN I TYPE A51 AT MY COMMAND LINE.
I GET TERMINATED.
WHY?
Your shift key seems to be stuck. But I digress.
When you type only "A51" at the command line, you run the A51 assembler - without telling it which file to process. Since there is nothing meaningful for it to do, it prints an error message and exits.
What exactly are you trying to accomplish by running the A51 assembler from the command line ? Usually, the assembler is called by the IDE. Except for experimentation, there are very few reasons to actually run the assembler "by hand".
HOW DO I GET ULTRAEDIT TO DO IT?
I thought you where terminated.
Stop writing in ALL CAPITALS!
"HOW DO I GET ULTRAEDIT TO DO IT?"
You read the "ultraedit" Manual, and do whatever it tells you!
As "ultraedit" isn't a Keil product, this isn't really the place to get support on it! http://www.keil.com/forum/
I TRY ULTRAEDIT FORUM BUT THEY SAY I MUST GO TO KIEL BCOZ IT IS NOT ULTRAEDIT BUG!
Clever - did you say that it was a bug? Of course they say it isn't an Ultraedit bug. It isn't a Keil bug either.
It is a SBK bug. A "I don't know how to do it" bug.
Incorrectly calling something a bug means no one is interested in helping you.
GO TO KIEL BCOZ IT IS NOT ULTRAEDIT BUG!
Its not a bug at all !
If you really want to piece together your own developer environment, you must read the manuals of the products you are using and then use this information to set up an actual build chain. This is not a trivial task. You may not want to try to tackle it if this is your first attempt at writing programs for a '51.
Instructions on how to use the A51 assembler can be found here:
http://www.keil.com/support/man/docs/a51/
A "I don't know how to do it" bug.
Looks more like an
"I don't know that there is a manual"-, "I don't want to bother with reading the manual"-, or "I have trouble understanding the contents of the manual"-
type of bug.
TNX FOR THE HELP. I WILL READ THE MANAUL AND FIND LIST OF HOW TO WORKAROUND BUGS.
I WILL READ THE MANAUL AND FIND LIST OF HOW TO WORKAROUND BUGS.
Then you will be looking in the wrong place.
What you call a "bug" is actually a completely normal behavior of the A51 compiler, and a typical reaction to insufficient or wrong command line arguments given by the user (that means "by you").
You need to read the parts of the manual concerning the normal usage of the A51 compiler - i.e. what command line options it expects and needs to do its job (convert an assembly file to an object code file).
HI AGAIN.
DOES ANYONE KNOW WHERE IN THE MANUAL IT HAS A INDEX OF BUGS?
I LOOK AND CANNOT FIND. SO I DON'T KNOW HOW TO WORK AROUND THE PROBELM.
Err ... nowhere. That wouldn't really make sense, since documenting a bug would make it an undesired feature, wouldn't it ?
And once again, what you are seeing is not a bug. It is a normal, expected reaction of the assembler to wrong or insufficient input data. It then prints an error message.
Yyou can find a list of error messages in the manual.
http://www.keil.com/support/man/docs/a51/a51_errors.htm
More precisely, the error message you are seeing can be found on this page, along with a description of what causes it.
http://www.keil.com/support/man/docs/a51/a51_er_messages.htm
Begone heathen! You are not seeing the result of a bug - you have a "*** bekind the keyboard" problem. YOU did wrong, and the program complained. When you start to feed reasonable command-line parameters, the program will stop complaining!
THANX FOR YOUR ALL YOUR ADVICE.
I WILL CHECK THE MANUALZ AGIAN.
BUT I AM HAPPY TO SPEAK THAT I HAVE NEVER HAD A *** BEHIND THE KEYBOARD. I ALWAYS GO BEHIND THE BUSH!
your humor is appreciated, however, that does not reduce the anoyance of reading what you are typing in all CAPITALS which makes your posts difficult to read.
In addition, many consider CAPITALS 'shouting' and consider that very impolite.
Erik
PS "*** bekind the keyboard" is a phrase more modern than "garbage in = garbage out" i.e. if you do not use the proper command line you will not get the expected result.