Getting Started: Running the “Graphics Object Layer Palette” demo
The demo is the same as the “Graphics Object Layer Demo”. The only difference is that this version of the demo will only run on the PIC24FJ256DA210 Development Board (Part Number: DM240312) with the color look up (CLUT) enabled and the Low-Cost Controllerless (LCC) Graphics PICtail Plus Daughter Board (Part Number: AC164144) running at 8BPP color depth. The images used in this demo are specially processed to share a common palette.
The “Resources” folder also contains the xml project used to generate the images stored in the internal flash memory. Open the file in "Graphics Resource Converter" utility to see which files are loaded from internal flash memory.
· InternalResourceObjectLayerPalette.xml
To run the demo in the supported Development Board combination, set the proper hardware profile in the project HardwareProfile.h file:
· To run the demo on selected Development Boards using QVGA display and display buffer is placed in internal RAM use:
#include "Configs/HWP_XXX_INT_QVGAv1.h”
· To run the demo on selected Development Boards using VGA display and 4-wire Resistive Touch Screen Driver use:
#include "Configs/HWP_XXX_VGAv1.h”
· To run the demo on selected Development Boards using WVGA display and 4-wire Resistive Touch Screen Driver use:
#include "Configs/HWP_XXX_WVGAv1.h”
· To run the demo on selected Development Boards using VGA display and AR1020 Touch Controller use:
#include "Configs/HWP_XXX_AR1020_VGAv1.h”
· To run the demo on selected Development Boards using WVGA display and AR1020 Touch Controller use:
#include "Configs/HWP_XXX_AR1020_WVGAv1.h”
Where: XXX represents any of the selected Development Boards.
The hardware profile file name refers to the combination of Development Boards that are used to run the demo. Refer to the abbreviations summary (link) for details.
The table below shows the hardware set up for the selected Development Boards attached to different Display Boards:
Required Hardware/Configuring the Hardware
|
Selected Development Boards |
Resistive Touch Controller |
3.2″ QVGA Truly TFT Display Board (AC164127-4) |
5.7″ VGA Truly TFT Display Board (AC164127-8) |
7.0″ WVGA Truly TFT Display Board (AC164127-9) |
|
PIC24FJ256DA210 Development Board (DM240312) |
Resistive Touch Screen Software Driver |
✓(see note 1) |
☑(see notes 2, 3) |
☑(see notes 2, 3) |
|
PIC24FJ256DA210 Development Board (DM240312) |
✗ |
✓(see note 1) |
✓(see note 1) |
|
|
Low Cost Controllerless (LCC) Graphics PICtail™ Plus Board (AC164144) |
Resistive Touch Screen Software Driver |
✓ |
✗ |
✗ |
|
Note: 1. When using the 4-wire Resistive Touch Screen driver make sure the jumpers are set properly: PIC24FJ256DA210 Development Board - JP8 – closed (PMBE1 must be enabled) - JP9 – set to 1-2 (use Y- signal) - JP10 – set to 1-2 (use X+ signal) - JP11, JP12, JP23 – don’t care - JP13 – set to RG8-S1 (use S1 switch) - JP14 – set to RE9-S2 (use S2 switch) - JP15 – set to RB5-POT(RB5) (use potentiometer)
5.7” or 7.0” TFT Display Board - J1, J2, J3, J4 – set to (2-3) (use MCU signals) - J5 – don’t care 2. When AR1020 is enabled in this hardware configuration. The potentiometer will not be enabled since the potentiometer measurement is performed in the resistive touch driver which is replaced by the AR1020 driver. 3. When using the AR1020 make sure the jumpers are set properly: PIC24FJ256DA210 Development Board - JP8 – closed (PMBE1 must be enabled) - JP9 – set to 2-3 (use TC_CS signal) - JP10 – set to 2-3 (use PEN_INT signal) - JP11 – set to 2-3 (enable PMA17 to SRAM since display buffer requirement needs PMA17) - JP12 – set to 1-2 (use BKLT_PWM signal to drive the display backlight) - JP13 – set to RG8-S1 (use S1 switch) - JP14 – set to RE9-S2 (use S2 switch) - JP15 – set to RB5-POT(RB5) (use potentiometer) - JP23 – don’t care
5.7” or 7.0” TFT Display Board - J1, J2, J3, J4 – set to (1-2) (use AR1020 signals) - J5 – closed (if LED is used to show interrupt signal being asserted) 4. The demo is not limited to the selected display boards used here. Other display boards can be used with the appropriate hardware profiles.
|
||||
|
Legend: |
|||
|
✓ |
Supported out of the box |
☒ |
Hardware compatible, will need firmware modification |
|
☑ |
Supported, see limitations |
✗ |
Not supported, hardware not compatible |
Please refer to the “Graphics Object Layer Demo” for the detailed description of the demo.
Trademarks:
The Microchip name and logo, the Microchip logo, MPLAB, and PIC are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
PICDEM and PICTail are trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
SD is a trademark of the SD Association in the U.S.A and other countries
Microsoft, Windows, Excel, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.