Jump to content

Single Armbian image for RK + AML + AW (aarch64 ARMv8)

balbes150

By balbes150
in General Chat

 Share

Recommended Posts

balbes150

balbes150

Posted
  • Author
Posted
15 hours ago, lgranie said:

I mount an usb drive with vfat filesystem on usb3 (personal files, no system). I will try soon booting on it to test your next releases.

 

Can it be the reason for my reboot problem that I have got a usb drive plug during reboot?

startup, the system checks all media for running scripts.

 

13 hours ago, igor_carenko said:

The question is - what kind of u-boot i can flash into the X96 Android set-top box on the S905x processor in order to try to load armbian from eMMC?

The exact name of the image you are using, the exact name of the TV box model (characteristics), and a detailed description of the steps you are taking.

 

 

Link to comment
Share on other sites
igor_carenko

igor_carenko

Posted
Posted (edited)
2 hours ago, balbes150 said:

The exact name of the image you are using, the exact name of the TV box model (characteristics), and a detailed description of the steps you are taking.

1. From Android selected and executed "aml_update.zip", for activation boot.
2. Writed to USB-flash drive "armbian" image.
// Tryed "Armbian_20.05.0-_Arm-64*" (tryed buster, focal 5.5.1 20200212; yesterday tryed Armbian_20.05.0-trunk_Arm-64_bionic_dev_5.6.0-rc1-next-20200214_desktop - all booting and working OK from USB-flash)
3. Edited uEnv for "p212". Inserted USB-flash and boot :).
4. Launched ./install_aml.sh from root folder, script executed done.
5. If I try boot without USB-flash - looped bootscreen "x96"; USB booting OK.

P.S. TV-box "X96", 2G RAM/16G ROM
PCB: "Q2X V2.1"
eMMC: Samsung KLMAG2WEMB-B031
Wi-Fi: RTL8189ETV

Edited by igor_carenko
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted

1. Show the output of "fdisk-l" after the installation and reboot.

2. Run gparted and show what it sees on eMMC after installation.

3. What version of Android was in the firmware before installation ?

4. Show the content (uEnv.txt)

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
2 hours ago, igor_carenko said:

1. From Android selected and executed "aml_update.zip", for activation boot.
2. Writed to USB-flash drive "armbian" image.

Where did the activation files come from if the image was recorded later ????

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted

New versions of images 20200218.

 

Important change. With this version, you can easily add the desired u-boot on any PC (including Windows) .

 

To do this, new versions of u-boot are downloaded on the site.

 

https://yadi.sk/d/lTbXkrmZN5Hf6g

 

Rules for using the new u-boot option. Download, Armbian image, unpack. Write image Armbian to the SD card. Download and write the desired version of the u-boot file to SD card. Configure the DTB and the launch string (APPEND) in (uEnv.txt) for the desired model\platform.

 

Pay attention. Now you don't need to write u-boot with complex commands, you write the u-boot image with the same program as you usually write an Armbian image. This allows you to configure the system to run (including writing a u-boot image) on any PC (including Windows).

 

Pay attention. The new version changed the size of the partitions that are obtained when writing an image (all images have a fixed size of 5GB).  This u-boot entry option only applies to the new version 20200218 and subsequent versions. Don't try this for old images. This will not work on older images.

2
Link to comment
Share on other sites
igor_carenko

igor_carenko

Posted
Posted
2 hours ago, balbes150 said:

1. Show the output of "fdisk-l" after the installation and reboot.

2. Run gparted and show what it sees on eMMC after installation.

3. What version of Android was in the firmware before installation ?

4. Show the content (uEnv.txt)

Spoiler

uEnv.txt:

LINUX=/zImage
INITRD=/uInitrd

# aml s9xxx
FDT=/dtb/amlogic/meson-gxl-s905x-p212.dtb
APPEND=root=LABEL=ROOT_EMMC rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

*************************************************************************

fdisk:

Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mmcblk1: 14.6 GiB, 15634268160 bytes, 30535680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0694b701

Device         Boot   Start      End  Sectors  Size Id Type
/dev/mmcblk1p1      1368064  1867775   499712  244M  c W95 FAT32 (LBA)
/dev/mmcblk1p2      1869824 30535679 28665856 13.7G 83 Linux


Disk /dev/sda: 14.5 GiB, 15527313408 bytes, 30326784 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8892cc98

Device     Boot  Start      End  Sectors  Size Id Type
/dev/sda1        32768   557055   524288  256M  e W95 FAT16 (LBA)
/dev/sda2       557056 30023487 29466432 14.1G 83 Linux


Disk /dev/zram0: 50 MiB, 52428800 bytes, 12800 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram1: 886.3 MiB, 929333248 bytes, 226888 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

 

Screenshot_2020-02-18_13-44-19.png

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
32 minutes ago, igor_carenko said:

There is a file with a size of 0 in the image, it does not work on my TV box :( Therefore, I kind found old file:
https://yadi.sk/d/bqV6MEL-sWKmv
Android version was 6, non-rooted.
Only after this script, multiload runed in my occurence.

Since then, and we had to start, these versions are not consistent with existing systems and will not work. Everything else doesn't make sense.

 

Activating the multi-boot does not work, because you probably ran all sorts of shit on the TV box before and did not follow the instructions - full recovery of the standard firmware via USB Burn Tool.

Link to comment
Share on other sites
NicoD

NicoD

Posted
Posted
2 hours ago, balbes150 said:

New versions of images 20200218.

I just tried "Armbian_20.05.0-trunk_Arm-64_bionic_current_5.5.1_desktop_20200218.img" with the Orange Pi3.
1 . Wrote it to sd-card.
2 . Downloaded "u-boot-allwinner-h6-tanix-tx6.img" Wrote that to the first (boot) patition.
3 . Adjusted the uEnv.txt to point to "sun50i-h6-orangepi-3.dtb"
4 . Tried first the second APPEND line without the first. Then the first without the 2nd.

No boot, all lights stay off.

Without doing 2, but all others it just boots from eMMC. What am I doing wrong?  Thanks.

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
21 minutes ago, NicoD said:

No boot, all lights stay off.

I don't have OPI3, I can assume that OPI3 needs its own u-boot. The version from Tanix TX6 will not work. You can try pulling u-boot from any working image (which runs on OPI3) and try using it. If you get a working u-boot, send it my, I can process it for use in the specified mode (writing from Windows) on universal images for writing them to OPI3.

1
Link to comment
Share on other sites
NicoD

NicoD

Posted
Posted
On 2/18/2020 at 2:37 PM, balbes150 said:

You can try pulling u-boot from any working image (which runs on OPI3) and try using it. If you get a working u-boot, send it my, I can process it for use in the specified mode (writing from Windows) on universal images for writing them to OPI3.

Are you something with this? Sorry I'm bit clueless about these things.

linux-u-boot-current-orangepi3_20.05.0-trunk_arm64.deb linux-u-boot-dev-orangepi3_20.05.0-trunk_arm64.deb

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
19 minutes ago, NicoD said:

Are you something with this? Sorry I'm bit clueless about these things.

Getting the right file is very easy. Run any version of Armbian on OPI3, and run  the command

 

fdisk -l

 

pay attention to the number that indicates the beginning of the first section on the SD card, then run the second command, which uses the number of the beginning of the section minus 1

for example you will get this output

 

/dev/sdf1                32768  1081343 1048576   512M             e W95 FAT16 (LBA)
/dev/sdf2              1081344 10239999 9158656   4,4G            83 Linux

 

32768 - 1 = 32767

 

dd if=/dev/sdf of=u-boot-opi3.img bs=512 count=32767

 

You send the received file u-boot-opi3.img  to me.

1
Link to comment
Share on other sites
NicoD

NicoD

Posted
Posted

@balbes150 I must be doing something wrong. When I write the u-boot-opi3.img to the boot partition, the boot partition disappears from view. 
This is what I've done.
 

Spoiler 

nicod@orangepi3:~$ sudo fdisk -l
[sudo] password for nicod: 
Disk /dev/mmcblk1: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xa886ce14

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk1p1       8192 15117183 15108992  7.2G 83 Linux


Disk /dev/mmcblk2: 59.6 GiB, 64021856256 bytes, 125042688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x42bb5020

Device         Boot Start       End   Sectors Size Id Type
/dev/mmcblk2p1       8192 123792255 123784064  59G 83 Linux


Disk /dev/zram0: 50 MiB, 52428800 bytes, 12800 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram1: 997 MiB, 1045385216 bytes, 255221 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

nicod@orangepi3:~$ sudo dd if=/dev/mmcblk2p1 of=u-boot-opi3.img bs=512 count=8191
8191+0 records in
8191+0 records out
4193792 bytes (4.2 MB, 4.0 MiB) copied, 0.216758 s, 19.3 MB/s

 

Sorry for the troubles. If I can do it right I'll do it for a lot more boards I've got.

u-boot-opi3.img

Link to comment
Share on other sites
martinayotte

martinayotte

Posted
Posted
14 minutes ago, NicoD said:

I must be doing something wrong. When I write the u-boot-opi3.img to the boot partition, the boot partition disappears from view.

That is because Armbian doesn't have any BOOT partition, and doing "dd" without "skip/seek" will copy Armbian partition table over the Balbes one.

To avoid that overwrite of partition table, you need to "skip" the first 8192 bytes when reading, and "seek" the same amount of bytes when writing into the other image.

Link to comment
Share on other sites
NicoD

NicoD

Posted
Posted
4 minutes ago, martinayotte said:

That is because Armbian doesn't have any BOOT partition, and doing "dd" without "skip/seek" will copy Armbian partition table over the Balbes one.

To avoid that overwrite of partition table, you need to "skip" the first 8192 bytes when reading, and "seek" the same amount of bytes when writing into the other image.

:unsure:
I'm confused. The more I read the 2nd sentence the less I understand. Could you tell me what command I can use to get the u-boot to work on Balbes images? All that uboot wizardness goed above my hat :)
I don't understand what you mean with "and "seek" the same amount of bytes when writing into the other image."

Link to comment
Share on other sites
martinayotte

martinayotte

Posted
Posted
2 hours ago, NicoD said:

I'm confused.

The U-Boot is located after the partition table but before the first partition. So, when you grabbed the U-Boot from Armbian image, and when you start the extract at byte # 0, it is also grabbing the partition table followed by U-Boot itself. U-Boot location is at byte #8192, so the extract should be done like that : 

dd if=ambian.img of=u-boot-only.img bs=1024 skip=8 count=1024

This will extract a 1MB image, big enough since native Armbian U-Boot is sized about 620KB ...

Then, you can place it inside Balbes image without touching it own partition table by doing a "seek" : 

dd if=u-boot-only.img of=balbes-image.img bs=1024 seek=8 conv=notrunc

That should do the job without scrapping Balbes original partition table ...

1
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
14 hours ago, NicoD said:

Sorry for the troubles. If I can do it right I'll do it for a lot more boards I've got.

You did almost everything right, one small mistake. :)

 

wrong

sudo dd if=/dev/mmcblk2p1 of=u-boot-opi3.img bs=512 count=8191

 

 

right

sudo dd if=/dev/mmcblk2 of=u-boot-opi3.img bs=512 count=8191

 

 

Note that you need to copy the first sectors of the device (not the partition). The loader is always located in the first sectors of the device. 

1
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
14 hours ago, martinayotte said:

To avoid that overwrite of partition table, you need to "skip" the first 8192 bytes when reading, and "seek" the same amount of bytes when writing into the other image.

If you use an arbitrary u-boot (not files that are already specially prepared and located on my site), then you use two commands to write u-boot.

This is indicated in the instructions in the first message of this topic (in the spoiler for old u-boot).  :)

 

11 hours ago, martinayotte said:

The U-Boot is located after the partition table but before the first partition. So, when you grabbed the U-Boot from Armbian image, and when you start the extract at byte # 0, it is also grabbing the partition table followed by U-Boot itself. U-Boot location is at byte #8192, so the extract should be done like that :

AML also uses the first bytes, so the universal option (which will work on all platforms the same way) is specified in my message.  :)

 

Pay attention. A key feature of my ready-made u-boot is the ability to write them in a "dumb" way (by any program), including in the Wibdow system, where there is no easy way to perform complex writing options (for saving the partition table).

 

 

@NicoD  To use your received u-boot file (which you will get yourself), you need to write this file with two commands (these commands are in the first message of the theme in the spoiler). I asked you for this file, just in order to process it at home and make a u-boot file that can be used in a simple "stupid" recording mode by any program in Windows. If you provide me with verified files from other devices (models), I can also make the necessary u-boot options from them (for simple recording) and put them on the site for General use by other users.

1
Link to comment
Share on other sites
tomassosk

tomassosk

Posted
Posted

Hello,

I am owner of Ugoos AM6 PRO and I want to know if it is possible to run armbian with passthrough ( DTS, AC3, DTS-HD, TrueHD... ).

I have tried armbian image, but with pulseaudio there is no sound ( hdmi, spdif ), after g12_sound.sh script there is only hdmi stereo to my receiver.

 

Am I doing something wrong, or there is no support for passthrough in armbian?

Link to comment
Share on other sites
noname

noname

Posted
Posted

Hello,

After I broke my tronsmart, I decided to buy Tanix TX6 (4/64) (I already have orange pi+ 2e and everything works well).

I tried to use the latest image with a new mechanism uboot and device does not boot.

I use windows and rufus. (and u-boot-allwinner-h6-tanix-tx6.img)

I guess that after I write an image with uboot it breaks everything.

863275505_.png.d63943714cc4e12cdeb86a131e979ed0.png

Link to comment
Share on other sites
almotra

almotra

Posted
Posted

Hello,
Installation of the new image on x96mini is ok.
I am trying to install a Traccar server on this image but it does not work, the Traccar server does not start.
It worked with the old x96mini stretch images.
Anyone know he Traccar, and why he didn't start on this new armbian image?

 

Alex

Link to comment
Share on other sites
NicoD

NicoD

Posted
Posted

This will be it. I'll do all the other boards next week when I find the time. Thank you.
Edit : Doesn't work, I'm trying to find what's wrong. I have no idea. 

This is what I've done to get the u-boot
 

Spoiler 

fdisk -l
--Output "
Disk /dev/mmcblk2: 59.6 GiB, 64021856256 bytes, 125042688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x42bb5020

Device         Boot Start       End   Sectors Size Id Type
/dev/mmcblk2p1       8192 123792255 123784064  59G 83 Linux


Disk /dev/mmcblk1: 7.3 GiB, 7818182656 bytes, 15269888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xa886ce14

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk1p1       8192 15117183 15108992  7.2G 83 Linux


Disk /dev/zram0: 50 MiB, 52428800 bytes, 12800 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram1: 997 MiB, 1045385216 bytes, 255221 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
*
  ---mmcblk2p1 start = 8192 - 1 = 8191

sudo dd if=/dev/mmcblk2 of=u-boot-opi3.img bs=512 count=8191
--Output"
8191+0 records in
8191+0 records out
4193792 bytes (4.2 MB, 4.0 MiB) copied, 0.21479 s, 19.5 MB/s
"

 


I then wrote "Armbian_20.05.0-trunk_Arm-64_bionic_dev_5.6.0-rc2-next-20200220_desktop.img" to an sd-card.
I then did where sdb is the sd-card with the armbian image.
 
  

sudo dd if=u-boot-opi3.img of=/dev/sdb conv=fsync bs=1 count=442

sudo dd if=u-boot-opi3.img of=/dev/sdb conv=fsync bs=512 skip=1 seek=1

 

I adjusted uEnv.txt to point to OPi3.dtb file and activate the correct append for 2GB..
When I insert the sd-card in the OPi3 it boots from eMMC and not from the SD-card.

u-boot-opi3.img

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
13 hours ago, NicoD said:

When I insert the sd-card in the OPi3 it boots from eMMC and not from the SD-card.

 For proper execution, you need to focus on the size of the media. If your SD card is 8Gb and your eMMC is 64GB, you need to use the correct name (SD card) in the copy command.

 

13 hours ago, NicoD said:

Disk /dev/mmcblk1: 7.3 GiB,

 

dd if=/dev/mmcblk1 of=u-boot-opi3.img bs=512 count=8191

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
19 hours ago, noname said:

After I broke my tronsmart, I decided to buy Tanix TX6 (4/64) (I already have orange pi+ 2e and everything works well).

I tried to use the latest image with a new mechanism uboot and device does not boot.

I use windows and rufus. (and u-boot-allwinner-h6-tanix-tx6.img)

I guess that after I write an image with uboot it breaks everything.

Show the full output of "fdisk -l" after writing the image and u-boot. If other systems with the GPT table have previously written to this SD card, all GPT data must be completely erased (including at the end of the media).

Link to comment
Share on other sites
noname

noname

Posted
Posted
20 hours ago, noname said:

Hello,

After I broke my tronsmart, I decided to buy Tanix TX6 (4/64) (I already have orange pi+ 2e and everything works well).

I tried to use the latest image with a new mechanism uboot and device does not boot.

I use windows and rufus. (and u-boot-allwinner-h6-tanix-tx6.img)

Sorry, everything works perfectly (i tried rufus and ImageWriter).

Last time i missed this item

Quote

For the aw H6 platform, all scripts are already in the image (which have the ending aw). You need to rename the files with the replacement (remove the .aw ending).

I run Armbian_20.05.0-trunk_Arm-64_bionic_current_5.5.1_desktop_20200220:
- only 2G ram;

- no wi-fi;

- youtube freezing and throttling (temp 80 deg);

- no poweroff.

 

I want to use tanix as a miniserver and my question is, can I use more memory and can I write armbian to eMMC?

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
30 minutes ago, noname said:

- only 2G ram;

The original (not fake) Tanix TX6 works with 3Gb of RAM (this is the maximum value for the h6 chip). You need to use the APPEND string without a parameter with a 2GB memory limit.

 

33 minutes ago, noname said:

(temp 80 deg);

Improvement of the cooling system is required (I remove the case cover, place the case with the radiator up and add a fan).

 

34 minutes ago, noname said:

can I use more memory and can I write armbian to eMMC?

Yes, this is possible using a script install-aw.sh

But be sure to make a full backup of eMMC with the DDBR utility before installing it

Link to comment
Share on other sites
noname

noname

Posted
Posted
19 hours ago, balbes150 said:

The original (not fake) Tanix TX6 works with 3Gb of RAM (this is the maximum value for the h6 chip). You need to use the APPEND string without a parameter with a 2GB memory limit.

 

Improvement of the cooling system is required (I remove the case cover, place the case with the radiator up and add a fan).

 

Yes, this is possible using a script install-aw.sh

But be sure to make a full backup of eMMC with the DDBR utility before installing it

Thanks, 3Gb of RAM available.

With the transfer to eMMC, I will wait for a stable release. In your opinion, is it possible to use kernel version 5.5?

 

Spoiler

balbes150, Огромное спасибо за вашу работу и ваше потраченное время.

 

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept