I am sure I have seen the procedure to transfer an existing image on a sd card to a bootable ssd connected to USB 3 but cannot find the detail. Can you help please. What format should I use on the ssd. The image I wish to transfer is ubuntu 18.04 LXDE. I am using this to run opencpn navigation sofware with ais overlay and it runs well.

I am attempting to SPL over FEL so I can load a BL32 by hand (sorry if this reads as jargon).  I am on mainline u-boot and using sunxi-fel spl uboot/spl/sunxi-spl.bin.  It begins attempting to boot and then says:

Hi everyone,

I drafted a Brave Heart welcome letter and would appreciate your feedback. Is something missing? should something be phrased differently? Let me know.

[edit] I redrafted the letter based on your suggestions. Tried to squeeze as much as I could in the little space a page permits. Feedback please - don't have much time to get this to TL.

Quote:Dear Piner,

Congratulations on receiving your Brave Heart edition PinePhone! 

You are one of the very first to have a PinePhone and we hope you’ll help us and our partner projects by testing, contributing to, and documenting the development progress. Thank you!

Brave Heart phones come preloaded with a factory test software and nothing else, so you’ll have to seek out the OSs you’re interested in on your own. Most mobile distributions OS images are linked on the PinePhone subsection of the PINE64 Wiki (wiki.pine64.org). 

The PinePhone Wiki subsection also contains schematics, instructions, hardware configuration details and other useful information about your device. You can edit and contribute to the Wiki by logging in using your forum credentials. We encourage you to do so.  

Since this is fundamentally a community project, we strongly suggest you join the #pinephone chat, accessible via Telegram, Discord, IRC and Matrix (NB. all chat protocols are bridged). You can find links to the chat on PINE64 Wiki and under the Forums and Chats tab our main site (pine64.org). Your input is valuable regardless of if you’re a tester, developer or just an enthusiastic end-user, so it is important that you join the conversation.

Most partner projects - a list of which can be found under Partner Project tab on our site - also have discussion threads or chats dedicated to the PinePhone. So if you’re interested in one particular OS, and wish to contribute to it, then make sure to check out the forums and/or chats of the project in question.  

Brave Heart is meant for early-adopters - developers and enthusiasts - so we expect and even encourage you to experiment with the software and hardware by pushing the envelope. That said, please keep in mind that the device is under standard warranty, so braking components during disassembly or tampering with eFUSEs is a subject to voiding of your warranty. We trust this is common sense. 

Now, have fun with your PinePhone!  

PINE64 Community Team

Quote:Dear Piner,

Congratulations on receiving your Brave Heart edition PinePhone! 

You are one of the very first to have a PinePhone and we hope you’ll help us and our partner projects by testing, contributing to, and documenting the development progress. Keep in mind that all OSs are presently in a pre-release (Alpha) state and vary in functionality, even from one pre-release to another.   

Your input is valuable so it is important that you report problems you encounter and join the conversation on whatever platform suits you best. When you report problems make sure to also include relevant logs and/or UART outputs. 

You can report non-OS specific (kernel) issues you encounter on: https://gitlab.com/pine64-org. OS specific problems should be reported on the PINE64 Wiki (wiki.pine64.org/PinePhone#Software Support) as well as directly to developers in the pinephone chats (Forums and Chats tab on https://pine64.org), on PINE64 forums (forum.pine64.org) or on the relevant partner-project forums (see Partner Projects tab on https://pine64.org). 

Brave Heart phones come preloaded with a factory test software and nothing else, so you’ll have to seek out the OSs you’re interested in on your own. Most mobile distributions OS images are linked on the PinePhone subsection of the PINE64 Wiki. OS builds absent from Wiki may require you seek them out by talking to developers directly.

The PinePhone Wiki subsection also contains schematics, instructions, hardware configuration details and other useful information about your device. You can edit and contribute to the Wiki by logging in using your forum credentials. We encourage you to do so.  

Brave Heart is meant for early-adopters - developers and enthusiasts - so we expect and even encourage you to experiment with the software and hardware by pushing the envelope. That said, please keep in mind that the device is under standard warranty, so braking components during disassembly or tampering with eFUSEs is a subject to voiding of your warranty. We trust this is common sense. 

