Thomas131

October 10, 2019

Hello!
I have an Cubietruck with an attached SATA-Disk. I would like to use the board without an SD-Card (I don't see why I should use one when I have a nand and a Disk). I can boot u-boot-sunxi-with-spl.bin using FEL and Armbian boots successfully. I can write stuff to nand, but I didn't manage to write an working u-boot to nand. Is the SPL-Version the correct one or the one without? Do I have to write to something special like MBR? Where does the BROM search for the bootloader? Does it parse the partition-table?

Thanks in advance!

July 9, 2018

Hello!
I have the same Problem on the Huawei E3531. I attached dmesg after attaching on a normal Linux Mint-PC and my Pine64.

Thanks in advance!
Thomas

linux_mint_dmesg.txt

pine64_dmesg.txt

July 28, 2017

Thanks, this really helped!:

me@pine64:~$ uname -a
Linux pine64 3.10.105-pine64 #2 SMP PREEMPT Fri Jun 23 21:12:42 CEST 2017 aarch64 aarch64 aarch64 GNU/Linux
me@pine64:~$ sudo cat /sys/kernel/debug/gpio
[sudo] password for meroot:
GPIOs 0-255, platform/1c20800.pinctrl, 1c20800.pinctrl:
gpio-0   (?                   ) in lo
gpio-72 (w1                  ) in lo
gpio-166 (1c0f000.sdmmc cd    ) in lo
gpio-231 (SPK                 ) out lo

GPIOs 352-383, platform/1f02c00.pinctrl, 1f02c00.pinctrl:
gpio-354 (wlan_regon          ) out hi
gpio-355 (wlan_hostwake       ) in lo
gpio-356 (bt_rst              ) out lo
gpio-359 (system_status       ) out hi

GPIOs 1024-1027, platform/pinctrl.2, axp-pinctrl:
me@pine64:~$ exit

After a search on the internet, I found out, that this is the 1-wire kernel module. I unloaded it with sudo modprobe -r w1-gpio. Now it works! To permanently prevent the module from loading, I added it to /etc/modprobe.d/blacklist.conf.

Thanks! Your answer helped a lot!!!!

July 28, 2017

Hello!

I installed a fresh Armbian (5.31; Server) on my Pine64 yesterday. Today I wanted to start playing around with GPIO ... And it seems like Pin 72 isn't working ... Doing the same on Pin 77, everything works fine ... For the secound test, I used https://github.com/databit/Pine64-CPP. I only added some Debug info to example.cpp.

Spoiler

Script started on Fri 28 Jul 2017 01:35:44 PM CEST
root@pine64:/sys/class/gpio# echo "72" > export
bash: echo: write error: Device or resource busy
root@pine64:/sys/class/gpio# echo "72" > unexport
bash: echo: write error: Invalid argument
root@pine64:/sys/class/gpio# ls
export gpiochip0 gpiochip1024 gpiochip352 unexport
root@pine64:/sys/class/gpio# cd /opt/Pine64-CPP/
[Removed some lines where I was inserting debug info into example.cpp]
root@pine64:/opt/Pine64-CPP# make
g++ -fpermissive -Wall -o test *cpp
sudo ./test
Set GPIO pin directions
Turn Led ON    PinMode:1   Value:1
Turn Led OFF   PinMode:0   Value:0
Turn Led ON    PinMode:0   Value:0
Turn Led OFF   PinMode:0   Value:0
Turn Led ON    PinMode:0   Value:0
Turn Led OFF   PinMode:0   Value:0
^CMakefile:2: recipe for target 'default' failed
make: *** [default] Interrupt

root@pine64:/opt/Pine64-CPP# make
g++ -fpermissive -Wall -o test *cpp
sudo ./test
Set GPIO pin directions
Turn Led ON    PinMode:1   Value:1
Turn Led OFF   PinMode:1   Value:0
Turn Led ON    PinMode:1   Value:1
Turn Led OFF   PinMode:0   Value:1
Turn Led ON    PinMode:0   Value:1
Turn Led OFF   PinMode:0   Value:1
Turn Led ON    PinMode:0   Value:1
^CMakefile:2: recipe for target 'default' failed
make: *** [default] Interrupt

root@pine64:/opt/Pine64-CPP# cat example.cpp
/*
                              PINE 64 - C++ lib                                            1
Copyright (c) 2017 Daniele Contarino <daniele.contatino@studium.unict.it>               i111i
This library is based over work by:                                                  .ft .; .tf.
     Eric Ptak <trouch@trouch.com>                                                    ft. ,fft. .ff
     Stefan Mavrodiev @ OLIMEX LTD <support@olimex.com>                               1fffffffffff1
     Kamil Trzcinski <ayufan@ayufan.eu>                                           ,LLf. ,fffffff, ,LLL,
Permission is hereby granted, free of charge, to any person obtaining a copy of   ,LLLLLLLi   iLLLLLLL,
this software and associated documentation files (the "Software"), to deal in     ,LLL; 1LLLLLi ;LLL,
the Software without restriction, including without limitation the rights to        :LLLLLLLLLLLLLLL:
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies    .LLL; 1LLLLLLLi ;LLL
of the Software, and to permit persons to whom the Software is furnished to do    :LLLLLLL:   :LLLLLLL,
so, subject to the following conditions:                                           iLLf. :LLLLL, .LLL;
The above copyright notice and this permission notice shall be included in all       1LLLLLLLLLLLLLi
copies or substantial portions of the Software.                                          :LLLLL:
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR                  L
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,                    L
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
*/
#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#include <sys/resource.h>
#include <errno.h>
#include <unistd.h>
#include <string.h>
#include <iostream>
#include <sstream>

#include "pinout.h"
#include "gpio.h"
#include "i2c.h"
#include "spi.h"

using namespace std;
using namespace Pine64;

int main (void) {
GPIO* man = new GPIO();

    if (man->setup()) {
        cout << "Failed to configure GPIO\n" << endl;
        return 1;
    }

   cout << " Set GPIO pin directions" << endl;
   man->pinMode(72, OUTPUT, PUD_OFF);

   while(1) {
           cout << "Turn Led ON ";
           man->digitalWrite(72, HIGH);
       cout << "\tPinMode:" << man->GPIOFunction(72);
       cout << "\tValue:" << man->digitalRead(72) << endl;
           man->delay(1000);

       cout << "Turn Led OFF";
           man->digitalWrite(72, LOW);
       cout << "\tPinMode:" << man->GPIOFunction(72);
       cout << "\tValue:" << man->digitalRead(72) << endl;
           man->delay(1000);
   }

cout << "Exiting....." << endl;
return 0;
}
root@pine64:/opt/Pine64-CPP# exit

Script done on Fri 28 Jul 2017 01:43:42 PM CEST

When I looked at the Schematics of the Pine64 (http://files.pine64.org/doc/Pine A64 Schematic/Pine A64plus 2GB Rev C-20160113_Release.pdf), I noticed that according to Page 7, the Pine has eMMC on it and the whole Port C is connected to it ... I haven't found that somewhere else and couldn't find an eMMC-Chip on my Pine, too.

Do you have an idea, why it doesn't work? A reboot didn't help, too ...

Thanks in advance!

Thomas

July 19, 2017

Hello!

And another time sorry for the late reply!

To be honest, it has helped less ... Ok, UAS seems to have less to do with SCSI/SAS-Disks. At least the protocol works with normal SATA-Disks, too. (What is the big difference between SAS and SCSI?) Sorry, I have a big hole in my knowledge according to SCSI and SAS!

Still thanks for the link!

Thomas

July 17, 2017

Hello!

Thanks for all the answers! Sorry, that I am that late ... I was ill and I completely forgot to look for answers ... I miss mail notifications (now I enabled them) ...

On 13.7.2017 at 0:39 PM, Igor said:

This particular board is not the best choice for NAS I would say since its USB to SATA implementation is not good, but you can find better options. Check H3 devices as NAS topic. H3 devices are stable, we know them good, kernel is in good state and they are cheap. USB UAS implementation help to gain better speed.

Ok, you are right! That was the reason, I wrote, that I wouldn't buy it.

Just for clarification: UAS has to do with SCSI, has it? What are the relationships with SATA? Sorry for this noob question ... I don't have done anything with SAS/SCSI-Disks ...

According to customs ... I don't have a problem to pay some (lets say 20€) taxes, but for example a shipment (another Pine64) of a teacher at our school was sent back by the Customs ... Thats what I want not to happen ...

To clarify: I DON'T need WiFi, nor will use it! I want GbE ... Simpler, less power consumption, faster (except of IEEE 802.11ac in very special cases maybe).

Since I read some posts, boards with FAST/GOOD USB 2.0 Implimentations or USB 3.0 will get into consideration, too. And *good* USB2SATA bridges.

BTW: If I use sshfs to transfer my data, the CPU will probably be the bottleneck (encryption). I can lower the encryption maybe (just@home and VLAN is on my TODO-List) ... or use NFS for my Workstation. But for my Laptop, I will NEVER use NFS since it is to insecure for me when I take it out of home ... What do you suggest?

Btw: What do you say about the Cubietruck? For me it seems great, but a bit slow (especially ssh?). I will probably get one from a friend for free if I want ... Now, that is my #1 at the moment.

Thanks for all the patience!

Thomas131

July 12, 2017

Thanks for your answers!

I didn't know, that OrangePi is that bad, too ...

I thought that USB -> SATA converters are horrible and a huge bottleneck ...

I think I will wait and see if the espressobin gets supported better ... I want a stable OS (Ok, maybe it is one already). And GPIO is essential on my server ... The next question will be how to get one in Austria (I don't know the customs conditions but last time I had to pay a high fee for some Pine64).

Thanks and I am still open for recommendations! Especially I am unsure how good RAID1 between USB and SD works ... Write Speed ... Since the Espressobin has no eMMC onboard, too and I don't want to solder one for myself ...

Thanks again!

Thomas

July 11, 2017

Hello!
I want to replace my old "Server" (Pi 1B) with something more powerfull. In the same move, I want to use my server to do a lot more things than it does now. To be future-proof I would like my server to have GbE and 2 GB RAM. I would also love internal storage that I am able to do software RAID 1 with my SD-Card for security (Could I also use an simple USB-Stick instead of onboard flash?).

Also I want to have a Home-NAS for Backups. (SATA; GbE)

I am wondering if I should combine the two into one ... in this case, the Server-OS would be backed up probably on my workstation. Why using two devices if I could use one ... It would have lots of minor benefits ... saving Power, saving Ethernet-Ports, saving Power Supply Ports, SD-Cards, save buy coasts, I would only need to keep one device up to date

But at the moment, I haven't really found a board which I would buy for both in one:

Banana Pi M2U: Not supported by armbian, yet
Banana Pi M1: just 1 GB RAM
Orange Pi+ 2: I assume the USB->SATA-bridge would be a bottleneck for the Backups ... or GbE ... I don't know ...
Marvell ESPRESSOBin: seems great, but is very unpopular&unsupported by armbian at the moment

Armbian is no "must have" ...

Or should I buy an NAS and flash some Linux on it?

If I would seperate the two boards, I would take an Banana Pi M1 as NAS and a very cheap SoC with GbE as Server ... I have a Pine64 laying around ... but I would prefer one device ...

Do you have any recommendations or would you change something in my requirements?

Thanks in advance!
Thomas

Sign In

Thomas131

Posts

Joined

Last visited

Content Type

Forums

Store

Crowdfunding

Applications

Events

Raffles

Community Map

Posts posted by Thomas131

write u-boot to nand

Huawei Hilink modem on Armbian

Pine64: Pin 72/PC8 not working

Pine64: Pin 72/PC8 not working

Server & NAS in one Hardware

Server & NAS in one Hardware

Server & NAS in one Hardware

Server & NAS in one Hardware

Forums

My Activity Streams

Download

Store

Important Information