This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bad code

See code in last thread

Author
Andy Neil
Posted
12-Jun-2007 05:39
Toolset
C51 Irrelecant code!
Andy Neil
Author: jamil rafar
Posted: 12-Jun-2007 04:54
"what is wrong with this code plese"

Apart from the formatting, It appears to have nothing whatsoever with the topic of this thread!

Please start a new thread for a new topic!

Parents
  • "I answerde all the question that I understood"

    They weren't difficult questions!
    If you really don't know what chips you are using, you certainly won't get very far with this!

    Let's look again at the questions, and your answers:

    Q: What toolset & versions are you using?
    A: I use c version 12.00.8804

    'C' is just a language; The "Toolset" refers to the compiler, linker, etc that you use for your development.

    When you made your post, you had to choose a toolset under "MCU (Architecture)"

    You chose "Non-Specific (Generic)"; that is incorrect - you must be using one of the four specific Keil toolsets.
    Which is it?

    It must be one of these: http://www.keil.com/product/

    Q: What specific chips are you using?
    A: I dont understand your question

    Each of Keil's toolsets covers a family of processors.
    To be able to answer questions about specific code, people need to know which particular member of the family you are using; ie, which specific chip.
    eg, there are many hundreds of different chips in the 8051 family!

    It is also important to know about any other specific chips that are central to the understanding of your system.

    Q: What is the code supposed to do?
    A: Code is not working

    Now there's a logical contradiction!

    If your code is supposed to "not work" and it does, in fact, not work - then it is actually working according to that requirement, isn't it!

    Q: What does it actually do?
    A: I want the code to work

    Well, doesn't everyone?!

    Q: What debugging have you done so far to account for
    the difference?
    A: (none)

    So you haven't even bother to try any debugging at all, then?

Reply
  • "I answerde all the question that I understood"

    They weren't difficult questions!
    If you really don't know what chips you are using, you certainly won't get very far with this!

    Let's look again at the questions, and your answers:

    Q: What toolset & versions are you using?
    A: I use c version 12.00.8804

    'C' is just a language; The "Toolset" refers to the compiler, linker, etc that you use for your development.

    When you made your post, you had to choose a toolset under "MCU (Architecture)"

    You chose "Non-Specific (Generic)"; that is incorrect - you must be using one of the four specific Keil toolsets.
    Which is it?

    It must be one of these: http://www.keil.com/product/

    Q: What specific chips are you using?
    A: I dont understand your question

    Each of Keil's toolsets covers a family of processors.
    To be able to answer questions about specific code, people need to know which particular member of the family you are using; ie, which specific chip.
    eg, there are many hundreds of different chips in the 8051 family!

    It is also important to know about any other specific chips that are central to the understanding of your system.

    Q: What is the code supposed to do?
    A: Code is not working

    Now there's a logical contradiction!

    If your code is supposed to "not work" and it does, in fact, not work - then it is actually working according to that requirement, isn't it!

    Q: What does it actually do?
    A: I want the code to work

    Well, doesn't everyone?!

    Q: What debugging have you done so far to account for
    the difference?
    A: (none)

    So you haven't even bother to try any debugging at all, then?

Children
  • post a link to a website that give away crystal balls.

    Jamil:
    If you expect anyone to answer by psychic powers you should ask at www.psychichhotline.com, not here.

    You are frustrated that you do not get any answers, but refuse (there can be no other reason) to help those willing to help you. If you will not give the answers needed to determine the cause of your problem, nobody can help you.

    Erik

    re 'refuse'
    Q: What specific chips are you using?
    A: I dont understand your question


  • Author
    Andy Neil
    Posted
    12-Jun-2007 07:05
    Toolset
    None

    New! RE: Bad code
    Andy Neil

    "I answerde all the question that I understood"

    They weren't difficult questions!
    If you really don't know what chips you are using, you certainly won't get very far with this!

    Let's look again at the questions, and your answers:

    Q: What toolset & versions are you using?
    A: I use c version 12.00.8804

    'C' is just a language; The "Toolset" refers to the compiler, linker, etc that you use for your development.

    When you made your post, you had to choose a toolset under "MCU (Architecture)"

    You chose "Non-Specific (Generic)"; that is incorrect - you must be using one of the four specific Keil toolsets.
    Which is it?

    It must be one of these: http://www.keil.com/product/

    Q: What specific chips are you using?
    A: I dont understand your question

    Each of Keil's toolsets covers a family of processors.
    To be able to answer questions about specific code, people need to know which particular member of the family you are using; ie, which specific chip.
    eg, there are many hundreds of different chips in the 8051 family!

    It is also important to know about any other specific chips that are central to the understanding of your system.

    Q: What is the code supposed to do?
    A: Code is not working

    Now there's a logical contradiction!

    If your code is supposed to "not work" and it does, in fact, not work - then it is actually working according to that requirement, isn't it!

    Q: What does it actually do?
    A: I want the code to work

    Well, doesn't everyone?!

    Q: What debugging have you done so far to account for
    the difference?
    A: (none)

    So you haven't even bother to try any debugging at all, then?

    Sorry my answer is slow but my computer keeps craching when I answer so I find someones computer to give you my answre.

    I gave you answers but I missed a question so my answer looked wrong to you but it was because the answer was to the bad question so you think it was wrong but it was to the wrong one because you gave a question that i did not answer because I did not give a good question to you so here is the big list for you:

    1 I use c version 12.00.8804 which I get from the about box. I think that the program is from Cryslat Systems which it says there to.

    2 I do not know what you mean whith chipset. The memory chip I use is from ebay and it cost $12.72 plus $3.57 for delivery. It has a label sayings Dell on it.

    3 I want the code to test the memory chip because the seller says that it works but it doesnt not work when I put it into my camera but the seller says that it is my camera that must be bad but I have used other memory cards in my camera and they work so I think it must be the card so he gave me code to test card but I cannot get that to work.

    4 I run the code but I cannot read the card

    I do not know if ti is the card of the computer of the code that is bad. I think it is the card but he says that I must check the card and return it by the weekend toget my money back because he says that if the card is good when I send it back he will keep the card and my money. But I think that he 5tries to cheat me with the code because I can not get the code to work roperly.

  • From the above I take it that you are not implementing a new embedded program for use in the camera.

    You are not using any Keil tools, so this seems to be the wrong forum.

    What platform are you trying to test the memory chip on?

    The question about chip was which _microprocessor_ the target hardware is using. If the target is a PC, then you are very much in the wrong forum.

    If this is an embedded system, then we also need to know how the microcontroller is connected to the memory.

    Why not just use normal memory reader on a PC, and test the card? Do the camera support the specific size of card? Is the card formatted? Is the card formatted with a file system that the camera supports? Have you tried letting the camera format the card?

    About your source code: It is not complete. It is only a partial function. The rest of the function - and a number of other functions - are missing.

  • "1 I use c version 12.00.8804 which I get from the about box. I think that the program is from Cryslat Systems which it says there to."

    That is not a Keil product.
    This forum is specifically for discussions about Keil products:
    http://www.keil.com/forum/

    You need to find a different forum - one that deals with your particular product.

    "It has a label sayings Dell on it."

    So it's a PC part?
    Keil tools are for developing embedded microcontroller products - not PC applications.

    Again, you need to find a different forum relevant to your question.

    This also explains why your questions make no sense to the people on this forum, and their answers make no sense to you!