Now, have fun with your PinePhone!  

PINE64 Community Team

Anyone received confirmation that their ANSI pinebook pro has shipped? Is December dispatch no longer a reality?

Hello:

I want to compile a driver for an external long range wifi and it needs the kernel header files.
The synaptic package list for Debian installs for kernel version 4.9 and not 4.4 as required.

Thanks,

Crusty

PBP ARM Processor RECOGNIZED by Default Debian OS Synaptic Package Manager?  
I have begun learning to handle my December 2019 PBP Debian, all updated, by starting the Synaptic Package Manager, and learning to install a few apps.  To my surprise the SPM seems to recognize the PBP ARM processor and installs an ARM version of any software chosen?  The GVIM app actually even displays that it is an ARM version!  Is it a fact that SPM does detect the processor type, and will install only those apps provided as ARM binaries?

PBP Displayed Clock-Calendar Drops Hour Setting On Reboot or shutdown.  Clock appears to hold minutes correctly, but not hour of the day.  Almost acts like the PBP fails to hold Time Zone setting across reboots, one must reset the time each time one reboots.  Does PBP have a battery held time chip?  My PBP was just delivered to me early this month, December; and was delivered with the Debian OS.

I'm trying to figure out what binary blobs exist in the PinePhone.

The Allwinner A64 has many GPL violations:

Quote:Kernel:

• lichee/linux-3.10/modules/aw_schw/libschw
  
• lichee/linux-3.10/modules/nand/sun50iw1p1/libnand_sun50iw1p1
  
• lichee/linux-3.10/drivers/input/touchscreen/aw5x06/libAW5306
  
• lichee/linux-3.10/drivers/video/sunxi/disp2/hdmi/libhdmi_sun50iw1
  
• lichee/linux-3.10/drivers/media/platform/sunxi-vfe/lib/lib{isp,mipicsi2_v1,mipicsi2_v2}
  

U-Boot:
(Only u-boot-2014.07 is checked here)

• lichee/brandy/u-boot-2014.07/arch/arm/cpu/armv8/wine/dram/libdram-homlet
  
• lichee/brandy/u-boot-2014.07/arch/arm/cpu/armv8/wine/dram/libdram-pad
  
• lichee/brandy/u-boot-2014.07/arch/arm/cpu/armv7/sun50iw1p1/dram/libchipid
  
• lichee/brandy/u-boot-2014.07/arch/arm/cpu/armv7/sun50iw1p1/dram/libdram
  
• lichee/brandy/u-boot-2014.07/drivers/video/sunxi/disp2/hdmi/libhdmi_sun50iw1
  
• lichee/brandy/u-boot-2014.07/nand_sunxi/sun50iw1p1/libnand-sun50iw1p1
  

Problem Statement

In an x11 terminal if you press Shift-` or Shift-3, or AltGr-4, you do not get the expected characters.

And if you open a console (Ctrl-Alt-F1) and login, and you press Shift-`, or Shift-3, or AltGr-`, or AltGr-4, you again do not get the expected characters.

Disclaimer/Recognition

The solution provided below works on the default Debian desktop that is shipped with the Pinebook Pro. Thanks @Mrfixit2001  and @Luke for your work on crafting this.

Solution

You will need an internet connection to install a package (console-setup) farther down.

Confirm you have the problem by checking the keys as described in the Problem Statement above, this could potentially be fixed in a later version of the default Debian desktop.

Open a terminal in an x11 session (the second icon from the left next to the Menu button) and run the following:

Hi all,

I've seen a lot of people struggling flashing images to sd cards/emmc from the command line and even more people asking for support after flashing images improperly or without media verification. I wrote a script to make this process easier, hopefully it will reduce the number of problems people are experiencing.

The script handles both raw images (.img files) and xz compressed images and will write and then verify, or with the --verify-only flag simply verify, that your media has been written correctly.

The script is located here: https://github.com/foundObjects/sbc-flasher

Installation is simple, either download the script and optionally make it executable and place it somewhere in your path or just run the installer code below. If pv isn't installed in your distribution by default you'll need to install it if you want pretty progress meters. The installer will ask for sudo permission to install the script in /usr/local/sbin as needed, so there's no need to run it with sudo or as root.