Component design

[DPM]

Tools: Standard, SP1
Platform: XPpro SP2

I'm still struggling with getting a custom hardware component to work.
Here's what I did:

1. Installed XPpro and the XPe toolset on my target;
2. Installed the driver (video adapter);
3. Copied the relevant files to a separate folder;
4. Opened CD and imported the INF file;
5. Copied the SLD and driver files to a folder on my development machine;
6. Opened CD, loaded the SLD;
7. On the left pane in CD expanded the SLD to the "Repositories" line,
right-clicked, selected "Add repository";
8. Entered a repository name, went to the "source path" line and browsed to
the folder containing the driver files;
9. Saved the SLD & closed CD;
10. Opened CDM and imported the SLD (CDM reported success);
11. Opened TD and added one of the components;
12. TD reports that it cannot find the component files in a list of
repositories, none of which has a GUID that CDM assigned to my new
repository.

Obviously I'm doing something wrong, but what? I thought followed the
procedure in
http://msdn.microsoft.com/library/d.../cdtskimportingdatafrominffileintosldfile.asp,
but clearly not.

Please help!

 

[DPM]

Tools: Standard, SP1
Platform: XPpro SP2

I'm still struggling with getting a custom hardware component to work.
Here's what I did:

1. Installed XPpro and the XPe toolset on my target;
2. Installed the driver (video adapter);
3. Copied the relevant files to a separate folder;
4. Opened CD and imported the INF file;
5. Copied the SLD and driver files to a folder on my development machine;
6. Opened CD, loaded the SLD;
7. On the left pane in CD expanded the SLD to the "Repositories" line,
right-clicked, selected "Add repository";
8. Entered a repository name, went to the "source path" line and browsed to
the folder containing the driver files;
9. Saved the SLD & closed CD;
10. Opened CDM and imported the SLD (CDM reported success);
11. Opened TD and added one of the components;
12. TD reports that it cannot find the component files in a list of
repositories, none of which has a GUID that CDM assigned to my new
repository.

Obviously I'm doing something wrong, but what? I thought followed the
procedure in
http://msdn.microsoft.com/library/d.../cdtskimportingdatafrominffileintosldfile.asp,
but clearly not.

Please help!

Let me add that if I use Explorer to look at the repository CDM identifies
as the one associated with my component, the files are there. But
apparently when TD looks at the component it does not find the link to that
repository.

So I guess the question is: how do I specify that link in CD? And why did
steps 7 and 8 above not do that?

Regards,
Dean

 

[DPM]

Well, I think I finally figured this out. When I imported the driver, the
INF detailed 38 supported adapters. But even though I correctly created a
repository, I had to associate all 38 adapter components individually with
that repository.

This, ladies & gentlemen, is a pain in the ass. I can't believe there isn't
a function that associates the repository with ALL components at once.
Surely this is fixed in the FP2007 toolset?

Regards,
Dean

 

[KM]

DPM,

Seems like you missed associating your component to the created repository.
Open up your SLD with CD. Go to your component node and set the right value to the Repository field on the right panel. Save and
reimport the SLD, upgrade the component in your Config and rebuild the image.

 

[KM]

DPM,

Nothing changed for the CD functionality in FP2007.
It has always been a responsibility of the developer to associate components with the right repositories. The logic there< I
believe, is that only you know what repository contains the files of your component(s).
Although I agree it would be nice to have a checkbox in the CD Import UI to have the repository created automatically and hence
automatically associated with all the components on the same import.
I think the best now is to provide this feedback to Microsoft. If you do that, they may include [or consider] this feature in next
releases.

 

[crus]

DPM
I agree with you that setting repository 38 times is boring, but it tooks no
more than 20 minutes one time only when the .SLD is done.
You may even to consider extracting only the driver for device that you have
on your hardware selected accoding PnP value and delete the others ones..
According me MS should improve a LOT documentation about components
relationships:
I have been two days looking the setting to avoid a warning message and not
yet found, this is a time waste!
Good work
Raffaele

DPM,

Nothing changed for the CD functionality in FP2007.
It has always been a responsibility of the developer to associate
components with the right repositories. The logic there< I believe, is
that only you know what repository contains the files of your
component(s).
Although I agree it would be nice to have a checkbox in the CD Import UI
to have the repository created automatically and hence automatically
associated with all the components on the same import.
I think the best now is to provide this feedback to Microsoft. If you do
that, they may include [or consider] this feature in next releases.

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

Well, I think I finally figured this out. When I imported the driver,
the
INF detailed 38 supported adapters. But even though I correctly created
a
repository, I had to associate all 38 adapter components individually
with
that repository.

This, ladies & gentlemen, is a pain in the ass. I can't believe there
isn't
a function that associates the repository with ALL components at once.
Surely this is fixed in the FP2007 toolset?

Regards,
Dean