• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 99 subscribers
  • Views 1328 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

OMAP-L138 CETK COM Tests and Storage Tests

1258021
Genius 5120 points
Other Parts Discussed in Thread: OMAP-L138, OMAPL138

Hi,

I am using OMAP-L138 WinCE BSP and I have executed CETK tests on COM3 and Storage Device Tests on SD Card.

My observation is below,

Serial Tests: CETK Test Case Id 11 is failing. The below is the few lines from the CETK Test Log

BEGIN GROUP: SERDRVBVT.DLL
   <TESTCASE ID=11>
   *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
   *** TEST STARTING
   ***
   *** Test Name:      Send bytes at all supported bauds, data-bits, parity and stop-bits
   *** Test ID:        11
   *** Library Path:   \serdrvbvt.dll
   *** Command Line:   -p COM3:
   *** Kernel Mode:    No
   *** Random Seed:    467
   *** Thread Count:   1
   *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
   BEGIN TEST: "Send bytes at all supported bauds, data-bits, parity and stop-bits", Threads=1, Seed=467
      Send bytes at all supported bauds, data-bits, parity and stop-bits on COM3
      Calling GetCommProperties() on COM3
      COM3 does not support 110 baud
      COM3 does not support 300 baud
      COM3 does not support 600 baud
      COM3 does not support 1200 baud
      Calling GetCommState() on COM3
      Calling GetCommTimeouts() on COM3
      WARNING in C:\yzqa\private\test\BaseOS\Drivers\Serial\BVT\serdrvbvt\.\testproc.cpp at line 221: GetCommTimeouts()
      WARNING!! :: WriteTotalTimeoutConstant in serial driver on COM3 == 0.....may create undesired hangs in system
      Setting WriteTotalTimeoutConstant to 100 so test will not hang
      Calling SetCommTimeouts() on COM3
      Calling SetCommState() on COM3
      SetCommState() failed on COM3, 2400 baud, 5 data-bits, No parity, 1 stop-bits
      ERROR in C:\yzqa\private\test\BaseOS\Drivers\Serial\BVT\serdrvbvt\.\testproc.cpp at line 262: SetCommState(); error 87


Storage tests (Standard SD Card 2GB):

On storage card File System Driver test (rw_all test case is failing) and Storage Device Block Driver Benck Mark test is failing.

Anybody has seen different results from the above ?

Thank You & Regards,

GSR

 

  • 0
    TI__Intellectual 805 points

    For storage SD card tests, do you see all of them failing or just a few test case failing. Could you give us more information? what is the command line option you are using?

     

    Regards,

    Yan

  • 0 in reply to yaliu_2000
    Genius 5120 points

    Hi Yan,

    Thank You for replying.

    I am using -c "-p SDMemory -zorch"

    Here it is the few lines of the log from CETK Results.

    For File System Driver Test I am seeing the following test cases were failing 5010, 5011, 5012, 5013, 5014, 5015, 5016, 5017, 5018 - 5032. The attached File System Driver Test Failed Test Results.txt contains the log.

    7128.File System Driver Test Failed Test Results.txt

    Thank You & Regards,

    GSR

  • 0 in reply to 1258021
    TI__Intellectual 805 points

    Hi GSR,

    I just run the same test 5010 with the same command option and test pass on the latest wince BSP release for omapl138. Do you have the same problem with other SD cards? Are you using Omapl138 EVM with released BSP or you are using customized platform / BSP?

     

    Regards,

    Yan

  • 0 in reply to yaliu_2000
    Genius 5120 points

    Hi Yan,

    We are using the Logic-PD EVM and the BSP downloaded from TI URL.

    Basically what I have observed is as soon as the display goes to off the SD Tests are failing.

    So, what I have done is when I increased the values for ACUserIdle and ACSystemIdle the SD Card tests are passing.

    Was this behaviour not seen at your end ?

    Do you have any information on why Serial CETK Tests case Id 11 was failing ?

    Thank You & Regards,

    GSR

  • 0 in reply to 1258021
    TI__Intellectual 2525 points

    Hi GSR,

    Test case ID 11 could fail if the UART on the platform does not support features requested by the test case - DTR/DSR, CTS/RTS.

    Having said that, I do see these failures even when RtsCtsFlowCtl has been set to 1 in the registry. We will keep you updated as soon as we have some additional information about this test result.

    Regards,

    Aparna

  • 0 in reply to 1258021
    TI__Intellectual 805 points

    I don't see this problem you described so far.

     

    Regards,

    Yan

  • 0 in reply to Aparna Balasubramanian
    TI__Intellectual 2525 points

    Hi GSR,

    The UART on this platform does not support DTR. The pdd code for the serial driver would need to be modified as follows to initalize the DTRcontrol to be disabled (which is initialized to be enabled by the MDD).

    Alternately, the test code can do the correct initliazation (sample is provided in the BSP - uarttest application).

    regards,

    Aparna

    Please update the code at the start of COMAPL13xSerial::SetDCB() to:

    if (m_dwRtsCtsFlowCtrl)

    {

    // UART supports RTS/CTS flow control

    pDCB->fOutxDsrFlow = FALSE;

    pDCB->fDtrControl = DTR_CONTROL_DISABLE;

    }

    else

    {

    // UART does not support RTS/CTS flow control

    pDCB->fOutxCtsFlow = FALSE;

    pDCB->fOutxDsrFlow = FALSE;

    pDCB->fDtrControl = DTR_CONTROL_DISABLE;

    pDCB->fRtsControl = RTS_CONTROL_DISABLE;

    }

  • 0 in reply to Aparna Balasubramanian
    Genius 5120 points

    Hi Aparna Balasubramanian,

    Thank You for replying.

    After adding the code to BSP the serial test case Id: 11 is passing.

    I am still seeing the problem with SD Card that the tests are failing as soon as Display goes to off state.

    I have opened the Remote File Viewer from Remote Tools in VS2005.

    As long as Display is in ON state I can see the folder named as SDCard in the Remote File Viewer. Once the Display goes off when I refresh SDCard disappears.

    This means at this time if I run Storage Tests for SD Card they shall fail which is expected right?

    But in my previous posts one of the TI Employee is seeing different behaviour why is it so?

    Thank You & Regards,

    GSR

     

  • 0 in reply to 1258021
    Genius 5120 points

    Hi,

    Processor: OMAP-L138 OS: WinCE 6.0 R3

    Has any one seen the problem with SD Card.

    The problem that we are facing is, once the display goes off if we tap on touch screen the Display comes up with out any issue. But, when we check the SD Card availability its not mounted.

    Any inputs on this.

    Thank You & Regards,

    GSR

  • 0 in reply to 1258021
    TI__Intellectual 2525 points

    GSR,

    I am unable to see the problem with TI BSP version - BSP_WINCE_ARM9.01.00.02

    The display does not go off by default in my setup. So, I am curious to know if you made any changes in the code or passed some commands to move display to idle.

    To reproduce the problem on my setup, I telnet to the platform and send the command - pmtimeout set 10 10. This will set the user idle and system idle timeout values to 10 sec.

    Once the display goes to idle, I do not see "SDCard" mount point listed (using "dir" command from telnet).

    When I tap on the touchscreen and display is back up, I see that "SDCard" is listed again.

    Regards,

    Aparna

  • 0 in reply to Aparna Balasubramanian
    Genius 5120 points

    Hi Aparna Balasubramanian,

    Thank You the reply.

    I am very sorry. Today when I tested I had observed the same behaviour as you did.

    Regards,

    GSR