Will WinEC7 Platform builder support ARM8.

Question

Hi,

I have a query related to WinEC7 platform builder supporting ARM8 .

I am trying to build a BSP for Am387x(Arm cortex core- A8),While downloading WinEC7 platform builder it gave the option of downloading the arm 5,6&7 BSP files as default files, does this mean WinEC7 is not supported in the development of ARM8.  

Answer 1

Windows CE 7 supports Cortex-A8. You can now use different ARM compiler versions to create more effective code for the core processor you are using. For the Crotex-A8 you should ues the ARMV7 files.

Best regards,

Mike

---

Digi International Inc http://www.digi.com

Answer 2

CE 7 pre-built binaries is based on architecture but not specific core.
And it is always quite confusing for the ARM's architecture and core names.
Cortex-A8 is the core which is based on ARMv7 architecture.
For more core and architecture relationship, you may refer to http://en.wikipedia.org/wiki/List_of_ARM_microprocessor_cores

Answer 3

The answers  were  helpful for me.

  I installed the Visual studio 2008 and i was able to invoke the plugin ,i tried creating a design by cloning an existing design by following this link http://www.youtube.com/watch?v=-WTer-axwV4 ,but i am unable to succeed after copying the (Eboot.nb0,MLO,NK.bin) in trhe following order to the SD card i am not able to bring up the EVM with WIN7, can i have a solution for it.

Hoping i get a solution ASAP.

Answer 4

Just to summarize:

1) You have OMAP3530 board.

2) You cloned project, built it, got as an output three images mentioned above run the board. Do you see any output from xloader, eboot, kernel is loading

3)  If you not see xloader printouts and you are sure that your serial is working well,

         a) are you sure that strap pins at your board defines SD as boot device?

         b) did you formatted sd card as described in omap spec? I do not remember, there should be fat32 partition with MLO, e/u boot and os image

   Otherwise paste your logs.

   

Answer 5

     1) I am trying to bring up DM8148EVM which is of arm 7 architecture , in this WIKI link they give us the option of considering OMAP3530BSP for testing purpose ,i tried with both (OMAP3530BSP and AM3874BSP provided by TI).

link

http://processors.wiki.ti.com/index.php/WinCE-BSP_ARM-A8_User_Guide#Building_Images

2) YES.

3) a) YES

    b) YES

Answer 6

  Adding to that

After selecting the option from the main menu to boot from SD card the error messages seen in the tera term are.

OEMPreDownload: Filename nk.bin
Init HW: controller RST
SDCARD: requested speed 1000000, actual speed 1000000
SDCARD: requested speed 25000000, actual speed 19200000

BL_IMAGE_TYPE_BIN

+OEMMultiBinNotify(0x8feb1cc0 -> 1)
Download file information:
------------------------------

-----------------------------
[0]: Address=0x80002000  Length=0x03d4672c  Save=0x80002000
-----------------------------------------------------------
Download file type: 1
+OEMIsFlashAddr(0x80002000) g_eboot.type 1
.............................................................................................................................................................................................................................................................................................................................................rom_offset=0x0.
..ImageStart = 0x80002000, ImageLength = 0x3d4672c, LaunchAddr = 0x80008040

Completed file(s):
-------------------------------------------------------------------------------
+OEMIsFlashAddr(0x80002000) g_eboot.type 1
[0]: Address=0x80002000  Length=0x3d4672c  Name="" Target=RAM
ROMHDR at Address 80002044h
Launch Windows CE image by jumping to 0x80008040...

Windows CE Kernel for ARM (Thumb Enabled)
CPU CP15 Control Register = 0xc5387f
CPU CP15 Auxiliary Control Register = 0x42
+OALTimerInit(1, 20000, 200)
--- High Performance Frequecy is 24 MHz---
PID:00400002 TID:00410002 +PrcmPostInit()
PID:00400002 TID:01370006 ECC TYPE is BCH 8 bit with ELM
PID:00400002 TID:01370006 16Bit NAND device
PID:00400002 TID:01370006 NAND manufacturer 17 device 17 : no matching device found
PID:00400002 TID:01370006 FMD driver does not support NAND manufacturer:0x17 dev:0x17
PID:00400002 TID:01370006 ECC TYPE is BCH 8 bit with ELM
PID:00400002 TID:01370006 16Bit NAND device
PID:00400002 TID:01370006 NAND manufacturer 17 device 17 : no matching device found
PID:00400002 TID:01370006 FMD driver does not support NAND manufacturer:0x17 dev:0x17
PID:00400002 TID:01370006 +TLV320AIC3106CodecConfig::EnableMic3: lVol=0x30 rVol=0x30
PID:00400002 TID:01370006 Cpsw3g_InitializeAdapter: mode=1, port=1, ActiveCpgmac=0
PID:00400002 TID:01370006 SDHC: CPU revision 0xffffffff
PID:00400002 TID:01370006 SDHC host controller initialize: m_fastPathSDIO:1 m_fastPathSDMEM:0
PID:00400002 TID:01370006 <1>SysLink version : 02.00.00.67_alpha2 created Dec 19 2011 at 17:38:57
PID:00400002 TID:01370006 UCD_Init: <><><><><><> COMPARE WITH SA
PID:00400002 TID:01370006 CAM3xxOTG::Init DEVCTL 88
PID:00400002 TID:01370006 CAM3xxOTG::Init DEVCTL 88
PID:00400002 TID:01370006 HDMI: >>> configure_hdmi_pll: read_clkctrl=0x08910810 <<<
PID:00400002 TID:01370006 HDMI: Initialized.  hdmi_mode 3
PID:00400002 TID:05870002 Syslink ProcMgr loaded VPSS M3 code successfully
PID:00400002 TID:05870002 PVR:getCpuFamily: 4
PID:00400002 TID:05870002 PVR:omapsgxddgpe getCpuFamily: 4
PID:00400002 TID:05870002 M3 firmware version 0x01000126.
                                                         PID:00400002 TID:01720006 kernel PVRSRV_IOCTL_POWER_SET setting state 1

Answer 7

This is debug build?

Answer 8

Can i know the mistake done by me to resolve this issue.

Answer 9

I told you what was wrong in your other thread on this same problem.   You responded that something about Linux.  Until you figure out what the FMD is failing, you will be stuck.    You could remove hive based registry and it will probably boot up.

---

Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT Eurotech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

Eurotech Inc.
www.Eurotech.com

Answer 10

Your FMD driver is having the issue, with manufacturer id and device id.

"FMD driver does not support NAND manufacturer:0x17 dev:0x17"

Disable hive setting and dont access the NAND in any case first .

Resolve the NAND issue then.

--- Misbah

---

Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com [e-mail]

Answer 11

 Hi Bruce Eitman,Misbah.

    Thanks for your suggestions,

 I tried Disabling the Hive based registry and even checked on the Persistent Hive registry storage,Cross checked with user guide registry and made sure all the register contents match in nand.reg,but the problem is still the same ,THE nand device is not Found.

The below image will show you the disabled catalog item.

 I tried building image by selecting the RAM based registry option in the catalog item, even then the issue is not resolved,

Can you please suggest me what should be done.

Hoping i get reply ASAP.

Answer 12

1. Build the image for RAM based reg settings (This you already did)

2. Exclude NAND driver from your Os design.

3. Under project properties->build option-> Write run time memory to flash, set it "NO"

