I am trying to program a TFT LCD Display with an ITEK ILI9163C Driver attached. Is this the correct software to program this controller?
Err. Did you miss something in that message? What attachment?
Hint: this forum does not support the inclusion of attachments
Apart from that, it is a well structured post that clearly took a lot of consideration and effort to ensure sufficient detail is included to allow others to understand your question.
No, he wasn't talking about any attached document, but hardware attached to the LCD.
But what he forgot to mention was what processor he is using.
And what software he was referring to as, "this software"...
Reading it again, I see you could be right.
But in the grand scheme of things, that correction barely helps :(
"And what software he was referring to as, 'this software'..."
For some reason, lots of people fails to realize that to be able to expect a great answer, they have to start by asking a great question. With a bad question with lots of missing information, the responders has to guess. And it's way easier to ignore bad questions instead of investing time on writing answers based on guesswork.
ITEK does not google well, DigiKey does not know the ILI9163C provide a link to the datasheet
It seems like the OP has disappeared for the duration.
About the easiest way to get a display such as the one that uses the ILI9163C is to search for an arduino driver and modify it to match your processor and hardware.
Using arduino and ILI9163C as search terms throws up quite a few suitable matches.
But most people who get stuck do not know how to modify code to fit a different processor. That isn't part of the standard cut-and-paste concept.
That isn't part of the standard cut-and-paste concept.
Per, you make me sad. I know that the number of "cut-and-paste artists" calling themselves programmers is growing, but has it become the standard?
Remember that the majority of people needing help aren't professional developers, but people who have bought some Arduino, Rasp.Pi etc and trying to just connect individual boxes into a working program.
This can work quite well, because of the standardized hardware.
There are even a growing number of (self proclaimed) professionals who are from the cut-and-paste camp. I have the misfortune of having a new manager who has already decreed that we should only consider development tools that supply libraries suitable for our chosen platforms; but he still wants me to design those platforms.
My new year's resolution list includes not putting up with such pr@ts.
It's the individual touch with either customized hardware or customized software that makes the difference when it comes to commercial work. Why should a customer buy product A instead of product B, if both products are copy-pasted with practically the same features and quality?
I try to reuse libraries and code. Not copy-paste code found on the net, but code developed to give an advantage in previous projects. So for each new projects the library code gets some new tweaks to match changing requirements or take advantages of hardware improvements.
But whenever library code is moved to new hardware, that does require good knowledge of the new hardware. It's only bit-banged code that manages to isolate itself from all the control register bits of a modern chip.
And it's quite clear that people do not want to spend the hours reading through the datasheet and making sure they actually understand what the processor can do. Or cross-correlate the processor manual with the source code, to understand exactly why each line in the code is needed, and exactly what the line does.
In the end, only the company that has the lowest production costs can manage to sell commodity products. The rest of the companies needs to avoid the price competition by instead making unique products where brand name, quality, functionality, originality, ... will make the customers focus on something else than the purchase price. And such products can't be supplied by merging a number of standard off-the-shelf LEGO pieces by connecting outputs to inputs and adding a few knobs to allow some basic end-user adjustments.
It's just that an original product requires a creative developer. And it isn't the creative developers who normally shows up here - most new threads are written by people who get stuck by just about any unexpected outcome. Be it a missing '}' somewhere in the code, an error message they haven't seen before, two copy/pasted code blocks that doesn't like each other, a file the compiler can't find, some trivial incompatibility between two processor models, a missing declaration in some header file, ...
If people don't want to be creative and inventive and willing to spend their time to come up with (new/improved) solutions to problems, then I don't understand why they bother with programming - it would be so much faster to just buy something from a web shop. The world doesn't need yet another "turn on/off lamp with SMS" box. Especially since many of the "me too" solutions aren't industrial strength and doesn't support 24x7x365 use, taking into account brownouts, issues with the cellular network, high/low temperatures, ...
Creativity isn't part of the schooling, so if people can't be creative when solving problems in school they are not likely to be creative later in life. I just wish the schools would be required to hand out the recommendation "consider another line of work" to some of the students - and have the school be economically compensated so the school doesn't have any economical incentives to pass students that will be liabilities for the companies to employ.
I think they offer that at the local community collage level..
I need to program a Newhaven 1.8" TFT LCD NHD-1.8-128160EF-CTXI-T touch screen display with an Ilitek ILI9163 built in controller.
Can the Keil ARM uVision be used to program this device?
The Key MDK-ARM tools can be used to program devices that has a supported ARM core. It will then be up to _you_ if you will manage to make the ARM core perform the actions needed to handle different hardware interfacing internally/externally to the core.
If you have pen and paper, that isn't enough to answer if you will be able to produce an opera or a New York Times best seller.
Note that you made your post specifying "Toolset None". If you have a Z80 processor, you need tools suited for a Z80 processor. But the Keil ARM tools doesn't support Z80 processors. If you instead use a 8051-compatible device, you need tools that supports 8051-compatible chips. But the Keil ARM tools doesn't support 8015-based chips. If you instead have an ARM processor, you need tools that supports that. In that case, the Keil MDK-ARM might be a good choice. Just that you still have never mentioned what processor you have - Keil MDK-ARM is not a good choice for a 64-bit quad-core ARM chip. And you don't want to port the Linux kernel when it is so much easier to use gcc with such a processor.
If you specified "Toolset None", because you wondered specifically about the editor in "Keil ARM uVision", then the editor can be used with a huge number of different processors, if you just use it together with a compiler tool chain suitable for your processor.
So in the end: It isn't the Keil tools that seems to be the weak link here, which means we can't answer your question based on the information you have posted.
with an Ilitek ILI9163 built in controller.
you STILL have provided no link to datasheets.