• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 20 subscribers
  • Views 6301 views
  • Users 0 members are here
Options
How was your experience today?
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

is volatile array needed?

chao lin

There is a string buffer referenced by both an ISR and the main(). The ISR collects a sentence from UART and put it into the buffer. Once the received sentence is completed a flag is raised. The main() checks the flag and copies the sentence to another buffer. The code is like

unsigned char xdata RxBuffer[];
unsigned char xdata buffer[];
bit RxFlag = 0;

void uart( void )
{
  //receive data from sbuf
  RxBuffer[] = sbuf;
  //if done
    RxFlag = 1;
}

void main( void )
{
  while( 1 )
  {
    if( RxFlag )
      strcpy( buffer, RxBuffer );
  }
}
The question is "Should I declare RxBuffer as volatile?" RxFlag doesn't need to be volatile because it is an automatic variable. The assembly code is "JNB RxFlag, xxxx". By the way, strcpy() is a reentrant function and the UART is at 4800 bps. The worst case is while strcpy is coping data, RxBuffer starts storing another new sentence. The purpose is to keep the integrity of the received data very time. I know I can use ES = 0 and ES = 1 before and after strcpy().

Three more questions:
1. Do I misunderstand the usage of volatile on array?
2. Does the reentrancy play any significant role here?
3. What is the difference between memcpy() and strcpy()? What are the advantages and disadvatages on each?

Thank you for answering my questions.

chao.

0