CH341A Programmer | [Programmer] Bios Firmware CH341A Programmer
Instruction_v2_CH341A.zip
1. With Aliexpress ordered already. Sorry for a long time, my hands are itching)
2. There is one thought. The chip is not erased in an empty place of the BIOS. Bios is written to its addresses. After the recording, the firmware is as it were, but in an empty place of it, which tail is not erasable in the chip. In theory, the bios will be intact, only with a piece of something unknown to it. What do you think it makes sense to try?
3. In general, Frankeinstein was launched))) as expected by the post above. Recorded bios on the buggy chip. And it started.
Chip soldered at the time of the experiments. Since the Soldering Iron is not convenient to solder such a trifle.
A couple of pictures. Launched without a hard disk. I'll put the system in, I can get a cant somewhere)
Thank you all for your help.
Post has been editedboar-hooligan - 29.09.18, 16:52
2. There is one thought. The chip is not erased in an empty place of the BIOS. Bios is written to its addresses. After the recording, the firmware is as it were, but in an empty place of it, which tail is not erasable in the chip. In theory, the bios will be intact, only with a piece of something unknown to it. What do you think it makes sense to try?
3. In general, Frankeinstein was launched))) as expected by the post above. Recorded bios on the buggy chip. And it started.
Chip soldered at the time of the experiments. Since the Soldering Iron is not convenient to solder such a trifle.
A couple of pictures. Launched without a hard disk. I'll put the system in, I can get a cant somewhere)
a photo
 |
 |
 |
Thank you all for your help.
Post has been editedboar-hooligan - 29.09.18, 16:52
Reason for editing: We hide the pictures under the spoiler + glued posts
crysis-gra, Well what happened, I did not advise anything because there are too many "ifs". In any case, change the flash drive as soon as it comes. Last picture amused: D
relixiv Oh necroposting! Myusie knows a lot about perversion: D
Good day. A couple of pages back I asked for advice (I did not flash the microcircuit). I report: I ordered a new one, everything was done right from the first time. Modification with resistors did not. The microcircuit was on 3b, and not on 1.8 (this followed from the datasheet). About the write protection / service bits, I really did not understand, for a total of kmk, the problem was either in them or the microcircuit was damaged in the process of soldering.
I use the programmer to communicate with the HDD via RX / TX.
1. I connect the programmer to the HDD.
2. I connect the programmer to the computer.
3. I launch the terminal (HyperTerminal 7.0).
4. I open connection in the terminal.
5. I connect HDD power (I plug in HDD SATA Power).
Then one of two things (a - in 75% of cases, b - in 25%):
6a. From the speakers of the computer you can hear the sound of connecting a new device.
6b. Nothing.
7a. The terminal does not display anything, but when you try to enter something, it hangs.
7b. The terminal displays information from the HDD and then works without problems.
It seems to me that along the RX / TX lines some voltage jumps from the HDD and the CH341A reboots and the terminal loses connection with it.
How to get rid of it?
Post has been editedAleksRazgul - 03.10.18, 21:44
1. I connect the programmer to the HDD.
2. I connect the programmer to the computer.
3. I launch the terminal (HyperTerminal 7.0).
4. I open connection in the terminal.
5. I connect HDD power (I plug in HDD SATA Power).
Then one of two things (a - in 75% of cases, b - in 25%):
6a. From the speakers of the computer you can hear the sound of connecting a new device.
6b. Nothing.
7a. The terminal does not display anything, but when you try to enter something, it hangs.
7b. The terminal displays information from the HDD and then works without problems.
It seems to me that along the RX / TX lines some voltage jumps from the HDD and the CH341A reboots and the terminal loses connection with it.
How to get rid of it?
Post has been editedAleksRazgul - 03.10.18, 21:44
Demonis, I finally decided to do everything correctly: happy:
I found the time, rummaged in the dumps and clean firmware and it turned out the following:
My time with the inclusion of a long nouta Dell N5110 began to strain, especially if it is due to the ME region. I finally gathered his thoughts, prosherstit shot curve dump and found an area with DMI. If someone will be useful, it is an area 1A0000h - 1AFFFFh (starts at $ TAG). His, respectively, put into a clean firmware and run nouta became perfect :) And not only the laptop immediately began to run, but is not included in Manufacturing Mode. Apparently, the presence of serial numbers is enough and no additional parameters to change the firmware is not necessary. In addition, the device in the system to handle downed disappeared (or was the function normally).
Question with FPT also decided - I at first did not even know that for a particular chipset needs its own version of the FPT. As a result, I was able to remove the dumps with all the necessary computers through DOS. Well, of course, ME region not only zabekapit because denied to the default reading. Once I have a Dell N5110 noutom figured out, I finished it experiments and found that FPT removes it through the DOS all the dumps right (for test unlocked firmware ME region through programming). Similarly, sews all the bios without problems. Through Windows is not tried and will not try: happy:
By the way here caught chip W25Q64FV in DIP8 housing, from which the dump rented programmer. He stands on the motherboard chipset AMD. Software like Intel FPT found for him so useful to take a dump programmer (good desoldering do not need anything). I found therein set bit QE. I remembered that our programming needs refinement to work with this bit (set / reset). But if I do not want anything to do with it, but simply to read or write to the chip, I need to refine the programming?
However, the read attempts were successful, the two dumps taken in a row coincided.
Still slightly offtopic (sorry):
Along with the experience of finding and changing DMI and regional rights, I decided to try changing the logos when loading the BIOS (well, I wonder the same). The PhoenixTool utility helped in this case. On YouTube was just an example of changing the logo on the laptop Dell N5110. It turned out great, but in the end left the regular Dell logo.
But the change of the logo in the BIOS on the Intel DN2800MT board - at first seemed hell! Intel either encrypt, or compress specific manner the bulk of the dump so that no program can not remove from it all the Old but DMI (like settings and couples). This logo dump not modified. If you take the firmware from the site, it is decompressed normally, but the reverse, wrapping PhoenixTool-om does not one of the common firmware for firmware via IFlash2 (intelovkaya). Somewhere in the internet found out that in the firmware bunch of checks / signatures / checksum. And because they do not modify the firmware again. I found the official tool from Intel, which allows you to change the settings in the firmware. Parameters change is possible, but there is no logo. But in those. the manual is written as you can! It turned out that it is necessary to rename the file (in my case) MT0171C.itk in MT0171P .itk. Only then a clause appeared, allowing to change the logo.
Post has been editedMczion - 05.10.18, 15:12
Green programmer mode (possibly suitable for blue)
 |
 |
