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.
Hi: I find the same question I meeted. But I don't understand the content as followed... ..................................... 3. Add the following instruction (ANL 0B1h, #01h) at the beginning of the startup code (BEFORE XDATA is cleared). ..................................... ANL 0B1h, #01h ??? Thanks for any reply.
Whoa! You seem to have just posted something completely out of comtext from an ongoing discussion!
ANL 0B1h, #01h
Probably refer to clearing a bit in a SFT that control the source of XDATA for the addresses where external and internal XDATA both exist. (internal XDATA, do'nt you love it) I suggest EDATA for extended data as the name for this. Now my question: you have an existing design with external RAM mapped from 0000. To gain a bit more RAM withou modifying the hardware, you pop a chip with some EDATA memory in. QUESTION: How do you define which variables are in XDATA and which in EDATA since the addresses are the same - and how do you specify the switch the thread originatot talks about (I know that e.g. Winbond and Philips use different mechanisms). Have fun, Erik