Hi, hope this info will help you to get started.
To get the Sabre up and running with the demo OS come with the BSP, you need the following :
1. VS2k8 with service pack 1
2. Platform Builder 7 with WCE7. Make sure it is updated with the updates from Microsoft (be warned it will download the updates for almost every platform and it took my installation 36 hours to download the full update package - This is the worst part).
3. Go to freescale site to download the SMD BSP and Multimedia SDK for SMD platform. You can also download all the documents from there.
4. Install the BSP.
5. Install the MM-SDK if you want to use the Freescale Codec. Usually you just install it anyway and does not matter whether you are using it or not. Also it will do some update to the Built environment which can be importance unless you want to do that yourself.
When all this is done (many many hours later) then you can start to compile the first OS using the SMD OS example in the OS Design directory. Make sure that you follow the BSP doc to add in the boot option if you want it to boot up other than from RAM. (if you booting from SD then you need to add in the imgsdmmc = 1 into the built environment - see the guideline in the BSP user guide). One word about the BSP user guide....quite a few errors here and there and has made me wasted many hours till recently that I only manage to work out the solution for SD booting.
6. Once the OS image is generated then you have to compile the Eboot as well. Best to use retail version for now before debug as it is quicker and smaller for both the OS and Eboot.
7. Use the cfimager.exe provided by Freescale to program the eboot.nb0 to the boot media (for SD / Sata devices). Or you will have to follow the user guide if you want to boot the Eboot directly from RAM.
8. Once Eboot is up and running, then it will send BOOTME message over the Ethernet (make sure your development PC is connected to the Sabre via Ethernet - either using cross cable or hub and make sure the PC/Sabre are set to the unique IP on same subnet. Also you will need to connect the Sabre to the development PC via the COM port as well as that's where you have to use any terminal app - like Hyperterminal to configure the network and correct boot options on the Sabre. This step is essential!
9. Once it is configure correctly you should see the terminal message telling you that Sabre is broadcasting the BOOTME message after you select the "download image now" option on the Eboot menu. Then you can click the connect device icon on the Platform builder in VS to connect with the Sabre. After a few while it should start to download the WCE7 OS to the Sabre 9(either to RAM or boot media - depends on what you have specify in the built environment).
10. Then - The most important step if you are using SD to boot the OS image - enter yes to allow the Eboot to flash the downloaded OS image onto the boot media. - Never ever use the cfimager to flash the nk.nb0 as what suggested in the user guide as this will never ever work and has wasted 2 days of my time!!! The CFI tool just simply not able to work out where is the correct jump to address.
11. Once it is down - sit back and enjoy watching the Sabre booting up the Win CE7 image - the booting up can take about 20s - Oh yes, before you reboot the system, make sure you select the boot option is to boot from the correct boot media - such as the SD if you have used the imgsdmmc flag in the built environment.
Well this is just the starting point if you think you can relax now. If you are looking to port your PC .Net app to the WCE7. You need to generate the SDK from the platform builder. Then an installable msi will be created that you can install it on your development PC. Once it is installed you should get a SDK device for imx and you have to re-compile your existing .net application for the IMX platform. It might or might not just work from there - depends what library you have used in the .NET. WCE7 use compact framework which is a lot less libraries included compare to the full desktop .Net framework. You will have to be very lucky to not have use any libraries that is not included for the compact. If you does, then it mean re-write / redevelop that part of the functions / coding.
Hopefully this is helpful to you as it has taken me almost 1 week to set it up correctly and start my development work on the Sabre, thanks for the awful documentation from Freescale with lots of errors and the forever slowing broadband connection when you need it the most.
p/s : In your OS image generation, make sure you also include the compact framework in the catalogue selection.