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

how long is the time

Hi friends,i must have you help for this Cereous problum,

i have a code about a digital thermometer using the proc baord. I have compiled this code in microvision ide And the code is compiled and Built with some warnings and it works very Well.

The point is that i have built the circuit in time and it works perfectly.

the code isthis


int wait_1second ( void) delay

{
   int delay_count ;

    delay_count = 100000;

label:

    delay_count = --delay_count;

    if ( delay_count > 1 ) goto label;

    end_label:
}

}

I burn the proc whith the .hex generated and my LCD just show squares and charactors .

I have written the same code using other one and it works perfectly, i don't use assembler, thats the reason why i'm here asking for help. I put this circuit in files .asm & .hex for you to see.

Thanks in advance

Parents
  • Wow I'm not sure weather to say "that's amazing" or "that's dismaying"

    However most if not all programmers are somewhat unaware of there own mistakes. It is the same reason why one cannot proof read there own documentation safely (it just doesn't work because your BRAIN fixes the problem without you noticing it as you know what you said).

    It would be great if one had used a language for 10 years and new it by heart, however new programmers pop up every day. Doing the same mistakes the prior generation warned them NOT TO. (Some think they are even clever.) Back to the point, it's very difficult for someone to see something wrong with there own code. This is why sometimes it's good to flow chart what your code is doing and then ask yourself "does this make sense"?

    hence the ancient phrase "a man is always right in their own eyes"

    Stephen

Reply
  • Wow I'm not sure weather to say "that's amazing" or "that's dismaying"

    However most if not all programmers are somewhat unaware of there own mistakes. It is the same reason why one cannot proof read there own documentation safely (it just doesn't work because your BRAIN fixes the problem without you noticing it as you know what you said).

    It would be great if one had used a language for 10 years and new it by heart, however new programmers pop up every day. Doing the same mistakes the prior generation warned them NOT TO. (Some think they are even clever.) Back to the point, it's very difficult for someone to see something wrong with there own code. This is why sometimes it's good to flow chart what your code is doing and then ask yourself "does this make sense"?

    hence the ancient phrase "a man is always right in their own eyes"

    Stephen

Children