How to init touch screen

Kha Man Huynh

my init is the same

The same as what?

Kha Man Huynh

but it didn't work

Then it cannot be the same!

Kha Man Huynh

Can anyone help me ?

Not based on the information you've provided - or, rather, the lack of it!

I suggest that you start with one of the provided examples, and work from there...

Kha Man Huynh

I'm new

New to what, exactly?

• New to any form of programming?
• New to microcontrollers?
• or what?

Many share your difficulty in, "creating a new project."  So many things have to go right - even one "missed" setting will yield errors - derail your progress.  So - do you really "need" a "new project?"  You can build your understanding/experience with your IDE by staying with a "provided" project.  You can add a numeral suffix (test.c becomes test1.c) - which maintains the original file.  You must read, understand & comply with the IDE's instructions to "remove" this single, original file - and then "add" the renamed/copied file.  This should work.  

Before you attempt your "new project" you must carefully note - and log - "ALL" of your project's settings - especially those which involve "finding" files, and other file or tool linkages.  Even with years of use - we find it easiest/less frustrating to simply "copy" an existing project - then rename it - and then add it to our workspace.  This is NOT fully automatic - several key IDE files then must be renamed or otherwise "tweaked" - but it is much simpler than starting a project completely from scratch...

I'd bet that several hundred such "new project then Boom!" posts lurk in this (and other) ARM forums.  IDE tool providers care/skill at clearly detailing, "new project creation" seems "not" to match the otherwise neat capabilities of their IDE...  (IDE creators are likely "too close" to their creation - cannot imagine the multiple pitfalls we mortal users face...)

BTW - should not your post's subject be, "Creating a New Project," - rather than "init a Touch-Screen?"  Future searchers will "not" be pleased...

As Andy said, you really don't provide enough information here to help someone else have an idea of what may be wrong. If you can provide more useful on the problem (for example, I presume you've run your code in the debugger? Is the touchscreen ADC interrupt service routine getting called? Is the system faulting? If so, where?) we will have a better chance of pointing you in the right direction.

In the meantime, if the code is not faulting due to a peripheral that you are accessing without calling SysCtlPeripheralEnable first, I'm willing to guess that your problem relates to not having hooked the touchscreen driver's interrupt handler in your startup_rvmdk.S file. Did you copy this from another project that uses the touchscreen? If not, take a look at one of the examples that does use the touchscreen and make sure you have TouchScreenIntHandler hooked to the ADC3 vector.

This reporter continues in the belief that poster's issue extends "far beyond" touch-screen init.  The "Create NEW Project" issue is the gorilla in this room - and has been (seemingly) "ducked." 

Specific "touch" advice appears "spot-on" - but avoids the growing, "NEW Project disenchantment."  BTW - poster clearly states that touch screen & related code all DID WORK - issue arose "only after" his, "NEW Project" attempt. 

I agree with you 100%. We're aware of the general confusion related to creating new StellarisWare projects on all the supported GUI toolchains and you can be assured that we're working on making it a lot cleaner and easier.

Thank you Sir - when the "event counter" over-flows - perhaps "time is right" to deal with the real issue.  (I know big firm has inertia - and you did respond timely and with great specifics - but "someone" had to point toward the obvious)

Not content to "confine meddling" - much earlier raised this flag w/Blake.  I'm told he posted my suggestion "high on pile" from "unsolicited/crazies."   Ah - status at last...

I found out my problem that SW-GRL-UG-7xxx.pdf is not in My Stellaware. I'm terribly sorry because of the little information but I think if anyone works with it a lot, so they will answer this problem quickly.Thanks you for replying this thread

I has just finished my project with my LM3S9B92 & LM3S6618 design board that using Ethernet,sd card, graphic LCD , ... It's new for me, moreover, debugger such as ULINK, ICDI made me debug a lot . I can't find what my problem is , for ex, invalid rom, cannot access memory , especially at that time i didn't know about it & stellaris MCUs are not popular in my country

JLINK is the best tool debugger Stellaris MCUs indeed.

However, it didn't related to this subject. In SW-GRL-UG (that found in another Firmware package) give a lot information about graphic 3.5" :D. Specially I'm very interested in the programming way of TI, very very excellent although it's hard to understand.

I don't know why most of Stellaris MCUs are so HOT ? Will they die in a unlucky day ?

Well, however STM32 will be the best in ARM M3 branch because of its performance & price. Stellaris may be in 2nd or 3rd because their documents are so strange for learning to design & they are very expensive. For example, I'm newbie, when I see ICDI design & JTAG debugger with ICDI, their components are so strange. Why don't you make easy designs for students to learn ?

I think Ethernet on chip is only thing for you to consider using Stellaris (>6000).

Uh oh - "time to run for the hills..."   Ai Carumba...  How "could" we have known?

Interesting. If you did not include grlib in your project, you would have seen linker errors when you tried to build the project. From your initial post, I assumed you were seeing a runtime error after downloading so that prompted my original suggestions. I'm glad you got the problem fixed, though. You mentioned that you were using a dk-lm3s9b96 board and the StellarisWare release for this board includes the graphics library. The releases for boards which contain no displays (like the ek-lm3s9b92 and ek-lm3s9b90), however, do not include grlib since it would be rather confusing. As for any other component of StellarisWare, even if your board's release doesn't include a component, you can download it separately from the http://www.ti.com/stellarisware.

Regarding usability of StellarisWare, we spend a great deal of time trying to make the software as easy to use as possible. All kits are tested by people unfamiliar with the boards and software to make sure that they can be brought up in 10 minutes or less using the provided instructions as we promise. If you are having problems, please send us suggestions for improvement or let us know the areas that you think are confusing and it's pretty likely that you'll see changes in the next release to address those concerns.

Your choice of MCU will obviously depend upon the requirements of your project and there will definitely be cases where you can't use a Stellaris part for some reason or another. In cases where parts from a competitor and Stellaris parts both fit your requirements, however, take a look at our competitors' software offerings and play with their boards and I'm willing to bet you'll change your opinion about the usability of StellarisWare :-)

Always glad to help!

For the "Popular Post" widget in regards to E2E and current slate of development we are looking at fixes for this in 1H 2012. In the short term efforts like the Code Composer Forum have opted to remove it all together and gone with a manual based approach for curating most relevant forum threads.

Blake

First half 2012 is long time to "keep" never-functional "popularity gauge!"   Especially when (and previously noted) alternative use of such vital space is, "on the table."

I know that (you/TI) are not "ready" to implement such change - as past suggested.  However sometimes even "imperfect" first-pass "safeguards" serve as a substantial improvement over, "lost/meaningless holders" of such priority space!  Cannot - should not - this errant popularity gauge be moved to a screen location of less prominence?  (thus providing "prime space" for (others/I believe) meaningful MCU safeguards...) 

Preventing issues is most always preferable to (forgive me) their harder, more expensive "after the fact" fix...

Kha Man Huynh

JLINK is the best tool debugger Stellaris MCUs indeed

On what basis?

Kha Man Huynh

the programming way of TI ... it's hard to understand

What, specifically, is hard to understand?

Kha Man Huynh

STM32 will be the best in ARM M3 branch because of its performance & price. Stellaris may be in 2nd or 3rd because their documents are so strange

If you're using the same STM32 documentation that I've seen, I fail to see how the Stellaris documentation can in any way be called "strange"!!

Kha Man Huynh

... for learning to design

Neither the Stellaris nor the STM32 documentation is intended to teach you to design; ST and TI are manufacturers - if you need to learn how to design, then you should be seeking a training provider...

(having said that, both TI and ST do provide seminars, etc)

Kha Man Huynh

Why don't you make easy designs for students to learn ?

I think Stellaris kits are ideal for students to learn on - but the student must have have the necessary background, and needs to put in the effort to study the supporting material

I certainly agree with your assessment and we push as hard as we can for improvement. Some items require longer given current projects and development schedules. Feedback like this is great for us being able to potentially escalate items quicker.

For this the solution we have for Code Composer or similar could potentially work here in the interim if stakeholders in the Stellaris forum are willing to do so.

You Sir - truly/ever the diplomat.  (so expected you to tell me how you "really" felt - where I should go...)   (and you do realize that now - past 17:00 local - my "forum rescue rate" rises to 1.5x "normal")   As Army Lt we were taught less, "let's see" - more CAN DO...

Quick update cb1, we are in the process of reviewing this to see what we can do in the short term in regards to popular widget and trending/important threads. Content curation will take longer but will see on getting more traction there. For hours of operation, I try to be on here 24/7 save for when I sleep.