41
of HCS08 (port E, bits from 0 to 3) are respectively mapped to
Serial Clock
Master Data Out, Slave Data In,
Master Data In, Slave Data Out,
Slave Select (active low)
of SPI module internal to MCU (please note this position is NOT the default mapping, according to data-sheets).
Those are also respectively connected to pins #
14 (SPI_SCLK / DIO18),
16 (SPI_MOSI / DIO16),
17 (SPI_MISO / DIO15),
15 (nSPI_SSEL / DIO17)
of your XBee S2C SMT module.
Knowing this, you could try to drive the display just by properly connecting it to pins 14 to 17 of your XB24CZ7UISB003… provided Digi’s SDK for S2C programmable modules (which, again, I don’t know) lets you access the SPI module of HCS08.
Unfortunately this can’t be taken for granted: in my short experience with XBee3 ZigBee modules, I can tell you MicroPython implementation (which will supplant Digi’s SDK for programming more recent modules, I presume) still lacks lot of useful modules/functions (not just serial interfaces… even basic I/O control!).
For the sake of information, external pins #:
14,
16,
17,
15
of your XBee S2C SMT module are probably connected to internal EM357’s pins #:
19 (PB3),
30 (PB1, or pin #31 - PB2 - if configured as slave),
31 (PB2, or pin #30 - PB1 - if configured as slave),
20 (PB4)
if Serial Controller 1 is used. Otherwise they should be connected to pins #:
Thanks a lot for your response and a detailed description. {I had been away with my exams}
I tried working exactly the way you had told. But I believe there is still some lacking with the model of xbee or the graphic display. Since I am using the sample project provided by the programmable SDK installed with code warrior, it should work. A normal character LCD is working fine but not the graphic display.
can it be an issue with the RAM of flashram