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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,976
» Latest member: georgeolive34
» Forum threads: 16,335
» Forum posts: 117,443

Full Statistics

Latest Threads
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
Yesterday, 10:08 AM
» Replies: 0
» Views: 47
Booting Issues
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:17 PM
» Replies: 24
» Views: 18,915
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:12 PM
» Replies: 1
» Views: 1,035
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,272
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 217
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,963
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 318
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 144
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 218,053
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 275

 
  PineTime Developer Kit
Posted by: futurejones - 11-27-2019, 05:45 PM - Forum: PineTime Hardware and Accessories - Replies (8)

I would like to get involved in the development of PineTime. There was mention in the forums that the developer kit would be available in the store but I can't find it anywhere. How do I get a developer kit?
Thanks.


  U-Boot with direct NVMe boot support for eMMC/SPI Flash
Posted by: pcm720 - 11-27-2019, 03:34 PM - Forum: General Discussion on Pinebook Pro - Replies (125)

Update (08/07/2020):
Now there's also an option to use mainline U-Boot (v2020.07) with reference ARM Trusted Firmware, no need to use Rockchip blobs anymore.
You can build it yourself using this repository and flash the image as usual (flash_erase + dd works for Manjaro):

https://github.com/pcm720/u-boot-build-scripts

The build script uses patches from dhivael, sigmaris and Manjaro.
v2020.07 binaries for SD/eMMC and SPI Flash are available as well, you can find them on Releases page of the repo.
The resulting SPI image works on my PBP and boots from NVMe just fine.
Boot priority is SD -> eMMC -> NVMe -> USB, and there's no need to destroy U-Boot on SD card anymore.

---------
While it's possible to place the boot partition on eMMC and use NVMe as rootfs, the lack of NVMe support in stock U-Boot kept bugging me, so I decided to do something about it.

So, by porting Rockchip PCIe patches from Radxa and backporting some NVMe patches from upstream U-boot, I was able to get NVMe support going on mrfixit2001's fork and now can successfully boot from my NVMe drive:

[Image: nrnCuS0.png]

You can find binary images for SD/eMMC/SPI flash and source code here.
Note that the current SPI image has issues when booting pre-made images from SD card.

For some reason Rockchip's SPL tries (and fails) to initialize trust mode with the microSD, so you'll have to zero out the bootloader, U-Boot and ATF on your SD card with the following commands:

Quote:dd if=/dev/zero bs=32k seek=1 count=1 of=<microSD>
dd if=/dev/zero bs=64k seek=128 count=64 of=<microSD>
dd if=/dev/zero bs=64k seek=192 count=64 of=<microSD>
The first command corrupts Rockchip's SPL, and second and third zero out U-Boot and ATF, respectively.

In other words, the microSD must not contain any of the bootcode. The same most likely goes for the eMMC.

As usual, I am not responsible for any damage or data loss caused by using these images. They work for me.
Don't flash it if you don't know how to recover from damaged bootloader and can't be bothered to search for recovery options.

If you're flashing the SPI image, make sure that all 16 Mbytes are accessible and that it can be flashed properly before doing anything.
If something doesn't look right, try using Manjaro. That's what I used to flash it to my device.


Question Android Phone Setting Managed By Administrator?
Posted by: TDC_PBP - 11-27-2019, 02:48 PM - Forum: Chromium OS on Pinebook Pro - Replies (1)

As I was exploring Chromium settings, I stumbled across the connected devices tab, with the setting to connect your android phone to the laptop underneath it. It is, however, greyed out, saying "This setting is enforced by your administrator." Is that just its way of saying that isn't supported right now? As far as I know the administrator of my PBP is me...


  how to attach video file to forum post
Posted by: richfm - 11-27-2019, 10:04 AM - Forum: General Discussion on Pinebook Pro - Replies (2)

I'm trying to attach a video file screen capture of how my wifi reception decreases when I move away from the gateway. I've tried several files with sizes under the attachment limit (under 2 MB), with ogv and mkv formats but get an error message

"Please correct the following errors before continuing:

  • The type of file that you attached is not allowed. Please remove the attachment or choose a different type."
How can I attach this video to a post in this forum?


  Ubuntu mate boot failure
Posted by: hdk - 11-27-2019, 09:58 AM - Forum: Linux on Pinebook Pro - Replies (3)

Ubuntu mate, during boot (the fast text command scrolling):
7613770 fixing recursive fault but reboot is needed.

I have to hold the power button down for longer time to reboot.


