jock

Members
  • Content Count

    496
  • Joined

  • Last visited

1 Follower

About jock

  • Rank
    Embedded member

Recent Profile Visitors

2105 profile views
  1. I'm aware of the great difference between the two, nonetheless a reported temperature of 70-80°C, if thermal pad/paste is correctly applied and effectively transferring heat, I expect the heatsink to be quite warm, not just mildly warm as usually happens with these chips. Years ago I made a tweak utility for AMD chips for linux and had to read some chapter of the datasheet througly. The reported temperature was taken using a thermistor diode in an arbitrary scale with an arbitrary offset. What worked in way for 90nm chips was not working the same way with 65nm chips and temperature offset
  2. Do this happens only with mainline kernel or also with legacy kernel? I have no real problems running boxes at 70°C, actually I have one which is happily running at 89°C with libreelec, then happens the thermal throttling which keeps frequencies low. As often pointed out also by @fabiobassa, the temperature seems to be erratic because the heatsink is usually just a bit warm while the software reports temperatures that may cause you a burn. From what I learned as an overclocking/downvolting fan in the past, the temperature heavily depends upon the processor production process and
  3. @xwiggen Uhm, I inspected the device tree of the mainline kernel and the only thing that could be interfering is this line: rockchip,default-sample-phase = < 0xb4 >; I made a device tree without that line, you can try to install the mainline kernel and substitute /boot/dtb/rk322x-box.dtb with the one I propose you here. Use it for recent mainline kernels only! If your box works, I will remove that line in the generic setup (which is also useless there BTW, because it should be important only when DDR mode is in use). rk322x-box.dtb
  4. Urgh, that's bad dmesg should tell us something more, if you can upload it here it will be surely useful! Did you have your rootfs on eMMC or sdcard? I'd rather check on my boxes for the same behaviour, looks like something is missing/messing with device trees and mass storage device disappears. TBH, I never tried to upgrade from legacy to mainline via apt-get recently, so I hope there isn't a hole there. Stay tuned, I'll check ASAP. edit: don't you have NAND mass storage, do you? If so everything explains easily since NAND is not supported on mainline beca
  5. Well... it's pretty difficult to say if your board is borked or not, usually backpowering via USB is safe but manufacturers suggest to avoid. Anyway mali blobs have always had a bad reputation, and Mali400/450 drivers are terrible, so it is expected that you get an unresponsive system after some tries, it happened to me too, expecially if you are running thing in X11. NEON code should run pretty fine, didn't try by myself but I don't see a valid reason it should not. Also GBM consumers, like Kodi in fullscreen, should run better and be more stable than X11 applications. Y
  6. Glad you went a step further. This looks definitely a new board I never dealt with. The multitool sources are available on my repository https://github.com/paolosabatino/multitool However if you can boot the multitool from the USB stick you can get a shell and look into dmesg for further details, like for example if the emmc and sdcard are seen by the kernel, it's a starting point to understand why u-boot does not detect the sdcard. You should also be able to interrupt the u-boot bootstrap and use it's interactive shell to get further info about the mmc subsys
  7. Be sure to have armbian-firmware package updated, try to run apt-get dist-upgrade to get all the packages. In case you are holding pack some packages (maybe with armbian-config), unhold them and then upgrade again.
  8. @Alex83 @tediwildan I checked the issue with apt-get upgrade and actually it happens only on NAND boards due to some misbehaving code in armbian. I'm fixing the issue, in the meantime you can plug an sdcard in the sd slot and then run apt-get upgrade: the presence of the sdcard in the slot is sufficient to avoid the issue and the upgrade should install fine.
  9. @the_collector looks quite regular, except for the fact u-boot does not see the sd card at all. Device 0: unknown device message is very suspicious, maybe you get a different board that requires different gpio configuration. Could you provide some details, like a couple of photos, the board name (usually it is printed on the PCB, like R329Q_v3.0 or XT-MX1VR, etc...)
  10. Ah ok, I did not understand you wanted composite tvout; well can't be really helpful here, I never tried it actually. You may take a look to libreelec forum, @knaerzche tested it and it worked on his builds.
  11. Just tested, it worked flawlessy. If you're using from command line you may want to add: defaults.pcm.card 2 defaults.ctl.card 2 to /etc/asound.conf to make the analog the default
  12. Do you mean that you don't see the analog audio output device or the output is going to HDMI by default? Didn't try recently, but all the three audio devices (HDMI, SPDIF and Analog) should be all there. Depending on your application, you may need to change ALSA or Pulseaudio output device. Output of aplay -L and aplay -l can be useful, you may also try alsamixer and see if analog audio is available and unmuted.
  13. Right one! It's the rk3328 that has the USB3 port and two ethernet interfaces, one is gigabit and the other is fast ethernet. Usually on tv-boxes only the fast ethernet is wired in to keep costs down, but you can find SBCs (like the RockPi-E) with both.
  14. Measuring the performance over localhost is a bit pointless. You're measuring how much data the kernel TCP/IP stack is capable of pushing trough: fundamentally, the faster the CPU, the higher the number. Quality and speed of the ethernet interface is totally unrelated to this. That's the opposite: * rk3229 is the "big" brother, * rk3228b is a trust-os stripped down rk3229 * rk3228a is a slower rk3228b (1.2ghz for cores, 400 Mhz for GPU) At least this is what we are guessing, because there is no official documentation about the differences. The att