4. In boot loader you might be accessing NAND try to comment out eg (BLConfigureFlashPartitions()  under eboot\main.c.

If you do this correctly you would be able to load your image to RAM using eth boot and execute from there.

--- Misbah

---

Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com [e-mail]

Answer 13

Hi Misbah and Bruce ,Thanks for your precious time .

I have a question .

I tried a new experiment by Replacing NAND.c with FMd.c and trying to build the solution , i need to know whether i am on the right side of the build or not.

Ill give a brief on what i have done.

Nand.c(It had only this code)
*/
//--------------------------------------------------------------------------
//
//  File: nand.c
//
//  Platform specific funtionality for the NAND driver.
//

#include <windows.h>

void GpmcEnable(BOOL on)
{
    // Nothing to do
    return;
}

After the replacement of FMD.c i renamed it as Nand.c and even modified the NAND.def File.i thought this will resolve the FMD driver issue.

I have even modified the Nand.def files with FMD functions.

As i am Newbie to this field ,please help me out in getting solved this issue.Will this experiment work will it consider it ???????

I have included all the header and def files required .

Answer 14

Adding to that , when i tried to build the OS,i got the following errors.

Error(s) in directory "C:\VS_WINEC7\platform\AM387X_BSP\SRC\DRIVERS\BLOCK\NAND\".
BUILD: [01:0000014595:ERRORE] nand.obj : error LNK2001: unresolved external symbol g_ecctype
BUILD: [01:0000014596:ERRORE] nand.obj : error LNK2019: unresolved external symbol OALPAtoVA referenced in function NAND_Initialize
BUILD: [01:0000014597:ERRORE] elm.obj : error LNK2001: unresolved external symbol OALPAtoVA
BUILD: [01:0000014598:ERRORE] nand.obj : error LNK2019: unresolved external symbol SOCGetGPMCAddress referenced in function NAND_Initialize
BUILD: [01:0000014599:ERRORE] C:\WINCE700\OSDesigns\AM387X_OS\AM387X_OS\Wince700\AM387X_BSP_ARMV7_Retail\cesysgen\platform\AM387X_BSP\target\ARMV7\retail\am387x_nand.dll : fatal error LNK1120: 3 unresolved externals
BUILD: [01:0000014600:ERRORE] NMAKE : fatal error U1077: 'C:\VS_WINEC7\sdk\bin\i386\ARM\link.EXE' : return code '0x460'
BUILD: [01:0000014601:INFO  ] Stop.

Answer 15

I cannot validate whether the experiment that you are doing is correct or not.

Since i dont have the source file and the details of your hardware. Hence cannot comment on this.

The error you are getting is a linking error due to certain lib files are required to be included into your driver sources file.

The libraries required is "Developer-defined" hence you need to find which lib files are required in your case for the functions "OALPAtoVA()", SOCGetGPMCAddress(), and variable "g_ecctype"

Hope this will help!

--- Misbah

---

Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com [e-mail]

Answer 16

   Hi Misbah,

  Thanks for the suggestion ,i tried it and i have a few queries to ask .

I disabled the Nand settings (Am387x_nand.dll,and even the Am387x_nand_sdhc.dll) and even disabled the IMREGHIVE,IMREGHIVE_SD.

and disabled the hive registry settings and persistent based registry ,enabled the RAM based registry.

my question is there any required catalog items to be enabled for Ethernet boot.

i have attached all the catalog items selected please spare some time and look at it and tell is there anything else i need to do , to make my device get detected .

this the output seen in Tera term console.



 [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
 [9] Enable/Disable OAL Retail Messages
 [0] Exit and Continue

 Selection: 0
+Cpsw3gInit(0x4a100000, 0x00000001, 0x8fefff6c) v0.3
g_cpsw3g_reg_base = 0xb0400000
Phy_init: Auto negotitation completed
Cpsw3gInit, wait link up on mac port:1.
link up on port 1, speed 100, full duplex
-Cpsw3gInit
INFO: Boot device uses MAC 40:5f:c2:09:30:41
INFO: *** Device Name EVM387X-12353 ***
+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

Answer 17

Adding to that .

Answer 18

Answer 19

Answer 20

Answer 21

Answer 22

Answer 23

Once the Ethernet Download Settings dialog is showing, restart your device so that the BOOTME messages are sent out while that dialog is listening for them.

---

Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT Eurotech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

Eurotech Inc.
www.Eurotech.com

Answer 24

Did you tried what Bruce has suggested ? Device is sending bootme message and VS is waiting for it, hence looks ok

Your device and development PC should be in the same N/W. Are you assigning static IP or you are using DHCP ?

If you are assigning static ip to the device (boot option 4 network setting)make sure that the device and development PC's IP address should be of same series (for eg PC ip - 10.20.1.1 and device ip - 10.20.1.10) sharing same netmask. IF you are using DHCP for ip in your n/w then you need to enable DHCP in the boot option when the device boots.

Nand_test_driver.dll is also not required.

---- Misbah

---

Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com [e-mail]

Answer 25

   Hi Bruce and Misbah,

  Thanks for the reply and support by you guys.

I tried with the Bruce method and also by disabling the Firewall on my PC.and i also enabled the DHCP with making sure both having the same IP mask address.

Its good to see i was able to detect the device in Ethernet download settings then i gave the command apply

the next step i followed was to attach this device it got attached but i am failing to download the image even though its connected its saying  waiting for download request from device , the device is on here .can i know what is going wrong here.

Answer 26

In this pic ,as you can see it is not allowing me to apply , it allowed me to select for the very first time when it got detected later its not allowing me to select it, rather as soon as the device displays the sent boot me messages it will diretcly take me to device status dialog box.

Answer 27

Device catalog box.

--------------------------------------------------------------------------------
 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
 [9] Enable/Disable OAL Retail Messages
 [0] Exit and Continue

 Selection: 2

--------------------------------------------------------------------------------
 Select Boot Device
--------------------------------------------------------------------------------
 [1] Internal EMAC
 [2] NK from SDCard FILE
 [3] NK from NAND
 [0] Exit and Continue

 Selection (actual Internal EMAC): 1
 Boot device set to Internal EMAC

--------------------------------------------------------------------------------
 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
 [9] Enable/Disable OAL Retail Messages
 [0] Exit and Continue

 Selection: 7
 Do you want save current settings [-/y]? y
Incorrect ECC type setting
 Current settings has been saved

--------------------------------------------------------------------------------
 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
 [9] Enable/Disable OAL Retail Messages
 [0] Exit and Continue

 Selection: 0
+Cpsw3gInit(0x4a100000, 0x00000001, 0x8fefff6c) v0.3
g_cpsw3g_reg_base = 0xb0400000
Phy_init: Auto negotitation completed
Cpsw3gInit, wait link up on mac port:1.
link up on port 1, speed 100, full duplex
-Cpsw3gInit
INFO: Boot device uses MAC 40:5f:c2:09:30:41
INFO: *** Device Name EVM387X-12353 ***
+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 192.168.11.153 Port Dest IP 192.168.11.27 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

+OEMMultiBinNotify(0x8feb1cc0 -> 1)
Download file information:
-----------------------------------------------------------
[0]: Address=0xc0002000  Length=0x03e850e0  Save=0x80002000
-----------------------------------------------------------
Download file type: 6
+OEMIsFlashAddr(0xc0002000) g_eboot.type 6

Answer 28

It is stopping here, i hope i am missing something here which is not allowing it to boot up ,please help me out.....

Answer 29

Hi Misbah,Bruce.

I was able to boot the WINEC7 on 8148EVM.

Thanks for the support provided by you guys.

i need to know how to monitor and see the log file in  system resource monitor (CPU performance)

Answer 30

Rajath,

very good to know that your issue is resolved.

What are the things you did to resolve the issue.  Can you describe it here. This will help the readers.

Also close this post by proposing it as answered.

--- Misbah

---

Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com [e-mail]

Answer 31

Hi Misbah,

Sorry for delayed reply

I reverted back all the changes made to source files of Nand and disabled all the Hive based registry settings in catalog items even the dependencies of Sysgen_hive.

Download file type: 6
+OEMIsFlashAddr(0xc0002000) g_eboot.type 6

this error is actually caused because of the OS is looking for NAND.even though you have given SD boot Switch settings thanks for your help for helping to get OS developed.

Answer 32

Hi Bruce, Misbah.

   I have couple of queries:

1) I am trying to build the Os in debug mode but i am unable to generate MLO file in debug folder,

I set in .bat at the top level by referring to following link-http://msdn.microsoft.com/en-us/library/ee479008.aspx

I even chane the settings in Os design Properties,Configuration manager to create the image in debug directory.

But still i am not able to see the MLO file in Debug folder.

could you please help me in debugging the issue.

Thanks in advance.

Answer 33

What is an MLO file?  MLO is not mentioned on the page that you referenced and I have never heard of one.

Speaking of the page that you mentioned, what did you set in what .BAT file?

Looking over this discussion, it looks like an MLO file is unique to your processor and is not a standard Windows CE file.   Therefore, you may need to look at the sources/dirs files that build your MLO.  They may skip the build if building debug.   This may be becuase a debug build would be too large for the minimal space allocated for it.

---

Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT Eurotech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

Eurotech Inc.
www.Eurotech.com

Answer 34

In addition to Bruce's reply.

MLO file will be generated using XLDRSD.nb0

Below is the application to convert XLDRSD.nb0 to MLO under windows PC

///////////////////////////////////////////////////////////////////////////////////////////////////////

//
// signGP.c
// Read the x-load.bin file and write out the x-load.bin.ift file.
// The signed image is the original pre-pended with the size of the image
// and the load address.  If not entered on command line, file name is
// assumed to be x-load.bin in current directory and load address is
// 0x40200800.

#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <sys/stat.h>
#include <string.h>
#include <malloc.h>


main(int argc, char *argv[])
{
    int    i;
    char    ifname[FILENAME_MAX], ofname[FILENAME_MAX], ch;
    FILE    *ifile, *ofile;
    unsigned long    loadaddr, len;
    struct stat    sinfo;


    // Default to x-load.bin and 0x40200800.
    strcpy(ifname, "XLDRSD.nb0");
    //loadaddr = 0x40200800;
    loadaddr = 0x40200000;

    if ((argc == 2) || (argc == 3))
        strcpy(ifname, argv[1]);

    if (argc == 3)
        loadaddr = strtol(argv[2], NULL, 16);

    // Form the output file name.
    strcpy(ofname, "mlo");
    
    // Open the input file.
    ifile = fopen(ifname, "rb");
    if (ifile == NULL) {
        printf("Cannot open %s\n", ifname);
        exit(0);
    }

    // Get file length.
    stat(ifname, &sinfo);
    len = sinfo.st_size;

    // Open the output file and write it.
    ofile = fopen(ofname, "wb");
    if (ofile == NULL) {
        printf("Cannot open %s\n", ofname);
        fclose(ifile);
        exit(0);
    }

    // Pad 1 sector of zeroes.
    //ch = 0x00;
    //for (i=0; i<0x200; i++)
    //    fwrite(&ch, 1, 1, ofile);

    fwrite(&len, 1, 4, ofile);
    fwrite(&loadaddr, 1, 4, ofile);
    for (i=0; i<len; i++) {
        fread(&ch, 1, 1, ifile);
        fwrite(&ch, 1, 1, ofile);
    }

    fclose(ifile);
    fclose(ofile);
}
////////////////////////////////////////////////////////////////////////////////////////////////////////

--- Misbah

---

Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com [e-mail]

Answer 35

MLO is the name TI uses for the X-Loader binary file on OMAP processors.  Sorry but I don't know how one gets made, either.  On my vendor's BSP, the MLO only gets built for release versions, and not for debug versions.  When I am loading a debug image, I use the "release" MLO.

Answer 36

Hello everyone,

(Bruce,Misbah,I_hart_software)

Let me be more specific to the issue.

@Bruce  MLO=primary boot loader-(XLDRSD.NB0)  

            from this link-http://msdn.microsoft.com/en-us/library/ee479008.aspx , i set the WINCEDEBUG=DEBUG in the batch file of the BSP.

@Misbah

             In debug mode under debug folder i am not able to find any of the XLDR files for instance-(XLDRSD,XLDRNAND,XLDRUART with extensions .NB0/.bin).when i used to build in release mode MLO used to get generated along with XLDRSD.NB0 so it was not necessary to use any application to convert XLDRSD.NB0 to MLO file.

In debug mode i cant use the source file to convert it to MLO as i am not able to see XLDRSD.NB0 getting generated under debug mode in any of the (DEBUG,RELEASE) folders.

@I_hart_software

I tried using the MLO from release build and copied EBBOTSD.NB0,NK.bin from debug build into SD card and tried booting but it couldn proceed after displaying the message

JUMPING to EBOOTSD.NB0

The ebbot menu doesn show to continue further.

I hope i get a solution to boot the evm in DEBUG mode.

Thanks................

Answer 37

Hello everyone ,

i had initiated a new thread for display problem but i have got no response.so i am posting it here give me a solution

Hi Everyone,

I was successful in booting up WINEC7 on DM8148EVM through seniors guidance  in this forum.

Now i am trying to port WINEC7 on custom board(which is same as DM8148EVM with minor changes in NAND flash part numbers).

The problem i am facing at present is , i am able to boot the WINEC7 OS on custom board but the issue is after kernel load it will take around 10 min to load VPSS(display firmware)  and then display comes up at HDMI monitor could you please share your thoughts on this issue and help me in debugging this issue.

 (The custom board has 2GB DDR and the required changes have been done to the source files)There is a delay of around 10 min for the display to come up after the kernel gets downloaded.

Following is the log messages i receive in Tera Term Console.

BL_IMAGE_TYPE_BIN

+OEMMultiBinNotify(0x8feb1cc0 -> 1)
Download file information:
-----------------------------------------------------------
[0]: Address=0x80002000  Length=0x041f5454  Save=0x80002000
-----------------------------------------------------------
Download file type: 1
+OEMIsFlashAddr(0x80002000) g_eboot.type 1
...................................................................................................................................................................................................................................................................................................................................................rom_offset=0x0.
...ImageStart = 0x80002000, ImageLength = 0x41f5454, LaunchAddr = 0x80008040

Completed file(s):
-------------------------------------------------------------------------------
+OEMIsFlashAddr(0x80002000) g_eboot.type 1
[0]: Address=0x80002000  Length=0x41f5454  Name="" Target=RAM
ROMHDR at Address 80002044h
Launch Windows CE image by jumping to 0x80008040...

Windows CE Kernel for ARM (Thumb Enabled)
CPU CP15 Control Register = 0xc5387f
CPU CP15 Auxiliary Control Register = 0x42
+OALTimerInit(1, 20000, 200)
--- High Performance Frequecy is 24 MHz---
DeviceId................. EVM387X-
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......... 0x8420D000
WARN: OALKitlInit: KITL Disabled
PID:00400002 TID:00410002 +PrcmPostInit()

PID:00400002 TID:01330006 +TLV320AIC3106CodecConfig::EnableMic3: lVol=0x30 rVol=0x30

PID:00400002 TID:01330006 SDHC: CPU revision 0xffffffff
PID:00400002 TID:01330006 SDHC host controller initialize: m_fastPathSDIO:1 m_fastPathSDMEM:0
PID:00400002 TID:01330006 <1>SysLink version : 02.00.00.67_alpha2 created Dec 19 2011 at 17:38:57
PID:00400002 TID:01330006 UCD_Init: <><><><><><> COMPARE WITH SA
PID:00400002 TID:01330006 CAM3xxOTG::Init DEVCTL 88
PID:00400002 TID:01330006 CAM3xxOTG::Init DEVCTL 88
PID:00400002 TID:01330006 DllMain(): DEBUGMSG LLTD dll attach.
PID:00400002 TID:01330006 DllMain RETAILMSG RSPNDR_DLL_PROCESS_ATTACH...PID:00400002 TID:01330006 RSPNDR_Init... wm7 PID:00400002 TID:01330006 +++ TopEnableRspndrPolicyCallback:  NdisRegisterProtocolDriver Status : 0 PID:00400002 TID:01330006 RSPNDR_Init: DriverEntry succeeded.PID:00400002 TID:01330006 HDMI: >>> configure_hdmi_pll: read_clkctrl=0x09910812 <<<
PID:00400002 TID:01330006 HDMI: Initialized.  hdmi_mode 3
PID:00400002 TID:02EF0012 CAM3xxOTG[2]::HostMode(): entering host mode
PID:00400002 TID:02EF0012 HcdPdd_Init::CHECK FOR CENTAURUS
PID:00400002 TID:02EF0012 USBH: HcdPdd_SetDevicePower: State 0
PID:00400002 TID:02EF0012 USBH: HcdPdd_SetDevicePower: DEVCTL 0x5D

It stops here and takes around 10 min to download completely and for display to come up on HDMI monitor.

PID:00400002 TID:04380002 Syslink ProcMgr loaded VPSS M3 code successfully
PID:00400002 TID:04380002 PVR:getCpuFamily: 4
PID:00400002 TID:04380002 PVR:omapsgxddgpe getCpuFamily: 4
PID:00400002 TID:04380002 M3 firmware version 0x01000126.
                                                         PID:00400002 TID:01550006 kernel PVRSRV_IOCTL_POWER_SET setting state 2
PID:00400002 TID:01720006 kernel PVRSRV_IOCTL_POWER_SET setting state 0
PID:00400002 TID:01720006 kernel PVRSRV_IOCTL_POWER_SET setting state 1

Hope i get a reply ASAP.

Thanku..........

Answer 38

Adding to that i tried debugging into through enabling kernel debugger and when i tried step into and found out where it hangs for 2 min

it actually enters into DEVICE IO CONTROL function under IPC DRV_IOCTL().

and it does not allow me to step into for next 2 min .

Answer 39

There is a driver possible generating error while loading and consuming CPU resource.

You need to first try finding that. Then remove this driver from loading during boot. Make changes in platform.bib file

Test without this module getting loaded, and see there is no such delay.

Then possible you can built this driver for debug and fix it later.

--- Misbah

---

Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com [e-mail]

Answer 40

Do you have to use HDMI, or could you configure things within the build process so that the default is some other display mode besides HDMI?  That would allow you to determine if the HDMI driver layers are the problem.

Answer 41

Hi,

 The WINEC7 bsp supports only to HDMI display.