Touch Screen Kits

FDI is committed to providing the best support possible for it's products. If there is an answer that you cannot find or if you have additional questions, you can send an email to our support team. We will respond directly to your inquiry as quickly as possible.

For additional questions that relate more specifically to the manufacturer’s products, FDI provides full service design and development support.

Touch Screen Kits FAQs

Can I debug the board using ULINK2 debugger as it is mentioned as "Mini-JTAG Debug Connector" in the page?
The SOMDIMM-LPC3250 includes a "Mini-JTAG Debug Connector" so a J-Link device can be used to debug the target outside of Linux. Inside of Linux there is information on the internet for setting up a gdb debug session, however, FDI currently does not offer support for this. If you purchase our complete DK-57TS-LPC3250 Kit or DK-57VTS-LPC3250 Kit, it includes a Segger JTAG debugger and the necessary cable to connect to the mini JTAG for debugging.
As the LPC3250 chip does not have internal flash how can I use a debugger and load the code into the external flash provided in the board?
If using Linux, the current method of programming the NAND flash involves using J-Link Commander to download the data into the memory and then program the NAND flash with the U-boot bootloader. Alternatives to using J-Link Commander is a network connection or even a serial download (usually quite slow). It should be noted that Linux executes from on-board SDRAM once it is loaded.
I need to integrate a TFT LCD with touch screen in my project. Is it possible for you to provide hardware, schematics and sample code for the same?
You can review any of our Touch Screen Kits. They are full blown LCD touch screen kits that should be perfect for your application.
On purchase of the SOMDIMM-LPC3250, what kind of support can I expect from you for my further development, such as Errata sheets, Application notes, Sample codes, Schematics, etc?
FDI provides basic hardware and software technical support for all of our products and NXP (or other silicon suppliers) provide data sheets, App Notes and other support for their ICs. FDI also offers full design customization for our Touch Screen Kits into customer applications, and we would be happy to provide you with a quote if you will e-mail us your requirements.
The website lists “Segger JTAG Debugger with cables.” Is this included in the kit?
The Segger JLink Lite is included with the DK-57VTS-LPC2478 and all other Touch Screen Kits from FDI. The JLink Lite is a low cost, custom JTAG debugger designed by Segger for use with NXP Development Kits. It will work with IDE tools that support ARM microcontrollers and Segger JTAG debuggers. The JLink Lite works exactly the same as the JLink except the download speed is only about 33% that of the full price JLink and the +5V is constantly powered vs. switched on the JLink. Segger does not sell the JLink Lite separately. If a customer wants to have a high speed, full featured JTAG debugger, Segger recommends that they purchase the JLink at current market prices.
Image of a JLink Lite
Can't get the Segger JTAG connected to the SOMDIMM-LPC2478 Module.
Download the following instructions to connect the Segger JLink Lite to the SOMDIMM-LPC2478 Module: SOMDIMM JTAG Connector Fix.
I accidently lost SIBL on the LPC3250 and need to get it back.
Download the following file to help get SIBL back: SOMDIMM-LPC3250 Programming SIBL.
Do you have an adapter to convert from the standard 20 Pin 0.1' JTAG header to the 10 Pin header on the DIMM Modules?
Unfortunately, we do not provide an adapter cable for the larger JTAG cable. All current units are now including a Seggar JTAG ULink Lite, which will connect directly to the SOMDIMM JTAG connector.
Also - download this drawing for creating your own adapter cable if you wish.
What are the Current Measurements for the SOMDIMM Modules?
Conditions: DIMM modules are installed into a ‘bare’ CARRIER PCB with only minimal decoupling and the Ethernet Combo Jack, and NO other additional circuitry. No LCD, no RS232, no 3.3V regulator, etc.
Measurement Method: Using a cable from the I2C header, the 5V & 3.3V rails are connected to the BK Precision Dual Output power supply. Current measurements were taken using Fluke 189 Meter in circuit.
SOMDIMM-LPC3250:
State: Power On, performing boot process
5V = 0.017A
3.3V = 0.148A
State: Linux booted and sitting at the ‘login’ prompt
5V = 0.002A
3.3V = 0.185A
Observed max:
5V = 0.025A
3.3V = 0.333A
SOMDIMM-LPC2478:
State: Booted at the μEZ Screen
5V = 0.000A
3.3V = 0200A
Observed max:
5V = 0.002A
3.3V = 0.208A
Do you supply all the source code of the software?
uEZ™ is an open source GPL project available at uez.sourceforge.net. There is no cost to use the software.
Do you need strictly to use the FreeRTOS or is it possible to have C-examples without an OS?
uEZ™ was developed using a RTOS model and requires one to operate properly. FreeRTOS is provided with uEZ™, but if another RTOS is required, uEZ™ has been developed to be RTOS portable.
What kind of Graphical Libraries do you supply in order to manage the TFT? Are they supplied as open source code?
uEZ™ includes the SWIM Graphical library. Basic features for drawing on the display are provided (lines, boxes, etc.). This code is included in the uEZ™ release. In fact, the demonstration that comes with the kit makes use of the SWIM Graphical Library.
Do you supply the source code about the USB management as Host? If yes, are you able to manage FAT32-File System and extended file names?
Yes. uEZ™ includes a USB Host driver and FATFS file system. Long filenames are not provided, but a FAT32 drive with short filenames is supported.
Can I use the uEZ with the IAR compiler?
uEZ™ does support the IAR compiler and the default project file can be found at uEZ_SRC/uEZ.eww within the downloaded files.
I suspect the software is configured for the 5.7" display and I have the 3.5" display. Can someone tell me how to change the settings so the 3.5" display will work?

