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.
I'm attempting to configure a Dallas 5000 series chip to work with 512k of external memory in "contiguous mode". Here are my memory classes, hopefully indicating a 1k spot (for my stack!) and a code/data partition at 128k:
START END USED MEMORY CLASS ========================================================== X:000400H X:0007FFH 000400H XDATA X:000400H X:0007FFH 000001H HDATA X:020000H X:07FFFFH C:001400H C:00FFFFH 00003CH CODE C:001400H C:01FFFFH 0000BBH ECODE C:001400H C:01FFFFH HCONST
?STACK SEGMENT XDATA AT 0400H RSEG ?STACK DS 1024
error C249: 'FDATA': SEGMENT TOO LARGE
char far s1[0xffff]; /* line 1 */ /* char far s2[0xffff]; */ /* line 2 */
Thinking more on Problem 1, other implications past just 'annoyance' are cropping up, indicating I've probably done something wrong. The standard library's variables, for instance, can't all be made far, so there must be an available XDATA class made somehow.. but if my chip's partition between code and data is at 128k, how are normal (non-far, non-HDATA) variables supposed to be stored?