F5F Stay Refreshed Hardware Desktop Did you damage your CH341 Programmer?

Did you damage your CH341 Programmer?

Did you damage your CH341 Programmer?

A
alexagas
Member
210
06-26-2016, 03:37 AM
#1
So, I had some trouble with two gigabyte motherboards I bought a while ago, both with inserting faulty parts that ended up bricking the motherboard. I bought a CH341 Programmer from amazon along with the clip and cable. I'm fairly certain everything hardware wise is fine. I'm having some issues with the drivers though, and from multiple download sources on the internet, and for all of them, the installer spits out a "driver install failure" error. I have connected the Programmer to multiple USB ports, and tried reading the BIOS chip anyway with the ASprogrammer tool I have downloaded from a Youtube video. Now windows will not play the device inserted sound on any of my computers, and I'm just wondering if its bricked, or if I have a common issue that someone else here has. Please offer help if you can and I will do my best to respond. Before and after of me plugging in the Prgrammer: Setup: Edited November 9, 2022 by Earthlyhuman Desc
A
alexagas
06-26-2016, 03:37 AM #1

So, I had some trouble with two gigabyte motherboards I bought a while ago, both with inserting faulty parts that ended up bricking the motherboard. I bought a CH341 Programmer from amazon along with the clip and cable. I'm fairly certain everything hardware wise is fine. I'm having some issues with the drivers though, and from multiple download sources on the internet, and for all of them, the installer spits out a "driver install failure" error. I have connected the Programmer to multiple USB ports, and tried reading the BIOS chip anyway with the ASprogrammer tool I have downloaded from a Youtube video. Now windows will not play the device inserted sound on any of my computers, and I'm just wondering if its bricked, or if I have a common issue that someone else here has. Please offer help if you can and I will do my best to respond. Before and after of me plugging in the Prgrammer: Setup: Edited November 9, 2022 by Earthlyhuman Desc

S
108
07-03-2016, 10:08 PM
#2
The bios test clip was placed in the wrong programmer slot—specifically the 24xx area, which isn't meant for SPI chips or BIOS chips. It should be connected to the front of a programmer designed for 25xx chips, also known as SPI BIOS chips. Using the correct SPI header is much simpler; just use a male-to-female jumper labeled SPI TPM, and follow the headers next to the desoldered COM pins. I wasn’t aware Gigabyte offered SPI headers on their earlier models either, though I don’t know the pin configuration well. It might be worth reaching out to Gigabyte for the pinout details if you need it for BIOS flashing. Also, I’m wondering if it’s possible to install a B560 BIOS on it for RAM OC—given my experience flashing a P7H55MLX to a P7P55D, that should be manageable, especially since both chipsets have similar capabilities. The differences in featuresets are notable, and I managed to get the splash screen of the P7P55D-E premium BIOS, but only up to that point.
S
Suicide_Senpai
07-03-2016, 10:08 PM #2

The bios test clip was placed in the wrong programmer slot—specifically the 24xx area, which isn't meant for SPI chips or BIOS chips. It should be connected to the front of a programmer designed for 25xx chips, also known as SPI BIOS chips. Using the correct SPI header is much simpler; just use a male-to-female jumper labeled SPI TPM, and follow the headers next to the desoldered COM pins. I wasn’t aware Gigabyte offered SPI headers on their earlier models either, though I don’t know the pin configuration well. It might be worth reaching out to Gigabyte for the pinout details if you need it for BIOS flashing. Also, I’m wondering if it’s possible to install a B560 BIOS on it for RAM OC—given my experience flashing a P7H55MLX to a P7P55D, that should be manageable, especially since both chipsets have similar capabilities. The differences in featuresets are notable, and I managed to get the splash screen of the P7P55D-E premium BIOS, but only up to that point.

I
iiMaya
Junior Member
10
07-04-2016, 05:56 AM
#3
They didn’t mention your response anywhere. I’ll check the 25xx version, but what’s the best way to resolve the driver problems?
I
iiMaya
07-04-2016, 05:56 AM #3

They didn’t mention your response anywhere. I’ll check the 25xx version, but what’s the best way to resolve the driver problems?

S
swade33458
Junior Member
11
07-04-2016, 10:33 AM
#4
I haven’t run into any problems with drivers, but if it’s truly stuck, swapping it should cost around $3 at most. No major concerns there.
S
swade33458
07-04-2016, 10:33 AM #4

I haven’t run into any problems with drivers, but if it’s truly stuck, swapping it should cost around $3 at most. No major concerns there.

J
J_DerpCake
Junior Member
29
07-04-2016, 12:24 PM
#5
did you have to install drivers for yours? Can you give a link?
J
J_DerpCake
07-04-2016, 12:24 PM #5

did you have to install drivers for yours? Can you give a link?

J
JBeast2014
Member
169
07-12-2016, 01:28 AM
#6
I obtained drivers from the source. It looks like the issue is that Windows isn't recognizing the ch341, otherwise it would play the sound the device is supposed to produce and install the driver provided by the installer. Perhaps the unit is faulty or I damaged it. I think I should purchase a new one.
J
JBeast2014
07-12-2016, 01:28 AM #6

I obtained drivers from the source. It looks like the issue is that Windows isn't recognizing the ch341, otherwise it would play the sound the device is supposed to produce and install the driver provided by the installer. Perhaps the unit is faulty or I damaged it. I think I should purchase a new one.