technik007_cz

Members
  • Content Count

    160
  • Joined

  • Last visited

About technik007_cz

  • Rank
    Elite member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

717 profile views
  1. technik007_cz

    One wire DS18B20 on 4.19.13-sunxi

    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: https://bananapi.gitbooks.io/bpi-m1-bpi-m1-plus-/content/zh/bpi-m1+_gpio_pin_define.html
  2. technik007_cz

    One wire DS18B20 on 4.19.13-sunxi

    I carry on watching movie so I will be not accessible for change
  3. technik007_cz

    One wire DS18B20 on 4.19.13-sunxi

    ... 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
  4. technik007_cz

    One wire DS18B20 on 4.19.13-sunxi

    And here is output of /sys/kernel/debug/gpio from the "virgin" image: onewire stays on value 271 like @Emil posted
  5. technik007_cz

    One wire DS18B20 on 4.19.13-sunxi

    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.
  6. technik007_cz

    One wire DS18B20 on 4.19.13-sunxi

    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.
  7. technik007_cz

    One wire DS18B20 on 4.19.13-sunxi

    My output seems to be shorter:
  8. technik007_cz

    One wire DS18B20 on 4.19.13-sunxi

    @martinayotte This dmesg output:
  9. technik007_cz

    One wire DS18B20 on 4.19.13-sunxi

    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.
  10. technik007_cz

    One wire DS18B20 on 4.19.13-sunxi

    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.
  11. technik007_cz

    testers wanted Testers wanted: sunxi Device Tree overlays

    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.
  12. technik007_cz

    Odroid XU4: critical temperature reached(228 C)

    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.
  13. 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.
  14. 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.
  15. 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.