rafaelSorel

Members
  • Content count

    28
  • Joined

  • Last visited

  1. Strange behaviour after installing linux on emmc.

    That is what I did, I have created a new dtb file based on the default one present in the emmc, but with minor changes , and when I flash it dd if=./new_dtb.img of=/dev/dtb bs=256k with the new created one and reboot, the system is always using the old one present in the emmc !
  2. Strange behaviour after installing linux on emmc.

    Thanks for reply, What do you mean by correct option dtb proper ID ? Is it something that I can do ? Thanks,
  3. Strange behaviour after installing linux on emmc.

    @balbes150 Here is attached the serial output of the tvbox. Thanks for help console.log
  4. Strange behaviour after installing linux on emmc.

    Ok , I will manage to get the UART output , need to make the UART output on the board.
  5. Strange behaviour after installing linux on emmc.

    No not yet , is it possible to do so via serial console ? because via this command : dd if=./dtb.img of=/dev/dtb bs=256k it does not work !
  6. Strange behaviour after installing linux on emmc.

    Thanks balbes150 for your reply. Yes but I have validate the fact that the dtb used in SD is the suitable one. I want to know Why when booting linux from eMMC it uses different dtb and how to change this dtb ? despite the fact that it is an Amlogic s905W, it works perfectly.
  7. Strange behaviour after installing linux on emmc.

    I succeded to generate a dtb.img in android format (linux kernel header + dtb.img), The problem comes when I try to update the dtb using this command from LE running on SD or eMMC dd if=./dtb.img of=/dev/dtb bs=256k After rebooting the old dtb is always used !! it seems that u-boot is generating another dtb file and never taking the one that I have flashed on /dev/dtb !!! Any idea on how to resolve this dtb emmc issue ?
  8. Strange behaviour after installing linux on emmc.

    [Update] I manage to make linux booting from the eMMC, it seems that the boot.img needs to be the same one recovered from android firmware. If we put anther one, the linux one it will ends up onto the recovery screen. [nextstep]: How to change the dtb file to be in sync with the one used on the SD card ? knowing that in andoird the dtb.img file is concatenated with some linux kernel header. any ideas ? Thanks
  9. Strange behaviour after installing linux on emmc.

    [Update] I have backup the android firmware from another mxq box and restore the one that ends up onto the recovery screen, but when I try to install the firmware into the emmc using one of the two scripts (install.sh or nand_sata_install), I always ends up into the recovery screen. Here attached the recovery screen. I don't know why I cannot copy LE from SD to eMMC ? Thanks for your help,
  10. Strange behaviour after installing linux on emmc.

    Yes that is my thoughts also, may be we are gona need help from @balbes150 ? to give us some hints about this ? [Update] It seems that the copy to internal memory that I have done is from armbian-config tools/system/Install to nand, emmc, sata by doing this I could start linux with the mentionned problem of chnaged dtb file. But when running ./install.sh which is suppose to be the same thing I ends up into the android recovery screen. So basically the two methods are not the same : 1- The first one (armbian-config install to nand, emmc) just generate a new dtb file based on the dtb file present on the /boot partition, but really a different dtb file from the sd /boot partion. 2- The second method which is the execution of the ./install.sh script make an exact verbatim copy to the emmc which ends up into recovery android mode.
  11. Strange behaviour after installing linux on emmc.

    Yes that is my thoughts also, may be we are gona need help from @balbes150 ? to give us some hints about this ?
  12. Strange behaviour after installing linux on emmc.

    Well actually it's name is install.sh and here is the attached script. install.sh
  13. Strange behaviour after installing linux on emmc.

    Thanks for help but this is not my problem. I want to know why when I have executed the ./linux.sh to copy linux to internal emmc, it does not use the same dtb.img file that is in /boot partition of the SD file, but it generates new one.
  14. Strange behaviour after installing linux on emmc.

    No the mxq_SD.dts is a decompiled gxbb_p200.dtb generic file that we could find in the /boot/dtb/ folder . And the mxq_emmc.dts is a decompiled dtb file from emmc after I have run the ./install.sh script. It is a standard armbian server img with kernel version 3.14
  15. Strange behaviour after installing linux on emmc.

    My box is 1G ram I am not sure about the p200 or p201 but you can check the mxq_SD.dts that I have attached with minor changes that I made to load some other drivers. My problem is coming from the one in the emmc. I don't know how it is autogenerated ? And how to edit/fix it ?