This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello ,
I am woking with the GUI related application migration from DK- Lm3S9D96 to Stellaris launchpad with custom LCD .
initially I managed to play around the library and create GUI application on my DK- Lm3S9D96. late on I managed to get working a LCD ie ETT- TFT320240TP with the launchpad kit. I also ported the GUI Library for the DK- Lm3S9D96 to launchpad but the problem is with the APIs and canvas buid. I have registered the prerequisite function(Drivers) of the LCD to the Driver structure .I am able to use the functions provided by the primitives of the G.LIB but when I try something to be built with the canvas the programs ends up with fault ISR and Callstack show UpdateContextCharacterMapping . I am stuck up this. please help me in this matter ..
thanks ,
VishvesH
I tried debugging the routine. Initially I had written the routine only for plotting the button with no callback . I had inserted a breakpoint at the pixel draw multiple callback. I noticed that in the callback the value of the pointer to data of (g_pucBlue50x50) is wrong (g_pucBlue50x50 is of the "const unsigned char" type) and it is unexpected . what might be the problem . Please }[elp
Thanks in advance .
VishvesH
Hi,
It is extremely hard to help in such situations. We have almost no information here. Using grlib with custom hardware is as easy as writing custom LCD driver. Unfortunately debugging FaultISR is not trivial. It is possible though.
Please check out http://www.ti.com/lit/an/spma043/spma043.pdf - Application Report, Diagnosing Software Faults in Stellaris® Microcontrollers by Joe Kroesche
Regards,
Maciej