Jump to content

SteeMan

Moderators
  • Posts

    1425
  • Joined

  • Last visited

Posts posted by SteeMan

  1. 1 hour ago, SteeMan said:

    I have needed to try different versions of usb burning tool for different boxes.  Tried different usb ports (generally only one usb port will work with the tool), And sometimes need to press the reset button for different lengths of time to get it to register.

    Have you tried all of these things I have recommended?  What different versions of usb burning tool have you tried?

  2. Here are the reasons to run off of emmc:

    emmc is faster than SD

    emmc is more durable than SD.  Both emmc and SD have limited lifes due to the number of write cycles they support.  But emmc should last longer than SD before wearing out

     

    Reasons to stay with SD:

    The ability to pop out the SD card and replace it with another or to move it to another device to read/write the contents is sometimes very useful

    SD cards can give you more storage than the onboard emmc

  3. The uboot has nothing to do with the Amlogic burning tool, the tool connects before uboot starts.  I have needed to try different versions of usb burning tool for different boxes.  Tried different usb ports (generally only one usb port will work with the tool), And sometimes need to press the reset button for different lengths of time to get it to register.

  4. So I guess getting back to your original question:

     

    On 1/31/2024 at 4:56 PM, Pszemek said:

    Is there any way to restore original firmware?

    Did you make a backup of the EMMC before you overwrote it?

    Do you have an original android firmware for your box?

    Yes you can restore the box, but how you do that depends on what you are restoring from.

  5. Interesting.  I didn't know that existed.  It must be a wrapper for the functionality available through armbian-config (or vise-versa).  Either way the standard Armbian functionality doesn't work with the amlogic TV box builds and will not leave you with a working EMMC install.  That is why the amlogic TV box install instructions give the correct alternative.

     

    Regardless of that, your logs show that you are booting from sd card.  And the state of your EMMC shouldn't cause the type of error you are seeing.  

  6. I think your real question is why hasn't Rockchip put in the effort to get these drivers into mainline linux?  It isn't the goal of Armbian to be the repository of large amounts of unmaintained code.  The goal is really to bring mainline linux to devices.  But that assumes that everyone else is working to bring various bits and pieces from custom linux forks to mainline linux.  While sometimes it is necessary to temporarily host code that has been ported to mainline, but not yet incorporated upstream, most of the efforts should be to get the code into upstream mainline linux.

     

  7. It reports it is full, probably because it is full.  The last set of commands @going suggested you run are to try to figure out what has filled up the storage.  du -s  will be your tool in looking as where the storage is being used.  Google for how others use this command for this purpose.

  8. It looks like that box is using an amlogic s805 cpu (which is a very old 32 bit cpu). The amlogic s905 was their move to 64 bit cpu.

    There isn't any currently active work that I am aware of to support this cpu anytime recently.

     

    There is a very old thread dedicated to this cpu:

     

  9. 31 minutes ago, Victorhtf said:

    EDIT: After post my reply I tried to use the exactly same DTB as you said. And it worked.

    The reason this would work is that you really have a s905L2 cpu.  This wouldn't be the first time that a TV Box vendor and/or parts supplier changed the markings on a chip to give the impression it is something else.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines