Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 11 Aug 2009 01:24 PM by  mikea@logicpd.com
Booting Slowly : Getting stuck somewhere
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages
sandeep.akkanapragada@lntemsys.com
New Member
New Member
Posts:


--
05 Aug 2009 09:15 AM
    Hi,
    The time taken for booting is more than 7 minutes ( for OS to get into working state, with task bar up ..). we tried to enable the OAL messages in serial port (since kitl is not getting connected as it is very slow)
    KITL LOG
    PB Debugger The Kernel Debugger is waiting to connect with target.
    4294767296 PID:0 TID:2
    4294767296 PID:0 TID:2 -----------------------------------------
    4294767296 PID:0 TID:2 LPD_OMAP35X_SOM Revision Information
    4294767296 PID:0 TID:2 .......................................
    4294767296 PID:0 TID:2 BSP Revision : 0.9.0
    4294767296 PID:0 TID:2 -----------------------------------------
    4294767296 PID:0 TID:2
    4294767296 PID:0 TID:2
    4294767296 PID:0 TID:2 -----------------------------------------
    4294767296 PID:0 TID:2 LPD_OMAP35X_SOM Cache Information
    4294767296 PID:0 TID:2 .......................................
    4294767296 PID:0 TID:2 L1 Cache : Enabled
    4294767296 PID:0 TID:2 L2 Cache : Enabled
    4294767296 PID:0 TID:2 Branch Prediction : Enabled
    4294767296 PID:0 TID:2 -----------------------------------------
    PB Debugger Kernel debugger connected.
    4294767296 PID:0 TID:2
    PB Debugger Unexpected Debugger Service error: 0x80070057
    4294767296 PID:0 TID:2 OEM Initialization Done.
    PB Debugger Unexpected Debugger Service error: 0x80070057
    PB Debugger Unexpected Debugger Service error: 0x80070057
    PB Debugger Unexpected Debugger Service error: 0x80070057
    PB Debugger Unexpected Debugger Service error: 0x80070057
    PB Debugger Unexpected Debugger Service error: 0x80070057
    4294767296 PID:0 TID:2 Starting Kernel...
    4294767296 PID:0 TID:2 Error Reporting Memory Reserved, dump size = 0004b000
    4294767296 PID:0 TID:2 Setting up softlog at 0x86fb1000 for 0x800 entries
    4294767296 PID:0 TID:2 Booting Windows CE version 6.00 for (ARM)
    4294767296 PID:0 TID:2 &pTOC = 83eedc1c, pTOC = 83e97360, pTOC->ulRamFree = 83ef2000, MemForPT = 00001000
    4294767296 PID:0 TID:2
    Old or invalid version stamp in kernel structures - starting clean!
    4294767296 PID:0 TID:2 Configuring: Primary pages: 12470, Secondary pages: 0, Filesystem pages = 1656
    4294767296 PID:0 TID:2
    Booting kernel with clean memory configuration:
    4294767296 PID:0 TID:2 Memory Sections:
    4294767296 PID:0 TID:2 [0] : start: 83ef4000, extension: 00007000, length: 030b6000
    4294767296 PID:0 TID:2 NKStartup done, starting up kernel.
    5218 PID:0 TID:2 Windows CE KernelInit
    5340 PID:400002 TID:2 Reserve VM for kernel XIP DLls, first = c0010000, last = c1650000
    5351 PID:400002 TID:2 g_pprcNK == 0x83eebaa0
    5352 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0002a000
    5354 PID:400002 TID:410002 Initializing Memory Mapped File Support
    5354 PID:400002 TID:410002 Scheduling the first thread.
    5355 PID:400002 TID:410002 Detecting VFP...
    5355 PID:400002 TID:410002 VFP Found!
    5356 PID:400002 TID:410002 LoaderInit: Initialing loader
    5377 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0002a000
    5380 PID:400002 TID:410002 Updated eptr->e32_vsize to = 000a2000
    5387 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00019000
    5625 PID:400002 TID:410002 PGPOOL: Reserved 768 pages for Loader pool
    5625 PID:400002 TID:410002 PGPOOL: Reserved 256 pages for File pool
    5633 PID:400002 TID:410002 OSAXST0: Platform Name = LPD_OMAP35X_SOM
    5641 PID:400002 TID:410002 OSAXST1: >>> Loading Module 'kd.dll' (0x86F8387C) at address 0xC0010000-0xC0045000 in Process 'NK.EXE' (0x83EEBAA0)
    5642 PID:400002 TID:410002 KD: Starting kernel debugger software probe (KdStub) - KD API version 22
    5643 PID:400002 TID:410002 OSAXST1: >>> Loading Module 'NK.EXE' (0x83EEBAA0) at address 0x80200000-0x8022A000 in Process 'NK.EXE' (0x83EEBAA0)
    PB Debugger The Kernel Debugger connection has been established (Target CPU is ARM).
    PB Debugger Target name: CE Device
    PB Debugger Probe name: KdStub
    PB Debugger Binary Image should be loaded at 0x80200000 / Data relocated at 0x83ea6000
    PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\NEW_OS\LPD_OMAP35X_SHOW\RELDIR\LPD_OMAP35X_SOM_ARMV4I_DEBUG\NK.EXE'
    PB Debugger Loaded 'C:\WINCE600\OSDESIGNS\NEW_OS\LPD_OMAP35X_SHOW\RELDIR\LPD_OMAP35X_SOM_ARMV4I_DEBUG\COREDLL.DLL', no matching symbolic information found.
    PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\NEW_OS\LPD_OMAP35X_SHOW\RELDIR\LPD_OMAP35X_SOM_ARMV4I_DEBUG\KITL.DLL'
    PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\NEW_OS\LPD_OMAP35X_SHOW\RELDIR\LPD_OMAP35X_SOM_ARMV4I_DEBUG\KERNEL.DLL'
    PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\NEW_OS\LPD_OMAP35X_SHOW\RELDIR\LPD_OMAP35X_SOM_ARMV4I_DEBUG\OALIOCTL.DLL'
    PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\NEW_OS\LPD_OMAP35X_SHOW\RELDIR\LPD_OMAP35X_SOM_ARMV4I_DEBUG\HD.DLL'
    PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\NEW_OS\LPD_OMAP35X_SHOW\RELDIR\LPD_OMAP35X_SOM_ARMV4I_DEBUG\OSAXST0.DLL'
    PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\NEW_OS\LPD_OMAP35X_SHOW\RELDIR\LPD_OMAP35X_SOM_ARMV4I_DEBUG\OSAXST1.DLL'
    PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\NEW_OS\LPD_OMAP35X_SHOW\RELDIR\LPD_OMAP35X_SOM_ARMV4I_DEBUG\K.COREDLL.DLL'
    PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\NEW_OS\LPD_OMAP35X_SHOW\RELDIR\LPD_OMAP35X_SOM_ARMV4I_DEBUG\KD.DLL'
    14057 PID:400002 TID:410002 HD: Immediate debugger module load notifications ACTIVE (slower boot - non real-time).
    /*************************/
    and it stops here...forever.

    the serial log I can send if needed.
    We observed that instead of loading dlls, it goes into a loop and at very large intervals it gives this messages
    /***************************/
    OEMInterruptHandler(Irq 37)
    Unsupported OALLED(LED_IDX_:31, data:2)
    +OALIntrDoneIrqs(1, 0xffffc734)
    -OALIntrDoneIrqs
    /****************************/
    ..after some time it resumes the work of loading the dll's and finally stops at the same place...
    If we connect KIT to PC through OTG, or if we remove & reinsert the SD card it thakes a very long time for them to get recognized...

    what can be the problem..?

    Thanks and Regards,
    Sandy.
    mikea@logicpd.com
    New Member
    New Member
    Posts:


    --
    11 Aug 2009 01:24 PM
    I highly suggest downloading BSP version 1.0.2, which was posted in May or June. This should help this issue I believe.
    You are not authorized to post a reply.