• Posts

  • Joined

  • Last visited

 Content Type 


Member Map




Everything posted by rodolfo

  1. Simply connecting and doing nothing via g_ether adds virtually nothing to total consumption ( ~ .4 W ). Using the connection running iperf ( at 102 mbps and 92/28mbps since PIZERO uses no hub ) on both boards adds .4 W with actual usage of the board ( the luxury non-null use case ). Using a PIZERO as a "slave" hooked up to an OPI ONE/LITE/PC might be interesting in cases where there exist viable solutions (GPIO/SPI..) for RASPI not yet ported to Armbian. OPI ONE/LITE/PC with superior processing power and connectivity would serve as gateway, logger, number cruncher ... While lowest possible consumption is of rather limited value, lowest practical consumption for H3-boards ( clever fex and userspace settings for the main power hogs and boosting performance under user control ) is of great value specially in battery-operated/buffered environments.
  2. All batteries degenerate. "Passthrough" is somewhat misleading, "battery buffering" would be a better description of what really happens. Surprisingly enough, the method outlined actually works and that's all I care about. Good luck.
  3. Just keep it simple. You do not need an "expensive UPS" or large power bank to keep a simple tinkerboard ( no insult intended, tinkering IS engineering ) running.for a couple hours without any charger power. A "power bank" is just batteries combined with charging/discharging circuitry. Charging/discharging are mutually exclusive unless you pay extra for "passthrough charging". Just use two regular power banks and hook them together on the battery side ( + to + / - to - ). You can now charge the double-pack power bank through one circuit and draw power from the other. Unplug charger and it still runs for a couple hours, replug and reload the batteries. Viability of this approach depends largely on connected peripherals as current is limited by max.charging/discharging capability of the power bank circuitry. Powering disks ( peak >1A draw ) is not reconmmended, but OPI ONE/LITE with wifi and USB storage have been running fine for weeks with random plugging/unplugging of power supply. Presently I'm successfully using VERY cheap power banks and run them in parallel when needing more juice. The fancy luxury version of this poor man's UPS would sense charging power via GPIO pin and use some program logic to gracefully shut down the board after extended power-out (some hours).
  4. This one works for OPI and RASPI :
  5. I do not consider myself an expert ( ex-spurt ) at all. I just like to learn and as an engineer I'm too lazy to not pick the low-hanging fruit. Keep it simple and try to follow advice from others who have successfully managed to make things go right. Best of luck !
  6. By using g_ether instead of g_serial ( same method as described ) one gets a fast ethernet connection ( usb0 ). With static IPs and routing defined for the PIZERO and the host ( Armbian board, Linux/OSX notebook ) one gains easy network access for any updates/upgrades on the PIZERO. If you really need the early boot messages on the PIZERO, a serial console cable on the GPIO pins can still be used to power/connect the PIZERO.
  7. The reboot command on OPI ONE is pretty useless as USB peripherals keep being powered and no actual reset happens. Power down system, disconnect power for at least 20s and restart. The "power button" can be defined in software to power down the OPI, but not to start it.
  8. Ora et labora ( and some minor fun in-between ) ....
  9. Image 1MB of the old SDcard to the new SDcard. This contains the loader. On Linux as root : stick in old SDcard, check device with lsblk ( e.g. /dev/sdb ) dd if=/dev/sdb of=loader.img bs=1M count=1 eject sdcard, stick in new SDcard, check device with lsblk ( e.g. /dev/sdb ) dd if=loader.img of=/dev/sdb
  10. @tmp Armbian probably is the "classic Debian" for your board. Once you figured out the differences between the "classic Debian" ( I assume you refer to an arm distribution ) and Armbian, you'd probably start reinventing Armbian. Save yourself the travail and find out how to run Armbian with an encrypted rootfs.
  11. Open source was a marketing gag by IBM trying to usurp the professional work of the free software world. The Armbian team does a stellar professional job to convert some random heaps of assorted hardware into useful working systems. There is a lot of dedication, pride and hard work to put some basic sanity into this tinker world. True FREEDOM in software is complete CONTROL. Don't blame professionals for doing their job. Feel free to run your car off the cliff.
  12. Idle consumption is just perfect for the null use case RasPI Zero/ A+ are great as low power IoT gateways for sub-Arduino ATTINYs operating on watchdog. Higher up in the food chain OPIs deliver all the Linux fun at reasonable consumption. "Power on demand" for OPIs, idling at very low power and bursting to full blast when actually needed, is a very interesting strategy when running the boards from batteries. Thank you for the hints .
  13. I've tested OPI ONE/LITE with moderate loads running stably from very modest power banks. The superior performance compared to RasPis ( ZERO/A+/B+/2 ) clearly make the OPIs the boards of choice. Good to know settings can be further adjusted from user space.
  14. @tahaea1 First things to check with HDD errors would be power supply/cable ( you need a >2A stable PSU for the 1A power surges of HDDs ), USB adapter/cable ( USB3 adapters normally work, USB2 adapters most likely need additional power/second USB power connector ). HDDs on OPI usually work like a charm with Armbian when powered and interfaced correctly. Are you planning to use the "NTFS storage partition" for some proprietary nostalgia ? Have a look at ext4 if you plan to use it with modern Armbian. Good luck.
  15. /etc/network/interfaces auto eth0 allow-hotplug eth0 auto wlan0 allow-hotplug wlan0 You might get some ideas from Check your configuration and retry. Good luck.
  16. Try
  17. There most likely is, but I doubt you'll get the point. Before flooding the forum with your rants, please show some respect for the hard-working Armbian team providing an excellent product. @igor, a major if not the source of Armbian, has given you precise instructions. Follow them and succeed.
  18. Hi Tracy, First thing I'd check is power supply. I've been running all sorts of HDDs and SSDs on OPI boards and regularly encountered problems when they were powered directly by the board. Peak current easily tops (additional) 1A. Additionally Firefox ( like most browsers ) spends 2-3% on useful stuff and another 97-98% on plain junk justified as personalized targeted marketing experience.
  19. OK, fine, wonderful !!!! Why invent further problems when there are none whatsoever ?
  20. OPI ONEs run reliably when fed through the dedicated power plug. Extensive testing was done with - 5V/2A power supplies - 5V/1A - 5V/2A power banks with passthrough charging - 5V/6A DC/DC step down converters Most of the problems encountered were crappy cables ( only 5 out of 20 cables had losses < 0.4V ) or braindead use cases ( powering HDDs with peak >1A currents directly through USB2 ). RaspberryPIs A+ or PiZero consume less power and are WAY BELOW OPI ONE PERFORMANCE, Raspi2 has slightly less performance and comparable power consumption to OPI ONE. Get a decent PSU with matching cable and enjoy Armbian on OPI ONE.
  21. Sorry - cannot help you there. Pls. reread the instructions in case you would like working wifi. Obviously you started out somewhere and ended up in the boonies. To end this endless cycle I'd recommend you reread the basic documentations on getting started with Armbian, prepare a completely NEW current Armbian_5.15 sdcard and take it from there. Best of luck!
  22. Try instructions on forum
  23. @FPeter I just did an upgrade to Armbian_5.15 and rechecked wifi working with module 8188eu. root@opione_6:/home/pi# lsmod Module Size Used by ..... 8188eu 908230 0 root@opione_6:/home/pi# ifconfig ..... wlan0 Link encap:Ethernet HWaddr 00:13:ef:80:02:7f inet addr:xxxxxxxxxxxxxxxxx Bcast: Mask: inet6 addr: xxxxxxxxxxxxxxxxxxxxx Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 TX bytes:116 (116.0 wlan1 Link encap:Ethernet HWaddr 06:13:ef:80:02:7f inet addr:xxxxxxxxxxxxxxxxx Bcast: Mask: inet6 addr: xxxxxxxxxxxxxxxxxxxxx Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14782 errors:0 dropped:211 overruns:0 frame:0 TX packets:11804 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8906076 (8.4 MiB) TX bytes:2727423 (2.6 MiB) root@opione_6:/home/pi# lsusb .... Bus 002 Device 002: ID 0bda:8179 Realtek Semiconductor Corp. Works like a charm. Pls. check your setup and retry per earlier instructions. Good luck.
  24. I used stock 8188eu driver of Armbian_5.10 on OPI ONE/LITE and have since just upgraded ( presently I'm at 5.14 ). Here's what I get from a running OPI ONE : root@opione_6:/home/pi# modinfo 8188eu filename: /lib/modules/3.4.112-sun8i/kernel/drivers/net/wireless/rtl8188eu/8188eu.ko version: v4.3.0.6_12167.20140828 author: Realtek Semiconductor Corp. description: Realtek Wireless Lan Driver license: GPL srcversion: 6E1E9435E7EEE679F088FA2 alias: usb:v07B8p8179d*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp0179d*dc*dsc*dp*ic*isc*ip* alias: usb:v0BDAp8179d*dc*dsc*dp*ic*isc*ip* depends: intree: Y vermagic: 3.4.112-sun8i SMP preempt mod_unload modversions ARMv7 p2v8 parm: rtw_ips_mode:The default IPS mode (int) parm: rtw_usb_rxagg_mode:int parm: rtw_qos_opt_enable:int parm: ifname:The default name to allocate for first interface (charp) parm: if2name:The default name to allocate for second interface (charp) parm: rtw_initmac:charp parm: rtw_custom_default_mac:charp parm: rtw_channel_plan:int parm: rtw_chip_version:int parm: rtw_rfintfs:int parm: rtw_lbkmode:int parm: rtw_network_mode:int parm: rtw_channel:int parm: rtw_mp_mode:int parm: rtw_wmm_enable:int parm: rtw_vrtl_carrier_sense:int parm: rtw_vcs_type:int parm: rtw_busy_thresh:int parm: rtw_ht_enable:int parm: rtw_bw_mode:int parm: rtw_ampdu_enable:int parm: rtw_rx_stbc:int parm: rtw_ampdu_amsdu:int parm: rtw_lowrate_two_xmit:int parm: rtw_rf_config:int parm: rtw_power_mgnt:int parm: rtw_smart_ps:int parm: rtw_low_power:int parm: rtw_wifi_spec:int parm: rtw_antdiv_cfg:int parm: rtw_antdiv_type:int parm: rtw_enusbss:int parm: rtw_hwpdn_mode:int parm: rtw_hwpwrp_detect:int parm: rtw_hw_wps_pbc:int parm: rtw_max_roaming_times:The max roaming times to try (uint) parm: rtw_fw_iol:FW IOL (int) parm: rtw_mc2u_disable:int parm: rtw_80211d:Enable 802.11d mechanism (int) parm: rtw_notch_filter:0:Disable, 1:Enable, 2:Enable only for P2P (uint) parm: rtw_hiq_filter:0:allow all, 1:allow special, 2:deny all (uint) parm: rtw_tx_pwr_lmt_enable:0:Disable, 1:Enable, 2: Depend on efuse (int) parm: rtw_tx_pwr_by_rate:0:Disable, 1:Enable, 2: Depend on efuse (int) parm: rtw_phy_file_path:The path of phy parameter (charp) parm: rtw_load_phy_file:PHY File Bit Map (int) parm: rtw_decrypt_phy_file:Enable Decrypt PHY File (int) Hope this helps. I have not compiled the drivers and do not have any further info. Good luck.
  25. Just rechecked the steps outlined in previous posts so there must be something different in your setup. Connect Armbian device ( OPI ) to Linux host and you should be able to communicate when the /dev/ttyACMx shows up on the host without any need of setting up serial parameters ( baud rate, parity, flow control etc...). On the OS-X side this would require a suitable (acm) driver for the specific interface that shows up when you plug in the USB cable. Best of luck - you're close.