I recently (early January) got my ANSI keyboard PBP, including the serial console cable I ordered. Based on other threads I knew the cable had an incorrect 5V signal level, but I wanted to investigate the situation a bit more myself.

So I looked at the schematics and RK3399 SoC datasheet, and realized that the UART signal voltage isn't 5V, but it isn't 3.3V either, as other threads have said... It's actually supposed to be 3.0V!

If you trace the signal from the headphone jack through the schematic, it leads you to the lower right corner of page 10:



This helpfully shows this group of pins on the SoC can be configured as 1.8V or 3.0V, but based on the connection of pin APIO4_VDD to 3.0V (see green circle) and a quick look at the datasheet, I concluded that in the PBP the correct voltage is 3.0V. These UART signals do go through U7002 to switch the jack between headphone and serial modes, but that does nothing to convert voltages.

I double-checked the voltage with a voltmeter on the PBP's TX line, which also indicated 3.0V.

My next question was whether the SoC could tolerate 3.3V on these pins, but I checked the datasheet and it indicates a maximum of 3.15V:



So not only is 5V too high, but so is 3.3V!

Unfortunately, 3.0V isn't a standard voltage for USB serial cables, and I didn't find any commercially available (but I didn't look too hard). And since I already had the 5V one from Pine64, I decided to mod it!

Here's the schematic of my mod. Original is in pencil; my changes are in blue:



There are conceptually two changes:

1. Previously, the receive line had a 4.7K pullup resistor to 5V. I changed this to use a voltage divider that pulls up to 3V and has roughly the same impedance as the original, using an 8.2K resistor to 5V and a 12K resistor to ground. You could probably get away with leaving the 4.7K resistor in and just adding a 7K resistor to ground instead.
   
2. I added a voltage divider on the transmit line to create 3V output signals using a 240 ohm series resistor and a 360 ohm resistor to ground.
   

Hello Pine64 Community,

since Oracle has no available option for Java 11 for Arm64 I was asking and looking for different ways and sources.

I found out that Azul Systems (https://www.azul.com/downloads/zulu-comm...ackage=jdk)
and also Bellsoft (https://bell-sw.com/pages/java-11/) both distribute a Java Version that is made for Arm64 Systems and thus should work for Pinebook Pro.

Nevertheless, since I am quite a novice I was not able to properly install them and make them work.
Is it even possible to install them on the Pinebook Pro and make Java 11 work for Arm64 (yet)?

When I tried to install from the terminal there was no executable option to install (e.g. like configure)
When I tried to install via package installer the option to install was greyed out.

It would be so great if one of you could answer my questions or even help me work around my problem.
Maybe someone could provide me with a "how to" or "step by step" support as Iam currently about to give up.


Thanks!

Hi all.

Who is interested to meet in London on Sat 25 Jan 2020 to discuss all things pine?

Here is a link to gettogether, an open source Meetup.com alternative:
https://gettogether.community/events/402...in-london/

As location the Café in the Science Museum is planned

I could bring the OG Pjnebook, Pinebook Pro and PineTime

In @Luke's stickied post, a fix for the NVME adapter was mentioned. 

Two questions:

1. As part of the 2nd community batch of PBP shipments, if you ordered an adapter with your PBP and received one, will you be automatically receiving the parts required for the NVME adapter fix?
   
2. What are the timelines for the new parts to ship?
   

Hello! I seem to have possibly messed up my ANSI layout PBP but I'm not sure what I might have done or what the problem is exactly.

I was booting from a microSD of the Manjaro ARM KDE 19.12 eMMC Installer image found here https://osdn.net/projects/manjaro-arm/st...sma/19.12/ and all seemed to be going well. I selected the eMMC device and it ran through the xz decrypt and flashed the eMMC steps fun but then it said press any key to continue and when I pressed a key nothing happened.

I have tried booting from other images on the microSD and this problem now seems systemwide. The keyboard and trackpad simply do not work anymore. Furthermore, a mouse and keyboard that I have confirmed are working on other devices simply get no power from the PBP anymore. I've also removed the battery and powered on from mains and the problem persists.

This is puzzling to me because the power button (which seems to be part of the nonworking keyboard) still works fine and the computer itself has no problem booting from either eMMC or from microSD.

I'd really like to be able to fix this, but I don't have the knowledge to diagnose the issue.

Just got my PBP yesterday.  Most of the stuff looks good.  One big problem I am having is that the
down-arrow cursor key is not working so well.  Like it's registering double-touches when I hit it once, or thinking I'm holding it down when I press it briefly.  It's making it quite frustrating when I have to navigate text-mode menus (which I've found myself doing a few times).

Anybody else having this problem?
Is it already discussed in another thread that I can't find?

I'm running version 1.9 of the OS according to /usr/share/myver
I've done the keyboard/trackpad firmware upgrade, and I think it went fine, but I'm not sure how to double-check that (I suppose I could just try to run it again).

Just thought I'd share for anyone else trying to figure this out. Enabling Natural Scrolling for Manjaro XFCE in the touchpad settings panel does not currently work. You can however, set it via the command-line according to the Arch Wiki. I'm not sure if this is the best/appropriate way to fix the issue, but it did work for me:


1. Using the package manager, install the xorg-xinput package, which contains the xinput utility

2. From the terminal, run the following command and note the ID number for the Touchpad:

Can anyone confirm if their tracking link displays accurate information?  The tracking number that I received shows that my order was shipped February of 2019 from Zürich, then went to Hong Kong, then arrived in Switzerland on the 20th, and has now been marked as "Expired." (See attached)

Not sure if the system is just glitchy, the shipment went wrong, or I'm missing something.  Thanks!

Attached Files

  Tracking.png (Size: 31.49 KB / Downloads: 1288)
  ExpiredExplanation.png (Size: 15.75 KB / Downloads: 920)

I really wanted to have a top of the line open source, with 1Tb of internal space and with input for MicroSD and DualSIM.

Hey all! 

I've been digging into the keyboard firmware recently and trying to figure out how it all works, and luckily it's been pretty straight-forward 8051 assembly. I've started writing some pseudo-code to figure out the flow and data that's being read from the memory. From all that, it's been pretty easy to tackle some of the issues people have been reporting in the forums and Github, and I've put together a "revised" version of the binaries that contain some modifications that you might enjoy:

• Corrected Fn+F9-12 keys for ANSI (ISO version didn't have this issue)
  
• Arrow (and other) keys work with the Pine (GUI) key
  
• NumLock is respected only in the Fn layer, i.e. NumLock can be left on all the time
  
• Privacy switches now send keycodes when being enabled/disabled, for working into scripts/notifications: