Standard PC and ACPI confliction.

[SAM Yoon]

Dear,

I have a confliction with Standard PC and ACPI. I got a PQM file from my
target and my target dosn't support ACPI. After that, I merged that PQM file
into my database. In TD, whenever I do a dependency check, TD automatically
install ACPI item and make a confliction. Also, I tried to turn off the
Autoreserve option in TD, but it doesn't work. I don't need ACPI function.
Why does it has problem?

Did someone solve this problem?

SAM

 

[Slobodan Brcin \(eMVP\)]

Hi SAM,

Remove ACPI and find all component that have dependency on ACPI component and remove them as well.

Best regards,
Slobodan

 

[Matt Kellner \(MS\)]

Hi Sam. If the ACPI HAL component is appearing in your configuration on
dependency check, it means that either you are including a macro component
that specifically calls for the ACPI module, or one of the components in
your runtime has a dependency on ACPI. (This may include power-management
functionality.) If you are using a macro component (such as a specific
scenario macro), you should check its settings to see if ACPI is being
called automatically - if so, the component will be checkmarked in the list
under Settings.

Did you import your PMQ file into an existing SLX or create a new SLX? If
you pulled it into an existing SLX, the new components found in the PMQ are
likely to conflict with existing components. It's always best to import
your PMQ into a brand new SLX and then build your runtime around that.

Please let me know if this helps resolve your issue. Thanks. =)

--
----------
Matt Kellner ([email protected])
STE, Windows Embedded Group

This posting is provided "AS IS" with no warranties, and confers no rights.
===============================

 

[SAM Yoon]

Thank you so much.

BTW, How could I know that some devices has dependencies with ACPI
component? How could I check it in TD?

Thank you so much, again.

 

[KM]

SAM,

If you turn off "Auto-Resolve" dependency option in TD and run Dependency Checker again, you will get a bunch of errors (tasks) that
tell you what components require dependencies that are not in your image.

Or you can use DependencyExplorer component from www.xpefiles.com (Development Utilities/Main folder/XPeTools package).

 

[SAM Yoon]

Thank you so much.

I made a brand new SLX file.
Even though I imported only my target hardware SLX, It made that problem. I
didn't add any other GUIs or other platforms but just import my hardware
database and checked dependency check in TD and found ACPI and Standard PC
confliction.

Thank you so much, again.

Have a good day.

 

[Matt Kellner \(MS\)]

Are you using a scenario component (such as RPOS, Gaming Kiosk, etc.)? If
so, which one?

--
----------
Matt Kellner ([email protected])
STE, Windows Embedded Group

This posting is provided "AS IS" with no warranties, and confers no rights.
===============================