Hi Troy, Thanks for the fast reply. I was just making sure I was not missing anything. I have been getting spoiled lately with MCU hardware FIFOs. On another note I have been using the GTT for a year now as a proof of concept testbed. I would like to use it in my company's higher budget specialty di...

I am running my GTT at 115200 over the ttl connection. When the unit is sending a touch response for touch region 1 the communication flows as follows: <0xFC><pause ~690us> <0x87><pause ~900us> <0x00><0x02><pause ~500us> <0x00><0x01> Is this typical. It was timing out my hardware FIFO. I have worked...

I added a "00" as the last byte in the file with my binary editor and it has appeared to solve the "Waiting for debug commands..." issue. A raw HEX command of "00" in the support tool's command tab will accomplish the same thing before you save the AUTOEXEC as a binary....

The .gsf extension on the AUTOEXEC was my problem all along, however another issue has me a little puzzled. Even with just a beep command in autoexec the GTT's screen displays "Waiting for debug commands...." after the autoexec has executed. The only thing the support tool's debug view sho...

Thanks for the quick response Troy, here and the TTL question I submitted through the support link on the website. I have been itching to get my MCU board layout finished and sent out. One less 232 transceiver is always good. Don't mean to be needy but I came across a few other things I am curious a...

My bitmap editor was corrupting the the bitmaps upon saving. Switched to MS Paint and everything works fine. Still curious as to how much ram is available for the buffer, and the test connection button still crashes the evaulation software. I have no real use for the test connection feature, however...

I am having a hell of a time trying to get any .bmp, .gif, or .jpeg to load into the bitmap buffer. I have tried different sizes (250KB-2.2MB) and types of these files with no luck. Always get the "out of RAM storage" error. I have seen this question asked before but never answered "W...