Lightbulb Keyboard Shortcut Suggestion
Posted by: User 11436 - 11-27-2019, 04:08 AM - Forum: Pinebook Pro Hardware and Accessories - Replies (1)

Hi,

Maybe I'm getting old and senile, but I keep forgetting the keyboard shortcuts to disable/enable the camera, microphone, and WiFi. On future iterations of the keyboard, it might be an idea to place symbols on the bottom left of the F10-12 keys.

Ben


  Pinebook Pro 'xtreme'
Posted by: bcnaz - 11-26-2019, 12:43 PM - Forum: General Discussion on Pinebook Pro - Replies (60)

   ***
 Now that the Pinebook Pro is being perfected,

   How about a :   'Pinebook Pro Extreme'   ?

  1) a 19" Wide screen
  2) Maybe dual batteries
  3) Able to boot from the NVMe
  4) Larger Speakers that point up from the palmrest
 
   That would likely attract a lot of attention,
    
        Of Course it would cost a bit More,,,
 
   but it likely attract even more potential high end customers.

               
                   Just a thought  ?


***     "More than a utility device,  an entertainment center"  !    (?)   ***


  Using Crouton to install Arch
Posted by: tophneal - 11-26-2019, 12:13 PM - Forum: Chromium OS on Pinebook Pro - Replies (3)

I wanted to share this, after trying so many different forks. For anyone interested in using crouton to install Arch, refer to this fork of chroagh. I tried/edited about 4 other forks, but this buried beauty has actually allowed me to install aarch64 Arch within Chromium.

Since it's outdated, you'll likely need to run sudo enter-chroot -n [chroot name] -u root in order to be able to login/finish setup.


  Raspberry Pi Piface2 board installed on a Pine64?
Posted by: coolio - 11-26-2019, 11:39 AM - Forum: Accessories - No Replies


.jpg   2434230-40.jpg (Size: 11.22 KB / Downloads: 713) Hello,

I'm wondering if anyone has installed and configured a Piface2 Digital Input Output board on a A64 Pine 1GB board?
The Piface2 was originally designed for the Raspberry Pi A+ and B+ models.


Here's a link to the Piface datasheet:  
http://www.farnell.com/datasheets/188155...1574787277

Any help would be appreciated.
Dave


  Wrong resolution on external monitor
Posted by: vfr400racer - 11-26-2019, 06:55 AM - Forum: Pinebook Pro Hardware and Accessories - Replies (2)

When I connect a monitor via hdmi port (which resides on a USB-C hub), the Pinebook Pro decides to choose a wrong resolution. dmesg shows, that the monitors resolution of 1680x1050  is announced, but the set to a lower resolution of 1024x768. What can I do to keep the monitors resolution? I append the dmesg's output:

Code:
[ 1964.973219] wl_run_escan: LEGACY_SCAN sync ID: 25, bssidx: 0
[ 2084.964338] wl_run_escan: LEGACY_SCAN sync ID: 26, bssidx: 0
[ 2204.970521] wl_run_escan: LEGACY_SCAN sync ID: 27, bssidx: 0
[ 2324.974063] wl_run_escan: LEGACY_SCAN sync ID: 28, bssidx: 0
[ 2444.977071] wl_run_escan: LEGACY_SCAN sync ID: 29, bssidx: 0
[ 2454.324170] fusb302 4-0022: attention, dp_status 9a
[ 2454.324587] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected, not enabled. Enabling cdn
[ 2454.725233] rockchip-vop ff8f0000.vop: [drm:vop_crtc_enable] Update mode to 1680x1050p0, type: 10
[ 2454.730653] cdn-dp fec00000.dp: 2700Mbps x 2lanes
[ 2517.578690] rockchip-pm-domain ff310000.power-management:power-controller: Looking up pd_vopb-supply from device tree
[ 2517.578721] rockchip-pm-domain ff310000.power-management:power-controller: Looking up pd_vopb-supply property in node /power-management@ff310000/power-controller failed
[ 2517.613120] fusb302 4-0022: attention, dp_status 19a
[ 2517.613518] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected, not enabled. Enabling cdn
[ 2517.640606] rockchip-pm-domain ff310000.power-management:power-controller: Looking up pd_vo-supply from device tree
[ 2517.640636] rockchip-pm-domain ff310000.power-management:power-controller: Looking up pd_vo-supply property in node /power-management@ff310000/power-controller failed
[ 2517.714332] fusb302 4-0022: attention, dp_status 19a
[ 2517.839090] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected with sink. Re-train link
[ 2517.842296] cdn-dp fec00000.dp: 2700Mbps x 2lanes
[ 2517.876548] rockchip-vop ff8f0000.vop: [drm:vop_crtc_enable] Update mode to 1024x768p0, type: 10
[ 2517.918330] rockchip-vop ff900000.vop: [drm:vop_crtc_enable] Update mode to 1024x768p0, type: 14
[ 2517.944504] rockchip-dp ff970000.edp: [drm:analogix_dp_link_start] Enable downspread on the sink
[ 2517.949571] rockchip-dp ff970000.edp: Link Training Clock Recovery success
[ 2517.952185] rockchip-dp ff970000.edp: Link Training success!
[ 2531.066030] fusb302 4-0022: attention, dp_status 19a
[ 2531.066231] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected, not enabled. Enabling cdn
[ 2531.094537] rockchip-vop ff900000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 14
[ 2531.133833] rockchip-dp ff970000.edp: [drm:analogix_dp_link_start] Enable downspread on the sink
[ 2531.136888] rockchip-dp ff970000.edp: Link Training Clock Recovery success
[ 2531.138341] rockchip-dp ff970000.edp: Link Training success!
[ 2531.166542] fusb302 4-0022: attention, dp_status 19a
[ 2531.287242] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected with sink. Re-train link
[ 2531.290530] cdn-dp fec00000.dp: 1620Mbps x 2lanes
[ 2531.337748] rockchip-vop ff8f0000.vop: [drm:vop_crtc_enable] Update mode to 1024x768p60, type: 10
[ 2555.807734] rockchip-vop ff900000.vop: [drm:vop_crtc_enable] Update mode to 1024x768p0, type: 14
[ 2555.850406] rockchip-dp ff970000.edp: [drm:analogix_dp_link_start] Enable downspread on the sink
[ 2555.854127] rockchip-dp ff970000.edp: Link Training Clock Recovery success
[ 2555.856205] rockchip-dp ff970000.edp: Link Training success!
[ 2564.976728] wl_run_escan: LEGACY_SCAN sync ID: 30, bssidx: 0
[ 2633.016519] rockchip-vop ff900000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p0, type: 14
[ 2633.056441] rockchip-dp ff970000.edp: [drm:analogix_dp_link_start] Enable downspread on the sink
[ 2633.060114] rockchip-dp ff970000.edp: Link Training Clock Recovery success
[ 2633.061728] rockchip-dp ff970000.edp: Link Training success!
[ 2664.782286] fusb302 4-0022: attention, dp_status 19a
[ 2664.782612] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected, not enabled. Enabling cdn
[ 2664.858662] rockchip-vop ff900000.vop: [drm:vop_crtc_enable] Update mode to 1024x768p0, type: 14
[ 2664.882869] fusb302 4-0022: attention, dp_status 19a
[ 2664.883537] rockchip-dp ff970000.edp: [drm:analogix_dp_link_start] Enable downspread on the sink
[ 2664.887178] rockchip-dp ff970000.edp: Link Training Clock Recovery success
[ 2664.888755] rockchip-dp ff970000.edp: Link Training success!
[ 2665.005392] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Connected with sink. Re-train link
[ 2665.008731] cdn-dp fec00000.dp: 1620Mbps x 2lanes
[ 2665.076362] rockchip-vop ff8f0000.vop: [drm:vop_crtc_enable] Update mode to 1024x768p0, type: 10
[ 2684.979849] wl_run_escan: LEGACY_SCAN sync ID: 31, bssidx: 0
[ 2691.393900] rockchip-vop ff900000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p0, type: 14
[ 2691.435076] rockchip-dp ff970000.edp: [drm:analogix_dp_link_start] Enable downspread on the sink
[ 2691.439657] rockchip-dp ff970000.edp: Link Training Clock Recovery success
[ 2691.442173] rockchip-dp ff970000.edp: Link Training success!
[ 2804.979824] wl_run_escan: LEGACY_SCAN sync ID: 32, bssidx: 0
[ 2907.896835] fusb302 4-0022: attention, dp_status 1a
[ 2907.897251] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] Not connected. Disabling cdn
[ 2924.980531] wl_run_escan: LEGACY_SCAN sync ID: 33, bssidx: 0
[ 2969.465450] r8152 8-1.2:1.0 eth0: Stop submitting intr, status -71
[ 2969.467386] fusb302 4-0022: connection has disconnected