[DM6446]USB2.0 BulkIN transacion issue

Masaharu Takahashi

Expert 4170 points

Other Parts Discussed in Thread: OMAPL138

Hi All.

This is Masaharu Takahashi in Japan.

Could you tell me as below question?

[DM6446 USB2.0 High-Speed BulkIN Transaction.]

At my customer's system, DM6446 USB2.0 are used as High-Speed device(peripheral).
It is connected to Host PC(USB Host) and they are having problem during BulkIN transaction.
(This system is non-OS)

While USB communication are working fine,
sometimes DM6446 USB won't send any response(DATA/NACK/STALL) after IN Token send from the Host USB.
And Host USB keep sending IN Token 3 times continuously whether USB device(DM6446) are not sending response.

After Host sending IN Token 3 times as above, Host are sending next SOF,
and it seems Bulk Transaction are woriking fine again.

What kind of things will cause this issue?

question 2.

[USB Revision]

Could you tell me what is USB Revision for DM6446BZWT as well OMAP L137 ?

Thanks,

Best Regards,

Masaharu Takahashi

over 8 years ago

0 Senthilkumar Srinivasan over 8 years ago

TI__Mastermind 43660 points

Masaharu,

I think the same customer has posted this query in OMAPL138 forum as well. It will be addressed soon.

e2e.ti.com/.../507035

Regards,
Senthil

0 Masaharu Takahashi over 8 years ago in reply to Senthilkumar Srinivasan

TI__Expert 4170 points

Hi, SenthilKumar Srinivasan.

that's same trouble.
he is distributor for the customer what i've supported.
it'd be nice if you could suggest anything.

Thanks,
Best Regards,.
Masaharu

0 Sivaraj Kuppuraj over 7 years ago in reply to Masaharu Takahashi

TI__Mastermind 35645 points

Hi,

Kindly don't create duplicate posts on different forum on the same issue.

I think, your request was addressed on the other post on OMAPL13x forum as below:
e2e.ti.com/.../1839147

Kindly follow it up on the above post. Hereby closing this post.

Thanks for your understanding.

Regards,
Sivaraj K

0 Ravi B over 7 years ago

TI__Expert 7885 points

The 3 IN transaction shown in the bus capture, where the host issued the IN token but there is no response from the device, this kind of situation is possible if the IN token is not received at device side or lost or corrupted during the transmission or device received the IN token with error, during this scenario the device drop the packet and does not respond.

Regards

Ravi