• Content Count

  • Joined

  • Last visited

Reputation Activity

  1. Like
    dale reacted to gurzixo in CSC Armbian for RK322X TV Boxes   
    Boa noite KSilva! (I'm French, but I live in Algarve...)
    I was in the same case as you, knew nothing about those boxes and rochchip, but, with the STRONG help of fabiobassa, I have been able to resuscitate a few of thoses boxes, and at least for some of them, able to have a stable Linux.
    A few questions:
    - Are you "fluent" in Linux and windows, do you have a windows system available?
    - Do you have some experience in electronics, microprocessors and microcomputers?
    - Do you have experience with serial connexions?
    My recommendation for you:
    - grab a male-male A-A usb cable, a micro (I mean MICRO) screwdriver, and a high magnification magnifying glass.
    - Open your box, take good quality pictures of both sides of the PCB and  put them on the forum.
    - The 2 next steps are: put the box either in Rockchip (ie. Loader) mode or in Maskrom mode, and try to connect a serial line to the box serial connection (1500000-N-8-1) to get console log, as this helps A LOT. (all cards have 3 or 4 plots for that: Gnd, Tx, Rx, Vcc . We can help you find that on the pictures; you will need a serial adapter, some thin wires that you have usually to solder on some pads and a com program - minicom works very well)
    - After that, you will have to flash some firmware using the USB to USB OTG cable.
    - Even if you prefer Linux (that'salso my case...), I suggest that you use windows for bringing back your box alive, as W tools are A LOT more complete, and also windows emits a sound when a new USB device is recognized, which helps a lot.
    This page explains the boot process.
    You can grab your stock firmware on this page . The archive of firmware contains RKDevelopTool.exe, which is used for flashing firmware.
    You can grab also some more Rockchip tools here
    Here are the main points that I understood:
    - Armbian and Rockchip/android firmwares are RADICALLY different, and their boot process are INCOMPATIBLE. Conceptually, they are similar, but takes very different approaches.
    - Let's detail the RK approach, which is very basic, unsophisticated and pragmatic. The image in flash contains the following elements at FIXED addresses, from bottom to top of flash:
    - A "partition table", (Parameter in RKDevTool) which indicates the addresses of the following blobs (with extension .img)
    - Loader, closed source called after reset by the HW of the processor.
    - The "trusted bloc", closed source, which performs some needed magic... started by the loader
    - The RK uboot, started by the trust module, which is similar to the BIOS for PC, and contains an interactive monitor, that you can start by entering a char on the serial console; otherwise it continues the boot.
    - The Device Tree Block (DTB, called "Resource" in RKDevTool)): this is a binary blob  which contains all the details and parameters of the hardware. it is compiled from source, and is COMPLETELY INCOMPATIBLE with the Armbian DTB. This allows to have a standard kernel, which is the same for all boxes.
    - The Linux kernel, started by the uboot, with a command line indicating where in flash to find the DTB, the Boot partition and the root file system.
    - The Boot partition
    - The Root partition (called "System" in RKDevTool), containing the Linux userland.
    On android, there are other blobs, used for backup and recovery, in case something goes wrong.
    All those blobs are usually packed together by the above RK tools, to create a complete image.
    RKDevtool allows you to flash each of those blobs in a specific place in memory, erase the memory, do some low level tests or flash a complete image.
    I will detail some practical instructions on a next post.
  2. Like
    dale reacted to fabiobassa in CSC Armbian for RK322X TV Boxes   
    since you are able to manage linux and linux command , you can enjoy yourself with a chron command too:
    a simple bash script that in the morning at 8:00 ( or when is usefull for you) does a
    echo default-on ( ot timer or heartbeat or cpu0 ) >>> /sys/class/leds/here_the_name_of_your_led/trigger  
    and the at 20:00 ( or when is usefull for you) does a
    echo none ( ATTENTION: none and default on " could be inverted as logical but you will realize it by yourself ;-) ) >>> /sys/class/leds/put_here_your_led_name/trigger  
    If you are electronic skilled, too, you can even control something with a simple transistor and a relay attached to that led
  3. Like
    dale reacted to jock in CSC Armbian for RK322X TV Boxes   
    Hello, I investigated quite a bit the u-boot issue, but it is not an immediately solvable issue, so it has to wait for the time being.
    About the leds, they can be controlled using the sysfs interface available in /sys/class/leds.
    In particular, you can do cat /sys/class/leds/working/trigger that will tell you a list of acceptable options, and use echo value > /sys/class/leds/working/trigger (change value with something you got from the list) to change the led behaviour.
  4. Like
    dale reacted to fabiobassa in CSC Armbian for RK322X TV Boxes   
    ty so much for sharing your experiments. This helps  @jock and me to better understand behaviour of some boxes that haven't sd card reader , ddr3 and nand.
    The u-boot legacy we realized have some difficult to proper initialize the usb: it's random failure so quite difficult to debug, maybe jock will investigate further or/and rewrite some pieces of code to proper start USB subsystem but this requires it's time. For now we are glad your board is functional

    ty for sharing the dtb and your experiences, too
  5. Like
    dale got a reaction from fabiobassa in CSC Armbian for RK322X TV Boxes   
    Hi @jock,
    Play around with rockchip tv box is always such an interesting thing.
    I tried to boot off usb drive with 3 types of image:
    1) same with image flashed into NAND (buster legacy) --> Armbian could boot from usb drive
    2) focal legacy image --> could not boot armbian just ignored the usb drive and booted right from NAND
    3) Multiboot --> could not boot, armbian just ignored the usb drive and booted right from NAND
  6. Like
    dale reacted to jock in CSC Armbian for RK322X TV Boxes   
    @Seth I will take a look to the dtb, expecially for the led configuration (maybe yours is a special one)
    @dale Congrats, finally you made it! Need to understand why the multitool is not booting although, on my box it boots fine from USB. May I ask what happens exactly when you power on the box with the USB stick into?
    The system hangs and you see a black screen? The led is blinking or is steady on/off? Do armbian boots instead like no USB stick is in the port at all?
    edit: about the temps, yes they are a bit weird. Some chips reports rather high temperatures, I have a board with rk3229 that is idling at 82°C and easily reaches 90°C, but never had any lock-up and the heatspreader is just regularly warm.
  7. Like
    dale reacted to fabiobassa in CSC Armbian for RK322X TV Boxes   
    Glad everything is working . Later personally will investigate vwhy multitool doesn t work as expected 
    And don't forget help good reputation of authors with a simple like, thanks !
    What exactly do you want to achieve now?
    Maybe I missed something
  8. Like
    dale reacted to Seth in CSC Armbian for RK322X TV Boxes   
    congrats for successful setup!
    Anyway, i got a hold of the device tree copy from android as well as dmesg.
    I figured, i'm gonna follow @hexdump's instructions. hope it all works out fine.
    device-tree-copy.tar.gz dmesg_android.txt
  9. Like
    dale reacted to jock in CSC Armbian for RK322X TV Boxes   
    @dale Definitely the Multitool was not behaving correctly when used from USB - I was pretty sure someone else in the past used it successfully, but probably he/she made some modifications to let it boot and work correctly.
    Anyway I have uploaded a new fixed version of the Multitool. Download it again from the first page.
    Follow the instructions to install into NAND you find in the first page, of course burn the Multitool on the USB stick, then boot with the USB stick in the USB OTG port of the box and let's see if it finally works!
    PS: if the Multitool still refuses to load, follow the suggestion to burn the Armbian legacy image directly on the USB stick and let's see if it at least works (BTW it should work, it has been tested in the past)
  10. Like
    dale reacted to fabiobassa in CSC Armbian for RK322X TV Boxes   

    hello dale, would you try this loader and give us feedback , please