Reprogrammed the board here using my patch (
https://github.com/kratsg/meta-l1calo/commit/2ddfbfa7a1d6c2a11c3035e3b0e504be793352fc)
and u-boot still hangs at the MMC line. Is there something I missed?
Giordon
On Sat, Nov 18, 2017 at 12:26 PM Giordon Stark wrote:
> After a bit
After a bit of hunting down, I did the modifications using the devtool
helper and wrote my procedure down since I couldn't find a good guide
online (
https://github.com/kratsg/meta-l1calo/wiki/Creating-a-patch-for-an-existing-recipe-source-file
)
Thanks!
Giordon
On Sat, Nov 18, 2017 at 11:36 AM
That said, I found the config here:
https://github.com/Xilinx/u-boot-xlnx/blob/master/include/configs/xilinx_zynqmp_zcu102.h#L13
and
just need to generate a bbappends that's only applied for a specific
machine.
Giordon
On Sat, Nov 18, 2017 at 11:16 AM Giordon Stark wrote:
>
I'm also unable to run `bitbake -c menuconfig "virtual/bootloader". I think
I run into a similar error as this SO post (
https://stackoverflow.com/questions/43211384/how-to-get-to-menuconfig-for-u-boot-in-yocto-environment
)
ERROR: Task do_menuconfig does not exist for target virtual/bootloader
(resending with right email, sorry for spam) Incredibly naive question
since I've been wondering about these things. Is it not possible to write
this as a patch or a .bbappends and put it in my meta layer (where?). I
assume the u-boot config is defined in meta-xilinx/classes or
meta-xilinx/conf as
Incredibly naive question since I've been wondering about these things. Is
it not possible to write this as a patch or a .bbappends and put it in my
meta layer (where?). I assume the u-boot config is defined in
meta-xilinx/classes or meta-xilinx/conf as Xilinx maintains their own fork
of u-boot I
Basically boils down to disabling SD support in u-boot.
In OE/Yocto, run "bitbake -c menuconfig virtual/bootloader" and remove
the MMC option (and whatever other options you like). Save the
configuration as /tmp/defconfig, and exit. Copy the defconfig to the
u-boot recipe location and add a
Here's an image showing what the console looks like:
https://www.dropbox.com/s/c62tabxsmghaccc/Screenshot%202017-11-17%2015.56.49.png?dl=0
from
QSPI boot with where it hangs.
Giordon
On Fri, Nov 17, 2017 at 2:55 PM Giordon Stark wrote:
> The reason I ask is that when I try to
The reason I ask is that when I try to program the QSPI flash with this
BOOT.bin
//arch = zynqmp; split = false; format = BIN
the_ROM_image:
{
[fsbl_config]a53_x64
[bootloader]E:\gFEX_pre_production\image\zu19eg_3\zu19eg_3.sdk\fsbl_a53\Debug\fsbl_a53.elf
[destination_cpu =
Is it possible to tell u-boot to not boot from MMC? I suspect it's a
configuration flag -- and this is when I try to program the QSPI using my
boot.bin and it would be beneficial to make that work.
Thanks,
Giordon
--
___
meta-xilinx mailing list
10 matches
Mail list logo