technik007_cz

Members
  • Content Count

    148
  • Joined

  • Last visited

About technik007_cz

  • Rank
    Elite member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

572 profile views
  1. technik007_cz

    Odroid XU4: critical temperature reached(228 C)

    This is (probably) last comment because all these boards (XU4) have been damaged during fire in my room. Fortunately that fire was extinguished quickly and I only lost some electronics. What I found out XU4 and HC1 cannot run ffmpeg on maximum cpu frequency 2Ghz, maximum stable frequency is 1,6Ghz and must be limited by cpufrequtils settings in /etc/default/cpufrequtils file otherwise unexpected shutdown occured. I am not going to replace these XU4 boards from this reason, keeping only 2x Orange Pi PC, Orange Pi PC plus, Olimex Micro and four Nanopi2. This is not only one reason, secondly it is very high current demanding board (4A or 6A) causing voltage drops, and therefore sata errors due to bus resets. I have never had these issues with Orange Pi PC boards family or Olimex Micro and I feel happy what community have done to support these.
  2. technik007_cz

    Odroid XU4: critical temperature reached(228 C)

    Both boards are doing well. Each board unexpectedly turned off only once in 3 week period. It reminds me fighting with Odroid U3 even I have not experienced same with Odroid HC1 board and I run six of them in past. Perhaps combination of different heatsink/cpu throtling is behind, I do not know. But XU4/HC1/U3 performance is still above everything I know in low powered boards world and this is reason why I will not give up.
  3. technik007_cz

    Odroid XU4: critical temperature reached(228 C)

    This was result of testing different version of kernel which has been replaced same day and problems had not gone. I think I tested all kernels and no improve. I run those 2 boards for few days without stability issues after: setting memory frequency to lowest value found in boot.ini which is 633Mhz limiting max cpufrequency for LITTLE cores 1200Mhz and for big cores 1600Mhz (thanks @rooted) AND these boards run with all 8 cores turned on Note: First board reports temperatures correctly but second one still reports high temperatures 85-100C, more likely 100C, what put frequency of big cores down to range 1000-600Mhz. I gonna test higher memory frequencies.
  4. technik007_cz

    Odroid XU4: critical temperature reached(228 C)

    I think this is hardware failure because I put silver thermal compound between SoC and heatsink. I found way how to run this board. I simply wrote script which shutdowns cores 3 and 4 ( one LITTLE and one big ) during boot. Performance penalty is about 25% percent but the board run 2 days without overheating shutdown occurred and this is big, very big step forward. What I learnt this board does not like Ubuntu Bionic and hate Ubuntu Bionic with btrfs filesystem. (I used working system successfully from second board having no issues running next and powered by same step-down converter to exclude microSD card or power supply issues). This is because Bionic from some reason asking for more processing power and it triggered overheating protection. What does work is Ubuntu Xenial and cores 3 and 4 off. I had plugged in USB meter during tests showing board's actual voltage and having low voltage acoustic signalization which has helped me many times to detect undervoltage conditions.
  5. technik007_cz

    Odroid XU4: critical temperature reached(228 C)

    You can see temperature drop on previous 2 images where temperature dropped to -27°C. What is situation now showing next picture. Maximum clock available is limited to 1300Mhz for LITTLE cores and 1900Mhz for big ones. Why clock dropped to 600Mhz for these? There is script running on the background throttling frequency when temperature is higher than 80 °C. I am waiting until job on this machine is finished and then I will reboot it and try another tests/tasks.
  6. technik007_cz

    Odroid XU4: critical temperature reached(228 C)

    I have not experienced any problems with high temperatures causing shutdowns since Monday. Only one thing I needed to do was clone system again because one board did not allow me to log in. However I am experiencing false temperature readings since Wednesday. I got 87°C on zone 0 and 1 and it stopped updating until I rebooted board. ( This is second time I have seen this, but on Home Cloud One with same SoC). And I got temperature below zero, yes it is true, -27°C on zone 0 and I am having now 91°C even there is less than 60°C on other zones 1-4 what is very weird.
  7. technik007_cz

    Odroid XU4: critical temperature reached(228 C)

    It is still too early to confirm what issue was behind the problem. But you will not believe I think there were network problems I found which could keep overloading this devices. And NanoPi M3 stopped hanging up or lagging when I was on terminal after this. I need more than 24 hours to confirm this.
  8. technik007_cz

    Odroid XU4: critical temperature reached(228 C)

    I checked graphs "active cooler (ODROID-XU4) VS passive cooler (ODROID-XU4Q)" on www.hardkernel.com. You are right @TonyMac32, it is in couple of seconds before SoC temperature starts hitting a roof, not miliseconds. Because there is still little possibility the heatsing is not attached right (hardkernel's decided to put SoC not to the middle of heatsink), it is not clear is this software or hardware issue.
  9. technik007_cz

    Odroid XU4: critical temperature reached(228 C)

    And what about if this temperature spike above this limit is reached for couple of ms during heavy load? What could I test is better cooling block/heatsink with better absorption capability but I have no idea where can I get better one. I made USB to 3pin fan adapter with inserted step up converter boosting 5V to 12V. And has started testing again.
  10. technik007_cz

    Odroid XU4: critical temperature reached(228 C)

    Maybe it's incorrect but it shutdowns board anyway. Secondly why only one board having this issues even system is cloned and these are connected to same power rail ( rated 5V 10A ) .
  11. Hi, I received 2 same boards recently. One is working great, second has suffered from unexpected shutdowns. Rpimonitor has not recorded this high temperatures yet, maximum temperature recorded is not more than 90C. SoC has been utilized on 100% with ffmpeg video conversion and other tasks. I run these board on Jessie or Bionic system and have tested mainline stable and beta kernel. These board have got passive heatsink however I put 80x80 quiet slower fan on the top of heatsink, thermal compound is replaced for silver one without making problem solved.
  12. technik007_cz

    [WiP] axp209 mainline sysfs interface

    What is strange that script reports if dc in is NOT present: Battery discharge current = 0mA Battery charge current = XXXmA Secondly BOINC manager do not register system is running on battery.
  13. technik007_cz

    [WiP] axp209 mainline sysfs interface

    I checked the datasheet and not register 0x34 but 0x33 is responsible for charging current. However it has been already set to maximum value 1200mAh. To get status of register I run command i2cget -y -f 0 0x34 0x33. Because the value 1001 for bit 0-3 has been reported back, there was nothing to adjust to get higher charging current. binary 1001 => decimal 9, 9*100mAh + 300mAh=1200mAh I found useful script, see link below, reporting charging values and status of both registers 0x33 and 0x34 (default values: 0xCX and 0x45). https://gist.github.com/tstellanova/b726545cc9bd2a01bb553f34509a5c96
  14. technik007_cz

    [WiP] axp209 mainline sysfs interface

    I have got Lime connected on big battery pack. Therefore charging takes long time. Do you have an idea how to increase charging current on 4.X kernel ?