Remote power trouble

Quote from bumerc

gulp79

update

u-boot_ddr4

still bootloop.. i think i'm going to stay with 2gb of ram

Btw thank you for all your efforts!!

This is the last log:

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

BL2 Built : 13:27:37, Oct 25 2017. gxl g56b77aa - xiaobo.gu@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 3
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR4 chl: Rank0+1 @ 1008MHz
Trainin.g Err PGSR0: 0x840847ff.Retry...
DX0GSR0: 0x00952520....
DX1GSR0: 0x009626a0....
DX2GSR0: 0x00992520....
DX3GSR0: 0x00942620....
DX0GSR2: 0x26000018....
DX1GSR2: 0x26000018....
DX2GSR2: 0x26000018....
DX3GSR2: 0x25800018....
DX0GSR3: 0x01010100....
DX1GSR3: 0x01010100....
DX2GSR3: 0x01010100....
DX3GSR3: 0x01010100....

gulp79

1008Mhz, apparently too much for your "DDR4"

tomorrow, I reduce the clk rate and do another build

seems that i can boot with ChimeyJimmey link

MEGA

i've extracted

aml_sdc_burn.UBOOT

and

bootloader.PARTITION

and now:

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

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 = 3
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
STICKY_REG0: 0x00000000
STICKY_REG1: 0x00000000
STICKY_REG9: 0x00000000
DDR3 chl: Rank0+1 @ 672MHz - FAIL
STICKY_REG0: 0x00000000
STICKY_REG1: 0x00000000
STICKY_REG9: 0x00000000
DDR4 chl: Rank0+1 @ 672MHz - PASS
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: 0x05100000, size: 0x0002c600
Load bl33 from SD, src: 0x00050200, des: 0x01000000, size: 0x00065800
NOTICE:  BL3-1: v1.0(release):a625749
NOTICE:  BL3-1: Built : 11:25:15, Aug 25 2017
NOTICE:  BL31: BL33 decompress pass
mpu_config_enable:ok
[Image: gxl_v1.1.3243-377db0f 2017-09-07 11:28:58 qiufang.dai@droid07]
OPS=0x82
wdt: reset registers!
a1 14 cc 9c 7a 4a 4f e 1 4 c0 16 [0.781345 Inits done]
secure task start!
high task start!
low task start!
ERROR:   Error initializing runtime service opteed_fast


U-Boot 2015.01-g2d1a155-dirty (Nov 20 2017 - 15:06:32)

DRAM:  3 GiB
Relocation Offset is: b6eb4000
register usb cfg[0][1] = 00000000b7f5b0e0
[CANVAS]canvas init
boot_device_flag : 1
set wlan gpio down.
set bluetooth gpio down.
Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc.
init bus_cycle=6, bus_timing=7, system=5.0ns
reset failed
get_chip_type and ret:fffffffe
get_chip_type and ret:fffffffe
chip detect failed and ret:fffffffe
nandphy_init failed and ret=0xfffffff1
MMC:   aml_priv->desc_buf = 0x00000000b3eb4790
aml_priv->desc_buf = 0x00000000b3eb6ab0
SDIO Port B: 0, SDIO Port C: 1
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
init_part() 293: PART_TYPE_AML
[mmc_init] mmc init success
dtb magic edfe0dd0
      Amlogic multi-dtb tool
      Single dtb detected
start dts,buffer=00000000b3eb9300,dt_addr=00000000b3eb9300
      Amlogic multi-dtb tool
      Single dtb detected
parts: 11
00:      logo   0000000002000000 1
01:  recovery   0000000002000000 1
02:       rsv   0000000000800000 1
03:       tee   0000000000800000 1
04:     crypt   0000000002000000 1
05:      misc   0000000002000000 1
06: instaboot   0000000020000000 1
07:      boot   0000000002000000 1
08:    system   0000000040000000 1
09:     cache   0000000020000000 2
10:      data   ffffffffffffffff 4
init_part() 293: PART_TYPE_AML
....

I'm testing it right now.... i don't know if the bug is still there or not

no.... i can boot from sd (aml_sdc_burn.UBOOT used as u-boot.bin.sd.bin)

but not with u-boot from internal storage... (UBOOT.USB and also bootloader.partition used as u-boot.ini)

once i write to internal memory the uboot this is the log:

BL2 Built : 13:27:37, Oct 25 2017. gxl g56b77aa - xiaobo.gu@droid12

