• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map





Everything posted by technik007_cz

  1. Banana Pi M1+, kernel 4.19.38-sunxi, Debian stretch I needed to get bus i2c-2 working so I went to armbian-config, ticked i2c-2. After reboot I found some information from PMU were missing, some i2c buses were removed and some added. before crw-rw---- 1 root i2c 89, 0 May 26 18:24 /dev/i2c-0 crw-rw---- 1 root i2c 89, 1 May 26 18:24 /dev/i2c-1 after crw-rw---- 1 root i2c 89, 2 Jun 11 10:29 /dev/i2c-2 crw-rw---- 1 root i2c 89, 3 Jun 11 10:29 /dev/i2c-3 crw-rw---- 1 root i2c 89, 4 Jun 11 10:29 /dev/i2c-4 armbianEnv.txt verbosity=0 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun7i-a20 rootdev=UUID=078696dc-d479-4821-8b2f-47fa5c0e05f1 rootfstype=btrfs fdtfile=sun7i-a20-bananapi-m1-plus.dtb extraargs=net.ifnames=0 biosdevname=0 overlays=i2c2 w1-gpio param_w1_pin=PI18 param_w1_pin_int_pullup=1 usbstoragequirks=0x152d:0x1561:u,0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x61b7:u,0x152d:0x9561:u I found i2c-1 changed to i2c-4: before after So I tried "overlays=i2c2 w1-gpio" to "overlays=i2c0 i2c1 i2c2 w1-gpio" in armbianEnv.txt but after another reboot i2c-0 bus was still missing. crw-rw---- 1 root i2c 89, 1 Jun 11 10:58 /dev/i2c-1 crw-rw---- 1 root i2c 89, 2 Jun 11 10:58 /dev/i2c-2 crw-rw---- 1 root i2c 89, 3 Jun 11 10:58 /dev/i2c-3 crw-rw---- 1 root i2c 89, 4 Jun 11 10:58 /dev/i2c-4 Swapping i2c1 and i2c4 in rpimonitor config files is not big problem for me, it takes lest than 1 minute, but with i2c-0 missing I lost access to information what is undefined in the picture bellow and I do not know how can I get i2c-0 and i2c-2 working at once. Note: This device was connected to poor power source, this is reason why USB voltage is low(4.372V) and battery charging was going very slowly (20mA). This was not I believe affecting badly this test :-).
  2. I bought 2pcs of BananaPi M1 Plus and received them about 2 weeks ago. I can't use legacy kernel because I want filesystem with compression support. This requirement matches only btrfs filesystem which is best supported on mainline kernels. Secondly this board supports lipol battery and this was second reason why I bought it. Even it cannot power sata drive while it is only battery powered (not tested on this board but on BananaPi few years ago) it was cheapest option with this feature among all SBC's on the market. Get right gpio pin numbering for my board is horrible experience for me. What I am missing is simple conversion software/script between what provides command cat /sys/kernel/debug/gpio and what is present in file: armbianEnv.txt I found one script but it is one way only. So I stick with with BPI-WiringPi2 => 'gpio readall' table and pin definition found there:
  3. I carry on watching movie so I will be not accessible for change
  4. ... and wifi is not accessible: [ 9.702977] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout [ 9.702998] brcmfmac: brcmf_bus_started: failed: -110 [ 9.703025] brcmfmac: brcmf_attach: dongle is not responding: err=-110 [ 9.719331] brcmfmac: brcmf_sdio_firmware_callback: brcmf_attach failed
  5. And here is output of /sys/kernel/debug/gpio from the "virgin" image: onewire stays on value 271 like @Emil posted
  6. Yes, it was present. (I did not do any edit of that file and that image is about 2 weeks old.) Here is u-boot from image I downloaded few minutes ago. I made only one change, right after rootfstype=ext4 was added to armbianEnv.txt this: It is exactly same like in non working image with latest kernel.
  7. I check our community website, downloaded and flashed latest stretch image for bananapi and during routine upgrade right after logging in and etc I found that image is not latest because it started downloading kernel packages.
  8. I can get this message now but there was second problem maybe related to this, wifi stopped working. There was message in red about it.
  9. Hi @Emil, I can confirm this issue. It did not work either on my BananaPi M1 Plus after kernel upgrade. Problem is it stopped accepting pin value and whatever is in config file output of command below remained after reboot the same: cat /sys/kernel/debug/gpio Fastest solution is to run armbian-config and change kernel to previous version.
  10. Kernel version 4.19.13-sunxi does not accept param_w1_pin= while 4.14.70-sunxi is working. After every change I rebooted system and checked value for change with command below: "cat /sys/kernel/debug/gpio" Testing setup: BananaPi M1 Plus, sensors DS18B20, debian stretch.
  11. Not entire house but hopefully part of room only. However that room needed new painting, floor and furniture, all was in black. The fire brigade believed it was caused by faulty charging device/circuit charging the powerbank.
  12. 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.
  13. 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.
  14. 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.
  15. 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.
  16. 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.
  17. 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.
  18. 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.
  19. I checked graphs "active cooler (ODROID-XU4) VS passive cooler (ODROID-XU4Q)" on 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.
  20. 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.
  21. 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 ) .