vlad59
-
Posts
180 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by vlad59
-
-
First it's not a complaint (really). The new forum feel a little slow comparing to before. I have no way to be sure but I wonder if I'm alone here ?
-
You're using mainline kernel (4.10) so the fex is not used anymore.
You'll have to use some device tree overlays (search the forum for that)
-
Hi,
I'm not fluent with pyA20 but I worked with DH11/DHT12 (before using onewire, si7201 or bme280 and never getting back)
I would remove all PULLUP or PULLDOWN from your code, Looking at the photo you don't use the bare sensor but an all-in-one -> I'm almost sure you already have an embedded pullup (between 1kΩ and 4kΩ so way better than the integrated ones) and you may also have a small decoupling cap as a bonus.
Did you try your pin with a simple led to check if you are using the good one ?
Back then I had a lot problem with the cpu speed, try to force a higher frequency (that will help all the sleeps to be more accurate) and try to kill all other daemon that you don't need.
-
The only thing I wanted to change is to set scaling_min_freq to 528000 for consistency. But it won't change a single thing.
Anyway thanks a lot for your answer, my curiosity is satisfied
. -
Hi,
No real problem, just a question. I'm using latest Armbian Jessie 5.25 with my good old Banana Pi.
root@marvin:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies 144000 312000 528000 720000 864000 912000 960000 root@marvin:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 480000 root@marvin:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 960000
Please notice that 480MHz (the min freq) is not in the available frequencies.
So that gives the following output with cpufreq-info :
root@marvin:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 1 maximum transition latency: 244 us. hardware limits: 144 MHz - 960 MHz available frequency steps: 144 MHz, 312 MHz, 528 MHz, 720 MHz, 864 MHz, 912 MHz, 960 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 528 MHz (asserted by call to hardware). cpufreq stats: 144 MHz:0,00%, 312 MHz:0,00%, 528 MHz:98,22%, 720 MHz:1,04%, 864 MHz:0,08%, 912 MHz:0,23%, 960 MHz:0,43% (39367) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 CPUs which need to have their frequency coordinated by software: 0 1 maximum transition latency: 244 us. hardware limits: 144 MHz - 960 MHz available frequency steps: 144 MHz, 312 MHz, 528 MHz, 720 MHz, 864 MHz, 912 MHz, 960 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 480 MHz and 960 MHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 528 MHz (asserted by call to hardware). cpufreq stats: 144 MHz:0,00%, 312 MHz:0,00%, 528 MHz:98,22%, 720 MHz:1,04%, 864 MHz:0,08%, 912 MHz:0,23%, 960 MHz:0,43% (39367)Should I set /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq to 528000 or is there a problem with 480MHz not being in available frequencies ?
IIRC I had the same problem with the previous kernel (Armbian 5.24), I do not remember if it happened before.
-
Hi this is latest Armbian on my Banana Pi with a SSD drive :
root@marvin:~# uname -a Linux marvin 4.9.5-sunxi #1 SMP Fri Jan 20 22:01:51 CET 2017 armv7l GNU/Linux root@marvin:~# dmesg | grep scsi [ 3.942302] scsi host0: ahci-sunxi [ 4.285757] scsi 0:0:0:0: Direct-Access ATA SanDisk SDSSDA24 00RL PQ: 0 ANSI: 5 [ 4.361854] sd 0:0:0:0: Attached scsi generic sg0 type 0 root@marvin:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 223.6G 0 disk └─sda1 8:1 0 223.6G 0 part / mmcblk0 179:0 0 7.4G 0 disk └─mmcblk0p1 179:1 0 7.3G 0 part /media/mmcboot
Everything is working as expected. My power source is a good quality 2A adapter.
-
Answering questions like that is always tricky but I got a Banana Pi (so A20) running 24/7 with a SSD for more that two years (since July 2014). At first it was with legacy kernel but now it's using vanilla 4.X. it has some I2C sensors directly connected to GPIO, one UART is also used for my Moteino network.
No random crash, every restarts was because of me or electrical problems. I'm trying to do the same with H3 but not having real SATA support (so no SSD) is a problem (I have a NFS / DLNA Server on it).
Depending on your needs (domotic you said), Nanopi Air could be completely enough.
-
is that pin already used for something else ?
-
Seagate Dockstar is Marvell Kirkwood and there you're able to benefit from CESA through /dev/crypto (without performance would really suck). A small overview regarding those 'NAS and router SoCs' can be found here: https://wiki.openwrt.org/doc/hardware/cryptographic.hardware.accelerators
Exactly, SFTP performance were 2 times better with CESA but both my Dockstars NAND died after running 24/7 for 2 years.
-
IIRC, a while ago, I made some benchmark with hardware crypto engine on a Dockstar and I was using :
openssl speed -elapsed -evp aes-128-cbc
the -elapsed was essential for the comparison
-
Really appreciated !!!!
Thanks for sharing.
-
Another advice.
If you need a good quality sensor (especially for humidity), BME280 is a better choice (with a higher price, I know) and you get a pressure sensor for free. it's also using i2c so easier to handle.
If you wish to keep the price low SHT21 can be found around 3€ (Aliexpress) and it's still i2c.
-
Hi,
I'll try to help even if I only own many DHT22 and no DHT21.
I have one Banana Pi (basically the same as Lamobo R1) which is reading temperature and humidity (with the DHT22), here is my configuration :
* the program used is lol_dht22 on top of WiringBp
* the DHT22 is powered with 3.3V (not 5V)
* my cables are small (10~15cm)
* I have a 4.7K pullup resistor (it was mandatory for me, removing it caused bad CRC almost everytime), I guess you can use resistor from 1K up to 10K with the same effect.
* I used it with legacy kernel (3.X) for one year and use it with modern kernel (4.X) for another year and it's still going
* my Banana pi is up 24/7 and read value from DHT22 every 15 minutes
So my advice : use 3.3V, use a real pullup and make sure there is zero load on your Lamobo when you make the test (to make sure all timings can be handled)
-
I've advised to change the minimal frequency to an higher value (not lower) : 600MHz instead of 480MHz
That's mainly because delayMicroseconds is a busy loop so having an higher frequency will make it more precise. Linux is not a realtime OS so you don't have much choice.
Of course if you need 100% reliability, your best choice is to connect your DHT22 to an Arduino and connect your Arduino to your Orange Pi with an UART.
-
You can try this project for DHT22 : https://github.com/technion/lol_dht22
I made some modifications here : https://github.com/seblucas/lol_dht22and I've been using it for a year and a half on my Banana Pi doing a reading every 15 minutes. So far I loose on average 1 reading per day.
You can see here that the program has to wait for specific amount of time. So if you want to use your DHT22 with a lot of reliability, you'll have to keep the CPU load low and maybe tweak your cpufreq settings to set a minimal freq at around 600MHz this should help lowering the errors you see.
-
They have finally arrived. Sent via the wrong shipping method but they got to me in the end. Just going through and checking them all now.
I hope they'll arrive soon then
-
Looks like I won't be getting my order this week. Apparently due to a high volume of orders they are unable to send out my order until next week. Kinda sucks but can't do anything about it.
My order has been delayed too
-
I should be receiving 2 nanopi Neo in 3 weeks hopefully. I'll make all the tests needed as soon as received.
<off topic>I can confirm that my Nanopi M1 work fine even at 744MHz so no need to lower the DRAM settings for them</off topic>
-
This was actually easy, I only need the dts directory and the kernel headers (they were already installed) and that's it. The compile script look like that :
#!/bin/sh IDE=sun7i-a20-bananapro SRC=$IDE.dts TMP=$IDE.tmp.dts DST=$IDE.dtb cpp -nostdinc -I /usr/src/linux-headers-4.5.2-sunxi/include -undef -x assembler-with-cpp $SRC > $TMP dtc -O dtb -b 0 -o $DST $TMP #rm $TMP
I'll check tonight if the DTB I compiled is exactly the same as the one from Armbian.
EDIT : An additional interest of having all the DTS files is that you can quickly find the DTB file you're currently using :
root@bananapipro:~/test/dts# grep "`cat /proc/device-tree/model`" *.dts sun7i-a20-bananapro.dts: model = "LeMaker Banana Pro";
-
While it's possible to pack full kernel source into a .deb package, installing a package with such number of small files on a device will be a nightmare (especially on a slow SD card). It may be better to provide ony "arch/arm/boot/dts" and "include" directories - this should be enough for compiling DT from scratch.
I'll try that tonight. Thanks for the idea.
-
This is the right approach if you don't know exact name of DTB file. ${fdtfile} variable in u-boot is defined at compile time (in defconfig file for the board) and this value is not accessible outside of u-boot.
Thanks for the confirmation.
Another quick question, currently I can install the kernel headers (patched Armbian version).
Would it be possible to have the complete patched kernel sources through apt.armbian.com ?
If that's possible, we could have access to the real DTS file (with comments, unprocessed) and use dtc on them (like shown here). It would make the job easier most of the time and there would be no need to recompile the full kernel.
I always find it hard to manually edit decompiled DTB.
-
For people who wanted to help with documentation, here is your chance:
This was added recently, so it's a good idea to extend this to more or less universal HOWTO for different boards.
Things to add:
- Generic prologue about kernel version and configuration files(TL;DR - fex/bin for legacy, Device Tree for mainline);
- Decompiling/editing/compiling back .bin/.fex files with some practical examples;
- Decompiling/editing/compiling back .dtb/.dts files, matching original and decompiled syntax, some practical examples;
- Compiling DT from scratch if changes are too big, some examples for this case too;
- Troubleshooting (how to check that changes were correctly applied, where to look for error logs (dmesg), etc);
I'm not saying that one person should do all of this, so feel free to claim topics you are most familiar with.
Hi I'm currently working on this and while I'm fluent (or at least I hope so) in FEX modification (two commits were merged), DT is newer for me.
I'll certainly need some guidance here. My first question is how do you know which DTB file you're currently using. For now my method it to use
cat /proc/device-tree/model
and try to guess the file in /boot/dtb. It worked, but there's certainly a better method.
boot.cmd is using ${fdtfile} so no help here
boot.src is compiled so no help there either.
Thanks in advance.
-
Here is the graph for more than an hour of cpuburnA7 with my Nanopi M1 without heatsink.
So my conclusion :
* No crash also so the setting from Banana Pi M2+ seems good. I'll make a lima_memtest run but I think it'll be fine.
* The heatsink does help (the CPU stayed mostly at 648MHz with 3 cores with the heatsink and was much erratic without)
* The Nanopi M1 performance under load is way lower than Orange Pi (see tkaiser post)
I think I'll use my NanoPI with Openelec to replace my Raspberry Pi 2. I'll make a test this weekend and ask my daughters to watch Frozen / Any Ghibli movie one or two times on it
. That's not what I have planned but that'll do.@tkaiser
Can I make a PR on github to update the nanopim1.fex or do you want to fix differently ?
Should I add the nanopi M1 page on linux-sunxi's Wiki ?
That should close the Nanopi case for now unless anybody need another test (once the nanopi are in the hands of my daughters, tests will be way harder to plan)
-
At last one good news. I made three one hour runs of lima_memtester at 696, 720 and 744 MHz and they all passed without any crash or redish background.
Tomorrow I'll remove the heatsink, clean the CPU and remake a cpuburn-a7 to be absolutely sure that my previous graph is trustable.
@tkaiser
Let me know if you need something else.
Testers wanted: sunxi Device Tree overlays
in Advanced users - Development
Posted
Hi,
Just to be sure to understand, to make some test on A20 (Banana Pi in my case), I simply need latest Armbian (either 5.25 or 5.26) as you can see here :
root@marvin:~# dpkg -l | grep kernel ii cpufrequtils 008-1 armhf utilities to deal with the cpufreq Linux kernel feature ii kmod 18-3 armhf tools for managing Linux kernel modules ii libcpufreq0 008-1 armhf shared library to deal with the cpufreq Linux kernel feature ii linux-headers-next-sunxi 5.26 armhf Linux kernel headers for 4.9.12-sunxi on armhf ii linux-image-next-sunxi 5.26 armhf Linux kernel, version 4.9.12-sunxi ii rsyslog 8.4.2-1+deb8u2 armhf reliable system and kernel logging daemon root@marvin:~# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=bananapi BOARD_NAME="Banana Pi" VERSION=5.25 LINUXFAMILY=sunxi BRANCH=next ARCH=arm IMAGE_TYPE=stable root@marvin:~# uname -a Linux marvin 4.9.12-sunxi #4 SMP Thu Feb 23 19:46:51 CET 2017 armv7l GNU/LinuxOr do I need a nightly build ?
I can test the various i2c buses (I'm currently using i2c-1 with 3 sensors). I could also test i2s but I don't think it's available on the Banana Pi.