How to setup uVision4 project for MCB2929 EVB

Your analogy with a car fails badly. If you buy a car, you are normally an end user intending to use the car for transport. You don't buy it as a evaluation/development kit.

If you buy a development board, the development board is not intended for end user mass products. You normally buy a development board to get a soldered copy of a processor you want to experiment with.

For things built into the processor (UART, SPI, ...) it would then normally be the CPU manufacturer who should supply examples how to use them.

For external hardware, like a display connected to the CPU, it should normally be the board manufacturer, as integrator, who should spend time documenting the design and how to access the display.

When interfacing external RAM to a processor, it's normally the CPU manufacturer who have to be the main source of information how to do it.

Having the board manufacturer supplying a large number of sample code that can be directly compiled is of course a bonus. But not a primary goal with a development board. That is also the reason why many CPU manufacturers explicitly buys services from board manufacturers to create reference boards - because the CPU manufacturer is responsible for supplying documentation/samples while a manufacturer of compilers and development boards have the supply chain for distributing adapted sample code with the boards. Remember that without explicit backing from the chip manufacturers, the board manufacturers will not have access to any more information than you, as CPU buyer, also have access to.

But back to your car analogy - how many car manufacturer have you seen that sells evaluation kits/development kits for allowing a buyer to experiment with a specific break system, V8 engine or air condition?

Your analogy with a car fails badly. If you buy a car, you are normally an end user intending to use the car for transport. You don't buy it as a evaluation/development kit.

If you buy a development board, the development board is not intended for end user mass products. You normally buy a development board to get a soldered copy of a processor you want to experiment with.

For things built into the processor (UART, SPI, ...) it would then normally be the CPU manufacturer who should supply examples how to use them.

For external hardware, like a display connected to the CPU, it should normally be the board manufacturer, as integrator, who should spend time documenting the design and how to access the display.

When interfacing external RAM to a processor, it's normally the CPU manufacturer who have to be the main source of information how to do it.

Having the board manufacturer supplying a large number of sample code that can be directly compiled is of course a bonus. But not a primary goal with a development board. That is also the reason why many CPU manufacturers explicitly buys services from board manufacturers to create reference boards - because the CPU manufacturer is responsible for supplying documentation/samples while a manufacturer of compilers and development boards have the supply chain for distributing adapted sample code with the boards. Remember that without explicit backing from the chip manufacturers, the board manufacturers will not have access to any more information than you, as CPU buyer, also have access to.

But back to your car analogy - how many car manufacturer have you seen that sells evaluation kits/development kits for allowing a buyer to experiment with a specific break system, V8 engine or air condition?

As you said, this was analogy. But, at the bottom line, it seems that nobody on this forum doesn't know how to use external SRAM on MCB2929 EVB. Maybe, even the Keil programmers haven't tested the external SRAM on their own evaluation board.

Am I right, or am I right?

With best regards,
Dragan Kujovic