How to use USB to brush firmware for mining machine control boar
Publish: 2021-03-26 20:02:52
1. Sony's np-fh50, 60, 70, and 100 card slots are the same
it is compatible, but it depends on whether the dcr-sr300 can be installed
some Sony cameras have built-in batteries, while others are external. If they are external, they should be usable
if you don't want to buy the original one, I agree that the Pinsheng brand suggested by the netizens upstairs should be a better brand than the original one.
it is compatible, but it depends on whether the dcr-sr300 can be installed
some Sony cameras have built-in batteries, while others are external. If they are external, they should be usable
if you don't want to buy the original one, I agree that the Pinsheng brand suggested by the netizens upstairs should be a better brand than the original one.
2. Refresh the firmware may solve the problem, but it may also be the U disk hardware problem ha
kingston u disk is generally a cluster chip, download a software (mpall) to try, as for how to use the software, you can search, the tutorial is more, mpall software version is many, a can't change a version to try, hope your U disk can be solved by brushing firmware.
kingston u disk is generally a cluster chip, download a software (mpall) to try, as for how to use the software, you can search, the tutorial is more, mpall software version is many, a can't change a version to try, hope your U disk can be solved by brushing firmware.
3. If your USBASP has a shell, you need to open it first. If you don't have a shell, go straight up! We need to find the jumper (after short circuit, upgrade the firmware for USBASP). I have two usbasps in my hand. As the Post said, one has a color shell and the other has no shell
on the back, we need to short the through holes indicated by the two red arrows in the figure. I use pointed tweezers. Of course, it's OK to use wires, but we need to ensure reliable short circuit
if there is no color case, we can see that there are two pads, as shown in the red circle in the figure below. We need to short those two pads. I still use pointed tweezers. How about you
next, we need two usbasps, one as the programmer and the other as the target (update the program on the chip and upgrade the firmware). Connect the two usbasps, that is, their ISP interfaces: pin 1 of one is connected to pin 1 of the other, pin 2 of one is connected to pin 2 of the other, and so on. Of course, when you buy a programmer, it should be accompanied by a 10p cable, which can be directly connected. If not, you can only use ten DuPont cables. After the connection is completed, short-circuit the place just shown (I use tweezers), and then plug it into the USB port of the computer
we still use the original progisp software. Open the software interface and select ATmega8 in the device column (in most cases, the chip used by the programmer is ATmega8, unless you have a personality explosion). Next, keep a reliable short circuit until the firmware is updated. We can read the serial number of the device. If the prompt reads the ID successfully, as shown in the figure below, then your wiring is correct and we can continue
before updating the firmware, I suggest you back up the current firmware just in case. That is to read out the contents of the chip and then save them. The method is: click "command" in the menu bar of progisps software to select "read flash" in the drop-down menu, as shown in the figure below. After a while, you can finish reading. Then click "file" in the menu bar. After the drop-down menu appears, click "save flash". By default, it is saved in the form of bin file. After the firmware is backed up in this way, even if the upgrade fails, we still have "regret medicine"
in this operation, there is no need to modify the fuse bit, because the original firmware has modified the fuse bit before leaving the factory. Of course, just in case, I read out the fuse position and make a backup. The fuse position is as follows:
OK, the preliminary work has been completed, and the real critical moment has come. We call the firmware in the attachment, the path is: usasp. 2011-05-28 & # 92; usbasp.2011-05-28\ bin\ firmware\ USB asp.atmega8.2011-05-28.hex, and then as before, set the programming parameters: check flash, chip erase and programming flash, other do not check. As shown in the figure below:
then click the "auto" button. After a while, the firmware of USBASP will be updated! Well, it's not hard. At this time, you need to pull the programmer out of the USB port, and then you need to remove the short circuit. From then on, the USBASP firmware update is completed
of course, you can update the firmware of another USBASP after updating the firmware! In other words, progisp software can still be used normally, you can still use this software to write programs for other chips
if you only have one USBASP, don't worry, you can use arino uno as ISP programmer to update the firmware for USBASP
after the firmware is updated, insert the USBASP with the updated firmware into the USB port of the computer, and then update the corresponding driver on the computer to the latest version (attachment usbsasp WinDriver. 2011-05-28), the latest version is 1.2.4.0
then, it's time to be once and for all
let's take arino uno as an example to describe the method of burning bootloader
open the arino IDE and select the board type as arino UNO
next, select USBASP as the programmer
finally, click "burn bootloader". After a while, you will be prompted to finish burning! As shown in the figure below. How about it? It's super simple. You guys don't have to worry about setting the wrong fuse position any more
reprint
on the back, we need to short the through holes indicated by the two red arrows in the figure. I use pointed tweezers. Of course, it's OK to use wires, but we need to ensure reliable short circuit
if there is no color case, we can see that there are two pads, as shown in the red circle in the figure below. We need to short those two pads. I still use pointed tweezers. How about you
next, we need two usbasps, one as the programmer and the other as the target (update the program on the chip and upgrade the firmware). Connect the two usbasps, that is, their ISP interfaces: pin 1 of one is connected to pin 1 of the other, pin 2 of one is connected to pin 2 of the other, and so on. Of course, when you buy a programmer, it should be accompanied by a 10p cable, which can be directly connected. If not, you can only use ten DuPont cables. After the connection is completed, short-circuit the place just shown (I use tweezers), and then plug it into the USB port of the computer
we still use the original progisp software. Open the software interface and select ATmega8 in the device column (in most cases, the chip used by the programmer is ATmega8, unless you have a personality explosion). Next, keep a reliable short circuit until the firmware is updated. We can read the serial number of the device. If the prompt reads the ID successfully, as shown in the figure below, then your wiring is correct and we can continue
before updating the firmware, I suggest you back up the current firmware just in case. That is to read out the contents of the chip and then save them. The method is: click "command" in the menu bar of progisps software to select "read flash" in the drop-down menu, as shown in the figure below. After a while, you can finish reading. Then click "file" in the menu bar. After the drop-down menu appears, click "save flash". By default, it is saved in the form of bin file. After the firmware is backed up in this way, even if the upgrade fails, we still have "regret medicine"
in this operation, there is no need to modify the fuse bit, because the original firmware has modified the fuse bit before leaving the factory. Of course, just in case, I read out the fuse position and make a backup. The fuse position is as follows:
OK, the preliminary work has been completed, and the real critical moment has come. We call the firmware in the attachment, the path is: usasp. 2011-05-28 & # 92; usbasp.2011-05-28\ bin\ firmware\ USB asp.atmega8.2011-05-28.hex, and then as before, set the programming parameters: check flash, chip erase and programming flash, other do not check. As shown in the figure below:
then click the "auto" button. After a while, the firmware of USBASP will be updated! Well, it's not hard. At this time, you need to pull the programmer out of the USB port, and then you need to remove the short circuit. From then on, the USBASP firmware update is completed
of course, you can update the firmware of another USBASP after updating the firmware! In other words, progisp software can still be used normally, you can still use this software to write programs for other chips
if you only have one USBASP, don't worry, you can use arino uno as ISP programmer to update the firmware for USBASP
after the firmware is updated, insert the USBASP with the updated firmware into the USB port of the computer, and then update the corresponding driver on the computer to the latest version (attachment usbsasp WinDriver. 2011-05-28), the latest version is 1.2.4.0
then, it's time to be once and for all
let's take arino uno as an example to describe the method of burning bootloader
open the arino IDE and select the board type as arino UNO
next, select USBASP as the programmer
finally, click "burn bootloader". After a while, you will be prompted to finish burning! As shown in the figure below. How about it? It's super simple. You guys don't have to worry about setting the wrong fuse position any more
reprint
4. Hello, did you upgrade? I didn't upgrade. The machine doesn't work
5. Generally speaking, USB devices (only USB devices are analyzed here, not USB host, USB OTG and USB
hub) have a USB chip and a MCU inside. Of course, some USB chips provided by some manufacturers have integrated MCU inside, such as cy68013 of cypress. Here, consider the case of MCU and USB chip separated, the integrated is also similar, you can analyze it by yourself. When receiving, the USB serial data is identified and stored in the internal cache after unpacking, and then the MCU is informed by interrupt that the data packet has been received. The MCU reads back the received data through the parallel or serial interface with the USB chip and carries out the corresponding analysis and processing; When sending data, MCU writes the data to be sent to the internal cache of USB chip through the interface with USB chip. After writing, generally speaking, USB chip will send the data in the cache to USB bus when receiving in token packet from host. When the transmission is completed, usually the USB chip can also interrupt the way to inform the MCU< p> from this, we can see that USB chip only completes the unpacking and packaging of data, and does not carry out any analysis and processing of data. The analysis and processing of data packets are completed by MCU. Specifically, it is completed by the program running in MCU, which is commonly known as USB
firmware or USB firmware program< p> first, analyze a simple data transmission from host to device, that is, the out type transmission, assuming that the transmission type is bulk< p> USB transmission can only be initiated by host, and host needs to send an out token packet to device. In this package, the device address and endpoint to receive data are specified. Then the packet is sent to the USB bus. The USB device that is not the destination receiving device will not respond to the packet. If the destination receiving device can receive the packet, it will respond with an ACK handshake packet. If it cannot receive the packet, it will respond with a
NAK handshake packet< p> in the above process, the USB chip will interrupt the MCU after receiving the data packet, and then the MCU reads the data packet cached in the USB chip, and then decides to reply to ACK or NAK< p> the above is just a simple bulk out transmission. For bulk
in transmission, host first sends an in token packet, and the USB chip will interrupt MCU after receiving the token packet. If MCU sends data back to host, it will write the data to the corresponding breakpoint cache in the USB chip, and then the USB chip will automatically send the data to the USB bus. And wait to receive the handshake packet from host< p> for block, interrupt and synchronous transmission, the transmission process is similar. The whole transmission process consists of token packet, data packet and handshake packet< p> for control transmission, a transmission consists of three stages, namely setup stage, optional data stage and status stage< p> the setup phase is an out transmission, and host sends the 8-byte setup packet to the device. These 8 bytes specify the request type for this control transfer. Device will make corresponding action according to the 8 bytes< p> the second stage is the data stage. Some control transmissions do not have this stage, such as the set address request< p> in the data phase, host sends data to device through out transmission, or requests data from device through in transmission< p> the third stage is the state stage, which is to get the state of the control transmission and confirm whether the transmission is completed normally. Host or device uses an empty packet of length 0 to indicate a positive response< p> most of the programs in USB firmware are dealing with control transmission, specifically, there are 11 kinds of standard requests and class requests for specific devices, such as mass
storage class requests, and some customized requests from manufacturers< p> The design and debugging of USB
firmware should start with a basic transmission. To be able to complete a normal transmission, especially control transmission, otherwise even the enumeration of devices can not be completed, that is to say, the device can not be correctly identified by the computer< p>
20:59:00 after the USB device is powered on, the firmware program starts to run. The first thing to do is initialization, including the initialization of device logic and USB chip. Generally speaking, USB firmware is designed as the way of front-end and back-end. The front-end program is a big dead loop, and the back-end is an interrupt processing function. When the USB chip generates the interrupt signal, the microprocessor enters the interrupt processing program, reads the interrupt mark of the USB chip, judges the type of interrupt (such as transmission error, receiving setup package, receiving token package, transmission completion, etc.), and then sets the corresponding flag bit. The variable that stores the flag bit should be a global variable. In the foreground program, the firmware constantly detects the flag bit to determine whether there is an interrupt event. If there is, it will enter the corresponding time processing function. As mentioned earlier, most USB firmware programs are processing requests from host, that is, the setup packets sent by host. When the current program detects the setup event, it will first read back the 8-byte setup packet from the USB chip's cache, and then analyze the packet according to the structure defined in the USB specification, and then proceed to the corresponding request processing function. It can be summarized into the following structure======== Background = = = = = = = = = = = = = = = = = = = = = = = = = = = = interrupt handling function (ISR) cycle {read interrupt register of USB chip [device transaction] clear USB chip interrupt if USB interrupt flag is set, judge interrupt type {interrupt event handling set interrupt flag read setup package = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =========================== =========In the request function processing function, the firmware program either writes the corresponding descriptor to the breakpoint buffer of the USB chip, and then sends it to the host, or reads back the data from the host from the breakpoint buffer of the USB chip. Here is a typical getdescriptor request. Host sends setup token packet; Causes the USB chip to interrupt the MCU, the interrupt event is setup, the MCU is interrupted, and the interrupt flag host is set to send the setup packet; The USB chip receives the data packet, stores it in the breakpoint cache, and automatically responds to the host firmware with ack. MCU detects the interrupt event, and the type is setup event. It enters the setup event processing function, reads back the setup data packet, parses it, fills the device descriptor into the USB chip cache, and waits for the data transmission to complete. Host sends in token packet; If the MCU has completed the data filling, the USB chip will send the data back to host, otherwise it will respond with NAK. Loop the previous step until the data is sent. Host receives the descriptor and responds to the USB device with ack; At this time, the USB chip interrupts the MCU, and the MCU will know that the transmission is completed from this interrupt. MCU sets USB chip to automatically reply a packet with length of 0 when receiving the next in token packet. Host sends in token packet; The USB chip automatically replies to a packet with a length of 0. Host receives the packet and returns ack-----------------& gt; USB request completion [device transaction] above refers to the transaction of USB device itself, such as reading and processing of AD sampling data. The above is the basic framework of USB firmware program. A complete firmware program has to deal with many interrupt transactions, but the basic processing is similar. Each USB subclass device, such as mass storage device and hid device, has its own request class. Please handle it
hub) have a USB chip and a MCU inside. Of course, some USB chips provided by some manufacturers have integrated MCU inside, such as cy68013 of cypress. Here, consider the case of MCU and USB chip separated, the integrated is also similar, you can analyze it by yourself. When receiving, the USB serial data is identified and stored in the internal cache after unpacking, and then the MCU is informed by interrupt that the data packet has been received. The MCU reads back the received data through the parallel or serial interface with the USB chip and carries out the corresponding analysis and processing; When sending data, MCU writes the data to be sent to the internal cache of USB chip through the interface with USB chip. After writing, generally speaking, USB chip will send the data in the cache to USB bus when receiving in token packet from host. When the transmission is completed, usually the USB chip can also interrupt the way to inform the MCU< p> from this, we can see that USB chip only completes the unpacking and packaging of data, and does not carry out any analysis and processing of data. The analysis and processing of data packets are completed by MCU. Specifically, it is completed by the program running in MCU, which is commonly known as USB
firmware or USB firmware program< p> first, analyze a simple data transmission from host to device, that is, the out type transmission, assuming that the transmission type is bulk< p> USB transmission can only be initiated by host, and host needs to send an out token packet to device. In this package, the device address and endpoint to receive data are specified. Then the packet is sent to the USB bus. The USB device that is not the destination receiving device will not respond to the packet. If the destination receiving device can receive the packet, it will respond with an ACK handshake packet. If it cannot receive the packet, it will respond with a
NAK handshake packet< p> in the above process, the USB chip will interrupt the MCU after receiving the data packet, and then the MCU reads the data packet cached in the USB chip, and then decides to reply to ACK or NAK< p> the above is just a simple bulk out transmission. For bulk
in transmission, host first sends an in token packet, and the USB chip will interrupt MCU after receiving the token packet. If MCU sends data back to host, it will write the data to the corresponding breakpoint cache in the USB chip, and then the USB chip will automatically send the data to the USB bus. And wait to receive the handshake packet from host< p> for block, interrupt and synchronous transmission, the transmission process is similar. The whole transmission process consists of token packet, data packet and handshake packet< p> for control transmission, a transmission consists of three stages, namely setup stage, optional data stage and status stage< p> the setup phase is an out transmission, and host sends the 8-byte setup packet to the device. These 8 bytes specify the request type for this control transfer. Device will make corresponding action according to the 8 bytes< p> the second stage is the data stage. Some control transmissions do not have this stage, such as the set address request< p> in the data phase, host sends data to device through out transmission, or requests data from device through in transmission< p> the third stage is the state stage, which is to get the state of the control transmission and confirm whether the transmission is completed normally. Host or device uses an empty packet of length 0 to indicate a positive response< p> most of the programs in USB firmware are dealing with control transmission, specifically, there are 11 kinds of standard requests and class requests for specific devices, such as mass
storage class requests, and some customized requests from manufacturers< p> The design and debugging of USB
firmware should start with a basic transmission. To be able to complete a normal transmission, especially control transmission, otherwise even the enumeration of devices can not be completed, that is to say, the device can not be correctly identified by the computer< p>
< table border = "0" > < tbody > usbfirmware process (2) bytopone was published on July 21, 2008
20:59:00 after the USB device is powered on, the firmware program starts to run. The first thing to do is initialization, including the initialization of device logic and USB chip. Generally speaking, USB firmware is designed as the way of front-end and back-end. The front-end program is a big dead loop, and the back-end is an interrupt processing function. When the USB chip generates the interrupt signal, the microprocessor enters the interrupt processing program, reads the interrupt mark of the USB chip, judges the type of interrupt (such as transmission error, receiving setup package, receiving token package, transmission completion, etc.), and then sets the corresponding flag bit. The variable that stores the flag bit should be a global variable. In the foreground program, the firmware constantly detects the flag bit to determine whether there is an interrupt event. If there is, it will enter the corresponding time processing function. As mentioned earlier, most USB firmware programs are processing requests from host, that is, the setup packets sent by host. When the current program detects the setup event, it will first read back the 8-byte setup packet from the USB chip's cache, and then analyze the packet according to the structure defined in the USB specification, and then proceed to the corresponding request processing function. It can be summarized into the following structure======== Background = = = = = = = = = = = = = = = = = = = = = = = = = = = = interrupt handling function (ISR) cycle {read interrupt register of USB chip [device transaction] clear USB chip interrupt if USB interrupt flag is set, judge interrupt type {interrupt event handling set interrupt flag read setup package = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =========================== =========In the request function processing function, the firmware program either writes the corresponding descriptor to the breakpoint buffer of the USB chip, and then sends it to the host, or reads back the data from the host from the breakpoint buffer of the USB chip. Here is a typical getdescriptor request. Host sends setup token packet; Causes the USB chip to interrupt the MCU, the interrupt event is setup, the MCU is interrupted, and the interrupt flag host is set to send the setup packet; The USB chip receives the data packet, stores it in the breakpoint cache, and automatically responds to the host firmware with ack. MCU detects the interrupt event, and the type is setup event. It enters the setup event processing function, reads back the setup data packet, parses it, fills the device descriptor into the USB chip cache, and waits for the data transmission to complete. Host sends in token packet; If the MCU has completed the data filling, the USB chip will send the data back to host, otherwise it will respond with NAK. Loop the previous step until the data is sent. Host receives the descriptor and responds to the USB device with ack; At this time, the USB chip interrupts the MCU, and the MCU will know that the transmission is completed from this interrupt. MCU sets USB chip to automatically reply a packet with length of 0 when receiving the next in token packet. Host sends in token packet; The USB chip automatically replies to a packet with a length of 0. Host receives the packet and returns ack-----------------& gt; USB request completion [device transaction] above refers to the transaction of USB device itself, such as reading and processing of AD sampling data. The above is the basic framework of USB firmware program. A complete firmware program has to deal with many interrupt transactions, but the basic processing is similar. Each USB subclass device, such as mass storage device and hid device, has its own request class. Please handle it
6. Hello! Mobile phone brushing can solve the system failure of mobile phone and bring different system experience, but it is easy to affect the hardware of mobile phone and affect the service life of mobile phone; It's easy for our mobile phone to be paralyzed if we brush the machine blindly. If so, it's more complicated and intractable. It's suggested that non professional operators brush the machine and send it to after-sales department.
7. In fact, it's quite a lot. It depends on your needs. I think Tencent's security leading blockchain is really good, and the completion is also very good. Tencent has also continued to carry out the exploration of blockchain and other new technologies in the application of public search and charity fundraising, bringing benefits to everyone.
8. Blockchain and bitcoin are not the same thing. Blockchain is a distributed accounting technology, and bitcoin is a point-to-point form of digital currency, but bitcoin uses blockchain as its underlying technology.
Hot content