About offset 0x017C register of HS-USB Register of i.MX51

[yuuki]

Dear  All,

In FSL WindowsBSP,
We have the problem that a CPU may be hung-up, when a register is written by USB Driver.

When a USB driver writes any value into offset 0x017C of HS-USB register, this problem may occur.

In the source code of WinCE BSP, this register is defined as ENDPTNAKEN.

However, in a reference manual, this 0x017C register is "reserved".

MCIMX51 Multimedia Applications Processor Reference Manual Rev. 1 2/2010
- Table 60-28. HS-USB Register Summary(P.2882)

In Linux BSP source code, this 0x017C register is not defined.

In WinCE,
What kind of function does this 0x017C register have?
Is access(writing) to this 0x017C register required?

Best Regards,
Yuuki

[CommunityBot · Accepted solution]

This an automatic process.

We are marking this post as solved, due to the either low activity or any reply marked as correct.

If you have additional questions, please create a new post and reference to this closed post.

NXP Community!

[igorpadykov]

Hi yuuki

please look below for description,

I think its usage is optional

Best regards

igor

[yuuki]

Dear Igor-san,

Thank you for your support.

Are there any limitations about writing in these fields?
If access to this register is deleted, does a problem occur?

We want to know how to prevent the hang-up of CPU.

Best Regards,
Yuuki

[igorpadykov]

Hi yuuki

access to this register is performed in

..COMMON_FSL_V2/USBD/COMMON/pdd.c

do you mean that this piece of code is not working ?

Also this register is defined in i.MX53 RM IMX53RM

sect.77.6.30 Endpoint Nake Enable (USB_UOG_ENDPTNAKEN)

Best regards

igor

[yuuki]

Dear Igor-san,

Thank you for your support.

> do you mean that this piece of code is not working ?
=>
No.

When it is accessed this register, a CPU may be hung up.
We are looking for this root cause and workaround.

Best Regards,
Yuuki

[igorpadykov]

Hi yuuki

I think answer depends on what do you mean

by "accessed this register" - what method are you using.

Since USB driver is high speed driver, accessing its registers

as not allowed at runtime - this violates USB driver timings, they have

strict timing constraints.

I think you can write own standalone code (without OS) like

On-Board Diagnostic Suit for the i.MX53 Quick Start Board

and try to access these registers.

~igor

[yuuki]

Dear Igor-san,

Thank you for your support.

> I think answer depends on what do you mean
> by "accessed this register" - what method are you using.
=>
The driver in FSL_WinCE6.0 BSP for i.MX51EVK has accessed to the register.

Does standalone code for i.MX51EVK exist?
Would you send it, if you have it?

Best Regards,
Yuuki

[igorpadykov]

Hi yuuki

sorry, there is no official standalone code for i.MX51EVK

but you can request unofficial creatng SR ticket.

~igor