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.

wince 7 slow - BMQ benchmark

Other Parts Discussed in Thread: OMAP3530

Hi,

I tested my custom board (OMAP3530 + latest TI BSP for wince 7) with BMQ benchmark, but regarding 'Window' test the result is quite different from the one I found in http://processors.wiki.ti.com/index.php/WinCE_Comparative_Benchmarks !

Below my results:

Integer 2152

Float 546

Draw 652

Window 280

Memory 2517

Total 1229

Configuration: omap3530 500MHz, 256Mb ram, PowerVR (SGX 121), Display driver + ISP resizer activated, PMExt, SDMA driver + proxy, all directshow filters, cmem, cs, dsplink

 

Where could be the problem?

 

Thanks

 

  • Luca,

    Could you try at 600 MHz? Although the "window" readings you have are extremely low and might only go up a few notches when the modified frequency - that's my guess. When you mention SDMA driver+proxy, do you mean you are running the proxy app or is it just part of the build? What is PMExt?

     

    Do you have a ce6 version for your customised board and if so, were you able to achieve numbers similar to what we have published for ce6 on the wiki?

     

    MPU-600.00 MHz, IVA-430.00 MHz, CORE-332.00 MHz is the setting at which the wiki benchmarks were measured.

    Let us know what you find.

     

    regards,

    Aparna

  • Hi Aparna,

    1) Our omap 3530 doesn't support 720MHz, is it safe to run it at 600MHz? 

    2) I'm not running any application besides BMQ.exe

    3) PMExt is Power Management Extension, as written in the catalog items, it's the only power-related item select (no smart reflex and so on)

    4) I also tested (bmq) the same board with ce6 and the results are comparable

     

    I selected the cpu speed from the eboot menu, so I don't know for sure the speed of cpu, iva and core.

    Also, once the system is running I can read the following key from the registry:

    [HKEY_LOCAL_MACHINE\System\Ceddk]

        "StallCounter"=dword:6A

    Maybe it doesn't matter, but as stated in the platform.reg this value should be set either to 0x85 for 266MHz or 0xA5 for 330MHz.

     

    Regards

     

  • Luca,

    My responses inline

    1) Our omap 3530 doesn't support 720MHz, is it safe to run it at 600MHz? 

    Not sure but since you have a comparable result on ce6, maybe we could leave this for the time being.

    I selected the cpu speed from the eboot menu, so I don't know for sure the speed of cpu, iva and core.

    You can check this by telnetting to platform and doing a "do opm ?" and checking under "Current Frequencies: " in the output.


     

     Also, are you using kitl or a debug build? If I just ftp bmq.exe to the target (temp folder) and telnet to the platform and execute bmq.exe, select all in the bmq gui on target, I have my readings. If your procedure is any different, might be worth trying out this sequence. I am booting from SD card.

    Regards,

    Aparna

  • Aparna,

    I'm using release build, no kitl. I'm also booting from SD card, bmq.exe is on sd card, I run it from there.

    This is what I get from 'do opm ?':

    Current Frequencies: MPU-500.00, IVA-360.00, CORE-332.00

     

    Regards,

    Luca

     

     

  • Luca,

    I ran the test with the same frequency settings as you and with bmq.exe on sd card. My results are as below. Any changes in your BSP with respect to display (overlay, vrfb, etc)? You did mention dsplink, etc. Are you building the DVSDK subproject as well here? Not that any of this should matter but I am just trying to see what else is different from our BSP. At least, we can conclude that it is not the frequency or the method of running the test which is playing a role here.

    Integer 1818

    Float 546

    Draw 584

    Window 656

    Memory 1729

    Total 1066

    regards,

    Aparna

  • Aparna,

    I don't have select vrfb and I'm 'building' the dvsdk subproject. I get the same results using dvi 1024x768x32bpp, dvi 800x600x32bpp, dvi 1024x768x16bpp, lcd 480x272x32bpp.

     

    Regards

    Luca

  • Okay, I dont see the issue even with dvi 1024x768x16bpp. I measure 632 for windows. Wiki benchmark numbers were reported with 480x640x16bpp lcd.

    Aparna