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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,667
» Latest member: yipog39807
» Forum threads: 16,243
» Forum posts: 117,143

Full Statistics

Latest Threads
I think you can try compi...
Forum: General Discussion on Pinebook Pro
Last Post: wangyukunshan
8 hours ago
» Replies: 0
» Views: 42
Second screen mirroring
Forum: General
Last Post: OpalTromp
Yesterday, 09:53 PM
» Replies: 2
» Views: 1,705
kivy app keeping focus wh...
Forum: Mobian on PinePhone
Last Post: Kevin Kofler
Yesterday, 08:37 PM
» Replies: 1
» Views: 47
Optimizing Battery Life o...
Forum: General Discussion on PinePhone
Last Post: Kevin Kofler
Yesterday, 08:31 PM
» Replies: 1
» Views: 74
Wake up Call
Forum: General Discussion on PinePhone
Last Post: biketool
Yesterday, 02:35 PM
» Replies: 4
» Views: 227
How to add an homemade ap...
Forum: Mobian on PinePhone
Last Post: JChdeL
Yesterday, 04:13 AM
» Replies: 3
» Views: 291
Has anyone installed Tris...
Forum: General
Last Post: RandB
11-03-2025, 12:08 PM
» Replies: 1
» Views: 2,184
Xen hypervisor on Rock64
Forum: Linux on Rock64
Last Post: darkfader
11-03-2025, 09:25 AM
» Replies: 6
» Views: 9,694
[Article] RISC-V Ox64 BL8...
Forum: General
Last Post: smithjohns
11-03-2025, 12:54 AM
» Replies: 3
» Views: 9,470
Pinetab2s running DanctNI...
Forum: PineTab Software
Last Post: biketool
11-02-2025, 04:45 AM
» Replies: 0
» Views: 97

 
  Article: NuttX RTOS for PinePhone: USB with Enhanced Host Controller Interface
Posted by: lupyuen - 03-23-2023, 08:15 PM - Forum: PinePhone Software - Replies (2)

Weeks ago we talked about porting Apache NuttX RTOS (Real-Time Operating System) to PinePhone, and how we might turn it into a Feature Phone.

But to make phone calls and send text messages, we need to control the LTE Modem over USB. Thus today we’ll build a USB Driver for NuttX on PinePhone…

1. What’s USB Enhanced Host Controller Interface (EHCI)

2. Why it’s simpler than USB On-The-Go (OTG)

3. How we ported the USB EHCI Driver from NuttX to PinePhone

4. Handling USB Clocks and USB Resets on PinePhone (with tips from U-Boot Bootloader)

5. And the NuttX EHCI Driver boots OK on PinePhone!

NuttX RTOS for PinePhone: Simpler USB with EHCI (Enhanced Host Controller Interface)


  Suspend/Resume Broken with Bootloader on SPI Flash
Posted by: xp19375 - 03-23-2023, 06:35 PM - Forum: Linux on Pinebook Pro - Replies (2)

I previously posted about having broken suspend/resume by installing tow-boot to the SPI flash.  My workaround was to just not use tow-boot and erase the SPI flash.  However recently I got an NVMe drive and installed Slackware on it.  I'd like to be able to boot from the NVMe drive directly, which I gather requires a boot loader on the SPI flash (I'd like to keep Manjaro on the eMMC if possible).

My questions are, what boot loader does the PBP/Manjaro use by default when it comes from the factory?  What is it doing that allows suspend/resume to work while other boot loaders break it?  What setups do people use to boot from an NVMe drive and have working suspend/resume?


Photo My PinePhone Pro does not read the micro SD card at all.
Posted by: tux_life - 03-23-2023, 03:34 PM - Forum: PinePhone Pro Hardware - Replies (7)

Hi!
My PinePhone Pro does not read the micro SD card at all.
I tried booting from SD card as indicated here: https://wiki.pine64.org/wiki/PinePhone_Pro#Boot_from_microSD_card_temporarily.
I also tried holding the RE button.
Nothing works and the operating system does not detect any SD card.
The microSD card is inserted all the way...

[Image: gXPySj4G]

[Image: 7GmC3ZWs]


Sad PPP shuts off when reaching battery level >50% <70%
Posted by: crt0mega - 03-23-2023, 09:38 AM - Forum: PinePhone Pro Hardware - Replies (6)

Hi there,

has someone else experienced such weird behaviour?

I couldn't use my PinePhone Pro for months now because the reported battery level immediately crashes to 0% at some point between 50% and 70%, leading to a forced shutdown. Support says it has to be a software problem but I actually doubt that. The battery itself is working flawlessly in another phone and the issue persists even if I boot up the factory test build.

Any help leading to fix this issue (besides buying a new mainboard) is appreciated.

Thanks Smile


  Hide Swipe Up Arrow?
Posted by: jakfish - 03-22-2023, 09:56 AM - Forum: General Discussion on PinePhone - No Replies

With PP Beta/Manjaro Beta 30/kb, I use Alt-Tab to cycle programs. So the Swipe Up arrow just takes up screen real estate.

Through gsettings or elsewhere, can the Swipe Up arrow be hidden or disabled?


  Case for the rock64 that supports the POE hat.
Posted by: o1CRiMSON1o - 03-21-2023, 03:48 PM - Forum: Rock64 Hardware and Accessories - Replies (2)

I'm trying (and in vien) to find a case that supports the rock64 but has space to include the POE hat inside the case.

Has someone come across a case that supports this?


  Why do mouse, keyboard and HDMI not work with 3.th party usb-c adapters?
Posted by: Peter Gamma - 03-21-2023, 11:37 AM - Forum: PinePhone Accessories - Replies (3)

