| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,476
» Latest member: alain
» Forum threads: 16,197
» Forum posts: 116,882
Full Statistics
|
|
|
| A64 LTS Boot Sequence? |
|
Posted by: Robert2020 - 07-16-2023, 02:49 AM - Forum: General Discussion on PINE A64-LTS / SOPINE
- No Replies
|
 |
Hi,
I want to run my own hobby bootloader/ kernel on the A64. Sadly I couldn't find any information about the new boards LTS variant boot sequence.
There ist he non A64 LTS version of the linux-sunix wiki but the new one doesn't have a section for the boot sequence so I'm wondering wether it's the same.
Next to that, I was also wondering where excatly and in what EL the BROM bootloader is loading my binary from the SD Card to. My assumption would be that I would endup in EL3 somewhere (0x8000 maybe) in DRAM, does that come close?
regards robert
|
|
|
|
| Star64: jtag debugging? |
|
Posted by: bluepill - 07-15-2023, 10:29 PM - Forum: Getting Started
- Replies (1)
|
|
I'm thinking of getting a Star64 to do some practical learning about operating system development and I haven't been able to find some clear/simple information about compatible equipment and the process for setting up a jtag debugging environment. Please note that my experience is mostly with software and I am really, really new to working so close to the hardware.
The Star64 schematics show GPIO pins 0 to 4 for debug trace and pins 9 to 13 for jtag HIFI4 (audio DSP). From the very little that I know about jtag this is the minimum number of pins - so minimum amount of jtag functionality.
I have been looking at the Segger J-Link Edu because it has support for the U74 and E24 SiFive cores in the Star64, but I'm not sure if it is a good choice.
Has anyone setup jtag debugging for the Star64? What hardware/software are you using and can you recommend a beginners guide that can get me started?
|
|
|
|
| eMMC upgrade |
|
Posted by: EuvzO8 - 07-15-2023, 02:08 PM - Forum: PinePhone Hardware
- Replies (5)
|
|
Has anyone tried to replace stock eMMC (16Gb or 32Gb) with a bigger eMMC (in a phone repair shop for example)? Is it possible? What models are compatible?
|
|
|
|
| Lots of problems with pinebuds |
|
Posted by: elix - 07-15-2023, 09:25 AM - Forum: General
- Replies (1)
|
|
I got my pinebuds yesterday and out of the box they didn't work correctly. They continuously cut out making them unusable. I tried resetting them and they wouldn't even reset. I hit the reset button in the middle, the charging LEDs flash, close the lid and nothing.
I tried flashing new firmware in a docker on my pinebook pro and couldn't because its not arch64. Which I find ironic that I have to have a windows machine or a different type of computer other than a pine64 product but I digress.
I'll try it on my desktop later but has anyone else been able to successfully reset them?
|
|
|
|
| Will sudo pacman -Syu brick the PineTab2? |
|
Posted by: cgbarros - 07-15-2023, 06:21 AM - Forum: PineTab Software
- Replies (10)
|
|
Right after I got my PineTab2 one of the first things I did was to run a sudo pacman -Syu to update the system. But after that I bricked the thing. Luckily it comes with the UART board and I saw that the kernel wasn't working (I think it was not finding it? Don't remember exactly).
I reinstalled the factory image and it's all good. But now I'm afraid of updating the system again. Is updating everything with pacman like this not recommended? Anyone had the same issue or I just got unlucky that time?
|
|
|
|
| Access to system directories from flatpak |
|
Posted by: lagrang3 - 07-15-2023, 05:53 AM - Forum: PinePhone Software
- Replies (2)
|
|
I've started developing an app for the Pinephone, my app would be deployed with a flatpak.
My application needs access to system directories to read the device camera.
Doing some testing I've discovered that a native Pinephone application called megapixels doesn't launch if I package it into a flatpak. The error is related to not being able to read a system directory `/sys/firmware/devicetree/base`
In order to diagnose the problem I've run a python terminal inside the container and I've verified that neither `/sys/firmware` nor `/dev/video*` are visible from within the container:
Code: mobian@mobian:~$ /usr/bin/flatpak run --branch=master --arch=aarch64 --command=python3 com.lagrange.myapp
Python 3.11.4 (main, Jul 13 2023, 12:52:58) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> os.listdir('/sys')
['devices', 'dev', 'class', 'bus', 'block']
>>> os.listdir('/dev')
['console', 'ptmx', 'pts', 'shm', 'core', 'fd', 'stderr', 'stdout', 'stdin', 'tty', 'urandom', 'random', 'full', 'zero', 'null']
>>> exit()
they are there, just not visible from the container:
Code: mobian@mobian:~$ ls /dev/video*
/dev/video0 /dev/video1 /dev/video2 /dev/video3
mobian@mobian:~$ ls /sys
block bus class dev devices firmware fs kernel module power
Even though I've built the flatpak with `"finish-args": ["--filesystem=host", "--filesystem=host-os"]`.
What am I missing?
Any help will be much appreciated.
|
|
|
|
| Plans for higher Power PinePowers |
|
Posted by: PMARC14 - 07-14-2023, 03:03 PM - Forum: General
- Replies (1)
|
|
I am new to the community, but I wanted to ask if their was any interest or plans for higher power versions in the PinePowers family, 100 watts or even higher in PD3.1 EPR range. I mostly was thinking about this due to frameworks new laptop seemingly being first to possibly use the full 240 watts of the PD EPR range, but only are shipping with a 180 watt adaptor planned right now. Are their any 240 watt PD 3.1 chip IC's out their as the cables have caught up at least.
|
|
|
|
| Touch doesnt rotate on Sway in PineTab2 |
|
Posted by: cgbarros - 07-14-2023, 01:15 PM - Forum: PineTab Software
- Replies (4)
|
|
Hello!
I'm experimenting on running sway on PineTab2. My idea would be to use it together with the keyboard attached and sometime detach to read or doing stuff that are not keyboard heavy.
I managed to rotate the screen to landscape mode manually by running:
$ swaymsg output DSI-1 transform 90
This is fine, except that if I try to use the touchscreen it seems like the touch gestures "didn't rotate" together with the screen, i.e., I need to swipe left and right in order to scroll up and down when I'm reading a text.
Does anyone know what might be causing this? What is the KDE WM doing besides just rotating the output to match the gestures?
|
|
|
|
|
