I just watched the DestinationLinux podcast interview with Luke, in which he spoke at length about Pinebook, Pinebook Pro, PineTab, PinePhone, Pinetime, and his aspirations for creating a converged hardware platform for Pine64 offerings . 

This is a fascinating insight into the great work that the Pine64 team AND all of the team's developer partners are doing.

All of us in the Pine64 community are so fortunate to have these great people working so hard on our behalf.

Here is the link to the show:

https://destinationlinux.org/episode-145/


Enjoy 

hello,

Can the pinebook Pro m.2/ngff nvme SSD interface adapter support Toshiba tc500?
can boot OS from this ssd?

thanks!

I fully charged my PineTime and then started measuring the battery voltage until it was completely empty. Here is the chart:

You can see the raw data here. It contains two axis: the x axis is the raw 12-bit ADC value and the y axis is the number of seconds since measuring started.

As for methodology: I charged the PineTime for about 3 hours so it must be completely full. Before measurements started, there was maybe a gap of one or two minutes. The screen was on all the time (refreshing every ~10 seconds) and LCD_BACKLIGHT_HIGH was on all the time as well. The CPU was in sleep mode most of the time between displaying the results. However, it was connected with a debug wire which AFAIK prevents the CPU from going to sleep. Measurements were sent to the host using ARM Semihosting.
To my surprise, it still took almost 7 hours for the battery to run empty.

This data could be useful for developing a discharge indication algorithm for the PineTime.

*
1) Phone Service
2) SMS Service
3) Internet Service  Hot spot/tethering capable  
4) Isolated/Independent GPS service
5) Screen - big enough to view comfortably
6) Battery - Bigger is Better,  easy to replace even Better
7) Decent speaker(s) Absolutely must be able to "Hear" !

 These are the Features I personally consider "Important to Me"

The numbers are just because it is a list,  but if you cannot hear it what good is phone service ?
  So number 7 is as important as number one.
As far as size goes, the larger the device, can house a larger antenna, Reception improves with size,
  though transmission does require calibrated length antenna .

Hello

Just wondering if the pre-order date of November 1st is current reality or a dream ... Shall the Pine Store be accepting orders for PinePhone Brave Heart edition on November 1st.
Or should community members expect further delays. 
I know the personnel in charge of Pine64 are dedicated and working to give us the best service

Thanks

Hi.
Tonight my Rock64 was unexpectedly shut down (UPS ran out of battery) and after that it doesn't seem to boot and I don't know how to get in to it. It answers on SSH port, but when trying to log in I get:

If you have an LPC-Link2 lying around, you can use it to debug/develop on the PineTime dev kit.

First, you need to flash a CMSIS-DAP firmware on the LPC-Link2. NXP has these.

If you're using the wires provided with the PineTime, then you will need to populate the J6 location on the LPC-Link2; it's the only one which expects a pin header. I fitted a 9-pin right-angle header.

Then you have to properly match the PineTime SWD pinout to the J6 header pins. Gnd goes to pin 8, Vcc to pin 1, SWDIO to pin 2 and SWDCLK to pin 3.

Last, you have to put jumpers on both JP1 and JP2 of the LPC-Link2. JP1 will make it boot on its internal firmware and thus act as a CMSIS-DAP probe; JP2 will power the SWD signal buffers. If you forget JP2, OpenOCD will recodgnize the probe but not the PineTime.

Then you need a configuration file for OpenOCD. This file should contain the following:

For those of us getting on in years and small displays harder to read, is the pseudo analog display only an option that can be switched to a simple large font digital time and date?

soyrunner

For reasons unbeknownst to me, the first row of the alphanumeric keyboard (1234....) packed in. Some random letters in the other rows as well.
Any clue on how to solve that as I want the Pinebook to survive at least until the Pro arrives....

(I've initially intended to ask in the Linux-specific sub-forum, but I guess this is not limited to Linux only. Corrections welcome)

To be ready for un-bricking my horrible experiments that are bound to come, I'm slowly working on gathering information on how this wonderful creature boots.

Mrfixit (thanks!) clarified on IRC that the u-Boot bootloader is stored in an off-set on the eMMC, not directly accessible (~not in one of the two actual partitions, I assume).
So my questions would be:
- Where is it exactly?
- How do I find it?
- How do I recognize that I have actually found it?


I have also had a look at the ChromiumOS image, and in it, there are two interesting files in /boot: boot.scr and bootloader.bin.
(disclaimer: I'm away from the PBP and SD card, so I may be misremembering the filenames. Corrections will follow.)
When I run "file boot.scr", this is identified as an u-Boot bootloader image. The other file is simply data.
==> this brings a side-question: can the bootloader then be stored completely in the /boot partition? Or am I misunderstanding the purpose of these two files?

Upon further googling and reading, I've stumbled upon these links:
https://linux-sunxi.org/Bootable_SD_card
https://linux-sunxi.org/Mainline_U-Boot

These suggest specific places on the eMMC for the location of u-boot. I have also noticed that there are "gaps" at the beginning of the mmcblk1 disk and between the two "readable" partitions.
I've tried to copy various amounts of data from the above start locations using dd into a file and then tried to identify them with "file", but had no luck so far.

Am I looking into the wrong place?
Am I applying a completely wrong approach to find and identify u-Boot?

Ultimately, the question can be boiled down to: Once I have a u-Boot binary, where do I put it on the disk?
Apologies if these questions are too dumb, but I sort of figured this might be useful to document somewhere on the forums/wiki.