Code
thanks YOU brother
Waiting for you tomorrow or MondayBeiträge von Rami2
-
-
Code
And what is the solution, brother?CodeI have these files, do you help me with something I downloaded before the problem occurred to my device -
I installed botloader.img file on sd by LibreELEC.USB-SD.Creator.Win32
Then I put the sd in the device and it reads the bootloader from the sd and gives me this logo logo
Code
Alles anzeigenbl2_stage_init 0x01 bl2_stage_init 0x81 hw id: 0x0000 - pwm id 0x01 bl2_stage_init 0xc1 bl2_stage_init 0x02 no sdio debug board detected L0:e033003f L1:00000703 L2:0000c067 L3:14000020 B2:00433060 B1:f0c021b0 TE: 735865 BL2 Built : 15:17:18, Feb 20 2019. g12b gb91a9c0 - jenkins@walle02Ysh Board ID = 2 Set A53 clk to 24M Set A73 clk to 24M Set clk81 to 24M A53 clk: 1200 MHz A73 clk: 1200 MHz CLK81: 166.6M smccc: 000b470c DDR driver_vesion: LPDDR4_PHY_V_0_1_11 build time: Feb 20 2019 15:17:14 board id: 2 Load FIP HDR from SD, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0 fw parse done Load ddrfw from SD, src: 0x00014200, des: 0xfffd0000, size: 0x0000c000, part: 0 Load ddrfw from SD, src: 0x00068200, des: 0xfffd0000, size: 0x00004000, part: 0 PIEI prepare done Cfg max: 4, cur: 1. Board id: 255. Force loop cfg DDR4 probe ddr clk to 1200MHz Load ddrfw from SD, src: 0x0002c200, des: 0xfffd0000, size: 0x0000c000, part: 0 Check phy result INFO : End of initialization INFO : End of read enable training INFO : End of fine write leveling INFO : End of read dq deskew training INFO : End of MPR read delay center optimization INFO : End of Write leveling coarse delay INFO : End of write delay center optimization INFO : End of read delay center optimization INFO : End of max read latency training INFO : Training has run successfully! 1D training succeed Load ddrfw from SD, src: 0x00038200, des: 0xfffd0000, size: 0x0000c000, part: 0 Check phy result INFO : End of initialization INFO : End of 2D read delay Voltage center optimization INFO : End of 2D write delay Voltage center optimization INFO : Training has run successfully! R0_RxClkDly_Margin==91 ps 7 R0_TxDqDly_Margi==156 ps 12 R1_RxClkDly_Margin==0 ps 0 R1_TxDqDly_Margi==0 ps 0 dwc_ddrphy_apb_wr((0<<20)|(2<<16)|(0<<12)|(0xb0):0001 ddr scramble enable 2D training succeed auto size-- 65535DDR cs0 size: 2048MB DDR cs1 size: 0MB DMC_DDR_CTRL: 0040002cDDR size: 2048MB cs0 DataBus test pass cs0 AddrBus test pass pre test bdlr_100_average==462 bdlr_100_min==462 bdlr_100_max==462 bdlr_100_cur==462 aft test bdlr_100_average==462 bdlr_100_min==462 bdlr_100_max==462 bdlr_100_cur==462 100bdlr_step_size ps== 457 result report boot times 0 non-sec scramble use zero key ddr scramble enabled Enable ddr reg access Load FIP HDR from SD, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 0 Load BL3X from SD, src: 0x0006c200, des: 0x0175c000, size: 0x00128000, part: 0 0.0;0.0;M3 CHK:0;bl30 start run into bl31 NOTICE: BL31: v1.3(release):bee21ef NOTICE: BL31: Built : 16:42:55, Feb 21 2019 NOTICE: BL31: G12A secure boot! INFO: BL3-2: ATOS-V2.4-202-g7b21f5e #1 Fri Dec 21 01:30:01 UTC 2018 arm INFO: BL3-2: Chip: Unknown Rev: A (29:A - 40:2) INFO: BL3-2: crypto engine DMA INFO: BL3-2: secure time TEE INFO: BL3-2: CONFIG_DEVICE_SECURE 0xb200000e U-Boot 2015.01-g90d64dd5d3-dirty (Apr 23 2019 - 10:52:48) DRAM: 2 GiB Relocation Offset is: 76ef7000 spi_post_bind(spicc): req_seq = 0 spi_post_bind(spifc): req_seq = 1 register usb cfg[0][1] = 0000000077f8a4a8 MMC: dm one emmc init . aml_priv->desc_buf = 0x0000000073ee77b0 aml_priv->desc_buf = 0x0000000073ee9af0 SDIO Port B: 0, SDIO Port C: 1 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 emmc/sd response timeout, cmd1, status=0x1ff2800 MMC init failed Using default environment In: serial Out: serial Err: serial reboot_mode=cold_boot itest - return true/false on integer compare Usage: itest [.b, .w, .l, .s] [*]value1 <op> [*]value2 [store]To run cmd[emmc dtb_read 0x1000000 0x40000] co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 emmc/sd response timeout, cmd1, status=0x1ff2800 _dtb_init()-2795: mmc init failed [KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000 vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters vpu: clk_level = 7 vpu: vpu_power_on vpu: set clk: 666667000Hz, readback: 666666667Hz(0x100) vpu: vpu_module_init_config vpp: vpp_init vpp: g12a/b osd1 matrix rgb2yuv .............. vpp: g12a/b osd2 matrix rgb2yuv.............. vpp: g12a/b osd3 matrix rgb2yuv.............. cvbs: cpuid:0x29 tpm activate 01 01: 18 02 01: 00 03 04: 00 00 52 4e 06 08: 32 30 31 39 30 35 30 39 07 0f: 33 35 30 39 32 34 30 30 30 30 32 31 30 37 30 05 04: 01 01 01 01 08 01: 00 04 06: 00 09 34 4a ef de ff 01: 7d card in co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 40000000 aml_sd_retry_refix[983]:delay = 0x0,gadjust =0x12000 [mmc_startup] mmc refix success [mmc_init] mmc init success cannot get sdcard label co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 400000 co-phase 0x3, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 emmc/sd response timeout, cmd2, status=0x1ff2800 ** Bad device mmc 1 ** Normal bootup Net: dwmac.ff3f0000 Hit Enter or space or Ctrl+C key to stop autoboot -- : 0 Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store rom_write add off size. write uboot to the boot device store erase boot/data: erase the area which is uboot or data store erase partition <partition_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store read boot 0x1080000 0x0 0x100000] Err imgread(L320):Fail to read 0x100000B from part[boot] at offset 0 Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store rom_write add off size. write uboot to the boot device store erase boot/data: erase the area which is uboot or data store erase partition <partition_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store read recovery 0x1080000 0x0 0x100000] Err imgread(L320):Fail to read 0x100000B from part[recovery] at offset 0 dreambox_one#CodeDoes not connect to the network As soon as I pull out the sd, the black screen returns without reading anything -
Thank you brother from the heart
-
My brother is red, unsteady
-
My brother, I sent a message to them and they did not answer me
Why is this complex? The device does not connect to the network, there is no IP
The solution is only by com and a file, and if the support team has the solution why not publish it publicly
What is the program and file to get out of the fatal stage
solution only by com
-
Unfortunately, the Chinese don't tell you how the problem happened, why you did it, and why you did it
They treat you well and immediately give you programs and files that get you out of the deadly stages
Don't blame me if I'm wrong
What should I do I made a mistake but I don't know where I did wrong
give me a solution
Give me a program and a file to get out of the fatal stage
-
The device does not stop in stop mode does not give me the ip
It is not connected to the network
It lights up but the bulb is red
And when I try to link it in putty it gives me a black screen even though it is linked to com but the logo does not come up and the screen is black in putty
Give me only one program linked to com to revive the device
As in the miserable Chinese devices that have many programs to get out of the deadly stages
-
Do you know what is the problem?
The problem is that the miserable Chinese devices that are sold in the market for $ 10 have support programs to install the kernel.bin and bootloader.bin files and other files, and the dreambox devices only have dreamup and it does not work on oe2.5 and 2.6 to revive the devices. None of us makes mistakes. Therefore, it is necessary to provide programs to solve the fatal problems. We'll be heading back in the opposite direction with the dreambox 7 exit. I intended to buy it for me and some friends, but now after what happened to me, unfortunately I will not buy it
-
Please don't paste links to random/unverified bootloaders here. I've deleted the link from your initial post.
If you have any issues please contact the official support. There are recovery mechanismns almost every possible failure (hardware excluded).
Is it possible to have the official support link?
-
Code
Question: Are you in charge here? We have problems, where do we solve them? Corrupt cheap Chinese devices have programs and support. And the Chinese don't say go to Emmanuel Again, are you the official here on the site? -
Yes, dreamup should run on kernel 2.6
I have the same problem with putty black screen due to a mistake I made
No stop mode
Red lamb turns on and off
