(almost) upstream uboot/atf

[User 15997]

i strongly advise against using this with the mrfixit debian. that debian kernel is built to work with firmware that works differently in important ways, using upstream firmware may not work at all. that said, the article was written assuming an aarch64 host (manjaro). the mrfixit debian is, i think, a 32 bit userland, so even there you'd have to cross-compile for aarch64. i have absolutely no clue how debian names its cross-compiler packages though.

cloning does work fine here, even though it takes a while and the progress output for http clones really isn't great will have to do something about that eventually ...

[Jeremiah Cornelius]

i strongly advise against using this with the mrfixit debian. that debian kernel is built to work with firmware that works differently in important ways, using upstream firmware may not work at all. that said, the article was written assuming an aarch64 host (manjaro). the mrfixit debian is, i think, a 32 bit userland, so even there you'd have to cross-compile for aarch64. i have absolutely no clue how debian names its cross-compiler packages though.

cloning does work fine here, even though it takes a while and the progress output for http clones really isn't great will have to do something about that eventually ...

Gotcha. I'll have to work from my daniel scripted native Debian. I targeted a USB for an interim test - only to find the stock uBoot doesn't order this before the EMMc. Haven't cracked the case for the switch or anything, yet.

[as400]

@"dhivael" I think I experienced error in your uboot.

When I power on my pbp usually nvme drive doesn't get initialized properly and is not visible by OS. It's a lottery. On 6-7 subsequent boots it is ok and visible by OS once.

I don't get that behaviour using other uboots.

[User 15997]

that's odd. this one doesn't do anything with nvme, and it shouldn't matter once linux has started running. could this be another nvme power issue in disguise? if only we had an nvme drive here to try this out with

[as400]

that's odd. this one doesn't do anything with nvme, and it shouldn't matter once linux has started running. could this be another nvme power issue in disguise? if only we had an nvme drive here to try this out with

Power issue was the first thing that came to my mind but after I reverted to previous uboot I don't get that behaviour.

I really have no idea how to explain it   

I have also stressed the machine today to the absolute limits in terms of IO. Doing dd back and forth from emmc to nvme and the other way. Everything on battery and nothing wrong happened.

[User 15997]

update on nvme support:

https://git.eno.space/pbp-uboot.git/log/?h=nvme is a new branch for nvme support, using a different pcie driver than the one we tried previously. nvme boot is enabled in the pinebook defconfig and seems to work, but i'm a bit reluctant to call it stable just yet. any testing is appreciated!

[clover]

update on nvme support:

https://git.eno.space/pbp-uboot.git/log/?h=nvme is a new branch for nvme support, using a different pcie driver than the one we tried previously. nvme boot is enabled in the pinebook defconfig and seems to work, but i'm a bit reluctant to call it stable just yet. any testing is appreciated!

Awesome!

Is it possible for you to add an SPI flash .bin file similar to what pcm700 did here: https://github.com/pcm720/rockchip-u-boot/releases

[User 15997]

Awesome!

Is it possible for you to add an SPI flash .bin file similar to what pcm700 did here: https://github.com/pcm720/rockchip-u-boot/releases

sadly not at this point, since i have no idea how those images are built. it is reasonable though to assume that the same process pcm720 used can be used on this version as well.

[User 15997]

the nvme branch now also has support for building SPI images, so emmc is no longer necessary. instructions on how to build the image are in the latest commit message, instructions for flashing are omitted to protect the innocent

[as400]

@"dhivael" - I confirm it's working. Whether from nvme or sd.

Thanks