I'm trying to build a U-Boot loader for PineTab2 (don't ask me why, I have no answer to this question).

Just received a gifted Pinebook Pro. Donor said "look in the forums" when I asked for the login & password.
May I please ask what are the default username and password?
TY.

UPDATE: rock/rock
--
73 & best regards de K7AAY CN85oj @503bartley.pdx.social @503bartley.bsky.social

Purchased an Alpha One, took it out of the box, plugged in the Ethernet cord, inserted a blank SD Card, and plugged in the provided power cable. Noticed from the start, only one of the two ethernet port lights were lit, which indicates a faulty port. I created a brand new Cat6 Ethernet cable with shielded RJ45s, and tested it, to make sure the cable was not the issue. I then checked to see if the alpha one had acquired an IP Address, it indicated it did, but attempts to connect failed due to timing out. So then an ARP scan was performed to see if the board would respond to ARP, but it did not. I performed a ping test for redundancy, which timed out, then the Alpha One disappeared entirely from the network.

Repeated attempts to try to configure the network proved unsuccessful, until the decision to reflash the entire board with the official image was reached. This was performed to the letter as instructed by RockOS, here[url=https://docs.rockos.dev/en/docs/installation/][/url]. The result of which was fewer errors generated in syslog, but overall no change. Neither could the board obtain connectivity, nor could anything connect to it. 

Current efforts are invested towards discovering whether the EMMC is defective, before moving on to other parts of the board itself. In my sixteen years of experience, I have yet to encounter a system I have been unable to get up and running, I do not plan for the AlphaOne to be the first, but there is little I can do when it appears the hardware itself arrives broken.

Why has a section for StarPro64 not been created yet? 
Why is there no "Catch all for problems" thread either?  

Hi,
I'm writing a custom pyqt6 app on my pinephone but I cannot access the camera.
In dmesg, I see

Quote:ov5640 0-004C: ov5640_write_reg: error: reg=3008, val=42

Can someone help me with an overview of the steps I'd need to play a PCM sample from RAM via the PinePhone speaker please?  I want my bare-metal OS to have some beeps

This is what I have so far:

LINEOUT to Speaker goes via component U800, audio amplifier, and link expired in the component list.  but seems to have an interesting connection to NAND. (PA-SHDN)

[edit: ignore this paragraph, I got AC_PR working!]    AC_PR Configuration Register mentioned (p362), but not sure of it's register address or usage, it mentions PRCM but doesnt explain how.  It seems I'll need this for access to : 0x05 LINEOUT Control Register, and maybe to un-mute the MIX channels.   [Edit: I found more information in the A80 manual   it looks like R_PRCM is at 0x01F01400 in the A64,but still not clear where this AC+PR register is located.]

Looking at the data path diagram (page 280).  It looks like I should be able to send PCM over I2S, but sounds like there is a mode that reads direct from RAM?

As you can hear, I'm a bit lost down the rabbit hole at the moment!

https://vector3d.shop/ - they are not in the affiliates list but seem legitimate.

I finally got the touch screen working! still some spurious events I need to track down still, including an interrupt flood.  But the first thing I added was finger paint mode, to check touch locations, and a button to clear the screen  

All good fun, but my 'clear screen' functionality is super slow.  I'm guessing at .25s, slow enough to see the progress.  This is using a framebuffer approach i.e. no GPU, and a memset to do the clear.  But I also tried a direct arm assembly loop, and looks the same.

I dont have enough experience with the PinePhone to know if this is to be expected? or an anomaly in my approach.  I was expecting to be able to easily do 60fps with plenty of spare cycles to run my apps.

firstly the earpiece hardware works fine, I can play audio through it.

I replaced the mainboard on my PPpro and at some point early on I lost the ability to hear or send audio on a telephone call.

Follow down the thread to see the Quectel EG25 modem's dmsg failing to create the audio device

I flashed themodemdistro firmware 8.0 via ./flashall and then ADSP V 01.003.01.003 and then DSP V 01.002.01.002 
https://github.com/the-modem-distro/pine...LASHING.md
did both several times over the last days.
incoming and outgoing calls no luck; 2g, 3g, 4g
interesting ringtone doesn't work either

I have been flashing various images testing, I have flashed an image of the final from my old main board where phone audio mostly worked.  I have been writing my old /home onto the new installs once I have them installed but I do a phone test first.

Rebooting as well as shutdown, rest, boot doesn't work either.

Data works, SMS works, DIalling works receiving works, just no audio except that 4g fails to make/take a call as usual which will be a problem once 2g and 3g shut down.

the audio line alsa/pipewire stuff gets complicated I am nut sure what to look for in the modem's dmsg

I am probably missing an obvious mistake, embarrass me please by showing me my error!

(edit)moved to ADSB 30.004 and 4g seems to be work, but that is always temporary, not the real problem of this post anyways
(edit2) I even rewrote the EFS https://themodemdistro.com/efs_recovery makes calls no audio in/out

As was just verified, the arm64 UEFI variant of the Window Maker Live Linux distribution based on Debian/Trixie boots just fine on towboot enabled Pinebook Pro. This also includes the graphical debian installer routine, avoiding the need to bother with the awkward serial console for installations. I didn't complete a full installation yet on my own bare metal PBP because the machine needed for development is not suitable also for testing, and all installation testing has been done only in qemu so far.

See https://wmlive.sourceforge.net for more details and descriptions, screenshots, and download options.

Before you start downloading the ISO image for trying it out yourself, be aware that with the exception of the freely usable i386 version, the ISO images for both arm64 and amd64 are distributed as encrypted 7z archives which require a password to unpack them. Due to personal circumstances i am currently not in the position to just give away the fruits of my time and efforts investment without asking for a return. Until it will finally be publicly disclosed at the end of this year, this password is therefore provided only to people who are donating some cash to the project. 

On the other hand, the sources to enable people to build any variant of the ISO themselves are, of course, readily available. So if you can't afford even any minimal donation and don't want to wait for the public password disclosure at the end of the year, you can simply create your own custom ISO image.

For interested people who are contributing any publicly accessible open source work themselves, the password will be freely provided without any donation requirement. Please contact me privately if this is of interest for you.