According to this video, different usb-c adapter work with the PinePhone pro, keyboard, mouse and HDMI:

https://youtu.be/NrOwj2JVlBU

Liliputing wrote on 10/23/2020 PostmarketOS brings HDMI update. But we tested 3 usb-c adapters with the Pinephone, all where usb-c  and powered, but mouse, keyboard and HDMI did not work with none of them. What could be wrong?


  Stuck on K logo
Posted by: mazanax - 03-21-2023, 06:13 AM - Forum: PinePhone Software - Replies (1)

Hey folks,

Recently I decided to install an update on my PinePhone, but something went wrong in the process and the phone just shut down.

Now when I try to turn it on, the yellow LED lights up, the phone vibrates and then hangs on the screen with the logo (the letter K and a gear wheel) and the mouse cursor appears.

I have tried connecting the phone to the computer (but nothing happens), pressing the volume buttons when turning it on, etc. but the result is always the same.

Could anybody help me with it?


  Having an issue flashing my 0x64. Invalid literal for int() with base 16
Posted by: 3BeetMassacre - 03-20-2023, 07:21 PM - Forum: General - Replies (1)

First, I apologize for posting in the General forum but couldn't find the Ox64 section.

Any ideas on how to remedy this?


Win 10 pro
Dev Cube 1.8.3
Using firmware dated 2 weeks ago
Silicon Labs CP2104 USB to UART Bridge

Following the instructions on the Github page found HERE

Dev Cube MCU page flashing m0 and d0 was successful but then moved to the IOT tab of Dev Cube in order to flash the BL808-firmware.bin to address 0x800000 and received the following error:

TL;DR version



Code:
invalid literal for int() with base 16: ''
Traceback (most recent call last):
File "libs\bflb_eflash_loader.py", line 3568, in efuse_flash_loader_do
ValueError: invalid literal for int() with base 16: ''

Full Log


Code:
[13:23:18.624] - ========= Interface is Uart =========
[13:23:18.624] - eflash loader bin is eflash_loader_auto.bin
[13:23:18.639] - Version: eflash_loader_v2.4.5
[13:23:18.639] - Program Start
[13:23:18.655] - ========= eflash loader cmd arguments =========
[13:23:18.655] - C:\Users\****\Desktop\New folder\chips\bl808\eflash_loader/eflash_loader_cfg.ini
[13:23:18.655] - Config file: C:\Users\****\Desktop\New folder\chips\bl808\eflash_loader/eflash_loader_cfg.ini
[13:23:18.655] - serial port is COM4
[13:23:18.655] - cpu_reset=False
[13:23:18.655] - chiptype: bl808
[13:23:18.655] - ========= Interface is uart =========
[13:23:18.655] - com speed: 2000000
[13:23:18.655] - Bootrom load
[13:23:18.655] - ========= get_boot_info =========
[13:23:18.655] - ========= image get bootinfo =========
[13:23:20.770] - ack is
[13:23:20.770] - Not ack OK
[13:23:20.770] - result:
[13:23:21.051] - tx rx and power off, press the machine!
[13:23:21.051] - cutoff time is 0.05
[13:23:21.113] - power on tx and rx
[13:23:22.110] - reset cnt: 0, reset hold: 0.05, shake hand delay: 0.1
[13:23:22.110] - clean buf
[13:23:22.110] - send sync
[13:23:22.643] - ack is 4f4b
[13:23:22.690] - shake hand success
[13:23:23.191] - data read is b'01000808000000000b14c102991335cf0eb458002ff4fb18'
[13:23:23.191] - ========= ChipID: b40ecf351399 =========
[13:23:23.191] - Get bootinfo time cost(ms): 4535.835205078125
[13:23:23.191] - clock para file: C:\Users\****\Desktop\New folder\chips/bl808/efuse_bootheader/clock_para.bin
[13:23:23.191] - change bdrate: 2000000
[13:23:23.191] - Clock PLL set
[13:23:23.191] - clock para:
[13:23:23.191] - 5043464707040000030103000102000201010001010101010a894b86
[13:23:23.191] - Set clock time cost(ms): 0.0
[13:23:23.347] - Read mac addr
[13:23:23.347] - flash set para
[13:23:23.347] - get flash pin cfg from bootinfo: 0x04
[13:23:23.347] - set flash cfg: 14104
[13:23:23.347] - Set flash config
[13:23:23.347] - Set para time cost(ms): 0.0
[13:23:23.347] - ========= flash read jedec ID =========
[13:23:23.347] - Read flash jedec ID
[13:23:23.347] - flash jedec id: ef601800
[13:23:23.347] - Finished
[13:23:23.363] - Program operation
[13:23:23.363] - Dealing Index 0
[13:23:23.363] - invalid literal for int() with base 16: ''
Traceback (most recent call last):
File "libs\bflb_eflash_loader.py", line 3568, in efuse_flash_loader_do
ValueError: invalid literal for int() with base 16: ''
[13:23:23.378] - Burn Retry
[13:23:23.378] - 0
[13:23:23.378] - Burn return with retry fail


  None Pine64 USB-C Docking Bar?
Posted by: Peter Gamma - 03-20-2023, 10:25 AM - Forum: PinePhone Accessories - No Replies

I made a quick test with a none Pine64 USB-C Docking Bar. It has a USB-C charging port, where I attached the power source. Then it has a HDMI port and two USB-C connectors. I plugged it into my PinePhone with pmOS over usb-c, and then plugged in a HDMI monitor, a usb mouse and a usb keyboard. None of the peripherals worked out of the box.

Is the Pine64 USB-C Docking Bar a miracle bar with miracle software and the one and only docking bar, or should also other docking bars work? Or does eventually installation of drivers help to get my non Pine64 docking bar to work?