• Content count

  • Joined

  • Last visited

About technik007_cz

  • Rank
    Elite member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

379 profile views
  1. [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.
  2. [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).
  3. [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 ?
  4. Orange Pi One USB-OTG

    Very good effort mate, I followed your instructions and successfully changed OTG port to host mode on my A20 lime board. It was really necessary for me because this board has got only 2 USB ports. Just only for record I did it on kernel version 4.14.15-sunxi and it was really hard to find complete instructions.
  5. It would be nice to get working a second ESP8266 with a display connected to and redirect temperature and humidity data to this.
  6. Award for implementing Banana Pi M3 into armbian

    Do you want to support so overpriced product? Board you bought for about £60 should be selling for £20 with software support you can get now.
  7. NFS boot stopped (legacy kernel, Orange Pi Zero )

    Version ? 5.27 build from sources on about 3rd of April.
  8. NFS boot stopped (legacy kernel, Orange Pi Zero )

    I have sorted out nfs booting problem differently using older image couple of weeks ago. But I had same screen on my Orange Pi 2 mini when I watched booting on serial console. I changed settings in /boot/boot.cmd to "console=ttyS0,115200" (without quotes) from "console=tty1" and it solved problem when booting stopped on "ion_reserve_common ... Probably booting did not stopped like I thought. Probably just only output of serial console was silent.
  9. SD card from ancient times

    @tkaiser I tested 10pcs of 128MB sized and there is result. I needed insert card in and just only press enter in opened terminal screen (with command ready like badblocks -wsv /dev/mmcblk0), replace card and press again until no more cards left. Badblocks found 5 cards with errors and i decided just for case test good ones with f3. I must mount card, change directory, write test data, unmount, unplug it, plug it again. (I tried test on cards marked bad by badblocks and sometimes it did not find error without replugging it !!!) and make same procedure .. mount card, change directory and run reading test of previously data. And result of f3 test on "badblocks" cards marked ok? F3 did not find any error. Sorry F3 is not user friendly and I am definitely staying with "badblocks -wsv" which is easier to operate for me.
  10. SD card from ancient times

    I run test on debian distro at this moment. (I can switch on windows but only if it is question of life or die). Thank you for keeping me updated I gonna try f3.
  11. SD card from ancient times

    I needed small sized cards for nfs boot. I ordered 10pcs of them on Aliexpress and received exactly same ones (Nokia 128MB) probably ripped off old phones :-). 1 could not initialize but rest of them passed badblock test (I received refund for bad piece without any problem). Than I ordered cheaper ones, 10 pcs again. I got new cards with orange/white colour. 1 could not innitialize => rubbish 2 did not pass test in external but passed test in internal reader => ??rubbish 2 did not pass neither in external or internal reader => rubbish So keep this card :-) it still has value.
  12. NFS boot stopped (legacy kernel, Orange Pi Zero )

    Another question which can help me to build working system. What should I change to build previous release of system? For example latest release is 5.27 and I want 5.26...
  13. Hi guys, do you have idea why boot stopped? Check log below please. It was build about 25minutes ago but about 1 week younger build was working. U-Boot SPL 2017.03-armbian (Apr 03 2017 - 19:48:42) DRAM: 256 MiB Trying to boot from MMC1 U-Boot 2017.03-armbian (Apr 03 2017 - 19:48:42 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Zero DRAM: 256 MiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment Setting up a 720x576i composite-pal console (overscan 32x20) Error: no valid bmp image at 66000000 In: serial Out: vga Err: vga Net: phy interface0 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 ** File not found /boot/boot.bmp ** 38518 bytes read in 114 ms (329.1 KiB/s) switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 1879 bytes read in 153 ms (11.7 KiB/s) ## Executing script at 43100000 ** File not found .next ** ** Unrecognized filesystem type ** 35384 bytes read in 453 ms (76.2 KiB/s) 4771976 bytes read in 824 ms (5.5 MiB/s) 3548294 bytes read in 658 ms (5.1 MiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3548230 Bytes = 3.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Ramdisk to 49bd2000, end 49f34446 ... OK Starting kernel ... [sun8i_fixup]: From boot, get meminfo: Start: 0x40000000 Size: 256MB ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1 ion_reserve_select: ion chipid [0x2c00042! ion_reserve_common: ion reserve: [0x47e00000, 0x50000000]!
  14. This is second afternoon I spend trying configure wifi on headless orange pi because we started using nmtui-connect (editing /etc/network/interfaces was much more easier especially when I need make universal image for about 15 same boards). It found wifi but when I try enter password it instead shows message "Could not activate connection: No plugin │ │ │ │ supported adding this connection" I can select which wifi I want but It everytime ends with same message. I tried it on image Armbian_5.25_Orangepizero_Debian_jessie_default_3.4.113.img I made no changes on this image except changing root password. User creation I canceled.
  15. no space in /armbian/output/cache/

    Thank you for your help @zador.blood.stained This case is closed for me ;-).