MUTT device exerciser -regarding

NTDEV
1

Hi all,

I have used the MUTT model 3101 and connected the USB type b to power up and got the 0 voltage and 0 ampere in led display , then it shows the light indication in USB B(J6) and plan to use for HLK test cases.

It shows the " USB Serial Device (COM3) " in device manager in windows 10.

if it power up means we can use it for HLK and is there any thing to do over that device ?

Pls help on this.

Regards,

PRabhakar V

2

xxxxx@gmail.com wrote:

Hi all,

I have used the MUTT model 3101 and connected the USB type b to power up and got the 0 voltage and 0 ampere in led display , then it shows the light indication in USB B(J6) and plan to use for HLK test cases.

It shows the " USB Serial Device (COM3) " in device manager in windows 10.

if it power up means we can use it for HLK and is there any thing to do over that device ?

Have you read the documentation? I don’t know what more we can add.

https://msdn.microsoft.com/en-us/library/windows/hardware/mt644884.aspx

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

Hi Tim, it’s correct behaviour. Where we can connect the SUT on J1 and J2
and J3 where we can connect the USB type c cable to other ucsi capabale
device.

But for hlk I were bit confused.

SUT is also a ucsi system in which we have installed hlk client and connect
it to J1 and how we can connect t partner system where we can mention that
name in hlk server ?

Regards,
Prabhakar v

On 7 Mar 2017 1:35 a.m., “Tim Roberts” wrote:

> xxxxx@gmail.com wrote:
> > Hi all,
> >
> > I have used the MUTT model 3101 and connected the USB type b to power up
> and got the 0 voltage and 0 ampere in led display , then it shows the light
> indication in USB B(J6) and plan to use for HLK test cases.
> >
> > It shows the " USB Serial Device (COM3) " in device manager in windows
> 10.
> >
> > if it power up means we can use it for HLK and is there any thing to do
> over that device ?
>
> Have you read the documentation? I don’t know what more we can add.
>
> https://msdn.microsoft.com/en-us/library/windows/hardware/mt644884.aspx
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>

4

Prabhakar V wrote:

Hi Tim, it’s correct behaviour. Where we can connect the SUT on J1
and J2 and J3 where we can connect the USB type c cable to other ucsi
capabale device.

But for hlk I were bit confused.

SUT is also a ucsi system in which we have installed hlk client and
connect it to J1 and how we can connect t partner system where we can
mention that name in hlk server ?

The HLK server does not need to know about the “partner system”. It’s
just used to provide a host-type port for testing. In some of the
tests, you hook the partner system up to J2. In some tests you hook it
up to J6.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

5

I were keep on posting Tim for this help from msdn.
I have not get proper response.
If I’m wrong they have atleast to point me.

Suppose the mutt connection exerciser setup I have done it.

Please don’t hesitate on in keep on asking .
Setup:

  1. UCSI_1 capable system which has hlk client and act as a SUT and will be
    viewed on hlk server.
  2. sut is connected to mutt device of J1 and J2 and J3 is connected to
    other ucsi_2 capable system through USB type c device.
    3)on both ucsi system where I have loaded the test ucsi.sys in which I have
    updated the ucsi driver of inbox driver ucmusci.sys

This is the connection i were made and read from the msdn.

Now how the server will run test cases on server machine and communicate to
mutt device to other ucsi_2 system via USB type c cable

Partner system how to be in hlk machine.
Ucsi_1 is a SUT device and listed in hlk server.

I were little confused whether this setup is correct ?
Still I need to figure out wat was missing.
,
Regards,
Prabhakar v

On 7 Mar 2017 11:32 p.m., “Tim Roberts” wrote:

> Prabhakar V wrote:
> > Hi Tim, it’s correct behaviour. Where we can connect the SUT on J1
> > and J2 and J3 where we can connect the USB type c cable to other ucsi
> > capabale device.
> >
> > But for hlk I were bit confused.
> >
> > SUT is also a ucsi system in which we have installed hlk client and
> > connect it to J1 and how we can connect t partner system where we can
> > mention that name in hlk server ?
>
>
> The HLK server does not need to know about the “partner system”. It’s
> just used to provide a host-type port for testing. In some of the
> tests, you hook the partner system up to J2. In some tests you hook it
> up to J6.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:></http:>

6

Prabhakar V wrote:

Please don’t hesitate on in keep on asking .

One of the things you haven’t said is “what do you actually see”? Are
the tests running at all?

  1. UCSI_1 capable system which has hlk client and act as a SUT and
    will be viewed on hlk server.
  2. sut is connected to mutt device of J1 and J2 and J3 is connected to
    other ucsi_2 capable system through USB type c device.

Your sentence is a little confusing here, because we can’t tell which
system is plugged into which jack. Your SUT should be plugged into J1.
J2 (for some tests) should be plugged into an ordinary USB-C connector.
J3 (for some tests) should be plugged into a USB 2 connector.

3)on both ucsi system where I have loaded the test ucsi.sys in which I
have updated the ucsi driver of inbox driver ucmusci.sys

I’m pretty sure the partner system should NOT have your modifications
It is supposed to be a known-good USB-C setup.

Now how the server will run test cases on server machine and
communicate to mutt device to other ucsi_2 system via USB type c cable

How? The server remotely controls the client (SUT) computer, installing
special drivers and running applications that communicate with the
MUTT. It doesn’t have to communicate with the partner system.

I were little confused whether this setup is correct ?
Still I need to figure out wat was missing.

Why is something missing? What happens?

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.