graphics controller pmp drops out

Hi There,

In response to your questions:

1. I have a DA256 development board and have been testing the code between it and my custom board. The code runs on the development board, but not on my custom board.

2. I'm pretty sure it is not a jumper issue, as the code runs ok on the dev board.  Most of the jumpers have to do with using external RAM, board buttons, or ADC inputs.

3. The LCD datasheet, app not can be found here:http://www.trulydisplays.com/tft/index.html  The model is: TFT-G240320LTSW-118W-E

I have done some further debugging and found that the problem seems to be coming from the intialization of the epmp module.

*  When I initialize the epmp all of the control signals on my custom board run correctly, but the GD15:0 signals latch high.  When I do not initialize the pmp module the GD15:0 signals output pixel data, but incorrect pixel data.

I am having a hard time finding good documentation on how the initialize the pmp port in the case where I am Not using external memory.  For that matter I am not exactly sure why I need to initialize the pmp as I thought its use is to access external memory.  I think that this may have something to do with accessing the extended data space, but I am not sure and cannot find related documentation.

* trying to eliminate use of the pmp module

Based on these observations I have tried to eliminate the use of the pmp, but cannot output correct pixel data information with by not using the pmp module.  I think it is accessing extended data space somehow.  So I may need to configure it so that it does not conflict with external pins, such as my LED, PMA, PMD pins.  I have not been able to do this by trial and error.

* trying to reconfigure the pmp module so GD15:0 do not latch

    - I have not been able to figure out how to configure the pmp module so that the GD pins output correct data.  In the code there is use of CS1 and base CS1 address.  I looks like this is to access external data, which I do not need to do, based on my understanding of the project being built using internal flash for graphics data.

Any more questions I can answer for you?  Are you familiar with the use of the EPMP?  What is your understanding of its use where external memory is not being used?

Attached is a barebones project that has my custom board pin configurations with the ResetDevice() function that intializes the graphics module and the epmpInit() function which initializes the pmp module.  Or the same functions lie deep within the project builds of the microchip solutions graphics library example projects.  The barebones project is enough to simulate the problem I am having.

Thanks for the help!

Hi There,

In response to your questions:

1. I have a DA256 development board and have been testing the code between it and my custom board. The code runs on the development board, but not on my custom board.

2. I'm pretty sure it is not a jumper issue, as the code runs ok on the dev board.  Most of the jumpers have to do with using external RAM, board buttons, or ADC inputs.

3. The LCD datasheet, app not can be found here:http://www.trulydisplays.com/tft/index.html  The model is: TFT-G240320LTSW-118W-E

I have done some further debugging and found that the problem seems to be coming from the intialization of the epmp module.

*  When I initialize the epmp all of the control signals on my custom board run correctly, but the GD15:0 signals latch high.  When I do not initialize the pmp module the GD15:0 signals output pixel data, but incorrect pixel data.

I am having a hard time finding good documentation on how the initialize the pmp port in the case where I am Not using external memory.  For that matter I am not exactly sure why I need to initialize the pmp as I thought its use is to access external memory.  I think that this may have something to do with accessing the extended data space, but I am not sure and cannot find related documentation.

* trying to eliminate use of the pmp module

Based on these observations I have tried to eliminate the use of the pmp, but cannot output correct pixel data information with by not using the pmp module.  I think it is accessing extended data space somehow.  So I may need to configure it so that it does not conflict with external pins, such as my LED, PMA, PMD pins.  I have not been able to do this by trial and error.

* trying to reconfigure the pmp module so GD15:0 do not latch

    - I have not been able to figure out how to configure the pmp module so that the GD pins output correct data.  In the code there is use of CS1 and base CS1 address.  I looks like this is to access external data, which I do not need to do, based on my understanding of the project being built using internal flash for graphics data.

Any more questions I can answer for you?  Are you familiar with the use of the EPMP?  What is your understanding of its use where external memory is not being used?

Attached is a barebones project that has my custom board pin configurations with the ResetDevice() function that intializes the graphics module and the epmpInit() function which initializes the pmp module.  Or the same functions lie deep within the project builds of the microchip solutions graphics library example projects.  The barebones project is enough to simulate the problem I am having.

Thanks for the help!

I thought that graphics data was being saved in internal flash, it turns out that only fonts and bitmaps are based on the defines in the graphicsConfig.h file.  The Demo board projects are all using external RAM with the pmp.  I don't see any options to compile the graphics projects to store everything inside of the PIC.  I understand I will be limited the amount of graphics I will be able to display, color depth, but thats OK.  Do you know of options to build an internal memory only project with the library?

Any ideas?

For Anyone who might run into this same issue.  The defines within the HardwareProfile_xxxx.h in the graphics project must point to valid DA256 internal memory addresses.  All of the projects built in library 2.1 use external memory.  I thought this was confusing in that the font and bitmap files are defined as being stored in internal memory.  Anyhow the following defenitions will get graphics of reasonable size to run on internal memory using the color look up table.  Hope someone might find this useful.  I think I'm going go grab a beer as I just got the graphics running on my custom board . 

#define PIC24FJ256DA210_DEV_BOARD

#define DISPLAY_CONTROLLER MCHP_DA210

#define DISPLAY_PANEL TFT_G240320LTSW_118W_E

#define COLOR_DEPTH 8

#define GFX_GCLK_DIVIDER 61

#define GFX_DISPLAY_BUFFER_START_ADDRESS 0x00004B00ul

#define GFX_DISPLAY_BUFFER_LENGTH 0x00025800ul

#define GFX_WORK_AREA1_START_ADDRESS GFX_DISPLAY_BUFFER_START_ADDRESS

#define GFX_WORK_AREA2_START_ADDRESS GFX_DISPLAY_BUFFER_START_ADDRESS

Congratulations

The combinations of internal / external memory do makes things a little tricky

regards