I am not sure where you did fid -rt or -armmp? If there is something it is a glitch from transitioning the build scripts.
It is all here: https://download.goldelico.com/letux-kernel/letux-5.14-rc1-lpae/
You can find a debian header package, but preferred is to use the git source tree.
There you...
1. Letux is: www.letux.org and https://pyra-handheld.com/boards/threads/letux-os.81518/
2. the U-Boot/DDR message may be that your board needs slightly different DDR timings setup. ED mentioned a while ago that there is a patch in PyraOS and I am not sure if it is missing in the LetuxOS U-Boot...
download makesd: https://projects.goldelico.com/p/gta04-makesd/
run
DEV=/dev/$your_SD_reader makesd pyra -r minimal
or if your have a 4GB RAM Pyra use DEV=/dev/$your_SD_reader makesd pyra-4g -r minimal
This creates a bootable SD card which you can access through the USB-FTDI console. It is...
For GPS: just tried with letux-5.13.0 kernel (incl. one patch not yet upstream that fixes a boot issue).
root@letux:~# cat $(./gps-on)
./gps-on: line 13: warning: command substitution: ignored null byte in input
[ 955.045999] wwan_on_off_rfkill_set_block: blocked: 0
[ 955.051828]...
You could ask for support, e.g. on the pyra or letux kernel mailing list.
It is a while that I tested the modem last time but with LetuxOS it did work back then.
There is also some gps script to demonstrate basic functionality...
Maybe show a copy of the console log with:
* 'ls -l' showing the executable
* 'file' showing the executable
* 'echo $PATH'
* running the command
Then it may be easier to help.
Handling sensors is quite a standard problem for all handheld devices software stacks. First activities go back to the (OpenMoko) GTA02. But AFAIR there is no "standard" besides Android/Replicant (or iOS). There, all sensors are mapped to some high level abstraction Java/Swift/Obj-C classes...
Well every choice has its drawbacks.
Encoder wheel usually has small steps (sending impulses to wake up the processor to be counted up or down). It reports changes. Therefore there is no well defined "off" position which it can be turned to even when the system is powered off. And off-the-shelf...
It is just a little waste of SD card space for the twl6030 driver which is neither loaded nor used by the Pyra. But yes, the CONFIG can be removed which will also improve compile time a little.
Good news:
1. starting your image
I flashed the card again (with a fresh download) and this time it did boot and run through the wizard. I checked that it is running your kernel build
[ 0.000000] Linux version 5.12.1-letux-lpae (pyra@debian-buster) (arm-linux-gnueabihf-gcc (Debian 8.3.0-2)...
Hm. There was no wizzard. Just boot log on the screen and console and now a login: on both.
And the message
[FAILED] Failed to start Pyra First Run Wizard.
See 'systemctl status pyra-first-run.service' for details.
Starting Light Display Manager...
Doing as suggested:
root@pyra:~#...
Thanks!
I've now flashed an SD card and could boot up to the login: prompt.
Now I am stuck with the standard-issue of prebuilt images :)
What is the user/password to get into the console?
Well, this can have thoudsands of reasons.
Which kernel and which config are you using? Which user-space setup? Or in other words: do you have an SD card image or a full description of all steps which I could use to try to reproduce this and analyse e.g. differences to my LetuxOS setup?
I haven't observed that myself or run into trouble, but if a CONFIG is missing, please let me know to add it to the pyra_defconfig. It is done in minutes if I know.
Well, in an ideal world the latest Debian kernel would simply boot the Pyra fully functional.
When starting the GTA04 project...
I'd suggest to base work on letux-5.10 because it already contains all the work I have invested to make AESS work.
Unfortunately I am no longer in a situation where I could help out ED with this topic, even with a bounty (I have to focus my plethora of projects).
Status is:
* a full AESS driver...
Most of the information is available through
cat /sys/class/power_supply/bq24297/uevent
cat /sys/class/power_supply/bq24297/device/registers
so that you do not have to bypass i2c of the chip driver.
Plugging in a charging cable can turn on the Pyra if it was completely powered down (done by Palmas power controller chip). This lights up the green led until the OMAP turns on the display.
I am not sure if this auto-poweron can be disabled by software (some control bits of the Palmas and if...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.