Unsolved
This post is more than 5 years old
6 Posts
0
15010
September 11th, 2012 16:00
6430/6530 ST Microacellerometer driver conflict on a 6420
I've got a universal image that contains the driver packs for the 6420, 6430, and 6530. When I image a 6420 with this image, MiniSetup hangs after installing the ST MicroAccelerometer (ST MA) driver. It says it installed successfully in setupapi.log, but setup just doesn't proceed from there.
The setupapi log from the 6420 shows that MiniSetup selects the 6430 version of the ST MA driver. I removed that from the image, but then it selects the 6530 driver and has the same problem. I removed the 6530 driver from the image, and MiniSetup completes successfully (it selects the 6420 version of the ST MA driver).
Is there any way to get these drivers to coexist on the same image?
No Events found!
SSEJones
6 Posts
0
September 12th, 2012 09:00
And, not unexpectedly, the 6530 won't use the 6420 version of the driver.
SSEJones
6 Posts
0
September 13th, 2012 14:00
I've figured out the why, just not how to fix it yet. The inf for the 6430/6530 driver lists the 6420's ST MA deviceid (SMO8800 below). So with a newer date stamp than the 6420's driver, it's picking the 6x30.
Out of curiosity, I removed that line from the 6x30's inf and that allows it to work on the 6420, but breaks the signing of the driver for the 6x30's, so it doesn't install during the MiniSetup.
I'm almost to the point of just making a separate image for the 6x30's, but would prefer not to.
[ST.NTx86]
; DisplayName Section DeviceId
; ----------- ------- --------
%ST_ACCEL.DeviceDesc%= ST_ACCEL, *SMO8800
%ST_ACCEL.DeviceDesc%= ST_ACCEL, *SMO8801
%ST_ACCEL.DeviceDesc%= ST_ACCEL, *SMO8810
%ST_ACCEL.DeviceDesc%= ST_ACCEL, *SMO8811
%ST_ACCEL.DeviceDesc%= ST_ACCEL, *SMO8820
%ST_ACCEL.DeviceDesc%= ST_ACCEL, *SMO8821
%ST_ACCEL.DeviceDesc%= ST_ACCEL, *SMO8830
%ST_ACCEL.DeviceDesc%= ST_ACCEL, *SMO8831