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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,729
» Latest member: Rsquared
» Forum threads: 16,272
» Forum posts: 117,244

Full Statistics

Latest Threads
irradium (based on crux l...
Forum: Linux on Quartz64
Last Post: mara
2 hours ago
» Replies: 7
» Views: 14,486
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: Rsquared
4 hours ago
» Replies: 6
» Views: 452
Shipping Update and Stock...
Forum: News
Last Post: hk123
6 hours ago
» Replies: 93
» Views: 149,766
SSH over USB
Forum: PineNote Software
Last Post: PYXY
9 hours ago
» Replies: 3
» Views: 1,293
Booting Issues
Forum: PineNote Software
Last Post: PYXY
Yesterday, 03:29 PM
» Replies: 21
» Views: 15,515
PinePhone USB-C port and ...
Forum: PinePhone Hardware
Last Post: Kevin Kofler
Yesterday, 08:57 AM
» Replies: 3
» Views: 6,013
No telephone call audio, ...
Forum: PinePhone Pro Hardware
Last Post: biketool
Yesterday, 08:06 AM
» Replies: 5
» Views: 193
camera not usable with tr...
Forum: Mobian on PinePhone
Last Post: JChdeL
Yesterday, 01:45 AM
» Replies: 0
» Views: 47
No touch KB after update(...
Forum: Mobian on PinePhone
Last Post: biketool
Yesterday, 01:15 AM
» Replies: 4
» Views: 430
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
12-04-2025, 05:20 PM
» Replies: 13
» Views: 6,184

 
  auto-owning the SD card in DanctNIX (Pinetab2)
Posted by: biketool - 10-09-2025, 05:55 AM - Forum: PineTab Software - Replies (1)

What is the most elegant way to get the Pinetab to both auto mount and own the SD card to user [alarm] ?
I have it auto mounting the SD card using settings but because user alarm doesn't own the SD card device/mount point I cant use it normally.
I could chown it but that would have to happen every bootup.
(edit) I will probably edit /etc/fstab but that is skill learned maybe 25 years ago and I expect that in systemb days there is probably something automatic and I dont want to break that.

I have not wiped and loaded Mobian despite using that for my Pinephone there doesnt seem to be enough clear instruction to get everything working, it feels like the shipped DanctNIX OS has the most functionality.


That said I would in any fully Linux OS really love to have the bluetooth and cameras fully functional as well as a smart way to setup a NMEA USB GPS device for navigation.


  Hohlbuchse
Posted by: slon1975 - 10-08-2025, 01:17 PM - Forum: Deutsche Sprache - No Replies

Hallo! Ich habe nach ca.2 Jahren teilweise kein Kontakt mehr über den Hohlstecker- Anschluss. Pinecil v2 geht ständig an und aus, spielt verrückt und einmal die Spitze zum Glühen gebracht. Vom einfachen Löten ist da gar keine Rede mehr. Macht kein Spaß mehr die Situation.
Stecker selbst ist von Reichelt und made in Japan. Die Abmessungen passen genau zur Buchse. Qualität von der Buchse lässt wohl zu wünschen übrig. Kann mir bitte jemand sagen wo man passendes Ersatzteil besorgen kann? 
Vielen Dank im voraus.


  trixie update poll questions suggestions
Posted by: j_s - 10-04-2025, 04:58 PM - Forum: Mobian on PinePhone - Replies (5)

I want to post a poll asking whether or if they are updating trixie installs once they find a weekly build that mostly works for them. It seems like polls almost always omit some important op tion, so I am going to throw some out there and am asking for suggested improvements and additions. The question is addressed to users, not developers/testers.

If you have mobian trixie installed, do you regularly update it?

1. Yes, with apt(-get) or the Software app.

2. Yes, by reflashing a more recent weekly build.

3. Yes, other reason (please specify in a post).

4. No, I don't want to risk breakage and don't want to reflash or wait for a fix.

5. No, other reason (please specify in a post).


  Update pinetime bootloader OTA?
Posted by: oscar-gardiazabal - 10-04-2025, 03:25 PM - Forum: Development Discussion on PineTime - Replies (1)

Hi, I'm trying to upload a modified pinetime bootloader using the reloader-mcuboot-1.0.1.zip from https://github.com/InfiniTimeOrg/pinetim.../tag/1.0.1
I tried with the simplest test possible changing the version of the header to 2.0.0 in the reloader-mcuboot.bin of the reloader-mcuboot.zip with:
"printf '\x02\x00\x00\x00\x00\x00\x00\x00' | dd of=reloader-mcuboot.bin bs=1 seek=$((0x14)) conv=notrunc"
and build it again with the same command of the Makefile:
"python3 -m nordicsemi dfu genpkg --dev-type 0x0052 --application reloader-mcuboot.bin reloader-mcuboot.zip"
After uploading the zip with Watchmate for Linux I got the image is ok but the InfiniTime shows the same version for the bootloader "1.0.1".
It is still possible to update the bootloader OTA? I'm missing something? Thank you!
Last try was using: Python 3.10.13, adafruit-nrfutil version 0.5.3.post16


Lightbulb Product idea: Pinebank, 18650 multifunction power bank/speaker/light/etc
Posted by: cowsay - 10-03-2025, 11:35 AM - Forum: General - No Replies

Hello .. just passing along a product idea. It is a product that doesn't exist that I've always in the back of my mind wished for.  

I dub it the Pinebank. It is a versatile, open source, extensible, multifunction power bank that uses off-the-shelf replaceable 18650s for serviceability and long term utility.  

Maybe low power RISC-V under the hood like the pinecil

Here is a 18650 DIY power bank for some additional inspiration https://www.youtube.com/watch?v=_PBr_jUA4Iw

The hypothetical Pinebank at its core it has 3 primary functions: Power bank, light, speaker

General use cases:
* General purpose power bank
* Bluetooth speaker
* Flashlight
* Work light
* Diffuser cap for lantern operation (power outages, camping, etc)
* Strobe for emergencies, maybe even red light beacon option
* Display function: clock, alarm, weather, radio

Some ideas (some possibly as pluggable module/daughterboard addons): 
* AM/FM/NOAA weather
* Connections for solar panels for off grid/emergencies
* SDR/Radio transceiver/antenna for radio geeks/search and rescue
* WWAN
* Lora
* It's a stretch, but it's possible that it could even be used to jumpstart a car or pump up your tires.  Like this product https://halo.acgbrands.com/en_US/bolt-ai...phite.html

Since it has a processor, you could use it as a little low powered micro server. Lots of options here.



Perhaps it is not possible to cram in ALL of these features, I'm just airing ideas.

I think something like this would be incredibly useful.  Seems like a good fit for Pine.   Cool


Question Simulating a touch through the command line
Posted by: babygnu - 10-03-2025, 10:50 AM - Forum: PineNote Software - Replies (1)

Hi all,

First time poster! Excited to be here!

I'm working on a project where my pine note is networked to my computer. I want to control software on my pinenote that does *not* have command line access, from my computer. 

Seems the best way to do this is to simulate a touch on the pinenote.

Anyone know how to do this?

Thanks for reading my query!

- BabyGNU


  U-Boot env save error
Posted by: r4ms - 10-03-2025, 06:40 AM - Forum: PineNote Hardware - Replies (1)

There seems to be a hard coded mistake in uboot. "env save" uses parition 4 (Logo) instead of 3:

=> env save                             
Saving Environment to FAT...

** Unable to use mmc 0:4 for saveenv **


I haven't found any way to change the partition. Is there any?


  Bonk to boot
Posted by: biketool - 10-01-2025, 02:17 AM - Forum: General Discussion on Pinebook Pro - Replies (2)

So my year and a half old PPp has started to have an issue where it wont come out of sleep, this has happened before it is related to the power/wake button not showing up in the system a reboot or two has always fixed this issue.
Now though the regular from fully off boot activators (USB power or power button) but a good smack on my hand and the boot process starts.  I have to guess there is a loose ribbon cable somewhere, any ideas what the issue is?


  Does PinePhone support long-term battery health optimization?
Posted by: roseblack - 09-30-2025, 09:09 PM - Forum: General Discussion on PinePhone - Replies (5)

Hi everyone,
I’m curious if the PinePhone has (or will have) any built-in feature or community tool to help optimize long-term battery health, like charging limits (e.g., stopping at 80%) or adaptive charging. I know some laptops and modern smartphones have this option, and it really helps prolong battery life.

Has anyone experimented with something similar on the PinePhone, or is it more a matter of manually managing charging?


Sad USB Gadget on PineTab2
Posted by: Tronar - 09-26-2025, 12:42 PM - Forum: PineTab Software - No Replies

Dear Piners,

has anybody of you tried to get a USB gadget working for the second USB interface on the PineTab2? This is a fully functional OTG interface that you can use for much more than only charging. Anyway, as long as you don't connect an OTG cable, it will reside in device mode, so it should be possible to program USB gadgets following such instructions:
https://openwrt.org/docs/guide-user/hardware/usb_gadget
https://trac.gateworks.com/wiki/linux/OTG
https://developer.toradex.com/linux-bsp/...ode-linux/
https://www.kernel.org/doc/Documentation...nfigfs.txt
https://github.com/torvalds/linux/blob/m...usb-gadget
Based on these (and some other web sites) I contrived a script for a mass storage gadget. First I prepared an 8 GB big container file using these commands:

Code:
dd if=/dev/zero of=/stick.img bs=1M count=8192
fdisk /stick.img
# Inside fdisk I prepared the image using the following keys:
# o x s 32 h 128 c 4096 r n p 1 \n \n t c p w
losetup -o 1M /dev/loop0 /stick.img
mkfs.vfat /dev/loop0
mount -t vfat /dev/loop0 /mnt
echo hallo >/mnt/test.txt
umount /mnt
losetup -d /dev/loop0
The following script intends to simulate a USB stick on the device mode USB port:
Code:
#!/bin/sh
cd /sys/kernel/config/usb_gadget
mkdir g1
sleep 1
cd g1

echo 0x1d6b >idVendor  # reserved for the Linux Foundation
echo 0x0104 >idProduct  # multifunction is sufficient
#echo 0x0615 > bcdDevice  This is preset for some reason.
echo 0x0200 > bcdUSB    # USB 2.0
# Is the following correct for a flash stick?
echo 0x08 > bDeviceClass
echo 0x06 > bDeviceSubClass
echo 0x80 > bDeviceProtocol
#echo 0x62 > bDeviceProtocol
echo 0x40 >bMaxPacketSize0
echo high-speed >max_speed

# The following strings can be chosen freely; for the serial number I take the
# actual SN of my PineTab2.
cd strings
mkdir 0x409 && cd 0x409
sleep 1
cat /proc/device-tree/serial-number >serialnumber
echo Pine64 >manufacturer
echo PineTab2\ v2.0 >product
# Alternatively one could also use some of the information in
# /sys/bus/i2c/drivers/husb311/0-004e to fill in the above.

cd ../../configs
mkdir c.1 && cd c.1
sleep 1
mkdir strings/0x409
sleep 1
echo "Memory stick emulation based on image file" >strings/0x409/configuration
# German:
mkdir strings/0x407
sleep 1
echo "Speicherstick-Emulation mit einer Image-Datei" >strings/0x407/configuration
echo 0xc0 >bmAttributes  # self-powered
echo 2 >MaxPower        # probably irrelevant when self-powered

cd ../../functions
mkdir mass_storage.usb0
sleep 1
cd mass_storage.usb0
echo 1 >stall
cd lun.0
echo /stick.img >file
echo 0 >removable
echo 1 >nofua
cd ../../..
ln -s functions/mass_storage.usb0 configs/c.1
sleep 1

# and now make it active:
ls /sys/class/udc >UDC

# to unbind it: echo "" >UDC; sleep 1; cd ..; rm -rf g1
# in emergency: echo 1 >functions/mass_storage.usb0/lun.0/forced_eject
Several of these settings are not absolutely necessary, also the sleep statements; they reflect only my desperate attempts to get it working. When I execute it, not having anything connected to the USB port yet, I see these lines in my dmesg:
Code:
Mass Storage Function, version: 2009/09/11
LUN: removable file: (no medium)
dwc3 fcc00000.usb: failed to enable ep0out
Why "removable"? Why "no medium"? What exactly "failed" w.r.t. endpoint 0?

Then I connect my PineTab2 to a PC's USB-2 port, which results in four more lines in the dmesg:
Code:
typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=0 usb_host=0 dp=0
typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=1 usb_host=0 dp=0
typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=0 usb_host=0 dp=0
typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=1 usb_host=0 dp=0
The dmesg of the PC is full of errors then:
Code:
usb 4-10: new high-speed USB device number 5 using xhci_hcd
usb 4-10: device descriptor read/64, error -71
usb 4-10: device descriptor read/64, error -71
usb 4-10: new high-speed USB device number 6 using xhci_hcd
usb 4-10: device descriptor read/64, error -71
usb 4-10: device descriptor read/64, error -71
usb usb4-port10: attempt power cycle
usb 4-10: new high-speed USB device number 7 using xhci_hcd
usb 4-10: Device not responding to setup address.
usb 4-10: Device not responding to setup address.
usb 4-10: device not accepting address 7, error -71
usb 4-10: new high-speed USB device number 8 using xhci_hcd
usb 4-10: Device not responding to setup address.
usb 4-10: Device not responding to setup address.
usb 4-10: device not accepting address 8, error -71
usb usb4-port10: unable to enumerate USB device
Obviously the gadget isn't functional. When I unplug the cable again, the PC's dmesg shows nothing, the PineTab2's just the ususal extcon stuff:
Code:
typec-extcon typec-extcon: extcon changed sdp=1 cdp=0 dcp=0 usb=0 usb_host=0 dp=0
typec-extcon typec-extcon: extcon changed sdp=0 cdp=0 dcp=0 usb=0 usb_host=0 dp=0
The worst thing I observe when I try to switch off the gadget again using echo "" >UDC; it seems to be some kind of crash:
Code:
dwc3 fcc00000.usb: wait for SETUP phase timed out
dwc3 fcc00000.usb: failed to set STALL on ep0out
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5177 at dwc3_ep0_out_start+0xc8/0xe0
Modules linked in: aes_ce_ccm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device zram aes_ce_blk aes_ce_cipher polyval_ce polyval_generic ghash_ce bes2600(C) sm4 sha2_ce sha256_arm64 sha1_ce snd_soc_simple_amplifier mac80211 st_accel_i2c st_sensors_i2c libarc4 ov5648 st_accel st_sensors v4l2_fwnode dw9714 snd_soc_simple_card v4l2_async cfg80211 snd_soc_simple_card_utils phy_rockchip_inno_csidphy snd_soc_rockchip_i2s_tdm snd_soc_rk817 rfkill snd_soc_hdmi_codec snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer hantro_vpu snd v4l2_vp9 v4l2_jpeg v4l2_h264 rockchip_rga videobuf2_dma_contig soundcore v4l2_mem2mem videobuf2_dma_sg videobuf2_memops videobuf2_v4l2 videodev videobuf2_common mc joydev mousedev sch_fq_codel crypto_user loop fuse nfnetlink ip_tables x_tables ipv6 crc_ccitt dw_hdmi_cec panfrost dw_hdmi_i2s_audio drm_shmem_helper gpu_sched hid_multitouch
CPU: 0 UID: 0 PID: 5177 Comm: bash Tainted: G        C          6.15.2-danctnix2-1-pinetab2 #1 PREEMPT(full)  2075623fc0cc7105688baa1cc4ca060147351f05
[ 3357.684396] Tainted: [C]=CRAP
[ 3357.684413] Hardware name: Pine64 PineTab2 v2.0 (DT)
[ 3357.684434] pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 3357.684464] pc : dwc3_ep0_out_start+0xc8/0xe0
[ 3357.684504] lr : dwc3_ep0_out_start+0x4c/0xe0
[ 3357.684535] sp : ffff80008778ba70
[ 3357.684552] x29: ffff80008778ba70 x28: ffff00010088b900 x27: 0000000000000000
[ 3357.684605] x26: 0000000000000000 x25: 0000000000000000 x24: ffff00013c924840
[ 3357.684655] x23: ffff0001039f0810 x22: 0000000000000000 x21: ffff000100b76990
[ 3357.684705] x20: ffff000100b76880 x19: ffff00010434f200 x18: ffff8000842730b8
[ 3357.684755] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000006
[ 3357.684804] x14: 0000000000000000 x13: ffffffffffff3f08 x12: ffff800081cd3d70
[ 3357.684854] x11: ffffffffffff3f04 x10: ffff800081cd3dc8 x9 : ffffffffffff3f00
[ 3357.684905] x8 : ffffffffffff3f0c x7 : ffff80008435d000 x6 : 0000000000000000
[ 3357.684954] x5 : ffff800081c4f000 x4 : 0000000000000000 x3 : 0000000000000000
[ 3357.685003] x2 : 0000000000000000 x1 : ffff00010088b900 x0 : 00000000ffffff92
[ 3357.685054] Call trace:
[ 3357.685073]  dwc3_ep0_out_start+0xc8/0xe0 (P)
[ 3357.685118]  dwc3_ep0_stall_and_restart+0xb4/0xe0
[ 3357.685158]  dwc3_ep0_reset_state+0x68/0xa0
[ 3357.685194]  dwc3_gadget_soft_disconnect+0x13c/0x1d0
[ 3357.685231]  dwc3_gadget_pullup+0x8c/0x138
[ 3357.685267]  usb_gadget_disconnect_locked+0x4c/0x170
[ 3357.685303]  gadget_unbind_driver+0x54/0x158
[ 3357.685334]  device_remove+0x54/0x90
[ 3357.685371]  device_release_driver_internal+0x1d4/0x240
[ 3357.685407]  driver_detach+0x54/0xc0
[ 3357.685440]  bus_remove_driver+0x78/0x108
[ 3357.685472]  driver_unregister+0x38/0x78
[ 3357.685506]  usb_gadget_unregister_driver+0x28/0x50
[ 3357.685538]  gadget_dev_desc_UDC_store+0xc0/0x150
[ 3357.685580]  configfs_write_iter+0xcc/0x130
[ 3357.685617]  vfs_write+0x24c/0x388
[ 3357.685658]  ksys_write+0x78/0x120
[ 3357.685695]  __arm64_sys_write+0x24/0x40
[ 3357.685734]  invoke_syscall+0x6c/0x100
[ 3357.685777]  el0_svc_common.constprop.0+0x48/0xf0
[ 3357.685817]  do_el0_svc+0x24/0x38
[ 3357.685846]  el0_svc+0x2c/0x138
[ 3357.685883]  el0t_64_sync_handler+0x10c/0x140
[ 3357.685916]  el0t_64_sync+0x160/0x168
[ 3357.685951] ---[ end trace 0000000000000000 ]---
Also, I can't delete the directory tree of my gadget in the configfs: not permitted.

Further observations:
* After this disaster I can plug a USB stick into this very socket using an OTG cable. It works, switches to host mode and mounts the stick.
* Also, charging the PineTab2 will work as always.
* The message "dwc3 fcc00000.usb: failed to enable ep0out" always shows up, also when I try other configurations, e.g. the script here near the bottom of the page (8814.usbconfigfs.sh.txt for an acm gadget):
https://e2e.ti.com/support/processors-gr...-am62x_dts

My questions:
a) Has anybody got a working USB gadget of any flavour (mass_storage, acm, ecm, ...) on the PineTab2? Please show me your script or tell me my mistake.
b) Could this be a broken kernel driver? Should I report an issue to danctnix?
c) Can you reproduce the problem on your own PineTab2 using my script?

Sorry for this terribly long write-up.

Any ideas?