• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 656 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Can I disable the flash driver in the TI_EVM_3530 BSP and OS Design with Win Compact 7?

Glenn Sikkema
Prodigy 110 points
Other Parts Discussed in Thread: OMAP3530, BQ27000

Hi-

I am trying to get Win Embedded Compact 7 running on the OMAP3530 EVM. This question may be more for Microsoft, but am posting it here in case someone else has had the same issue. There's an OMAP3530EVM platform included with Microsoft's eval platform builder. I've successfully built the image and downloaded it by booting from SD, configuring eboot to use ethernet for boot and debug devices and connecting the platform builder. However, out of the box it crashes apparently because it can't find a valid Windows partition on the NAND flash.

There are other threads here about this issue showing how to use EVMFlash to put that partition in, but I don't want to do that because we also use this EVM for Linux development and the NAND flash contains some Linux tools, notably u-boot. So, I tried to remove the flash driver from the BSP and OS Image. By making sure I used a RAM-based registry I was able to do so through the catalog.

However, it still does not complete the boot. It seems fine until I get this:

32343 PID:400002 TID:5d0002 FSDMGR: DEBUGCHK failed in file d:\chelanrtm14\private\winceos\coreos\storage\fsdmgr\volumeapi.cpp at line 402

at which point it quits. I don't have the source for volumeapi.cpp so I can't tell why it's unhappy; but since others have been successful in getting this going with the flash driver included, I am assuming it is because there's no flash access. So, I have two questions:

1. Has anyone successfully booted a Windows Embedded Compact 7 nk.bin with the flash driver disabled? If so, how did you do it?

2. If I absolutely have to have the flash driver enabled and a Windows partition on the flash, where can i get the latest EVMFlash tool to do it? It doesn't look like it is in Microsoft's trial version of Compact 7.

 

  • 0
    TI__Intellectual 2525 points

    Glenn,

    Are you seeing this with a debug build? If so, could you try with a retail build?

    Thanks,

    Aparna

  • 0 in reply to Aparna Balasubramanian
    TI__Expert 5320 points

    If you have WinCE 6 Combined BSP drop (see details here http://e2e.ti.com/support/embedded/f/353/t/96647.aspx), then the pserial.exe is part of that drop and can be used to flash XLDR and EBOOT to NAND. When eboot boots up from NAND, it auto detects and formats the NAND with OS-partition. This works as is for WEC7 too.

    If you are unfamiliar with pserial.exe utility, see instructions here http://processors.wiki.ti.com/index.php/WinCE-BSP_ARM-A8_User_Guide#Booting_from_NAND_Flash

    -Madhvi

  • 0 in reply to Madhvi
    Prodigy 110 points

    Madhvi-

    Sorry for my late response; I got pulled off on another project for a week. Thanks very much for your suggestion; this is what I intend to do. I have pserial.exe working fine. However, it doesn't look like Windows Embedded Compact 7 builds XLDRUARD.nb0, and when I tried to rebuild my TI_EVM_3530 BSP in release mode to build this file there, I'm having a problem as shown in the excerpt of the build log below. I apparently have messed something up, but am unfortunately no expert on WinCE BSPs. Do you know what could be causing this? Do I need to reinstall the BSP?

     

    BUILD: [00:0000000315:PROGC ] Building COMPILE Pass in C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\BATTERY\BQ27000\ directory.

    BUILD: [00:0000000326:PROGC ] Building COMPILE Pass in C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\ISP_RESIZER\ directory.

    BUILD: [00:0000000336:WARNN ] C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\CEDDK\DLL\: Missing source file: C:\WINCE600\platform\common\lib\ARMV4I\debug\OMAP3530_soccfg.lib.

    BUILD: [00:0000000337:WARNN ] C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\CEDDK\DLL\: Missing source file: C:\WINCE600\platform\common\lib\ARMV4I\debug\common_ti_devicesmap.lib.

    BUILD: [00:0000000338:WARNN ] C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\CEDDK\DLL\: Missing source file: C:\WINCE600\platform\common\lib\ARMV4I\debug\common_ti_device_gpiodispatch.lib.

    BUILD: [00:0000000339:WARNN ] C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\CEDDK\DLL\: Missing source file: C:\WINCE600\platform\common\lib\ARMV4I\debug\ceddk_i2c_lib.lib.

    BUILD: [00:0000000340:WARNN ] C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\CEDDK\DLL\: Missing source file: C:\WINCE600\platform\common\lib\ARMV4I\debug\ceddk_clock_lib.lib.

    BUILD: [00:0000000341:WARNN ] C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\CEDDK\DLL\: Missing source file: C:\WINCE600\platform\common\lib\ARMV4I\debug\ceddk_spi_lib.lib.

    BUILD: [00:0000000342:WARNN ] C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\CEDDK\DLL\: Missing source file: C:\WINCE600\platform\common\lib\ARMV4I\debug\ceddk_reg_lib.lib.

    BUILD: [00:0000000343:WARNN ] C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\CEDDK\DLL\: Missing source file: C:\WINCE600\platform\common\lib\ARMV4I\debug\ceddk_dma_lib.lib.

    BUILD: [00:0000000344:WARNN ] C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\CEDDK\DLL\: Missing source file: C:\WINCE600\platform\common\lib\ARMV4I\debug\ceddk_pmext_lib.lib.

    BUILD: [00:0000000345:WARNN ] C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\CEDDK\DLL\: Missing source file: C:\WINCE600\platform\common\lib\ARMV4I\debug\ceddk_padcfg_lib.lib.

    BUILD: [00:0000000346:WARNN ] C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\CEDDK\DLL\: Missing source file: C:\WINCE600\platform\common\lib\ARMV4I\debug\ceddk_bus_lib.lib.

    BUILD: [00:0000000370:PROGC ] Building LIB Pass in C:\WINCE600\PLATFORM\EVM_OMAP3530\SRC\DRIVERS\CEDDK\DLL\ directory.

    BUILD: [01:0000000380:ERRORE] NMAKE : U1073: don't know how to make 'C:\WINCE600\platform\common\lib\ARMV4I\debug\OMAP3530_soccfg.lib'

    BUILD: [01:0000000382:ERRORE] NMAKE.EXE TargetLibFiles -i -c BUILDMSG=Stop. BUILDROOT=C:\WINCE600\PLATFORM\EVM_OMAP3530 LINKONLY=1 NOPASS0=1 failed - rc = 2

  • 0 in reply to Glenn Sikkema
    Prodigy 110 points

    Followup- In my statement "when I tried to rebuild my TI_EVM_3530 BSP in release mode to build this file there", I meant in WinCE 6R3 because I can't find XLDRUART.nb0 in a release build of the BSP for Windows Embedded Compact 7.

     

    Glenn

  • 0 in reply to Glenn Sikkema
    TI__Expert 5320 points

    For the Build problem, make sure you have the directory C:\WINCE600\PLATFORM\COMMON\SRC\SOC\COMMON_TI_V1 and is being built as part of your solution.

    For the Flashing and creating partitions issue, I am sorry to have misled you. I was under the wrong impression that TI_EVM_3530 (Rel 6.x) produces XLDRUART.nb0. So you cannot use pserial.exe with the 6.x OMAP35x releases (but you can use it for ARM A8 01.xx releases). To get the flash tool that should work with the TI_EVM_3530 WEC 7 BSP, please use the EVM flash tool in the bspdemo_omapwince_06_15_00 installer.

    Sorry for the misdirection,

    Madhvi