(05-03-2016, 06:43 AM)Manilow Wrote: The pine64(512) stays at 480MHz and 36°C temperature, when I run my testscript, while the PINE64+ (1GB) jumps up to 912MHz and 53°C, when running the script. [...]
how the decision is made, which of those dtb files is used? Right now there are both files in the /boot/pine64 folder.
Regarding .dtb first: This is u-boot's job. By looking at the available DRAM the correct .dtb will be chosen (using the wrong .dtb would most probably result in no network at all but I'm not 100% sure).
Cpufreq does matter (at least with ARMv7 boards this was an observation) so please consider adding priot to "exit 0" to /etc/rc.local:
Code:
echo performance >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governorAnd then regarding TX/RX delay. We have several sunxi boards where depending on these values you get almost no packets through the wire. Longsleep did many testings (details here) but IIRC he was focused on Pine64+ so maybe they're completely off for Pine64. Some background information: http://linux-sunxi.org/Ethernet#GMAC and http://forum.armbian.com/index.php/topic...h-gigabit/
And also another issue that plagued users of Olimex boards that use a different external PHY than most other boards (RTL8211CL instead of RTL8211E): https://www.mail-archive.com/u-boot@list...07006.html
The links aren't meant as 'here you find a solution' but just to outline in which sorts of problems you might run (and I really mean you since I believe of the few linux-sunxi devs that work on Pine64 support only longsleep got also the 512MB board -- and pays not that much attention to it since not just in his opinion the 2GB version with GbE is the only interesting one)
Addendum: Using longsleep's monitoring script you can get the actual values but I find it sometimes more convenient to use a real monitoring solution that also gives access to 'historical' data. I provide a simple installation routine for Ubuntu on Pine64+ with all the adjustments for A64/AXP803: http://kaiser-edv.de/tmp/4U4tkD/install-...for-a64.sh (takes a few minutes to install)
EDIT: Just realized that you don't use an original OS image but a 3rd party one. In case you haven't done already please ensure you really use latest u-boot/kernel fixes:
Code:
bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_uboot.sh)
bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_kernel.sh)
bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_fix_whatever.sh)Just to ensure u-boot is up-to-date to choose the correct .dtb.
(05-03-2016, 06:43 AM)Manilow Wrote: Furthermore: The files in the /boot/pine64 directory or binary, while your github files are text. How do I convert them to binary?
Sorry, overread that. You need the dtc tool. No idea whether that's part of your distro but since this is Debian an 'apt-get install devicetree-compiler' should do the job (ditto a web search for 'dtc dtb dts' for the basic syntax)