I have a single board computer designed after the OMAPEVM, using the OMAP3530 and similar Flash as well as SDRAM. Copying the files MLO, ebootsd.nb0, and nk.bin from the EVM project onto a SD card, I am able to boot our custom board. However, after eboot copies the OS image to SDRAM and jumps to the image launch address, the code crashes somewhere and I no longer see debug messages coming out on the COM3 debug terminal. Using the same SD card on the EVM, it can go all the way to show the window screen.
I added some printfs before the jump to the OS to dump out the first 1024 long words, starting at the launch address. The dumped data are the same between the EVM and our custom board. I also added code in the Eboot to test the SDRAM for the entire space except the Eboot portion. The test passes.
As far as I know, Eboot is running in SDRAM, so SDRAM configurations should be OK. I don't know why the OS does not run?
Does anyone have any suggestions for me on how to debug this kind of problem?
Thanks,
Luan
Have you tried enabling KITL + KERNEL debugger to debug using Platform builder? However this will only help if your kernel is crashing after OAL and KITL have been initialized. Give it a try if you havent done already.
Please click Verify Answer button if this response answers your question. For updated information on TI WINCE BSP, please check out the WinCE Handbook.
My board does not have Ethernet and that was why I tried to boot from SD. I am learning how to use RNDIS USB on the EVM so that I can implement your suggestion but at this time, I have some problem doing that. After power on, I got the following output on the UART3 terminal:
Hit space to enter configuration menu 5...Hit space to enter configuration menu 4...Hit space to enter configuration menu 3...Hit space to enter configuration menu 2...Hit space to enter configuration menu 1...HostMiniInit:: !!Rndis:: initialization: with addr=480AB000Rndis:: Address static map to addr=480AB000Rndis:: initialization!+USBFN::Device ID = 0x4b7ae02f+USBFN::Device ID = 0x4b7ae02fRndis:: PDDInit Success!Rndis:: Get MAC address 200,902F,B5DRndis:: initialization: Fail!ERROR: Boot device driver Init call failed
I also got a window poped up asking to install a USB driver "Microsoft RNDIS KITL for OMAP2430. I do not know where to get this driver. Would you please help from you on this?
Luan,
it seems you are missing the RNDIS driver on the PC side. I vaguely remember I had the same issues when I first used KITL via USB. Now I forgot where I got the driver from (as this is nearly 2 years ago...). However I think you can google this or contact Microsoft for support as this is a generic platform builder issue. I don't think there is a special OMAP RNDIS driver.
Regards.
Here are the steps to use USB RNDIS as KITL device.
Here are the steps you need to follow in order to make USB RNDIS work:
Setup Device:
1. On the debug terminal, press SPACE when prompted. Using the bootloader menu, set the boot device to USBFn RNDIS.
2. Set the debug device to USBFn RNDIS
3. In ‘Network Settings’:
a. Disable DHCP
b. Assign Static IP Address
c. Assign IP Mask
4. In the bootloader main menu, select “Exit and Continue” to download image.
Setup Host PC:
5. Host PC will display ‘Found New Hardware Wizard’
6. Select ‘No, not this time’ and press next.
7. Select ‘Install from a list or specific location then press ‘next’ button
8. Ensure that ‘Search for the best driver in these locations’ is selected. Also ensure that ‘Include this location in the search’ is selected and click ‘Browse” button.
9. In the ‘Browse for Folder’ window navigate to: ‘C:\WINCE600\PUBLIC\COMMON\OAK\DRIVERS\ETHDBG\RNDISMINI\HOST’
10. Press ‘Next’ button. RNDIS Connection is made.
11. In network connections, make sure to set an IP and subnet mask similar to that set on the device.
Example: Set IP as 192.168.1.24 and subnet mask as 255.255.255.0.
12. From Platform Builder, select Target | Connectivity Options. Set:
a. Download to Ethernet
b. Transport to Ethernet
c. Click on the Settings button and select the device (on the debug console, you should see that the device is sending BOOTME packets).
d. Apply these settings.
13. Attach the device