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

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).

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)