Learning to program with MCB-STR9 Evalution board by uVision3. HOW TO DO?

I'm not sure that an STR9 is a particularly good choice for a beginner?

Neither uVision-3 - being well out-of-date.

Actually I updated to uvision4 but board is the same mcbstr9. Which board do u prefer to beginers?

Perhaps you want to look at some that isn't 7 years old, and has current support and following? Perhaps something based of the Cortex-Mx series from TI, NXP or ST?

Where exactly on the learning curve are you? Can you program in C, write applications on a PC or tablet? Any other language experience? Any electronics experience?

Google about a bit for boards being used in the educational world, course notes, etc. Find something that fits your learning needs.

I know C but only normal C. I have no experiance on programming microcontroller with C or other language thats why I am asking this question.
I have programmed at FPGA board with Xiling program but it is different. That is my rducation level.
Thanks...

The LPC21xx are ancient and replaced with the LPC23xx family that have been replaced by the LPC17xx family.

Not sure why it would be too important to care about the "ARM" core compared to the "Cortex" core.

But LPC23xx (ARM7) and LPC17xx (Cortex) have almost identical peripherial devices, making the C code almost directly movable from LPC23xx ti LPC17xx as long as the peripherials are accessed directly.

The LPC21xx on the other hand, have much older peripherial devices that (besides being different) have much more limited functionality. In LPC23xx, NXP took all the feedback they got from the LPC21xx users and fixed most/all important weak spots.

LPC1114 is an excellent device for a beginner. You can even get it in DIL package (LPC1114FN28) so you can craft your own development board. Look on ebay and you can see loads of very capable and cheap development boards.

You can even get it in DIL package (LPC1114FN28) so you can craft your own development board.
I STRONGLY advice any beginner against "crafting your own development board".

in the beginning, the thing you need the least is the question "is it hardware or software".

not to mention that most beginners believe that "a wire is a wire" and end up with non-functioning decoupling etc.

If a beginner want to do hardware, first make something work on a devboard, then make your own hardware and make the same work

Look on ebay and you can see loads of very capable and cheap development boards\
BEWARE, there are a lot of "me too" boards that only function marginally. Buy a board from a well known manufacturer.

Erik

Where is you're sense of adventure?
I have no problem with adventure, but if I were to take up mountain climbing, I would not start at Mt Everest

It would surprise me if even a virgin hardware experimenter would fail to manage to get something like this going.
if done as the schematic show, it will, most likey not work, where are the decoupling caps

I suppose you would want to plug in your logic analysers, ICE etc before you could get blinky going reliably.
as a professional, I use whatever tools that makes the issue get resolved the fastest, 'want to' does not apply

Erik

I'm pretty sure the processor will run fine without decoupling capacitors.

The current consumption is tiny. And it has an internal RC oscillator that is less sensitive than an external crystal. And it has quite a bit of safety margin on the supply voltage.

The issue with it is that it has no reset circuit, so it will fail when power is slowly going down or is having a short dip.

Note that "as a professional" doesn't apply to hobbyists. Good methodology can apply. How to try to design and document before starting to write code can work. But there are often a much different priority between money and saved own time. 10 extra hours looking for problems can be a better choice than paying $50 - because the real alternatives may be 10 hours searching for troubles or not doing anything at all.

I would not start at Mt Everest

Do you really think that the familiarisation of an LPC1114FN28 is anything like the effort required in climbing Mt Everest?

Not sure why it would be too important to care about the "ARM" core compared to the "Cortex" core.
"...But then it would take almost a year to switch to other higher end controllers (for eg: ARM7 or ARM9), which are not the latest ones.
The latest ones are Cortex-Mx series (M0 - 4)
...
Basically, you have to get acquainted with the peripheral interfaces and writing the driver codes for peripherals. as long as you learn peripheral interfacing and driver coding you can choose any architecture and any language"

Have not given importance to any architecture as such. Dont know where did you figure out an 'importance giving statement'? :O
Have left it to the OP to decide what Core he wants to use. :P

I STRONGLY advice any beginner against "crafting your own development board".
I agree with Erik (not strongly though).
It often happens that the passion, the zeal to learn controllers decreases if the person starts from scratch and gets lost mid-way.
Crafting own development board is a good idea, but a long process - designing the schematic, checking net lists, designing the layouts, soldering components on PCB, troubleshooting the board, etc - consuming almost 6-8weeks. also the time period between giving the layout to the pcb designer and getting the pcb (soldered/bare circuit board) is wasted as nothing can be done in that time but just wait for the pcb to arrive. (This is process when designing a new board, YOURSELF - i dont find much adventure here) Buy a development board if you want to avoid these steps.

This is the bottom line...
Basically, you have to get acquainted with the peripheral interfaces and writing the driver codes for peripherals. as long as you learn peripheral interfacing and driver coding you can choose any architecture and any language, any circuit board
i prefer a ready to use development board to begin with, start writing the code, learn peripherals _what i can do with them_ and simultaneously design my own circuit to implement the project/design that i want.

I dnt say others are wrong, but i think this was and is good for me. :)
All the Best (Thumbs up).

Crafting own development board is a good idea, but a long process - designing the schematic, checking net lists, designing the layouts, soldering components on PCB, troubleshooting the board, etc - consuming almost 6-8weeks. also the time period between giving the layout to the pcb designer and getting the pcb (soldered/bare circuit board) is wasted as nothing can be done in that time but just wait for the pcb to arrive. (This is process when designing a new board, YOURSELF - i dont find much adventure here) Buy a development board if you want to avoid these steps.

'scuse me, but did you actually follow at the link I gave? Get a piece of breadboard, insert components, apply power. job done. It takes nearer six minutes rather than six weeks.

I had this bread-boarding method of working with things, but could not get long way as its reliability is doubtful. There are times when circuit dont work, after taking pain in debugging the whole circuit, you find that the circuit wasnt working just because of loosening of components.
But I agree that the idea is good for getting started. :)

And stop involving Middle names. Idiot!! (sic)

Amfortunately, I have readily got "MCB-STR9" Development board for learning. Which include STR912FAW44X6 microcontroller which is done by using 32-bit ARM966E-S RISC processor core.(also I have uVision4 software installed to use)
It is ARM9 which you claimed to learn later after older ones.
Will it be too hard for me to start with it?
Or take 'The 8051' or LPC23xx(ARM7) or LPC1114 and start with them?
If you sujest one of this ways, if possible and if you know, could you also tell what book or tutorial online or any kind of good source for beginners is good?

Thanks too much Dhaval Solanki,Per Westermark, Erik malund, P Magson for your valuable responds...