| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
04-19-2026, 12:56 PM
» Replies: 13
» Views: 14,640
|
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
04-18-2026, 10:08 AM
» Replies: 0
» Views: 77
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:17 PM
» Replies: 24
» Views: 18,999
|
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:12 PM
» Replies: 1
» Views: 1,047
|
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,299
|
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 236
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 9,022
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 340
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 148
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 218,270
|
|
|
| Pinebook Pro won't turn on |
|
Posted by: codebreaker - 10-31-2019, 01:52 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (62)
|
 |
I just received my Pinebook Pro. I opened the box, and hit the power button, but nothing happens. I plugged the charger in, and I see a tiny LED near the barrel connector that is red, but then it turns off after about a minute. No other lights come on, and after a half hour of being plugged into the charger, the unit still won't power on. Any suggestions?
|
|
|
|
| DestinationLinux show episode 145 - interview with Luke |
|
Posted by: ndp - 10-31-2019, 04:40 AM - Forum: General
- Replies (1)
|
 |
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
|
|
|
|
| Battery discharge curve |
|
Posted by: ayke - 10-30-2019, 04:04 AM - Forum: Development Discussion on PineTime
- Replies (15)
|
 |
I fully charged my PineTime and then started measuring the battery voltage until it was completely empty. Here is the chart:
![[Image: pinetime-battery-log-plot.svg]](https://aykevl.nl/download/pinetime-battery-log-plot.svg)
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.
|
|
|
|
| Pine phone Hardware features, "Wish-List" |
|
Posted by: bcnaz - 10-29-2019, 05:10 PM - Forum: PinePhone Hardware
- Replies (16)
|
 |
*
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 .
|
|
|
|
| Brave Heart Edition Pre-orders |
|
Posted by: Rocky-IV - 10-29-2019, 02:55 PM - Forum: PinePhone Hardware
- Replies (2)
|
 |
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
|
|
|
|
Rock64 stuck in boot, please help! |
|
Posted by: Malmgren - 10-29-2019, 02:46 AM - Forum: Linux on Rock64
- Replies (7)
|
 |
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:
Code: "System is booting up. Unprivileged users are not permitted to log in yet. Please come back later. For technical details, see pam_nologin(8)."
Connection closed by 192.168.168.8
So it's obviously stuck somewhere in the boot process, but I don't know where and why. Anyone can think of any other way to access it? It's booted from eMMC and unfortunately I have got no other way to read eMMC.
It's running Debian Buster, if it's of any help.
edit: Ok, you might call me stupid, but I just realized that I've got a hdmi port that I've never used. Plugged in my tv and a keyboard and thought I'd find the solution. Still stuck though. I can see the kernel booting and the network getting up, but then nothing more happens. No errors, no nothing. I can switch TTY with the keyboard (ctrl+alt+F2 etc) but that's about it (the other tty's are black). Wtf?
|
|
|
|
| HW setup with an LPC-Link2 in CMSIS-DAP mode |
|
Posted by: aaribaud - 10-28-2019, 03:51 PM - Forum: PineTime Tutorials
- Replies (2)
|
 |
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:
Code: source [find interface/cmsis-dap.cfg]
source [find target/nrf52.cfg]
telnet_port 4444
Name this file appropriately -- I named mine pinetime-lpc-link2-cmsis-dap.cfg.
Now run OpenOCD. In Linux, I run
Code: openocd -f pinetime-lpc-link2-cmsis-dap.cfg -c init
At this point, if your PineTime still contains the factory firmware, it will be access-protected, i.e. you cannot read from it or write to it yet. You'll know it's the case if OpenOCD says "Error: Could not find MEM-AP to control the core".
If your PineTime is access-protected, you'll have to unprotect it before you can program it. This will remove the factory firmware, but it will have to go at some point, right? So open a second terminal, connect to OpenOCD using for instance
Code: telnet localhost 4444
Now issue the following command:
If the value displayed is 0x00000000 then your PineTime is indeed access-protected, and you can unprotect it by issuing
Code: dap apreg 1 0x04 0x01
then
to which OpenOCD should eventually display
Code: nrf52.cpu: hardware has 6 breakpoints, 4 watchpoints
... and that is the sign that your PineTime is unprotected and now ready to be reprogrammed!
|
|
|
|
| Pinebook 11" Keyboard |
|
Posted by: Corkonian - 10-28-2019, 04:54 AM - Forum: Pinebook Hardware and Accessories
- Replies (2)
|
 |
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....
|
|
|
|
|