What device comes on the OMAP35x Mistral EVM (TMDXEVM3503)?

I had same confusion for a long time. Thanks for clarification!

I would also add that because OMAP35x parts are closely related (e.g. OMAP3503 is subset of OMAP3530), it made sense to build one EVM (with the OAMP3530 which includes all features of course) to support all OMAP35x platforms.  If you are building a product around OMAP3503, you simply refrain from using DSP or GFX functionalities on EVM during your prototyping/evaluation phase.

This is definately the case, there is no need to have a development board that uses a subset device like the OMAP3503 since the cost of the silicon for these boards is small relative to the board itself. You actually find this practice across pretty much any EVM/DSK we sell (not just OMAP and Davinci), it will almost always contain the superset or 'flagship' part of the device family the EVM represents.

I recompiled my kernel with 3530 option and fired it on my board. Everything else (root.jffs, uboot, x-loader) are as it is. At the time of booting, it says uncompressing done, booting kernel. But kernel does not boot after this. It hangs. If EVM has 3530, it should boot. Did I miss anything? I have Omap35x revision D EVM from Mistral.

You are correct that it should work.  Things to consider

1) Are the other software components (especially root.jffs) from the same DVSDK version?  Sometimes, this can cause problems.

2) It has been a while since I touched an OMAP EVM, but I believe the SDK software comes with pre-built Linux kernel binaries; if so, can you give those a try?

I downloaded dvsdk_setuplinux_3_00_00_13.bin and I had already omap35x_sdk_setuplinux_1_0_0.bin with me. I thought I can compile kernel with OMAP3530 option and then run example code from dvsdk_setuplinux_3_00_00_13 subfolder. I hope there is no new map35x_sdk_setuplinux_1_0_0.bin corresponding to DVSDK.

The SDK package is the same for the DVSDK, the DVSDK just adds on new tools to the existing SDK for 1.0.0. Even the kernel binary that comes with SDK 1.0.0 should work with the DVSDK software. If you have not already you may want to try setting up your U-Boot to boot the 1.0.0 kernel via TFTP (to ensure you are using 1.0.0 kernel) and boot the file system over NFS into the DVSDK target filesystem (dvsdk_3_00_00_13\targetfs). This should get you up and running with the demo application that is described in the DVSDK getting started guide, at least this worked for me, I do not recall having to rebuild the kernel for the DVSDK to work.

In order to track down the 'real' issue, I would recommend trying things out with the pre-built Linux kernel and default file system per Getting Started Guide; if you can get this running, and only replace the Linux Kernel with the one your built, and things break, then we can focus on the Linux Kernel build process.  It may be that your Linux kernel build is fine but there are other issues with the system set-up; with so many variables, we do not want to spend too much time focusing on the wrong software component.

Following along with what comes on the Mistral EVM, the documentation that Mistral provides says the processor module comes with either the Samsung POP flash/SDRAM chip or the Micron POP flash/SDRAM chip.  When ordering this EVM from TI is there any way to tell or specific which one I get?  I personally would like to get the processor module with the Micron chip on it.

Thanks

Gary

I believe the older EVMs shipped with the Samsung, but all newer boards will have the Micron chip on it.   Unfortunately, there is any way to specify, it depends on when you ordered your EVM.

I believe pretty much any board you order now will have the Micron device on it, so you are in luck :). My understanding is that only the really early boards had the Samsung memory (my EVM included), but that production has since shifted to the Micron based processor modules.