PINE64   ›   Portal

Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  

Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,997
» Latest member: darrendemers12
» Forum threads: 16,337
» Forum posts: 117,447

Full Statistics

Latest Threads
Mobian image for the Pine...
Forum: Mobian on PinePhone
Last Post: Korfou
04-27-2026, 09:57 AM
» Replies: 2
» Views: 122
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
04-19-2026, 12:56 PM
» Replies: 13
» Views: 14,909
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
04-18-2026, 10:08 AM
» Replies: 0
» Views: 189
Booting Issues
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:17 PM
» Replies: 24
» Views: 19,452
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:12 PM
» Replies: 1
» Views: 1,123
my pinecil v2 is not work...
Forum: General Discussion on Pinecil
Last Post: jagrav
04-17-2026, 06:28 AM
» Replies: 0
» Views: 117
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,439
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 308
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 9,260
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 431

 
  RFLink connected to /dev/ttyUSB0 not working
Posted by: ulysse132 - 05-15-2018, 08:19 AM - Forum: Linux on Rock64 - Replies (9)

Hello,

I've build my own RFLink using an arduino. It work very well on RPi.

But I have problem to make it work on Rock64. It worked this morning but after a restart (sudo reboot), it didn't work anymore.
Domoticz is configured to connect to RFLink via /dev/ttyUSB0.
After the restart, I have this error :

Quote:Error: RFLink: Error opening serial port!

I have no idea to solve it. Could you please help me ?

I use ayufan's latest stable version of xenial linux.
On RPi, the solution was to add 
Code:
enable_uart=1
to /boot/config.txt but there isn't any config.txt file.


Thanks a lot !


  unable to switch usb3 ports on
Posted by: cglhu - 05-14-2018, 12:15 PM - Forum: Rock64 Hardware and Accessories - Replies (6)

Hi all,

I have a problem with the usb3 ports. I run an arch linux installation on a rock64. I followed the instructions in this thread 
https://forum.pine64.org/showthread.php?tid=5001
and that helped me to get usb2 ports working. But I can't do the same thing for the usb3 ports (toggle the right gpio to switch the regulator for usb3 on). Mostly I don't know, which gpio port belongs to the usb3 regulator.

Maybe someone can give me a hint.

Thanks in advance and

Best regards,
Christoph


  RockPro64 On its way
Posted by: mikeD - 05-14-2018, 04:42 AM - Forum: General Discussion on ROCKPRO64 - Replies (17)

Just had confirmation that my order is on its way. cannot wait.
Looking forward to getting my hands on this.


  Some problems with kernel module und device tree..
Posted by: Osiander - 05-14-2018, 02:32 AM - Forum: General - No Replies

Hello guys,

I'm developing a kernel driver for a MOST NIC and have got some problems by reading the chip configuration from device tree.

Here is the configuration:

Code:
&i2c2 {
    pinctrl-names = "default";
    pinctrl-0 = <&i2c2_pins_a>;
    status = "okay";
    
    os8104: os8104@41 {
        compatible = "smsc,os8104";
        reg = <0x41>;
        master = <0>;
        bypass = <0>;
        
        gpio_reset = <&pio 8 17>;    /* PI17 */
        gpio_int = <&pio 8 16>;        /* PI16 */
        gpio_aint = <&pio 8 19>;    /* PI19 */
        gpio_error = <&pio 8 18>;    /* PI18 */
    };
};

My NIC (os8104) is connected to i2c-2. 

And here is the corresponding code in LKM:

Code:
static int os8104_probe(struct i2c_client *client, const struct i2c_device_id *id) {
    struct device_node *dn;
    int rc;
    int master = 0, bypass = 0;
    struct os8104 *priv;

    dn = of_find_node_by_name(NULL, os8104_driver.driver.name);
    if (dn == NULL) {
        return -ENODEV;
    }

    rc = of_property_read_u32(dn, "master", &master);
    pr_err("rc = %d, master = %11d\n", rc, master);
    
    rc = of_property_read_u32(dn, "bypass", &bypass);
    pr_err("rc = %d, bypass = %11d\n", rc, bypass);

    priv = devm_kzalloc(&client->dev, sizeof(*priv), GFP_KERNEL);

    if (!priv) {
        return -ENOMEM;
    }

    priv->adapter = to_i2c_adapter(client->dev.parent);
    priv->client = client;
    priv->mode = val;
    
    priv->gpio_reset = of_get_named_gpio(dn, "gpio_reset", 0);
    priv->gpio_int = of_get_named_gpio(dn, "gpio_int", 0);
    priv->gpio_aint = of_get_named_gpio(dn, "gpio_aint", 0);
    priv->gpio_error = of_get_named_gpio(dn, "gpio_error", 0);
    
    return 0;
}

If I'm loading the module, the function of_find_node_by_name find my os8104 node, then I'm able to read the both properties (master and bypass). 

But, if I do an of_get_named_gpio(dn, "gpio_reset", 0), I get for each of four gpio-properties

Quote:[ 1610.330108] OF: /soc@01c00000/i2c@01c2b400/os8104@41: arguments longer than property

in dmesg.

Any ideas?

Kernel version is 4.14.39 and SBC is a BananaPRO (Allwinner A20 SoC).

Many thanks. Smile


  Screen flickering when playing multiple videos with rkximagesink
Posted by: matwey - 05-14-2018, 02:10 AM - Forum: Linux on Rock64 - Replies (2)

Hello,

I am running gstreamer-rockchip-extra on Rock64 SBC (RK3328) with the following software.

  • Linux kernel 4.4.120-rockchip-ayufan-209
  • gstreamer-rockchip-extra 1.10
  • gstreamer-rockchip 1.10-5ayufan12
  • librockchip-mpp1 1.4.0-1ayufan3-2
I try to run two H264 video simultaneously as the following:
Code:
gst-launch-1.0 uridecodebin uri=file:///home/rock64/big_buck_bunny_480p_h264.mov ! rkximagesink

I see constant flickering in both windows. It seems that every other frame is replaced by black rectangle.
Short video explaining what I see is available at https://transfer.sh/j1PII/gst-rockchip.mp4

Here is initial github issue:

https://github.com/rockchip-linux/gstrea...a/issues/2

But people at #rockchip-linux IRC channel said that they do not reply at github and I have to report it here.


  Summer Undergraduate Research using Pine64's
Posted by: pkivolowitz - 05-13-2018, 09:20 PM - Forum: Ubuntu - Replies (3)

Hi All,

I am leading two undergraduates on a summer research experience. My question follows this brief project description.

The goal of the project is educational not necessarily practical so after reading what comes next causes you to say to yourself: Why would you do that? The answer is to get down and dirty and learn.

We aim to modify Ubuntu to assert affinity only over certain cores and a portion of physical memory and during boot, load and launch a parallel real time OS. Certain hardware on the Pine64 will be stripped from Ubuntu and given over to the conjoined twin. Hardware related code such as interrupt handling will be modified to multiplex as needed. A thread safe intercommunications portal will exist allowing applications on Linux to exchange data with plugins running on the conjoined twin.

My first question is to confirm I'm downloading the right source code for this purpose (work starts in 3 weeks so I'm getting prepared).




Was this the right place? https://github.com/ayufan-rock64/linux-kernel.git



Thank you all


  Xen hypervisor on Rock64
Posted by: tumbleweed - 05-13-2018, 09:03 PM - Forum: Linux on Rock64 - Replies (6)

Hello,

I'm trying to install the Xen hypervisor on rock64, starting with the info at Xen ARM with Virtualization.
Here are the steps I followed so far:

  1. Installed a minimal debian stretch image on the rock64 mmc (thanks @ayufan !)
  2. Built Xen on rock64 (for XEN_TARGET_ARCH=arm64)
  3. Used mkimage to prep xen for uboot: mkimage -A arm -C none -T kernel -a 0x00800800 -e 0x00800800 -d dist/install/boot/xen xen-uImage
  4. Modified //boot/efi/extlinux/extlinux.conf  to add a custom configuration that loads the xen kernel (xen-uImage) using the same dtb that came with the stretch image (see config code below)
  5. Reboot with serial console attached, select my custom extlinux configuration
  6. rock64 hangs (serial output stops) at "Starting kernel ..."