The option to change the LCD is in a file called Source\App\Config_App.h

You need to comment out #define for the Toshiba QVGA and remove the // before the #define for the Okaya 3x5.

Should look like this when you're done...

// Configure LCD screen being used and pull in the specific setup 

// information for that LCD. See Types/LCD/Config_LCD.h for a list.

//#define UEZ_DEFAULT_LCD_CONFIG     LCD_CONFIG_TOSHIBA_QVGA_LCDC_REV2

//#define UEZ_DEFAULT_LCD_CONFIG     LCD_CONFIG_TOSHIBA_QVGA_LCDC_3_5

//#define UEZ_DEFAULT_LCD_CONFIG     LCD_CONFIG_OKAYA_QVGA_LCDC_3_5

//#define UEZ_DEFAULT_LCD_CONFIG     LCD_CONFIG_OKAYA_VGA_LCDC_3_5

#define UEZ_DEFAULT_LCD_CONFIG       LCD_CONFIG_OKAYA_QVGA_3x5_LCDC_3_5
How can I change the settings so the 5.7" Okaya VGA display will work?

The option to change the LCD is in a file called Source\App\Config_App.h

You need to comment out #define for the Toshiba QVGA and remove the // before the #define for the Okaya VGA LCDC_3_5. LCDC_3_5 refers to the LCD CARRIER board number and not the size of the display. VGA refers to a resolution of 640x480 instead of a QVGA resolution of 320x240.

The code should look like this when you're done...

// Configure LCD screen being used and pull in the specific setup 

// information for that LCD. See Types/LCD/Config_LCD.h for a list.

//#define UEZ_DEFAULT_LCD_CONFIG      LCD_CONFIG_TOSHIBA_QVGA_LCDC_REV2

//#define UEZ_DEFAULT_LCD_CONFIG      LCD_CONFIG_TOSHIBA_QVGA_LCDC_3_5

//#define UEZ_DEFAULT_LCD_CONFIG      LCD_CONFIG_OKAYA_QVGA_LCDC_3_5

#define UEZ_DEFAULT_LCD_CONFIG        LCD_CONFIG_OKAYA_VGA_LCDC_3_5

//#define UEZ_DEFAULT_LCD_CONFIG      LCD_CONFIG_OKAYA_QVGA_3x5_LCDC_3_5

Recompile the code and the unit will work just like the release VGA version.

 

uEZGUI-2478-43WQS

uEZGUI-1788-43WQS

uEZGUI-2478-70WVE

uEZGUI-1788-70WVE

uEZGUI-RX62N-35QT

uEZGUI-EXP1

DK-35TS-LPC2478

DK-57TS-LPC2478

DK-57VTS-LPC2478

DK-57VTS-LPC1788

DK-43WQH-1788

DK-57TS-LPC3250

DK-57VTS-LPC3250

DK-57TS-RX62N

DK-43WQT-RX62N

DK-47WQH-RX62N