I have another layout on a black programmer. Blowed out a socket. And of course, the legs were connected right there, on the upper side of the board, under the socket. And exactly there it is necessary to cut the tracks, and only then from the bottom side to solder the cuttings between the adjacent legs and from the first to the seventh. This can only be done with a normal camera in macro mode, unfortunately this is not at hand.
Post has been editedDef1985 - 11.10.18, 15:11
Exelero @ 08.22.18, 14:18
Now it remains to find out what kind of data there needs to be replaced, so that it becomes 1500 sheets)
Counted through 4 contacts (4,5,6,8)
Counted through 4 contacts (4,5,6,8)
Did I understand you correctly?
On the block of the C341A programmer under the 24XX microcircuit, I took the contacts:
4-GND
5-DATA
6-clk
8-VCC
Attached to the chip counting from the hole in order GND-VCC-CLK-DATA.
Inserted, programmer in USB connector launched the program for C341A, counted, cleared, recorded.
A photo
 |
 |
Post has been editedboar-hooligan - 09.10.18, 21:32
Reason for editing: We hide the pictures under the spoiler
MK_mk, [email protected], 14:55
From 3.3 volts mikruh:
"Absolute Maximum Stress Ratings (Applied conditions greater than those listed under the“ Absolute Maximum Ratings ”) Exposure to absolute stress rating.
Voltage on Any Pin to Ground Potential .............................- 0.5V to VDD + 0.5V "
Sew, who will forbid you. Keep arguing with development engineers, they like it :)
I urge the rest to think after the above quotation: is it worth extrapolating this practical experience of the firmware to your case, and can there be errors when reading if at 4.1 volts on any leg mikruhi with 3.3 volts can burn it.
"Absolute Maximum Stress Ratings (Applied conditions greater than those listed under the“ Absolute Maximum Ratings ”) Exposure to absolute stress rating.
Voltage on Any Pin to Ground Potential .............................- 0.5V to VDD + 0.5V "
Sew, who will forbid you. Keep arguing with development engineers, they like it :)
I urge the rest to think after the above quotation: is it worth extrapolating this practical experience of the firmware to your case, and can there be errors when reading if at 4.1 volts on any leg mikruhi with 3.3 volts can burn it.
Look in the same datasheet now - how many VDDs are there, in the same section “Absolute MaximumStress Ratings”. Usually all mikruhi 3.3 V easily undergo a connection to 5 volts, besides a short-term (I have never had any precedents of failure).
Post has been editedsteesel - 09.10.18, 21:13
Hello gentlemen bios, in the hope of at least reading it, but the story is the same .. voltage measured at Vcc 3.26 in. Maybe someone had this? Or the programmer-corpse was originally? The power light is on, the computer displays as USB-EPP / I2C ... CH341.win 7 x64
thank you in advance
Post has been editedvitalik_24 - 09.10.18, 21:54
thank you in advance
Post has been editedvitalik_24 - 09.10.18, 21:54
vitalik_24, Do you connect the mikruha according to the pinout on the programmer itself or how is it drawn in the software?
Frog @ 10/10/2018 07:45
vitalik_24, Do you connect the mikruha according to the pinout on the programmer itself or how is it drawn in the software?
as drawn on the programmer. in the reverse case, I tried something (the unfortunate experimenter) heated up both micra and a stub on the programmer. . But the machine does not determine mikru.
As I understand it, the jumper influences the firmware of the microcircuits either in the connector (with the jumper) or on board the programmer itself (without the jumper), that is, directly onto the solder tracks. without adapters. .
I apologize for the long text, please do not punish.
vitalik_24, Jumper changes modes: parallel programmer - UART TTL (USB-RS232 converter), you needonly first mode (jumper 1-2). The microcircuit is set to the position for the x25 series of microcircuits (i.e., closer to the USB connector), the key of the microcircuit to the ZIF lever of the socket.
You install firewood for the USB-EPP / I2C ... CH341 device and the AsProgrammer_1.4.0 program and try it.
In the finalization of the programmer has a picture and description
And in the picture which leg is under what number?
Also according to the description it is written what to let THEM (both) through the resistor
but from the photo you can see that only one leg is connected through the resistor
clear up please
To fix this flaw, you need to detach the legs #WP (pin 3) and #HOLD (pin7) from VCC
and connect them to VCC via resistors 4.7 com.
On the "black programmer" it looks like this:
and connect them to VCC via resistors 4.7 com.
On the "black programmer" it looks like this:
And in the picture which leg is under what number?
Also according to the description it is written what to let THEM (both) through the resistor
but from the photo you can see that only one leg is connected through the resistor
clear up please
©savagemessiahzine.com2005-2020 All rights reserved.
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement