Rajesh

Members
  • Content Count

    35
  • Joined

  • Last visited

About Rajesh

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am unable to locate gx_sound.sh in /root folder on the image I am burning on sd card. Is there any other location I can get copy of this script? Thanks -R
  2. Thank you for the inputs. I wish I could get some debug output, but box does not have a UART debug pins and I do not wish to mess with soldering etc as I have just borrowed it for testing. I created a disk image of sd card (the one with working image for T95U pro) using dd on an Ubuntu system, copied it to a USB and then tried to move that image to eMMC/NAND (whatever it is) using dd if=/mnt/sd.img of=/dev/mmcblk1 bs=1M status=progress. Unfortunately this did not help. --Rajesh
  3. Thought I should just close the loop on this one. I tried this image on another Arm64 box 'Tanix TX3 mini' and it works like charm. I was able to move the image to eMMC using install-aml.sh. T95U Pro could possibly have some issue and needs further investigations. @balbes150 If this has NAND and not eMMC, is there a workaround to create new partitions on the device. Thank you very much for useful tips. --Rajesh
  4. The TV Box specs mentions: I am able to restore the stock Android image 'T95U Pro 7.1.1 V1012 AP6522' using Amlogic USB Burning tool so I presume 'eMMC content replacement protection firmware' may not be the case in this instance. I tried to change these commands in install-aml.sh as: echo "Start restore u-boot" dd if=/root/u-boot-default-aml.img of="${DEV_EMMC}" conv=fsync bs=1 count=446 dd if=/root/u-boot-default-aml.img of="${DEV_EMMC}" conv=fsync bs=512 skip=1 seek=1 Changed 442 to 446 and now I am not able to even see the device listed: Should I be looking at some other scripts boot.cmd etc? Thanks Rajesh
  5. Has anyone been able to run any of the images from eMMC on a S912 device? My device is T95U Pro running buster desktop from image Armbian_20.08.0_Arm-64_buster_current_5.7.0-rc7_desktop_20200531.img The image works perfectly well from SD card. I am unable to setup eMMC to run this image using install-aml.sh. I also noticed the partition table on the SD card and location specified in the script install-aml.sh are different. install-aml.sh When the script is run I can see only two partitions on /dev/mmcblk1. After rebooting the device, all previous partition of Android stock image gets restored. Am I missing something here? Thank you for your help! -R
  6. Tanix TX6 which I think is of type 6Xa has firmware download available here http://www.tanix-box.com/downloads/ -R
  7. TX6a is I believe 4 GM RAM / 32 GB eMMC. Well if you are able to boot and bring up the OS then it could be something else and not the DTB file. This is the dts file from @jernej https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/allwinner/sun50i-h6-tanix-tx6.dts You can convert it to dtb and give it a try. If you have issues with your stock firmware also then it might be something to do with the box. --R
  8. There are several variant of Tanix TX6 models listed here https://linux-sunxi.org/Tanix_TX6 and they mostly differ in RAM and eMMC sizes. There is reference to single dtb file there sun50i-h6-tanix-tx6.dtb for all these models. Will this dtb file work with all the models with the Single Armbian Image for RK+AML+AW (aarch64 ARMv8)? If not what changes would be needed in dtb files for these models? Thanks Rajesh
  9. Resolved: I added this code in boot.cmd and did 'mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr' The boot logo is now shown when I boot from splash also. Hope this help to anyone facing similar issue. -Rajesh
  10. There was this patch introduced when HDMI driver was added - sunxi-boot-splash.patch: It appears that this patch always looks for boot.bmp in mmc 0. Probably this is why the boot.bmp is displayed only when I boot from SD card. When I boot from onboard eMMC, mmc device number is 2 and not 0. I will try to load bitmap in boot.cmd and see if this makes the difference. --Rajesh
  11. I am trying to make sense of all of this but it is getting more complicated for me. I read this message on the forum which includes you comments but appears beyond my capability to deal with this. If you can give me little more pointers on how to deal with this, I will try to give my best. Best Regards Rajesh
  12. These are the initial boot messages I see while booting from onboard eMMC vs SD Card Onboard eMMC: SD Card / Show Logo: Does this ring any bells? --Rajesh
  13. logo=enabled does not help. I am aware about logo being disabled for HDMI Patch. I applied these patches to 20.08-trunk to get the logo enabled 1. disable patch xxx-disable-de2-to-improve-edid-detection.patch 2. enable patch remove-boot-messages-from-hdmi.patch I works for 20.08-trunk but only on SD Card. Flash the image on eMMC and the boot logo disappears. I did armbianmonitor -u after boot from SD Card for comparison ( http://ix.io/2omV ) and compared the two logs. They are absolutely same until about 6 seconds when the kernel starts to load. --Rajesh
  14. Current 5.4.x. I think it was 5.4.43 / 5.4.44. --Rajesh
  15. Armbianmonitor log: http://ix.io/2omP --Rajesh