Jump to content

jock

Members
  • Posts

    1811
  • Joined

  • Last visited

Everything posted by jock

  1. @EmilB sure you can mix things. On the first kernel upgrade the whole thing will break and the system won't boot anymore. I won't suggest to others doing the same.
  2. Most probably for some reason jumpstart is not getting written on the nand. Clean the NAND and then armbian should boot from sdcard. As said, I updated the instructions to be used with rkflashtool, you can perhaps try with that.
  3. @EmilB No, the upgrade of the loader does not magically gives you the USB boot. I didn't even understand why you had to this loader upgrade, on NAND boards it is not suggested to do. The only thing you should have done (and you have to do right now) is installing the jumpstart thing via multitool, then it should boot armbian/libreelec from both sdcard or USB stick/drive
  4. @dicky soeliantoro follow the instructions, you don't need to change dtb files manually. The approach is radically different: there is a basic device tree installed by default which is very compatible among the various boards then, with the help of rk3318-config script, you can choose your board and apply a device tree overlay which further enables features and compatibility settings with specific boards. Exchanging device trees without consciousness is the proper way to cause unwanted troubles.
  5. Actually H3 are way less troublesome because they boot first from sdcard (rockchip first boot from emmc). People have had quite success in using the Sunvell R69 image for them: https://github.com/armbian/community
  6. @dicky soeliantoro On first page you can find the "Prebuilt images" links. The "archived" ones are quite recent with kernel 6.1.x are good to go with stable kernel. There are also the "nightly stables", which have 6.3.x kernel, which is newer and with more features, but also could be less stable. The choice is yours, it depends on what you want to do with the box.
  7. The reference thread for 322x device is this: anyway, for your specific case, the board is a very old one, in fact it has a much better design and components than newer boards, which have been under a cost cutting over time. You have what it looks like a very accessible serial port (the four holes near the sdcard), so the first step to do debug is getting a TTL-to-USB adapter and logging what happens on the board. Of course armbian does not boot from sdcard: it is done on purpose that way; the installation procedure is described in the post above and the multitool is designed to that exactly that. Also note that the led should be blinking when the multitool boots; also if you don't see anything on screen, you can still access it via network using SSH. Everything is described in the first post of that thread
  8. None, since you say your box has a rk3288 which is not rk3318 nor rk3328
  9. @EmilB from the logs you posted above, I see "Opening loader failed"; did you download the bootloader file in the same directory of the tools? Looking into the rkdeveloptool source code, the error comes out because the file is not found. 🤨 Also to upgrade the loader upgrade_tool is the only one which was reported to be working: rkdeveloptool will tell that everything went fine, but actually won't upgrade anything. The procedure is described in this post, but I guess you already read it. edit: about the hack you had to do to boot the multitool correctly, I don't know where the problem lies. We know that in some cases the multitool does not boot but instead libreelec do. We did some speculation with @ilmich and thought it was some sdcard "power" missing in the multitool device tree, but after doing the changes, it still does not work. edit2: I update the nand bootloader installation process in this post to use rkflashtool in place of rkdeveloptool/upgrade_tool. It is suggested to use that tool and the shipped bootloader binaries which have tested. Also I checked the multitool jumpstart feature with an USB stick right now and it works pretty well.
  10. It is widely known that often they reuse those chips which are not up to the specs. They pick parts from the trash and assemble the tvboxes. Sure you are not the only one, but helping solve the problem without the board in my lab for tests is difficult anyway.
  11. 5v, no less no more. Anything else will probably destroy the board. Unfortunately I don't think you can do anything with maskrom mode; I don't have such a board so I absolutely don't know what is going on with that particular board. All we can do is guessing 🤷‍♂️ rkdeveloptool via maskrom mode if you have a full-image backup, or AndroidTool and the upgrade images for your board you can find on the internet. You have to find the right one though, which can be a time consuming task. Well, tvboxes are not really serious things. If you really need the board to do something minimally serious, it is better to go with a proper SBC and even better a proper SBC officially supported by armbian. if you want to toy around, tvboxes can be funny but beware they are often assembled with scrap parts stick together with hacks, especially the cheapest ones, and supporting them is quite painful.
  12. @Scmel actually it is neither armbian nor homeassistant problem. I mean, armbian community does not have to tell you how to install homeassistant, and homeassistant does not have to tell you how to install it on every platform available on the planet. You have to find the way through, as I said I installed the core version successfully following the instructions on the homeassistant site and it was sufficient to me.
  13. @Scmel Honestly, you should ask on homeassistant forums perhaps, or read the documentation. I have an instance of homeassistant core installed on a rk322x box and works fine, but you have to install it manually by yourself. The other versions may require virtualization or other unsupported/unavailable features.
  14. Hello @guitoscan , two possible issues come up to my mind right now: 1. the system is unstable because some of some wrong cpu/memory setting (voltage too low, frequency too high, things like that) 2. the trust os is doing something bad, and since it is closed source, we could never know what it is doing. To handle the former issue, you can try adding cpu-stability overlay in /boot/armbianEnv.txt adding a line like this: overlays=cpu-stability beware that running rk322x-config will overwrite the overlays line, so you will have to append cpu-stability to the other overlays if you run rk322x-config The latter issue can't be solved easily right now 😕
  15. Yes, then the red and blue leds are alternative and cannot be controlled independently. It is very common. For making them blink on "disk" operations, for which I intend sdcard/emmc IO, you have to echo the right mmc device (mmc0, mmc1 or mmc2 - depending on what you want) to trigger.
  16. @pakos96 https://linuxreviews.org/HOWTO_Control_LED_Lights, in particular the paragraph "Inspecting Your LED Lights" Note that, depending on the board, red and blue leds can be controlled independently or are mutually exclusive (ie: "on" state turns red led on, "off" state turns blue led on)
  17. @spinning banner Yes, it should work that way (except your board has some more other flaws which I'm not aware about...)
  18. @spinning banner Hello! Unfortunately R29 boards seem to have a widely well-known issue with HDMI output, which is not working for some unknown reason. Some research has already been done in the past on device trees, inspecting photos and logs, but still the problem is unknown, as long as I don't have such a board in my lab to really study where the problems are. The S9012P wifi chip also is a no-name chip, as long as I remember it is a chinese chip with no known drivers that "emulates" a realtek chip (not a broadcom one, like those which AP6xxx are based upon), but I can be wrong. @RaptorSDS did some research on that chip, but as far as I know, there is no solution because there is no driver for that (see https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes/page/57/#comment-156548) R29 is a quite weird board actually; despite being very similar to others, has some compatibility issues all-around and it does not surprise me the multitool has troubles with emmc, although it should have none. From the android dmesg I see on android the eMMC runs at 31.25 MHz; Multitool runs it at standard 50 MHz, and that may be the cause of the flash storage issues on multitool. The reason could be a very poor quality board or eMMC, because ALL the boards with eMMC I have ever seen runs the eMMC at 50Mhz perfectly fine and I never had to downclock the eMMC frequency to solve an issue like that.
  19. @olivluca well, it is not totally a stupid idea, but consider that tv boxes are mostly just-for-fun kind of product; I would rather go with a properly supported SBC, or at least a community supported SBC. For example, today I test a Radxa Pi-e board (very small, one gigabit eth, one fast eth, 802.11ac/b/g/n wifi) that turned out being a very impressive throughput of > 100mbps on a 300mbps 802.11n 2.4ghz link, and the access point was one floor above! SImilar results came from an Orange Pi 4 LTS; the tv boxes I tried couldn't reach such bitrate and one of them which had the ssv6051 wifi on board was not even working right. I never tried RaspAp, but looks very good if it does what it promises. But if you want something reliable, go with an SBC + armbian, otherwise find an access point that supports openwrt.
  20. There is no prebuilt image of that kind on purpose: whenever you do an update of the kernel/uboot, it will break the system and it won't boot anymore.
  21. @Anthony Walter The Mali-400 GPU is supported out of the box with recent kernel and distributions. There is already a driver in the kernel, but (I guess) it has to be properly set up in the device tree and in userspace for your particular board. Since your board is not maintained by anyone, support is community based. If someone step out for help good, otherwise you have to do it yourself.
  22. @http418 Still, the necessity of the boot logs are sine-qua-non condition to understand why the board does not boot, otherwise anyone can't be of any help here. To get the boot logs you need the serial adapter and to find the serial pads/pins on your board. Possibly they are below the heatsink, but I have no such board so I don't know. About your board, an R29, the HDMI port is reported to not work and I can't fix that, because - again - I have no such board. Did you try to access via SSH to the board after 5 minutes it booted to see if is working or not?
  23. @sermayoral if you search through this thread, you will see that box vendors are often altering the specs on purpose to fraud people, other time they are just coarse.
  24. @http418 If you don't provide any logs, photos, description of the issue (you were talking about the loader before, now you talk about armbian dtb...) you will be banging the head for yet long time...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines