PINE64
U-Boot with direct NVMe boot support for eMMC/SPI Flash - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: General Discussion on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=112)
+--- Thread: U-Boot with direct NVMe boot support for eMMC/SPI Flash (/showthread.php?tid=8439)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13


RE: U-Boot with direct NVMe boot support for eMMC/SPI Flash - pcm720 - 07-07-2020

Nah, this has nothing to do with your AUR helper (pamac).
The issue is that Makefile of rkdeveloptool forces GCC to treat all warnings as errors.
Here's the solution:
https://github.com/rockchip-linux/rkdeveloptool/issues/25

By the way, I updated the repository to use U-Boot v2020.07 and uploaded images for SD/eMMC and SPI.
You can find them on Releases page of the repository.


RE: U-Boot with direct NVMe boot support for eMMC/SPI Flash - mamboman777 - 07-07-2020

(07-07-2020, 03:16 PM)tophneal Wrote: This’s is likely what I was trying to say:

https://wiki.archlinux.org/index.php/Makepkg#Makepkg_fails,_but_make_succeeds

Try adding the suggested option to the pkgbuild. Or you can try grabbing it from git and building it manually
I did try manually from the git and it didn't build that way.  I do not know where to add the lines in the PKGBUILD.  Do I just put them at the top?


U-Boot with direct NVMe boot support for eMMC/SPI Flash - tophneal - 07-07-2020

Perfect, pcm720 jumped in. Take his advice not mine lol


RE: U-Boot with direct NVMe boot support for eMMC/SPI Flash - mamboman777 - 07-07-2020

(07-07-2020, 03:22 PM)pcm720 Wrote: Nah, this has nothing to do with your AUR helper (pamac).
The issue is that Makefile of rkdeveloptool forces GCC to treat all warnings as errors.
Here's the solution:
https://github.com/rockchip-linux/rkdeveloptool/issues/25

By the way, I updated the repository to use U-Boot v2020.07 and uploaded images for SD/eMMC and SPI.
You can find them on Releases page of the repository.
Thanks for your help.  I'm having a hard time following what to do on the git page.  If I run "make maintainer-clean" I get the message make: *** No rule to make target 'maintainer-clean'. Stop.

I do not understand where to place the code under "Apply the following patch" in the git page.

Thanks again!
-Josh


RE: U-Boot with direct NVMe boot support for eMMC/SPI Flash - belfastraven - 07-07-2020

Thanks for this @pcm720 .  Although I did sucessfully build from your git using  the current u-boot (on ubuntu focal desktop),  I just grabbed your released spiflash.bin and flashed in on current (from unstable) Manjaro.    It's great--boots even faster than it did with the Feb. mainline uboot and atf.  So far I've only booted from my NVME but will test other devices, too.  

A note for other newbies:  Flash_erase is part of the mtd-utils package in arch/Manjaro and one needs to sudo the flash_erase and dd commands if not logged in as root.  

thanks again.


RE: U-Boot with direct NVMe boot support for eMMC/SPI Flash - pcm720 - 07-08-2020

(07-07-2020, 03:58 PM)mamboman777 Wrote:
(07-07-2020, 03:22 PM)pcm720 Wrote: Nah, this has nothing to do with your AUR helper (pamac).
The issue is that Makefile of rkdeveloptool forces GCC to treat all warnings as errors.
Here's the solution:
https://github.com/rockchip-linux/rkdeveloptool/issues/25

By the way, I updated the repository to use U-Boot v2020.07 and uploaded images for SD/eMMC and SPI.
You can find them on Releases page of the repository.
Thanks for your help.  I'm having a hard time following what to do on the git page.  If I run "make maintainer-clean" I get the message make: *** No rule to make target 'maintainer-clean'. Stop.

I do not understand where to place the code under "Apply the following patch" in the git page.

Thanks again!
-Josh

Okay, instead of trying to use PKGBUILD, do the following:
- Clone the repository
- Inside the directory,
 - Run "autoreconf -i"
 - Run "./configure"
 - Run "sed -i "s/-Werror//" Makefile" (with quotes before "s" and after the third "/")
 - Run make
You'll find rkdeveloptool binary inside the repo folder.

(07-07-2020, 07:22 PM)belfastraven Wrote: Thanks for this @pcm720 .  Although I did sucessfully build from your git using  the current u-boot (on ubuntu focal desktop),  I just grabbed your released spiflash.bin and flashed in on current (from unstable) Manjaro.    It's great--boots even faster than it did with the Feb. mainline uboot and atf.  So far I've only booted from my NVME but will test other devices, too.  

A note for other newbies:  Flash_erase is part of the mtd-utils package in arch/Manjaro and one needs to sudo the flash_erase and dd commands if not logged in as root.  

thanks again.

Awesome, thanks for trying it out! Yeah, both commands need to be run with root privileges.
I've added that to release description.


RE: U-Boot with direct NVMe boot support for eMMC/SPI Flash - mamboman777 - 07-08-2020

(07-08-2020, 01:00 AM)pcm720 Wrote:
(07-07-2020, 03:58 PM)mamboman777 Wrote:
(07-07-2020, 03:22 PM)pcm720 Wrote: Nah, this has nothing to do with your AUR helper (pamac).
The issue is that Makefile of rkdeveloptool forces GCC to treat all warnings as errors.
Here's the solution:
https://github.com/rockchip-linux/rkdeveloptool/issues/25

By the way, I updated the repository to use U-Boot v2020.07 and uploaded images for SD/eMMC and SPI.
You can find them on Releases page of the repository.
Thanks for your help.  I'm having a hard time following what to do on the git page.  If I run "make maintainer-clean" I get the message make: *** No rule to make target 'maintainer-clean'. Stop.

I do not understand where to place the code under "Apply the following patch" in the git page.

Thanks again!
-Josh

Okay, instead of trying to use PKGBUILD, do the following:
- Clone the repository
- Inside the directory,
 - Run "autoreconf -i"
 - Run "./configure"
 - Run "sed -i "s/-Werror//" Makefile" (with quotes before "s" and after the third "/")
 - Run make
You'll find rkdeveloptool binary inside the repo folder.

(07-07-2020, 07:22 PM)belfastraven Wrote: Thanks for this @pcm720 .  Although I did sucessfully build from your git using  the current u-boot (on ubuntu focal desktop),  I just grabbed your released spiflash.bin and flashed in on current (from unstable) Manjaro.    It's great--boots even faster than it did with the Feb. mainline uboot and atf.  So far I've only booted from my NVME but will test other devices, too.  

A note for other newbies:  Flash_erase is part of the mtd-utils package in arch/Manjaro and one needs to sudo the flash_erase and dd commands if not logged in as root.  

thanks again.

Awesome, thanks for trying it out! Yeah, both commands need to be run with root privileges.
I've added that to release description.
All right. Sitrep. I finally get rkdeveloptool up and running, but it's very unstable on my machine for some reason. I'm guessing that my USB is sleeping within seconds of entering maskrom. So I have to enter the commands almost faster than I can type. I got very good at shorting the correct pins on my SPI. That being said. I was able to get the PBP to boot, but only with an empty SPI. I tried flashing spiflash.bin from within Manjaro running on an SD and using maskrom and neither produced bootable machine. Could it be that something went wrong in the build, I am flashing the wrong "spiflash.bin" (I realized there are more than one last night) or something just doesn't seem whenever I try to flash my SPI? What are my next steps?


RE: U-Boot with direct NVMe boot support for eMMC/SPI Flash - mamboman777 - 07-08-2020

(07-08-2020, 05:53 AM)mamboman777 Wrote:
(07-08-2020, 01:00 AM)pcm720 Wrote:
(07-07-2020, 03:58 PM)mamboman777 Wrote:
(07-07-2020, 03:22 PM)pcm720 Wrote: Nah, this has nothing to do with your AUR helper (pamac).
The issue is that Makefile of rkdeveloptool forces GCC to treat all warnings as errors.
Here's the solution:
https://github.com/rockchip-linux/rkdeveloptool/issues/25

By the way, I updated the repository to use U-Boot v2020.07 and uploaded images for SD/eMMC and SPI.
You can find them on Releases page of the repository.
Thanks for your help.  I'm having a hard time following what to do on the git page.  If I run "make maintainer-clean" I get the message make: *** No rule to make target 'maintainer-clean'. Stop.

I do not understand where to place the code under "Apply the following patch" in the git page.

Thanks again!
-Josh

Okay, instead of trying to use PKGBUILD, do the following:
- Clone the repository
- Inside the directory,
 - Run "autoreconf -i"
 - Run "./configure"
 - Run "sed -i "s/-Werror//" Makefile" (with quotes before "s" and after the third "/")
 - Run make
You'll find rkdeveloptool binary inside the repo folder.

(07-07-2020, 07:22 PM)belfastraven Wrote: Thanks for this @pcm720 .  Although I did sucessfully build from your git using  the current u-boot (on ubuntu focal desktop),  I just grabbed your released spiflash.bin and flashed in on current (from unstable) Manjaro.    It's great--boots even faster than it did with the Feb. mainline uboot and atf.  So far I've only booted from my NVME but will test other devices, too.  

A note for other newbies:  Flash_erase is part of the mtd-utils package in arch/Manjaro and one needs to sudo the flash_erase and dd commands if not logged in as root.  

thanks again.

Awesome, thanks for trying it out! Yeah, both commands need to be run with root privileges.
I've added that to release description.
All right. Sitrep. I finally get rkdeveloptool up and running, but it's very unstable on my machine for some reason. I'm guessing that my USB is sleeping within seconds of entering maskrom. So I have to enter the commands almost faster than I can type. I got very good at shorting the correct pins on my SPI. That being said. I was able to get the PBP to boot, but only with an empty SPI. I tried flashing spiflash.bin from within Manjaro running on an SD and using maskrom and neither produced bootable machine. Could it be that something went wrong in the build, I am flashing the wrong "spiflash.bin" (I realized there are more than one last night) or something just doesn't seem whenever I try to flash my SPI? What are my next steps?
Is there a way that someone can get me a properly build "flashspi.bin" to compare to the one I built?  I suspect that's the issue.


RE: U-Boot with direct NVMe boot support for eMMC/SPI Flash - belfastraven - 07-08-2020

get it from @pcm720 https://github.com/pcm720/u-boot-build-scripts/releases/tag/v2020.07 It's on his github site along with instructions for installing without the RKDeveloptools...,


RE: U-Boot with direct NVMe boot support for eMMC/SPI Flash - mamboman777 - 07-08-2020

(07-08-2020, 09:57 AM)belfastraven Wrote: get it from @pcm720    https://github.com/pcm720/u-boot-build-scripts/releases/tag/v2020.07  It's on his github site along with instructions for installing without the RKDeveloptools...,
Awesome!  Thank you.  Actually, when comparing I believe the spiflahs.bin I ended up with is similar.  At this point, I'm going to have to enter rkdeveloptools anyways to clear the broken spi flash, so I thought I may as well try while I'm in there.

-Josh