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.

Compact 7 Debug Boot Problem on OMAP3530 EVM

Other Parts Discussed in Thread: OMAP3530

Hi,

I cannot boot correctly in Debug Mode.

I enabled KITL and kernel debugger on Build Options menu, and set BSP_NOETHERNET environment variable to disable Ethernet NDIS miniport driver that interferes KITL communication. I downloaded the OS image (95.9MB) to the target board (TMDSEVM3530) and tried to boot the OS. But Platform Builder (PB) requires some files and I cannot boot it correctly. Below is what I saw and did after PB downloaded the image to the board.

1. "tcsncpy_s.inl" is required by PB, so I selected this file located in C:\\Program Files\Microsoft Visual Studio 9.0\VC\crt\src.

2. "devpnp.c" is required by PB, but this file doesn't exist in C:\\, so I select "cancel" to skip.

3. "bkist.cpp" is required by PB, but this file doesn't exist in C:\\, so I select "cancel" to skip.

4. "thread.c" is required by PB, so I selected this file located in C:\\Program Files\Microsoft Visual Studio 9.0\VC\crt\src.

5. "gwe_s.cpp" is required by PB, but this file doesn't exist in C:\\, so I select "cancel" to skip.

6. "input.c" is required by PB, so I selected this file located in C:\\WINCE700\public\wceshellfe\oak\ctlpnl\intl2.

7. "crtsupp.cpp" is required by PB, but this file doesn't exist in C:\\, so I select "cancel" to skip.

8. "fscall.c" is required by PB, but this file doesn't exist in C:\\, so I select "cancel" to skip.

9.  "First-chance exception in KERNEL.DLL. (0xC0000005: Access Violation)" dialog is appeared, then I select  "OK".

10. "Pass exception on to the program being debugged? Will default to 'Yes' if dialog disabled" dialog is appeared, then I select "Yes".

11. "First-chance exception in MUSBOTG.DLL. (0xDFFF0123: unnamed)" dialog is appeared, then I select "OK".

12. "Pass exception on to the program being debugged? Will default to 'Yes' if dialog disabled" dialog is appeared, then I select "Yes".

13. OS doesn't boot and PB downloads the image to the board again.

 

The memory allocation in config.bib is below.

MEMORY
;   Name                        VA          Length      Type
    ARGS                     84000000    00001000    RESERVED ; 4K
#if (defined BSP_DSPLINK || defined BSP_TI_DVSDK)
IF BSP_SDRAM_BANK1_ENABLE
    NK                           84001000    063FF000    RAMIMAGE   ; 100MB - 4K
    DISPLAY                8A400000    01000000    RESERVED  ; 16MB
    CMEM_DSP          8B400000    02800000    RESERVED  ; 40 MB
    RAM                        8DC00000   06400000    RAM               ; 100MB
ELSE

 

What causes this problem?

  • We have really not tried the full debug build with WinCE 7. The WinCE 7 image size has increased compared to WinCE 6. Can you also contact Microsoft/MSDN channel for this to see if they have any suggestion?

    (Unrelated to this issue I would like to point out that moving the memory around will create problem with video playback as well as display functionality. The CMEM_DSP area is expected to be at the same place as in the original file. It is possible to move it but it needs a recompilation of the DSP component of DVSDK. Also the display memory area has a setting in a header file that needs to mirror the same setting. I agree this is not apparent looking at the config.bib file. My suggestion would be for you to keep the DISPLAY and the CMEM_DSP as is and just swap the NK and RAM around. This would be the least disruptive. I have not tried it though).  

    Another suggestion: If you are only interested in particular area/driver for debugging it maybe better to just do a debug for those modules. 

  • Hi Jatin,

    Thank you for your suggestion.

    I didn't know that moving the memory around will create problems with video playback and display functionality.

    I will modify the memory allocation keeping the DISPLAY and the CMEM_DSP as-is and just swapping the NK and RAM around, and try to decrease the size of the image by excluding some components.

    Also I will try to contact Microsoft/MSDN channel for the problem I post this time.

  • One more thing. Currently the DSP based video playback does not work on the WinCE 7 codebase. Some of the TI DVSDK components need to be upgraded/rebuilt (by TI). But regardless of that the memory location is expected to remain the same and hence what I suggested in my previous post still applies. So if you try avi playback with H.264 or MPEG4 video codecs it will fail.

    As regards to the display setting the file that needs parallel changes (if the "DISPLAY" setting is changed in config.bib) is ti_evm_3530\SRC\INC\image_cfg.h and the setting is IMAGE_DISPLAY_BUF_PA. It is not apparent that these are related since config.bib specifies virtual address and image_cfg.h specifies the physical address. So the config.bib 88800000 corresponds to image_cfg.h 84800000. Hopefully we can get this cleaned up in a future release so that it is easier to move memory around. But as of now these limitations exist.

     

  • I was able to build/load the debug image (KITL and kernel debugger enabled) with the following setting in config.bib (I'm using WinCE 7 build 373 from July). I did not change anything in the image_cfg.h file.

    MEMORY

    ;   Name                        VA          Length      Type

        ARGS                       84000000    00001000    RESERVED ; 4K 

        RAM                         84001000    047FF000    RAM      ; 72MB - 4K

        DISPLAY                   88800000    01000000    RESERVED ; 16MB

        CMEM_DSP               89800000    02800000    RESERVED ; 40 MB.

        NK                            8C000000    08000000    RAMIMAGE ; 128MB.

    My problem was that my debug image size was more than 128MB (lot of OS features included) and that was creating problem and would have needed movement of eboot section in image_cfg.h to make space for nk.bin. You mentioned that your debug image is about 93MB and in that case you should be able to use the same setting as above. 
    I cut down some core OS features and brought the image down to about 110MB and I did not see anything similar to the issue you mentioned in your initial post. But I did encounter a few "DEBUGCHK" failed breaks and I kept hitting F5 so that it would proceed. Eventually it booted to WinCE desktop and was able to try a few things.
    My suggestion to you is for you to clean sysgen and build the debug image as is and not disable the ethernet/vmini that you mentioned in your post. 
    Also I was able to get by without changing the image_cfg.h file since I was loading from PB. But if you were to load it from NAND or from SD card then there are some settings in the image_cfg.h given below that has to match the configuration in config.bib. So you have to take care of those as well. (please remember the following are physical address while the ones in config.bib are virtual address). 
    #define IMAGE_WINCE_CODE_PA             0x80001000
    #define IMAGE_WINCE_CODE_SIZE           0x02FFF000
    In addition if your debug image goes beyond 128MB then multiple complicated steps would be needed. Relocating DSP_CMEM with appropriate changes in DSP image, changing the eboot location to correspond to the CMEM_DSP since these are never needed simultaneously. Eboot location should be separate from the NK area etc. Most of the needed settings are in image_cfg.h, config.bib, ebootsd.bib, ebootnand.bib, etc. I hope you don't have to do all that since your debug image is less than 128MB. 

  • Hi Jatin,

    Thank you for your detail information.

    I was able to boot correctly by just swapping NK and RAM in config.bib. I edited nothing in image_cfg.h.

    Also, I'm sure that multiple complicated steps would be needed if debug image exceeds 128MB.

    I will try to exclude unneeded components as many as possible in order to reduce the size of debug image.

     

    Thank you for your big help.

  • Hi there,

    I am working on a WinCE 7 image to run on a BeagleBoard xM rev C.

    When I load a release build, it goes fine and I can get things working so far, including my custom drivers.

    However, when I load a debug build, it keeps breaking on DEBUGCHK macros.

    The issue is I do not have the source code of the entire image, so I cannot recompile the image with a new DEBUGCHK definition.

    Is there any way to ignore these DEBUGCHK breaks, thru a runtime command in the CE> command line

    I have read about the zo comand, but I cannot quite get there yet ...

    Any comment on the right way to use a debug build with its DEBUGMSG, but without continuous break at each DEBUGCHK ?

    Thanks

    Franck

  • Hi Jatin Jain,

    I am trying to boot up my devkit8000 board which is TI's Omap 3530, using windows embedded compact 7. Have builded an os image with TI Omap 3530 EVM supported bsp from platform. I tried loading from platform builder. It shows downloaded and transported successfully. But board is not booting up.

    40W              
    Texas Instruments Windows CE SD X-Loader for EVM 3530                                                    
    Built Feb 17 2012 at 11:11:25                            
    Version 6.13.00              
    open ebootsd.nb0 file                    
    Init HW: controller RST                      
    read ebootsd.nb0 file                    
    jumping to ebootsd image                       

    Microsoft Windows CE Bootloader Common Library Version 1.4 Built Feb 17 2012 11:                                                                               
    06:23    

    Texas Instruments Windows CE EBOOT for Mistral OMAP EVM, Built Feb 17 2012 at 11                                                                               
    :11:19     
    EBOOT Version 1.5, BSP 6.13.00                             

    TI OMAP3530 Version 0x4b7ae02f (ES3.1)                                     
    TPS659XX Version 0x10 (Unknown)                              
    System ready!            
    Preparing for downl                
    INFO: Predownload....                    
    WARN: Boot config wasn't found, using defaults                                             
    INFO: SW4 boot setting: 0x2f                           

    >>> Forcing cold boot (non-persistent registry and other data will be wiped) <<<                                                                               

    Hit space to enter configuration menu 5...                                         
    Hit space to enter configuration menu 4...                                         

    --------------------------------------------------------------------------------                                                                               

     Main Menu         
    --------------------------------------------------------------------------------                                                                               

     [1] Show Current Settings                         
     [2] Select Boot Device                      
     [3] Select KITL (Debug) D                        
     [4] Network Settings                    
     [5] SDCard Settings                   
     [6] Set Device ID                 
     [7] Save Settings                 
     [8] Flash Management                    
     [0] Exit and Continue                     

     Selection: 2            

    --------------------------------------------------------------------------------                                                                               

     Select Boot Device                  
    --------------------------------------------------------------------------------                                                                               

     [1] DM9000A MAC               
     [2] USBFn RNDIS               
     [3] NK from SDCard FILE                       
     [0] Exit and Continue                     

     Selection (actual DM9000A MAC): 2                                 
     Boot device set to USBFn RNDIS                              

    ----------------------------------------------                                            

     Main Menu         
    --------------------------------------------------------------------------------                                                                               

     [1] Show Current Settings                         
     [2] Select Boot Device                      
     [3] Select KITL (Debug) Device                              
     [4] Network Settings                    
     [5] SDCard Settings                   
     [6] Set Device ID                 
     [7] Save Settings                 
     [8] Flash Management                    
     [0] Exit and Continue                     

     Selection: 3            

    --------------------------------------------------------------------------------                                                                               

     Select Debug Device                   
    --------------------------------------------------------------------------------                                                                               

     [1] USBFn RNDIS               
     [2] DM9000A MAC               
     [0] Exit and Continue                     

     Selection (actual DM9000A MAC): 1                                 
     Debug device set to USBFn RNDIS                               

    --------------------------------------------------------------------------------                                                                               

     Main Menu         
    --------------------------------------------------------------------------------                                                                               

     [1] Show Current Settings                         
     [2] Select Boot Device                      
     [3] Select KITL (Debug) Device                              
     [4] Network Settings                    
     [5] SDCard Settings                   
     [6] Set Device ID                 
     [7] Save Settings                 
     [8] Flash Management                    
     [0] Exit and Continue                     

     Selection: 4            

    --------------------------------------------------------------------------------                                                                               

     Network Settings                
    --------------------------------------------------------------------------------                                                                               

     [1] Show Current Settings                         
     [2] Enable/disable KITL                       
     [3] KITL interrupt/poll mode                            
     [4] KITL Active/Passive mode                            
     [5] Enable/disable DHCP                       
     [6] Set IP address                  
     [7] Set IP mask               
     [8] Set default router                      
     [9] Enable/disable VMINI                        
     [a] Set MAC address                   
     [0] Exit and Continue                     

     Selection: 5            
     Disable DHCP (actually enabled) [y/-]: y                                        
     DHCP disabled             

    --------------------------------------------------------------------------------                                                                               

     Network Settings                
    --------------------------------------------------------------------------------                                                                               

     [1] Show Current Settings                         
     [2] Enable/disable KITL                       
     [3] KITL interrupt/poll mode                            
     [4] KITL Active/Passive mode                            
     [5] Enable/disable DHCP                       
     [6] Set IP address                  
     [7] Set IP mask               
     [8] Set default router                      
     [9] Enable/disable VMINI                        
     [a] Set MAC address                   
     [0] Exit and Continue                     

     Selection: 6            
     Enter Device IP address (actual 0.0.0.0): 10.10.10.10                                                     
     Device IP address set to 10.10.10.10                                    

    --------------------------------------------------------------------------------                                                                               

     Network Settings                
    --------------------------------------------------------------------------------                                                                               

     [1] Show Current Settings                         
     [2] Enable/disable KITL                       
     [3] KITL interrupt/poll mode                            
     [4] KITL Active/Passive mode                            
     [5] Enable/disable DHCP                       
     [6] Set IP address                  
     [7] Set IP mask               
     [8] Set default router                      
     [9] Enable/disable VMINI                        
     [a] Set MAC address                   
     [0] Exit and Continue                     

     Selection: 7            
     Enter Device IP mask (actual 0.0.0.0): 255.255.255.0                                                    
     Device IP mask set to 255.255.255.0                                   

    --------------------------------------------------------------------------------                                                                               

     Network Settings                
    --------------------------------------------------------------------------------                                                                               

     [1] Show Current Settings                         
     [2] Enable/disable KITL                       
     [3] KITL interrupt/poll mode                            
     [4] KITL Active/Passive mode                            
     [5] Enable/disable DHCP                       
     [6] Set IP address                  
     [7] Set IP mask               
     [8] Set default router                      
     [9] Enable/disable VMINI                        
     [a] Set MAC address                   
     [0] Exit and Continue                     

     Selection: 8            
     Enter Default router IP address (actual 0.0.0.0): 10.10.10.1                                                            
     Default router IP address set to 10.10.10.1                                           

    --------------------------------------------------------------------------------                                                                               

     Network Settings                
    --------------------------------------------------------------------------------                                                                               

     [1] Show Current Settings                         
     [2] Enable/disable KITL                       
     [3] KITL interrupt/poll mode                            
     [4] KITL Active/Passive mode                            
     [5] Enable/disable DHCP                       
     [6] Set IP address                  
     [7] Set IP mask               
     [8] Set default ro                 
     [9] Enable/disable VMINI                        
     [a] Set MAC address                   
     [0] Exit and Continue                     

     Selection: 0            

    --------------------------------------------------------------------------------                                                                               

     Main Menu         
    --------------------------------------------------------------------------------                                                                               

     [1] Show Current Settings                         
     [2] Select Boot Device                      
     [3] Select KITL (Debug) Device                              
     [4] Network Settings                    
     [5] SDCard Settings                   
     [6] Set Device ID                 
     [7] Save Settings                 
     [8] Flash Management                    
     [0] Exit and Continue                     

     Selection: 0            
    HostMiniInit:: !!                
    Rndis:: initialization: with addr=480ab000                                         
    Rndis:: Address static map to addr=480ab000                                          
    Rndis:: initialization!                      
    +USBFN::Device ID = 0x4b7ae02f                             
    +USBFN::Device ID = 0x4b7ae02f                             
    Rndis:: PDDInit Success!                       
    Rndis:: Get MAC address 200,902f,b5d                                   
    RndisMdd:: PDD's max RX buffer = [8192] bytes.                                             
    Rndis:: initialization: Success                              
    HostMini:: New filter set: [0x0] --> [0xb]                                         
    INFO: Boot device uses MAC 00:02:2f:90:5d:0b                                           
    INFO: *** Device Name EVM3530-23819 ***                                      
    +EbootSendBootmeAndWaitForTftp                             
    Sent BOOTME to 255.255.255.255                             
    Sent BOOTME to 255.255.255.255                             
    Sent BOOTME to 255.255.255.255                             
    Sent BOOTME to 255.255.255.255                             
    Sent BOOTME to 255.255.255.255                             
    Sent BOOTME to 255.255.255.255                             
    Sent BOOTME to 255.255.255.255                             
    Sent BOOTME to 255.255.255.255                             
    Packet has the following data:                             
      boot.bin[NULL]octet[NULL]blksize[NULL]1024[NULL]                                                 
    TFTP packet could have 2 name/value pairs                                        
    Locked Down Link 1                 
    Src IP 10.10.10.10 Port Dest IP 10.10.10.20 Port Default TFTP block size set to:                                                                               
     512 bytes         
    This TFTP packet contains 1 options.                                   
    We currently only look at the first and expect it to be BLKSIZE.                                                               
    The packet's option name is blksize.                                   
    The option's value is 1024                         
    with a value that is in range.                             
    BLKSIZE will be adjusted to 1024.                                
    EthDown::TFTPD_OPEN::boot.bin                            
    An OACK packet is the proper acknowledgement                                           
    -EbootSendBootmeAndWaitForTftp                             

    BL_IMAGE_TYPE_BIN                

    Download file information:                         
    -----------------------------------------------------------                                                          
    [0]: Address=0x8c000000  Length=0x027324c8  Save=0xa0000000                                                          
    ----------------------------------------------------                                                  
    Download file type: 1                    
    rom_offset=0x0.              
    ImageStart = 0x8c000000, ImageLength = 0x27324c8, LaunchAddr = 0x8c00bf00                                                                        

    Completed file(s):                 
    -------------------------------------------------------------------------------                                                                              
    [0]: Address=0x8c000000  Length=0x27324c8  Name="" Target=RAM                                                            
    ROMHDR at Address 8C000044h                          
    Got EDBG_CMD_JUMPIMG                   
    Got EDBG_CMD_CONFIG, flags:0x0                             
    Launch Windows CE image by jumping to 0xa000bf00...                                                  

    Windows CE Kernel for ARM (Thumb Enabled)                                        
    --- High Performance Frequecy is 32768 khz---                                            
    DeviceId................                      
    pArgs->flags............. 0x29                             
    pArgs->devLoc.IfcType.... 0                          
    pArgs->devLoc.LogicalLoc. 0x480AB000                                   
    pArgs->devLoc.PhysicalLoc 0x0                            
    pArgs->devLoc.Pin........ -2015299124                                    
    pArgs->ip4address........ 1                          
    pDevice->Name............  s                           
    pDevice->ifcType......... 0                          
    pDevice->id.............. 0x480AB000                                   
    pDevice->resource........ 0                          
    pDevice->type............ 2                          
    pDevice->pDriver......... 0x8E751058                                   
    g_kitlLock = 0x8E798C20
    HostMiniInit:: !!
    Rndis:: initialization: with addr=480AB000
    Rndis:: Address static map to addr=C0400000
    Rndis:: initialization!
    +USBFN::Device ID = 0x4b7ae02f
    +USBFN::Device ID = 0x4b7ae02f
    Rndis:: PDDInit Success!
    Rndis:: Get MAC address 200,902F,B5D
    RndisMdd:: PDD's max RX buffer = [8192] bytes.
    Rndis:: initialization: Success
    HostMini:: New filter set: [0x0] --> [0xB]
    KITL: *** Device Name EVM3530-23819 ***
    WARN: KITL can't obtain IRQ for KITL device
    WARN: KITL will run in polling mode
    VBridge:: built on [Feb 17 2012] time [11:06:02]
    VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
    Tx buffer [0x8E7903A0] to [0x8E7943A0].
    Rx buffer [0x8E7943C0] to [0x8E7983C0].
    VBridge:: NK add MAC: [0-2-2F-90-5D-B]
    Connecting to Desktop
    KITL: Connected host  IP: 10.10.10.20  Port: 60020
    KITL connected with Desktop

    It is hanging up after this... Please suggest me what might be cause?

       

  • Does the target come up successfully when you have kitl disabled from NK.bin and/or eboot->networking options sub-menu? Also, you are using an image based on BSP version 6.13 which is very old. You can find newer versions of the BSP at the following location. You would have to make the necessary changes to support your EVM, though.

    http://www.ti.com/tool/wincesdk-a8

    Regards,

    Aparna

  • What changes i need to do in image_cfg.h file for above config.bib changes?

    Am trying to load WinCE 7 Debug mode image from SD card. Please reply me...

  • Hi Tajpeer,

     

    to disable KITL, rght click on your project tree root, in solution explorer window, and choose "properties".

    open the Configuration Prperties, in build optons, choose your buildoptions. if you d not want KITL and kernel debugge, make sure the corresponding optons:

    - Enable kernel debugger

    - Enabke KITL

    are not selected.

    Also, try the t load the release buid from your SD card.

    let me know how you succeed

    good luck

    Franck

     

  • Hi All,

    I am building the debug build for OMAP4430 BSP.

    So board is getting booted but the problem is that board is getting rebooted after every 3min so I am not able to check further where Nk image is working fine or not.

    I am providing the log after which it is getting rebooted. So if any one can assist the solution for that let me know.

    Windows CE SD X-Loader for OMAP4430
    Built Jan  4 2013 at 10:36:22
    Version 6.13.00
    open ebootsd.nb0 file

    jumping to ebootsd image

    Microsoft Windows CE Bootloader Common Library Version 1.4 Built Jan  4 2013 11:31:49

    Texas Instruments Windows CE EBOOT for Mistral OMAP EVM, Built Jan  4 2013 at 11:36:56
    EBOOT Version 1.5, BSP 6.13.00
    BEFORE RETURN System ready!
    Preparing for download...
    INFO: Predownload....
    WARN: Boot config wasn't found, using defaults
    INFO: SW4 boot setting: 0x05

     After default boot configuration
    >>> Forcing cold boot (non-persistent registry and other data will be wiped) <<<
    Hit space to enter configuration menu 5...

    --------------------------------------------------------------------------------
     Main Menu
    --------------------------------------------------------------------------------
     [1] Show Current Settings
     [2] Select Boot Device
     [3] Select KITL (Debug) Device
     [4] Network Settings
     [5] SDCard Settings
     [6] Set Device ID
     [7] Save Settings
     [8] Flash Management
     [0] Exit and Continue

     Selection: 2

    --------------------------------------------------------------------------------
     Select Boot Device
    --------------------------------------------------------------------------------
     [1] LAN9115 MAC
     [2] USBFn RNDIS
     [3] NK from SDCard FILE
     [0] Exit and Continue

     Selection (actual LAN9115 MAC): 3
     Boot device set to NK from SDCard FILE

    --------------------------------------------------------------------------------
     Main Menu
    --------------------------------------------------------------------------------
     [1] Show Current Settings
     [2] Select Boot Device
     [3] Select KITL (Debug) Device
     [4] Network Settings
     [5] SDCard Settings
     [6] Set Device ID
     [7] Save Settings
     [8] Flash Management
     [0] Exit and Continue

     Selection: 0

    BL_IMAGE_TYPE_BIN

    Download file information:
    -----------------------------------------------------------
    [0]: Address=0x8c000000  Length=0x03462a18  Save=0x80000000
    -----------------------------------------------------------
    Download file type: 1
     <> Record [ 0 ] dwRecAddr = 0x8c000000, dwRecLen = 0x4
     <> Record [ 1 ] dwRecAddr = 0x8c000040, dwRecLen = 0x8
     <> Record [ 2 ] dwRecAddr = 0x8c000048, dwRecLen = 0x4
     <> Record [ 3 ] dwRecAddr = 0x8c001000, dwRecLen = 0x3effc
     <> Record [ 4 ] dwRecAddr = 0x8c040000, dwRecLen = 0x1228
     <> Record [ 5 ] dwRecAddr = 0x8c043000, dwRecLen = 0xaeac0
     <> Record [ 6 ] dwRecAddr = 0x8c0f1ac0, dwRecLen = 0x2753c
     <> Record [ 7 ] dwRecAddr = 0x8c119000, dwRecLen = 0x40518
     <> Record [ 8 ] dwRecAddr = 0x8c159518, dwRecLen = 0xaae4
     <> Record [ 9 ] dwRecAddr = 0x8c164000, dwRecLen = 0x1325d8
     <> Record [ 10 ] dwRecAddr = 0x8c2965d8, dwRecLen = 0x5a28
     <> Record [ 11 ] dwRecAddr = 0x8c29c000, dwRecLen = 0x12d7b0
     <> Record [ 12 ] dwRecAddr = 0x8c3c97b0, dwRecLen = 0x3d848
     <> Record [ 13 ] dwRecAddr = 0x8c407000, dwRecLen = 0x3d000
     <> Record [ 14 ] dwRecAddr = 0x8c444000, dwRecLen = 0x3dff8
     <> Record [ 15 ] dwRecAddr = 0x8c482000, dwRecLen = 0x35ffc
     <> Record [ 16 ] dwRecAddr = 0x8c4b8000, dwRecLen = 0x1a000
     <> Record [ 17 ] dwRecAddr = 0x8c4d2000, dwRecLen = 0xb2d2c
     <> Record [ 18 ] dwRecAddr = 0x8c584d2c, dwRecLen = 0x32d4
     <> Record [ 19 ] dwRecAddr = 0x8c588000, dwRecLen = 0x1ca474
     <> Record [ 20 ] dwRecAddr = 0x8c752474, dwRecLen = 0x4b8c
     <> Record [ 21 ] dwRecAddr = 0x8c757000, dwRecLen = 0x799f4
     <> Record [ 22 ] dwRecAddr = 0x8c7d09f4, dwRecLen = 0x216a4
     <> Record [ 23 ] dwRecAddr = 0x8c7f3000, dwRecLen = 0x3b0d0
     <> Record [ 24 ] dwRecAddr = 0x8c82f000, dwRecLen = 0x37ffc
     <> Record [ 25 ] dwRecAddr = 0x8c867000, dwRecLen = 0x1e098
     <> Record [ 26 ] dwRecAddr = 0x8c886000, dwRecLen = 0x3bff8
     <> Record [ 27 ] dwRecAddr = 0x8c8c2000, dwRecLen = 0x23000
     <> Record [ 28 ] dwRecAddr = 0x8c8e5000, dwRecLen = 0x22ae0
     <> Record [ 29 ] dwRecAddr = 0x8c908000, dwRecLen = 0x20c0
     <> Record [ 30 ] dwRecAddr = 0x8c90b000, dwRecLen = 0x20c0
     <> Record [ 31 ] dwRecAddr = 0x8c90e000, dwRecLen = 0x34000
     <> Record [ 32 ] dwRecAddr = 0x8c942000, dwRecLen = 0x182b0
     <> Record [ 33 ] dwRecAddr = 0x8c95b000, dwRecLen = 0x4ffc
     <> Record [ 34 ] dwRecAddr = 0x8c960000, dwRecLen = 0xc6818
     <> Record [ 35 ] dwRecAddr = 0x8ca26818, dwRecLen = 0x1da58
     <> Record [ 36 ] dwRecAddr = 0x8ca45000, dwRecLen = 0x44
     <> Record [ 37 ] dwRecAddr = 0x8ca46000, dwRecLen = 0x1a000
     <> Record [ 38 ] dwRecAddr = 0x8ca60000, dwRecLen = 0x405d0
     <> Record [ 39 ] dwRecAddr = 0x8caa05d0, dwRecLen = 0x24a30
     <> Record [ 40 ] dwRecAddr = 0x8cac5000, dwRecLen = 0x2b000
     <> Record [ 41 ] dwRecAddr = 0x8caf0000, dwRecLen = 0x2affc
     <> Record [ 42 ] dwRecAddr = 0x8cb1b000, dwRecLen = 0x3fffc
     <> Record [ 43 ] dwRecAddr = 0x8cb5b000, dwRecLen = 0x10070
     <> Record [ 44 ] dwRecAddr = 0x8cb6c000, dwRecLen = 0x18ffc
     <> Record [ 45 ] dwRecAddr = 0x8cb85000, dwRecLen = 0x2c000
     <> Record [ 46 ] dwRecAddr = 0x8cbb1000, dwRecLen = 0x3f000
     <> Record [ 47 ] dwRecAddr = 0x8cbf0000, dwRecLen = 0x2a000

    So after this board is getting rebooted.

    Any help is appreciated.

  • Hi ,

    Now I am able to build the Debug Build Image and I have a crash in kernel after loading the pm.dll.

    Log messages which i am getting are:

    PID:00400002 TID:00920006 -OEMIoControl(rc = 1)
    PID:00400002 TID:00920006 InitializePMExtension: Can't find 'PmExtPath' key.
    PID:00400002 TID:00920006 OSAXST1: >>> Loading Module 'ccfgsvc.dll' (0xC040B1F8) at address 0xEEB10000-0xEEB3D000 in Process 'NK.EXE' (0x90611AD0)
    PID:00400002 TID:00920006 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\MUsbOtg\DllName) returned 2
    PID:00400002 TID:00920006 DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\MUsbOtg'
    PID:00400002 TID:00920006 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\FlashDisk\DllNamPID:00400002 TID:00920006
    PID:00400002 TID:00920006
    e) returned 2
    PID:00400002 TID:00920006 DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\FlashDisk'
    PID:00400002 TID:00500002

    After this it is going to IdleState and not launching the shell

  • Good day,

    I 've bought used Asus P526 mobile with Windows Mobile 6.1 on it, but after battery discharged, it turned off and didn't turn on. i connected a USB cable. then after first boot i got a message - "IPL: Insert USB Cable"

    so i tried to charge it for few hours, reset it, restart - same - nothing! same msg - IPL: Insert USB Cabl

    so i tried to change firmware - still nothing good!

    finally, i remembered that once i got into this "service menu". but found on forum that i can get into it by pressing "OK + camera + reset" while removing "Hold button"...

    so, i think i pressed exactly these three buttons (by memory, though, maybe three others, butsu rely with camera and reset), and ! yes! device started up! windows loaded!

    but i tried to check if it will work well.. so turned off, and...

    again - got same IPL: Insert USB Cable =-(

    so  i tried again to enter into this "service menu"... but instead i got real service menu (no black screen),

    Main menu
    (1) Show current settings
    (2) Select boot device
    (3) Select Debug device
    (4) Network settings
    (5) Nand/Nor/Mdoc Flash
    (6) Save settings
    (0) Exit and continue

    and not  ms windows... =-(

    so is it a problem with boot device?

    i see that now it is set to : 

    "

     Selection (actual ipl from do(c?):                                   
     Debug device set to USBFn RNDIS        

    "

    how to make windows running as before?

    what is this USBFn RNDIS     ?

    what is  ipl from doc?

    why i see always -

    IPL: Insert USB Cable

    ?

    actually joystick is not working (on left top - it can't press button up - but up+reset is needed to hard-reset...)

    so it seems that joystick_up+reset are being pressed "automatically" but i don't need it...

    can i change this settings by software?

     

  • I guess you may not find solution in this forum for that.

    Because the processor being used by ASUS P526 is only sold to mobile handset manufacturers. (http://en.wikipedia.org/wiki/OMAP search for 850 in that page)

    You may want to see the below ASUS URLs:

    http://vip.asus.com/forum/view.aspx?board_id=12&model=P527&id=20091105101609406&page=3&SLanguage=en-us and http://www.asus.com/supportonly/P526/HelpDesk_Download/

    Regards,

    GSR