Jump to content

rafaelSorel

Members
  • Posts

    46
  • Joined

  • Last visited

Posts posted by rafaelSorel

  1. Hello, 

     

    I have bought an x96mini with a uboot version from 03/2019, everythings works perfectly when booting from SD, but when I try to boot from internal the kernel boots and it stops at "waiting for root device", after an investigation I have noticed that the partitions layout is different from the standard one, I have updated the dtb to be inline with that layout but the problem remains the same, unable to boot from internal.

     

    Here is the original dts file from that box, 

     

    Any help would be appreciated, knowing that I am using the kernel version 3.14.

     

    Thanks,

    01_dtbdump_Amlogic.dts

  2. 5 hours ago, rafaelSorel said:

     

    The second thing is since I want to update the boot screen logo, I managed to extract the bootup.bmp from logo.img partition using this script https://github.com/steeve/aml-imgpack

    then I have repacked a new logo.img with the changed bootup.img file using the same script. 

    so is it possible to update the logo.img using this command: "dd if=logo.img of=/dev/logo bs=32M" ?

    [Update] I manage to change the bootup logo successfully, basically we need to unpack the logo.img and change the bootup.bmp with the wanted one, the format needs to be (16bit RGB565 BMP)

  3. @balbes150: I have checked the u-boot help command line and I could see the sdc_update command. So basically it is possible to update the bootloader from u-boot command line.

    My question is :

    What is the best way to flash a new u-boot on emmc  (sdc_update from u-boot console or running dd if=u-boot.bin of=/dev/bootloader from running linux on SD card) ?

     

    The second thing is since I want to update the boot screen logo, I managed to extract the bootup.bmp from logo.img partition using this script https://github.com/steeve/aml-imgpack

    then I have repacked a new logo.img with the changed bootup.img file using the same script. 

    so is it possible to update the logo.img using this command: "dd if=logo.img of=/dev/logo bs=32M" ?

     

    Thanks,

  4. Well it was a connector issue, I have changed connector and it worked like a charm, I have tested the device connector on S905, S905X and S905W with a success.

     

    This is good news because we don't need anymore to weld any thing on the board to get a serial output, we could even setenv on u-boot without booting on android or even root it.

     

    For those who are interested here is the link from where I have ordered the devices:

    Micro-SD-Card-Breakout-for-Exporting-UART-and-JTAG

     

    Have a nice uarting :)

  5. Hello Guys , 

     

    I have ordered Micro SD Card Breakout for Exporting UART and JTAG Pins to get serial output on the SD card port without making any welding on the box.

    I have test it and it seems to work. The problem is that the output is some king of unreadable characters.

     

    I don't know whether it is a config issue or something else ?

     

    Does any one have used the UART over SD port ?

     

    Thanks,

  6. I have found the issue, indeed the server packages does not contain pulseaudio and it seems that the alsa config files are not well configured to handle the volume control. I have installed and configured the pulse along with alsa config files and now I can perfectly control volume on all outputs (analog, hdmi, spdif.)

  7. Hello, 

     

    I am trying to control volume Up/Down and mute through alsamixer with no success.

    When launching alsamixer the only changable device is DAC Digital, but actually it does not change anything, the volume remains at "56" and won't change.

    It is almost not possible to control volume through alsamixer or amixer command line. The only control I have found is the mute/unmute through /sys/class/amaudio but not the volume level !

     

    It is the case for all armbian (debian, ubuntu) servers packages.

     

    I think some thing goes wrong...

     

    Any help or hint would be appreciated.

     

    Thanks 

  8. Typically most of the android boxes contains 1/8" coaxial spdif. So if your AV receiver (home theater) doesn't have a coaxial spdif input, you need to convert it to optical spdif. So you gonna need a cable like this: 

    https://www.amazon.com/Micca-Premium-SPDIF-Digital-Coaxial/dp/B00V436UQU

     

    and to convert it to optical output something like this:

    https://www.ramelectronics.net/pof-820-1.aspx

     

     

    I know it is a hell of devices but this is the only way to get your optical output.

    But check may be your home theater has a coaxial spdif input and you are only going to need the first cable.

  9. Hello, 

     

    Have you made a backup of your android image from emmc before ?

     

    I have got a same situation and I backup the emmc from running linux from SD card, so basically you need to bootup on linux from SD card then reflash the emmc using ddbr_restore script. may be uboot could not init emmc , but linux does.

     

     

  10. 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 ?

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines