[Trongle S3 no signal, no anything]

***APOLOGIES FOR DELAY, LIMIT ON HOW MANY TIMES I CAN POST PER 24 HOURS***

 

I've managed to connect via TTL EEPROM connection and am getting the below. I'm using the meson-gxl-s905x-p212.dtb dtb file. With the "Armbian_20.02.0-rc1.037_Aml-s9xxx_bionic_current_5.5.0-rc6_desktop_20200205.img" image.

 

Is "fdt_instaboot: no instaboot image" causing the issue?

 

Any advice is much appreciated. 

 

Courtesy note: any one else using this the ttl speed is 115200.

 

Quote

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.02.19 22:27:47 =~=~=~=~=~=~=~=~=~=~=~=
GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;
TE: 150401

BL2 Built : 13:48:56, Sep 23 2016. 
gxl g7459bd4 - jianxin.pan@droid06

set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 1
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - PASS
Rank0: 1024MB(auto)-2T-13
Rank1: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from eMMC, src: 0x00020200, des: 0x10100000, size: 0x00015400
Load bl33 from eMMC, 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
e0 64 25 87 a7 56 28 f 21 20 68 3f [0.390607 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-gdd4a4de (Mar 03 2017 - 18:35:08)

DRAM:  2 GiB
Relocation Offset is: 76ec9000
register usb cfg[0][1] = 0000000077f5f500
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: clk_level = 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
vpp: vpp_init
boot_device_flag : 1
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 = 0x0000000073ec96b0
aml_priv->desc_buf = 0x0000000073ecb9d0
SDIO Port B: 0, SDIO Port C: 1
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
[mmc_init] mmc init success
mmc read lba=0x14000, blocks=0x400
      Amlogic multi-dtb tool
      Multi dtb detected
      Multi dtb tool version: v2 .
      Support 2 dtbs.
        aml_dt soc: gxl platform: p212 variant: 2g
        dtb 0 soc: gxl   plat: p212   vari: 1g
        dtb 1 soc: gxl   plat: p212   vari: 2g
      Find match dtb: 1
start dts,buffer=0000000073ece270,dt_addr=0000000073ed8270
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    0000000080000000 1
09:     cache    0000000020000000 2
10:      data    ffffffffffffffff 4
get_dtb_struct: Get emmc dtb OK!
overide_emmc_partition_table: overide cache 
[mmc_get_partition_table] skip partition cache.
Partition table get from SPL is : 
        name                        offset              size              flag
===================================================================================
   0: bootloader                         0            400000                  0
   1: reserved                     2400000           4000000                  0
   2: cache                        6c00000          20000000                  2
   3: env                         27400000            800000                  0
   4: logo                        28400000           2000000                  1
   5: recovery                    2ac00000           2000000                  1
   6: rsv                         2d400000            800000                  1
   7: tee                         2e400000            800000                  1
   8: crypt                       2f400000           2000000                  1
   9: misc                        31c00000           2000000                  1
  10: instaboot                   34400000          20000000                  1
  11: boot                        54c00000           2000000                  1
  12: system                      57400000          80000000                  1
  13: data                        d7c00000         2c5400000                  4
mmc read lba=0x12000, blocks=0x2
mmc read lba=0x12002, blocks=0x2
mmc_read_partition_tbl: mmc read partition OK!
eMMC/TSD partition table have been checked OK!
mmc env offset: 0x27400000 
In:    serial
Out:   serial
Err:   serial
reboot_mode=cold_boot
hpd_state=0
cvbs performance type = 6, table = 0
[store]To run cmd[emmc dtb_read 0x1000000 0x40000]
read emmc dtb
      Amlogic multi-dtb tool
      Multi dtb detected
      Multi dtb tool version: v2 .
      Support 2 dtbs.
        aml_dt soc: gxl platform: p212 variant: 2g
        dtb 0 soc: gxl   plat: p212   vari: 1g
        dtb 1 soc: gxl   plat: p212   vari: 2g
      Find match dtb: 1
Net:   dwmac.c9410000
wipe_data=successful
wipe_cache=successful
upgrade_step=2
[OSD]load fb addr from dts
[OSD]failed to get fb addr for logo
[OSD]use default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]load fb addr from dts
[OSD]failed to get fb addr for logo
[OSD]use default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[CANVAS]canvas init
[CANVAS]addr=0x3d800000 width=5760, height=2160
amlkey_init() enter!
[EFUSE_MSG]keynum is 4
[BL31]: tee size: 0
[KM]Error:f[key_manage_query_size]L507:key[usid] not programed yet
[KM]Error:f[key_manage_query_size]L507:key[deviceid] not programed yet
get_cpu_id flag_12bit=1
SARADC open channel(0).
SARADC channel(0) is 0x3ef, Out of range(0x0~0x50)!
saradc - saradc sub-system

Usage:
saradc saradc open <channel>        - open a SARADC channel
saradc close    - close the SARADC
saradc getval    - get the value in current channel
saradc get_in_range <min> <max>    - return 0 if current value in the range of current channel

InUsbBurn
noSof
Hit Enter or space or Ctrl+C key to stop autoboot -- :  1 0 
card in
[mmc_init] mmc init success
Device: SDIO Port B
Manufacturer ID: 3
OEM: 3456
Name: ASTCTran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.5 GiB
mmc clock: 40000000
Bus Width: 4-bit
reading s905_autoscript
1351 bytes read in 5 ms (263.7 KiB/s)
## Executing script at 01020000
start amlogic old u-boot
reading boot_android
** Unable to read file boot_android **
** Bad device usb 0 **
reading u-boot.ext
** Unable to read file u-boot.ext **
** Bad device usb 0 **
reading uEnv.txt
1157 bytes read in 4 ms (282.2 KiB/s)
mac=42:f2:9e:a9:91:c3
reading /zImage
23357952 bytes read in 1295 ms (17.2 MiB/s)
reading /uInitrd
11037395 bytes read in 615 ms (17.1 MiB/s)
reading /dtb/amlogic/meson-g12b-odroid-n2.dtb
47774 bytes read in 9 ms (5.1 MiB/s)
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
[rsvmem] bl31 reserved memory set addr error.
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    11037331 Bytes = 10.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
      Amlogic multi-dtb tool
      Single dtb detected
load dtb from 0x1000000 ......
## Flattened Device Tree blob at 01000000
   Booting using the fdt blob at 0x1000000
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
[rsvmem] bl31 reserved memory set addr error.
   Loading Ramdisk to 7342f000, end 73eb5a93 ... OK
   Loading Device Tree to 000000001fff1000, end 000000001ffffa9d ... OK
signature: 
fdt_instaboot: no instaboot image

Starting kernel ...

uboot time: 4530887 us

 

[Trongle S3 no signal, no anything]

Anyone else ever get just a blank screen? I’m trying to install onto a Trongle S3 box. I’ve tried a number of dtb’s but as it’s a relatively rear box nothing is definite. Tried to match them by spec but hoped it would at least register an output on my monitor. 

I get a no signal notification. 

 

I will be trying to tty the com port but this includes soldering so wanted to see if anyone else knew of a possible solution before I spent time doing this.