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.

EHCI data abort after resum.

Other Parts Discussed in Thread: AM3715

Hi,

Our customer use WinCE BSP version 6.1x and platform is AM3715.

They have EHCI/OHCI data abort issue when resuming.

I dump the registers setting of the PRCM list below.

 

The PRCM setting without error when resuming:

RM_RSTST_USBHOST = 4
PM_WKEN_USBHOST = 1
PM_MPUGRPSEL_USBHOST = 1
PM_IVA2GRPSEL_USBHOST = 1
PM_WKST_USBHOST = 0
PM_WKDEP_USBHOST = 2
PM_PWSTCTRL_USBHOST = 30105
PM_PWSTST_USBHOST = 3
PM_PREPWSTST_USBHOST = 1
CM_FCLKEN_USBHOST = 3
CM_ICLKEN_USBHOST = 1
CM_IDLEST_USBHOST = 0
CM_AUTOIDLE_USBHOST = 1
CM_SLEEPDEP_USBHOST = 2
CM_CLKSTCTRL_USBHOST = 3

CM_CLKSTST_USBHOST = 1

 

The PRCM setting with data abort when resuming:

RM_RSTST_USBHOST = 4
PM_WKEN_USBHOST = 1
PM_MPUGRPSEL_USBHOST = 1
PM_IVA2GRPSEL_USBHOST = 1
PM_WKST_USBHOST = 0
PM_WKDEP_USBHOST = 2
PM_PWSTCTRL_USBHOST = 30105
PM_PWSTST_USBHOST = 100003
PM_PREPWSTST_USBHOST = 0
CM_FCLKEN_USBHOST = 3
CM_ICLKEN_USBHOST = 1
CM_IDLEST_USBHOST = 3
CM_AUTOIDLE_USBHOST = 1
CM_SLEEPDEP_USBHOST = 2
CM_CLKSTCTRL_USBHOST = 3
CM_CLKSTST_USBHOST = 0

It seems the data abort is caused by accessing the USB host registers when USB HOST domain still in idle state.

But we don't know why and how to fix/avoid this issue.

Has anyone else seen this problem or help us to slove this issue?

  • BSP 6.1x is no longer supported.  Couple of suggestions.

    1. Can you be more specific than BSP 6.1x? Is it BSP 6.15, or 6.14? If they are not on BSP 6.15 then they could compare with the BSP 6.15 release (last in the BSP 6.xx series) . Better yet we recommend that the customer upgrade to the latest version given below.

    2. The latest BSP release (for WinCE6) can be found here. 

    http://software-dl.ti.com/sdoemb/sdoemb_public_sw/wince_sdk/latest/index_FDS.html

    Can your customer try the latest release on TI EVM to see if the problem can be recreated. If they cannot upgrade to this release then I would suggest that they compare the latest release with the one they have to find out what maybe wrong.