Hi all,
Im not writing the custom driver .
Here one of our team updating the firmware for a chip which supports the
power delivery which inbox driver is using in windows 10.
I’m getting the yellow bank which shows the power device failure.
Ucmusci.sys is a connector manager driver uses the USB type c device.
In windows 10 if the inbox driver were in yellow bank or something happened
it doesn’t boot to windows normally also it were scrolling.
In windows 10 machine it doesn’t have last known good configuration also.
How I can move or how I can store the last known good configuration ?
How I can trace the error if doesn’t move to good configuration using
windbg whether the inbox driver ucmusci.sys has lot of information of print
log which I can see using windbg
Is there how I can move to good configuration in windows 10 ?
If suppose it doesn’t boot to windows normally ?
Windows automatic repair /safe mode also doesn’t boot to windows 10 ?
What are the hardware require for USB type c connector to get certified for
the inbox driver ?
What is the hardware requirements for hlk test ?
Is Mutt device is essential for this ?
Regards,
Prabhakar v
On 4 Jun 2016 7:02 a.m., “Tran Phuc Khanh” wrote:
> Thanks Vivek,
>
> My system have no EC.
>
> I’m contacting with Intel for SMBUS controller about the access.
>
> Thanks,
> KHANH
> On Jun 4, 2016 08:26, “Vivek Gupta” wrote:
>
>> Hi Khanh,
>>
>> You seem to be on the right path as far as Type C/PD is concerned. I am
>> assuming that the target system doesn’t have an EC; I ask because there is
>> an easier solution for EC based type c systems.
>>
>> However, your issue is not related to type c; it is related to the
>> discovery of the device on SMBUS. I think you will need to consult the
>> owner of the SMBUS controller driver for that.
>>
>> Thanks,
>> Vivek
>> ------------------------------
>> From: xxxxx@gmail.com
>> Date: Thu, 2 Jun 2016 09:33:40 +0700
>> Subject: Re: [ntdev] UCMCx Client Driver for USB-C
>> To: xxxxx@lists.osr.com
>>
>> Hi Tim,
>>
>> Thanks for your reply.
>>
>> We have two rear USB type C ports with thunderbolt support. The ports
>> also support charging (dual role) by using Power Delivery(PD) device. The
>> PD device connect to PCH SMBUS interface.
>>
>> As I understand for UCMCx Client Driver implement, we will need install
>> the driver on PD device. That why our driver need to access to PCH SMBUS
>> to enumerate device info, am I wrong here?
>>
>> Thanks,
>> KHANH
>>
>>
>>
>> On Thu, Jun 2, 2016 at 7:10 AM, Tim Roberts wrote:
>>
>> Tran Phuc Khanh wrote:
>> >
>> > I’m writing a UCMCx Client Driver for USB-C as
>> > specs: https://msdn.microsoft.com/en-us/library/windows/hardware/
>> mt188011(v=vs.85).aspx
>> > https:>> hardware/mt188011%28v=vs.85%29.aspx>
>> >
>> > In my case: The devices use I2C pins, I2C_1 PIN connect to Thunder
>> > bolt I2c Interface; I2C_2 PIN connect to PCH SMBUS interface.
>>
>> I’m rather confused by your post. There are no I2C pins in a USB-C
>> connector, nor in a Thunderbolt connector. Further, each I2C bus
>> requires two pins, not just one. Can you try to describe your
>> configuration in more detail?
>>
>>
>> > I tried to enumerate SMBUS information in my driver follow the
>> > specs: http://smbus.org/specs/smbus_driver_ext_arch10.pdf but got NOT
>> > FOUND result. My device is using Windows 10 with Intel Sky-lake.
>>
>> This is not an easy area to deal with. The SMBus has traditionally been
>> reserved for the BIOS, so drivers don’t play there. What information
>> were you trying to get? Are you quite sure that your SMBus peripherals
>> are enumerated in your ACPI DSDT?
>>
>> –
>> 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>
>>
>>
>> — NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars
>> on crash dump analysis, WDF, Windows internals and software drivers!
>> Details at To unsubscribe, visit the List Server section of OSR Online at
>>
>> —
>> 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>
>>
> — NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars
> on crash dump analysis, WDF, Windows internals and software drivers!
> Details at To unsubscribe, visit the List Server section of OSR Online at</http:></http:></http:></http:></https:>