We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
We're using AT89C51ED2, and now are busy with a problem, witch was caused by reading back the content of XRAM. As it is officially published in datasheet, this MC has 1792 bytes of internal XRAM. We have set the XRS's bits for selecting the full size of XRAM, and cleared the EXTRAM bit, and EEE bit, mapping the XRAM segment. After that, we are writing data to XRAM using MOVX @DPTR, A procedure. After we have reashed the last adress we are trying to readback the data from XRAM and it is not correct at all.
To Mark Hickman You've said you've been using this model. Did it bring you any problems. You see? it is the first time we've chosen this MC and the first task for us is to test it for confirming its reliabness. We've studied the atmel's errata docs, they says about reinterrups, witch takes places using timer 0 and 1 in X2 mode. Nowdays we have not yet confirmed it. We have experience of using AT89S8252, and found a problem with flash RAM, witch sometimes after several resets and power-downs, cleares itself. We'll test C51ED2 for this later. May be there is something more?
hi, they says about reinterrups, witch takes places using timer 0 and 1 in X2 mode No, it occures only if the timers in different X2 mode: either Timer 1 in X1 and Timer 2 in X2 or vice versa. Regards, Oleg