The idea would be to get the O/P to decide whether his problem is hardware or firmware. Whether he's right or not doesn't matter so much.

It's just a question of putting it in a category. Goodness knows, most of the questions initially asked border on the inane. They're either too general, or barely relevant, or totally "barking up the wrong tree", though they do reveal where the O/P's thought, what little there has been of it, has led him.

Generally, driving a display of any sort is a hardware problem right up to the point at which data has to be processed, timed, and transferred. Then it's a firmware problem. One can't expect a total newbie to understand the difference. One can expect him to make a choice, though. "Am I unable to make the display work because I don't know how to select and to interconnect the hardware bits, or is it because I don't know how to manipulate the signals in the MCU? ... could it be because I don't know how to search?" After all, those problems have been solved dozens of times on 8052.COM.

RE