u-boot VS Jumpdrive

coreboot just initializes the hardware, the logo is something that the payload displays: https://www.coreboot.org/Payloads

The most typically used payload is u-boot: https://docs.u-boot.org/en/latest/

u-boot supports specifying splash screens via "splashfile", but it seems only bmp and maybe some raw image format are supported: https://github.com/u-boot/u-boot/blob/2f0282922b2c458eea7f85...

In other words, no support for png, which this exploit uses :). That doesn't mean that coreboot/u-boot aren't written in C though which is a language known for its vulnerabilities.

Probably a better example than WiFi would be the on-chip SDRAM controller. It's always somebody's IP and there's a blob in the boot firmware that's just binary register settings. Like so:

https://github.com/u-boot/u-boot/blob/master/arch/riscv/dts/...

Hello, It's my understanding that the following OSS software is used in the AtGames Legends family of products. Specifically: "Das U-Boot" https://github.com/u-boot/u-boot GPL-2.0+ Linux Kernel https://github.com/torvalds/linux GPL-2.0 The AtGames website at https://www.atgames.us/pages/credits does not contain the source code used in these products. Specifically, the GPL requires that if any modifications are made to GPL code, you must make the source code available to the users of the program as described in the GPL, and they must be allowed to redistribute and modify it as described in the GPL. Any modification to u-boot or the Linux Kernel adding the ability to boot a device must be made available to users of the program. Please see the following links regarding acceptable use of GPL software: https://www.gnu.org/licenses/gpl-faq.en.html#GPLRequireSourcePostedPublic https://www.gnu.org/licenses/gpl-faq.en.html#WhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions https://www.gnu.org/licenses/gpl-faq.en.html#GPLCommercially https://www.gnu.org/licenses/gpl-faq.en.html#GPLInProprietarySystem https://www.gnu.org/licenses/gpl-faq.en.html#DistributingSourceIsInconvenient Please let this request serve as written notice of a request for source code for the OSS software used in the following products: HA2810, HA2811, HA2812 AtGames Legends Core Puck HA2819 AtGames Legends Core Max HA8800, HA8801, HA8802 AtGames Legends Ultimate HA8810, HA8812 AtGames Legends Ultimate Mini HA8819, HA8819C AtGames Legends Pinball (Model unknown) AtGames Legends Pinball Micro At this point in time, AtGames is in violation of the GPL and should work to return to compliance by publishing the requested source code and making it available to users of the products.

Upstream u-boot also supports quite a lot of boards: https://github.com/u-boot/u-boot/tree/master/arch/arm/dts

git clone https://github.com/u-boot/u-boot make smdk5250_defconfig Makefile:40: *** missing operator. Stop.

Hey everyone, if this question is off-topic I apologize in advance and if you can redirect me into correct channel or any other source where I can ask question I would happily do, for now I think this is the best place to ask. I daily drive arch and wanted to run freeBSD/riscv64 image on qemu following this https://wiki.freebsd.org/riscv#QEMU_Emulator and u-boot guide: https://github.com/u-boot/u-boot/blob/master/doc/board/emulation/qemu-riscv.rst However it seems I'm doing something wrong and compilation results in error here is all additional info: https://pastebin.com/72shccGa

The normal way this is done is the DDR training blob is just embedded into the bootloader like any other data, and the bootloader loads it into the PMU. Same exact end result, minus involving a Cortex-M4 core for no reason and minus sticking the blob in external flash for no reason. Here, this is how U-Boot does it on every other platform:

https://github.com/u-boot/u-boot/blob/master/drivers/ddr/imx...

Same code, just running on the main CPU because it is absolutely pointless running it on another core, unless you're trying to obfuscate things to appease the FSF. And then the blob gets appended to the U-Boot image post-build:

https://github.com/u-boot/u-boot/blob/master/tools/imx8m_ima...

Purism went out of their way and wasted a ton of engineering hours just to create a more convoluted process with precisely the same end result, because somehow all these extra layers of obfuscation made the blob not a blob any more in the FSF's eyes.

The RK3399 LPDDR4 training code is open-source (albeit rather impenetrable to read) - implementations exist in coreboot, u-boot, and levinboot, so closed source firmware isn't required. I'm afraid I don't know answers to the other questions.

Download: https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.8/pine64-pinephone.img.xz

To confirm the battery status I flashed the charging image from https://github.com/dreemurrs-embedded/Jumpdrive/issues/55. That indeed showed that there was pretty much no charge in the battery. I then took my macbook adapter and charged it for two hours using that, and then the status led started flashing green. Looks like this is solved!

I would suggest that you download https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.8/pine64-pinephone.img.xz. Then write it to a microSD card using "Balena Etcher" and then insert the microSD card in the top slot and let us know if there is a question or if it changed anything.

Please put Jumpdrive on a microSD card and try to boot that. Jumpdrive boots independently from the battery charge. If it boots fine you can let it charge in there for multiple hours and then see if you can boot the phone properly again. https://github.com/dreemurrs-embedded/Jumpdrive

That sounds like a corrupted installation, not a drained battery. If you're on the regular PinePhone (not the Pro) I would suggest you to flash JumpDrive on a microSD card, insert that into the phone (top slot) and to boot from that. The image can be found here: https://github.com/dreemurrs-embedded/Jumpdrive/releases/download/0.8/pine64-pinephone.img.xz

At this point if you haven't updated in a long time it's best if you flash a new image to your eMMC because if you pacman -Syu your just gonna bork it like I did when I updated my KDE edition after a year of being sidelined lol. Luckily jumpdrive exists and makes this task as simple as running a dd command.

JumpDrive -> https://github.com/dreemurrs-embedded/Jumpdrive/releases

The last time I had to reinstall my Librem 5 I ended up using JumpDrive and a fresh image from Purism's Jenkins, reusing the instructions from postmarketOS Wiki#Installation).

https://github.com/dreemurrs-embedded/Jumpdrive/releases/tag/0.8 I had a similar situation. After getting a pinephone pro my pinephone OG set idle for several months. I couldn't boot to the eMMc or the sd. I still had jumpdrive on an sd so i tried booting from it. It fixed everything although I don't know how. Now it boots from eMMc or sd just fine. I didn't even plug it into a laptop. After the jumpdrive screen booted I powered it down and removed the jumpdrive for pinephone sd. I fired up the pinephone OG to fix the modem firmware. Flashing the modem went well and the pinephone is ready for use should I need it.