set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 3
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 792MHz
Trainin  Err PGSR0: 0x8040007f.Retry...
DX0GSR0: 0x00bf2fa0....
DX1GSR0: 0x00be2fa0....
DX2GSR0: 0x00bf2f20....
DX3GSR0: 0x00be2fa0....
DX0GSR2: 0x30800000....
DX1GSR2: 0x30800000....
DX2GSR2: 0x30000000....
DX3GSR2: 0x2f800000....
DX0GSR3: 0x00000000....
DX1GSR3: 0x00000000....
DX2GSR3: 0x00000000....
DX3GSR3: 0x00000000....
Trainin  Err PGSR0: 0x8040007f.Retry...

Quote from TheChief

Is that ROM also working in the blue PCB S32-V6 with LPDDR3?

I would suggest to find a suitable Android ROM for your box (stock, preferably),

then edit it like suggested in this post - Remote power trouble - by injecting this u-boot, for example:

u-boot.bin@LPDDR3-792Mhz (Post #151)

Then flash it via USB Burning Tool/Burn Card Maker.

Keep the stock ROM at hand and beware that you might need to short-circuit the eMMc pins (while keeping the reset pressed all the time), in case you brick the box to a black one...

The file in post #151 does not exist anymore. Can i use this from #122 or #149?

You're free to try it.

Otherwise - ask bumerc or BigMike to supply again the one from #151...

P.S. The one from #149 seems to be for normal DDR3, as advised previously - I do NOT recommend flashing it on LPDDR3 box...

bumerc  BigMike What is the latest u-boot for S32-V6 (LPDDR3), blue PCB?

Since i'm also running the ROM from Freaktab on internal, this method would be more easy for me.

Tried the u-boot.bin (u-boot_lpddr3.tar.gz) from here: u-boot_h96pro+_fixed_power_on — Яндекс.Диск

Freaktab firmware loads and seems to work, but now i cannot boot from SD card using toothpicker method. Any ideas?

"adb reboot update"

from Android?

Semms to be a bigger problem, my keyboard locks and couldt not reboot/power off with RC. Will flash back the original Freaktab firmware and wait for a response of the guys here.

Why don't you:

# adb connect <ipofyourboxhere>

from another device with ADB in your network,

and once successfully connected,

try

# adb reboot update

to see if it will boot from LE SD/TF card?

Quote from TheChief

bumerc  BigMike What is the latest u-boot for S32-V6 (LPDDR3), blue PCB?

Since i'm also running the ROM from Freaktab on internal, this method would be more easy for me.

Remote power trouble

Thank you. Now Power on/off works with LE. Have to check Android on internal again, after some minutes keyboard/RC does not reponse. System seems to be freezed. I used the ChimeyJimmey method.

Now LE also freezed. How can i debug and help? With ADB? How can i get the bootloader log?

EDIT:

Could i have this RAM chip? Found one single chip with D9TXF printed on. Clock rate 933Mzh, Data rate: DDR3-1866

Quote from tyrol_gangster

there have been users on this forum ( zed85 ) claiming they don't experience the same issue, which is why I believe there has to be a solution that does not include trashing the whole thing

True. My brother has a H96 Pro Plus Amlogic S912 (or +) and can power up the device with his remote. He can also power down the box with his remote.
There is no working Android ROM (corrupted by internal installation) on the box anymore. I tried to install to internal after installing it to SD card first and that failed... Now he is running Libreelec from SD card and he can power up and power down the device.

See the following post for the remote.conf he is using right now.

remote.conf repository

Quote from TheChief

Thank you. Now Power on/off works with LE. Have to check Android on internal again, after some minutes keyboard/RC does not reponse. System seems to be freezed. I used the ChimeyJimmey method.

Now LE also freezed. How can i debug and help? With ADB? How can i get the bootloader log?

EDIT:

Could i have this RAM chip? Found one single chip with D9TXF printed on. Clock rate 933Mzh, Data rate: DDR3-1866

Check the power supply. So far none of the users complained about it

bumerc

Do you have something to tell about the question in post #197, please?

It freezes in LE and with Android. Without your u-boot.bin everything works as expected (except power on with LE). So i dont think, its the power supply. I would like to debug, but i dont know how. Now i'm back on the original Freaktab firmware. How can i get the log about RAM? Do i need e serial connection? Tutorial somewhere?