XPECMD -- using deptree to find which components need component X

J

jimt

I am building the XP Pro emulation configuration with the TAP.exe derived
component on FP2007. In TD, auto-resolve is adding the "CompactPCI Hot Swap
Support" component. The Info record in the TD log says this addition was
originated by the "Generic CompactPCI Chassis" module. Ok, makes sense.

But.. If I start xpecmd, connect to the database, and run deptrace on
"CompactPCI Hot Swap Support" the Chassis module is not reported as a
"dependee". I thought that deptrace was supposed to report which components
depend on the specified component.

My question is: Why wasn't the "Generic CompactPCI Chassis" module reported
in the following DEPTRACE output?

xpecmd>deptrace foo 'comp:CompactPCI Hot Swap Support'
Analyzing Database... 100%
Components: [4 items]
----- ------------
Index: Value
----- ------------
1: Force Computers CPCI-731 [R1507]
3: Generic Intel-21554 based non-system slot board [R1507]
4: Intel NetStructure ZT 5541 Peripheral Master Processor Board [R1507]
2: Motorola CPV 8540 [R1507]
xpecmd>

Just for grins, here is a list of components that "CompactPCI Hot Swap
Support" is dependent on:

xpecmd>deptree 'comp:CompactPCI Hot Swap Support'
Dependency tree for: CompactPCI Hot Swap Support [Version 5.1.2600.1106,
R1507]
+-> Dependency: Dependency on "I/O Error Log Messages" caused by
"IOLOGMSG.DLL"
+-> Dependency: Dependency on "Primitive: Setupapi" caused by
"SETUPAPI.DLL"
+-> Dependency: Dependency on "Win32 API - Advanced" caused by
"ADVAPI32.DLL"
+-> Dependency: Dependency on "Win32 API - Kernel" caused by
"KERNEL32.DLL"
+-> Dependency: CompactPCI Hot Swap feature requires exactly 1
CompactPCI chassis.
+-> Dependency: CompactPCI Hot Swap feature requires one or more
CompactPCI compatible CPU boards.
+-> Dependency: (from group) -> (include class) Group: CompactPCI Base
Hot Swap Support [Version 5.1.2600.1106, R1507]
xpecmd>


FYI, version info:

FP2007, xpecmd 'ver' reports:

XPECMD version : 3.15.674
VBSUtils version : 2.07.674
VBSClasses version : 2.03.674
CMI revision : 578
 
K

KM

jimt,

I am not sure how the deptrace works but here is what I see using ConfigurationExplorer.

The list of dependencies for the "CompactPCI Hot Swap Support" is the same as you mentioned below.

But for the XP Pro Emulation project the components that depends and bring in the "CompactPCI Hot Swap Support" are as follows:
Generic CompactPCI Chassis [Version 5.1.2600.1106, R1507], [Visibility=1000]
Generic CompactPCI CPU board [Version 5.1.2600.1106, R1507], [Visibility=1000]

(it doesn't show the other hardware related components that depends on the CompactPCI Hot Swap support because the initial XPPro
Config doesn't have any hardware related components included)

Also, "Standard PC" HAL depends on the "Generic CompactPCI CPU board" component.

That means if you removes the above two components from your image config and replace the "Standard PC" with an ACPI PC component
(whta your target hardware supports?) you shouldn't see the "CompactPCI Hot Swap Support" appearing there again in the config.
Otheriwse, if "Standard PC" HAL is what you need to use, you will have to live with one error (task) in your build (dependency
checker) log. Assuming you turned off the dependency auto resolver in TD.



--
=========
Regards,
KM

I am building the XP Pro emulation configuration with the TAP.exe derived component on FP2007. In TD, auto-resolve is adding the
"CompactPCI Hot Swap Support" component. The Info record in the TD log says this addition was originated by the "Generic
CompactPCI Chassis" module. Ok, makes sense.

But.. If I start xpecmd, connect to the database, and run deptrace on "CompactPCI Hot Swap Support" the Chassis module is not
reported as a "dependee". I thought that deptrace was supposed to report which components depend on the specified component.

My question is: Why wasn't the "Generic CompactPCI Chassis" module reported in the following DEPTRACE output?

xpecmd>deptrace foo 'comp:CompactPCI Hot Swap Support'
Analyzing Database... 100%
Components: [4 items]
----- ------------
Index: Value
----- ------------
1: Force Computers CPCI-731 [R1507]
3: Generic Intel-21554 based non-system slot board [R1507]
4: Intel NetStructure ZT 5541 Peripheral Master Processor Board [R1507]
2: Motorola CPV 8540 [R1507]
xpecmd>

Just for grins, here is a list of components that "CompactPCI Hot Swap Support" is dependent on:

xpecmd>deptree 'comp:CompactPCI Hot Swap Support'
Dependency tree for: CompactPCI Hot Swap Support [Version 5.1.2600.1106, R1507]
+-> Dependency: Dependency on "I/O Error Log Messages" caused by "IOLOGMSG.DLL"
+-> Dependency: Dependency on "Primitive: Setupapi" caused by "SETUPAPI.DLL"
+-> Dependency: Dependency on "Win32 API - Advanced" caused by "ADVAPI32.DLL"
+-> Dependency: Dependency on "Win32 API - Kernel" caused by "KERNEL32.DLL"
+-> Dependency: CompactPCI Hot Swap feature requires exactly 1 CompactPCI chassis.
+-> Dependency: CompactPCI Hot Swap feature requires one or more CompactPCI compatible CPU boards.
+-> Dependency: (from group) -> (include class) Group: CompactPCI Base Hot Swap Support [Version 5.1.2600.1106, R1507]
xpecmd>


FYI, version info:

FP2007, xpecmd 'ver' reports:

XPECMD version : 3.15.674
VBSUtils version : 2.07.674
VBSClasses version : 2.03.674
CMI revision : 578
Click to expand...
 
S

Sean Liming \(eMVP\)

Using my Component Hunter tool, I am getting the same result. There doesn't
seem to be a dependency relationship between CompactPCI Hot Swap Support and
Generic CompactPCI Chassis. In fact, Generic CompactPCI Chassis doesn't seem
to have any relationships with other components in the database.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit
 
K

KM

Sean,

Dependency on the "CompactPCI Hot Swap Support" is inherited by "Generic CompactPCI Chassis" via its prototype "Prototype:
CompactPCI Chassis" component.
The same way the "Generic CompactPCI Chassis" component inherits dependency on "CompactPCI Base Hot Swap Support'.

Please see the base component chain for the "CompactPCI Hot Swap Support".

Prototype dependencies is what probably new DEPTRACE tool is not tracing.

--
=========
Regards,
KM
Using my Component Hunter tool, I am getting the same result. There doesn't seem to be a dependency relationship between
CompactPCI Hot Swap Support and Generic CompactPCI Chassis. In fact, Generic CompactPCI Chassis doesn't seem to have any
relationships with other components in the database.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit


jimt said:
I am building the XP Pro emulation configuration with the TAP.exe derived component on FP2007. In TD, auto-resolve is adding the
"CompactPCI Hot Swap Support" component. The Info record in the TD log says this addition was originated by the "Generic
CompactPCI Chassis" module. Ok, makes sense.

But.. If I start xpecmd, connect to the database, and run deptrace on "CompactPCI Hot Swap Support" the Chassis module is not
reported as a "dependee". I thought that deptrace was supposed to report which components depend on the specified component.

My question is: Why wasn't the "Generic CompactPCI Chassis" module reported in the following DEPTRACE output?

xpecmd>deptrace foo 'comp:CompactPCI Hot Swap Support'
Analyzing Database... 100%
Components: [4 items]
----- ------------
Index: Value
----- ------------
1: Force Computers CPCI-731 [R1507]
3: Generic Intel-21554 based non-system slot board [R1507]
4: Intel NetStructure ZT 5541 Peripheral Master Processor Board [R1507]
2: Motorola CPV 8540 [R1507]
xpecmd>

Just for grins, here is a list of components that "CompactPCI Hot Swap Support" is dependent on:

xpecmd>deptree 'comp:CompactPCI Hot Swap Support'
Dependency tree for: CompactPCI Hot Swap Support [Version 5.1.2600.1106, R1507]
+-> Dependency: Dependency on "I/O Error Log Messages" caused by "IOLOGMSG.DLL"
+-> Dependency: Dependency on "Primitive: Setupapi" caused by "SETUPAPI.DLL"
+-> Dependency: Dependency on "Win32 API - Advanced" caused by "ADVAPI32.DLL"
+-> Dependency: Dependency on "Win32 API - Kernel" caused by "KERNEL32.DLL"
+-> Dependency: CompactPCI Hot Swap feature requires exactly 1 CompactPCI chassis.
+-> Dependency: CompactPCI Hot Swap feature requires one or more CompactPCI compatible CPU boards.
+-> Dependency: (from group) -> (include class) Group: CompactPCI Base Hot Swap Support [Version 5.1.2600.1106, R1507]
xpecmd>


FYI, version info:

FP2007, xpecmd 'ver' reports:

XPECMD version : 3.15.674
VBSUtils version : 2.07.674
VBSClasses version : 2.03.674
CMI revision : 578
Click to expand...
Click to expand...
 
S

Sean Liming \(eMVP\)

That would make sense. XPECMD like my tool are just looking at the database
tables.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit


KM said:
Sean,

Dependency on the "CompactPCI Hot Swap Support" is inherited by "Generic
CompactPCI Chassis" via its prototype "Prototype: CompactPCI Chassis"
component.
The same way the "Generic CompactPCI Chassis" component inherits
dependency on "CompactPCI Base Hot Swap Support'.

Please see the base component chain for the "CompactPCI Hot Swap Support".

Prototype dependencies is what probably new DEPTRACE tool is not tracing.

--
=========
Regards,
KM
Using my Component Hunter tool, I am getting the same result. There
doesn't seem to be a dependency relationship between CompactPCI Hot Swap
Support and Generic CompactPCI Chassis. In fact, Generic CompactPCI
Chassis doesn't seem to have any relationships with other components in
the database.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit


jimt said:
I am building the XP Pro emulation configuration with the TAP.exe derived
component on FP2007. In TD, auto-resolve is adding the "CompactPCI Hot
Swap Support" component. The Info record in the TD log says this
addition was originated by the "Generic CompactPCI Chassis" module. Ok,
makes sense.

But.. If I start xpecmd, connect to the database, and run deptrace on
"CompactPCI Hot Swap Support" the Chassis module is not reported as a
"dependee". I thought that deptrace was supposed to report which
components depend on the specified component.

My question is: Why wasn't the "Generic CompactPCI Chassis" module
reported in the following DEPTRACE output?

xpecmd>deptrace foo 'comp:CompactPCI Hot Swap Support'
Analyzing Database... 100%
Components: [4 items]
----- ------------
Index: Value
----- ------------
1: Force Computers CPCI-731 [R1507]
3: Generic Intel-21554 based non-system slot board [R1507]
4: Intel NetStructure ZT 5541 Peripheral Master Processor Board [R1507]
2: Motorola CPV 8540 [R1507]
xpecmd>

Just for grins, here is a list of components that "CompactPCI Hot Swap
Support" is dependent on:

xpecmd>deptree 'comp:CompactPCI Hot Swap Support'
Dependency tree for: CompactPCI Hot Swap Support [Version
5.1.2600.1106, R1507]
+-> Dependency: Dependency on "I/O Error Log Messages" caused by
"IOLOGMSG.DLL"
+-> Dependency: Dependency on "Primitive: Setupapi" caused by
"SETUPAPI.DLL"
+-> Dependency: Dependency on "Win32 API - Advanced" caused by
"ADVAPI32.DLL"
+-> Dependency: Dependency on "Win32 API - Kernel" caused by
"KERNEL32.DLL"
+-> Dependency: CompactPCI Hot Swap feature requires exactly 1
CompactPCI chassis.
+-> Dependency: CompactPCI Hot Swap feature requires one or more
CompactPCI compatible CPU boards.
+-> Dependency: (from group) -> (include class) Group: CompactPCI
Base Hot Swap Support [Version 5.1.2600.1106, R1507]
xpecmd>


FYI, version info:

FP2007, xpecmd 'ver' reports:

XPECMD version : 3.15.674
VBSUtils version : 2.07.674
VBSClasses version : 2.03.674
CMI revision : 578
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

DependencyExplorer does not show components that need the named component 5

Top