bjhotmail
Junior Member level 2
- Joined
- Sep 29, 2007
- Messages
- 20
- Helped
- 1
- Reputation
- 2
- Reaction score
- 1
- Trophy points
- 1,283
- Location
- South Africa
- Activity points
- 1,407
PIC bad RAM
Hi everyone, hope someone can help. I have on two instances with two different devices (16F877 & 18F452) found that reading a value from a RAM register could sometimes hold invalid data. The proof is that in the CBLOCK i would list that register as BADRAM and give the data register a new address eg
cblock 0x20
reg1
reg2
reg3
badram
reg4
endc
So now reg4 holds valid data, if it was at 0x23 (for eg) the data would be invalid.
Has anyone else come across this problem before or am i doing something wrong somehow? Any routine (in ASM pref) to check for BADRAM?
Thanks!
Hi everyone, hope someone can help. I have on two instances with two different devices (16F877 & 18F452) found that reading a value from a RAM register could sometimes hold invalid data. The proof is that in the CBLOCK i would list that register as BADRAM and give the data register a new address eg
cblock 0x20
reg1
reg2
reg3
badram
reg4
endc
So now reg4 holds valid data, if it was at 0x23 (for eg) the data would be invalid.
Has anyone else come across this problem before or am i doing something wrong somehow? Any routine (in ASM pref) to check for BADRAM?
Thanks!
