Programming chip 25LB64CSIG

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ut-norm
    Senior Member
    • Nov 2019
    • 67
    • italia

    #1

    Programming chip 25LB64CSIG

    Greetings to all. I need to flash the bios of an ASUS x509M. I have two CH341A and EZP 2019+ programmers that do not recognize the chip which is: Gigadevice 25LB64CSIG (I have the adapter for 1.8 v.). How could I do? Can I use another programmer or perhaps an equivalent chip?
  • mon2
    Badcaps Legend
    • Dec 2019
    • 14240
    • Canada

    #2
    It is 1v8 version. See if this helps:

    https://www.badcaps.net/forum/troubl...9-help-request

    Comment

    • ut-norm
      Senior Member
      • Nov 2019
      • 67
      • italia

      #3

      Thanks mon2 I found the solution by reading the post.I programmed the chip with the CH 341A but without the 1.8v adapter.It didn't work with EZP 2019.The CH 341A recognized the chip as GD25Q64 powered at 2.98 v. voltage measured on pins 4 and 8. The PC with the new bios began to charge the battery and started up. Thanks again​

      Comment

      • Amigaaga
        New Member
        • Mar 2024
        • 3
        • France

        #4
        Hi,
        I would like to thank you.
        This was usefull for me.

        Comment

        • hairulole
          New Member
          • Jan 2024
          • 6
          • Malaysia

          #5
          ut-norm If using CH341a and converter 1.8v, does it detect the chip? I afraid without using converter it would be burn the chip. May i know which ch341a programmer version you be using to reprogram the chip?

          Comment

          • S4X0
            New Member
            • Aug 2022
            • 1
            • Indonesia

            #6
            Originally posted by hairulole
            ut-norm If using CH341a and converter 1.8v, does it detect the chip? I afraid without using converter it would be burn the chip. May i know which ch341a programmer version you be using to reprogram the chip?
            It's easier to flash the IC chip without having to remove it from the mainboard and I've tested it using the ch341a black edition

            Comment

            • gusto
              Member
              • Oct 2024
              • 34
              • Czech Republic

              #7
              I am using linux flashrom and I have this problem.

              Code:
              sudo flashrom --programmer ch341a_spi --read read01.bin
              Code:
              flashrom unknown on Linux 6.8.0-51-generic (x86_64)
              flashrom is free software, get the source code at https://flashrom.org
              
              Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
              Found GigaDevice flash chip "GD25LQ64(B)" (8192 kB, SPI) on ch341a_spi.
              Reading flash...
              cb_out: error: LIBUSB_TRANSFER_ERROR
              
              cb_in: error: LIBUSB_TRANSFER_ERROR
              
              cb_in: error: LIBUSB_TRANSFER_ERROR
              ch341a_spi_spi_send_command: Failed to write 4265 bytes
              
              cb_in: error: LIBUSB_TRANSFER_ERROR
              
              cb_in: error: LIBUSB_TRANSFER_ERROR
              
              cb_in: error: LIBUSB_TRANSFER_ERROR
              
              cb_in: error: LIBUSB_TRANSFER_ERROR
              Read operation failed!
              FAILED.
              
              cb_out: error: LIBUSB_TRANSFER_ERROR
              enable_pins: Failed to write 4 bytes

              Comment

              • mon2
                Badcaps Legend
                • Dec 2019
                • 14240
                • Canada

                #8
                To me, sounds like a Linux related local issue since the LIBUSB transfers are not being processed. Test with another distribution.

                Comment

                • gusto
                  Member
                  • Oct 2024
                  • 34
                  • Czech Republic

                  #9
                  I have updated Linux Mint 22 and I tried different USB ports.
                  Tomorrow I will try a completely different PC.
                  The log shows that the programmer identified the chip, but could not read the data.​

                  Comment

                  Related Topics

                  Collapse

                  Working...