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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,534
» Latest member: cbd gummies
» Forum threads: 16,206
» Forum posts: 116,942

Full Statistics

Latest Threads
Having trouble reading MP...
Forum: Getting Started
Last Post: Alex92
11 hours ago
» Replies: 1
» Views: 900
Call recording?
Forum: PinePhone Pro Software
Last Post: baptx
Yesterday, 02:43 PM
» Replies: 4
» Views: 4,396
Booting Issues
Forum: PineNote Software
Last Post: vlagged
09-04-2025, 12:52 PM
» Replies: 20
» Views: 7,713
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: teekay
09-04-2025, 01:40 AM
» Replies: 11
» Views: 2,333
[Article] RISC-V Ox64 BL8...
Forum: General
Last Post: PrinceMorissette
09-03-2025, 10:51 PM
» Replies: 2
» Views: 2,866
Why projects like PinePho...
Forum: General Discussion on PinePhone
Last Post: Kevin Kofler
09-03-2025, 02:47 PM
» Replies: 2
» Views: 1,407
irradium (based on crux l...
Forum: Linux on Quartz64
Last Post: mara
09-01-2025, 10:26 AM
» Replies: 6
» Views: 4,562
The PPP behaves as if the...
Forum: General Discussion of PinePhone Pro
Last Post: teekay
09-01-2025, 04:07 AM
» Replies: 2
» Views: 1,588
Pinephone Pro Neural Proc...
Forum: General Discussion on PinePhone
Last Post: biketool
09-01-2025, 02:05 AM
» Replies: 1
» Views: 2,515
Giving away a Pinebook Pr...
Forum: Pinebook Hardware and Accessories
Last Post: alchemist
09-01-2025, 12:24 AM
» Replies: 4
» Views: 3,145

 
  RockPRO64 Playbox vs PINE64 Playbox
Posted by: Firesped - 08-25-2018, 08:23 AM - Forum: General Discussion on ROCKPRO64 - No Replies

just wondering what the differences between these 2 products are, as the RockPRO64 playbox just went up on the store but I had already put an order in for the other one. It looked like the PINE64 playbox is compatible to me. That is why I ordered it.

are there plans to produce a battery that hooks internally into the power port for the RockPro64?

and to further ask, what other accessories are you planning for this device so we can just get all this amazement out of the way at how awesome this product is? what do you have planned?


Lightbulb Home server questions
Posted by: jannerman - 08-25-2018, 07:40 AM - Forum: General Discussion on ROCKPRO64 - Replies (3)

Hello all,
 
I need a small server to run on my living room (no space elsewhere), to be quiet and to use it for storage/nas, plex server, kodi, and some gaming if applicable (mame, snes psx etc) while will be connected to my 40" TV.
 
When I looked on RockPro64 4GB with the NAS case I thought that this is ideal for the job that I want.
 
So I intent to buy RockPro64 4GB, NAS Case, emmc 64GB, WiFi/Bluetooth Module, heatsinks/fan, PSU EU 5A and connect 2 HDD on it.
But before I buy it I have some questions, and I will appreciate any help:
1) Is v2.1 board available and without any H/W problems as the versions before (resistor removal etc)
2) Does PCIe SATA card works?
3) Which linux distro do you suggest in order to have desktop experience?
4) Based on (3) does it supports HW acceleration for Kodi?
5) Based on (3) can run Plex server (not just stream but transcode)?
6) Based on (3) I would want to install MAME, snes etc emulators. Would a bluetooth gamepad work?
7) Based on (3)  will a bluetooth Air mouse work?
 
The board will work as a server and NAS mostly but I want to be easy to control it with mouse and play some retro games from time to time.

EDIT: Looking the new ABS case with the graphene heatsink, I was thinking If I could power up a 2.5" HDD 1TB that I have with an external enclosure from the USB3.0 port.
It would take less space in the shelve under my TV.


Question SolusVM
Posted by: jcarroll53 - 08-24-2018, 04:58 PM - Forum: Linux on Pine A64(+) - No Replies

Anyone know if it is possible to run a SolusVM Slave Only server on a Pine A64? Side question, would it be better to run SolusVM Slave Only on a Rock64 instead?


  Clusterboard dimensions
Posted by: Pine - 08-24-2018, 03:58 PM - Forum: Clusterboard - Replies (3)

Does anyone have the LWH dimensions of the clusterboard in millimeters handy? The height to the top of the inserted SOPINE module would be great too. Thx


  man breaks after upgrade to 18.04
Posted by: goathunter - 08-24-2018, 10:37 AM - Forum: Ubuntu - Replies (9)

In a possibly silly move, last night, I upgraded Ubuntu MATE on my Pine A64+ from 16.04 to 18.04.

I'm still running the longsleep kernel 3.10.105. I was a little surprised that the upgrade worked, but it did. Everything was/is looking good, except that man is broken. When I run "man --debug man", I see:

Code:
man: can't execute preconv: Operation not permitted
loading seccomp filter (permissive: 1)
loading seccomp filter (permissive: 1)
loading seccomp filter (permissive: 0)
seccomp already enabled
man: can't execute col: Operation not permitted
man: can't execute tbl: Operation not permitted
trying encoding UTF-8 -> UTF-8//IGNORE
groff: couldn't exec troff: Operation not permitted


I can, of course, run all of those interactively without any problem.

Has anybody else tried upgrading to 18.04 and/or have any idea what the problem here might be?

Thanks!


  Does anyone have kodi working?
Posted by: blahblahblah - 08-24-2018, 09:48 AM - Forum: Linux on RockPro64 - Replies (6)

I just got my rockpro64 and I am trying to get it setup to run kodi and retroarch.  I have it running on the bionic-lxde-rockpro64-0.7.9-1067-arm64.img.xz image.  But I have no sound in kodi.  Sound works in mplayer after removing pulseaudio, but it gives the "your system is too slow" warning when trying to play any 1080p videos.


  Pine LCD on Rock64Pro
Posted by: DStanman - 08-22-2018, 11:20 PM - Forum: RockPro64 Hardware and Accessories - Replies (11)

I have read the threads on the 7” LCD that Pine sells.

I am looking to get this working on the Rock64Pro, but using the Bionic LXDE image.

1. No LCD by default. No power on, no backlight. HDMI works by default.
2. I tried setting the uEvb.txt lines, but that doesn’t existing in /boot/. Adding it had no effect.

Anyone able to help point me in the right direction?


  Customize LCD
Posted by: r.tanaka - 08-22-2018, 10:44 PM - Forum: LCD and Touch Panel - No Replies

Hi everyone

I'd like to change the setting value (resolution, format, porch, etc..) of DSI.

Therefore, do the following procedure.

1. edit /boot/uEnv.txt
 add disp_screen0=lcd

2. edit /boot/pine64/sun50i-a64-pine64-plus.dtb 

Code:
       lcd0@01c0c000 {
           compatible = "allwinner,sunxi-lcd0";
           pinctrl-names = "active", "sleep";
           status = "okay";
           device_type = "lcd0";
           lcd_used = <0x0>;
           lcd_driver_name = "mb709_mipi";
           lcd_backlight = <0x32>;
           lcd_if = <0x4>;
           lcd_x = <0x216>;
           lcd_y = <0x4B0>;
           lcd_width = <0x0>;
           lcd_height = <0x0>;
           lcd_dclk_freq = <0x37>;
           lcd_pwm_used = <0x1>;
           lcd_pwm_ch = <0x10>;
           lcd_pwm_freq = <0xc350>;
           lcd_pwm_pol = <0x1>;
           lcd_pwm_max_limit = <0xfa>;
           lcd_hbp = <0x78>;
           lcd_ht = <0x604>;
           lcd_hspw = <0x14>;
           lcd_vbp = <0x17>;
           lcd_vt = <0x27b>;
           lcd_vspw = <0x2>;
           lcd_dsi_if = <0x2>;
           lcd_dsi_lane = <0x4>;
           lcd_dsi_format = <0x0>;
           lcd_dsi_eotp = <0x0>;
           lcd_dsi_vc = <0x0>;
           lcd_dsi_te = <0x0>;
           lcd_frm = <0x0>;
           lcd_gamma_en = <0x0>;
           lcd_bright_curve_en = <0x0>;
           lcd_cmap_en = <0x0>;
           lcd_bl_en = <0x30 0x7 0xa 0x1 0x0 0xffffffff 0x1>;
           lcd_bl_en_power = "none";
           lcd_power = "vcc-mipi";
           lcd_fix_power = "vcc-dsi-33";
           lcd_gpio_0 = <0x30 0x3 0x18 0x1 0x0 0xffffffff 0x1>;
       };

The modified part is lcd_x and lcd_y.

3. reboot

When rebooted, a kernel panic has occurred.

Is there a mistake in the procedure?

Thank you.


  Defective? PCI-E -> SATA card no work good
Posted by: unregisteredidiot - 08-22-2018, 08:58 PM - Forum: General Discussion on ROCKPRO64 - Replies (11)

I'm excited about the RockPro64. It just arrived the other day. Sadly, I can't get the PCI-E -> Sata adapter card (also bought through Pine64) to work.

Symptoms:
System locks up hard when anything tries to touch a drive connected to the PCI-E SATA ports. Something as simple as `lspci -v` or `cfdisk /dev/sda` will lock the system and force a reset. Attempting to mount a partition has the same result.

Things I've ruled out:
It's not the drive. I tried multiple drives, all of which work fine in other systems. I was able to mount and use the same drives on my rockpro64 using an old usb2->sata adapter that I had lying around.
I don't think it's the OS images. I tried ayufan's lxde and minimal images, the latest stable 0.7.9 version.
I don't think it's this flaw: https://forum.pine64.org/announcements.php?aid=6 ... my board has a date stamp of 2018-06-06 and the schematics in that engineering notice do not match the power regulator design on my board.

Things I suspect:
I'm not an EE and it's likely that I don't know what I'm looking at, but I suspect there may still be a PCI-E power regulation defect in these boards. Yes, despite the hardware rev. `grep pcie /var/log/syslog` turns up lots of weirdness, including:


Code:
Jul 26 08:43:40 rockpro64 kernel: [    0.504648] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
Jul 26 08:43:40 rockpro64 kernel: [    0.504700] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [    0.504739] vcc3v3_pcie: supplied by dc_12v
Jul 26 08:43:40 rockpro64 kernel: [    0.504804] vcc3v3_pcie: 3300 mV
Jul 26 08:43:40 rockpro64 kernel: [    0.504959] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
Jul 26 08:43:40 rockpro64 kernel: [    2.854241] vcc3v3_pcie: disabling
Jul 26 08:43:40 rockpro64 kernel: [    3.185787] phy phy-pcie-phy.9: Looking up phy-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [    3.185794] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
Jul 26 08:43:40 rockpro64 kernel: [    3.242826] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
Jul 26 08:43:40 rockpro64 kernel: [    3.242833] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
Jul 26 08:43:40 rockpro64 kernel: [    3.242849] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
Jul 26 08:43:40 rockpro64 kernel: [    3.242997] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [    3.243058] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [    3.243063] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
Jul 26 08:43:40 rockpro64 kernel: [    3.243081] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
Jul 26 08:43:40 rockpro64 kernel: [    3.246321] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
Jul 26 08:43:40 rockpro64 kernel: [    3.246332] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
Jul 26 08:43:40 rockpro64 kernel: [    3.246349] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
Jul 26 08:43:40 rockpro64 kernel: [    3.249224] rockchip-pcie f8000000.pcie: invalid power supply
Jul 26 08:43:40 rockpro64 kernel: [    3.297572] PCI host bridge /pcie@f8000000 ranges:
Jul 26 08:43:40 rockpro64 kernel: [    3.312065] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
Jul 26 08:43:40 rockpro64 kernel: [    3.396326] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
Jul 26 08:43:40 rockpro64 kernel: [    3.399224] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
Jul 26 08:43:40 rockpro64 kernel: [    3.404688] pcie_pme 0000:00:00.0:pcie01: service driver pcie_pme loaded
Jul 26 08:43:40 rockpro64 kernel: [    3.404779] aer 0000:00:00.0:pcie02: service driver aer loaded
Aug 23 01:44:21 rockpro64 kernel: [  854.222319] Modules linked in: zram lz4_compress rockchip_saradc ip_tables x_tables autofs4 phy_rockchip_pcie midgard_kbase dw_hdmi_i2s_audio
Aug 23 01:48:14 rockpro64 kernel: [    0.502604] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc3v3-pcie-regulator[0]' - status (0)
Aug 23 01:48:14 rockpro64 kernel: [    0.502653] reg-fixed-voltage vcc3v3-pcie-regulator: Looking up vin-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [    0.502693] vcc3v3_pcie: supplied by dc_12v
Aug 23 01:48:14 rockpro64 kernel: [    0.502758] vcc3v3_pcie: 3300 mV
Aug 23 01:48:14 rockpro64 kernel: [    0.502914] reg-fixed-voltage vcc3v3-pcie-regulator: vcc3v3_pcie supplying 3300000uV
Aug 23 01:48:14 rockpro64 kernel: [    2.926112] vcc3v3_pcie: disabling
Aug 23 01:48:14 rockpro64 kernel: [    3.390905] phy phy-pcie-phy.9: Looking up phy-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [    3.390914] phy phy-pcie-phy.9: Looking up phy-supply property in node /pcie-phy failed
Aug 23 01:48:14 rockpro64 kernel: [    3.479972] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep
Aug 23 01:48:14 rockpro64 kernel: [    3.479988] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup
Aug 23 01:48:14 rockpro64 kernel: [    3.480049] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0)
Aug 23 01:48:14 rockpro64 kernel: [    3.480441] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [    3.480703] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [    3.480717] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed
Aug 23 01:48:14 rockpro64 kernel: [    3.480757] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found
Aug 23 01:48:14 rockpro64 kernel: [    3.489203] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree
Aug 23 01:48:14 rockpro64 kernel: [    3.489223] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed
Aug 23 01:48:14 rockpro64 kernel: [    3.489259] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found
Aug 23 01:48:14 rockpro64 kernel: [    3.497732] rockchip-pcie f8000000.pcie: invalid power supply

...halp? What do? I'm not sure how to troubleshoot this further. I'm 90% sure this is hardware related. If there is a known fix, I'm a steady hand with a soldering iron or a rework station. If there's not a known fix, is there a way to return this whole setup?


  CSI-2 MIPI
Posted by: astronomer - 08-22-2018, 04:18 PM - Forum: RockPro64 Hardware and Accessories - Replies (1)

Hi,

I'm designing a camera board to interface with the rockpro64 CSI-2 connector. Here're some questions I have because I could not find a hardware user guide for this board.

 1. What DVP_PDN stands for?
Pin 12 on the connector DVP_PDN1 and DVP_PDN0_H are each connected to a GPIO. Since MIPI_RST already has a RC delayed pull up for reset. I'm not sure what's this for. Or this can be used for any purpose?

2. I2C multiplexing
It appears all three connectors share a single I2C interface. Thus I'm not sure how it will be used if both sensor has the same slave ID especially in a dual cam HDR application. And it appears many Sony sensors shared the slave ID across variety of chips based on driver code on github.

3. Power voltage
I'm getting confused by the power voltage. On the connector it has two separate rails of 2.8V. Then a 1.2V and a 1.8V. But there's a note in the LDO section that says 1.8 is replaced with 2.8V? However many sensor out there, IMX214 included has one 1.8V. Can some engineer clarify this for me? Then there's a VCC5 and I assume that's constantly powered on?

Additional questions related to rock3399
4. CSI lane swapping
I can't find documentation on this. But many D-PHY is capable of lane swapping with register setting that controls the input MUX. I'm not sure if rock3399 has this capability. This will facilitate board layout.

Thanks!