Announcement

Collapse
No announcement yet.

Help me please erro [0x30405004] USB burning tool

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #91
    Like I said, check each power supply segment. A blown fuse resistor, or transistor switch for controlling sleep and wake will do it. Not familiar with your board, but transistor is located next to the power connector on the reverse side near the corner.

    you could have a blown 3.3v stage as well... not necessarily the power output, but a resistor or transistor to control it. Each stage should have one to either enable when power is applied, or control ed by CPU for sleep.

    try connecting USB power as well as power adapter. Should help if hardware is an issue with passing 5v to the step down stages for voltages.

    thus making uart active, without adding 3.3v from the adapter.

    Comment


    • #92
      I have another suspicion, we have to check that. I will provide you with another uboot version. Please be patient

      Comment


      • #93
        Ok, thanks.
        When I said that adapter works on my other box, I meant power adapter. I power my working box with power adapter from non-working, if box works normally then I assumed power adapter is ok.
        X92-2GB Thanks, will try first all software possibilities, if nothing helps then will move to hardware.

        Comment


        • #94
          Originally posted by Nebojsa View Post
          Ok, thanks.
          When I said that adapter works on my other box, I meant power adapter. I power my working box with power adapter from non-working, if box works normally then I assumed power adapter is ok.
          X92-2GB Thanks, will try first all software possibilities, if nothing helps then will move to hardware.
          Understood... just saying the uart communication seems to be relying on your adapter, so that brings up the red flag for the possibility of a hardware related issue. Tx and Rx should handshake without 3.3v applied as they are driven by shared pull up resistor function within their internal Vcc.

          If one does not have 3.3v active in their circuit, no communication is going on, let alone the box is not giving power to the uart and/or other devices that need it.

          Comment


          • #95
            u-boot.bin.sd.zip

            Installation via BootcardMaker.

            Comment


            • #96
              Link is not ok, nothing found...

              Comment


              • #97
                https://yadi.sk/d/BAhOafaF3XqpCr

                Comment


                • #98
                  Tried with this u-boot and BootcardMaker, no luck

                  GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:3;RCY:0 ;EMMC:0;READ:800;SD:0;READ:0;0.0;CHK:0;
                  no sdio debug board detected
                  TE: 148682

                  BL2 Built : 20:32:17, Sep 8 2017.
                  gxl g6296b83 - xiaobo.gu@droid12

                  set vdd cpu_a to 1120 mv
                  set vdd cpu_b to 1050 mv
                  set vddee to 1000 mv
                  Board ID = 6
                  CPU clk: 1200MHz
                  DQS-corr enabled
                  DDR scramble enabled
                  DDR4 chl: Rank0+1 @ 816MHz
                  Rank0: 2048MB(auto)-2T-18
                  Rank1: 1024MB(auto)-2T-18
                  DataBus test pass!
                  AddrBus test pass!
                  Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
                  New fip structure!
                  Load bl30 from SD, src: 0x00010200, des: 0x01100000, size: 0x0000d600
                  Load bl31 from SD, src: 0x00020200, des: 0x05100000, size: 0x0002c600
                  Load bl33 from SD, src: 0x00050200, des: 0x01000000, size: 0x00053e00

                  ▒▒GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:3;RCY :0;EMMC:0;READ:800;SD:0;READ:0;0.0;CHK:0;
                  no sdio debug board detected
                  TE: 148657

                  BL2 Built : 20:32:17, Sep 8 2017.
                  gxl g6296b83 - xiaobo.gu@droid12

                  set vdd cpu_a to 1120 mv
                  set vdd cpu_b to 1050 mv
                  set vddee to 1000 mv
                  Board ID = 6
                  CPU clk: 1200MHz
                  DQS-corr enabled
                  DDR scramble enabled
                  DDR4 chl: Rank0+1 @ 816MHz
                  Rank0: 2048MB(auto)-2T-18
                  Rank1: 1024MB(auto)-2T-18
                  DataBus test pass!
                  AddrBus test pass!
                  Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
                  New fip structure!
                  Load bl30 from SD, src: 0x00010200, des: 0x01100000, size: 0x0000d600
                  Load bl31 from SD, src: 0x00020200, des: 0x05100000, size: 0x0002c600
                  Load bl33 from SD, src: 0x00050200, des: 0x01000000, size: 0x00053e00

                  Comment


                  • #99
                    I'm sorry, I can not help you anymore. Use the original uboot again and try the tips from here.

                    Comment


                    • Ok, thanks anyway for your effort.
                      Maybe the problem is the Uart adapter. It's usb device so when I plug it (not connected to the box, just adapter) windows must recognize it and search for drivers. In this case windows said it's unrecognized device. Only when it's connected to the box with VCC windows recognize it like Prolific usb-to-serial comm port. Will try to replace it.

                      Comment


                      • Yes, that's not OK. Which chip is installed in your usb adapter?

                        Comment


                        • Think it's PL2303 XA

                          Comment


                          • Choose a suitable DriverInstaller for your Windows version here
                            Or install the driver manually.

                            Comment


                            • That's not a problem.
                              When box is connected, uart is detected properly and drivers are installed, in device manager everything is ok. But, when adapter only is connected windows not detecting it properly. So, drivers are installed, but when is no VCC, adapter is not detected properly. Probably adapter is faulty, will try to find another.

                              Comment


                              • I bought another ttl adapter, this one is ok, when connected to pc it's recognized properly.
                                I connected box just with RX TX GND and it's working normally, Putty displays log as it should.
                                But, log is the same, one thing is changed it's not repeating over and over, it's just one log:

                                GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:3;RCY:0 ;EMMC:800;NAND:82;SD:0;READ:0;0.0;CHK:0;
                                no sdio debug board detected
                                TE: 415677

                                BL2 Built : 13:18:48, Dec 21 2016.
                                gxl g4fc4d4e - xiaobo.gu@droid05

                                set vdd cpu_a to 1120 mv
                                set vdd cpu_b to 1050 mv
                                set vddee to 1000 mv
                                Board ID = 6
                                CPU clk: 1200MHz
                                DQS-corr enabled
                                DDR scramble enabled
                                DDR4 chl: Rank0+1 @ 636MHz
                                Rank0: 2048MB-2T-18
                                Rank1: 1024MB-2T-18
                                DataBus test pass!
                                AddrBus test pass!
                                Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
                                New fip structure!
                                Load bl30 from SD, src: 0x00010200, des: 0x01100000, size: 0x0000d600
                                Load bl31 from SD, src: 0x00020200, des: 0x10100000, size: 0x00015400
                                Load bl33 from SD, src: 0x00038200, des: 0x01000000, size: 0x000a9a00
                                NOTICE: BL3-1: v1.0(debug):2e39a99
                                NOTICE: BL3-1: Built : 16:36:21, Sep 20 2016
                                aml log : bl31 normal boot !
                                [Image: gxl_v1.1.3154-065f772 2016-09-29 14:08:54 yan.wang@droid05]
                                OPS=0x82
                                8b a8 52 a4 2f 34 df e4 3 3c 95 50 [0.830224 Inits done]
                                secure task start!
                                high task start!
                                low task start!
                                INFO: BL3-1: Initializing runtime services
                                WARNING: No OPTEE provided by BL2 boot loader
                                ERROR: Error initializing runtime service opteed_fast
                                INFO: BL3-1: Preparing for EL3 exit to normal world
                                INFO: BL3-1: Next image address = 0x1000000
                                INFO: BL3-1: Next image spsr = 0x3c9


                                U-Boot 2015.01-gf3cbd70 (Feb 24 2017 - 22:51:16)

                                DRAM: 3 GiB
                                Relocation Offset is: b6ec9000

                                Comment

                                Working...
                                X