http://files.pine64.org/doc/rockpro64/ro...21-SCH.pdf
"PCIe x4"-page 27

Please refer to the above page
What we want to pay attention to is the series of parts attached to the signal "PCIE_RX3P / PCIE_RX3P".
(These parts are not a typographical mistake in the circuit diagram. These parts are actually mounted.)

----

I would like to ask someone with hardware experience.
Is it allowed to add such parts to high-speed signal lines that require strict impedance matching?
In the first place, what is the significance of adding these parts?

If such a component is added to a high-speed signal line such as "PCIEx"
The signal amplitude that passes is greatly reduced, and it can be presumed that the eye pattern at the receiving end will be severe.
And all cards of type "x4" are actually affected.
For example, "nvme", but it goes without saying that the impact is not limited to this.

I own 3 "rockpro64" units. (2 units are unstable or limited)
And I actually removed the parts described above for these.
The result is as expected,
It was confirmed that all three units were operating stably, including two units that were originally unstable (crash or limited-Link).
---

Another product, for example:
"pinebookpro_v2.1_mainboard_schematic.pdf"
Does not include the parts described above.
And it is the same for other manufacturers.
From this, it is clear that these additional parts are not due to restrictions in "RK3399".

I think it is a complete mistake in circuit design.
Perhaps they forgot to remove the parts that were added for operation verification at the prototype stage.

For some aggrevating reason something keeps changing my resolv.conf, even though I've specified dhcp address only in network manager and set dns servers.

Resolv always gets set to:

I was so happy that I got the Rockpro64 working including Wifi. But I soon found it's not stable at all. I was listening to some internet radio with SMplayer and suddenly I heard the Rockpro crashed and couple seconds later screen went total black. Only thing I could do is remove the power supply and put it back to reboot.

First I thought maybe SMplayer was fooling around but even on a new fresh reboot I left the rockpro days on to see what will happen. And sometimes after couple days it crashed again. And onetime I had it for 11 days up no problem until it went black again. 

This is my Rockpro version:
Linux rockpro64 4.4.167-1213-rockchip-ayufan-g34ae07687fce #1 SMP Tue Jun 18 20:44:49 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux

Anyone also had these kind of problems? 

In the future I would like to run small things 24/7 on the Rockpro and need a stable one for that.

Thanks

Hello to the few of you in the same situation as me. As Luke suggested last week, I emailed the pine team to get an update on my order. I placed my order back in September and received an email in late October saying that my order would be shipping soon. Since then I haven't received any information from DHL. This is the response from the pine team in case some of you didn't get one: 


Hello there,

Thanks for your message.
We apologize as our China dispatch team was delayed the estimate shipping date on last week due to the civil unrest in Hong Kong.
They will try to travel to Hong Kong on this week to dispatch the Pinebook Pro if the civil unrest nearby our warehouse is calm down.

Appreciated for your patient and sorry for any inconvenience caused.

If you need further help, please do not hesitate to let us know.

We will be more than happy to assist you.


Have a great day.

Thanks. 
 
Sincerely,
[b]PINEBOOK Team[/b]
[u]http://www.pine64.org[/u]

I ordered my pinephone, and I am now thinking how to connect extra hardware to this pocket PC.
What I found so far is this (the 6in1 version):

https://nl.aliexpress.com/item/4000183847600.html


The big question, is this going to work with the pinephone?

In the sellers text there are 3 chips mentioned:

RTL5411 (3x USB3-hub)
VL102 (PD-port)
IT6563 (HDMI port)

What to do, ordering it now so I got it hopefully at the same time as the pinephone arrives, or better buy something else?

I am trying to get the [unsupported] armbian image to load from eMMC on my pine h64 model b.  The armbian image 

https://dl.armbian.com/pineh64/archive/A..._5.1.15.7z

seems to work like a charm on SD, but I'd like to get the os onto eMMC for faster io.  I have been able to get the Android eMMC and AOSC builds to boot from eMMC on this board, but I'd really prefer Armbian, just because it is a known and will be similar to the rock64 boards I have running Armbian.

However, flashing the image directly onto eMMC doesn't seem to work.  Trying to boot just gives me a black cursor on the serial console.  No activity at all, no u-boot or anything.  As far as I can tell, this should work.  The image seems to have the correct `eGON.BT0` header at the right offset in the image, so I presumed it would have/should have booted.  But no dice

I am new to u-boot, but took a stab at building and installing it onto the eMMC for the h6 anyway, using as a guide: 

