| ??? 12/06/06 19:32 Read: times |
#129094 - Oh no it doesn't! Responding to: ???'s previous message |
Richard Erlacher said:
The hardware problem doesn't explain his statement:
Priyanka Gupta said:
"... and using same program and only define : unsigned int xdata buff[BUFF_SIZE] = {'P','R','I','Y','A','N','K','A'};
Then it displays all characters right . Output is : PRIYANKA And i dont understand why only takes int (datatype) to display right characters and why not with char datatype ... " This wouldn't happen with a hard-stuck address line, would it? Yes, it could. If so, the simulation using data type int should have revealed why as well, shouldn't it? Only if the simulation could simulate a stuck-at address line. Since we don't have physical evidence, we can't claim it's faulty construction technique, and since we don't have evidence, we can't claim it's defective components. True, we don't have conclusive evidence - but I think we have sufficient evidence to make the stuck-at address line our prime suspect... If he had an oscilloscope, he'd already have seen that the LSB of the low address byte doesn't change at the correct rate... Hmm... Given that he doesn't even seem to understand the concept of a stuck-at address line fault, maybe not... |
