none
AM335x Boot issue RRS feed

  • Question

  • Dear Community,

    I have problems to boot WinEC7 on our self-made core module. We are using AM3354 CPU and the provided BSP from Adeneo.
    After I start the image on the core module I get the following debug messages:

    +OEMIsFlashAddr(0x80002000) g_eboot.type 1
    [0]: Address=0x80002000  Length=0x79f8ae4  Name="" Target=RAM
    ROMHDR at Address 80002044h
    Launch Windows CE image by jumping to 0x8000e960...

    Windows CE Kernel for ARM (Thumb Enabled) Built on Oct  3 2012 at 17:38:47
    ProcessorType=0c08  Revision=2 CpuId=0x413fc082
    OEMAddressTable = 8000eb3c
    CPU CP15 Control Register = 0xc5387f
    CPU CP15 Auxiliary Control Register = 0x42
    _PrcmHwEnableModuleClocks: CANNOT enable clock for devId=80
    Initializing VFP, FPSID=410330c3
    +OALTimerInit(1, 24000, 200)
    --- High Performance Frequecy is 24 MHz---
    NKStartup done, starting up kernel. nCpus = 1
    Windows CE KernelInit
    Error Reporting Memory Reserved, dump size = 0004b000
    Booting Windows CE version 7.00 for (ARM)
    Memory Configuring: Total pages: 62853, Filesystem pages = 2455
    Booting kernel with clean memory configuration:
    Total Memory Sections:2
    [0] (static): start: 87a2c000, extension/attributes: 00016000, length: 05585000
    [1] (dynamic): start: 00960000, extension/attributes: 00028800, length: 0a000000
    Scheduling the first thread.
    PID:00400002 TID:00410002 PGPOOL: Reserved 768 pages for Loader pool
    PID:00400002 TID:00410002 PGPOOL: Reserved 256 pages for File pool
    PID:00400002 TID:00410002 OSAXST0: Platform Name = BSP_AM33X
    PID:00400002 TID:00410002 OSAXST1: >>> Loading Module 'kd.dll' (0x9E801ED0) at address 0xEFFE0000-0xEFFFE000 in Process 'NK.EXE' (0x87A0EAD0)
    PID:00400002 TID:00410002 KD: Starting kernel debugger software probe (KdStub) - KD API version 27
    PID:00400002 TID:00410002 OSAXST1: >>> Loading Module 'NK.EXE' (0x87A0EAD0) at address 0x80002000-0x8003C000 in Process 'NK.EXE' (0x87A0EAD0)
    PID:00400002 TID:00410002 SetOpp to 1
    PID:00400002 TID:00410002 Message Queue support initialized, g_hMsgQHeap = a28c0010
    PID:00400002 TID:00500002 OSAXST1: >>> Loading Module 'filesys.dll' (0x9E802B94) at address 0xEFC70000-0xEFD24000 in Process 'NK.EXE' (0x87A0EAD0)
    PID:00400002 TID:00500002 OSAXST1: >>> Loading Module 'fsdmgr.dll' (0x9E802CCC) at address 0xEF760000-0xEF7AB000 in Process 'NK.EXE' (0x87A0EAD0)
    PID:00400002 TID:00520002 FileSystem Starting - starting with clean file system
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'romfsd.dll' (0x9E8033B8) at address 0xEFC60000-0xEFC67000 in Process 'NK.EXE' (0x87A0EAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'ramdisk.dll' (0x9E8054C0) at address 0xEF730000-0xEF738000 in Process 'NK.EXE' (0x87A0EAD0)
    PID:00400002 TID:00520002 RAM: No DeleteSectors entry specified in the registry
    PID:00400002 TID:00520002 RAM: No SectorSize entry specified in the registry
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'mspart.dll' (0x9E805808) at address 0xEF740000-0xEF750000 in Process 'NK.EXE' (0x87A0EAD0)
    PID:00400002 TID:00520002 FSDMGR!StoreDisk_t::Mount: Geometry: NumSec=196608 BytesPerSec=512 FreeSec=0 BiggestCreatable=0
    PID:00400002 TID:00520002 MSPART!PD_OpenPartition: dwStoreId=A2833D90, PartName=PART00
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'exfat.dll' (0x9E805C20) at address 0xEF8D0000-0xEF90D000 in Process 'NK.EXE' (0x87A0EAD0)
    PID:00400002 TID:00520002 OSAXST1: <<< Unloading Module 'exfat.dll' (0x9E805C20) at address 0xEF8D0000-0xEF90D000 in Process 'NK.EXE' (0x87A0EAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'exfat.dll' (0x9E805C20) at address 0xEF8D0000-0xEF90D000 in Process 'NK.EXE' (0x87A0EAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.fatutil.dll' (0x9E805ED8) at address 0xEF860000-0xEF888000 in Process 'NK.EXE' (0x87A0EAD0)
    PID:00400002 TID:00520002 FormatDisk!FormatVolume: New extended sectors successfully written

    What can go wrong or cause the system to hang at this point?

    Thank you,

    Shahal

    Monday, July 8, 2013 11:27 AM

All replies

  • I see this in the messages:

    PID:00400002 TID:00520002 FSDMGR!StoreDisk_t::Mount: Geometry: NumSec=196608 BytesPerSec=512 FreeSec=0 BiggestCreatable=0

    Does this mean that the driver reports zero free sectors available and the biggest possible creatable sector is zero size?  That seems like the place to dig deeper.  also, was PART00 the correct partition name?

    Monday, July 8, 2013 12:55 PM
  • I see this in the messages:

    PID:00400002 TID:00520002 FSDMGR!StoreDisk_t::Mount: Geometry: NumSec=196608 BytesPerSec=512 FreeSec=0 BiggestCreatable=0

    Does this mean that the driver reports zero free sectors available and the biggest possible creatable sector is zero size?  That seems like the place to dig deeper.  also, was PART00 the correct partition name?

    Dear I_hart_software

    Thanks for the reply, I'm not really sure about where you name the partition - it is what was set in the original BSP. 

    The EVM's output is the same for that segment ( I copied a few following lines but there are many more):

    +OEMIsFlashAddr(0x80002000) g_eboot.type 1
    [0]: Address=0x80002000  Length=0x7a33f04  Name="" Target=RAM
    ROMHDR at Address 80002044h
    Launch Windows CE image by jumping to 0x8000e1c0...

    Windows CE Kernel for ARM (Thumb Enabled) Built on Oct  3 2012 at 17:38:47
    ProcessorType=0c08  Revision=2 CpuId=0x413fc082
    OEMAddressTable = 8000e39c
    CPU CP15 Control Register = 0xc5387f
    CPU CP15 Auxiliary Control Register = 0x42
    IT IS A GP BOARD
    Unrecognized Board Version!
            Board Name: A33515BB
            Board Ver : 1.4A
            Board Ser : 41124P160241
            Board Type: SKU#01
    Daughter Board is present
            DB Board Name: A335GPBD
            DB Board Ver : 1.2A
            DB Board Ser : 44124P130035
            DB Board Type: SKU#01
    Using Profile#0 (g_dwBoardProfile=0x1)
    Initializing VFP, FPSID=410330c3
    +OALTimerInit(1, 24000, 200)
    --- High Performance Frequecy is 24 MHz---
    Changed KITL zone mask to 0x0000B003
    +OALKitlStart
    +OALKitlInit(' s',  0x 8X - -2147236872/44/0x 8X, 0x 8X)
    DeviceId................. EVM33X-
    pArgs->flags............. 0x2C
    pArgs->devLoc.IfcType.... 0
    pArgs->devLoc.LogicalLoc. 0x4A100000
    pArgs->devLoc.PhysicalLoc 0x0
    pArgs->devLoc.Pin........ 0
    pArgs->ip4address........ 0
    pDevice->Name............  s
    pDevice->ifcType......... 0
    pDevice->id.............. 0x4A100000
    pDevice->resource........ 0
    pDevice->type............ 2
    pDevice->pDriver......... 0x87A4E000
    WARN: OALKitlInit: KITL Disabled
    -OALKitlInit(rc = 1)
    -OALKitlStart(rc = 1)
    NKStartup done, starting up kernel. nCpus = 1
    Windows CE KernelInit
    Error Reporting Memory Reserved, dump size = 0004b000
    Booting Windows CE version 7.00 for (ARM)
    Memory Configuring: Total pages: 62725, Filesystem pages = 2450
    Booting kernel with clean memory configuration:
    Total Memory Sections:2
    [0] (static): start: 87aac000, extension/attributes: 00016000, length: 05505000
    [1] (dynamic): start: 00960000, extension/attributes: 00028800, length: 0a000000
    Scheduling the first thread.
    PID:00400002 TID:00410002 PGPOOL: Reserved 768 pages for Loader pool
    PID:00400002 TID:00410002 PGPOOL: Reserved 256 pages for File pool
    PID:00400002 TID:00410002 OSAXST0: Platform Name = BSP_AM33X
    PID:00400002 TID:00410002 OSAXST1: >>> Loading Module 'kd.dll' (0x9E80209C) at address 0xEFFE0000-0xEFFFE000 in Process 'NK.EXE' (0x87A8EAD0)
    PID:00400002 TID:00410002 KD: Starting kernel debugger software probe (KdStub) - KD API version 27
    PID:00400002 TID:00410002 OSAXST1: >>> Loading Module 'NK.EXE' (0x87A8EAD0) at address 0x80002000-0x8003B000 in Process 'NK.EXE' (0x87A8EAD0)
    PID:00400002 TID:00410002 SetOpp to 3
    PID:00400002 TID:00410002 Message Queue support initialized, g_hMsgQHeap = a28c0010
    PID:00400002 TID:00500002 OSAXST1: >>> Loading Module 'filesys.dll' (0x9E802D2C) at address 0xEFC80000-0xEFD2D000 in Process 'NK.EXE' (0x87A8EAD0)
    PID:00400002 TID:00500002 OSAXST1: >>> Loading Module 'fsdmgr.dll' (0x9E802E64) at address 0xEF750000-0xEF79B000 in Process 'NK.EXE' (0x87A8EAD0)
    PID:00400002 TID:00520002 FileSystem Starting - starting with clean file system
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'romfsd.dll' (0x9E803538) at address 0xEFC70000-0xEFC77000 in Process 'NK.EXE' (0x87A8EAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'ramdisk.dll' (0x9E804C70) at address 0xEF720000-0xEF728000 in Process 'NK.EXE' (0x87A8EAD0)
    PID:00400002 TID:00520002 RAM: No DeleteSectors entry specified in the registry
    PID:00400002 TID:00520002 RAM: No SectorSize entry specified in the registry
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'mspart.dll' (0x9E805000) at address 0xEF730000-0xEF740000 in Process 'NK.EXE' (0x87A8EAD0)
    PID:00400002 TID:00520002 FSDMGR!StoreDisk_t::Mount: Geometry: NumSec=196608 BytesPerSec=512 FreeSec=0 BiggestCreatable=0
    PID:00400002 TID:00520002 MSPART!PD_OpenPartition: dwStoreId=A2832AA0, PartName=PART00
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'exfat.dll' (0x9E805280) at address 0xEF8E0000-0xEF91D000 in Process 'NK.EXE' (0x87A8EAD0)
    PID:00400002 TID:00520002 OSAXST1: <<< Unloading Module 'exfat.dll' (0x9E805280) at address 0xEF8E0000-0xEF91D000 in Process 'NK.EXE' (0x87A8EAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'exfat.dll' (0x9E805280) at address 0xEF8E0000-0xEF91D000 in Process 'NK.EXE' (0x87A8EAD0)
    PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.fatutil.dll' (0x9E805538) at address 0xEF870000-0xEF898000 in Process 'NK.EXE' (0x87A8EAD0)
    PID:00400002 TID:00520002 FormatDisk!FormatVolume: New extended sectors successfully written

    PID:00400002 TID:00520002 FormatDisk!FormatVolume: New FAT #0 successfully written
    PID:00400002 TID:00520002 FormatDisk!FormatVolume: New FAT #1 successfully written
    PID:00400002 TID:00520002 FormatDisk!FormatVolume: New root directory successfully written
    PID:00400002 TID:00520002 FormatDisk!FormatVolume: New BPB successfully written
    PID:00400002 TID:00520002 FormatDisk!FormatVolume complete.
    PID:00400002 TID:00520002 OSAXST1: <<< Unloading Module 'k.fatutil.dll' (0x9E805538) at address 0xEF870000-0xEF898000 in Process 'NK.EXE' (0x87A8EAD0)

    Seems like the exact same output on the EVM so I'm not sure where to look.

    If anyone can point me, I would appreciate it.

    Thanks,

    Shahal

    Monday, July 8, 2013 2:18 PM
  • Hello Shahal,

    have you found any solution for this problem? I have problems to boot WinCE7 on our self-made core modul, too. We are using AM3359 CPU and the provided BSP from Adeneo. The debug output looks the same like yours. It hangs with last output: "FormatDisk!FormatVolume: New extended sectors successfully written"

    It seems somethin goes wrong in fatutil.dll. But I can't find any sources for it. And I can't set more Debug Zones to get more Debug output.

    best regards,

    Stephen

    Friday, February 7, 2014 6:08 PM