http://linux-sunxi.org/Mainline_U-Boot

After following the instructions, building u-boot on a rock64 (targeting the h6), and writing it to the eMMC at the 8kb offset, I pop the card onto the h6.  

However on boot I end up with :

Quote:U-Boot SPL 2020.01-rc2-00035-g3ff1ff3ff7 (Nov 17 2019 - 10:16:56 +0000)
DRAM: 4096 MiB
Trying to boot from MMC2

Title.


I would like to post Tab Porn there.

Please correct me if this has been discussed elsewhere, but has Brave Heart edition Pinephones been through FCC och CE testing? Just curious

Edit: or I'll just wait for the phone to arrive and I can just look at the back of the phone for a mark

This may be a n00b question but I am slightly puzzled about this:

I assume - in my naivety - that the Linux kernel abstracts away all hardware details from a distributions system services and applications. Thus, if there already is a kernel for the Rockchip 3399 platform, why is it that there are competing efforts (default mrfixit Debian 9 vs. ayufan Ubuntu 18) where the hardware support is not identical?

I would assume every distribution is supposed to work exactly the same in terms of hardware support as long as you put the same kernel underneath. Where am I going wrong?


Also, what is the main challenge to port the up-to-date arm64 Linux kernel to the rk3399 platform? I would have assumed the vanilla kernel is missing device drivers that are specific to the rk3399 board or the Pinebook Pro as a whole but could not these be added (either right into the kernel or as modules)?

Please understand this is not critique but simply me trying to get a better insight. So far I have only used Linux distributions but never worried about kernel versions etc...

Hi Everyone,

I did a one of these casual updates last month and thought that it would be a good idea to do one this month too. I won't be writing them every single month, but when there is something noteworthy happening - like now - I feel they serve a purpose.

Speaking of updates, the December update will be the last one of the year (obviously) and I'll run a poll a week prior to it being posted asking about how we did this year and what you'd like us to improve on in 2020. Keep a lookout for that, because we really like to hear back from you on this.

Pinebook Pro

We have the firmware for the Pinebook Pro trackpad & keyboard. I am running a little update thread here for those interested. Long story short, the process of flashing the new firmware is currently quite involved and we're thinking of ways to make it relatively painless. Both @xalius and @ayufan have been instrumental in working these things out - thanks guys! Ayufan is currently rewriting the flashing software based on the source, so the flashing process will either be fully or partly automated when end-users get it in their hands. Future PBPs will ship with this firmware already flashed.

[edit 26/11/2019] Trackpad fix is out and available here.

PinePhone

The Brave Heart edition is up for per-order right now. [sarcasm] The launch went smoothly without incidents Those of you who waited up / woke up to be there at zero-hour are sworn to secrecy and required to hold the line that it all went flawlessly [/sarcasm]. Congrats on getting your pre-orders in.  

Approximately half of all PinePhones have now sold so I expect that all will be gone by the end of this week.
Developer's phones keep shipping and are going out steadily albeit slower than we'd (and probably developers) hoped. A large portion of the dev phones will go out this week.

Behind the scenes a lot of debugging, testing and tweaking is going on to make sure that we can deliver the best early-adopter's phone possible. I'll leave the details for next months update. I should have my PinePhone (still pre-production rather than Brave Heart Edition) at the end of the month, and intend to record a video about it. If there are some things you'd like to see in this video - leave it in the comment below.

PineTab

In this month's update I asked if you'd like us to run an early adopters batch for the PineTab. The response to my query was very positive and the number of requests for making this happen was surprisingly large. As a result, its happening. The production of and early adopters batch of PineTabs has now began. I don't really have any other details to offer at this time; we probably going to wait until all the Brave Heart PinePhones ship before making arrangements for the PineTab. We still need a suitable OS to accompany this batch ... so it may yet take some time.  


PineTime

PineTime development has taken off and I've been super impressed by the progress. In recent weeks we've seen some spectacular write-ups too, like this one by Lup Yuen Lee. What makes so many of these write-ups interesting is that people don't always use the PineTime 'the way we envisaged', which frankly speaking is great and exciting.

As I have already indicated in the past on the forum, blog, chats and elsewhere - we were considering making the PineTime dev kits widely available, but were unsure of how many people would actually want one. As it turns out, a lot of people do. And this is good news, since this is a truly experimental side-kick community project.  So in the coming days we'll be making PineTime kits available for purchase from the Pine Store.