admin_from_Mars

  • Posts

    13
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Applications

Everything posted by admin_from_Mars

  1. I have a TV box with S905L3B (dtb file in android system is named gxlx2_p291_1g.dtb). However, I can't find a suitable dtb file for Armbian. So I wonder if I or someone else can adjust or modify the dtb file to boot an Armbian system if I have the gxlx2_p291_1g.dtb and gxlx2_p291_1g.dts files from the Android system(4.4.2)?
  2. I have a problem. I try to boot "Armbian_5.67_Aml-s9xxx_Debian_stretch_default_4.19.7_20181228.img.xz" on a S905L 3B TV box, the ditb file use the default one (it works for S905L). I use a TTL to USB device to check signal, and it started to login stage. However, the LAN port and HDMI port seem not work, as I can' t use SSH to connect to Armbian and I can't see any thing on the screen. So I guess maybe the dtb file is not suitable, and there may not be a suitable dtb for S905L3B. Could I modfiy a dtb file based on the S905L dtb file and the dtb file from the Andriod system in the S905L 3B TV box?
  3. balbes150 replied to my topic in TV boxes: There is no support for NAND in the main kernel.
  4. I have a problem. “ddbr” can not make a backup of a andriod system in a Amlogic S905 TV box with a NAND flash, see this link for more details. When I use 'ddbr' in an Ambian system booted by USB drive, it shows below: root@SumavisionQ5:~# ddbr DO YOU WANT TO BACKUP OR RESTORE ? BACKUP=(b) RESTORE=(r) b UNABLE TO FIND ANY EMMC OR SD DRIVES ON THIS SYSTEM!!! I think someone else must have the same problem. Can we make an improvement of 'ddbr' , so that it can be used for a NAND flash.
  5. Hello, everyone! I have an S905M device (Sumavision Q5, RAM:1G, ROM:8G), I made a bootable USB with an Armbian image( ARMBIAN 5.44 user-built Ubuntu 18.04.5 LTS 3.14.29, use gxbb_p201.dtb file ) . I want to use "ddbr" then “b” to make a backup of the EMMC. However, root@SumavisionQ5:~# ddbr DO YOU WANT TO BACKUP OR RESTORE ? BACKUP=(b) RESTORE=(r) b UNABLE TO FIND ANY EMMC OR SD DRIVES ON THIS SYSTEM!!! then I use command "lsblk", I found all partitions(cache, params, ... , data) of the internal storage (8G ROM) for andriod system are treated as seperated disks as shown below: root@SumavisionQ5:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 1 14.9G 0 disk |-sda1 8:1 1 128M 0 part /boot `-sda2 8:2 1 14.6G 0 part / cache 250:0 0 512M 0 disk params 250:1 0 64M 0 disk logo 250:2 0 32M 0 disk recovery 250:3 0 32M 0 disk rsv 250:4 0 8M 0 disk tee 250:5 0 8M 0 disk crypt 250:6 0 32M 0 disk misc 250:7 0 32M 0 disk instaboot 250:8 0 512M 0 disk boot 250:9 0 32M 0 disk system 250:10 0 1G 0 disk data 250:11 0 4.9G 0 disk zram0 253:0 0 100.9M 0 disk [SWAP] zram1 253:1 0 100.9M 0 disk [SWAP] zram2 253:2 0 100.9M 0 disk [SWAP] zram3 253:3 0 100.9M 0 disk [SWAP] use armbianmonitor -u, a detail info is uploaded in http://ix.io/2vPI From that, I find something the 8G ROM is in NAND instead of in EMMC : [ 6.263857] nandphy: Nand PHY Ver:XXX.XXX.001.0006 (c) 2013 Amlogic Inc. [ 6.270503] nandphy: ######STS IRQ mode for nand driver [ 6.275794] nandphy: NAND device id: 2c 64 44 4b a9 0 0 0 [ 6.281261] nandphy: detect NAND device: B revision NAND 8GiB MT29F64G08CBABA [ 6.340701] nandphy: clk_reg = 81000244 [ 6.343380] nandphy: bus_c=6,bus_t=7,sys=4.0ns,T_REA=16,T_RHOH=15 [ 6.347931] nandphy: new oob mode [ 6.352301] nandphy: NAND CKECK:arg nbbt:arg_valid=1,blk_addr=5,page_addr=0 [ 6.361720] nandphy: NAND CKECK:arg ncnf:arg_valid=1,blk_addr=4,page_addr=0 [ 6.382065] nandphy: NAND CKECK:arg phyp:arg_valid=1,blk_addr=8,page_addr=1 [ 6.402285] nandphy: NAND CKECK:arg nkey:arg_valid=1,blk_addr=9,page_addr=0 [ 6.432194] nandphy: NAND CKECK:arg ndtb:arg_valid=1,blk_addr=7,page_addr=33 [ 6.462225] nandphy: NAND CKECK:arg nenv:arg_valid=1,blk_addr=10,page_addr=9 [ 6.469413] nandphy: nfboot : [ 6.472338] nandphy: off:0x000000000000-0x000000800000 :partn=0:single_chip single_plane [ 6.478386] nandphy: nfcache : [ 6.481817] nandphy: off:0x000006800000-0x000029000000 :partn=2:single_chip multi_plane [ 6.489940] nandphy: nfcode : [ 6.493390] nandphy: off:0x00002f800000-0x000077000000 :partn=9:single_chip multi_plane [ 6.501481] nandphy: nfdata : [ 6.504948] nandphy: off:0x0000a6800000-0x000159800000 :partn=1:single_chip multi_plane How I can do it? Could command “ddbr” make a backup of NAND flash? OK! As far as I know,command “ddbr” can not make a backup of a andriod system in NAND flash. ________________________________________ Background................................................... I also have a device (Tianyi, TY1208-Z, RAM:1G, ROM:8G) with S905L, and I have successfully made a backup file of EMMC. The EMMC is normally recognised as shown below: root@aml:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk0 179:0 0 1.9G 0 disk |-mmcblk0p1 179:1 0 128M 0 part `-mmcblk0p2 179:2 0 1.7G 0 part mmcblk1 179:32 0 7.3G 0 disk |-mmcblk1p1 179:33 0 122M 0 part /boot `-mmcblk1p2 179:34 0 6.5G 0 part / mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk zram0 253:0 0 50M 0 disk /var/log zram1 253:1 0 417M 0 disk [SWAP]
  6. Yes, you can make a bootable USB with an Armbian image . Use "ddbr" then “b” to make a backup of the internal EMMC. The backup file will be in /ddbr of the USB device. Restore that image file with "ddbr" then "r" to another device with same hardwares.