As far as I know, nobody has written up a guide to doing this, on any RK3328 board, and it's my first time trying.
Anyone have suggestions on what I might try next to get past this hanging problem? 


Code:
label kernel-xen
   kernel /xen-uImage
   initrd /initrd.img
   fdt /dtb
   append earlyprintk=uart8250-32bit,0xff130000 rw root=LABEL=linux-root rootwait rootfstype=ext4 panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1

  RISC OS
Posted by: bencollier - 05-13-2018, 06:43 AM - Forum: General Discussion on Pinebook - Replies (7)

Hi,

Has anyone managed to get RISC OS running on the Pinebook?

Thanks,

Ben


Wink ROCKPRO64 PCI-E SATA is low price and low power best to choose wipe your hard disk
Posted by: joe - 05-13-2018, 12:57 AM - Forum: General Discussion on ROCKPRO64 - Replies (8)

If your company or personal not use your old hard disk , but the hard disk data include have your privacy data from hard disk e.g ( Your medical treatment information , ID CARD Number , VISA CARD , PASSWORD   ), this time you need to wipe your hard disk by the US LAW (HIPAA) .

This is very basic level to clear up your include privacy data.

I think most people know delete file is not really deleted , so this need to use Rrockpro64  help.
For the new generation HardDisk over 2TB , you need is time time time and more time and electricity  to wipe your hard disk.
.
Yes , you can say physical destroy is very fast , easy and safe , but physical destroy tool very expensive .


I reseach some have hardware they just to run software wipe your hard disk.

1. http://www.mejw.com.tw/  TP100-I around USD $456   ( Support  4TB )
2. http://www.killdisk.com/killdesk.htm USD $1999   ( Support more than 4TB in size )


Debian arm64 , armhf open source software have ( Scrub , Nwipe  ) can wipe your hard disk.
 
( Note: This two software without warranty and any certification  ( e.g HIPAA, ISO27001/27002) ,  no guarantee your data is completely sanitized across the entire drive , but the same have wipe algorithm .)

At least recovery software can't find it privacy data


1. Scrub  ( wipe algorithm )

https://github.com/chaos/scrub

[Image: A4RIenN.png]

2. Nwipe  (Based on Dban )

https://github.com/martijnvanbrummelen/nwipe


[Image: 3Uf44fc.png]

Other:  Open source Dban need your x86 , x86-64 pc around 300 w Power to wipe your harddisk , very waste your money  .

Rockpro64 you have 1 usb3.0 , 1 PCI-E support 2  SATA port


  Pine64 LTS Not booting
Posted by: krisclarkdev - 05-12-2018, 03:04 PM - Forum: General Discussion on PINE A64-LTS / SOPINE - Replies (2)

Hi all, I just received my Pine64 LTS in the mail today and loaded Diet Pi on an SD Card quickly to find out that it's not booting.

* Power is the provided barrel connector that I purchased
* SD Card is a San Disc 32 GB
* eMCC from plugged in, purchased at the same time as my Pine64
* USB Keyboard plugged in
* USB Mouse plugged in

I checked my DHCP Lease table and it doesn't look like it's powering up and getting an address.  I then took the SD Card out and put it in my Model B Pine64 and it boots right up without issue.

I also noticed that my USB Keyboard back light was on and the mouse was powered up too.

I then put the SD Card back into the LTS and removed parts one at a time in this order.

* eMCC
* Mouse
* Keyboard
* HDMI

And it is still not booting.

I've tried both Diet Pi and Xubuntu with the same results.  I'm starting to think my Pine64 was DOA.  Thoughts?

tyia,
Kris