[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

I am porting u-boot to nyan_big and need some input.  I have been searching
high and low and found this thread here: [U-Boot] [PATCH 0/20] tegra:
Expand Nyan-big support

 https://lists.denx.de/pipermail/u-boot/2015-March/209530.html

I have tried to build u-boot with the branch here:

https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big

and also the official chromium next branch

I followed building instructions here: https://www.chromium.org
/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-
samsung-arm-chromebook

I build with these commands:

mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its kernel-u-boot

(with and without the load address setting)

vbutil_kernel --arch arm --pack kernel.bin --keyblock
/usr/share/vboot/devkeys/kernel.keyblock --signprivate
/usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1 --config
dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt

I have had numerous failed attempts to boot uboot from sdcard mmcblk1p1

Any help is appreciated I have only gotten a blank screen after weeks of
flashing.  I can boot custom v3.10 kernels so I assume I am using the
correct building procedure.  Thanks in advance for help from the u-boot
community.

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Simon Glass]

Hi Matthew,

On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com> wrote:
> I am porting u-boot to nyan_big and need some input.  I have been searching
> high and low and found this thread here: [U-Boot] [PATCH 0/20] tegra: Expand
> Nyan-big support
>
>  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
>
> I have tried to build u-boot with the branch here:
>
> https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
>
> and also the official chromium next branch

Have you tried mainline U-Boot? It already supports nyan-big. I'm not
sure about the situation with the downstream trees.

>
> I followed building instructions here:
> https://www.chromium.org/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook
>
> I build with these commands:
>
> mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its kernel-u-boot
>
> (with and without the load address setting)
>
> vbutil_kernel --arch arm --pack kernel.bin --keyblock
> /usr/share/vboot/devkeys/kernel.keyblock --signprivate
> /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1 --config
> dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
>
> I have had numerous failed attempts to boot uboot from sdcard mmcblk1p1
>
> Any help is appreciated I have only gotten a blank screen after weeks of
> flashing.  I can boot custom v3.10 kernels so I assume I am using the
> correct building procedure.  Thanks in advance for help from the u-boot
> community.

It is possible that it needs a particular address due to limitations
in the FIT support on Nyan. I'm not sure what it is but might be able
to take a look at some point.

How are you building your SD card? Are you following some instructions
from somewhere?

Regards,
Simon

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

Thanks for the reply Simon.

I have been trying to find the System.map for depthcharge to see the kernel
load address but I am unable to find anything.  I have tried multiple
CONFIG_SYS_TEXT_BASE
settings with no luck.

I am creating my sdcard with a standard linux (Linux for Tegra) rootfs:
Partition an SD card

sudo cgpt create <MMC BLOCK DEVICE>
sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK DEVICE> #
16 MB kernel image partition
sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors> -t
rootfs <MMC BLOCK DEVICE>

cgpt doesn't seem to create a protective MBR. If one is not already in
place, it can be created with:

sudo gdisk <MMC BLOCK DEVICE> # and enter command w

<https://github.com/chromeos-nvidia-androidtv/gnu-linux-on-acer-chromebook-13#copy-data-to-the-sd-card>Copy
data to the SD card

sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
sudo mount <MMC BLOCK DEVICE>p2 /mnt/


On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org> wrote:

> Hi Matthew,
>
> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com> wrote:
> > I am porting u-boot to nyan_big and need some input.  I have been
> searching
> > high and low and found this thread here: [U-Boot] [PATCH 0/20] tegra:
> Expand
> > Nyan-big support
> >
> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
> >
> > I have tried to build u-boot with the branch here:
> >
> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
> >
> > and also the official chromium next branch
>
> Have you tried mainline U-Boot? It already supports nyan-big. I'm not
> sure about the situation with the downstream trees.
>
> >
> > I followed building instructions here:
> > https://www.chromium.org/chromium-os/firmware-porting-
> guide/using-nv-u-boot-on-the-samsung-arm-chromebook
> >
> > I build with these commands:
> >
> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its kernel-u-boot
> >
> > (with and without the load address setting)
> >
> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1 --config
> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
> >
> > I have had numerous failed attempts to boot uboot from sdcard mmcblk1p1
> >
> > Any help is appreciated I have only gotten a blank screen after weeks of
> > flashing.  I can boot custom v3.10 kernels so I assume I am using the
> > correct building procedure.  Thanks in advance for help from the u-boot
> > community.
>
> It is possible that it needs a particular address due to limitations
> in the FIT support on Nyan. I'm not sure what it is but might be able
> to take a look at some point.
>
> How are you building your SD card? Are you following some instructions
> from somewhere?
>
> Regards,
> Simon
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Simon Glass]

Hi Matthew,

On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com> wrote:
> Thanks for the reply Simon.
>
> I have been trying to find the System.map for depthcharge to see the kernel
> load address but I am unable to find anything.  I have tried multiple
> CONFIG_SYS_TEXT_BASE settings with no luck.

How did you choose what to use? Also note that Tegra uses SPL to
start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.

>
> I am creating my sdcard with a standard linux (Linux for Tegra) rootfs:

Did these instructions come from a web site somewhere?

>
> Partition an SD card
>
> sudo cgpt create <MMC BLOCK DEVICE>
> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK DEVICE> # 16 MB
> kernel image partition
> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors> -t rootfs
> <MMC BLOCK DEVICE>
>
> cgpt doesn't seem to create a protective MBR. If one is not already in
> place, it can be created with:
>
> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
>
> Copy data to the SD card
>
> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>

How are you actually making it boot? Is this in dev mode with USB boot
enabled and pressing Ctrl-U?

Also, as this is a mailing list, please avoid top-posting.

- Simon

>
> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org> wrote:
>>
>> Hi Matthew,
>>
>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> > I am porting u-boot to nyan_big and need some input.  I have been
>> > searching
>> > high and low and found this thread here: [U-Boot] [PATCH 0/20] tegra:
>> > Expand
>> > Nyan-big support
>> >
>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
>> >
>> > I have tried to build u-boot with the branch here:
>> >
>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
>> >
>> > and also the official chromium next branch
>>
>> Have you tried mainline U-Boot? It already supports nyan-big. I'm not
>> sure about the situation with the downstream trees.
>>
>> >
>> > I followed building instructions here:
>> >
>> > https://www.chromium.org/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook
>> >
>> > I build with these commands:
>> >
>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its kernel-u-boot
>> >
>> > (with and without the load address setting)
>> >
>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1 --config
>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
>> >
>> > I have had numerous failed attempts to boot uboot from sdcard mmcblk1p1
>> >
>> > Any help is appreciated I have only gotten a blank screen after weeks of
>> > flashing.  I can boot custom v3.10 kernels so I assume I am using the
>> > correct building procedure.  Thanks in advance for help from the u-boot
>> > community.
>>
>> It is possible that it needs a particular address due to limitations
>> in the FIT support on Nyan. I'm not sure what it is but might be able
>> to take a look at some point.
>>
>> How are you building your SD card? Are you following some instructions
>> from somewhere?
>>
>> Regards,
>> Simon
>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org> wrote:

Hi Matthew,

On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com> wrote:
> Thanks for the reply Simon.
>
> I have been trying to find the System.map for depthcharge to see the
kernel
> load address but I am unable to find anything.  I have tried multiple
> CONFIG_SYS_TEXT_BASE settings with no luck.

How did you choose what to use? Also note that Tegra uses SPL to
start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.

>
> I am creating my sdcard with a standard linux (Linux for Tegra) rootfs:

Did these instructions come from a web site somewhere?

>
> Partition an SD card
>
> sudo cgpt create <MMC BLOCK DEVICE>
> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK DEVICE> # 16
MB
> kernel image partition
> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors> -t rootfs
> <MMC BLOCK DEVICE>
>
> cgpt doesn't seem to create a protective MBR. If one is not already in
> place, it can be created with:
>
> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
>
> Copy data to the SD card
>
> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>

How are you actually making it boot? Is this in dev mode with USB boot
enabled and pressing Ctrl-U?

Also, as this is a mailing list, please avoid top-posting.

- Simon

I am using chained boot to test uboot as a FIT image so I I don't have to
flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
chained boot?

I am using instructions to boot Linux for Tegra from sdcard/USB in
developer mode.  I can boot L4T fine with kernel v3.10.

What mainline branch should I try?


>
> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org> wrote:
>>
>> Hi Matthew,
>>
>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> > I am porting u-boot to nyan_big and need some input.  I have been
>> > searching
>> > high and low and found this thread here: [U-Boot] [PATCH 0/20] tegra:
>> > Expand
>> > Nyan-big support
>> >
>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
>> >
>> > I have tried to build u-boot with the branch here:
>> >
>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
>> >
>> > and also the official chromium next branch
>>
>> Have you tried mainline U-Boot? It already supports nyan-big. I'm not
>> sure about the situation with the downstream trees.
>>
>> >
>> > I followed building instructions here:
>> >
>> > https://www.chromium.org/chromium-os/firmware-porting-
guide/using-nv-u-boot-on-the-samsung-arm-chromebook
>> >
>> > I build with these commands:
>> >
>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its kernel-u-boot
>> >
>> > (with and without the load address setting)
>> >
>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1 --config
>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
>> >
>> > I have had numerous failed attempts to boot uboot from sdcard mmcblk1p1
>> >
>> > Any help is appreciated I have only gotten a blank screen after weeks
of
>> > flashing.  I can boot custom v3.10 kernels so I assume I am using the
>> > correct building procedure.  Thanks in advance for help from the u-boot
>> > community.
>>
>> It is possible that it needs a particular address due to limitations
>> in the FIT support on Nyan. I'm not sure what it is but might be able
>> to take a look at some point.
>>
>> How are you building your SD card? Are you following some instructions
>> from somewhere?
>>
>> Regards,
>> Simon
>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

Let me repost this to the bottom.  New to the mailing list ;)

I am using chained boot to test uboot as a FIT image so I I don't have to
flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
chained boot?

I am using instructions to boot Linux for Tegra from sdcard/USB in
developer mode.  I can boot L4T fine with kernel v3.10.

What mainline branch should I try?

On May 1, 2017 12:11 PM, "Matthew Gorski" <matt.gorski@gmail.com> wrote:

On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org> wrote:

Hi Matthew,

On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com> wrote:
> Thanks for the reply Simon.
>
> I have been trying to find the System.map for depthcharge to see the
kernel
> load address but I am unable to find anything.  I have tried multiple
> CONFIG_SYS_TEXT_BASE settings with no luck.

How did you choose what to use? Also note that Tegra uses SPL to
start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.

>
> I am creating my sdcard with a standard linux (Linux for Tegra) rootfs:

Did these instructions come from a web site somewhere?

>
> Partition an SD card
>
> sudo cgpt create <MMC BLOCK DEVICE>
> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK DEVICE> # 16
MB
> kernel image partition
> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors> -t rootfs
> <MMC BLOCK DEVICE>
>
> cgpt doesn't seem to create a protective MBR. If one is not already in
> place, it can be created with:
>
> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
>
> Copy data to the SD card
>
> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>

How are you actually making it boot? Is this in dev mode with USB boot
enabled and pressing Ctrl-U?

Also, as this is a mailing list, please avoid top-posting.

- Simon

I am using chained boot to test uboot as a FIT image so I I don't have to
flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
chained boot?

I am using instructions to boot Linux for Tegra from sdcard/USB in
developer mode.  I can boot L4T fine with kernel v3.10.

What mainline branch should I try?


>
> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org> wrote:
>>
>> Hi Matthew,
>>
>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> > I am porting u-boot to nyan_big and need some input.  I have been
>> > searching
>> > high and low and found this thread here: [U-Boot] [PATCH 0/20] tegra:
>> > Expand
>> > Nyan-big support
>> >
>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
>> >
>> > I have tried to build u-boot with the branch here:
>> >
>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
>> >
>> > and also the official chromium next branch
>>
>> Have you tried mainline U-Boot? It already supports nyan-big. I'm not
>> sure about the situation with the downstream trees.
>>
>> >
>> > I followed building instructions here:
>> >
>> > https://www.chromium.org/chromium-os/firmware-porting-guide/
using-nv-u-boot-on-the-samsung-arm-chromebook
>> >
>> > I build with these commands:
>> >
>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its kernel-u-boot
>> >
>> > (with and without the load address setting)
>> >
>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1 --config
>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
>> >
>> > I have had numerous failed attempts to boot uboot from sdcard mmcblk1p1
>> >
>> > Any help is appreciated I have only gotten a blank screen after weeks
of
>> > flashing.  I can boot custom v3.10 kernels so I assume I am using the
>> > correct building procedure.  Thanks in advance for help from the u-boot
>> > community.
>>
>> It is possible that it needs a particular address due to limitations
>> in the FIT support on Nyan. I'm not sure what it is but might be able
>> to take a look at some point.
>>
>> How are you building your SD card? Are you following some instructions
>> from somewhere?
>>
>> Regards,
>> Simon
>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Simon Glass]

Hi Matthew,

On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com> wrote:
> Let me repost this to the bottom.  New to the mailing list ;)
>
> I am using chained boot to test uboot as a FIT image so I I don't have to
> flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
> chained boot?
>
> I am using instructions to boot Linux for Tegra from sdcard/USB in developer
> mode.  I can boot L4T fine with kernel v3.10.
>
> What mainline branch should I try?

There's only one mainline, here: http://git.denx.de/?p=u-boot.git;a=summary

There are various custodian branches but I don't believe the tegra one
has anything different from mainline at present.

- Simon

>
> On May 1, 2017 12:11 PM, "Matthew Gorski" <matt.gorski@gmail.com> wrote:
>
> On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org> wrote:
>
> Hi Matthew,
>
> On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> Thanks for the reply Simon.
>>
>> I have been trying to find the System.map for depthcharge to see the
>> kernel
>> load address but I am unable to find anything.  I have tried multiple
>> CONFIG_SYS_TEXT_BASE settings with no luck.
>
> How did you choose what to use? Also note that Tegra uses SPL to
> start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
>
>>
>> I am creating my sdcard with a standard linux (Linux for Tegra) rootfs:
>
> Did these instructions come from a web site somewhere?
>
>>
>> Partition an SD card
>>
>> sudo cgpt create <MMC BLOCK DEVICE>
>> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK DEVICE> # 16
>> MB
>> kernel image partition
>> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors> -t rootfs
>> <MMC BLOCK DEVICE>
>>
>> cgpt doesn't seem to create a protective MBR. If one is not already in
>> place, it can be created with:
>>
>> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
>>
>> Copy data to the SD card
>>
>> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
>> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>>
>
> How are you actually making it boot? Is this in dev mode with USB boot
> enabled and pressing Ctrl-U?
>
> Also, as this is a mailing list, please avoid top-posting.
>
> - Simon
>
> I am using chained boot to test uboot as a FIT image so I I don't have to
> flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
> chained boot?
>
> I am using instructions to boot Linux for Tegra from sdcard/USB in developer
> mode.  I can boot L4T fine with kernel v3.10.
>
> What mainline branch should I try?
>
>
>>
>> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org> wrote:
>>>
>>> Hi Matthew,
>>>
>>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com> wrote:
>>> > I am porting u-boot to nyan_big and need some input.  I have been
>>> > searching
>>> > high and low and found this thread here: [U-Boot] [PATCH 0/20] tegra:
>>> > Expand
>>> > Nyan-big support
>>> >
>>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
>>> >
>>> > I have tried to build u-boot with the branch here:
>>> >
>>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
>>> >
>>> > and also the official chromium next branch
>>>
>>> Have you tried mainline U-Boot? It already supports nyan-big. I'm not
>>> sure about the situation with the downstream trees.
>>>
>>> >
>>> > I followed building instructions here:
>>> >
>>> >
>>> > https://www.chromium.org/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook
>>> >
>>> > I build with these commands:
>>> >
>>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its kernel-u-boot
>>> >
>>> > (with and without the load address setting)
>>> >
>>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
>>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
>>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1 --config
>>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
>>> >
>>> > I have had numerous failed attempts to boot uboot from sdcard mmcblk1p1
>>> >
>>> > Any help is appreciated I have only gotten a blank screen after weeks
>>> > of
>>> > flashing.  I can boot custom v3.10 kernels so I assume I am using the
>>> > correct building procedure.  Thanks in advance for help from the u-boot
>>> > community.
>>>
>>> It is possible that it needs a particular address due to limitations
>>> in the FIT support on Nyan. I'm not sure what it is but might be able
>>> to take a look at some point.
>>>
>>> How are you building your SD card? Are you following some instructions
>>> from somewhere?
>>>
>>> Regards,
>>> Simon
>>
>>
>
>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@chromium.org> wrote:

> Hi Matthew,
>
> On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com> wrote:
> > Let me repost this to the bottom.  New to the mailing list ;)
> >
> > I am using chained boot to test uboot as a FIT image so I I don't have to
> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
> > chained boot?
> >
> > I am using instructions to boot Linux for Tegra from sdcard/USB in
> developer
> > mode.  I can boot L4T fine with kernel v3.10.
> >
> > What mainline branch should I try?
>
> There's only one mainline, here: http://git.denx.de/?p=u-boot.
> git;a=summary
>
> There are various custodian branches but I don't believe the tegra one
> has anything different from mainline at present.
>
> - Simon
>
> I will give mainline a try with:

CONFIG_SYS_TEXT_BASE 0x8010E000
and

CONFIG_SPL_TEXT_BASE		0x80108000


I know I will also need:


CONFIG_DISPLAY_PORT=y
CONFIG_VIDEO_TEGRA124=y


for the console to display command prompt.


The FIT config I am using is from
here:https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big


Do I need to adjust:


            load = <0>;
            entry = <0>;


/dts-v1/;

/ {
    description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO
THE IMAGE STARTS AT THE RIGHT OFFSET";
    #address-cells = <1>;
    images {
        kernel at 1{
            description = "kernel";
            data = /incbin/("u-boot-dtb.bin");
            type = "kernel_noload";
            arch = "arm";
            os = "linux";
            compression = "none";
            load = <0>;
            entry = <0>;
        };
        fdt at 1{
            description = "tegra124-nyan-big.dtb";
            data = /incbin/("dts/dt.dtb");
            type = "flat_dt";
            arch = "arm";
            compression = "none";
            hash at 1{
                algo = "sha1";
            };
        };
    };
    configurations {
        default = "conf at 1";
        conf at 1{
            kernel = "kernel at 1";
            fdt = "fdt at 1";
        };
    };
};


please let me know if I should also adjust the SPL CONFIG even though
I am chainbooting uboot:

https://www.chromium.org/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing-nv-U-Boot-chained-U-Boot-method-

>
> > On May 1, 2017 12:11 PM, "Matthew Gorski" <matt.gorski@gmail.com> wrote:
> >
> > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org> wrote:
> >
> > Hi Matthew,
> >
> > On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com> wrote:
> >> Thanks for the reply Simon.
> >>
> >> I have been trying to find the System.map for depthcharge to see the
> >> kernel
> >> load address but I am unable to find anything.  I have tried multiple
> >> CONFIG_SYS_TEXT_BASE settings with no luck.
> >
> > How did you choose what to use? Also note that Tegra uses SPL to
> > start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
> >
> >>
> >> I am creating my sdcard with a standard linux (Linux for Tegra) rootfs:
> >
> > Did these instructions come from a web site somewhere?
> >
> >>
> >> Partition an SD card
> >>
> >> sudo cgpt create <MMC BLOCK DEVICE>
> >> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK DEVICE> # 16
> >> MB
> >> kernel image partition
> >> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors> -t
> rootfs
> >> <MMC BLOCK DEVICE>
> >>
> >> cgpt doesn't seem to create a protective MBR. If one is not already in
> >> place, it can be created with:
> >>
> >> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
> >>
> >> Copy data to the SD card
> >>
> >> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
> >> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
> >> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
> >>
> >
> > How are you actually making it boot? Is this in dev mode with USB boot
> > enabled and pressing Ctrl-U?
> >
> > Also, as this is a mailing list, please avoid top-posting.
> >
> > - Simon
> >
> > I am using chained boot to test uboot as a FIT image so I I don't have to
> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
> > chained boot?
> >
> > I am using instructions to boot Linux for Tegra from sdcard/USB in
> developer
> > mode.  I can boot L4T fine with kernel v3.10.
> >
> > What mainline branch should I try?
> >
> >
> >>
> >> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org> wrote:
> >>>
> >>> Hi Matthew,
> >>>
> >>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com> wrote:
> >>> > I am porting u-boot to nyan_big and need some input.  I have been
> >>> > searching
> >>> > high and low and found this thread here: [U-Boot] [PATCH 0/20] tegra:
> >>> > Expand
> >>> > Nyan-big support
> >>> >
> >>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
> >>> >
> >>> > I have tried to build u-boot with the branch here:
> >>> >
> >>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/
> commit/?h=nyan-big
> >>> >
> >>> > and also the official chromium next branch
> >>>
> >>> Have you tried mainline U-Boot? It already supports nyan-big. I'm not
> >>> sure about the situation with the downstream trees.
> >>>
> >>> >
> >>> > I followed building instructions here:
> >>> >
> >>> >
> >>> > https://www.chromium.org/chromium-os/firmware-porting-
> guide/using-nv-u-boot-on-the-samsung-arm-chromebook
> >>> >
> >>> > I build with these commands:
> >>> >
> >>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its kernel-u-boot
> >>> >
> >>> > (with and without the load address setting)
> >>> >
> >>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
> >>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
> >>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1
> --config
> >>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
> >>> >
> >>> > I have had numerous failed attempts to boot uboot from sdcard
> mmcblk1p1
> >>> >
> >>> > Any help is appreciated I have only gotten a blank screen after weeks
> >>> > of
> >>> > flashing.  I can boot custom v3.10 kernels so I assume I am using the
> >>> > correct building procedure.  Thanks in advance for help from the
> u-boot
> >>> > community.
> >>>
> >>> It is possible that it needs a particular address due to limitations
> >>> in the FIT support on Nyan. I'm not sure what it is but might be able
> >>> to take a look at some point.
> >>>
> >>> How are you building your SD card? Are you following some instructions
> >>> from somewhere?
> >>>
> >>> Regards,
> >>> Simon
> >>
> >>
> >
> >
> >
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

On Mon, May 1, 2017 at 1:26 PM, Matthew Gorski <matt.gorski@gmail.com>
wrote:

>
>
> On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@chromium.org> wrote:
>
>> Hi Matthew,
>>
>> On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> > Let me repost this to the bottom.  New to the mailing list ;)
>> >
>> > I am using chained boot to test uboot as a FIT image so I I don't have
>> to
>> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
>> > chained boot?
>> >
>> > I am using instructions to boot Linux for Tegra from sdcard/USB in
>> developer
>> > mode.  I can boot L4T fine with kernel v3.10.
>> >
>> > What mainline branch should I try?
>>
>> There's only one mainline, here: http://git.denx.de/?p=u-boot.g
>> it;a=summary
>>
>> There are various custodian branches but I don't believe the tegra one
>> has anything different from mainline at present.
>>
>> - Simon
>>
>> I will give mainline a try with:
>
> CONFIG_SYS_TEXT_BASE 0x8010E000
> and
>
> CONFIG_SPL_TEXT_BASE		0x80108000
>
>
> I know I will also need:
>
>
> CONFIG_DISPLAY_PORT=y
> CONFIG_VIDEO_TEGRA124=y
>
>
> for the console to display command prompt.
>
>
> The FIT config I am using is from here:https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
>
>
> Do I need to adjust:
>
>
>             load = <0>;
>             entry = <0>;
>
>
> /dts-v1/;
>
> / {
>     description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE IMAGE STARTS AT THE RIGHT OFFSET";
>     #address-cells = <1>;
>     images {
>         kernel at 1{
>             description = "kernel";
>             data = /incbin/("u-boot-dtb.bin");
>             type = "kernel_noload";
>             arch = "arm";
>             os = "linux";
>             compression = "none";
>             load = <0>;
>             entry = <0>;
>         };
>         fdt at 1{
>             description = "tegra124-nyan-big.dtb";
>             data = /incbin/("dts/dt.dtb");
>             type = "flat_dt";
>             arch = "arm";
>             compression = "none";
>             hash at 1{
>                 algo = "sha1";
>             };
>         };
>     };
>     configurations {
>         default = "conf at 1";
>         conf at 1{
>             kernel = "kernel at 1";
>             fdt = "fdt at 1";
>         };
>     };
> };
>
>
> please let me know if I should also adjust the SPL CONFIG even though I am chainbooting uboot:
>
> https://www.chromium.org/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing-nv-U-Boot-chained-U-Boot-method-
>
>
Okay I tried a couple kernelpart.bin builds with the
stock 0x80110000 CONFIG_SYS_TEXT_BASE and no adjustment
to CONFIG_SPL_TEXT_BASE still no u-boot prompt.

Tried CONFIG_SYS_TEXT_BASE  0x8010E000 and still no command prompt.

What setting should I use for SPL? CONFIG_SPL_TEXT_BASE ?

I read from the older thread I should be getting a command prompt and I am
familiar with porting u-boot as I have ported my own custom builds to
Toradex Apalis TK1 and also Jetson TK1 boards.

I always used the L4T SYS TEXT BASE: define CONFIG_SYS_TEXT_BASE 0x8010E000

> >
>> > On May 1, 2017 12:11 PM, "Matthew Gorski" <matt.gorski@gmail.com>
>> wrote:
>> >
>> > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org> wrote:
>> >
>> > Hi Matthew,
>> >
>> > On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> >> Thanks for the reply Simon.
>> >>
>> >> I have been trying to find the System.map for depthcharge to see the
>> >> kernel
>> >> load address but I am unable to find anything.  I have tried multiple
>> >> CONFIG_SYS_TEXT_BASE settings with no luck.
>> >
>> > How did you choose what to use? Also note that Tegra uses SPL to
>> > start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
>> >
>> >>
>> >> I am creating my sdcard with a standard linux (Linux for Tegra) rootfs:
>> >
>> > Did these instructions come from a web site somewhere?
>> >
>> >>
>> >> Partition an SD card
>> >>
>> >> sudo cgpt create <MMC BLOCK DEVICE>
>> >> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK DEVICE> #
>> 16
>> >> MB
>> >> kernel image partition
>> >> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors> -t
>> rootfs
>> >> <MMC BLOCK DEVICE>
>> >>
>> >> cgpt doesn't seem to create a protective MBR. If one is not already in
>> >> place, it can be created with:
>> >>
>> >> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
>> >>
>> >> Copy data to the SD card
>> >>
>> >> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
>> >> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>> >> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>> >>
>> >
>> > How are you actually making it boot? Is this in dev mode with USB boot
>> > enabled and pressing Ctrl-U?
>> >
>> > Also, as this is a mailing list, please avoid top-posting.
>> >
>> > - Simon
>> >
>> > I am using chained boot to test uboot as a FIT image so I I don't have
>> to
>> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
>> > chained boot?
>> >
>> > I am using instructions to boot Linux for Tegra from sdcard/USB in
>> developer
>> > mode.  I can boot L4T fine with kernel v3.10.
>> >
>> > What mainline branch should I try?
>> >
>> >
>> >>
>> >> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org> wrote:
>> >>>
>> >>> Hi Matthew,
>> >>>
>> >>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> >>> > I am porting u-boot to nyan_big and need some input.  I have been
>> >>> > searching
>> >>> > high and low and found this thread here: [U-Boot] [PATCH 0/20]
>> tegra:
>> >>> > Expand
>> >>> > Nyan-big support
>> >>> >
>> >>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
>> >>> >
>> >>> > I have tried to build u-boot with the branch here:
>> >>> >
>> >>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/
>> ?h=nyan-big
>> >>> >
>> >>> > and also the official chromium next branch
>> >>>
>> >>> Have you tried mainline U-Boot? It already supports nyan-big. I'm not
>> >>> sure about the situation with the downstream trees.
>> >>>
>> >>> >
>> >>> > I followed building instructions here:
>> >>> >
>> >>> >
>> >>> > https://www.chromium.org/chromium-os/firmware-porting-guide/
>> using-nv-u-boot-on-the-samsung-arm-chromebook
>> >>> >
>> >>> > I build with these commands:
>> >>> >
>> >>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its kernel-u-boot
>> >>> >
>> >>> > (with and without the load address setting)
>> >>> >
>> >>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
>> >>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
>> >>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1
>> --config
>> >>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
>> >>> >
>> >>> > I have had numerous failed attempts to boot uboot from sdcard
>> mmcblk1p1
>> >>> >
>> >>> > Any help is appreciated I have only gotten a blank screen after
>> weeks
>> >>> > of
>> >>> > flashing.  I can boot custom v3.10 kernels so I assume I am using
>> the
>> >>> > correct building procedure.  Thanks in advance for help from the
>> u-boot
>> >>> > community.
>> >>>
>> >>> It is possible that it needs a particular address due to limitations
>> >>> in the FIT support on Nyan. I'm not sure what it is but might be able
>> >>> to take a look at some point.
>> >>>
>> >>> How are you building your SD card? Are you following some instructions
>> >>> from somewhere?
>> >>>
>> >>> Regards,
>> >>> Simon
>> >>
>> >>
>> >
>> >
>> >
>>
>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Simon Glass]

Hi Matthew,

On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@gmail.com> wrote:
>
>
>
> On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@chromium.org> wrote:
>>
>> Hi Matthew,
>>
>> On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> > Let me repost this to the bottom.  New to the mailing list ;)
>> >
>> > I am using chained boot to test uboot as a FIT image so I I don't have to
>> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
>> > chained boot?
>> >
>> > I am using instructions to boot Linux for Tegra from sdcard/USB in developer
>> > mode.  I can boot L4T fine with kernel v3.10.
>> >
>> > What mainline branch should I try?
>>
>> There's only one mainline, here: http://git.denx.de/?p=u-boot.git;a=summary
>>
>> There are various custodian branches but I don't believe the tegra one
>> has anything different from mainline at present.
>>
>> - Simon
>>
> I will give mainline a try with:
>
> CONFIG_SYS_TEXT_BASE 0x8010E000
> and
>
> CONFIG_SPL_TEXT_BASE 0x80108000
>
>
> I know I will also need:
>
>
> CONFIG_DISPLAY_PORT=y

Do you mean CONFIG_DISPLAY? If so, it is already defined.

> CONFIG_VIDEO_TEGRA124=y

That is defined in mainline

>
>
> for the console to display command prompt.
>
>
> The FIT config I am using is from here:https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
>
>
> Do I need to adjust:
>
>
>             load = <0>;
>             entry = <0>;
>
>
> /dts-v1/;
>
> / {
>     description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE IMAGE STARTS AT THE RIGHT OFFSET";

Perhaps you need to adjust this? How was the length of it calcualted?

>     #address-cells = <1>;
>     images {
>         kernel at 1{
>             description = "kernel";
>             data = /incbin/("u-boot-dtb.bin");
>             type = "kernel_noload";
>             arch = "arm";
>             os = "linux";
>             compression = "none";
>             load = <0>;
>             entry = <0>;
>         };
>         fdt at 1{
>             description = "tegra124-nyan-big.dtb";
>             data = /incbin/("dts/dt.dtb");
>             type = "flat_dt";
>             arch = "arm";
>             compression = "none";
>             hash at 1{
>                 algo = "sha1";
>             };
>         };
>     };
>     configurations {
>         default = "conf at 1";
>         conf at 1{
>             kernel = "kernel at 1";
>             fdt = "fdt at 1";
>         };
>     };
> };
>
>
> please let me know if I should also adjust the SPL CONFIG even though I am chainbooting uboot:
>
> https://www.chromium.org/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing-nv-U-Boot-chained-U-Boot-method-

This is exynos, where we booted directly into U-Boot. Actually I'm
wondering we should boot directly into U-Boot (instead of SPL) on nyan
also. Perhaps someone at collabora would know? Did you search the
mailing list?

Regards,
Simon

>>
>> >
>> > On May 1, 2017 12:11 PM, "Matthew Gorski" <matt.gorski@gmail.com> wrote:
>> >
>> > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org> wrote:
>> >
>> > Hi Matthew,
>> >
>> > On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> >> Thanks for the reply Simon.
>> >>
>> >> I have been trying to find the System.map for depthcharge to see the
>> >> kernel
>> >> load address but I am unable to find anything.  I have tried multiple
>> >> CONFIG_SYS_TEXT_BASE settings with no luck.
>> >
>> > How did you choose what to use? Also note that Tegra uses SPL to
>> > start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
>> >
>> >>
>> >> I am creating my sdcard with a standard linux (Linux for Tegra) rootfs:
>> >
>> > Did these instructions come from a web site somewhere?
>> >
>> >>
>> >> Partition an SD card
>> >>
>> >> sudo cgpt create <MMC BLOCK DEVICE>
>> >> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK DEVICE> # 16
>> >> MB
>> >> kernel image partition
>> >> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors> -t rootfs
>> >> <MMC BLOCK DEVICE>
>> >>
>> >> cgpt doesn't seem to create a protective MBR. If one is not already in
>> >> place, it can be created with:
>> >>
>> >> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
>> >>
>> >> Copy data to the SD card
>> >>
>> >> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
>> >> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>> >> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>> >>
>> >
>> > How are you actually making it boot? Is this in dev mode with USB boot
>> > enabled and pressing Ctrl-U?
>> >
>> > Also, as this is a mailing list, please avoid top-posting.
>> >
>> > - Simon
>> >
>> > I am using chained boot to test uboot as a FIT image so I I don't have to
>> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
>> > chained boot?
>> >
>> > I am using instructions to boot Linux for Tegra from sdcard/USB in developer
>> > mode.  I can boot L4T fine with kernel v3.10.
>> >
>> > What mainline branch should I try?
>> >
>> >
>> >>
>> >> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org> wrote:
>> >>>
>> >>> Hi Matthew,
>> >>>
>> >>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> >>> > I am porting u-boot to nyan_big and need some input.  I have been
>> >>> > searching
>> >>> > high and low and found this thread here: [U-Boot] [PATCH 0/20] tegra:
>> >>> > Expand
>> >>> > Nyan-big support
>> >>> >
>> >>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
>> >>> >
>> >>> > I have tried to build u-boot with the branch here:
>> >>> >
>> >>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
>> >>> >
>> >>> > and also the official chromium next branch
>> >>>
>> >>> Have you tried mainline U-Boot? It already supports nyan-big. I'm not
>> >>> sure about the situation with the downstream trees.
>> >>>
>> >>> >
>> >>> > I followed building instructions here:
>> >>> >
>> >>> >
>> >>> > https://www.chromium.org/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook
>> >>> >
>> >>> > I build with these commands:
>> >>> >
>> >>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its kernel-u-boot
>> >>> >
>> >>> > (with and without the load address setting)
>> >>> >
>> >>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
>> >>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
>> >>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1 --config
>> >>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
>> >>> >
>> >>> > I have had numerous failed attempts to boot uboot from sdcard mmcblk1p1
>> >>> >
>> >>> > Any help is appreciated I have only gotten a blank screen after weeks
>> >>> > of
>> >>> > flashing.  I can boot custom v3.10 kernels so I assume I am using the
>> >>> > correct building procedure.  Thanks in advance for help from the u-boot
>> >>> > community.
>> >>>
>> >>> It is possible that it needs a particular address due to limitations
>> >>> in the FIT support on Nyan. I'm not sure what it is but might be able
>> >>> to take a look at some point.
>> >>>
>> >>> How are you building your SD card? Are you following some instructions
>> >>> from somewhere?
>> >>>
>> >>> Regards,
>> >>> Simon
>> >>
>> >>
>> >
>> >
>> >
>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromium.org> wrote:

> Hi Matthew,
>
> On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@gmail.com> wrote:
> >
> >
> >
> > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@chromium.org> wrote:
> >>
> >> Hi Matthew,
> >>
> >> On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com> wrote:
> >> > Let me repost this to the bottom.  New to the mailing list ;)
> >> >
> >> > I am using chained boot to test uboot as a FIT image so I I don't
> have to
> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
> >> > chained boot?
> >> >
> >> > I am using instructions to boot Linux for Tegra from sdcard/USB in
> developer
> >> > mode.  I can boot L4T fine with kernel v3.10.
> >> >
> >> > What mainline branch should I try?
> >>
> >> There's only one mainline, here: http://git.denx.de/?p=u-boot.
> git;a=summary
> >>
> >> There are various custodian branches but I don't believe the tegra one
> >> has anything different from mainline at present.
> >>
> >> - Simon
> >>
> > I will give mainline a try with:
> >
> > CONFIG_SYS_TEXT_BASE 0x8010E000
> > and
> >
> > CONFIG_SPL_TEXT_BASE 0x80108000
> >
> >
> > I know I will also need:
> >
> >
> > CONFIG_DISPLAY_PORT=y
>
> Do you mean CONFIG_DISPLAY? If so, it is already defined.
>
> > CONFIG_VIDEO_TEGRA124=y
>
> That is defined in mainline
>
> >
> >
> > for the console to display command prompt.
> >
> >
> > The FIT config I am using is from here:https://git.collabora.
> com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
> >
> >
> > Do I need to adjust:
> >
> >
> >             load = <0>;
> >             entry = <0>;
> >
> >
> > /dts-v1/;
> >
> > / {
> >     description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE
> IMAGE STARTS AT THE RIGHT OFFSET";
>
> Perhaps you need to adjust this? How was the length of it calcualted?
>

I am really not sure how the padding was calculated.  I just assumed this
kernel-big.its FIT config was correct for nyan_big.  I will try using my
working linux kernel fit config.

>
> >     #address-cells = <1>;
> >     images {
> >         kernel at 1{
> >             description = "kernel";
> >             data = /incbin/("u-boot-dtb.bin");
> >             type = "kernel_noload";
> >             arch = "arm";
> >             os = "linux";
> >             compression = "none";
> >             load = <0>;
> >             entry = <0>;
> >         };
> >         fdt at 1{
> >             description = "tegra124-nyan-big.dtb";
> >             data = /incbin/("dts/dt.dtb");
> >             type = "flat_dt";
> >             arch = "arm";
> >             compression = "none";
> >             hash at 1{
> >                 algo = "sha1";
> >             };
> >         };
> >     };
> >     configurations {
> >         default = "conf at 1";
> >         conf at 1{
> >             kernel = "kernel at 1";
> >             fdt = "fdt at 1";
> >         };
> >     };
> > };
> >
> >
> > please let me know if I should also adjust the SPL CONFIG even though I
> am chainbooting uboot:
> >
> > https://www.chromium.org/chromium-os/firmware-porting-
> guide/using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-
> Installing-nv-U-Boot-chained-U-Boot-method-
>
> This is exynos, where we booted directly into U-Boot. Actually I'm
> wondering we should boot directly into U-Boot (instead of SPL) on nyan
> also. Perhaps someone at collabora would know? Did you search the
> mailing list?
>
> Regards,
> Simon
>

I have not searched the mailing list.  What should I search for?  Booting
nyan to u-boot directly bypassing SPL?

>
> >>
> >> >
> >> > On May 1, 2017 12:11 PM, "Matthew Gorski" <matt.gorski@gmail.com>
> wrote:
> >> >
> >> > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org> wrote:
> >> >
> >> > Hi Matthew,
> >> >
> >> > On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com> wrote:
> >> >> Thanks for the reply Simon.
> >> >>
> >> >> I have been trying to find the System.map for depthcharge to see the
> >> >> kernel
> >> >> load address but I am unable to find anything.  I have tried multiple
> >> >> CONFIG_SYS_TEXT_BASE settings with no luck.
> >> >
> >> > How did you choose what to use? Also note that Tegra uses SPL to
> >> > start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
> >> >
> >> >>
> >> >> I am creating my sdcard with a standard linux (Linux for Tegra)
> rootfs:
> >> >
> >> > Did these instructions come from a web site somewhere?
> >> >
> >> >>
> >> >> Partition an SD card
> >> >>
> >> >> sudo cgpt create <MMC BLOCK DEVICE>
> >> >> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK DEVICE>
> # 16
> >> >> MB
> >> >> kernel image partition
> >> >> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors> -t
> rootfs
> >> >> <MMC BLOCK DEVICE>
> >> >>
> >> >> cgpt doesn't seem to create a protective MBR. If one is not already
> in
> >> >> place, it can be created with:
> >> >>
> >> >> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
> >> >>
> >> >> Copy data to the SD card
> >> >>
> >> >> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
> >> >> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
> >> >> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
> >> >>
> >> >
> >> > How are you actually making it boot? Is this in dev mode with USB boot
> >> > enabled and pressing Ctrl-U?
> >> >
> >> > Also, as this is a mailing list, please avoid top-posting.
> >> >
> >> > - Simon
> >> >
> >> > I am using chained boot to test uboot as a FIT image so I I don't
> have to
> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted for
> >> > chained boot?
> >> >
> >> > I am using instructions to boot Linux for Tegra from sdcard/USB in
> developer
> >> > mode.  I can boot L4T fine with kernel v3.10.
> >> >
> >> > What mainline branch should I try?
> >> >
> >> >
> >> >>
> >> >> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org>
> wrote:
> >> >>>
> >> >>> Hi Matthew,
> >> >>>
> >> >>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com>
> wrote:
> >> >>> > I am porting u-boot to nyan_big and need some input.  I have been
> >> >>> > searching
> >> >>> > high and low and found this thread here: [U-Boot] [PATCH 0/20]
> tegra:
> >> >>> > Expand
> >> >>> > Nyan-big support
> >> >>> >
> >> >>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
> >> >>> >
> >> >>> > I have tried to build u-boot with the branch here:
> >> >>> >
> >> >>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/
> commit/?h=nyan-big
> >> >>> >
> >> >>> > and also the official chromium next branch
> >> >>>
> >> >>> Have you tried mainline U-Boot? It already supports nyan-big. I'm
> not
> >> >>> sure about the situation with the downstream trees.
> >> >>>
> >> >>> >
> >> >>> > I followed building instructions here:
> >> >>> >
> >> >>> >
> >> >>> > https://www.chromium.org/chromium-os/firmware-porting-
> guide/using-nv-u-boot-on-the-samsung-arm-chromebook
> >> >>> >
> >> >>> > I build with these commands:
> >> >>> >
> >> >>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its
> kernel-u-boot
> >> >>> >
> >> >>> > (with and without the load address setting)
> >> >>> >
> >> >>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
> >> >>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
> >> >>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1
> --config
> >> >>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
> >> >>> >
> >> >>> > I have had numerous failed attempts to boot uboot from sdcard
> mmcblk1p1
> >> >>> >
> >> >>> > Any help is appreciated I have only gotten a blank screen after
> weeks
> >> >>> > of
> >> >>> > flashing.  I can boot custom v3.10 kernels so I assume I am using
> the
> >> >>> > correct building procedure.  Thanks in advance for help from the
> u-boot
> >> >>> > community.
> >> >>>
> >> >>> It is possible that it needs a particular address due to limitations
> >> >>> in the FIT support on Nyan. I'm not sure what it is but might be
> able
> >> >>> to take a look at some point.
> >> >>>
> >> >>> How are you building your SD card? Are you following some
> instructions
> >> >>> from somewhere?
> >> >>>
> >> >>> Regards,
> >> >>> Simon
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >
> >
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Simon Glass]

Hi Matthew,

On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail.com> wrote:
>
>
> On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromium.org> wrote:
>>
>> Hi Matthew,
>>
>> On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> >
>> >
>> >
>> > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@chromium.org> wrote:
>> >>
>> >> Hi Matthew,
>> >>
>> >> On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> >> > Let me repost this to the bottom.  New to the mailing list ;)
>> >> >
>> >> > I am using chained boot to test uboot as a FIT image so I I don't
>> >> > have to
>> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted
>> >> > for
>> >> > chained boot?
>> >> >
>> >> > I am using instructions to boot Linux for Tegra from sdcard/USB in
>> >> > developer
>> >> > mode.  I can boot L4T fine with kernel v3.10.
>> >> >
>> >> > What mainline branch should I try?
>> >>
>> >> There's only one mainline, here:
>> >> http://git.denx.de/?p=u-boot.git;a=summary
>> >>
>> >> There are various custodian branches but I don't believe the tegra one
>> >> has anything different from mainline at present.
>> >>
>> >> - Simon
>> >>
>> > I will give mainline a try with:
>> >
>> > CONFIG_SYS_TEXT_BASE 0x8010E000
>> > and
>> >
>> > CONFIG_SPL_TEXT_BASE 0x80108000
>> >
>> >
>> > I know I will also need:
>> >
>> >
>> > CONFIG_DISPLAY_PORT=y
>>
>> Do you mean CONFIG_DISPLAY? If so, it is already defined.
>>
>> > CONFIG_VIDEO_TEGRA124=y
>>
>> That is defined in mainline
>>
>> >
>> >
>> > for the console to display command prompt.
>> >
>> >
>> > The FIT config I am using is from
>> > here:https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
>> >
>> >
>> > Do I need to adjust:
>> >
>> >
>> >             load = <0>;
>> >             entry = <0>;
>> >
>> >
>> > /dts-v1/;
>> >
>> > / {
>> >     description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE
>> > IMAGE STARTS AT THE RIGHT OFFSET";
>>
>> Perhaps you need to adjust this? How was the length of it calcualted?
>
>
> I am really not sure how the padding was calculated.  I just assumed this
> kernel-big.its FIT config was correct for nyan_big.  I will try using my
> working linux kernel fit config.
>>
>>
>> >     #address-cells = <1>;
>> >     images {
>> >         kernel at 1{
>> >             description = "kernel";
>> >             data = /incbin/("u-boot-dtb.bin");
>> >             type = "kernel_noload";
>> >             arch = "arm";
>> >             os = "linux";
>> >             compression = "none";
>> >             load = <0>;
>> >             entry = <0>;
>> >         };
>> >         fdt at 1{
>> >             description = "tegra124-nyan-big.dtb";
>> >             data = /incbin/("dts/dt.dtb");
>> >             type = "flat_dt";
>> >             arch = "arm";
>> >             compression = "none";
>> >             hash at 1{
>> >                 algo = "sha1";
>> >             };
>> >         };
>> >     };
>> >     configurations {
>> >         default = "conf at 1";
>> >         conf at 1{
>> >             kernel = "kernel at 1";
>> >             fdt = "fdt at 1";
>> >         };
>> >     };
>> > };
>> >
>> >
>> > please let me know if I should also adjust the SPL CONFIG even though I
>> > am chainbooting uboot:
>> >
>> >
>> > https://www.chromium.org/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing-nv-U-Boot-chained-U-Boot-method-
>>
>> This is exynos, where we booted directly into U-Boot. Actually I'm
>> wondering we should boot directly into U-Boot (instead of SPL) on nyan
>> also. Perhaps someone at collabora would know? Did you search the
>> mailing list?
>>
>> Regards,
>> Simon
>
>
> I have not searched the mailing list.  What should I search for?  Booting
> nyan to u-boot directly bypassing SPL?

Here are two subjects to search for:

Veyron-speedy u-boot
[PATCH 0/20] tegra: Expand Nyan-big support

Regards,
Simon

>>
>>
>> >>
>> >> >
>> >> > On May 1, 2017 12:11 PM, "Matthew Gorski" <matt.gorski@gmail.com>
>> >> > wrote:
>> >> >
>> >> > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org> wrote:
>> >> >
>> >> > Hi Matthew,
>> >> >
>> >> > On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> >> >> Thanks for the reply Simon.
>> >> >>
>> >> >> I have been trying to find the System.map for depthcharge to see the
>> >> >> kernel
>> >> >> load address but I am unable to find anything.  I have tried
>> >> >> multiple
>> >> >> CONFIG_SYS_TEXT_BASE settings with no luck.
>> >> >
>> >> > How did you choose what to use? Also note that Tegra uses SPL to
>> >> > start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
>> >> >
>> >> >>
>> >> >> I am creating my sdcard with a standard linux (Linux for Tegra)
>> >> >> rootfs:
>> >> >
>> >> > Did these instructions come from a web site somewhere?
>> >> >
>> >> >>
>> >> >> Partition an SD card
>> >> >>
>> >> >> sudo cgpt create <MMC BLOCK DEVICE>
>> >> >> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK DEVICE>
>> >> >> # 16
>> >> >> MB
>> >> >> kernel image partition
>> >> >> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors> -t
>> >> >> rootfs
>> >> >> <MMC BLOCK DEVICE>
>> >> >>
>> >> >> cgpt doesn't seem to create a protective MBR. If one is not already
>> >> >> in
>> >> >> place, it can be created with:
>> >> >>
>> >> >> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
>> >> >>
>> >> >> Copy data to the SD card
>> >> >>
>> >> >> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
>> >> >> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>> >> >> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>> >> >>
>> >> >
>> >> > How are you actually making it boot? Is this in dev mode with USB
>> >> > boot
>> >> > enabled and pressing Ctrl-U?
>> >> >
>> >> > Also, as this is a mailing list, please avoid top-posting.
>> >> >
>> >> > - Simon
>> >> >
>> >> > I am using chained boot to test uboot as a FIT image so I I don't
>> >> > have to
>> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted
>> >> > for
>> >> > chained boot?
>> >> >
>> >> > I am using instructions to boot Linux for Tegra from sdcard/USB in
>> >> > developer
>> >> > mode.  I can boot L4T fine with kernel v3.10.
>> >> >
>> >> > What mainline branch should I try?
>> >> >
>> >> >
>> >> >>
>> >> >> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org>
>> >> >> wrote:
>> >> >>>
>> >> >>> Hi Matthew,
>> >> >>>
>> >> >>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com>
>> >> >>> wrote:
>> >> >>> > I am porting u-boot to nyan_big and need some input.  I have been
>> >> >>> > searching
>> >> >>> > high and low and found this thread here: [U-Boot] [PATCH 0/20]
>> >> >>> > tegra:
>> >> >>> > Expand
>> >> >>> > Nyan-big support
>> >> >>> >
>> >> >>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
>> >> >>> >
>> >> >>> > I have tried to build u-boot with the branch here:
>> >> >>> >
>> >> >>> >
>> >> >>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
>> >> >>> >
>> >> >>> > and also the official chromium next branch
>> >> >>>
>> >> >>> Have you tried mainline U-Boot? It already supports nyan-big. I'm
>> >> >>> not
>> >> >>> sure about the situation with the downstream trees.
>> >> >>>
>> >> >>> >
>> >> >>> > I followed building instructions here:
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> > https://www.chromium.org/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook
>> >> >>> >
>> >> >>> > I build with these commands:
>> >> >>> >
>> >> >>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its
>> >> >>> > kernel-u-boot
>> >> >>> >
>> >> >>> > (with and without the load address setting)
>> >> >>> >
>> >> >>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
>> >> >>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
>> >> >>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1
>> >> >>> > --config
>> >> >>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
>> >> >>> >
>> >> >>> > I have had numerous failed attempts to boot uboot from sdcard
>> >> >>> > mmcblk1p1
>> >> >>> >
>> >> >>> > Any help is appreciated I have only gotten a blank screen after
>> >> >>> > weeks
>> >> >>> > of
>> >> >>> > flashing.  I can boot custom v3.10 kernels so I assume I am using
>> >> >>> > the
>> >> >>> > correct building procedure.  Thanks in advance for help from the
>> >> >>> > u-boot
>> >> >>> > community.
>> >> >>>
>> >> >>> It is possible that it needs a particular address due to
>> >> >>> limitations
>> >> >>> in the FIT support on Nyan. I'm not sure what it is but might be
>> >> >>> able
>> >> >>> to take a look at some point.
>> >> >>>
>> >> >>> How are you building your SD card? Are you following some
>> >> >>> instructions
>> >> >>> from somewhere?
>> >> >>>
>> >> >>> Regards,
>> >> >>> Simon
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >
>> >
>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

First off THANK YOU Simon for all the help and time.  I am making progress
now.

I found this here: https://lists.denx.de/pipermail/u-boot/2017-
February/281572.html

I adjusted my FIT its and now the display flashes like its entering u-boot
but immediately reboots into chromeos usb recovery.  I used the same fit
config I am using for a regular kernel and I am using mainline master
branch.

 /dts-v1/;

/ {
    description = "Chrome OS kernel image with one or more FDT blobs";
    images {
        kernel at 1{
            description = "kernel";
            data = /incbin/("u-boot-dtb.bin");
            type = "kernel_noload";
            arch = "arm";
            os = "linux";
            compression = "none";
            load = <0>;
            entry = <0>;
        };
        fdt at 1{
            description = "tegra124-nyan-big.dtb";
            data = /incbin/("dts/dt.dtb");
            type = "flat_dt";
            arch = "arm";
            compression = "none";
            hash at 1{
                algo = "sha1";
            };
        };
    };
    configurations {
        default = "conf at 1";
        conf at 1{
            kernel = "kernel at 1";
            fdt = "fdt at 1";
        };
    };
};

How do I adjust the padding in the FIT its file as shown here: #address-cells
= <1>; and is it needed at all?

+/ {
+ description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE IMAGE
STARTS AT THE RIGHT OFFSET";
+ #address-cells = <1>;
+ images {
+ kernel at 1{

On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.org> wrote:

> Hi Matthew,
>
> On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail.com> wrote:
> >
> >
> > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromium.org> wrote:
> >>
> >> Hi Matthew,
> >>
> >> On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@gmail.com> wrote:
> >> >
> >> >
> >> >
> >> > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@chromium.org> wrote:
> >> >>
> >> >> Hi Matthew,
> >> >>
> >> >> On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com>
> wrote:
> >> >> > Let me repost this to the bottom.  New to the mailing list ;)
> >> >> >
> >> >> > I am using chained boot to test uboot as a FIT image so I I don't
> >> >> > have to
> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted
> >> >> > for
> >> >> > chained boot?
> >> >> >
> >> >> > I am using instructions to boot Linux for Tegra from sdcard/USB in
> >> >> > developer
> >> >> > mode.  I can boot L4T fine with kernel v3.10.
> >> >> >
> >> >> > What mainline branch should I try?
> >> >>
> >> >> There's only one mainline, here:
> >> >> http://git.denx.de/?p=u-boot.git;a=summary
> >> >>
> >> >> There are various custodian branches but I don't believe the tegra
> one
> >> >> has anything different from mainline at present.
> >> >>
> >> >> - Simon
> >> >>
> >> > I will give mainline a try with:
> >> >
> >> > CONFIG_SYS_TEXT_BASE 0x8010E000
> >> > and
> >> >
> >> > CONFIG_SPL_TEXT_BASE 0x80108000
> >> >
> >> >
> >> > I know I will also need:
> >> >
> >> >
> >> > CONFIG_DISPLAY_PORT=y
> >>
> >> Do you mean CONFIG_DISPLAY? If so, it is already defined.
> >>
> >> > CONFIG_VIDEO_TEGRA124=y
> >>
> >> That is defined in mainline
> >>
> >> >
> >> >
> >> > for the console to display command prompt.
> >> >
> >> >
> >> > The FIT config I am using is from
> >> > here:https://git.collabora.com/cgit/user/tomeu/u-boot.
> git/commit/?h=nyan-big
> >> >
> >> >
> >> > Do I need to adjust:
> >> >
> >> >
> >> >             load = <0>;
> >> >             entry = <0>;
> >> >
> >> >
> >> > /dts-v1/;
> >> >
> >> > / {
> >> >     description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO
> THE
> >> > IMAGE STARTS AT THE RIGHT OFFSET";
> >>
> >> Perhaps you need to adjust this? How was the length of it calcualted?
> >
> >
> > I am really not sure how the padding was calculated.  I just assumed this
> > kernel-big.its FIT config was correct for nyan_big.  I will try using my
> > working linux kernel fit config.
> >>
> >>
> >> >     #address-cells = <1>;
> >> >     images {
> >> >         kernel at 1{
> >> >             description = "kernel";
> >> >             data = /incbin/("u-boot-dtb.bin");
> >> >             type = "kernel_noload";
> >> >             arch = "arm";
> >> >             os = "linux";
> >> >             compression = "none";
> >> >             load = <0>;
> >> >             entry = <0>;
> >> >         };
> >> >         fdt at 1{
> >> >             description = "tegra124-nyan-big.dtb";
> >> >             data = /incbin/("dts/dt.dtb");
> >> >             type = "flat_dt";
> >> >             arch = "arm";
> >> >             compression = "none";
> >> >             hash at 1{
> >> >                 algo = "sha1";
> >> >             };
> >> >         };
> >> >     };
> >> >     configurations {
> >> >         default = "conf at 1";
> >> >         conf at 1{
> >> >             kernel = "kernel at 1";
> >> >             fdt = "fdt at 1";
> >> >         };
> >> >     };
> >> > };
> >> >
> >> >
> >> > please let me know if I should also adjust the SPL CONFIG even though
> I
> >> > am chainbooting uboot:
> >> >
> >> >
> >> > https://www.chromium.org/chromium-os/firmware-porting-
> guide/using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-
> Installing-nv-U-Boot-chained-U-Boot-method-
> >>
> >> This is exynos, where we booted directly into U-Boot. Actually I'm
> >> wondering we should boot directly into U-Boot (instead of SPL) on nyan
> >> also. Perhaps someone at collabora would know? Did you search the
> >> mailing list?
> >>
> >> Regards,
> >> Simon
> >
> >
> > I have not searched the mailing list.  What should I search for?  Booting
> > nyan to u-boot directly bypassing SPL?
>
> Here are two subjects to search for:
>
> Veyron-speedy u-boot
> [PATCH 0/20] tegra: Expand Nyan-big support
>
> Regards,
> Simon
>
> >>
> >>
> >> >>
> >> >> >
> >> >> > On May 1, 2017 12:11 PM, "Matthew Gorski" <matt.gorski@gmail.com>
> >> >> > wrote:
> >> >> >
> >> >> > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org> wrote:
> >> >> >
> >> >> > Hi Matthew,
> >> >> >
> >> >> > On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com>
> wrote:
> >> >> >> Thanks for the reply Simon.
> >> >> >>
> >> >> >> I have been trying to find the System.map for depthcharge to see
> the
> >> >> >> kernel
> >> >> >> load address but I am unable to find anything.  I have tried
> >> >> >> multiple
> >> >> >> CONFIG_SYS_TEXT_BASE settings with no luck.
> >> >> >
> >> >> > How did you choose what to use? Also note that Tegra uses SPL to
> >> >> > start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
> >> >> >
> >> >> >>
> >> >> >> I am creating my sdcard with a standard linux (Linux for Tegra)
> >> >> >> rootfs:
> >> >> >
> >> >> > Did these instructions come from a web site somewhere?
> >> >> >
> >> >> >>
> >> >> >> Partition an SD card
> >> >> >>
> >> >> >> sudo cgpt create <MMC BLOCK DEVICE>
> >> >> >> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK
> DEVICE>
> >> >> >> # 16
> >> >> >> MB
> >> >> >> kernel image partition
> >> >> >> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors> -t
> >> >> >> rootfs
> >> >> >> <MMC BLOCK DEVICE>
> >> >> >>
> >> >> >> cgpt doesn't seem to create a protective MBR. If one is not
> already
> >> >> >> in
> >> >> >> place, it can be created with:
> >> >> >>
> >> >> >> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
> >> >> >>
> >> >> >> Copy data to the SD card
> >> >> >>
> >> >> >> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
> >> >> >> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
> >> >> >> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
> >> >> >>
> >> >> >
> >> >> > How are you actually making it boot? Is this in dev mode with USB
> >> >> > boot
> >> >> > enabled and pressing Ctrl-U?
> >> >> >
> >> >> > Also, as this is a mailing list, please avoid top-posting.
> >> >> >
> >> >> > - Simon
> >> >> >
> >> >> > I am using chained boot to test uboot as a FIT image so I I don't
> >> >> > have to
> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted
> >> >> > for
> >> >> > chained boot?
> >> >> >
> >> >> > I am using instructions to boot Linux for Tegra from sdcard/USB in
> >> >> > developer
> >> >> > mode.  I can boot L4T fine with kernel v3.10.
> >> >> >
> >> >> > What mainline branch should I try?
> >> >> >
> >> >> >
> >> >> >>
> >> >> >> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org>
> >> >> >> wrote:
> >> >> >>>
> >> >> >>> Hi Matthew,
> >> >> >>>
> >> >> >>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com>
> >> >> >>> wrote:
> >> >> >>> > I am porting u-boot to nyan_big and need some input.  I have
> been
> >> >> >>> > searching
> >> >> >>> > high and low and found this thread here: [U-Boot] [PATCH 0/20]
> >> >> >>> > tegra:
> >> >> >>> > Expand
> >> >> >>> > Nyan-big support
> >> >> >>> >
> >> >> >>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
> >> >> >>> >
> >> >> >>> > I have tried to build u-boot with the branch here:
> >> >> >>> >
> >> >> >>> >
> >> >> >>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/
> commit/?h=nyan-big
> >> >> >>> >
> >> >> >>> > and also the official chromium next branch
> >> >> >>>
> >> >> >>> Have you tried mainline U-Boot? It already supports nyan-big. I'm
> >> >> >>> not
> >> >> >>> sure about the situation with the downstream trees.
> >> >> >>>
> >> >> >>> >
> >> >> >>> > I followed building instructions here:
> >> >> >>> >
> >> >> >>> >
> >> >> >>> >
> >> >> >>> > https://www.chromium.org/chromium-os/firmware-porting-
> guide/using-nv-u-boot-on-the-samsung-arm-chromebook
> >> >> >>> >
> >> >> >>> > I build with these commands:
> >> >> >>> >
> >> >> >>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its
> >> >> >>> > kernel-u-boot
> >> >> >>> >
> >> >> >>> > (with and without the load address setting)
> >> >> >>> >
> >> >> >>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
> >> >> >>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
> >> >> >>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1
> >> >> >>> > --config
> >> >> >>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
> >> >> >>> >
> >> >> >>> > I have had numerous failed attempts to boot uboot from sdcard
> >> >> >>> > mmcblk1p1
> >> >> >>> >
> >> >> >>> > Any help is appreciated I have only gotten a blank screen after
> >> >> >>> > weeks
> >> >> >>> > of
> >> >> >>> > flashing.  I can boot custom v3.10 kernels so I assume I am
> using
> >> >> >>> > the
> >> >> >>> > correct building procedure.  Thanks in advance for help from
> the
> >> >> >>> > u-boot
> >> >> >>> > community.
> >> >> >>>
> >> >> >>> It is possible that it needs a particular address due to
> >> >> >>> limitations
> >> >> >>> in the FIT support on Nyan. I'm not sure what it is but might be
> >> >> >>> able
> >> >> >>> to take a look at some point.
> >> >> >>>
> >> >> >>> How are you building your SD card? Are you following some
> >> >> >>> instructions
> >> >> >>> from somewhere?
> >> >> >>>
> >> >> >>> Regards,
> >> >> >>> Simon
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >
> >> >
> >
> >
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.org> wrote:

> Hi Matthew,
>
> On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail.com> wrote:
> >
> >
> > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromium.org> wrote:
> >>
> >> Hi Matthew,
> >>
> >> On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@gmail.com> wrote:
> >> >
> >> >
> >> >
> >> > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@chromium.org> wrote:
> >> >>
> >> >> Hi Matthew,
> >> >>
> >> >> On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com>
> wrote:
> >> >> > Let me repost this to the bottom.  New to the mailing list ;)
> >> >> >
> >> >> > I am using chained boot to test uboot as a FIT image so I I don't
> >> >> > have to
> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted
> >> >> > for
> >> >> > chained boot?
> >> >> >
> >> >> > I am using instructions to boot Linux for Tegra from sdcard/USB in
> >> >> > developer
> >> >> > mode.  I can boot L4T fine with kernel v3.10.
> >> >> >
> >> >> > What mainline branch should I try?
> >> >>
> >> >> There's only one mainline, here:
> >> >> http://git.denx.de/?p=u-boot.git;a=summary
> >> >>
> >> >> There are various custodian branches but I don't believe the tegra
> one
> >> >> has anything different from mainline at present.
> >> >>
> >> >> - Simon
> >> >>
> >> > I will give mainline a try with:
> >> >
> >> > CONFIG_SYS_TEXT_BASE 0x8010E000
> >> > and
> >> >
> >> > CONFIG_SPL_TEXT_BASE 0x80108000
> >> >
> >> >
> >> > I know I will also need:
> >> >
> >> >
> >> > CONFIG_DISPLAY_PORT=y
> >>
> >> Do you mean CONFIG_DISPLAY? If so, it is already defined.
> >>
> >> > CONFIG_VIDEO_TEGRA124=y
> >>
> >> That is defined in mainline
> >>
> >> >
> >> >
> >> > for the console to display command prompt.
> >> >
> >> >
> >> > The FIT config I am using is from
> >> > here:https://git.collabora.com/cgit/user/tomeu/u-boot.
> git/commit/?h=nyan-big
> >> >
> >> >
> >> > Do I need to adjust:
> >> >
> >> >
> >> >             load = <0>;
> >> >             entry = <0>;
> >> >
> >> >
> >> > /dts-v1/;
> >> >
> >> > / {
> >> >     description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO
> THE
> >> > IMAGE STARTS AT THE RIGHT OFFSET";
> >>
> >> Perhaps you need to adjust this? How was the length of it calcualted?
> >
> >
> > I am really not sure how the padding was calculated.  I just assumed this
> > kernel-big.its FIT config was correct for nyan_big.  I will try using my
> > working linux kernel fit config.
> >>
> >>
> >> >     #address-cells = <1>;
> >> >     images {
> >> >         kernel at 1{
> >> >             description = "kernel";
> >> >             data = /incbin/("u-boot-dtb.bin");
> >> >             type = "kernel_noload";
> >> >             arch = "arm";
> >> >             os = "linux";
> >> >             compression = "none";
> >> >             load = <0>;
> >> >             entry = <0>;
> >> >         };
> >> >         fdt at 1{
> >> >             description = "tegra124-nyan-big.dtb";
> >> >             data = /incbin/("dts/dt.dtb");
> >> >             type = "flat_dt";
> >> >             arch = "arm";
> >> >             compression = "none";
> >> >             hash at 1{
> >> >                 algo = "sha1";
> >> >             };
> >> >         };
> >> >     };
> >> >     configurations {
> >> >         default = "conf at 1";
> >> >         conf at 1{
> >> >             kernel = "kernel at 1";
> >> >             fdt = "fdt at 1";
> >> >         };
> >> >     };
> >> > };
> >> >
> >> >
> >> > please let me know if I should also adjust the SPL CONFIG even though
> I
> >> > am chainbooting uboot:
> >> >
> >> >
> >> > https://www.chromium.org/chromium-os/firmware-porting-
> guide/using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-
> Installing-nv-U-Boot-chained-U-Boot-method-
> >>
> >> This is exynos, where we booted directly into U-Boot. Actually I'm
> >> wondering we should boot directly into U-Boot (instead of SPL) on nyan
> >> also. Perhaps someone at collabora would know? Did you search the
> >> mailing list?
> >>
> >> Regards,
> >> Simon
> >
> >
> > I have not searched the mailing list.  What should I search for?  Booting
> > nyan to u-boot directly bypassing SPL?
>
> Here are two subjects to search for:
>
> Veyron-speedy u-boot
> [PATCH 0/20] tegra: Expand Nyan-big support
>
> Regards,
> Simon
>

Very odd if I do not use "#address-cells = <1>;" the display flashes and
reboots into recovery but if I do use #address-cells = <1>; in my FIT
config I get a blank screen
so something is working when not using the padding.

/dts-v1/;

/ {
    description = "Chrome OS nyan u-boot chain boot method";
    #address-cells = <1>;
    images {
        kernel at 1{


> >>
> >>
> >> >>
> >> >> >
> >> >> > On May 1, 2017 12:11 PM, "Matthew Gorski" <matt.gorski@gmail.com>
> >> >> > wrote:
> >> >> >
> >> >> > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org> wrote:
> >> >> >
> >> >> > Hi Matthew,
> >> >> >
> >> >> > On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com>
> wrote:
> >> >> >> Thanks for the reply Simon.
> >> >> >>
> >> >> >> I have been trying to find the System.map for depthcharge to see
> the
> >> >> >> kernel
> >> >> >> load address but I am unable to find anything.  I have tried
> >> >> >> multiple
> >> >> >> CONFIG_SYS_TEXT_BASE settings with no luck.
> >> >> >
> >> >> > How did you choose what to use? Also note that Tegra uses SPL to
> >> >> > start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
> >> >> >
> >> >> >>
> >> >> >> I am creating my sdcard with a standard linux (Linux for Tegra)
> >> >> >> rootfs:
> >> >> >
> >> >> > Did these instructions come from a web site somewhere?
> >> >> >
> >> >> >>
> >> >> >> Partition an SD card
> >> >> >>
> >> >> >> sudo cgpt create <MMC BLOCK DEVICE>
> >> >> >> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK
> DEVICE>
> >> >> >> # 16
> >> >> >> MB
> >> >> >> kernel image partition
> >> >> >> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors> -t
> >> >> >> rootfs
> >> >> >> <MMC BLOCK DEVICE>
> >> >> >>
> >> >> >> cgpt doesn't seem to create a protective MBR. If one is not
> already
> >> >> >> in
> >> >> >> place, it can be created with:
> >> >> >>
> >> >> >> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
> >> >> >>
> >> >> >> Copy data to the SD card
> >> >> >>
> >> >> >> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
> >> >> >> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
> >> >> >> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
> >> >> >>
> >> >> >
> >> >> > How are you actually making it boot? Is this in dev mode with USB
> >> >> > boot
> >> >> > enabled and pressing Ctrl-U?
> >> >> >
> >> >> > Also, as this is a mailing list, please avoid top-posting.
> >> >> >
> >> >> > - Simon
> >> >> >
> >> >> > I am using chained boot to test uboot as a FIT image so I I don't
> >> >> > have to
> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted
> >> >> > for
> >> >> > chained boot?
> >> >> >
> >> >> > I am using instructions to boot Linux for Tegra from sdcard/USB in
> >> >> > developer
> >> >> > mode.  I can boot L4T fine with kernel v3.10.
> >> >> >
> >> >> > What mainline branch should I try?
> >> >> >
> >> >> >
> >> >> >>
> >> >> >> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org>
> >> >> >> wrote:
> >> >> >>>
> >> >> >>> Hi Matthew,
> >> >> >>>
> >> >> >>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com>
> >> >> >>> wrote:
> >> >> >>> > I am porting u-boot to nyan_big and need some input.  I have
> been
> >> >> >>> > searching
> >> >> >>> > high and low and found this thread here: [U-Boot] [PATCH 0/20]
> >> >> >>> > tegra:
> >> >> >>> > Expand
> >> >> >>> > Nyan-big support
> >> >> >>> >
> >> >> >>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
> >> >> >>> >
> >> >> >>> > I have tried to build u-boot with the branch here:
> >> >> >>> >
> >> >> >>> >
> >> >> >>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/
> commit/?h=nyan-big
> >> >> >>> >
> >> >> >>> > and also the official chromium next branch
> >> >> >>>
> >> >> >>> Have you tried mainline U-Boot? It already supports nyan-big. I'm
> >> >> >>> not
> >> >> >>> sure about the situation with the downstream trees.
> >> >> >>>
> >> >> >>> >
> >> >> >>> > I followed building instructions here:
> >> >> >>> >
> >> >> >>> >
> >> >> >>> >
> >> >> >>> > https://www.chromium.org/chromium-os/firmware-porting-
> guide/using-nv-u-boot-on-the-samsung-arm-chromebook
> >> >> >>> >
> >> >> >>> > I build with these commands:
> >> >> >>> >
> >> >> >>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its
> >> >> >>> > kernel-u-boot
> >> >> >>> >
> >> >> >>> > (with and without the load address setting)
> >> >> >>> >
> >> >> >>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
> >> >> >>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
> >> >> >>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1
> >> >> >>> > --config
> >> >> >>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
> >> >> >>> >
> >> >> >>> > I have had numerous failed attempts to boot uboot from sdcard
> >> >> >>> > mmcblk1p1
> >> >> >>> >
> >> >> >>> > Any help is appreciated I have only gotten a blank screen after
> >> >> >>> > weeks
> >> >> >>> > of
> >> >> >>> > flashing.  I can boot custom v3.10 kernels so I assume I am
> using
> >> >> >>> > the
> >> >> >>> > correct building procedure.  Thanks in advance for help from
> the
> >> >> >>> > u-boot
> >> >> >>> > community.
> >> >> >>>
> >> >> >>> It is possible that it needs a particular address due to
> >> >> >>> limitations
> >> >> >>> in the FIT support on Nyan. I'm not sure what it is but might be
> >> >> >>> able
> >> >> >>> to take a look at some point.
> >> >> >>>
> >> >> >>> How are you building your SD card? Are you following some
> >> >> >>> instructions
> >> >> >>> from somewhere?
> >> >> >>>
> >> >> >>> Regards,
> >> >> >>> Simon
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> >
> >> >
> >> >
> >
> >
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Simon Glass]

Hi Matthew,

On 1 May 2017 at 17:27, Matthew Gorski <matt.gorski@gmail.com> wrote:
>
>
> On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.org> wrote:
>>
>> Hi Matthew,
>>
>> On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> >
>> >
>> > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromium.org> wrote:
>> >>
>> >> Hi Matthew,
>> >>
>> >> On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> >> >
>> >> >
>> >> >
>> >> > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@chromium.org> wrote:
>> >> >>
>> >> >> Hi Matthew,
>> >> >>
>> >> >> On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com>
>> >> >> wrote:
>> >> >> > Let me repost this to the bottom.  New to the mailing list ;)
>> >> >> >
>> >> >> > I am using chained boot to test uboot as a FIT image so I I don't
>> >> >> > have to
>> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted
>> >> >> > for
>> >> >> > chained boot?
>> >> >> >
>> >> >> > I am using instructions to boot Linux for Tegra from sdcard/USB in
>> >> >> > developer
>> >> >> > mode.  I can boot L4T fine with kernel v3.10.
>> >> >> >
>> >> >> > What mainline branch should I try?
>> >> >>
>> >> >> There's only one mainline, here:
>> >> >> http://git.denx.de/?p=u-boot.git;a=summary
>> >> >>
>> >> >> There are various custodian branches but I don't believe the tegra
>> >> >> one
>> >> >> has anything different from mainline at present.
>> >> >>
>> >> >> - Simon
>> >> >>
>> >> > I will give mainline a try with:
>> >> >
>> >> > CONFIG_SYS_TEXT_BASE 0x8010E000
>> >> > and
>> >> >
>> >> > CONFIG_SPL_TEXT_BASE 0x80108000
>> >> >
>> >> >
>> >> > I know I will also need:
>> >> >
>> >> >
>> >> > CONFIG_DISPLAY_PORT=y
>> >>
>> >> Do you mean CONFIG_DISPLAY? If so, it is already defined.
>> >>
>> >> > CONFIG_VIDEO_TEGRA124=y
>> >>
>> >> That is defined in mainline
>> >>
>> >> >
>> >> >
>> >> > for the console to display command prompt.
>> >> >
>> >> >
>> >> > The FIT config I am using is from
>> >> >
>> >> > here:https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
>> >> >
>> >> >
>> >> > Do I need to adjust:
>> >> >
>> >> >
>> >> >             load = <0>;
>> >> >             entry = <0>;
>> >> >
>> >> >
>> >> > /dts-v1/;
>> >> >
>> >> > / {
>> >> >     description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO
>> >> > THE
>> >> > IMAGE STARTS AT THE RIGHT OFFSET";
>> >>
>> >> Perhaps you need to adjust this? How was the length of it calcualted?
>> >
>> >
>> > I am really not sure how the padding was calculated.  I just assumed
>> > this
>> > kernel-big.its FIT config was correct for nyan_big.  I will try using my
>> > working linux kernel fit config.
>> >>
>> >>
>> >> >     #address-cells = <1>;
>> >> >     images {
>> >> >         kernel at 1{
>> >> >             description = "kernel";
>> >> >             data = /incbin/("u-boot-dtb.bin");
>> >> >             type = "kernel_noload";
>> >> >             arch = "arm";
>> >> >             os = "linux";
>> >> >             compression = "none";
>> >> >             load = <0>;
>> >> >             entry = <0>;
>> >> >         };
>> >> >         fdt at 1{
>> >> >             description = "tegra124-nyan-big.dtb";
>> >> >             data = /incbin/("dts/dt.dtb");
>> >> >             type = "flat_dt";
>> >> >             arch = "arm";
>> >> >             compression = "none";
>> >> >             hash at 1{
>> >> >                 algo = "sha1";
>> >> >             };
>> >> >         };
>> >> >     };
>> >> >     configurations {
>> >> >         default = "conf at 1";
>> >> >         conf at 1{
>> >> >             kernel = "kernel at 1";
>> >> >             fdt = "fdt at 1";
>> >> >         };
>> >> >     };
>> >> > };
>> >> >
>> >> >
>> >> > please let me know if I should also adjust the SPL CONFIG even though
>> >> > I
>> >> > am chainbooting uboot:
>> >> >
>> >> >
>> >> >
>> >> > https://www.chromium.org/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing-nv-U-Boot-chained-U-Boot-method-
>> >>
>> >> This is exynos, where we booted directly into U-Boot. Actually I'm
>> >> wondering we should boot directly into U-Boot (instead of SPL) on nyan
>> >> also. Perhaps someone at collabora would know? Did you search the
>> >> mailing list?
>> >>
>> >> Regards,
>> >> Simon
>> >
>> >
>> > I have not searched the mailing list.  What should I search for?
>> > Booting
>> > nyan to u-boot directly bypassing SPL?
>>
>> Here are two subjects to search for:
>>
>> Veyron-speedy u-boot
>> [PATCH 0/20] tegra: Expand Nyan-big support
>>
>> Regards,
>> Simon
>
>
> Very odd if I do not use "#address-cells = <1>;" the display flashes and
> reboots into recovery but if I do use #address-cells = <1>; in my FIT config
> I get a blank screen
> so something is working when not using the padding.

If you figure out where u-boot-dtb.bin needs to start by looking at
depthcharge or where the kernel starts, then you can figure out how
long the padding needs to be at the start of the FIT. Rather than
guessing...!

- Simon

>
> /dts-v1/;
>
> / {
>     description = "Chrome OS nyan u-boot chain boot method";
>     #address-cells = <1>;
>     images {
>         kernel at 1{
>
>>
>> >>
>> >>
>> >> >>
>> >> >> >
>>
>> >> >> > On May 1, 2017 12:11 PM, "Matthew Gorski" <matt.gorski@gmail.com>
>> >> >> > wrote:
>> >> >> >
>> >> >> > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org> wrote:
>> >> >> >
>> >> >> > Hi Matthew,
>> >> >> >
>> >> >> > On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com>
>> >> >> > wrote:
>> >> >> >> Thanks for the reply Simon.
>> >> >> >>
>> >> >> >> I have been trying to find the System.map for depthcharge to see
>> >> >> >> the
>> >> >> >> kernel
>> >> >> >> load address but I am unable to find anything.  I have tried
>> >> >> >> multiple
>> >> >> >> CONFIG_SYS_TEXT_BASE settings with no luck.
>> >> >> >
>> >> >> > How did you choose what to use? Also note that Tegra uses SPL to
>> >> >> > start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
>> >> >> >
>> >> >> >>
>> >> >> >> I am creating my sdcard with a standard linux (Linux for Tegra)
>> >> >> >> rootfs:
>> >> >> >
>> >> >> > Did these instructions come from a web site somewhere?
>> >> >> >
>> >> >> >>
>> >> >> >> Partition an SD card
>> >> >> >>
>> >> >> >> sudo cgpt create <MMC BLOCK DEVICE>
>> >> >> >> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK
>> >> >> >> DEVICE>
>> >> >> >> # 16
>> >> >> >> MB
>> >> >> >> kernel image partition
>> >> >> >> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors>
>> >> >> >> -t
>> >> >> >> rootfs
>> >> >> >> <MMC BLOCK DEVICE>
>> >> >> >>
>> >> >> >> cgpt doesn't seem to create a protective MBR. If one is not
>> >> >> >> already
>> >> >> >> in
>> >> >> >> place, it can be created with:
>> >> >> >>
>> >> >> >> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
>> >> >> >>
>> >> >> >> Copy data to the SD card
>> >> >> >>
>> >> >> >> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
>> >> >> >> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>> >> >> >> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>> >> >> >>
>> >> >> >
>> >> >> > How are you actually making it boot? Is this in dev mode with USB
>> >> >> > boot
>> >> >> > enabled and pressing Ctrl-U?
>> >> >> >
>> >> >> > Also, as this is a mailing list, please avoid top-posting.
>> >> >> >
>> >> >> > - Simon
>> >> >> >
>> >> >> > I am using chained boot to test uboot as a FIT image so I I don't
>> >> >> > have to
>> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be adjusted
>> >> >> > for
>> >> >> > chained boot?
>> >> >> >
>> >> >> > I am using instructions to boot Linux for Tegra from sdcard/USB in
>> >> >> > developer
>> >> >> > mode.  I can boot L4T fine with kernel v3.10.
>> >> >> >
>> >> >> > What mainline branch should I try?
>> >> >> >
>> >> >> >
>> >> >> >>
>> >> >> >> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org>
>> >> >> >> wrote:
>> >> >> >>>
>> >> >> >>> Hi Matthew,
>> >> >> >>>
>> >> >> >>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com>
>> >> >> >>> wrote:
>> >> >> >>> > I am porting u-boot to nyan_big and need some input.  I have
>> >> >> >>> > been
>> >> >> >>> > searching
>> >> >> >>> > high and low and found this thread here: [U-Boot] [PATCH 0/20]
>> >> >> >>> > tegra:
>> >> >> >>> > Expand
>> >> >> >>> > Nyan-big support
>> >> >> >>> >
>> >> >> >>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
>> >> >> >>> >
>> >> >> >>> > I have tried to build u-boot with the branch here:
>> >> >> >>> >
>> >> >> >>> >
>> >> >> >>> >
>> >> >> >>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
>> >> >> >>> >
>> >> >> >>> > and also the official chromium next branch
>> >> >> >>>
>> >> >> >>> Have you tried mainline U-Boot? It already supports nyan-big.
>> >> >> >>> I'm
>> >> >> >>> not
>> >> >> >>> sure about the situation with the downstream trees.
>> >> >> >>>
>> >> >> >>> >
>> >> >> >>> > I followed building instructions here:
>> >> >> >>> >
>> >> >> >>> >
>> >> >> >>> >
>> >> >> >>> >
>> >> >> >>> > https://www.chromium.org/chromium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung-arm-chromebook
>> >> >> >>> >
>> >> >> >>> > I build with these commands:
>> >> >> >>> >
>> >> >> >>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its
>> >> >> >>> > kernel-u-boot
>> >> >> >>> >
>> >> >> >>> > (with and without the load address setting)
>> >> >> >>> >
>> >> >> >>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
>> >> >> >>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
>> >> >> >>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version 1
>> >> >> >>> > --config
>> >> >> >>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
>> >> >> >>> >
>> >> >> >>> > I have had numerous failed attempts to boot uboot from sdcard
>> >> >> >>> > mmcblk1p1
>> >> >> >>> >
>> >> >> >>> > Any help is appreciated I have only gotten a blank screen
>> >> >> >>> > after
>> >> >> >>> > weeks
>> >> >> >>> > of
>> >> >> >>> > flashing.  I can boot custom v3.10 kernels so I assume I am
>> >> >> >>> > using
>> >> >> >>> > the
>> >> >> >>> > correct building procedure.  Thanks in advance for help from
>> >> >> >>> > the
>> >> >> >>> > u-boot
>> >> >> >>> > community.
>> >> >> >>>
>> >> >> >>> It is possible that it needs a particular address due to
>> >> >> >>> limitations
>> >> >> >>> in the FIT support on Nyan. I'm not sure what it is but might be
>> >> >> >>> able
>> >> >> >>> to take a look at some point.
>> >> >> >>>
>> >> >> >>> How are you building your SD card? Are you following some
>> >> >> >>> instructions
>> >> >> >>> from somewhere?
>> >> >> >>>
>> >> >> >>> Regards,
>> >> >> >>> Simon
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >
>> >> >
>> >
>> >
>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

On Mon, May 1, 2017 at 7:34 PM, Simon Glass <sjg@chromium.org> wrote:

> Hi Matthew,
>
> On 1 May 2017 at 17:27, Matthew Gorski <matt.gorski@gmail.com> wrote:
> >
> >
> > On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.org> wrote:
> >>
> >> Hi Matthew,
> >>
> >> On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail.com> wrote:
> >> >
> >> >
> >> > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromium.org> wrote:
> >> >>
> >> >> Hi Matthew,
> >> >>
> >> >> On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@gmail.com>
> wrote:
> >> >> >
> >> >> >
> >> >> >
> >> >> > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@chromium.org>
> wrote:
> >> >> >>
> >> >> >> Hi Matthew,
> >> >> >>
> >> >> >> On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com>
> >> >> >> wrote:
> >> >> >> > Let me repost this to the bottom.  New to the mailing list ;)
> >> >> >> >
> >> >> >> > I am using chained boot to test uboot as a FIT image so I I
> don't
> >> >> >> > have to
> >> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be
> adjusted
> >> >> >> > for
> >> >> >> > chained boot?
> >> >> >> >
> >> >> >> > I am using instructions to boot Linux for Tegra from sdcard/USB
> in
> >> >> >> > developer
> >> >> >> > mode.  I can boot L4T fine with kernel v3.10.
> >> >> >> >
> >> >> >> > What mainline branch should I try?
> >> >> >>
> >> >> >> There's only one mainline, here:
> >> >> >> http://git.denx.de/?p=u-boot.git;a=summary
> >> >> >>
> >> >> >> There are various custodian branches but I don't believe the tegra
> >> >> >> one
> >> >> >> has anything different from mainline at present.
> >> >> >>
> >> >> >> - Simon
> >> >> >>
> >> >> > I will give mainline a try with:
> >> >> >
> >> >> > CONFIG_SYS_TEXT_BASE 0x8010E000
> >> >> > and
> >> >> >
> >> >> > CONFIG_SPL_TEXT_BASE 0x80108000
> >> >> >
> >> >> >
> >> >> > I know I will also need:
> >> >> >
> >> >> >
> >> >> > CONFIG_DISPLAY_PORT=y
> >> >>
> >> >> Do you mean CONFIG_DISPLAY? If so, it is already defined.
> >> >>
> >> >> > CONFIG_VIDEO_TEGRA124=y
> >> >>
> >> >> That is defined in mainline
> >> >>
> >> >> >
> >> >> >
> >> >> > for the console to display command prompt.
> >> >> >
> >> >> >
> >> >> > The FIT config I am using is from
> >> >> >
> >> >> > here:https://git.collabora.com/cgit/user/tomeu/u-boot.
> git/commit/?h=nyan-big
> >> >> >
> >> >> >
> >> >> > Do I need to adjust:
> >> >> >
> >> >> >
> >> >> >             load = <0>;
> >> >> >             entry = <0>;
> >> >> >
> >> >> >
> >> >> > /dts-v1/;
> >> >> >
> >> >> > / {
> >> >> >     description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO
> >> >> > THE
> >> >> > IMAGE STARTS AT THE RIGHT OFFSET";
> >> >>
> >> >> Perhaps you need to adjust this? How was the length of it calcualted?
> >> >
> >> >
> >> > I am really not sure how the padding was calculated.  I just assumed
> >> > this
> >> > kernel-big.its FIT config was correct for nyan_big.  I will try using
> my
> >> > working linux kernel fit config.
> >> >>
> >> >>
> >> >> >     #address-cells = <1>;
> >> >> >     images {
> >> >> >         kernel at 1{
> >> >> >             description = "kernel";
> >> >> >             data = /incbin/("u-boot-dtb.bin");
> >> >> >             type = "kernel_noload";
> >> >> >             arch = "arm";
> >> >> >             os = "linux";
> >> >> >             compression = "none";
> >> >> >             load = <0>;
> >> >> >             entry = <0>;
> >> >> >         };
> >> >> >         fdt at 1{
> >> >> >             description = "tegra124-nyan-big.dtb";
> >> >> >             data = /incbin/("dts/dt.dtb");
> >> >> >             type = "flat_dt";
> >> >> >             arch = "arm";
> >> >> >             compression = "none";
> >> >> >             hash at 1{
> >> >> >                 algo = "sha1";
> >> >> >             };
> >> >> >         };
> >> >> >     };
> >> >> >     configurations {
> >> >> >         default = "conf at 1";
> >> >> >         conf at 1{
> >> >> >             kernel = "kernel at 1";
> >> >> >             fdt = "fdt at 1";
> >> >> >         };
> >> >> >     };
> >> >> > };
> >> >> >
> >> >> >
> >> >> > please let me know if I should also adjust the SPL CONFIG even
> though
> >> >> > I
> >> >> > am chainbooting uboot:
> >> >> >
> >> >> >
> >> >> >
> >> >> > https://www.chromium.org/chromium-os/firmware-porting-
> guide/using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-
> Installing-nv-U-Boot-chained-U-Boot-method-
> >> >>
> >> >> This is exynos, where we booted directly into U-Boot. Actually I'm
> >> >> wondering we should boot directly into U-Boot (instead of SPL) on
> nyan
> >> >> also. Perhaps someone at collabora would know? Did you search the
> >> >> mailing list?
> >> >>
> >> >> Regards,
> >> >> Simon
> >> >
> >> >
> >> > I have not searched the mailing list.  What should I search for?
> >> > Booting
> >> > nyan to u-boot directly bypassing SPL?
> >>
> >> Here are two subjects to search for:
> >>
> >> Veyron-speedy u-boot
> >> [PATCH 0/20] tegra: Expand Nyan-big support
> >>
> >> Regards,
> >> Simon
> >
> >
> > Very odd if I do not use "#address-cells = <1>;" the display flashes and
> > reboots into recovery but if I do use #address-cells = <1>; in my FIT
> config
> > I get a blank screen
> > so something is working when not using the padding.
>
> If you figure out where u-boot-dtb.bin needs to start by looking at
> depthcharge or where the kernel starts, then you can figure out how
> long the padding needs to be at the start of the FIT. Rather than
> guessing...!
>
> - Simon
>
>  Okay so depthcharge starts at 0x81000000 from here:
https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/master/board/nyan_big/defconfig#11

In my System.map for u-boot after building says the start is:
81000100 T __image_copy_start
81000100 T _start

Hence the define CONFIG_SYS_TEXT_BASE 0x81000100

So you say use 0x81000000 as the CONFIG_SYS_TEXT_BASE and not 0x81000100
correct?

> >
> > /dts-v1/;
> >
> > / {
> >     description = "Chrome OS nyan u-boot chain boot method";
> >     #address-cells = <1>;
> >     images {
> >         kernel at 1{
> >
> >>
> >> >>
> >> >>
> >> >> >>
> >> >> >> >
> >>
> >> >> >> > On May 1, 2017 12:11 PM, "Matthew Gorski" <
> matt.gorski at gmail.com>
> >> >> >> > wrote:
> >> >> >> >
> >> >> >> > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org>
> wrote:
> >> >> >> >
> >> >> >> > Hi Matthew,
> >> >> >> >
> >> >> >> > On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com>
> >> >> >> > wrote:
> >> >> >> >> Thanks for the reply Simon.
> >> >> >> >>
> >> >> >> >> I have been trying to find the System.map for depthcharge to
> see
> >> >> >> >> the
> >> >> >> >> kernel
> >> >> >> >> load address but I am unable to find anything.  I have tried
> >> >> >> >> multiple
> >> >> >> >> CONFIG_SYS_TEXT_BASE settings with no luck.
> >> >> >> >
> >> >> >> > How did you choose what to use? Also note that Tegra uses SPL to
> >> >> >> > start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
> >> >> >> >
> >> >> >> >>
> >> >> >> >> I am creating my sdcard with a standard linux (Linux for Tegra)
> >> >> >> >> rootfs:
> >> >> >> >
> >> >> >> > Did these instructions come from a web site somewhere?
> >> >> >> >
> >> >> >> >>
> >> >> >> >> Partition an SD card
> >> >> >> >>
> >> >> >> >> sudo cgpt create <MMC BLOCK DEVICE>
> >> >> >> >> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK
> >> >> >> >> DEVICE>
> >> >> >> >> # 16
> >> >> >> >> MB
> >> >> >> >> kernel image partition
> >> >> >> >> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B sectors>
> >> >> >> >> -t
> >> >> >> >> rootfs
> >> >> >> >> <MMC BLOCK DEVICE>
> >> >> >> >>
> >> >> >> >> cgpt doesn't seem to create a protective MBR. If one is not
> >> >> >> >> already
> >> >> >> >> in
> >> >> >> >> place, it can be created with:
> >> >> >> >>
> >> >> >> >> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
> >> >> >> >>
> >> >> >> >> Copy data to the SD card
> >> >> >> >>
> >> >> >> >> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
> >> >> >> >> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
> >> >> >> >> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
> >> >> >> >>
> >> >> >> >
> >> >> >> > How are you actually making it boot? Is this in dev mode with
> USB
> >> >> >> > boot
> >> >> >> > enabled and pressing Ctrl-U?
> >> >> >> >
> >> >> >> > Also, as this is a mailing list, please avoid top-posting.
> >> >> >> >
> >> >> >> > - Simon
> >> >> >> >
> >> >> >> > I am using chained boot to test uboot as a FIT image so I I
> don't
> >> >> >> > have to
> >> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be
> adjusted
> >> >> >> > for
> >> >> >> > chained boot?
> >> >> >> >
> >> >> >> > I am using instructions to boot Linux for Tegra from sdcard/USB
> in
> >> >> >> > developer
> >> >> >> > mode.  I can boot L4T fine with kernel v3.10.
> >> >> >> >
> >> >> >> > What mainline branch should I try?
> >> >> >> >
> >> >> >> >
> >> >> >> >>
> >> >> >> >> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <sjg@chromium.org
> >
> >> >> >> >> wrote:
> >> >> >> >>>
> >> >> >> >>> Hi Matthew,
> >> >> >> >>>
> >> >> >> >>> On 1 May 2017 at 08:43, Matthew Gorski <matt.gorski@gmail.com
> >
> >> >> >> >>> wrote:
> >> >> >> >>> > I am porting u-boot to nyan_big and need some input.  I have
> >> >> >> >>> > been
> >> >> >> >>> > searching
> >> >> >> >>> > high and low and found this thread here: [U-Boot] [PATCH
> 0/20]
> >> >> >> >>> > tegra:
> >> >> >> >>> > Expand
> >> >> >> >>> > Nyan-big support
> >> >> >> >>> >
> >> >> >> >>> >  https://lists.denx.de/pipermail/u-boot/2015-March/
> 209530.html
> >> >> >> >>> >
> >> >> >> >>> > I have tried to build u-boot with the branch here:
> >> >> >> >>> >
> >> >> >> >>> >
> >> >> >> >>> >
> >> >> >> >>> > https://git.collabora.com/cgit/user/tomeu/u-boot.git/
> commit/?h=nyan-big
> >> >> >> >>> >
> >> >> >> >>> > and also the official chromium next branch
> >> >> >> >>>
> >> >> >> >>> Have you tried mainline U-Boot? It already supports nyan-big.
> >> >> >> >>> I'm
> >> >> >> >>> not
> >> >> >> >>> sure about the situation with the downstream trees.
> >> >> >> >>>
> >> >> >> >>> >
> >> >> >> >>> > I followed building instructions here:
> >> >> >> >>> >
> >> >> >> >>> >
> >> >> >> >>> >
> >> >> >> >>> >
> >> >> >> >>> > https://www.chromium.org/chromium-os/firmware-porting-
> guide/using-nv-u-boot-on-the-samsung-arm-chromebook
> >> >> >> >>> >
> >> >> >> >>> > I build with these commands:
> >> >> >> >>> >
> >> >> >> >>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its
> >> >> >> >>> > kernel-u-boot
> >> >> >> >>> >
> >> >> >> >>> > (with and without the load address setting)
> >> >> >> >>> >
> >> >> >> >>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
> >> >> >> >>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
> >> >> >> >>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk --version
> 1
> >> >> >> >>> > --config
> >> >> >> >>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
> >> >> >> >>> >
> >> >> >> >>> > I have had numerous failed attempts to boot uboot from
> sdcard
> >> >> >> >>> > mmcblk1p1
> >> >> >> >>> >
> >> >> >> >>> > Any help is appreciated I have only gotten a blank screen
> >> >> >> >>> > after
> >> >> >> >>> > weeks
> >> >> >> >>> > of
> >> >> >> >>> > flashing.  I can boot custom v3.10 kernels so I assume I am
> >> >> >> >>> > using
> >> >> >> >>> > the
> >> >> >> >>> > correct building procedure.  Thanks in advance for help from
> >> >> >> >>> > the
> >> >> >> >>> > u-boot
> >> >> >> >>> > community.
> >> >> >> >>>
> >> >> >> >>> It is possible that it needs a particular address due to
> >> >> >> >>> limitations
> >> >> >> >>> in the FIT support on Nyan. I'm not sure what it is but might
> be
> >> >> >> >>> able
> >> >> >> >>> to take a look at some point.
> >> >> >> >>>
> >> >> >> >>> How are you building your SD card? Are you following some
> >> >> >> >>> instructions
> >> >> >> >>> from somewhere?
> >> >> >> >>>
> >> >> >> >>> Regards,
> >> >> >> >>> Simon
> >> >> >> >>
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >
> >> >> >
> >> >
> >> >
> >
> >
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

Seems if you change the FIT description from anything but

"description = "Chrome OS kernel image with one or more FDT blobs";"

the kernel wont load. So this issue has to be in the kernel-big.its
<https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel-big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923>

https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel-big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923

We may just need a proper working .its for nyan

On Mon, May 1, 2017 at 7:45 PM, Matthew Gorski <matt.gorski@gmail.com>
wrote:

>
>
> On Mon, May 1, 2017 at 7:34 PM, Simon Glass <sjg@chromium.org> wrote:
>
>> Hi Matthew,
>>
>> On 1 May 2017 at 17:27, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> >
>> >
>> > On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.org> wrote:
>> >>
>> >> Hi Matthew,
>> >>
>> >> On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> >> >
>> >> >
>> >> > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromium.org>
>> wrote:
>> >> >>
>> >> >> Hi Matthew,
>> >> >>
>> >> >> On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@gmail.com>
>> wrote:
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@chromium.org>
>> wrote:
>> >> >> >>
>> >> >> >> Hi Matthew,
>> >> >> >>
>> >> >> >> On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com>
>> >> >> >> wrote:
>> >> >> >> > Let me repost this to the bottom.  New to the mailing list ;)
>> >> >> >> >
>> >> >> >> > I am using chained boot to test uboot as a FIT image so I I
>> don't
>> >> >> >> > have to
>> >> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be
>> adjusted
>> >> >> >> > for
>> >> >> >> > chained boot?
>> >> >> >> >
>> >> >> >> > I am using instructions to boot Linux for Tegra from
>> sdcard/USB in
>> >> >> >> > developer
>> >> >> >> > mode.  I can boot L4T fine with kernel v3.10.
>> >> >> >> >
>> >> >> >> > What mainline branch should I try?
>> >> >> >>
>> >> >> >> There's only one mainline, here:
>> >> >> >> http://git.denx.de/?p=u-boot.git;a=summary
>> >> >> >>
>> >> >> >> There are various custodian branches but I don't believe the
>> tegra
>> >> >> >> one
>> >> >> >> has anything different from mainline at present.
>> >> >> >>
>> >> >> >> - Simon
>> >> >> >>
>> >> >> > I will give mainline a try with:
>> >> >> >
>> >> >> > CONFIG_SYS_TEXT_BASE 0x8010E000
>> >> >> > and
>> >> >> >
>> >> >> > CONFIG_SPL_TEXT_BASE 0x80108000
>> >> >> >
>> >> >> >
>> >> >> > I know I will also need:
>> >> >> >
>> >> >> >
>> >> >> > CONFIG_DISPLAY_PORT=y
>> >> >>
>> >> >> Do you mean CONFIG_DISPLAY? If so, it is already defined.
>> >> >>
>> >> >> > CONFIG_VIDEO_TEGRA124=y
>> >> >>
>> >> >> That is defined in mainline
>> >> >>
>> >> >> >
>> >> >> >
>> >> >> > for the console to display command prompt.
>> >> >> >
>> >> >> >
>> >> >> > The FIT config I am using is from
>> >> >> >
>> >> >> > here:https://git.collabora.com/cgit/user/tomeu/u-boot.git/
>> commit/?h=nyan-big
>> >> >> >
>> >> >> >
>> >> >> > Do I need to adjust:
>> >> >> >
>> >> >> >
>> >> >> >             load = <0>;
>> >> >> >             entry = <0>;
>> >> >> >
>> >> >> >
>> >> >> > /dts-v1/;
>> >> >> >
>> >> >> > / {
>> >> >> >     description = "U-Boot + FDT --------- THIS PADDING IS NEEDED
>> SO
>> >> >> > THE
>> >> >> > IMAGE STARTS AT THE RIGHT OFFSET";
>> >> >>
>> >> >> Perhaps you need to adjust this? How was the length of it
>> calcualted?
>> >> >
>> >> >
>> >> > I am really not sure how the padding was calculated.  I just assumed
>> >> > this
>> >> > kernel-big.its FIT config was correct for nyan_big.  I will try
>> using my
>> >> > working linux kernel fit config.
>> >> >>
>> >> >>
>> >> >> >     #address-cells = <1>;
>> >> >> >     images {
>> >> >> >         kernel at 1{
>> >> >> >             description = "kernel";
>> >> >> >             data = /incbin/("u-boot-dtb.bin");
>> >> >> >             type = "kernel_noload";
>> >> >> >             arch = "arm";
>> >> >> >             os = "linux";
>> >> >> >             compression = "none";
>> >> >> >             load = <0>;
>> >> >> >             entry = <0>;
>> >> >> >         };
>> >> >> >         fdt at 1{
>> >> >> >             description = "tegra124-nyan-big.dtb";
>> >> >> >             data = /incbin/("dts/dt.dtb");
>> >> >> >             type = "flat_dt";
>> >> >> >             arch = "arm";
>> >> >> >             compression = "none";
>> >> >> >             hash at 1{
>> >> >> >                 algo = "sha1";
>> >> >> >             };
>> >> >> >         };
>> >> >> >     };
>> >> >> >     configurations {
>> >> >> >         default = "conf at 1";
>> >> >> >         conf at 1{
>> >> >> >             kernel = "kernel at 1";
>> >> >> >             fdt = "fdt at 1";
>> >> >> >         };
>> >> >> >     };
>> >> >> > };
>> >> >> >
>> >> >> >
>> >> >> > please let me know if I should also adjust the SPL CONFIG even
>> though
>> >> >> > I
>> >> >> > am chainbooting uboot:
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > https://www.chromium.org/chromium-os/firmware-porting-guide/
>> using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing
>> -nv-U-Boot-chained-U-Boot-method-
>> >> >>
>> >> >> This is exynos, where we booted directly into U-Boot. Actually I'm
>> >> >> wondering we should boot directly into U-Boot (instead of SPL) on
>> nyan
>> >> >> also. Perhaps someone at collabora would know? Did you search the
>> >> >> mailing list?
>> >> >>
>> >> >> Regards,
>> >> >> Simon
>> >> >
>> >> >
>> >> > I have not searched the mailing list.  What should I search for?
>> >> > Booting
>> >> > nyan to u-boot directly bypassing SPL?
>> >>
>> >> Here are two subjects to search for:
>> >>
>> >> Veyron-speedy u-boot
>> >> [PATCH 0/20] tegra: Expand Nyan-big support
>> >>
>> >> Regards,
>> >> Simon
>> >
>> >
>> > Very odd if I do not use "#address-cells = <1>;" the display flashes and
>> > reboots into recovery but if I do use #address-cells = <1>; in my FIT
>> config
>> > I get a blank screen
>> > so something is working when not using the padding.
>>
>> If you figure out where u-boot-dtb.bin needs to start by looking at
>> depthcharge or where the kernel starts, then you can figure out how
>> long the padding needs to be at the start of the FIT. Rather than
>> guessing...!
>>
>> - Simon
>>
>>  Okay so depthcharge starts at 0x81000000 from here:
> https://chromium.googlesource.com/chromiumos/platform/
> depthcharge/+/master/board/nyan_big/defconfig#11
>
> In my System.map for u-boot after building says the start is:
> 81000100 T __image_copy_start
> 81000100 T _start
>
> Hence the define CONFIG_SYS_TEXT_BASE 0x81000100
>
> So you say use 0x81000000 as the CONFIG_SYS_TEXT_BASE and not 0x81000100
> correct?
>
>> >
>> > /dts-v1/;
>> >
>> > / {
>> >     description = "Chrome OS nyan u-boot chain boot method";
>> >     #address-cells = <1>;
>> >     images {
>> >         kernel at 1{
>> >
>> >>
>> >> >>
>> >> >>
>> >> >> >>
>> >> >> >> >
>> >>
>> >> >> >> > On May 1, 2017 12:11 PM, "Matthew Gorski" <
>> matt.gorski at gmail.com>
>> >> >> >> > wrote:
>> >> >> >> >
>> >> >> >> > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org>
>> wrote:
>> >> >> >> >
>> >> >> >> > Hi Matthew,
>> >> >> >> >
>> >> >> >> > On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com>
>> >> >> >> > wrote:
>> >> >> >> >> Thanks for the reply Simon.
>> >> >> >> >>
>> >> >> >> >> I have been trying to find the System.map for depthcharge to
>> see
>> >> >> >> >> the
>> >> >> >> >> kernel
>> >> >> >> >> load address but I am unable to find anything.  I have tried
>> >> >> >> >> multiple
>> >> >> >> >> CONFIG_SYS_TEXT_BASE settings with no luck.
>> >> >> >> >
>> >> >> >> > How did you choose what to use? Also note that Tegra uses SPL
>> to
>> >> >> >> > start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
>> >> >> >> >
>> >> >> >> >>
>> >> >> >> >> I am creating my sdcard with a standard linux (Linux for
>> Tegra)
>> >> >> >> >> rootfs:
>> >> >> >> >
>> >> >> >> > Did these instructions come from a web site somewhere?
>> >> >> >> >
>> >> >> >> >>
>> >> >> >> >> Partition an SD card
>> >> >> >> >>
>> >> >> >> >> sudo cgpt create <MMC BLOCK DEVICE>
>> >> >> >> >> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK
>> >> >> >> >> DEVICE>
>> >> >> >> >> # 16
>> >> >> >> >> MB
>> >> >> >> >> kernel image partition
>> >> >> >> >> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B
>> sectors>
>> >> >> >> >> -t
>> >> >> >> >> rootfs
>> >> >> >> >> <MMC BLOCK DEVICE>
>> >> >> >> >>
>> >> >> >> >> cgpt doesn't seem to create a protective MBR. If one is not
>> >> >> >> >> already
>> >> >> >> >> in
>> >> >> >> >> place, it can be created with:
>> >> >> >> >>
>> >> >> >> >> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
>> >> >> >> >>
>> >> >> >> >> Copy data to the SD card
>> >> >> >> >>
>> >> >> >> >> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
>> >> >> >> >> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>> >> >> >> >> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> > How are you actually making it boot? Is this in dev mode with
>> USB
>> >> >> >> > boot
>> >> >> >> > enabled and pressing Ctrl-U?
>> >> >> >> >
>> >> >> >> > Also, as this is a mailing list, please avoid top-posting.
>> >> >> >> >
>> >> >> >> > - Simon
>> >> >> >> >
>> >> >> >> > I am using chained boot to test uboot as a FIT image so I I
>> don't
>> >> >> >> > have to
>> >> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be
>> adjusted
>> >> >> >> > for
>> >> >> >> > chained boot?
>> >> >> >> >
>> >> >> >> > I am using instructions to boot Linux for Tegra from
>> sdcard/USB in
>> >> >> >> > developer
>> >> >> >> > mode.  I can boot L4T fine with kernel v3.10.
>> >> >> >> >
>> >> >> >> > What mainline branch should I try?
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >>
>> >> >> >> >> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <
>> sjg at chromium.org>
>> >> >> >> >> wrote:
>> >> >> >> >>>
>> >> >> >> >>> Hi Matthew,
>> >> >> >> >>>
>> >> >> >> >>> On 1 May 2017 at 08:43, Matthew Gorski <
>> matt.gorski at gmail.com>
>> >> >> >> >>> wrote:
>> >> >> >> >>> > I am porting u-boot to nyan_big and need some input.  I
>> have
>> >> >> >> >>> > been
>> >> >> >> >>> > searching
>> >> >> >> >>> > high and low and found this thread here: [U-Boot] [PATCH
>> 0/20]
>> >> >> >> >>> > tegra:
>> >> >> >> >>> > Expand
>> >> >> >> >>> > Nyan-big support
>> >> >> >> >>> >
>> >> >> >> >>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.
>> html
>> >> >> >> >>> >
>> >> >> >> >>> > I have tried to build u-boot with the branch here:
>> >> >> >> >>> >
>> >> >> >> >>> >
>> >> >> >> >>> >
>> >> >> >> >>> > https://git.collabora.com/cgit
>> /user/tomeu/u-boot.git/commit/?h=nyan-big
>> >> >> >> >>> >
>> >> >> >> >>> > and also the official chromium next branch
>> >> >> >> >>>
>> >> >> >> >>> Have you tried mainline U-Boot? It already supports nyan-big.
>> >> >> >> >>> I'm
>> >> >> >> >>> not
>> >> >> >> >>> sure about the situation with the downstream trees.
>> >> >> >> >>>
>> >> >> >> >>> >
>> >> >> >> >>> > I followed building instructions here:
>> >> >> >> >>> >
>> >> >> >> >>> >
>> >> >> >> >>> >
>> >> >> >> >>> >
>> >> >> >> >>> > https://www.chromium.org/chrom
>> ium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung
>> -arm-chromebook
>> >> >> >> >>> >
>> >> >> >> >>> > I build with these commands:
>> >> >> >> >>> >
>> >> >> >> >>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its
>> >> >> >> >>> > kernel-u-boot
>> >> >> >> >>> >
>> >> >> >> >>> > (with and without the load address setting)
>> >> >> >> >>> >
>> >> >> >> >>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
>> >> >> >> >>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
>> >> >> >> >>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk
>> --version 1
>> >> >> >> >>> > --config
>> >> >> >> >>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
>> >> >> >> >>> >
>> >> >> >> >>> > I have had numerous failed attempts to boot uboot from
>> sdcard
>> >> >> >> >>> > mmcblk1p1
>> >> >> >> >>> >
>> >> >> >> >>> > Any help is appreciated I have only gotten a blank screen
>> >> >> >> >>> > after
>> >> >> >> >>> > weeks
>> >> >> >> >>> > of
>> >> >> >> >>> > flashing.  I can boot custom v3.10 kernels so I assume I am
>> >> >> >> >>> > using
>> >> >> >> >>> > the
>> >> >> >> >>> > correct building procedure.  Thanks in advance for help
>> from
>> >> >> >> >>> > the
>> >> >> >> >>> > u-boot
>> >> >> >> >>> > community.
>> >> >> >> >>>
>> >> >> >> >>> It is possible that it needs a particular address due to
>> >> >> >> >>> limitations
>> >> >> >> >>> in the FIT support on Nyan. I'm not sure what it is but
>> might be
>> >> >> >> >>> able
>> >> >> >> >>> to take a look at some point.
>> >> >> >> >>>
>> >> >> >> >>> How are you building your SD card? Are you following some
>> >> >> >> >>> instructions
>> >> >> >> >>> from somewhere?
>> >> >> >> >>>
>> >> >> >> >>> Regards,
>> >> >> >> >>> Simon
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >
>> >> >> >
>> >> >
>> >> >
>> >
>> >
>>
>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Tomeu Vizoso]

On 2 May 2017 at 03:19, Matthew Gorski <matt.gorski@gmail.com> wrote:
> Seems if you change the FIT description from anything but
>
> "description = "Chrome OS kernel image with one or more FDT blobs";"
>
> the kernel wont load. So this issue has to be in the kernel-big.its
> <https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel-big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923>
>
> https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel-big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923
>
> We may just need a proper working .its for nyan

Hi Matthew,

it has been quite a while, but I remember that if we only tried
chainloading U-Boot was because the goal was to integrate these
machines in our LAVA lab, which to date doesn't support Depthcharge
(though I hope this will change once I get back some time).

I cannot remember how the correct position of the kernel within the
FIT image was calculated, but it definitely involved looking at the
depthcharge sources.

But I do think to remember that it was only an issue once U-Boot tried
to relocate itself.

I don't see any reason why my old branch wouldn't work today on your
machine, other than maybe your hw is a different revision with a
memory chip that wasn't supported back then? I also don't see why
mainline wouldn't work, provided you have that hack in the ITS.

I'm adding Sjoerd to CC in case he remembers.

Good luck,

Tomeu

> On Mon, May 1, 2017 at 7:45 PM, Matthew Gorski <matt.gorski@gmail.com>
> wrote:
>
>>
>>
>> On Mon, May 1, 2017 at 7:34 PM, Simon Glass <sjg@chromium.org> wrote:
>>
>>> Hi Matthew,
>>>
>>> On 1 May 2017 at 17:27, Matthew Gorski <matt.gorski@gmail.com> wrote:
>>> >
>>> >
>>> > On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.org> wrote:
>>> >>
>>> >> Hi Matthew,
>>> >>
>>> >> On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail.com> wrote:
>>> >> >
>>> >> >
>>> >> > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromium.org>
>>> wrote:
>>> >> >>
>>> >> >> Hi Matthew,
>>> >> >>
>>> >> >> On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@gmail.com>
>>> wrote:
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@chromium.org>
>>> wrote:
>>> >> >> >>
>>> >> >> >> Hi Matthew,
>>> >> >> >>
>>> >> >> >> On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com>
>>> >> >> >> wrote:
>>> >> >> >> > Let me repost this to the bottom.  New to the mailing list ;)
>>> >> >> >> >
>>> >> >> >> > I am using chained boot to test uboot as a FIT image so I I
>>> don't
>>> >> >> >> > have to
>>> >> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be
>>> adjusted
>>> >> >> >> > for
>>> >> >> >> > chained boot?
>>> >> >> >> >
>>> >> >> >> > I am using instructions to boot Linux for Tegra from
>>> sdcard/USB in
>>> >> >> >> > developer
>>> >> >> >> > mode.  I can boot L4T fine with kernel v3.10.
>>> >> >> >> >
>>> >> >> >> > What mainline branch should I try?
>>> >> >> >>
>>> >> >> >> There's only one mainline, here:
>>> >> >> >> http://git.denx.de/?p=u-boot.git;a=summary
>>> >> >> >>
>>> >> >> >> There are various custodian branches but I don't believe the
>>> tegra
>>> >> >> >> one
>>> >> >> >> has anything different from mainline at present.
>>> >> >> >>
>>> >> >> >> - Simon
>>> >> >> >>
>>> >> >> > I will give mainline a try with:
>>> >> >> >
>>> >> >> > CONFIG_SYS_TEXT_BASE 0x8010E000
>>> >> >> > and
>>> >> >> >
>>> >> >> > CONFIG_SPL_TEXT_BASE 0x80108000
>>> >> >> >
>>> >> >> >
>>> >> >> > I know I will also need:
>>> >> >> >
>>> >> >> >
>>> >> >> > CONFIG_DISPLAY_PORT=y
>>> >> >>
>>> >> >> Do you mean CONFIG_DISPLAY? If so, it is already defined.
>>> >> >>
>>> >> >> > CONFIG_VIDEO_TEGRA124=y
>>> >> >>
>>> >> >> That is defined in mainline
>>> >> >>
>>> >> >> >
>>> >> >> >
>>> >> >> > for the console to display command prompt.
>>> >> >> >
>>> >> >> >
>>> >> >> > The FIT config I am using is from
>>> >> >> >
>>> >> >> > here:https://git.collabora.com/cgit/user/tomeu/u-boot.git/
>>> commit/?h=nyan-big
>>> >> >> >
>>> >> >> >
>>> >> >> > Do I need to adjust:
>>> >> >> >
>>> >> >> >
>>> >> >> >             load = <0>;
>>> >> >> >             entry = <0>;
>>> >> >> >
>>> >> >> >
>>> >> >> > /dts-v1/;
>>> >> >> >
>>> >> >> > / {
>>> >> >> >     description = "U-Boot + FDT --------- THIS PADDING IS NEEDED
>>> SO
>>> >> >> > THE
>>> >> >> > IMAGE STARTS AT THE RIGHT OFFSET";
>>> >> >>
>>> >> >> Perhaps you need to adjust this? How was the length of it
>>> calcualted?
>>> >> >
>>> >> >
>>> >> > I am really not sure how the padding was calculated.  I just assumed
>>> >> > this
>>> >> > kernel-big.its FIT config was correct for nyan_big.  I will try
>>> using my
>>> >> > working linux kernel fit config.
>>> >> >>
>>> >> >>
>>> >> >> >     #address-cells = <1>;
>>> >> >> >     images {
>>> >> >> >         kernel at 1{
>>> >> >> >             description = "kernel";
>>> >> >> >             data = /incbin/("u-boot-dtb.bin");
>>> >> >> >             type = "kernel_noload";
>>> >> >> >             arch = "arm";
>>> >> >> >             os = "linux";
>>> >> >> >             compression = "none";
>>> >> >> >             load = <0>;
>>> >> >> >             entry = <0>;
>>> >> >> >         };
>>> >> >> >         fdt at 1{
>>> >> >> >             description = "tegra124-nyan-big.dtb";
>>> >> >> >             data = /incbin/("dts/dt.dtb");
>>> >> >> >             type = "flat_dt";
>>> >> >> >             arch = "arm";
>>> >> >> >             compression = "none";
>>> >> >> >             hash at 1{
>>> >> >> >                 algo = "sha1";
>>> >> >> >             };
>>> >> >> >         };
>>> >> >> >     };
>>> >> >> >     configurations {
>>> >> >> >         default = "conf at 1";
>>> >> >> >         conf at 1{
>>> >> >> >             kernel = "kernel at 1";
>>> >> >> >             fdt = "fdt at 1";
>>> >> >> >         };
>>> >> >> >     };
>>> >> >> > };
>>> >> >> >
>>> >> >> >
>>> >> >> > please let me know if I should also adjust the SPL CONFIG even
>>> though
>>> >> >> > I
>>> >> >> > am chainbooting uboot:
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> > https://www.chromium.org/chromium-os/firmware-porting-guide/
>>> using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing
>>> -nv-U-Boot-chained-U-Boot-method-
>>> >> >>
>>> >> >> This is exynos, where we booted directly into U-Boot. Actually I'm
>>> >> >> wondering we should boot directly into U-Boot (instead of SPL) on
>>> nyan
>>> >> >> also. Perhaps someone at collabora would know? Did you search the
>>> >> >> mailing list?
>>> >> >>
>>> >> >> Regards,
>>> >> >> Simon
>>> >> >
>>> >> >
>>> >> > I have not searched the mailing list.  What should I search for?
>>> >> > Booting
>>> >> > nyan to u-boot directly bypassing SPL?
>>> >>
>>> >> Here are two subjects to search for:
>>> >>
>>> >> Veyron-speedy u-boot
>>> >> [PATCH 0/20] tegra: Expand Nyan-big support
>>> >>
>>> >> Regards,
>>> >> Simon
>>> >
>>> >
>>> > Very odd if I do not use "#address-cells = <1>;" the display flashes and
>>> > reboots into recovery but if I do use #address-cells = <1>; in my FIT
>>> config
>>> > I get a blank screen
>>> > so something is working when not using the padding.
>>>
>>> If you figure out where u-boot-dtb.bin needs to start by looking at
>>> depthcharge or where the kernel starts, then you can figure out how
>>> long the padding needs to be at the start of the FIT. Rather than
>>> guessing...!
>>>
>>> - Simon
>>>
>>>  Okay so depthcharge starts at 0x81000000 from here:
>> https://chromium.googlesource.com/chromiumos/platform/
>> depthcharge/+/master/board/nyan_big/defconfig#11
>>
>> In my System.map for u-boot after building says the start is:
>> 81000100 T __image_copy_start
>> 81000100 T _start
>>
>> Hence the define CONFIG_SYS_TEXT_BASE 0x81000100
>>
>> So you say use 0x81000000 as the CONFIG_SYS_TEXT_BASE and not 0x81000100
>> correct?
>>
>>> >
>>> > /dts-v1/;
>>> >
>>> > / {
>>> >     description = "Chrome OS nyan u-boot chain boot method";
>>> >     #address-cells = <1>;
>>> >     images {
>>> >         kernel at 1{
>>> >
>>> >>
>>> >> >>
>>> >> >>
>>> >> >> >>
>>> >> >> >> >
>>> >>
>>> >> >> >> > On May 1, 2017 12:11 PM, "Matthew Gorski" <
>>> matt.gorski at gmail.com>
>>> >> >> >> > wrote:
>>> >> >> >> >
>>> >> >> >> > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org>
>>> wrote:
>>> >> >> >> >
>>> >> >> >> > Hi Matthew,
>>> >> >> >> >
>>> >> >> >> > On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com>
>>> >> >> >> > wrote:
>>> >> >> >> >> Thanks for the reply Simon.
>>> >> >> >> >>
>>> >> >> >> >> I have been trying to find the System.map for depthcharge to
>>> see
>>> >> >> >> >> the
>>> >> >> >> >> kernel
>>> >> >> >> >> load address but I am unable to find anything.  I have tried
>>> >> >> >> >> multiple
>>> >> >> >> >> CONFIG_SYS_TEXT_BASE settings with no luck.
>>> >> >> >> >
>>> >> >> >> > How did you choose what to use? Also note that Tegra uses SPL
>>> to
>>> >> >> >> > start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
>>> >> >> >> >
>>> >> >> >> >>
>>> >> >> >> >> I am creating my sdcard with a standard linux (Linux for
>>> Tegra)
>>> >> >> >> >> rootfs:
>>> >> >> >> >
>>> >> >> >> > Did these instructions come from a web site somewhere?
>>> >> >> >> >
>>> >> >> >> >>
>>> >> >> >> >> Partition an SD card
>>> >> >> >> >>
>>> >> >> >> >> sudo cgpt create <MMC BLOCK DEVICE>
>>> >> >> >> >> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK
>>> >> >> >> >> DEVICE>
>>> >> >> >> >> # 16
>>> >> >> >> >> MB
>>> >> >> >> >> kernel image partition
>>> >> >> >> >> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B
>>> sectors>
>>> >> >> >> >> -t
>>> >> >> >> >> rootfs
>>> >> >> >> >> <MMC BLOCK DEVICE>
>>> >> >> >> >>
>>> >> >> >> >> cgpt doesn't seem to create a protective MBR. If one is not
>>> >> >> >> >> already
>>> >> >> >> >> in
>>> >> >> >> >> place, it can be created with:
>>> >> >> >> >>
>>> >> >> >> >> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
>>> >> >> >> >>
>>> >> >> >> >> Copy data to the SD card
>>> >> >> >> >>
>>> >> >> >> >> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
>>> >> >> >> >> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>>> >> >> >> >> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>>> >> >> >> >>
>>> >> >> >> >
>>> >> >> >> > How are you actually making it boot? Is this in dev mode with
>>> USB
>>> >> >> >> > boot
>>> >> >> >> > enabled and pressing Ctrl-U?
>>> >> >> >> >
>>> >> >> >> > Also, as this is a mailing list, please avoid top-posting.
>>> >> >> >> >
>>> >> >> >> > - Simon
>>> >> >> >> >
>>> >> >> >> > I am using chained boot to test uboot as a FIT image so I I
>>> don't
>>> >> >> >> > have to
>>> >> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be
>>> adjusted
>>> >> >> >> > for
>>> >> >> >> > chained boot?
>>> >> >> >> >
>>> >> >> >> > I am using instructions to boot Linux for Tegra from
>>> sdcard/USB in
>>> >> >> >> > developer
>>> >> >> >> > mode.  I can boot L4T fine with kernel v3.10.
>>> >> >> >> >
>>> >> >> >> > What mainline branch should I try?
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> >>
>>> >> >> >> >> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <
>>> sjg at chromium.org>
>>> >> >> >> >> wrote:
>>> >> >> >> >>>
>>> >> >> >> >>> Hi Matthew,
>>> >> >> >> >>>
>>> >> >> >> >>> On 1 May 2017 at 08:43, Matthew Gorski <
>>> matt.gorski at gmail.com>
>>> >> >> >> >>> wrote:
>>> >> >> >> >>> > I am porting u-boot to nyan_big and need some input.  I
>>> have
>>> >> >> >> >>> > been
>>> >> >> >> >>> > searching
>>> >> >> >> >>> > high and low and found this thread here: [U-Boot] [PATCH
>>> 0/20]
>>> >> >> >> >>> > tegra:
>>> >> >> >> >>> > Expand
>>> >> >> >> >>> > Nyan-big support
>>> >> >> >> >>> >
>>> >> >> >> >>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.
>>> html
>>> >> >> >> >>> >
>>> >> >> >> >>> > I have tried to build u-boot with the branch here:
>>> >> >> >> >>> >
>>> >> >> >> >>> >
>>> >> >> >> >>> >
>>> >> >> >> >>> > https://git.collabora.com/cgit
>>> /user/tomeu/u-boot.git/commit/?h=nyan-big
>>> >> >> >> >>> >
>>> >> >> >> >>> > and also the official chromium next branch
>>> >> >> >> >>>
>>> >> >> >> >>> Have you tried mainline U-Boot? It already supports nyan-big.
>>> >> >> >> >>> I'm
>>> >> >> >> >>> not
>>> >> >> >> >>> sure about the situation with the downstream trees.
>>> >> >> >> >>>
>>> >> >> >> >>> >
>>> >> >> >> >>> > I followed building instructions here:
>>> >> >> >> >>> >
>>> >> >> >> >>> >
>>> >> >> >> >>> >
>>> >> >> >> >>> >
>>> >> >> >> >>> > https://www.chromium.org/chrom
>>> ium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung
>>> -arm-chromebook
>>> >> >> >> >>> >
>>> >> >> >> >>> > I build with these commands:
>>> >> >> >> >>> >
>>> >> >> >> >>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its
>>> >> >> >> >>> > kernel-u-boot
>>> >> >> >> >>> >
>>> >> >> >> >>> > (with and without the load address setting)
>>> >> >> >> >>> >
>>> >> >> >> >>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
>>> >> >> >> >>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
>>> >> >> >> >>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk
>>> --version 1
>>> >> >> >> >>> > --config
>>> >> >> >> >>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
>>> >> >> >> >>> >
>>> >> >> >> >>> > I have had numerous failed attempts to boot uboot from
>>> sdcard
>>> >> >> >> >>> > mmcblk1p1
>>> >> >> >> >>> >
>>> >> >> >> >>> > Any help is appreciated I have only gotten a blank screen
>>> >> >> >> >>> > after
>>> >> >> >> >>> > weeks
>>> >> >> >> >>> > of
>>> >> >> >> >>> > flashing.  I can boot custom v3.10 kernels so I assume I am
>>> >> >> >> >>> > using
>>> >> >> >> >>> > the
>>> >> >> >> >>> > correct building procedure.  Thanks in advance for help
>>> from
>>> >> >> >> >>> > the
>>> >> >> >> >>> > u-boot
>>> >> >> >> >>> > community.
>>> >> >> >> >>>
>>> >> >> >> >>> It is possible that it needs a particular address due to
>>> >> >> >> >>> limitations
>>> >> >> >> >>> in the FIT support on Nyan. I'm not sure what it is but
>>> might be
>>> >> >> >> >>> able
>>> >> >> >> >>> to take a look at some point.
>>> >> >> >> >>>
>>> >> >> >> >>> How are you building your SD card? Are you following some
>>> >> >> >> >>> instructions
>>> >> >> >> >>> from somewhere?
>>> >> >> >> >>>
>>> >> >> >> >>> Regards,
>>> >> >> >> >>> Simon
>>> >> >> >> >>
>>> >> >> >> >>
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >
>>> >> >
>>> >
>>> >
>>>
>>
>>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Tomeu Vizoso]

On 2 May 2017 at 08:40, Tomeu Vizoso <tomeu@tomeuvizoso.net> wrote:
> On 2 May 2017 at 03:19, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> Seems if you change the FIT description from anything but
>>
>> "description = "Chrome OS kernel image with one or more FDT blobs";"
>>
>> the kernel wont load. So this issue has to be in the kernel-big.its
>> <https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel-big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923>
>>
>> https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel-big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923
>>
>> We may just need a proper working .its for nyan
>
> Hi Matthew,
>
> it has been quite a while, but I remember that if we only tried
> chainloading U-Boot was because the goal was to integrate these
> machines in our LAVA lab, which to date doesn't support Depthcharge
> (though I hope this will change once I get back some time).
>
> I cannot remember how the correct position of the kernel within the
> FIT image was calculated, but it definitely involved looking at the
> depthcharge sources.

Actually, I have grepped my IRC logs and turns out that we need for
the start of U-Boot's code to be aligned to 64kB.

Thus the padding.

Regards,

Tomeu

> But I do think to remember that it was only an issue once U-Boot tried
> to relocate itself.
>
> I don't see any reason why my old branch wouldn't work today on your
> machine, other than maybe your hw is a different revision with a
> memory chip that wasn't supported back then? I also don't see why
> mainline wouldn't work, provided you have that hack in the ITS.
>
> I'm adding Sjoerd to CC in case he remembers.
>
> Good luck,
>
> Tomeu
>
>> On Mon, May 1, 2017 at 7:45 PM, Matthew Gorski <matt.gorski@gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Mon, May 1, 2017 at 7:34 PM, Simon Glass <sjg@chromium.org> wrote:
>>>
>>>> Hi Matthew,
>>>>
>>>> On 1 May 2017 at 17:27, Matthew Gorski <matt.gorski@gmail.com> wrote:
>>>> >
>>>> >
>>>> > On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.org> wrote:
>>>> >>
>>>> >> Hi Matthew,
>>>> >>
>>>> >> On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail.com> wrote:
>>>> >> >
>>>> >> >
>>>> >> > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromium.org>
>>>> wrote:
>>>> >> >>
>>>> >> >> Hi Matthew,
>>>> >> >>
>>>> >> >> On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@gmail.com>
>>>> wrote:
>>>> >> >> >
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@chromium.org>
>>>> wrote:
>>>> >> >> >>
>>>> >> >> >> Hi Matthew,
>>>> >> >> >>
>>>> >> >> >> On 1 May 2017 at 10:40, Matthew Gorski <matt.gorski@gmail.com>
>>>> >> >> >> wrote:
>>>> >> >> >> > Let me repost this to the bottom.  New to the mailing list ;)
>>>> >> >> >> >
>>>> >> >> >> > I am using chained boot to test uboot as a FIT image so I I
>>>> don't
>>>> >> >> >> > have to
>>>> >> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be
>>>> adjusted
>>>> >> >> >> > for
>>>> >> >> >> > chained boot?
>>>> >> >> >> >
>>>> >> >> >> > I am using instructions to boot Linux for Tegra from
>>>> sdcard/USB in
>>>> >> >> >> > developer
>>>> >> >> >> > mode.  I can boot L4T fine with kernel v3.10.
>>>> >> >> >> >
>>>> >> >> >> > What mainline branch should I try?
>>>> >> >> >>
>>>> >> >> >> There's only one mainline, here:
>>>> >> >> >> http://git.denx.de/?p=u-boot.git;a=summary
>>>> >> >> >>
>>>> >> >> >> There are various custodian branches but I don't believe the
>>>> tegra
>>>> >> >> >> one
>>>> >> >> >> has anything different from mainline at present.
>>>> >> >> >>
>>>> >> >> >> - Simon
>>>> >> >> >>
>>>> >> >> > I will give mainline a try with:
>>>> >> >> >
>>>> >> >> > CONFIG_SYS_TEXT_BASE 0x8010E000
>>>> >> >> > and
>>>> >> >> >
>>>> >> >> > CONFIG_SPL_TEXT_BASE 0x80108000
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > I know I will also need:
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > CONFIG_DISPLAY_PORT=y
>>>> >> >>
>>>> >> >> Do you mean CONFIG_DISPLAY? If so, it is already defined.
>>>> >> >>
>>>> >> >> > CONFIG_VIDEO_TEGRA124=y
>>>> >> >>
>>>> >> >> That is defined in mainline
>>>> >> >>
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > for the console to display command prompt.
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > The FIT config I am using is from
>>>> >> >> >
>>>> >> >> > here:https://git.collabora.com/cgit/user/tomeu/u-boot.git/
>>>> commit/?h=nyan-big
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > Do I need to adjust:
>>>> >> >> >
>>>> >> >> >
>>>> >> >> >             load = <0>;
>>>> >> >> >             entry = <0>;
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > /dts-v1/;
>>>> >> >> >
>>>> >> >> > / {
>>>> >> >> >     description = "U-Boot + FDT --------- THIS PADDING IS NEEDED
>>>> SO
>>>> >> >> > THE
>>>> >> >> > IMAGE STARTS AT THE RIGHT OFFSET";
>>>> >> >>
>>>> >> >> Perhaps you need to adjust this? How was the length of it
>>>> calcualted?
>>>> >> >
>>>> >> >
>>>> >> > I am really not sure how the padding was calculated.  I just assumed
>>>> >> > this
>>>> >> > kernel-big.its FIT config was correct for nyan_big.  I will try
>>>> using my
>>>> >> > working linux kernel fit config.
>>>> >> >>
>>>> >> >>
>>>> >> >> >     #address-cells = <1>;
>>>> >> >> >     images {
>>>> >> >> >         kernel at 1{
>>>> >> >> >             description = "kernel";
>>>> >> >> >             data = /incbin/("u-boot-dtb.bin");
>>>> >> >> >             type = "kernel_noload";
>>>> >> >> >             arch = "arm";
>>>> >> >> >             os = "linux";
>>>> >> >> >             compression = "none";
>>>> >> >> >             load = <0>;
>>>> >> >> >             entry = <0>;
>>>> >> >> >         };
>>>> >> >> >         fdt at 1{
>>>> >> >> >             description = "tegra124-nyan-big.dtb";
>>>> >> >> >             data = /incbin/("dts/dt.dtb");
>>>> >> >> >             type = "flat_dt";
>>>> >> >> >             arch = "arm";
>>>> >> >> >             compression = "none";
>>>> >> >> >             hash at 1{
>>>> >> >> >                 algo = "sha1";
>>>> >> >> >             };
>>>> >> >> >         };
>>>> >> >> >     };
>>>> >> >> >     configurations {
>>>> >> >> >         default = "conf at 1";
>>>> >> >> >         conf at 1{
>>>> >> >> >             kernel = "kernel at 1";
>>>> >> >> >             fdt = "fdt at 1";
>>>> >> >> >         };
>>>> >> >> >     };
>>>> >> >> > };
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > please let me know if I should also adjust the SPL CONFIG even
>>>> though
>>>> >> >> > I
>>>> >> >> > am chainbooting uboot:
>>>> >> >> >
>>>> >> >> >
>>>> >> >> >
>>>> >> >> > https://www.chromium.org/chromium-os/firmware-porting-guide/
>>>> using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing
>>>> -nv-U-Boot-chained-U-Boot-method-
>>>> >> >>
>>>> >> >> This is exynos, where we booted directly into U-Boot. Actually I'm
>>>> >> >> wondering we should boot directly into U-Boot (instead of SPL) on
>>>> nyan
>>>> >> >> also. Perhaps someone at collabora would know? Did you search the
>>>> >> >> mailing list?
>>>> >> >>
>>>> >> >> Regards,
>>>> >> >> Simon
>>>> >> >
>>>> >> >
>>>> >> > I have not searched the mailing list.  What should I search for?
>>>> >> > Booting
>>>> >> > nyan to u-boot directly bypassing SPL?
>>>> >>
>>>> >> Here are two subjects to search for:
>>>> >>
>>>> >> Veyron-speedy u-boot
>>>> >> [PATCH 0/20] tegra: Expand Nyan-big support
>>>> >>
>>>> >> Regards,
>>>> >> Simon
>>>> >
>>>> >
>>>> > Very odd if I do not use "#address-cells = <1>;" the display flashes and
>>>> > reboots into recovery but if I do use #address-cells = <1>; in my FIT
>>>> config
>>>> > I get a blank screen
>>>> > so something is working when not using the padding.
>>>>
>>>> If you figure out where u-boot-dtb.bin needs to start by looking at
>>>> depthcharge or where the kernel starts, then you can figure out how
>>>> long the padding needs to be at the start of the FIT. Rather than
>>>> guessing...!
>>>>
>>>> - Simon
>>>>
>>>>  Okay so depthcharge starts at 0x81000000 from here:
>>> https://chromium.googlesource.com/chromiumos/platform/
>>> depthcharge/+/master/board/nyan_big/defconfig#11
>>>
>>> In my System.map for u-boot after building says the start is:
>>> 81000100 T __image_copy_start
>>> 81000100 T _start
>>>
>>> Hence the define CONFIG_SYS_TEXT_BASE 0x81000100
>>>
>>> So you say use 0x81000000 as the CONFIG_SYS_TEXT_BASE and not 0x81000100
>>> correct?
>>>
>>>> >
>>>> > /dts-v1/;
>>>> >
>>>> > / {
>>>> >     description = "Chrome OS nyan u-boot chain boot method";
>>>> >     #address-cells = <1>;
>>>> >     images {
>>>> >         kernel at 1{
>>>> >
>>>> >>
>>>> >> >>
>>>> >> >>
>>>> >> >> >>
>>>> >> >> >> >
>>>> >>
>>>> >> >> >> > On May 1, 2017 12:11 PM, "Matthew Gorski" <
>>>> matt.gorski at gmail.com>
>>>> >> >> >> > wrote:
>>>> >> >> >> >
>>>> >> >> >> > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chromium.org>
>>>> wrote:
>>>> >> >> >> >
>>>> >> >> >> > Hi Matthew,
>>>> >> >> >> >
>>>> >> >> >> > On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski@gmail.com>
>>>> >> >> >> > wrote:
>>>> >> >> >> >> Thanks for the reply Simon.
>>>> >> >> >> >>
>>>> >> >> >> >> I have been trying to find the System.map for depthcharge to
>>>> see
>>>> >> >> >> >> the
>>>> >> >> >> >> kernel
>>>> >> >> >> >> load address but I am unable to find anything.  I have tried
>>>> >> >> >> >> multiple
>>>> >> >> >> >> CONFIG_SYS_TEXT_BASE settings with no luck.
>>>> >> >> >> >
>>>> >> >> >> > How did you choose what to use? Also note that Tegra uses SPL
>>>> to
>>>> >> >> >> > start, so you may need to adjust CONFIG_SPL_TEXT_BASE instead.
>>>> >> >> >> >
>>>> >> >> >> >>
>>>> >> >> >> >> I am creating my sdcard with a standard linux (Linux for
>>>> Tegra)
>>>> >> >> >> >> rootfs:
>>>> >> >> >> >
>>>> >> >> >> > Did these instructions come from a web site somewhere?
>>>> >> >> >> >
>>>> >> >> >> >>
>>>> >> >> >> >> Partition an SD card
>>>> >> >> >> >>
>>>> >> >> >> >> sudo cgpt create <MMC BLOCK DEVICE>
>>>> >> >> >> >> sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t kernel <MMC BLOCK
>>>> >> >> >> >> DEVICE>
>>>> >> >> >> >> # 16
>>>> >> >> >> >> MB
>>>> >> >> >> >> kernel image partition
>>>> >> >> >> >> sudo cgpt add -b 32802 -s <ROOT PARTITION SIZE in 512B
>>>> sectors>
>>>> >> >> >> >> -t
>>>> >> >> >> >> rootfs
>>>> >> >> >> >> <MMC BLOCK DEVICE>
>>>> >> >> >> >>
>>>> >> >> >> >> cgpt doesn't seem to create a protective MBR. If one is not
>>>> >> >> >> >> already
>>>> >> >> >> >> in
>>>> >> >> >> >> place, it can be created with:
>>>> >> >> >> >>
>>>> >> >> >> >> sudo gdisk <MMC BLOCK DEVICE> # and enter command w
>>>> >> >> >> >>
>>>> >> >> >> >> Copy data to the SD card
>>>> >> >> >> >>
>>>> >> >> >> >> sudo dd if=./kernelpart.bin of=<MMC BLOCK DEVICE>p1
>>>> >> >> >> >> sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>>>> >> >> >> >> sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>>>> >> >> >> >>
>>>> >> >> >> >
>>>> >> >> >> > How are you actually making it boot? Is this in dev mode with
>>>> USB
>>>> >> >> >> > boot
>>>> >> >> >> > enabled and pressing Ctrl-U?
>>>> >> >> >> >
>>>> >> >> >> > Also, as this is a mailing list, please avoid top-posting.
>>>> >> >> >> >
>>>> >> >> >> > - Simon
>>>> >> >> >> >
>>>> >> >> >> > I am using chained boot to test uboot as a FIT image so I I
>>>> don't
>>>> >> >> >> > have to
>>>> >> >> >> > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE need to be
>>>> adjusted
>>>> >> >> >> > for
>>>> >> >> >> > chained boot?
>>>> >> >> >> >
>>>> >> >> >> > I am using instructions to boot Linux for Tegra from
>>>> sdcard/USB in
>>>> >> >> >> > developer
>>>> >> >> >> > mode.  I can boot L4T fine with kernel v3.10.
>>>> >> >> >> >
>>>> >> >> >> > What mainline branch should I try?
>>>> >> >> >> >
>>>> >> >> >> >
>>>> >> >> >> >>
>>>> >> >> >> >> On Mon, May 1, 2017 at 11:14 AM, Simon Glass <
>>>> sjg at chromium.org>
>>>> >> >> >> >> wrote:
>>>> >> >> >> >>>
>>>> >> >> >> >>> Hi Matthew,
>>>> >> >> >> >>>
>>>> >> >> >> >>> On 1 May 2017 at 08:43, Matthew Gorski <
>>>> matt.gorski at gmail.com>
>>>> >> >> >> >>> wrote:
>>>> >> >> >> >>> > I am porting u-boot to nyan_big and need some input.  I
>>>> have
>>>> >> >> >> >>> > been
>>>> >> >> >> >>> > searching
>>>> >> >> >> >>> > high and low and found this thread here: [U-Boot] [PATCH
>>>> 0/20]
>>>> >> >> >> >>> > tegra:
>>>> >> >> >> >>> > Expand
>>>> >> >> >> >>> > Nyan-big support
>>>> >> >> >> >>> >
>>>> >> >> >> >>> >  https://lists.denx.de/pipermail/u-boot/2015-March/209530.
>>>> html
>>>> >> >> >> >>> >
>>>> >> >> >> >>> > I have tried to build u-boot with the branch here:
>>>> >> >> >> >>> >
>>>> >> >> >> >>> >
>>>> >> >> >> >>> >
>>>> >> >> >> >>> > https://git.collabora.com/cgit
>>>> /user/tomeu/u-boot.git/commit/?h=nyan-big
>>>> >> >> >> >>> >
>>>> >> >> >> >>> > and also the official chromium next branch
>>>> >> >> >> >>>
>>>> >> >> >> >>> Have you tried mainline U-Boot? It already supports nyan-big.
>>>> >> >> >> >>> I'm
>>>> >> >> >> >>> not
>>>> >> >> >> >>> sure about the situation with the downstream trees.
>>>> >> >> >> >>>
>>>> >> >> >> >>> >
>>>> >> >> >> >>> > I followed building instructions here:
>>>> >> >> >> >>> >
>>>> >> >> >> >>> >
>>>> >> >> >> >>> >
>>>> >> >> >> >>> >
>>>> >> >> >> >>> > https://www.chromium.org/chrom
>>>> ium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung
>>>> -arm-chromebook
>>>> >> >> >> >>> >
>>>> >> >> >> >>> > I build with these commands:
>>>> >> >> >> >>> >
>>>> >> >> >> >>> > mkimage -e 0x81000100 -a 0x81000100 -f kernel-big.its
>>>> >> >> >> >>> > kernel-u-boot
>>>> >> >> >> >>> >
>>>> >> >> >> >>> > (with and without the load address setting)
>>>> >> >> >> >>> >
>>>> >> >> >> >>> > vbutil_kernel --arch arm --pack kernel.bin --keyblock
>>>> >> >> >> >>> > /usr/share/vboot/devkeys/kernel.keyblock --signprivate
>>>> >> >> >> >>> > /usr/share/vboot/devkeys/kernel_data_key.vbprivk
>>>> --version 1
>>>> >> >> >> >>> > --config
>>>> >> >> >> >>> > dummy.txt --vmlinuz kernel-u-boot --bootloader dummy.txt
>>>> >> >> >> >>> >
>>>> >> >> >> >>> > I have had numerous failed attempts to boot uboot from
>>>> sdcard
>>>> >> >> >> >>> > mmcblk1p1
>>>> >> >> >> >>> >
>>>> >> >> >> >>> > Any help is appreciated I have only gotten a blank screen
>>>> >> >> >> >>> > after
>>>> >> >> >> >>> > weeks
>>>> >> >> >> >>> > of
>>>> >> >> >> >>> > flashing.  I can boot custom v3.10 kernels so I assume I am
>>>> >> >> >> >>> > using
>>>> >> >> >> >>> > the
>>>> >> >> >> >>> > correct building procedure.  Thanks in advance for help
>>>> from
>>>> >> >> >> >>> > the
>>>> >> >> >> >>> > u-boot
>>>> >> >> >> >>> > community.
>>>> >> >> >> >>>
>>>> >> >> >> >>> It is possible that it needs a particular address due to
>>>> >> >> >> >>> limitations
>>>> >> >> >> >>> in the FIT support on Nyan. I'm not sure what it is but
>>>> might be
>>>> >> >> >> >>> able
>>>> >> >> >> >>> to take a look at some point.
>>>> >> >> >> >>>
>>>> >> >> >> >>> How are you building your SD card? Are you following some
>>>> >> >> >> >>> instructions
>>>> >> >> >> >>> from somewhere?
>>>> >> >> >> >>>
>>>> >> >> >> >>> Regards,
>>>> >> >> >> >>> Simon
>>>> >> >> >> >>
>>>> >> >> >> >>
>>>> >> >> >> >
>>>> >> >> >> >
>>>> >> >> >> >
>>>> >> >> >
>>>> >> >> >
>>>> >> >
>>>> >> >
>>>> >
>>>> >
>>>>
>>>
>>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> https://lists.denx.de/listinfo/u-boot

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Sjoerd Simons]

On Tue, 2017-05-02 at 08:42 +0200, Tomeu Vizoso wrote:
> On 2 May 2017 at 08:40, Tomeu Vizoso <tomeu@tomeuvizoso.net> wrote:
> > On 2 May 2017 at 03:19, Matthew Gorski <matt.gorski@gmail.com>
> > wrote:
> > > Seems if you change the FIT description from anything but
> > > 
> > > "description = "Chrome OS kernel image with one or more FDT
> > > blobs";"
> > > 
> > > the kernel wont load. So this issue has to be in the kernel-
> > > big.its
> > > <https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel
> > > -big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923>
> > > 
> > > https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel-
> > > big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923
> > > 
> > > We may just need a proper working .its for nyan
> > 
> > Hi Matthew,
> > 
> > it has been quite a while, but I remember that if we only tried
> > chainloading U-Boot was because the goal was to integrate these
> > machines in our LAVA lab, which to date doesn't support Depthcharge
> > (though I hope this will change once I get back some time).
> > 
> > I cannot remember how the correct position of the kernel within the
> > FIT image was calculated, but it definitely involved looking at the
> > depthcharge sources.
> 
> Actually, I have grepped my IRC logs and turns out that we need for
> the start of U-Boot's code to be aligned to 64kB.

Yup, U-boot both needs to be properly aligned and know its text base
address. 

So the calculation we did was basically look at depthcharge where in
memory the FIT image gets loaded, determine a suitable load address
after that (e.g fit load + 64k), configure that in u-boot and then add
enough padding in the fit image itself such that the u-boot code starts
at the determined address in memory by putting in just the right amount
of padding ;).

It is rather ugly, but it does allow running u-boot without the need to
change the firmware in flash.

> Thus the padding.
> 
> Regards,
> 
> Tomeu
> 
> > But I do think to remember that it was only an issue once U-Boot
> > tried
> > to relocate itself.
> > 
> > I don't see any reason why my old branch wouldn't work today on
> > your
> > machine, other than maybe your hw is a different revision with a
> > memory chip that wasn't supported back then? I also don't see why
> > mainline wouldn't work, provided you have that hack in the ITS.
> > 
> > I'm adding Sjoerd to CC in case he remembers.
> > 
> > Good luck,
> > 
> > Tomeu
> > 
> > > On Mon, May 1, 2017 at 7:45 PM, Matthew Gorski <matt.gorski@gmail
> > > .com>
> > > wrote:
> > > 
> > > > 
> > > > 
> > > > On Mon, May 1, 2017 at 7:34 PM, Simon Glass <sjg@chromium.org>
> > > > wrote:
> > > > 
> > > > > Hi Matthew,
> > > > > 
> > > > > On 1 May 2017 at 17:27, Matthew Gorski <matt.gorski@gmail.com
> > > > > > wrote:
> > > > > > 
> > > > > > 
> > > > > > On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.o
> > > > > > rg> wrote:
> > > > > > > 
> > > > > > > Hi Matthew,
> > > > > > > 
> > > > > > > On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail
> > > > > > > .com> wrote:
> > > > > > > > 
> > > > > > > > 
> > > > > > > > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromi
> > > > > > > > um.org>
> > > > > 
> > > > > wrote:
> > > > > > > > > 
> > > > > > > > > Hi Matthew,
> > > > > > > > > 
> > > > > > > > > On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@g
> > > > > > > > > mail.com>
> > > > > 
> > > > > wrote:
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@ch
> > > > > > > > > > romium.org>
> > > > > 
> > > > > wrote:
> > > > > > > > > > > 
> > > > > > > > > > > Hi Matthew,
> > > > > > > > > > > 
> > > > > > > > > > > On 1 May 2017 at 10:40, Matthew Gorski <matt.gors
> > > > > > > > > > > ki at gmail.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > > > Let me repost this to the bottom.  New to the
> > > > > > > > > > > > mailing list ;)
> > > > > > > > > > > > 
> > > > > > > > > > > > I am using chained boot to test uboot as a FIT
> > > > > > > > > > > > image so I I
> > > > > 
> > > > > don't
> > > > > > > > > > > > have to
> > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
> > > > > > > > > > > > need to be
> > > > > 
> > > > > adjusted
> > > > > > > > > > > > for
> > > > > > > > > > > > chained boot?
> > > > > > > > > > > > 
> > > > > > > > > > > > I am using instructions to boot Linux for Tegra
> > > > > > > > > > > > from
> > > > > 
> > > > > sdcard/USB in
> > > > > > > > > > > > developer
> > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
> > > > > > > > > > > > 
> > > > > > > > > > > > What mainline branch should I try?
> > > > > > > > > > > 
> > > > > > > > > > > There's only one mainline, here:
> > > > > > > > > > > http://git.denx.de/?p=u-boot.git;a=summary
> > > > > > > > > > > 
> > > > > > > > > > > There are various custodian branches but I don't
> > > > > > > > > > > believe the
> > > > > 
> > > > > tegra
> > > > > > > > > > > one
> > > > > > > > > > > has anything different from mainline at present.
> > > > > > > > > > > 
> > > > > > > > > > > - Simon
> > > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > I will give mainline a try with:
> > > > > > > > > > 
> > > > > > > > > > CONFIG_SYS_TEXT_BASE 0x8010E000
> > > > > > > > > > and
> > > > > > > > > > 
> > > > > > > > > > CONFIG_SPL_TEXT_BASE 0x80108000
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > I know I will also need:
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > CONFIG_DISPLAY_PORT=y
> > > > > > > > > 
> > > > > > > > > Do you mean CONFIG_DISPLAY? If so, it is already
> > > > > > > > > defined.
> > > > > > > > > 
> > > > > > > > > > CONFIG_VIDEO_TEGRA124=y
> > > > > > > > > 
> > > > > > > > > That is defined in mainline
> > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > for the console to display command prompt.
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > The FIT config I am using is from
> > > > > > > > > > 
> > > > > > > > > > here:https://git.collabora.com/cgit/user/tomeu/u-bo
> > > > > > > > > > ot.git/
> > > > > 
> > > > > commit/?h=nyan-big
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > Do I need to adjust:
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > >             load = <0>;
> > > > > > > > > >             entry = <0>;
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > /dts-v1/;
> > > > > > > > > > 
> > > > > > > > > > / {
> > > > > > > > > >     description = "U-Boot + FDT --------- THIS
> > > > > > > > > > PADDING IS NEEDED
> > > > > 
> > > > > SO
> > > > > > > > > > THE
> > > > > > > > > > IMAGE STARTS AT THE RIGHT OFFSET";
> > > > > > > > > 
> > > > > > > > > Perhaps you need to adjust this? How was the length
> > > > > > > > > of it
> > > > > 
> > > > > calcualted?
> > > > > > > > 
> > > > > > > > 
> > > > > > > > I am really not sure how the padding was calculated.  I
> > > > > > > > just assumed
> > > > > > > > this
> > > > > > > > kernel-big.its FIT config was correct for nyan_big.  I
> > > > > > > > will try
> > > > > 
> > > > > using my
> > > > > > > > working linux kernel fit config.
> > > > > > > > > 
> > > > > > > > > 
> > > > > > > > > >     #address-cells = <1>;
> > > > > > > > > >     images {
> > > > > > > > > >         kernel at 1{
> > > > > > > > > >             description = "kernel";
> > > > > > > > > >             data = /incbin/("u-boot-dtb.bin");
> > > > > > > > > >             type = "kernel_noload";
> > > > > > > > > >             arch = "arm";
> > > > > > > > > >             os = "linux";
> > > > > > > > > >             compression = "none";
> > > > > > > > > >             load = <0>;
> > > > > > > > > >             entry = <0>;
> > > > > > > > > >         };
> > > > > > > > > >         fdt at 1{
> > > > > > > > > >             description = "tegra124-nyan-big.dtb";
> > > > > > > > > >             data = /incbin/("dts/dt.dtb");
> > > > > > > > > >             type = "flat_dt";
> > > > > > > > > >             arch = "arm";
> > > > > > > > > >             compression = "none";
> > > > > > > > > >             hash at 1{
> > > > > > > > > >                 algo = "sha1";
> > > > > > > > > >             };
> > > > > > > > > >         };
> > > > > > > > > >     };
> > > > > > > > > >     configurations {
> > > > > > > > > >         default = "conf at 1";
> > > > > > > > > >         conf at 1{
> > > > > > > > > >             kernel = "kernel at 1";
> > > > > > > > > >             fdt = "fdt at 1";
> > > > > > > > > >         };
> > > > > > > > > >     };
> > > > > > > > > > };
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > please let me know if I should also adjust the SPL
> > > > > > > > > > CONFIG even
> > > > > 
> > > > > though
> > > > > > > > > > I
> > > > > > > > > > am chainbooting uboot:
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > https://www.chromium.org/chromium-os/firmware-porti
> > > > > > > > > > ng-guide/
> > > > > 
> > > > > using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing
> > > > > -nv-U-Boot-chained-U-Boot-method-
> > > > > > > > > 
> > > > > > > > > This is exynos, where we booted directly into U-Boot. 
> > > > > > > > > Actually I'm
> > > > > > > > > wondering we should boot directly into U-Boot
> > > > > > > > > (instead of SPL) on
> > > > > 
> > > > > nyan
> > > > > > > > > also. Perhaps someone at collabora would know? Did
> > > > > > > > > you search the
> > > > > > > > > mailing list?
> > > > > > > > > 
> > > > > > > > > Regards,
> > > > > > > > > Simon
> > > > > > > > 
> > > > > > > > 
> > > > > > > > I have not searched the mailing list.  What should I
> > > > > > > > search for?
> > > > > > > > Booting
> > > > > > > > nyan to u-boot directly bypassing SPL?
> > > > > > > 
> > > > > > > Here are two subjects to search for:
> > > > > > > 
> > > > > > > Veyron-speedy u-boot
> > > > > > > [PATCH 0/20] tegra: Expand Nyan-big support
> > > > > > > 
> > > > > > > Regards,
> > > > > > > Simon
> > > > > > 
> > > > > > 
> > > > > > Very odd if I do not use "#address-cells = <1>;" the
> > > > > > display flashes and
> > > > > > reboots into recovery but if I do use #address-cells = <1>;
> > > > > > in my FIT
> > > > > 
> > > > > config
> > > > > > I get a blank screen
> > > > > > so something is working when not using the padding.
> > > > > 
> > > > > If you figure out where u-boot-dtb.bin needs to start by
> > > > > looking at
> > > > > depthcharge or where the kernel starts, then you can figure
> > > > > out how
> > > > > long the padding needs to be at the start of the FIT. Rather
> > > > > than
> > > > > guessing...!
> > > > > 
> > > > > - Simon
> > > > > 
> > > > >  Okay so depthcharge starts at 0x81000000 from here:
> > > > 
> > > > https://chromium.googlesource.com/chromiumos/platform/
> > > > depthcharge/+/master/board/nyan_big/defconfig#11
> > > > 
> > > > In my System.map for u-boot after building says the start is:
> > > > 81000100 T __image_copy_start
> > > > 81000100 T _start
> > > > 
> > > > Hence the define CONFIG_SYS_TEXT_BASE 0x81000100
> > > > 
> > > > So you say use 0x81000000 as the CONFIG_SYS_TEXT_BASE and not
> > > > 0x81000100
> > > > correct?
> > > > 
> > > > > > 
> > > > > > /dts-v1/;
> > > > > > 
> > > > > > / {
> > > > > >     description = "Chrome OS nyan u-boot chain boot
> > > > > > method";
> > > > > >     #address-cells = <1>;
> > > > > >     images {
> > > > > >         kernel at 1{
> > > > > > 
> > > > > > > 
> > > > > > > > > 
> > > > > > > > > 
> > > > > > > > > > > 
> > > > > > > > > > > > 
> > > > > > > > > > > > On May 1, 2017 12:11 PM, "Matthew Gorski" <
> > > > > 
> > > > > matt.gorski at gmail.com>
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > 
> > > > > > > > > > > > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chr
> > > > > > > > > > > > omium.org>
> > > > > 
> > > > > wrote:
> > > > > > > > > > > > 
> > > > > > > > > > > > Hi Matthew,
> > > > > > > > > > > > 
> > > > > > > > > > > > On 1 May 2017 at 09:37, Matthew Gorski <matt.go
> > > > > > > > > > > > rski at gmail.com>
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > > Thanks for the reply Simon.
> > > > > > > > > > > > > 
> > > > > > > > > > > > > I have been trying to find the System.map for
> > > > > > > > > > > > > depthcharge to
> > > > > 
> > > > > see
> > > > > > > > > > > > > the
> > > > > > > > > > > > > kernel
> > > > > > > > > > > > > load address but I am unable to find
> > > > > > > > > > > > > anything.  I have tried
> > > > > > > > > > > > > multiple
> > > > > > > > > > > > > CONFIG_SYS_TEXT_BASE settings with no luck.
> > > > > > > > > > > > 
> > > > > > > > > > > > How did you choose what to use? Also note that
> > > > > > > > > > > > Tegra uses SPL
> > > > > 
> > > > > to
> > > > > > > > > > > > start, so you may need to adjust
> > > > > > > > > > > > CONFIG_SPL_TEXT_BASE instead.
> > > > > > > > > > > > 
> > > > > > > > > > > > > 
> > > > > > > > > > > > > I am creating my sdcard with a standard linux
> > > > > > > > > > > > > (Linux for
> > > > > 
> > > > > Tegra)
> > > > > > > > > > > > > rootfs:
> > > > > > > > > > > > 
> > > > > > > > > > > > Did these instructions come from a web site
> > > > > > > > > > > > somewhere?
> > > > > > > > > > > > 
> > > > > > > > > > > > > 
> > > > > > > > > > > > > Partition an SD card
> > > > > > > > > > > > > 
> > > > > > > > > > > > > sudo cgpt create <MMC BLOCK DEVICE>
> > > > > > > > > > > > > sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t
> > > > > > > > > > > > > kernel <MMC BLOCK
> > > > > > > > > > > > > DEVICE>
> > > > > > > > > > > > > # 16
> > > > > > > > > > > > > MB
> > > > > > > > > > > > > kernel image partition
> > > > > > > > > > > > > sudo cgpt add -b 32802 -s <ROOT PARTITION
> > > > > > > > > > > > > SIZE in 512B
> > > > > 
> > > > > sectors>
> > > > > > > > > > > > > -t
> > > > > > > > > > > > > rootfs
> > > > > > > > > > > > > <MMC BLOCK DEVICE>
> > > > > > > > > > > > > 
> > > > > > > > > > > > > cgpt doesn't seem to create a protective MBR.
> > > > > > > > > > > > > If one is not
> > > > > > > > > > > > > already
> > > > > > > > > > > > > in
> > > > > > > > > > > > > place, it can be created with:
> > > > > > > > > > > > > 
> > > > > > > > > > > > > sudo gdisk <MMC BLOCK DEVICE> # and enter
> > > > > > > > > > > > > command w
> > > > > > > > > > > > > 
> > > > > > > > > > > > > Copy data to the SD card
> > > > > > > > > > > > > 
> > > > > > > > > > > > > sudo dd if=./kernelpart.bin of=<MMC BLOCK
> > > > > > > > > > > > > DEVICE>p1
> > > > > > > > > > > > > sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
> > > > > > > > > > > > > sudo mount <MMC BLOCK DEVICE>p2 /mnt/
> > > > > > > > > > > > > 
> > > > > > > > > > > > 
> > > > > > > > > > > > How are you actually making it boot? Is this in
> > > > > > > > > > > > dev mode with
> > > > > 
> > > > > USB
> > > > > > > > > > > > boot
> > > > > > > > > > > > enabled and pressing Ctrl-U?
> > > > > > > > > > > > 
> > > > > > > > > > > > Also, as this is a mailing list, please avoid
> > > > > > > > > > > > top-posting.
> > > > > > > > > > > > 
> > > > > > > > > > > > - Simon
> > > > > > > > > > > > 
> > > > > > > > > > > > I am using chained boot to test uboot as a FIT
> > > > > > > > > > > > image so I I
> > > > > 
> > > > > don't
> > > > > > > > > > > > have to
> > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
> > > > > > > > > > > > need to be
> > > > > 
> > > > > adjusted
> > > > > > > > > > > > for
> > > > > > > > > > > > chained boot?
> > > > > > > > > > > > 
> > > > > > > > > > > > I am using instructions to boot Linux for Tegra
> > > > > > > > > > > > from
> > > > > 
> > > > > sdcard/USB in
> > > > > > > > > > > > developer
> > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
> > > > > > > > > > > > 
> > > > > > > > > > > > What mainline branch should I try?
> > > > > > > > > > > > 
> > > > > > > > > > > > 
> > > > > > > > > > > > > 
> > > > > > > > > > > > > On Mon, May 1, 2017 at 11:14 AM, Simon Glass
> > > > > > > > > > > > > <
> > > > > 
> > > > > sjg at chromium.org>
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > Hi Matthew,
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > On 1 May 2017 at 08:43, Matthew Gorski <
> > > > > 
> > > > > matt.gorski at gmail.com>
> > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > I am porting u-boot to nyan_big and need
> > > > > > > > > > > > > > > some input.  I
> > > > > 
> > > > > have
> > > > > > > > > > > > > > > been
> > > > > > > > > > > > > > > searching
> > > > > > > > > > > > > > > high and low and found this thread here:
> > > > > > > > > > > > > > > [U-Boot] [PATCH
> > > > > 
> > > > > 0/20]
> > > > > > > > > > > > > > > tegra:
> > > > > > > > > > > > > > > Expand
> > > > > > > > > > > > > > > Nyan-big support
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > >  https://lists.denx.de/pipermail/u-boot/2
> > > > > > > > > > > > > > > 015-March/209530.
> > > > > 
> > > > > html
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > I have tried to build u-boot with the
> > > > > > > > > > > > > > > branch here:
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > https://git.collabora.com/cgit
> > > > > 
> > > > > /user/tomeu/u-boot.git/commit/?h=nyan-big
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > and also the official chromium next
> > > > > > > > > > > > > > > branch
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > Have you tried mainline U-Boot? It already
> > > > > > > > > > > > > > supports nyan-big.
> > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > not
> > > > > > > > > > > > > > sure about the situation with the
> > > > > > > > > > > > > > downstream trees.
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > I followed building instructions here:
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > https://www.chromium.org/chrom
> > > > > 
> > > > > ium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung
> > > > > -arm-chromebook
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > I build with these commands:
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > mkimage -e 0x81000100 -a 0x81000100 -f
> > > > > > > > > > > > > > > kernel-big.its
> > > > > > > > > > > > > > > kernel-u-boot
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > (with and without the load address
> > > > > > > > > > > > > > > setting)
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > vbutil_kernel --arch arm --pack
> > > > > > > > > > > > > > > kernel.bin --keyblock
> > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kernel.keyblock
> > > > > > > > > > > > > > > --signprivate
> > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kernel_data_key.
> > > > > > > > > > > > > > > vbprivk
> > > > > 
> > > > > --version 1
> > > > > > > > > > > > > > > --config
> > > > > > > > > > > > > > > dummy.txt --vmlinuz kernel-u-boot --
> > > > > > > > > > > > > > > bootloader dummy.txt
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > I have had numerous failed attempts to
> > > > > > > > > > > > > > > boot uboot from
> > > > > 
> > > > > sdcard
> > > > > > > > > > > > > > > mmcblk1p1
> > > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > Any help is appreciated I have only
> > > > > > > > > > > > > > > gotten a blank screen
> > > > > > > > > > > > > > > after
> > > > > > > > > > > > > > > weeks
> > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > flashing.  I can boot custom v3.10
> > > > > > > > > > > > > > > kernels so I assume I am
> > > > > > > > > > > > > > > using
> > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > correct building procedure.  Thanks in
> > > > > > > > > > > > > > > advance for help
> > > > > 
> > > > > from
> > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > u-boot
> > > > > > > > > > > > > > > community.
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > It is possible that it needs a particular
> > > > > > > > > > > > > > address due to
> > > > > > > > > > > > > > limitations
> > > > > > > > > > > > > > in the FIT support on Nyan. I'm not sure
> > > > > > > > > > > > > > what it is but
> > > > > 
> > > > > might be
> > > > > > > > > > > > > > able
> > > > > > > > > > > > > > to take a look at some point.
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > How are you building your SD card? Are you
> > > > > > > > > > > > > > following some
> > > > > > > > > > > > > > instructions
> > > > > > > > > > > > > > from somewhere?
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > Simon
> > > > > > > > > > > > > 
> > > > > > > > > > > > > 
> > > > > > > > > > > > 
> > > > > > > > > > > > 
> > > > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > 
> > > > > > > > 
> > > > > > 
> > > > > > 
> > > > 
> > > > 
> > > 
> > > _______________________________________________
> > > U-Boot mailing list
> > > U-Boot at lists.denx.de
> > > https://lists.denx.de/listinfo/u-boot

-- 
Sjoerd Simons
Collabora Ltd.

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

On Tue, May 2, 2017 at 2:54 AM, Sjoerd Simons <sjoerd.simons@collabora.co.uk
> wrote:

> On Tue, 2017-05-02 at 08:42 +0200, Tomeu Vizoso wrote:
> > On 2 May 2017 at 08:40, Tomeu Vizoso <tomeu@tomeuvizoso.net> wrote:
> > > On 2 May 2017 at 03:19, Matthew Gorski <matt.gorski@gmail.com>
> > > wrote:
> > > > Seems if you change the FIT description from anything but
> > > >
> > > > "description = "Chrome OS kernel image with one or more FDT
> > > > blobs";"
> > > >
> > > > the kernel wont load. So this issue has to be in the kernel-
> > > > big.its
> > > > <https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel
> > > > -big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923>
> > > >
> > > > https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel-
> > > > big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923
> > > >
> > > > We may just need a proper working .its for nyan
> > >
> > > Hi Matthew,
> > >
> > > it has been quite a while, but I remember that if we only tried
> > > chainloading U-Boot was because the goal was to integrate these
> > > machines in our LAVA lab, which to date doesn't support Depthcharge
> > > (though I hope this will change once I get back some time).
> > >
> > > I cannot remember how the correct position of the kernel within the
> > > FIT image was calculated, but it definitely involved looking at the
> > > depthcharge sources.
> >
> > Actually, I have grepped my IRC logs and turns out that we need for
> > the start of U-Boot's code to be aligned to 64kB.
>
> Yup, U-boot both needs to be properly aligned and know its text base
> address.
>
> So the calculation we did was basically look at depthcharge where in
> memory the FIT image gets loaded, determine a suitable load address
> after that (e.g fit load + 64k), configure that in u-boot and then add
> enough padding in the fit image itself such that the u-boot code starts
> at the determined address in memory by putting in just the right amount
> of padding ;).
>
> It is rather ugly, but it does allow running u-boot without the need to
> change the firmware in flash.
>

Thank You Tomeu, Sjoerd and Simon for taking the time to chime in on an old
but interesting topic.

I believe I have enough info from you all to get this figured out now.

Since depthcharch loads the FIT image at 0x81000000
https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/master/board/nyan_big/defconfig#11

I need to determine a suitable load address e.g fit load + 64k

So 81000000 + 64k.

One thing I am not certain about is adding the padding to the FIT .its
config. How is this done?

description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE IMAGE
STARTS AT THE RIGHT OFFSET";

>
> > Thus the padding.
> >
> > Regards,
> >
> > Tomeu
> >
> > > But I do think to remember that it was only an issue once U-Boot
> > > tried
> > > to relocate itself.
> > >
> > > I don't see any reason why my old branch wouldn't work today on
> > > your
> > > machine, other than maybe your hw is a different revision with a
> > > memory chip that wasn't supported back then? I also don't see why
> > > mainline wouldn't work, provided you have that hack in the ITS.
> > >
> > > I'm adding Sjoerd to CC in case he remembers.
> > >
> > > Good luck,
> > >
> > > Tomeu
> > >
> > > > On Mon, May 1, 2017 at 7:45 PM, Matthew Gorski <matt.gorski@gmail
> > > > .com>
> > > > wrote:
> > > >
> > > > >
> > > > >
> > > > > On Mon, May 1, 2017 at 7:34 PM, Simon Glass <sjg@chromium.org>
> > > > > wrote:
> > > > >
> > > > > > Hi Matthew,
> > > > > >
> > > > > > On 1 May 2017 at 17:27, Matthew Gorski <matt.gorski@gmail.com
> > > > > > > wrote:
> > > > > > >
> > > > > > >
> > > > > > > On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.o
> > > > > > > rg> wrote:
> > > > > > > >
> > > > > > > > Hi Matthew,
> > > > > > > >
> > > > > > > > On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail
> > > > > > > > .com> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromi
> > > > > > > > > um.org>
> > > > > >
> > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Hi Matthew,
> > > > > > > > > >
> > > > > > > > > > On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@g
> > > > > > > > > > mail.com>
> > > > > >
> > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@ch
> > > > > > > > > > > romium.org>
> > > > > >
> > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi Matthew,
> > > > > > > > > > > >
> > > > > > > > > > > > On 1 May 2017 at 10:40, Matthew Gorski <matt.gors
> > > > > > > > > > > > ki at gmail.com>
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > > Let me repost this to the bottom.  New to the
> > > > > > > > > > > > > mailing list ;)
> > > > > > > > > > > > >
> > > > > > > > > > > > > I am using chained boot to test uboot as a FIT
> > > > > > > > > > > > > image so I I
> > > > > >
> > > > > > don't
> > > > > > > > > > > > > have to
> > > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
> > > > > > > > > > > > > need to be
> > > > > >
> > > > > > adjusted
> > > > > > > > > > > > > for
> > > > > > > > > > > > > chained boot?
> > > > > > > > > > > > >
> > > > > > > > > > > > > I am using instructions to boot Linux for Tegra
> > > > > > > > > > > > > from
> > > > > >
> > > > > > sdcard/USB in
> > > > > > > > > > > > > developer
> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
> > > > > > > > > > > > >
> > > > > > > > > > > > > What mainline branch should I try?
> > > > > > > > > > > >
> > > > > > > > > > > > There's only one mainline, here:
> > > > > > > > > > > > http://git.denx.de/?p=u-boot.git;a=summary
> > > > > > > > > > > >
> > > > > > > > > > > > There are various custodian branches but I don't
> > > > > > > > > > > > believe the
> > > > > >
> > > > > > tegra
> > > > > > > > > > > > one
> > > > > > > > > > > > has anything different from mainline at present.
> > > > > > > > > > > >
> > > > > > > > > > > > - Simon
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > I will give mainline a try with:
> > > > > > > > > > >
> > > > > > > > > > > CONFIG_SYS_TEXT_BASE 0x8010E000
> > > > > > > > > > > and
> > > > > > > > > > >
> > > > > > > > > > > CONFIG_SPL_TEXT_BASE 0x80108000
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > I know I will also need:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > CONFIG_DISPLAY_PORT=y
> > > > > > > > > >
> > > > > > > > > > Do you mean CONFIG_DISPLAY? If so, it is already
> > > > > > > > > > defined.
> > > > > > > > > >
> > > > > > > > > > > CONFIG_VIDEO_TEGRA124=y
> > > > > > > > > >
> > > > > > > > > > That is defined in mainline
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > for the console to display command prompt.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > The FIT config I am using is from
> > > > > > > > > > >
> > > > > > > > > > > here:https://git.collabora.com/cgit/user/tomeu/u-bo
> > > > > > > > > > > ot.git/
> > > > > >
> > > > > > commit/?h=nyan-big
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Do I need to adjust:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >             load = <0>;
> > > > > > > > > > >             entry = <0>;
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > /dts-v1/;
> > > > > > > > > > >
> > > > > > > > > > > / {
> > > > > > > > > > >     description = "U-Boot + FDT --------- THIS
> > > > > > > > > > > PADDING IS NEEDED
> > > > > >
> > > > > > SO
> > > > > > > > > > > THE
> > > > > > > > > > > IMAGE STARTS AT THE RIGHT OFFSET";
> > > > > > > > > >
> > > > > > > > > > Perhaps you need to adjust this? How was the length
> > > > > > > > > > of it
> > > > > >
> > > > > > calcualted?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I am really not sure how the padding was calculated.  I
> > > > > > > > > just assumed
> > > > > > > > > this
> > > > > > > > > kernel-big.its FIT config was correct for nyan_big.  I
> > > > > > > > > will try
> > > > > >
> > > > > > using my
> > > > > > > > > working linux kernel fit config.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >     #address-cells = <1>;
> > > > > > > > > > >     images {
> > > > > > > > > > >         kernel at 1{
> > > > > > > > > > >             description = "kernel";
> > > > > > > > > > >             data = /incbin/("u-boot-dtb.bin");
> > > > > > > > > > >             type = "kernel_noload";
> > > > > > > > > > >             arch = "arm";
> > > > > > > > > > >             os = "linux";
> > > > > > > > > > >             compression = "none";
> > > > > > > > > > >             load = <0>;
> > > > > > > > > > >             entry = <0>;
> > > > > > > > > > >         };
> > > > > > > > > > >         fdt at 1{
> > > > > > > > > > >             description = "tegra124-nyan-big.dtb";
> > > > > > > > > > >             data = /incbin/("dts/dt.dtb");
> > > > > > > > > > >             type = "flat_dt";
> > > > > > > > > > >             arch = "arm";
> > > > > > > > > > >             compression = "none";
> > > > > > > > > > >             hash at 1{
> > > > > > > > > > >                 algo = "sha1";
> > > > > > > > > > >             };
> > > > > > > > > > >         };
> > > > > > > > > > >     };
> > > > > > > > > > >     configurations {
> > > > > > > > > > >         default = "conf at 1";
> > > > > > > > > > >         conf at 1{
> > > > > > > > > > >             kernel = "kernel at 1";
> > > > > > > > > > >             fdt = "fdt at 1";
> > > > > > > > > > >         };
> > > > > > > > > > >     };
> > > > > > > > > > > };
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > please let me know if I should also adjust the SPL
> > > > > > > > > > > CONFIG even
> > > > > >
> > > > > > though
> > > > > > > > > > > I
> > > > > > > > > > > am chainbooting uboot:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > https://www.chromium.org/chromium-os/firmware-porti
> > > > > > > > > > > ng-guide/
> > > > > >
> > > > > > using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing
> > > > > > -nv-U-Boot-chained-U-Boot-method-
> > > > > > > > > >
> > > > > > > > > > This is exynos, where we booted directly into U-Boot.
> > > > > > > > > > Actually I'm
> > > > > > > > > > wondering we should boot directly into U-Boot
> > > > > > > > > > (instead of SPL) on
> > > > > >
> > > > > > nyan
> > > > > > > > > > also. Perhaps someone at collabora would know? Did
> > > > > > > > > > you search the
> > > > > > > > > > mailing list?
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Simon
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I have not searched the mailing list.  What should I
> > > > > > > > > search for?
> > > > > > > > > Booting
> > > > > > > > > nyan to u-boot directly bypassing SPL?
> > > > > > > >
> > > > > > > > Here are two subjects to search for:
> > > > > > > >
> > > > > > > > Veyron-speedy u-boot
> > > > > > > > [PATCH 0/20] tegra: Expand Nyan-big support
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Simon
> > > > > > >
> > > > > > >
> > > > > > > Very odd if I do not use "#address-cells = <1>;" the
> > > > > > > display flashes and
> > > > > > > reboots into recovery but if I do use #address-cells = <1>;
> > > > > > > in my FIT
> > > > > >
> > > > > > config
> > > > > > > I get a blank screen
> > > > > > > so something is working when not using the padding.
> > > > > >
> > > > > > If you figure out where u-boot-dtb.bin needs to start by
> > > > > > looking at
> > > > > > depthcharge or where the kernel starts, then you can figure
> > > > > > out how
> > > > > > long the padding needs to be at the start of the FIT. Rather
> > > > > > than
> > > > > > guessing...!
> > > > > >
> > > > > > - Simon
> > > > > >
> > > > > >  Okay so depthcharge starts at 0x81000000 from here:
> > > > >
> > > > > https://chromium.googlesource.com/chromiumos/platform/
> > > > > depthcharge/+/master/board/nyan_big/defconfig#11
> > > > >
> > > > > In my System.map for u-boot after building says the start is:
> > > > > 81000100 T __image_copy_start
> > > > > 81000100 T _start
> > > > >
> > > > > Hence the define CONFIG_SYS_TEXT_BASE 0x81000100
> > > > >
> > > > > So you say use 0x81000000 as the CONFIG_SYS_TEXT_BASE and not
> > > > > 0x81000100
> > > > > correct?
> > > > >
> > > > > > >
> > > > > > > /dts-v1/;
> > > > > > >
> > > > > > > / {
> > > > > > >     description = "Chrome OS nyan u-boot chain boot
> > > > > > > method";
> > > > > > >     #address-cells = <1>;
> > > > > > >     images {
> > > > > > >         kernel at 1{
> > > > > > >
> > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > On May 1, 2017 12:11 PM, "Matthew Gorski" <
> > > > > >
> > > > > > matt.gorski at gmail.com>
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chr
> > > > > > > > > > > > > omium.org>
> > > > > >
> > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hi Matthew,
> > > > > > > > > > > > >
> > > > > > > > > > > > > On 1 May 2017 at 09:37, Matthew Gorski <matt.go
> > > > > > > > > > > > > rski at gmail.com>
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > Thanks for the reply Simon.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I have been trying to find the System.map for
> > > > > > > > > > > > > > depthcharge to
> > > > > >
> > > > > > see
> > > > > > > > > > > > > > the
> > > > > > > > > > > > > > kernel
> > > > > > > > > > > > > > load address but I am unable to find
> > > > > > > > > > > > > > anything.  I have tried
> > > > > > > > > > > > > > multiple
> > > > > > > > > > > > > > CONFIG_SYS_TEXT_BASE settings with no luck.
> > > > > > > > > > > > >
> > > > > > > > > > > > > How did you choose what to use? Also note that
> > > > > > > > > > > > > Tegra uses SPL
> > > > > >
> > > > > > to
> > > > > > > > > > > > > start, so you may need to adjust
> > > > > > > > > > > > > CONFIG_SPL_TEXT_BASE instead.
> > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I am creating my sdcard with a standard linux
> > > > > > > > > > > > > > (Linux for
> > > > > >
> > > > > > Tegra)
> > > > > > > > > > > > > > rootfs:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Did these instructions come from a web site
> > > > > > > > > > > > > somewhere?
> > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Partition an SD card
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > sudo cgpt create <MMC BLOCK DEVICE>
> > > > > > > > > > > > > > sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t
> > > > > > > > > > > > > > kernel <MMC BLOCK
> > > > > > > > > > > > > > DEVICE>
> > > > > > > > > > > > > > # 16
> > > > > > > > > > > > > > MB
> > > > > > > > > > > > > > kernel image partition
> > > > > > > > > > > > > > sudo cgpt add -b 32802 -s <ROOT PARTITION
> > > > > > > > > > > > > > SIZE in 512B
> > > > > >
> > > > > > sectors>
> > > > > > > > > > > > > > -t
> > > > > > > > > > > > > > rootfs
> > > > > > > > > > > > > > <MMC BLOCK DEVICE>
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > cgpt doesn't seem to create a protective MBR.
> > > > > > > > > > > > > > If one is not
> > > > > > > > > > > > > > already
> > > > > > > > > > > > > > in
> > > > > > > > > > > > > > place, it can be created with:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > sudo gdisk <MMC BLOCK DEVICE> # and enter
> > > > > > > > > > > > > > command w
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Copy data to the SD card
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > sudo dd if=./kernelpart.bin of=<MMC BLOCK
> > > > > > > > > > > > > > DEVICE>p1
> > > > > > > > > > > > > > sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
> > > > > > > > > > > > > > sudo mount <MMC BLOCK DEVICE>p2 /mnt/
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > How are you actually making it boot? Is this in
> > > > > > > > > > > > > dev mode with
> > > > > >
> > > > > > USB
> > > > > > > > > > > > > boot
> > > > > > > > > > > > > enabled and pressing Ctrl-U?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Also, as this is a mailing list, please avoid
> > > > > > > > > > > > > top-posting.
> > > > > > > > > > > > >
> > > > > > > > > > > > > - Simon
> > > > > > > > > > > > >
> > > > > > > > > > > > > I am using chained boot to test uboot as a FIT
> > > > > > > > > > > > > image so I I
> > > > > >
> > > > > > don't
> > > > > > > > > > > > > have to
> > > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
> > > > > > > > > > > > > need to be
> > > > > >
> > > > > > adjusted
> > > > > > > > > > > > > for
> > > > > > > > > > > > > chained boot?
> > > > > > > > > > > > >
> > > > > > > > > > > > > I am using instructions to boot Linux for Tegra
> > > > > > > > > > > > > from
> > > > > >
> > > > > > sdcard/USB in
> > > > > > > > > > > > > developer
> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
> > > > > > > > > > > > >
> > > > > > > > > > > > > What mainline branch should I try?
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Mon, May 1, 2017 at 11:14 AM, Simon Glass
> > > > > > > > > > > > > > <
> > > > > >
> > > > > > sjg at chromium.org>
> > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Hi Matthew,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On 1 May 2017 at 08:43, Matthew Gorski <
> > > > > >
> > > > > > matt.gorski at gmail.com>
> > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > I am porting u-boot to nyan_big and need
> > > > > > > > > > > > > > > > some input.  I
> > > > > >
> > > > > > have
> > > > > > > > > > > > > > > > been
> > > > > > > > > > > > > > > > searching
> > > > > > > > > > > > > > > > high and low and found this thread here:
> > > > > > > > > > > > > > > > [U-Boot] [PATCH
> > > > > >
> > > > > > 0/20]
> > > > > > > > > > > > > > > > tegra:
> > > > > > > > > > > > > > > > Expand
> > > > > > > > > > > > > > > > Nyan-big support
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >  https://lists.denx.de/pipermail/u-boot/2
> > > > > > > > > > > > > > > > 015-March/209530.
> > > > > >
> > > > > > html
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I have tried to build u-boot with the
> > > > > > > > > > > > > > > > branch here:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > https://git.collabora.com/cgit
> > > > > >
> > > > > > /user/tomeu/u-boot.git/commit/?h=nyan-big
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > and also the official chromium next
> > > > > > > > > > > > > > > > branch
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Have you tried mainline U-Boot? It already
> > > > > > > > > > > > > > > supports nyan-big.
> > > > > > > > > > > > > > > I'm
> > > > > > > > > > > > > > > not
> > > > > > > > > > > > > > > sure about the situation with the
> > > > > > > > > > > > > > > downstream trees.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I followed building instructions here:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > https://www.chromium.org/chrom
> > > > > >
> > > > > > ium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung
> > > > > > -arm-chromebook
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I build with these commands:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > mkimage -e 0x81000100 -a 0x81000100 -f
> > > > > > > > > > > > > > > > kernel-big.its
> > > > > > > > > > > > > > > > kernel-u-boot
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > (with and without the load address
> > > > > > > > > > > > > > > > setting)
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > vbutil_kernel --arch arm --pack
> > > > > > > > > > > > > > > > kernel.bin --keyblock
> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kernel.keyblock
> > > > > > > > > > > > > > > > --signprivate
> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kernel_data_key.
> > > > > > > > > > > > > > > > vbprivk
> > > > > >
> > > > > > --version 1
> > > > > > > > > > > > > > > > --config
> > > > > > > > > > > > > > > > dummy.txt --vmlinuz kernel-u-boot --
> > > > > > > > > > > > > > > > bootloader dummy.txt
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > I have had numerous failed attempts to
> > > > > > > > > > > > > > > > boot uboot from
> > > > > >
> > > > > > sdcard
> > > > > > > > > > > > > > > > mmcblk1p1
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Any help is appreciated I have only
> > > > > > > > > > > > > > > > gotten a blank screen
> > > > > > > > > > > > > > > > after
> > > > > > > > > > > > > > > > weeks
> > > > > > > > > > > > > > > > of
> > > > > > > > > > > > > > > > flashing.  I can boot custom v3.10
> > > > > > > > > > > > > > > > kernels so I assume I am
> > > > > > > > > > > > > > > > using
> > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > correct building procedure.  Thanks in
> > > > > > > > > > > > > > > > advance for help
> > > > > >
> > > > > > from
> > > > > > > > > > > > > > > > the
> > > > > > > > > > > > > > > > u-boot
> > > > > > > > > > > > > > > > community.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > It is possible that it needs a particular
> > > > > > > > > > > > > > > address due to
> > > > > > > > > > > > > > > limitations
> > > > > > > > > > > > > > > in the FIT support on Nyan. I'm not sure
> > > > > > > > > > > > > > > what it is but
> > > > > >
> > > > > > might be
> > > > > > > > > > > > > > > able
> > > > > > > > > > > > > > > to take a look at some point.
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > How are you building your SD card? Are you
> > > > > > > > > > > > > > > following some
> > > > > > > > > > > > > > > instructions
> > > > > > > > > > > > > > > from somewhere?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Regards,
> > > > > > > > > > > > > > > Simon
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > >
> > > > _______________________________________________
> > > > U-Boot mailing list
> > > > U-Boot at lists.denx.de
> > > > https://lists.denx.de/listinfo/u-boot
>
> --
> Sjoerd Simons
> Collabora Ltd.
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

On Tue, May 2, 2017 at 9:25 AM, Matthew Gorski <matt.gorski@gmail.com>
wrote:

>
>
> On Tue, May 2, 2017 at 2:54 AM, Sjoerd Simons <
> sjoerd.simons at collabora.co.uk> wrote:
>
>> On Tue, 2017-05-02 at 08:42 +0200, Tomeu Vizoso wrote:
>> > On 2 May 2017 at 08:40, Tomeu Vizoso <tomeu@tomeuvizoso.net> wrote:
>> > > On 2 May 2017 at 03:19, Matthew Gorski <matt.gorski@gmail.com>
>> > > wrote:
>> > > > Seems if you change the FIT description from anything but
>> > > >
>> > > > "description = "Chrome OS kernel image with one or more FDT
>> > > > blobs";"
>> > > >
>> > > > the kernel wont load. So this issue has to be in the kernel-
>> > > > big.its
>> > > > <https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel
>> > > > -big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923>
>> > > >
>> > > > https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel-
>> > > > big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923
>> > > >
>> > > > We may just need a proper working .its for nyan
>> > >
>> > > Hi Matthew,
>> > >
>> > > it has been quite a while, but I remember that if we only tried
>> > > chainloading U-Boot was because the goal was to integrate these
>> > > machines in our LAVA lab, which to date doesn't support Depthcharge
>> > > (though I hope this will change once I get back some time).
>> > >
>> > > I cannot remember how the correct position of the kernel within the
>> > > FIT image was calculated, but it definitely involved looking at the
>> > > depthcharge sources.
>> >
>> > Actually, I have grepped my IRC logs and turns out that we need for
>> > the start of U-Boot's code to be aligned to 64kB.
>>
>> Yup, U-boot both needs to be properly aligned and know its text base
>> address.
>>
>> So the calculation we did was basically look at depthcharge where in
>> memory the FIT image gets loaded, determine a suitable load address
>> after that (e.g fit load + 64k), configure that in u-boot and then add
>> enough padding in the fit image itself such that the u-boot code starts
>> at the determined address in memory by putting in just the right amount
>> of padding ;).
>>
>> It is rather ugly, but it does allow running u-boot without the need to
>> change the firmware in flash.
>>
>
> Thank You Tomeu, Sjoerd and Simon for taking the time to chime in on an
> old but interesting topic.
>
> I believe I have enough info from you all to get this figured out now.
>
> Since depthcharch loads the FIT image at 0x81000000
> https://chromium.googlesource.com/chromiumos/platform/
> depthcharge/+/master/board/nyan_big/defconfig#11
>
> I need to determine a suitable load address e.g fit load + 64k
>
> So 81000000 + 64k.
>
> One thing I am not certain about is adding the padding to the FIT .its
> config. How is this done?
>
> description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE IMAGE
> STARTS AT THE RIGHT OFFSET";
>

Seems if I use the description "description = "U-Boot + FDT --------- THIS
PADDING IS NEEDED SO THE IMAGE STARTS AT THE RIGHT OFFSET"; "

I get a blank display that shows no signs of loading uboot BUT if I use:

description = "Chrome OS kernel image with one or more FDT blobs";

Nyan tries to load something because the display flashes like a normal
bootup but immediately reboots into chromeos usb/sdcard recovery.

So the hack in the the collabora uboot kernel-big.its doesnt seem to work
anymore unless the padding is messing with the load address.

I am using mainline uboot with CONFIG_SYS_TEXT_BASE 0x81000100 should this
be changed?

Also i am trying to figure out how padding is calculated in a fit image and
this is confusing.  Is the padding the actual description length?

>
>
>> > Thus the padding.
>> >
>> > Regards,
>> >
>> > Tomeu
>> >
>> > > But I do think to remember that it was only an issue once U-Boot
>> > > tried
>> > > to relocate itself.
>> > >
>> > > I don't see any reason why my old branch wouldn't work today on
>> > > your
>> > > machine, other than maybe your hw is a different revision with a
>> > > memory chip that wasn't supported back then? I also don't see why
>> > > mainline wouldn't work, provided you have that hack in the ITS.
>> > >
>> > > I'm adding Sjoerd to CC in case he remembers.
>> > >
>> > > Good luck,
>> > >
>> > > Tomeu
>> > >
>> > > > On Mon, May 1, 2017 at 7:45 PM, Matthew Gorski <matt.gorski@gmail
>> > > > .com>
>> > > > wrote:
>> > > >
>> > > > >
>> > > > >
>> > > > > On Mon, May 1, 2017 at 7:34 PM, Simon Glass <sjg@chromium.org>
>> > > > > wrote:
>> > > > >
>> > > > > > Hi Matthew,
>> > > > > >
>> > > > > > On 1 May 2017 at 17:27, Matthew Gorski <matt.gorski@gmail.com
>> > > > > > > wrote:
>> > > > > > >
>> > > > > > >
>> > > > > > > On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.o
>> > > > > > > rg> wrote:
>> > > > > > > >
>> > > > > > > > Hi Matthew,
>> > > > > > > >
>> > > > > > > > On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail
>> > > > > > > > .com> wrote:
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromi
>> > > > > > > > > um.org>
>> > > > > >
>> > > > > > wrote:
>> > > > > > > > > >
>> > > > > > > > > > Hi Matthew,
>> > > > > > > > > >
>> > > > > > > > > > On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@g
>> > > > > > > > > > mail.com>
>> > > > > >
>> > > > > > wrote:
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@ch
>> > > > > > > > > > > romium.org>
>> > > > > >
>> > > > > > wrote:
>> > > > > > > > > > > >
>> > > > > > > > > > > > Hi Matthew,
>> > > > > > > > > > > >
>> > > > > > > > > > > > On 1 May 2017 at 10:40, Matthew Gorski <matt.gors
>> > > > > > > > > > > > ki at gmail.com>
>> > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > Let me repost this to the bottom.  New to the
>> > > > > > > > > > > > > mailing list ;)
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > I am using chained boot to test uboot as a FIT
>> > > > > > > > > > > > > image so I I
>> > > > > >
>> > > > > > don't
>> > > > > > > > > > > > > have to
>> > > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
>> > > > > > > > > > > > > need to be
>> > > > > >
>> > > > > > adjusted
>> > > > > > > > > > > > > for
>> > > > > > > > > > > > > chained boot?
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > I am using instructions to boot Linux for Tegra
>> > > > > > > > > > > > > from
>> > > > > >
>> > > > > > sdcard/USB in
>> > > > > > > > > > > > > developer
>> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > What mainline branch should I try?
>> > > > > > > > > > > >
>> > > > > > > > > > > > There's only one mainline, here:
>> > > > > > > > > > > > http://git.denx.de/?p=u-boot.git;a=summary
>> > > > > > > > > > > >
>> > > > > > > > > > > > There are various custodian branches but I don't
>> > > > > > > > > > > > believe the
>> > > > > >
>> > > > > > tegra
>> > > > > > > > > > > > one
>> > > > > > > > > > > > has anything different from mainline at present.
>> > > > > > > > > > > >
>> > > > > > > > > > > > - Simon
>> > > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > I will give mainline a try with:
>> > > > > > > > > > >
>> > > > > > > > > > > CONFIG_SYS_TEXT_BASE 0x8010E000
>> > > > > > > > > > > and
>> > > > > > > > > > >
>> > > > > > > > > > > CONFIG_SPL_TEXT_BASE 0x80108000
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > I know I will also need:
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > CONFIG_DISPLAY_PORT=y
>> > > > > > > > > >
>> > > > > > > > > > Do you mean CONFIG_DISPLAY? If so, it is already
>> > > > > > > > > > defined.
>> > > > > > > > > >
>> > > > > > > > > > > CONFIG_VIDEO_TEGRA124=y
>> > > > > > > > > >
>> > > > > > > > > > That is defined in mainline
>> > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > for the console to display command prompt.
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > The FIT config I am using is from
>> > > > > > > > > > >
>> > > > > > > > > > > here:https://git.collabora.com/cgit/user/tomeu/u-bo
>> > > > > > > > > > > ot.git/
>> > > > > >
>> > > > > > commit/?h=nyan-big
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > Do I need to adjust:
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > >             load = <0>;
>> > > > > > > > > > >             entry = <0>;
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > /dts-v1/;
>> > > > > > > > > > >
>> > > > > > > > > > > / {
>> > > > > > > > > > >     description = "U-Boot + FDT --------- THIS
>> > > > > > > > > > > PADDING IS NEEDED
>> > > > > >
>> > > > > > SO
>> > > > > > > > > > > THE
>> > > > > > > > > > > IMAGE STARTS AT THE RIGHT OFFSET";
>> > > > > > > > > >
>> > > > > > > > > > Perhaps you need to adjust this? How was the length
>> > > > > > > > > > of it
>> > > > > >
>> > > > > > calcualted?
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > I am really not sure how the padding was calculated.  I
>> > > > > > > > > just assumed
>> > > > > > > > > this
>> > > > > > > > > kernel-big.its FIT config was correct for nyan_big.  I
>> > > > > > > > > will try
>> > > > > >
>> > > > > > using my
>> > > > > > > > > working linux kernel fit config.
>> > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > > >     #address-cells = <1>;
>> > > > > > > > > > >     images {
>> > > > > > > > > > >         kernel at 1{
>> > > > > > > > > > >             description = "kernel";
>> > > > > > > > > > >             data = /incbin/("u-boot-dtb.bin");
>> > > > > > > > > > >             type = "kernel_noload";
>> > > > > > > > > > >             arch = "arm";
>> > > > > > > > > > >             os = "linux";
>> > > > > > > > > > >             compression = "none";
>> > > > > > > > > > >             load = <0>;
>> > > > > > > > > > >             entry = <0>;
>> > > > > > > > > > >         };
>> > > > > > > > > > >         fdt at 1{
>> > > > > > > > > > >             description = "tegra124-nyan-big.dtb";
>> > > > > > > > > > >             data = /incbin/("dts/dt.dtb");
>> > > > > > > > > > >             type = "flat_dt";
>> > > > > > > > > > >             arch = "arm";
>> > > > > > > > > > >             compression = "none";
>> > > > > > > > > > >             hash at 1{
>> > > > > > > > > > >                 algo = "sha1";
>> > > > > > > > > > >             };
>> > > > > > > > > > >         };
>> > > > > > > > > > >     };
>> > > > > > > > > > >     configurations {
>> > > > > > > > > > >         default = "conf at 1";
>> > > > > > > > > > >         conf at 1{
>> > > > > > > > > > >             kernel = "kernel at 1";
>> > > > > > > > > > >             fdt = "fdt at 1";
>> > > > > > > > > > >         };
>> > > > > > > > > > >     };
>> > > > > > > > > > > };
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > please let me know if I should also adjust the SPL
>> > > > > > > > > > > CONFIG even
>> > > > > >
>> > > > > > though
>> > > > > > > > > > > I
>> > > > > > > > > > > am chainbooting uboot:
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > https://www.chromium.org/chromium-os/firmware-porti
>> > > > > > > > > > > ng-guide/
>> > > > > >
>> > > > > > using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing
>> > > > > > -nv-U-Boot-chained-U-Boot-method-
>> > > > > > > > > >
>> > > > > > > > > > This is exynos, where we booted directly into U-Boot.
>> > > > > > > > > > Actually I'm
>> > > > > > > > > > wondering we should boot directly into U-Boot
>> > > > > > > > > > (instead of SPL) on
>> > > > > >
>> > > > > > nyan
>> > > > > > > > > > also. Perhaps someone at collabora would know? Did
>> > > > > > > > > > you search the
>> > > > > > > > > > mailing list?
>> > > > > > > > > >
>> > > > > > > > > > Regards,
>> > > > > > > > > > Simon
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > I have not searched the mailing list.  What should I
>> > > > > > > > > search for?
>> > > > > > > > > Booting
>> > > > > > > > > nyan to u-boot directly bypassing SPL?
>> > > > > > > >
>> > > > > > > > Here are two subjects to search for:
>> > > > > > > >
>> > > > > > > > Veyron-speedy u-boot
>> > > > > > > > [PATCH 0/20] tegra: Expand Nyan-big support
>> > > > > > > >
>> > > > > > > > Regards,
>> > > > > > > > Simon
>> > > > > > >
>> > > > > > >
>> > > > > > > Very odd if I do not use "#address-cells = <1>;" the
>> > > > > > > display flashes and
>> > > > > > > reboots into recovery but if I do use #address-cells = <1>;
>> > > > > > > in my FIT
>> > > > > >
>> > > > > > config
>> > > > > > > I get a blank screen
>> > > > > > > so something is working when not using the padding.
>> > > > > >
>> > > > > > If you figure out where u-boot-dtb.bin needs to start by
>> > > > > > looking at
>> > > > > > depthcharge or where the kernel starts, then you can figure
>> > > > > > out how
>> > > > > > long the padding needs to be at the start of the FIT. Rather
>> > > > > > than
>> > > > > > guessing...!
>> > > > > >
>> > > > > > - Simon
>> > > > > >
>> > > > > >  Okay so depthcharge starts at 0x81000000 from here:
>> > > > >
>> > > > > https://chromium.googlesource.com/chromiumos/platform/
>> > > > > depthcharge/+/master/board/nyan_big/defconfig#11
>> > > > >
>> > > > > In my System.map for u-boot after building says the start is:
>> > > > > 81000100 T __image_copy_start
>> > > > > 81000100 T _start
>> > > > >
>> > > > > Hence the define CONFIG_SYS_TEXT_BASE 0x81000100
>> > > > >
>> > > > > So you say use 0x81000000 as the CONFIG_SYS_TEXT_BASE and not
>> > > > > 0x81000100
>> > > > > correct?
>> > > > >
>> > > > > > >
>> > > > > > > /dts-v1/;
>> > > > > > >
>> > > > > > > / {
>> > > > > > >     description = "Chrome OS nyan u-boot chain boot
>> > > > > > > method";
>> > > > > > >     #address-cells = <1>;
>> > > > > > >     images {
>> > > > > > >         kernel at 1{
>> > > > > > >
>> > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > On May 1, 2017 12:11 PM, "Matthew Gorski" <
>> > > > > >
>> > > > > > matt.gorski at gmail.com>
>> > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chr
>> > > > > > > > > > > > > omium.org>
>> > > > > >
>> > > > > > wrote:
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > Hi Matthew,
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > On 1 May 2017 at 09:37, Matthew Gorski <matt.go
>> > > > > > > > > > > > > rski at gmail.com>
>> > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > Thanks for the reply Simon.
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > I have been trying to find the System.map for
>> > > > > > > > > > > > > > depthcharge to
>> > > > > >
>> > > > > > see
>> > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > kernel
>> > > > > > > > > > > > > > load address but I am unable to find
>> > > > > > > > > > > > > > anything.  I have tried
>> > > > > > > > > > > > > > multiple
>> > > > > > > > > > > > > > CONFIG_SYS_TEXT_BASE settings with no luck.
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > How did you choose what to use? Also note that
>> > > > > > > > > > > > > Tegra uses SPL
>> > > > > >
>> > > > > > to
>> > > > > > > > > > > > > start, so you may need to adjust
>> > > > > > > > > > > > > CONFIG_SPL_TEXT_BASE instead.
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > I am creating my sdcard with a standard linux
>> > > > > > > > > > > > > > (Linux for
>> > > > > >
>> > > > > > Tegra)
>> > > > > > > > > > > > > > rootfs:
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > Did these instructions come from a web site
>> > > > > > > > > > > > > somewhere?
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > Partition an SD card
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > sudo cgpt create <MMC BLOCK DEVICE>
>> > > > > > > > > > > > > > sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t
>> > > > > > > > > > > > > > kernel <MMC BLOCK
>> > > > > > > > > > > > > > DEVICE>
>> > > > > > > > > > > > > > # 16
>> > > > > > > > > > > > > > MB
>> > > > > > > > > > > > > > kernel image partition
>> > > > > > > > > > > > > > sudo cgpt add -b 32802 -s <ROOT PARTITION
>> > > > > > > > > > > > > > SIZE in 512B
>> > > > > >
>> > > > > > sectors>
>> > > > > > > > > > > > > > -t
>> > > > > > > > > > > > > > rootfs
>> > > > > > > > > > > > > > <MMC BLOCK DEVICE>
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > cgpt doesn't seem to create a protective MBR.
>> > > > > > > > > > > > > > If one is not
>> > > > > > > > > > > > > > already
>> > > > > > > > > > > > > > in
>> > > > > > > > > > > > > > place, it can be created with:
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > sudo gdisk <MMC BLOCK DEVICE> # and enter
>> > > > > > > > > > > > > > command w
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > Copy data to the SD card
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > sudo dd if=./kernelpart.bin of=<MMC BLOCK
>> > > > > > > > > > > > > > DEVICE>p1
>> > > > > > > > > > > > > > sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>> > > > > > > > > > > > > > sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > How are you actually making it boot? Is this in
>> > > > > > > > > > > > > dev mode with
>> > > > > >
>> > > > > > USB
>> > > > > > > > > > > > > boot
>> > > > > > > > > > > > > enabled and pressing Ctrl-U?
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > Also, as this is a mailing list, please avoid
>> > > > > > > > > > > > > top-posting.
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > - Simon
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > I am using chained boot to test uboot as a FIT
>> > > > > > > > > > > > > image so I I
>> > > > > >
>> > > > > > don't
>> > > > > > > > > > > > > have to
>> > > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
>> > > > > > > > > > > > > need to be
>> > > > > >
>> > > > > > adjusted
>> > > > > > > > > > > > > for
>> > > > > > > > > > > > > chained boot?
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > I am using instructions to boot Linux for Tegra
>> > > > > > > > > > > > > from
>> > > > > >
>> > > > > > sdcard/USB in
>> > > > > > > > > > > > > developer
>> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > What mainline branch should I try?
>> > > > > > > > > > > > >
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > On Mon, May 1, 2017 at 11:14 AM, Simon Glass
>> > > > > > > > > > > > > > <
>> > > > > >
>> > > > > > sjg at chromium.org>
>> > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > Hi Matthew,
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > On 1 May 2017 at 08:43, Matthew Gorski <
>> > > > > >
>> > > > > > matt.gorski at gmail.com>
>> > > > > > > > > > > > > > > wrote:
>> > > > > > > > > > > > > > > > I am porting u-boot to nyan_big and need
>> > > > > > > > > > > > > > > > some input.  I
>> > > > > >
>> > > > > > have
>> > > > > > > > > > > > > > > > been
>> > > > > > > > > > > > > > > > searching
>> > > > > > > > > > > > > > > > high and low and found this thread here:
>> > > > > > > > > > > > > > > > [U-Boot] [PATCH
>> > > > > >
>> > > > > > 0/20]
>> > > > > > > > > > > > > > > > tegra:
>> > > > > > > > > > > > > > > > Expand
>> > > > > > > > > > > > > > > > Nyan-big support
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > >  https://lists.denx.de/pipermail/u-boot/2
>> > > > > > > > > > > > > > > > 015-March/209530.
>> > > > > >
>> > > > > > html
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > I have tried to build u-boot with the
>> > > > > > > > > > > > > > > > branch here:
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > https://git.collabora.com/cgit
>> > > > > >
>> > > > > > /user/tomeu/u-boot.git/commit/?h=nyan-big
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > and also the official chromium next
>> > > > > > > > > > > > > > > > branch
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > Have you tried mainline U-Boot? It already
>> > > > > > > > > > > > > > > supports nyan-big.
>> > > > > > > > > > > > > > > I'm
>> > > > > > > > > > > > > > > not
>> > > > > > > > > > > > > > > sure about the situation with the
>> > > > > > > > > > > > > > > downstream trees.
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > I followed building instructions here:
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > https://www.chromium.org/chrom
>> > > > > >
>> > > > > > ium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung
>> > > > > > -arm-chromebook
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > I build with these commands:
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > mkimage -e 0x81000100 -a 0x81000100 -f
>> > > > > > > > > > > > > > > > kernel-big.its
>> > > > > > > > > > > > > > > > kernel-u-boot
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > (with and without the load address
>> > > > > > > > > > > > > > > > setting)
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > vbutil_kernel --arch arm --pack
>> > > > > > > > > > > > > > > > kernel.bin --keyblock
>> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kernel.keyblock
>> > > > > > > > > > > > > > > > --signprivate
>> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kernel_data_key.
>> > > > > > > > > > > > > > > > vbprivk
>> > > > > >
>> > > > > > --version 1
>> > > > > > > > > > > > > > > > --config
>> > > > > > > > > > > > > > > > dummy.txt --vmlinuz kernel-u-boot --
>> > > > > > > > > > > > > > > > bootloader dummy.txt
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > I have had numerous failed attempts to
>> > > > > > > > > > > > > > > > boot uboot from
>> > > > > >
>> > > > > > sdcard
>> > > > > > > > > > > > > > > > mmcblk1p1
>> > > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > > Any help is appreciated I have only
>> > > > > > > > > > > > > > > > gotten a blank screen
>> > > > > > > > > > > > > > > > after
>> > > > > > > > > > > > > > > > weeks
>> > > > > > > > > > > > > > > > of
>> > > > > > > > > > > > > > > > flashing.  I can boot custom v3.10
>> > > > > > > > > > > > > > > > kernels so I assume I am
>> > > > > > > > > > > > > > > > using
>> > > > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > > > correct building procedure.  Thanks in
>> > > > > > > > > > > > > > > > advance for help
>> > > > > >
>> > > > > > from
>> > > > > > > > > > > > > > > > the
>> > > > > > > > > > > > > > > > u-boot
>> > > > > > > > > > > > > > > > community.
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > It is possible that it needs a particular
>> > > > > > > > > > > > > > > address due to
>> > > > > > > > > > > > > > > limitations
>> > > > > > > > > > > > > > > in the FIT support on Nyan. I'm not sure
>> > > > > > > > > > > > > > > what it is but
>> > > > > >
>> > > > > > might be
>> > > > > > > > > > > > > > > able
>> > > > > > > > > > > > > > > to take a look at some point.
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > How are you building your SD card? Are you
>> > > > > > > > > > > > > > > following some
>> > > > > > > > > > > > > > > instructions
>> > > > > > > > > > > > > > > from somewhere?
>> > > > > > > > > > > > > > >
>> > > > > > > > > > > > > > > Regards,
>> > > > > > > > > > > > > > > Simon
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > >
>> > > > > > > > > > > > >
>> > > > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > >
>> > > > >
>> > > >
>> > > > _______________________________________________
>> > > > U-Boot mailing list
>> > > > U-Boot at lists.denx.de
>> > > > https://lists.denx.de/listinfo/u-boot
>>
>> --
>> Sjoerd Simons
>> Collabora Ltd.
>>
>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

I have yet to produce a u-boot command prompt.  I can get the display to
flash using u-boot mainline with 0x81000100 as the SYS_TEXT_BASE and using:

 description = "Chrome OS kernel image with one or more FDT blobs";

but the boot process forces a reboot into recovery.

If I use:

description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE IMAGE
STARTS AT THE RIGHT OFFSET";
Produces a blank screen with the exact u-boot.bin

I hope someone can confirm nyan can chainboot u-boot and possibly post what
the used for their FIT its config.  Thanks for all the help and guided
responses.

On Tue, May 2, 2017 at 11:34 AM, Matthew Gorski <matt.gorski@gmail.com>
wrote:

>
>
> On Tue, May 2, 2017 at 9:25 AM, Matthew Gorski <matt.gorski@gmail.com>
> wrote:
>
>>
>>
>> On Tue, May 2, 2017 at 2:54 AM, Sjoerd Simons <
>> sjoerd.simons at collabora.co.uk> wrote:
>>
>>> On Tue, 2017-05-02 at 08:42 +0200, Tomeu Vizoso wrote:
>>> > On 2 May 2017 at 08:40, Tomeu Vizoso <tomeu@tomeuvizoso.net> wrote:
>>> > > On 2 May 2017 at 03:19, Matthew Gorski <matt.gorski@gmail.com>
>>> > > wrote:
>>> > > > Seems if you change the FIT description from anything but
>>> > > >
>>> > > > "description = "Chrome OS kernel image with one or more FDT
>>> > > > blobs";"
>>> > > >
>>> > > > the kernel wont load. So this issue has to be in the kernel-
>>> > > > big.its
>>> > > > <https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel
>>> > > > -big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923>
>>> > > >
>>> > > > https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel-
>>> > > > big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923
>>> > > >
>>> > > > We may just need a proper working .its for nyan
>>> > >
>>> > > Hi Matthew,
>>> > >
>>> > > it has been quite a while, but I remember that if we only tried
>>> > > chainloading U-Boot was because the goal was to integrate these
>>> > > machines in our LAVA lab, which to date doesn't support Depthcharge
>>> > > (though I hope this will change once I get back some time).
>>> > >
>>> > > I cannot remember how the correct position of the kernel within the
>>> > > FIT image was calculated, but it definitely involved looking at the
>>> > > depthcharge sources.
>>> >
>>> > Actually, I have grepped my IRC logs and turns out that we need for
>>> > the start of U-Boot's code to be aligned to 64kB.
>>>
>>> Yup, U-boot both needs to be properly aligned and know its text base
>>> address.
>>>
>>> So the calculation we did was basically look at depthcharge where in
>>> memory the FIT image gets loaded, determine a suitable load address
>>> after that (e.g fit load + 64k), configure that in u-boot and then add
>>> enough padding in the fit image itself such that the u-boot code starts
>>> at the determined address in memory by putting in just the right amount
>>> of padding ;).
>>>
>>> It is rather ugly, but it does allow running u-boot without the need to
>>> change the firmware in flash.
>>>
>>
>> Thank You Tomeu, Sjoerd and Simon for taking the time to chime in on an
>> old but interesting topic.
>>
>> I believe I have enough info from you all to get this figured out now.
>>
>> Since depthcharch loads the FIT image at 0x81000000
>> https://chromium.googlesource.com/chromiumos/platform/depthc
>> harge/+/master/board/nyan_big/defconfig#11
>>
>> I need to determine a suitable load address e.g fit load + 64k
>>
>> So 81000000 + 64k.
>>
>> One thing I am not certain about is adding the padding to the FIT .its
>> config. How is this done?
>>
>> description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE IMAGE
>> STARTS AT THE RIGHT OFFSET";
>>
>
> Seems if I use the description "description = "U-Boot + FDT --------- THIS
> PADDING IS NEEDED SO THE IMAGE STARTS AT THE RIGHT OFFSET"; "
>
> I get a blank display that shows no signs of loading uboot BUT if I use:
>
> description = "Chrome OS kernel image with one or more FDT blobs";
>
> Nyan tries to load something because the display flashes like a normal
> bootup but immediately reboots into chromeos usb/sdcard recovery.
>
> So the hack in the the collabora uboot kernel-big.its doesnt seem to work
> anymore unless the padding is messing with the load address.
>
> I am using mainline uboot with CONFIG_SYS_TEXT_BASE 0x81000100 should
> this be changed?
>
> Also i am trying to figure out how padding is calculated in a fit image
> and this is confusing.  Is the padding the actual description length?
>
>>
>>
>>> > Thus the padding.
>>> >
>>> > Regards,
>>> >
>>> > Tomeu
>>> >
>>> > > But I do think to remember that it was only an issue once U-Boot
>>> > > tried
>>> > > to relocate itself.
>>> > >
>>> > > I don't see any reason why my old branch wouldn't work today on
>>> > > your
>>> > > machine, other than maybe your hw is a different revision with a
>>> > > memory chip that wasn't supported back then? I also don't see why
>>> > > mainline wouldn't work, provided you have that hack in the ITS.
>>> > >
>>> > > I'm adding Sjoerd to CC in case he remembers.
>>> > >
>>> > > Good luck,
>>> > >
>>> > > Tomeu
>>> > >
>>> > > > On Mon, May 1, 2017 at 7:45 PM, Matthew Gorski <matt.gorski@gmail
>>> > > > .com>
>>> > > > wrote:
>>> > > >
>>> > > > >
>>> > > > >
>>> > > > > On Mon, May 1, 2017 at 7:34 PM, Simon Glass <sjg@chromium.org>
>>> > > > > wrote:
>>> > > > >
>>> > > > > > Hi Matthew,
>>> > > > > >
>>> > > > > > On 1 May 2017 at 17:27, Matthew Gorski <matt.gorski@gmail.com
>>> > > > > > > wrote:
>>> > > > > > >
>>> > > > > > >
>>> > > > > > > On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.o
>>> > > > > > > rg> wrote:
>>> > > > > > > >
>>> > > > > > > > Hi Matthew,
>>> > > > > > > >
>>> > > > > > > > On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail
>>> > > > > > > > .com> wrote:
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromi
>>> > > > > > > > > um.org>
>>> > > > > >
>>> > > > > > wrote:
>>> > > > > > > > > >
>>> > > > > > > > > > Hi Matthew,
>>> > > > > > > > > >
>>> > > > > > > > > > On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@g
>>> > > > > > > > > > mail.com>
>>> > > > > >
>>> > > > > > wrote:
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@ch
>>> > > > > > > > > > > romium.org>
>>> > > > > >
>>> > > > > > wrote:
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > Hi Matthew,
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > On 1 May 2017 at 10:40, Matthew Gorski <matt.gors
>>> > > > > > > > > > > > ki at gmail.com>
>>> > > > > > > > > > > > wrote:
>>> > > > > > > > > > > > > Let me repost this to the bottom.  New to the
>>> > > > > > > > > > > > > mailing list ;)
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > I am using chained boot to test uboot as a FIT
>>> > > > > > > > > > > > > image so I I
>>> > > > > >
>>> > > > > > don't
>>> > > > > > > > > > > > > have to
>>> > > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
>>> > > > > > > > > > > > > need to be
>>> > > > > >
>>> > > > > > adjusted
>>> > > > > > > > > > > > > for
>>> > > > > > > > > > > > > chained boot?
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > I am using instructions to boot Linux for Tegra
>>> > > > > > > > > > > > > from
>>> > > > > >
>>> > > > > > sdcard/USB in
>>> > > > > > > > > > > > > developer
>>> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > What mainline branch should I try?
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > There's only one mainline, here:
>>> > > > > > > > > > > > http://git.denx.de/?p=u-boot.git;a=summary
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > There are various custodian branches but I don't
>>> > > > > > > > > > > > believe the
>>> > > > > >
>>> > > > > > tegra
>>> > > > > > > > > > > > one
>>> > > > > > > > > > > > has anything different from mainline at present.
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > - Simon
>>> > > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > > I will give mainline a try with:
>>> > > > > > > > > > >
>>> > > > > > > > > > > CONFIG_SYS_TEXT_BASE 0x8010E000
>>> > > > > > > > > > > and
>>> > > > > > > > > > >
>>> > > > > > > > > > > CONFIG_SPL_TEXT_BASE 0x80108000
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > > I know I will also need:
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > > CONFIG_DISPLAY_PORT=y
>>> > > > > > > > > >
>>> > > > > > > > > > Do you mean CONFIG_DISPLAY? If so, it is already
>>> > > > > > > > > > defined.
>>> > > > > > > > > >
>>> > > > > > > > > > > CONFIG_VIDEO_TEGRA124=y
>>> > > > > > > > > >
>>> > > > > > > > > > That is defined in mainline
>>> > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > > for the console to display command prompt.
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > > The FIT config I am using is from
>>> > > > > > > > > > >
>>> > > > > > > > > > > here:https://git.collabora.com/cgit/user/tomeu/u-bo
>>> > > > > > > > > > > ot.git/
>>> > > > > >
>>> > > > > > commit/?h=nyan-big
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > > Do I need to adjust:
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > >             load = <0>;
>>> > > > > > > > > > >             entry = <0>;
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > > /dts-v1/;
>>> > > > > > > > > > >
>>> > > > > > > > > > > / {
>>> > > > > > > > > > >     description = "U-Boot + FDT --------- THIS
>>> > > > > > > > > > > PADDING IS NEEDED
>>> > > > > >
>>> > > > > > SO
>>> > > > > > > > > > > THE
>>> > > > > > > > > > > IMAGE STARTS AT THE RIGHT OFFSET";
>>> > > > > > > > > >
>>> > > > > > > > > > Perhaps you need to adjust this? How was the length
>>> > > > > > > > > > of it
>>> > > > > >
>>> > > > > > calcualted?
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > > I am really not sure how the padding was calculated.  I
>>> > > > > > > > > just assumed
>>> > > > > > > > > this
>>> > > > > > > > > kernel-big.its FIT config was correct for nyan_big.  I
>>> > > > > > > > > will try
>>> > > > > >
>>> > > > > > using my
>>> > > > > > > > > working linux kernel fit config.
>>> > > > > > > > > >
>>> > > > > > > > > >
>>> > > > > > > > > > >     #address-cells = <1>;
>>> > > > > > > > > > >     images {
>>> > > > > > > > > > >         kernel at 1{
>>> > > > > > > > > > >             description = "kernel";
>>> > > > > > > > > > >             data = /incbin/("u-boot-dtb.bin");
>>> > > > > > > > > > >             type = "kernel_noload";
>>> > > > > > > > > > >             arch = "arm";
>>> > > > > > > > > > >             os = "linux";
>>> > > > > > > > > > >             compression = "none";
>>> > > > > > > > > > >             load = <0>;
>>> > > > > > > > > > >             entry = <0>;
>>> > > > > > > > > > >         };
>>> > > > > > > > > > >         fdt at 1{
>>> > > > > > > > > > >             description = "tegra124-nyan-big.dtb";
>>> > > > > > > > > > >             data = /incbin/("dts/dt.dtb");
>>> > > > > > > > > > >             type = "flat_dt";
>>> > > > > > > > > > >             arch = "arm";
>>> > > > > > > > > > >             compression = "none";
>>> > > > > > > > > > >             hash at 1{
>>> > > > > > > > > > >                 algo = "sha1";
>>> > > > > > > > > > >             };
>>> > > > > > > > > > >         };
>>> > > > > > > > > > >     };
>>> > > > > > > > > > >     configurations {
>>> > > > > > > > > > >         default = "conf at 1";
>>> > > > > > > > > > >         conf at 1{
>>> > > > > > > > > > >             kernel = "kernel at 1";
>>> > > > > > > > > > >             fdt = "fdt at 1";
>>> > > > > > > > > > >         };
>>> > > > > > > > > > >     };
>>> > > > > > > > > > > };
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > > please let me know if I should also adjust the SPL
>>> > > > > > > > > > > CONFIG even
>>> > > > > >
>>> > > > > > though
>>> > > > > > > > > > > I
>>> > > > > > > > > > > am chainbooting uboot:
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > > https://www.chromium.org/chromium-os/firmware-porti
>>> > > > > > > > > > > ng-guide/
>>> > > > > >
>>> > > > > > using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing
>>> > > > > > -nv-U-Boot-chained-U-Boot-method-
>>> > > > > > > > > >
>>> > > > > > > > > > This is exynos, where we booted directly into U-Boot.
>>> > > > > > > > > > Actually I'm
>>> > > > > > > > > > wondering we should boot directly into U-Boot
>>> > > > > > > > > > (instead of SPL) on
>>> > > > > >
>>> > > > > > nyan
>>> > > > > > > > > > also. Perhaps someone at collabora would know? Did
>>> > > > > > > > > > you search the
>>> > > > > > > > > > mailing list?
>>> > > > > > > > > >
>>> > > > > > > > > > Regards,
>>> > > > > > > > > > Simon
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > > I have not searched the mailing list.  What should I
>>> > > > > > > > > search for?
>>> > > > > > > > > Booting
>>> > > > > > > > > nyan to u-boot directly bypassing SPL?
>>> > > > > > > >
>>> > > > > > > > Here are two subjects to search for:
>>> > > > > > > >
>>> > > > > > > > Veyron-speedy u-boot
>>> > > > > > > > [PATCH 0/20] tegra: Expand Nyan-big support
>>> > > > > > > >
>>> > > > > > > > Regards,
>>> > > > > > > > Simon
>>> > > > > > >
>>> > > > > > >
>>> > > > > > > Very odd if I do not use "#address-cells = <1>;" the
>>> > > > > > > display flashes and
>>> > > > > > > reboots into recovery but if I do use #address-cells = <1>;
>>> > > > > > > in my FIT
>>> > > > > >
>>> > > > > > config
>>> > > > > > > I get a blank screen
>>> > > > > > > so something is working when not using the padding.
>>> > > > > >
>>> > > > > > If you figure out where u-boot-dtb.bin needs to start by
>>> > > > > > looking at
>>> > > > > > depthcharge or where the kernel starts, then you can figure
>>> > > > > > out how
>>> > > > > > long the padding needs to be at the start of the FIT. Rather
>>> > > > > > than
>>> > > > > > guessing...!
>>> > > > > >
>>> > > > > > - Simon
>>> > > > > >
>>> > > > > >  Okay so depthcharge starts at 0x81000000 from here:
>>> > > > >
>>> > > > > https://chromium.googlesource.com/chromiumos/platform/
>>> > > > > depthcharge/+/master/board/nyan_big/defconfig#11
>>> > > > >
>>> > > > > In my System.map for u-boot after building says the start is:
>>> > > > > 81000100 T __image_copy_start
>>> > > > > 81000100 T _start
>>> > > > >
>>> > > > > Hence the define CONFIG_SYS_TEXT_BASE 0x81000100
>>> > > > >
>>> > > > > So you say use 0x81000000 as the CONFIG_SYS_TEXT_BASE and not
>>> > > > > 0x81000100
>>> > > > > correct?
>>> > > > >
>>> > > > > > >
>>> > > > > > > /dts-v1/;
>>> > > > > > >
>>> > > > > > > / {
>>> > > > > > >     description = "Chrome OS nyan u-boot chain boot
>>> > > > > > > method";
>>> > > > > > >     #address-cells = <1>;
>>> > > > > > >     images {
>>> > > > > > >         kernel at 1{
>>> > > > > > >
>>> > > > > > > >
>>> > > > > > > > > >
>>> > > > > > > > > >
>>> > > > > > > > > > > >
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > On May 1, 2017 12:11 PM, "Matthew Gorski" <
>>> > > > > >
>>> > > > > > matt.gorski at gmail.com>
>>> > > > > > > > > > > > > wrote:
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chr
>>> > > > > > > > > > > > > omium.org>
>>> > > > > >
>>> > > > > > wrote:
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > Hi Matthew,
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > On 1 May 2017 at 09:37, Matthew Gorski <matt.go
>>> > > > > > > > > > > > > rski at gmail.com>
>>> > > > > > > > > > > > > wrote:
>>> > > > > > > > > > > > > > Thanks for the reply Simon.
>>> > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > I have been trying to find the System.map for
>>> > > > > > > > > > > > > > depthcharge to
>>> > > > > >
>>> > > > > > see
>>> > > > > > > > > > > > > > the
>>> > > > > > > > > > > > > > kernel
>>> > > > > > > > > > > > > > load address but I am unable to find
>>> > > > > > > > > > > > > > anything.  I have tried
>>> > > > > > > > > > > > > > multiple
>>> > > > > > > > > > > > > > CONFIG_SYS_TEXT_BASE settings with no luck.
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > How did you choose what to use? Also note that
>>> > > > > > > > > > > > > Tegra uses SPL
>>> > > > > >
>>> > > > > > to
>>> > > > > > > > > > > > > start, so you may need to adjust
>>> > > > > > > > > > > > > CONFIG_SPL_TEXT_BASE instead.
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > I am creating my sdcard with a standard linux
>>> > > > > > > > > > > > > > (Linux for
>>> > > > > >
>>> > > > > > Tegra)
>>> > > > > > > > > > > > > > rootfs:
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > Did these instructions come from a web site
>>> > > > > > > > > > > > > somewhere?
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > Partition an SD card
>>> > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > sudo cgpt create <MMC BLOCK DEVICE>
>>> > > > > > > > > > > > > > sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t
>>> > > > > > > > > > > > > > kernel <MMC BLOCK
>>> > > > > > > > > > > > > > DEVICE>
>>> > > > > > > > > > > > > > # 16
>>> > > > > > > > > > > > > > MB
>>> > > > > > > > > > > > > > kernel image partition
>>> > > > > > > > > > > > > > sudo cgpt add -b 32802 -s <ROOT PARTITION
>>> > > > > > > > > > > > > > SIZE in 512B
>>> > > > > >
>>> > > > > > sectors>
>>> > > > > > > > > > > > > > -t
>>> > > > > > > > > > > > > > rootfs
>>> > > > > > > > > > > > > > <MMC BLOCK DEVICE>
>>> > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > cgpt doesn't seem to create a protective MBR.
>>> > > > > > > > > > > > > > If one is not
>>> > > > > > > > > > > > > > already
>>> > > > > > > > > > > > > > in
>>> > > > > > > > > > > > > > place, it can be created with:
>>> > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > sudo gdisk <MMC BLOCK DEVICE> # and enter
>>> > > > > > > > > > > > > > command w
>>> > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > Copy data to the SD card
>>> > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > sudo dd if=./kernelpart.bin of=<MMC BLOCK
>>> > > > > > > > > > > > > > DEVICE>p1
>>> > > > > > > > > > > > > > sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>>> > > > > > > > > > > > > > sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>>> > > > > > > > > > > > > >
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > How are you actually making it boot? Is this in
>>> > > > > > > > > > > > > dev mode with
>>> > > > > >
>>> > > > > > USB
>>> > > > > > > > > > > > > boot
>>> > > > > > > > > > > > > enabled and pressing Ctrl-U?
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > Also, as this is a mailing list, please avoid
>>> > > > > > > > > > > > > top-posting.
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > - Simon
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > I am using chained boot to test uboot as a FIT
>>> > > > > > > > > > > > > image so I I
>>> > > > > >
>>> > > > > > don't
>>> > > > > > > > > > > > > have to
>>> > > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
>>> > > > > > > > > > > > > need to be
>>> > > > > >
>>> > > > > > adjusted
>>> > > > > > > > > > > > > for
>>> > > > > > > > > > > > > chained boot?
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > I am using instructions to boot Linux for Tegra
>>> > > > > > > > > > > > > from
>>> > > > > >
>>> > > > > > sdcard/USB in
>>> > > > > > > > > > > > > developer
>>> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > What mainline branch should I try?
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > On Mon, May 1, 2017 at 11:14 AM, Simon Glass
>>> > > > > > > > > > > > > > <
>>> > > > > >
>>> > > > > > sjg at chromium.org>
>>> > > > > > > > > > > > > > wrote:
>>> > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > Hi Matthew,
>>> > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > On 1 May 2017 at 08:43, Matthew Gorski <
>>> > > > > >
>>> > > > > > matt.gorski at gmail.com>
>>> > > > > > > > > > > > > > > wrote:
>>> > > > > > > > > > > > > > > > I am porting u-boot to nyan_big and need
>>> > > > > > > > > > > > > > > > some input.  I
>>> > > > > >
>>> > > > > > have
>>> > > > > > > > > > > > > > > > been
>>> > > > > > > > > > > > > > > > searching
>>> > > > > > > > > > > > > > > > high and low and found this thread here:
>>> > > > > > > > > > > > > > > > [U-Boot] [PATCH
>>> > > > > >
>>> > > > > > 0/20]
>>> > > > > > > > > > > > > > > > tegra:
>>> > > > > > > > > > > > > > > > Expand
>>> > > > > > > > > > > > > > > > Nyan-big support
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > >  https://lists.denx.de/pipermail/u-boot/2
>>> > > > > > > > > > > > > > > > 015-March/209530.
>>> > > > > >
>>> > > > > > html
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > > I have tried to build u-boot with the
>>> > > > > > > > > > > > > > > > branch here:
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > > https://git.collabora.com/cgit
>>> > > > > >
>>> > > > > > /user/tomeu/u-boot.git/commit/?h=nyan-big
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > > and also the official chromium next
>>> > > > > > > > > > > > > > > > branch
>>> > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > Have you tried mainline U-Boot? It already
>>> > > > > > > > > > > > > > > supports nyan-big.
>>> > > > > > > > > > > > > > > I'm
>>> > > > > > > > > > > > > > > not
>>> > > > > > > > > > > > > > > sure about the situation with the
>>> > > > > > > > > > > > > > > downstream trees.
>>> > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > > I followed building instructions here:
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > > https://www.chromium.org/chrom
>>> > > > > >
>>> > > > > > ium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung
>>> > > > > > -arm-chromebook
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > > I build with these commands:
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > > mkimage -e 0x81000100 -a 0x81000100 -f
>>> > > > > > > > > > > > > > > > kernel-big.its
>>> > > > > > > > > > > > > > > > kernel-u-boot
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > > (with and without the load address
>>> > > > > > > > > > > > > > > > setting)
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > > vbutil_kernel --arch arm --pack
>>> > > > > > > > > > > > > > > > kernel.bin --keyblock
>>> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kernel.keyblock
>>> > > > > > > > > > > > > > > > --signprivate
>>> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kernel_data_key.
>>> > > > > > > > > > > > > > > > vbprivk
>>> > > > > >
>>> > > > > > --version 1
>>> > > > > > > > > > > > > > > > --config
>>> > > > > > > > > > > > > > > > dummy.txt --vmlinuz kernel-u-boot --
>>> > > > > > > > > > > > > > > > bootloader dummy.txt
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > > I have had numerous failed attempts to
>>> > > > > > > > > > > > > > > > boot uboot from
>>> > > > > >
>>> > > > > > sdcard
>>> > > > > > > > > > > > > > > > mmcblk1p1
>>> > > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > > Any help is appreciated I have only
>>> > > > > > > > > > > > > > > > gotten a blank screen
>>> > > > > > > > > > > > > > > > after
>>> > > > > > > > > > > > > > > > weeks
>>> > > > > > > > > > > > > > > > of
>>> > > > > > > > > > > > > > > > flashing.  I can boot custom v3.10
>>> > > > > > > > > > > > > > > > kernels so I assume I am
>>> > > > > > > > > > > > > > > > using
>>> > > > > > > > > > > > > > > > the
>>> > > > > > > > > > > > > > > > correct building procedure.  Thanks in
>>> > > > > > > > > > > > > > > > advance for help
>>> > > > > >
>>> > > > > > from
>>> > > > > > > > > > > > > > > > the
>>> > > > > > > > > > > > > > > > u-boot
>>> > > > > > > > > > > > > > > > community.
>>> > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > It is possible that it needs a particular
>>> > > > > > > > > > > > > > > address due to
>>> > > > > > > > > > > > > > > limitations
>>> > > > > > > > > > > > > > > in the FIT support on Nyan. I'm not sure
>>> > > > > > > > > > > > > > > what it is but
>>> > > > > >
>>> > > > > > might be
>>> > > > > > > > > > > > > > > able
>>> > > > > > > > > > > > > > > to take a look at some point.
>>> > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > How are you building your SD card? Are you
>>> > > > > > > > > > > > > > > following some
>>> > > > > > > > > > > > > > > instructions
>>> > > > > > > > > > > > > > > from somewhere?
>>> > > > > > > > > > > > > > >
>>> > > > > > > > > > > > > > > Regards,
>>> > > > > > > > > > > > > > > Simon
>>> > > > > > > > > > > > > >
>>> > > > > > > > > > > > > >
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > >
>>> > > > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > >
>>> > > > > > >
>>> > > > >
>>> > > > >
>>> > > >
>>> > > > _______________________________________________
>>> > > > U-Boot mailing list
>>> > > > U-Boot at lists.denx.de
>>> > > > https://lists.denx.de/listinfo/u-boot
>>>
>>> --
>>> Sjoerd Simons
>>> Collabora Ltd.
>>>
>>
>>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Simon Glass]

Hi Matthew,

On 2 May 2017 at 18:51, Matthew Gorski <matt.gorski@gmail.com> wrote:
> I have yet to produce a u-boot command prompt.  I can get the display to
> flash using u-boot mainline with 0x81000100 as the SYS_TEXT_BASE and using:
>
>  description = "Chrome OS kernel image with one or more FDT blobs";
>
> but the boot process forces a reboot into recovery.
>
> If I use:
>
> description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE IMAGE
> STARTS AT THE RIGHT OFFSET";
> Produces a blank screen with the exact u-boot.bin
>
> I hope someone can confirm nyan can chainboot u-boot and possibly post what
> the used for their FIT its config.  Thanks for all the help and guided
> responses.

I hope to be able to try this later in the week.

- Simon

>
> On Tue, May 2, 2017 at 11:34 AM, Matthew Gorski <matt.gorski@gmail.com>
> wrote:
>>
>>
>>
>> On Tue, May 2, 2017 at 9:25 AM, Matthew Gorski <matt.gorski@gmail.com>
>> wrote:
>>>
>>>
>>>
>>> On Tue, May 2, 2017 at 2:54 AM, Sjoerd Simons
>>> <sjoerd.simons@collabora.co.uk> wrote:
>>>>
>>>> On Tue, 2017-05-02 at 08:42 +0200, Tomeu Vizoso wrote:
>>>> > On 2 May 2017 at 08:40, Tomeu Vizoso <tomeu@tomeuvizoso.net> wrote:
>>>> > > On 2 May 2017 at 03:19, Matthew Gorski <matt.gorski@gmail.com>
>>>> > > wrote:
>>>> > > > Seems if you change the FIT description from anything but
>>>> > > >
>>>> > > > "description = "Chrome OS kernel image with one or more FDT
>>>> > > > blobs";"
>>>> > > >
>>>> > > > the kernel wont load. So this issue has to be in the kernel-
>>>> > > > big.its
>>>> > > > <https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel
>>>> > > > -big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923>
>>>> > > >
>>>> > > > https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel-
>>>> > > > big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923
>>>> > > >
>>>> > > > We may just need a proper working .its for nyan
>>>> > >
>>>> > > Hi Matthew,
>>>> > >
>>>> > > it has been quite a while, but I remember that if we only tried
>>>> > > chainloading U-Boot was because the goal was to integrate these
>>>> > > machines in our LAVA lab, which to date doesn't support Depthcharge
>>>> > > (though I hope this will change once I get back some time).
>>>> > >
>>>> > > I cannot remember how the correct position of the kernel within the
>>>> > > FIT image was calculated, but it definitely involved looking at the
>>>> > > depthcharge sources.
>>>> >
>>>> > Actually, I have grepped my IRC logs and turns out that we need for
>>>> > the start of U-Boot's code to be aligned to 64kB.
>>>>
>>>> Yup, U-boot both needs to be properly aligned and know its text base
>>>> address.
>>>>
>>>> So the calculation we did was basically look at depthcharge where in
>>>> memory the FIT image gets loaded, determine a suitable load address
>>>> after that (e.g fit load + 64k), configure that in u-boot and then add
>>>> enough padding in the fit image itself such that the u-boot code starts
>>>> at the determined address in memory by putting in just the right amount
>>>> of padding ;).
>>>>
>>>> It is rather ugly, but it does allow running u-boot without the need to
>>>> change the firmware in flash.
>>>
>>>
>>> Thank You Tomeu, Sjoerd and Simon for taking the time to chime in on an
>>> old but interesting topic.
>>>
>>> I believe I have enough info from you all to get this figured out now.
>>>
>>> Since depthcharch loads the FIT image at 0x81000000
>>> https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/master/board/nyan_big/defconfig#11
>>>
>>> I need to determine a suitable load address e.g fit load + 64k
>>>
>>> So 81000000 + 64k.
>>>
>>> One thing I am not certain about is adding the padding to the FIT .its
>>> config. How is this done?
>>>
>>> description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE IMAGE
>>> STARTS AT THE RIGHT OFFSET";
>>
>>
>> Seems if I use the description "description = "U-Boot + FDT --------- THIS
>> PADDING IS NEEDED SO THE IMAGE STARTS AT THE RIGHT OFFSET"; "
>>
>> I get a blank display that shows no signs of loading uboot BUT if I use:
>>
>> description = "Chrome OS kernel image with one or more FDT blobs";
>>
>> Nyan tries to load something because the display flashes like a normal
>> bootup but immediately reboots into chromeos usb/sdcard recovery.
>>
>> So the hack in the the collabora uboot kernel-big.its doesnt seem to work
>> anymore unless the padding is messing with the load address.
>>
>> I am using mainline uboot with CONFIG_SYS_TEXT_BASE 0x81000100 should this
>> be changed?
>>
>> Also i am trying to figure out how padding is calculated in a fit image
>> and this is confusing.  Is the padding the actual description length?
>>>
>>>
>>>>
>>>> > Thus the padding.
>>>> >
>>>> > Regards,
>>>> >
>>>> > Tomeu
>>>> >
>>>> > > But I do think to remember that it was only an issue once U-Boot
>>>> > > tried
>>>> > > to relocate itself.
>>>> > >
>>>> > > I don't see any reason why my old branch wouldn't work today on
>>>> > > your
>>>> > > machine, other than maybe your hw is a different revision with a
>>>> > > memory chip that wasn't supported back then? I also don't see why
>>>> > > mainline wouldn't work, provided you have that hack in the ITS.
>>>> > >
>>>> > > I'm adding Sjoerd to CC in case he remembers.
>>>> > >
>>>> > > Good luck,
>>>> > >
>>>> > > Tomeu
>>>> > >
>>>> > > > On Mon, May 1, 2017 at 7:45 PM, Matthew Gorski <matt.gorski@gmail
>>>> > > > .com>
>>>> > > > wrote:
>>>> > > >
>>>> > > > >
>>>> > > > >
>>>> > > > > On Mon, May 1, 2017 at 7:34 PM, Simon Glass <sjg@chromium.org>
>>>> > > > > wrote:
>>>> > > > >
>>>> > > > > > Hi Matthew,
>>>> > > > > >
>>>> > > > > > On 1 May 2017 at 17:27, Matthew Gorski <matt.gorski@gmail.com
>>>> > > > > > > wrote:
>>>> > > > > > >
>>>> > > > > > >
>>>> > > > > > > On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.o
>>>> > > > > > > rg> wrote:
>>>> > > > > > > >
>>>> > > > > > > > Hi Matthew,
>>>> > > > > > > >
>>>> > > > > > > > On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail
>>>> > > > > > > > .com> wrote:
>>>> > > > > > > > >
>>>> > > > > > > > >
>>>> > > > > > > > > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromi
>>>> > > > > > > > > um.org>
>>>> > > > > >
>>>> > > > > > wrote:
>>>> > > > > > > > > >
>>>> > > > > > > > > > Hi Matthew,
>>>> > > > > > > > > >
>>>> > > > > > > > > > On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@g
>>>> > > > > > > > > > mail.com>
>>>> > > > > >
>>>> > > > > > wrote:
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@ch
>>>> > > > > > > > > > > romium.org>
>>>> > > > > >
>>>> > > > > > wrote:
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > > > Hi Matthew,
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > > > On 1 May 2017 at 10:40, Matthew Gorski <matt.gors
>>>> > > > > > > > > > > > ki at gmail.com>
>>>> > > > > > > > > > > > wrote:
>>>> > > > > > > > > > > > > Let me repost this to the bottom.  New to the
>>>> > > > > > > > > > > > > mailing list ;)
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > I am using chained boot to test uboot as a FIT
>>>> > > > > > > > > > > > > image so I I
>>>> > > > > >
>>>> > > > > > don't
>>>> > > > > > > > > > > > > have to
>>>> > > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
>>>> > > > > > > > > > > > > need to be
>>>> > > > > >
>>>> > > > > > adjusted
>>>> > > > > > > > > > > > > for
>>>> > > > > > > > > > > > > chained boot?
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > I am using instructions to boot Linux for Tegra
>>>> > > > > > > > > > > > > from
>>>> > > > > >
>>>> > > > > > sdcard/USB in
>>>> > > > > > > > > > > > > developer
>>>> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > What mainline branch should I try?
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > > > There's only one mainline, here:
>>>> > > > > > > > > > > > http://git.denx.de/?p=u-boot.git;a=summary
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > > > There are various custodian branches but I don't
>>>> > > > > > > > > > > > believe the
>>>> > > > > >
>>>> > > > > > tegra
>>>> > > > > > > > > > > > one
>>>> > > > > > > > > > > > has anything different from mainline at present.
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > > > - Simon
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > I will give mainline a try with:
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > CONFIG_SYS_TEXT_BASE 0x8010E000
>>>> > > > > > > > > > > and
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > CONFIG_SPL_TEXT_BASE 0x80108000
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > I know I will also need:
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > CONFIG_DISPLAY_PORT=y
>>>> > > > > > > > > >
>>>> > > > > > > > > > Do you mean CONFIG_DISPLAY? If so, it is already
>>>> > > > > > > > > > defined.
>>>> > > > > > > > > >
>>>> > > > > > > > > > > CONFIG_VIDEO_TEGRA124=y
>>>> > > > > > > > > >
>>>> > > > > > > > > > That is defined in mainline
>>>> > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > for the console to display command prompt.
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > The FIT config I am using is from
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > here:https://git.collabora.com/cgit/user/tomeu/u-bo
>>>> > > > > > > > > > > ot.git/
>>>> > > > > >
>>>> > > > > > commit/?h=nyan-big
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > Do I need to adjust:
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >             load = <0>;
>>>> > > > > > > > > > >             entry = <0>;
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > /dts-v1/;
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > / {
>>>> > > > > > > > > > >     description = "U-Boot + FDT --------- THIS
>>>> > > > > > > > > > > PADDING IS NEEDED
>>>> > > > > >
>>>> > > > > > SO
>>>> > > > > > > > > > > THE
>>>> > > > > > > > > > > IMAGE STARTS AT THE RIGHT OFFSET";
>>>> > > > > > > > > >
>>>> > > > > > > > > > Perhaps you need to adjust this? How was the length
>>>> > > > > > > > > > of it
>>>> > > > > >
>>>> > > > > > calcualted?
>>>> > > > > > > > >
>>>> > > > > > > > >
>>>> > > > > > > > > I am really not sure how the padding was calculated.  I
>>>> > > > > > > > > just assumed
>>>> > > > > > > > > this
>>>> > > > > > > > > kernel-big.its FIT config was correct for nyan_big.  I
>>>> > > > > > > > > will try
>>>> > > > > >
>>>> > > > > > using my
>>>> > > > > > > > > working linux kernel fit config.
>>>> > > > > > > > > >
>>>> > > > > > > > > >
>>>> > > > > > > > > > >     #address-cells = <1>;
>>>> > > > > > > > > > >     images {
>>>> > > > > > > > > > >         kernel at 1{
>>>> > > > > > > > > > >             description = "kernel";
>>>> > > > > > > > > > >             data = /incbin/("u-boot-dtb.bin");
>>>> > > > > > > > > > >             type = "kernel_noload";
>>>> > > > > > > > > > >             arch = "arm";
>>>> > > > > > > > > > >             os = "linux";
>>>> > > > > > > > > > >             compression = "none";
>>>> > > > > > > > > > >             load = <0>;
>>>> > > > > > > > > > >             entry = <0>;
>>>> > > > > > > > > > >         };
>>>> > > > > > > > > > >         fdt at 1{
>>>> > > > > > > > > > >             description = "tegra124-nyan-big.dtb";
>>>> > > > > > > > > > >             data = /incbin/("dts/dt.dtb");
>>>> > > > > > > > > > >             type = "flat_dt";
>>>> > > > > > > > > > >             arch = "arm";
>>>> > > > > > > > > > >             compression = "none";
>>>> > > > > > > > > > >             hash at 1{
>>>> > > > > > > > > > >                 algo = "sha1";
>>>> > > > > > > > > > >             };
>>>> > > > > > > > > > >         };
>>>> > > > > > > > > > >     };
>>>> > > > > > > > > > >     configurations {
>>>> > > > > > > > > > >         default = "conf at 1";
>>>> > > > > > > > > > >         conf at 1{
>>>> > > > > > > > > > >             kernel = "kernel at 1";
>>>> > > > > > > > > > >             fdt = "fdt at 1";
>>>> > > > > > > > > > >         };
>>>> > > > > > > > > > >     };
>>>> > > > > > > > > > > };
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > please let me know if I should also adjust the SPL
>>>> > > > > > > > > > > CONFIG even
>>>> > > > > >
>>>> > > > > > though
>>>> > > > > > > > > > > I
>>>> > > > > > > > > > > am chainbooting uboot:
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > https://www.chromium.org/chromium-os/firmware-porti
>>>> > > > > > > > > > > ng-guide/
>>>> > > > > >
>>>> > > > > > using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing
>>>> > > > > > -nv-U-Boot-chained-U-Boot-method-
>>>> > > > > > > > > >
>>>> > > > > > > > > > This is exynos, where we booted directly into U-Boot.
>>>> > > > > > > > > > Actually I'm
>>>> > > > > > > > > > wondering we should boot directly into U-Boot
>>>> > > > > > > > > > (instead of SPL) on
>>>> > > > > >
>>>> > > > > > nyan
>>>> > > > > > > > > > also. Perhaps someone at collabora would know? Did
>>>> > > > > > > > > > you search the
>>>> > > > > > > > > > mailing list?
>>>> > > > > > > > > >
>>>> > > > > > > > > > Regards,
>>>> > > > > > > > > > Simon
>>>> > > > > > > > >
>>>> > > > > > > > >
>>>> > > > > > > > > I have not searched the mailing list.  What should I
>>>> > > > > > > > > search for?
>>>> > > > > > > > > Booting
>>>> > > > > > > > > nyan to u-boot directly bypassing SPL?
>>>> > > > > > > >
>>>> > > > > > > > Here are two subjects to search for:
>>>> > > > > > > >
>>>> > > > > > > > Veyron-speedy u-boot
>>>> > > > > > > > [PATCH 0/20] tegra: Expand Nyan-big support
>>>> > > > > > > >
>>>> > > > > > > > Regards,
>>>> > > > > > > > Simon
>>>> > > > > > >
>>>> > > > > > >
>>>> > > > > > > Very odd if I do not use "#address-cells = <1>;" the
>>>> > > > > > > display flashes and
>>>> > > > > > > reboots into recovery but if I do use #address-cells = <1>;
>>>> > > > > > > in my FIT
>>>> > > > > >
>>>> > > > > > config
>>>> > > > > > > I get a blank screen
>>>> > > > > > > so something is working when not using the padding.
>>>> > > > > >
>>>> > > > > > If you figure out where u-boot-dtb.bin needs to start by
>>>> > > > > > looking at
>>>> > > > > > depthcharge or where the kernel starts, then you can figure
>>>> > > > > > out how
>>>> > > > > > long the padding needs to be at the start of the FIT. Rather
>>>> > > > > > than
>>>> > > > > > guessing...!
>>>> > > > > >
>>>> > > > > > - Simon
>>>> > > > > >
>>>> > > > > >  Okay so depthcharge starts at 0x81000000 from here:
>>>> > > > >
>>>> > > > > https://chromium.googlesource.com/chromiumos/platform/
>>>> > > > > depthcharge/+/master/board/nyan_big/defconfig#11
>>>> > > > >
>>>> > > > > In my System.map for u-boot after building says the start is:
>>>> > > > > 81000100 T __image_copy_start
>>>> > > > > 81000100 T _start
>>>> > > > >
>>>> > > > > Hence the define CONFIG_SYS_TEXT_BASE 0x81000100
>>>> > > > >
>>>> > > > > So you say use 0x81000000 as the CONFIG_SYS_TEXT_BASE and not
>>>> > > > > 0x81000100
>>>> > > > > correct?
>>>> > > > >
>>>> > > > > > >
>>>> > > > > > > /dts-v1/;
>>>> > > > > > >
>>>> > > > > > > / {
>>>> > > > > > >     description = "Chrome OS nyan u-boot chain boot
>>>> > > > > > > method";
>>>> > > > > > >     #address-cells = <1>;
>>>> > > > > > >     images {
>>>> > > > > > >         kernel at 1{
>>>> > > > > > >
>>>> > > > > > > >
>>>> > > > > > > > > >
>>>> > > > > > > > > >
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > On May 1, 2017 12:11 PM, "Matthew Gorski" <
>>>> > > > > >
>>>> > > > > > matt.gorski at gmail.com>
>>>> > > > > > > > > > > > > wrote:
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chr
>>>> > > > > > > > > > > > > omium.org>
>>>> > > > > >
>>>> > > > > > wrote:
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > Hi Matthew,
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > On 1 May 2017 at 09:37, Matthew Gorski <matt.go
>>>> > > > > > > > > > > > > rski at gmail.com>
>>>> > > > > > > > > > > > > wrote:
>>>> > > > > > > > > > > > > > Thanks for the reply Simon.
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > I have been trying to find the System.map for
>>>> > > > > > > > > > > > > > depthcharge to
>>>> > > > > >
>>>> > > > > > see
>>>> > > > > > > > > > > > > > the
>>>> > > > > > > > > > > > > > kernel
>>>> > > > > > > > > > > > > > load address but I am unable to find
>>>> > > > > > > > > > > > > > anything.  I have tried
>>>> > > > > > > > > > > > > > multiple
>>>> > > > > > > > > > > > > > CONFIG_SYS_TEXT_BASE settings with no luck.
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > How did you choose what to use? Also note that
>>>> > > > > > > > > > > > > Tegra uses SPL
>>>> > > > > >
>>>> > > > > > to
>>>> > > > > > > > > > > > > start, so you may need to adjust
>>>> > > > > > > > > > > > > CONFIG_SPL_TEXT_BASE instead.
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > I am creating my sdcard with a standard linux
>>>> > > > > > > > > > > > > > (Linux for
>>>> > > > > >
>>>> > > > > > Tegra)
>>>> > > > > > > > > > > > > > rootfs:
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > Did these instructions come from a web site
>>>> > > > > > > > > > > > > somewhere?
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > Partition an SD card
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > sudo cgpt create <MMC BLOCK DEVICE>
>>>> > > > > > > > > > > > > > sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t
>>>> > > > > > > > > > > > > > kernel <MMC BLOCK
>>>> > > > > > > > > > > > > > DEVICE>
>>>> > > > > > > > > > > > > > # 16
>>>> > > > > > > > > > > > > > MB
>>>> > > > > > > > > > > > > > kernel image partition
>>>> > > > > > > > > > > > > > sudo cgpt add -b 32802 -s <ROOT PARTITION
>>>> > > > > > > > > > > > > > SIZE in 512B
>>>> > > > > >
>>>> > > > > > sectors>
>>>> > > > > > > > > > > > > > -t
>>>> > > > > > > > > > > > > > rootfs
>>>> > > > > > > > > > > > > > <MMC BLOCK DEVICE>
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > cgpt doesn't seem to create a protective MBR.
>>>> > > > > > > > > > > > > > If one is not
>>>> > > > > > > > > > > > > > already
>>>> > > > > > > > > > > > > > in
>>>> > > > > > > > > > > > > > place, it can be created with:
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > sudo gdisk <MMC BLOCK DEVICE> # and enter
>>>> > > > > > > > > > > > > > command w
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > Copy data to the SD card
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > sudo dd if=./kernelpart.bin of=<MMC BLOCK
>>>> > > > > > > > > > > > > > DEVICE>p1
>>>> > > > > > > > > > > > > > sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>>>> > > > > > > > > > > > > > sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > How are you actually making it boot? Is this in
>>>> > > > > > > > > > > > > dev mode with
>>>> > > > > >
>>>> > > > > > USB
>>>> > > > > > > > > > > > > boot
>>>> > > > > > > > > > > > > enabled and pressing Ctrl-U?
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > Also, as this is a mailing list, please avoid
>>>> > > > > > > > > > > > > top-posting.
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > - Simon
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > I am using chained boot to test uboot as a FIT
>>>> > > > > > > > > > > > > image so I I
>>>> > > > > >
>>>> > > > > > don't
>>>> > > > > > > > > > > > > have to
>>>> > > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
>>>> > > > > > > > > > > > > need to be
>>>> > > > > >
>>>> > > > > > adjusted
>>>> > > > > > > > > > > > > for
>>>> > > > > > > > > > > > > chained boot?
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > I am using instructions to boot Linux for Tegra
>>>> > > > > > > > > > > > > from
>>>> > > > > >
>>>> > > > > > sdcard/USB in
>>>> > > > > > > > > > > > > developer
>>>> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > What mainline branch should I try?
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > On Mon, May 1, 2017 at 11:14 AM, Simon Glass
>>>> > > > > > > > > > > > > > <
>>>> > > > > >
>>>> > > > > > sjg at chromium.org>
>>>> > > > > > > > > > > > > > wrote:
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > Hi Matthew,
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > On 1 May 2017 at 08:43, Matthew Gorski <
>>>> > > > > >
>>>> > > > > > matt.gorski at gmail.com>
>>>> > > > > > > > > > > > > > > wrote:
>>>> > > > > > > > > > > > > > > > I am porting u-boot to nyan_big and need
>>>> > > > > > > > > > > > > > > > some input.  I
>>>> > > > > >
>>>> > > > > > have
>>>> > > > > > > > > > > > > > > > been
>>>> > > > > > > > > > > > > > > > searching
>>>> > > > > > > > > > > > > > > > high and low and found this thread here:
>>>> > > > > > > > > > > > > > > > [U-Boot] [PATCH
>>>> > > > > >
>>>> > > > > > 0/20]
>>>> > > > > > > > > > > > > > > > tegra:
>>>> > > > > > > > > > > > > > > > Expand
>>>> > > > > > > > > > > > > > > > Nyan-big support
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >  https://lists.denx.de/pipermail/u-boot/2
>>>> > > > > > > > > > > > > > > > 015-March/209530.
>>>> > > > > >
>>>> > > > > > html
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > I have tried to build u-boot with the
>>>> > > > > > > > > > > > > > > > branch here:
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > https://git.collabora.com/cgit
>>>> > > > > >
>>>> > > > > > /user/tomeu/u-boot.git/commit/?h=nyan-big
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > and also the official chromium next
>>>> > > > > > > > > > > > > > > > branch
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > Have you tried mainline U-Boot? It already
>>>> > > > > > > > > > > > > > > supports nyan-big.
>>>> > > > > > > > > > > > > > > I'm
>>>> > > > > > > > > > > > > > > not
>>>> > > > > > > > > > > > > > > sure about the situation with the
>>>> > > > > > > > > > > > > > > downstream trees.
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > I followed building instructions here:
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > https://www.chromium.org/chrom
>>>> > > > > >
>>>> > > > > > ium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung
>>>> > > > > > -arm-chromebook
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > I build with these commands:
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > mkimage -e 0x81000100 -a 0x81000100 -f
>>>> > > > > > > > > > > > > > > > kernel-big.its
>>>> > > > > > > > > > > > > > > > kernel-u-boot
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > (with and without the load address
>>>> > > > > > > > > > > > > > > > setting)
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > vbutil_kernel --arch arm --pack
>>>> > > > > > > > > > > > > > > > kernel.bin --keyblock
>>>> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kernel.keyblock
>>>> > > > > > > > > > > > > > > > --signprivate
>>>> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kernel_data_key.
>>>> > > > > > > > > > > > > > > > vbprivk
>>>> > > > > >
>>>> > > > > > --version 1
>>>> > > > > > > > > > > > > > > > --config
>>>> > > > > > > > > > > > > > > > dummy.txt --vmlinuz kernel-u-boot --
>>>> > > > > > > > > > > > > > > > bootloader dummy.txt
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > I have had numerous failed attempts to
>>>> > > > > > > > > > > > > > > > boot uboot from
>>>> > > > > >
>>>> > > > > > sdcard
>>>> > > > > > > > > > > > > > > > mmcblk1p1
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > Any help is appreciated I have only
>>>> > > > > > > > > > > > > > > > gotten a blank screen
>>>> > > > > > > > > > > > > > > > after
>>>> > > > > > > > > > > > > > > > weeks
>>>> > > > > > > > > > > > > > > > of
>>>> > > > > > > > > > > > > > > > flashing.  I can boot custom v3.10
>>>> > > > > > > > > > > > > > > > kernels so I assume I am
>>>> > > > > > > > > > > > > > > > using
>>>> > > > > > > > > > > > > > > > the
>>>> > > > > > > > > > > > > > > > correct building procedure.  Thanks in
>>>> > > > > > > > > > > > > > > > advance for help
>>>> > > > > >
>>>> > > > > > from
>>>> > > > > > > > > > > > > > > > the
>>>> > > > > > > > > > > > > > > > u-boot
>>>> > > > > > > > > > > > > > > > community.
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > It is possible that it needs a particular
>>>> > > > > > > > > > > > > > > address due to
>>>> > > > > > > > > > > > > > > limitations
>>>> > > > > > > > > > > > > > > in the FIT support on Nyan. I'm not sure
>>>> > > > > > > > > > > > > > > what it is but
>>>> > > > > >
>>>> > > > > > might be
>>>> > > > > > > > > > > > > > > able
>>>> > > > > > > > > > > > > > > to take a look at some point.
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > How are you building your SD card? Are you
>>>> > > > > > > > > > > > > > > following some
>>>> > > > > > > > > > > > > > > instructions
>>>> > > > > > > > > > > > > > > from somewhere?
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > Regards,
>>>> > > > > > > > > > > > > > > Simon
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > >
>>>> > > > > > > > >
>>>> > > > > > >
>>>> > > > > > >
>>>> > > > >
>>>> > > > >
>>>> > > >
>>>> > > > _______________________________________________
>>>> > > > U-Boot mailing list
>>>> > > > U-Boot at lists.denx.de
>>>> > > > https://lists.denx.de/listinfo/u-boot
>>>>
>>>> --
>>>> Sjoerd Simons
>>>> Collabora Ltd.
>>>
>>>
>>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

Great Simon!  That would be very appreciated!  I look forward to your​
results.  Thanks for all the guidance.  If I have a servo board with serial
I'm sure I could see what's going on behind the scenes ;)

On May 2, 2017 10:40 PM, "Simon Glass" <sjg@chromium.org> wrote:

Hi Matthew,

On 2 May 2017 at 18:51, Matthew Gorski <matt.gorski@gmail.com> wrote:
> I have yet to produce a u-boot command prompt.  I can get the display to
> flash using u-boot mainline with 0x81000100 as the SYS_TEXT_BASE and
using:
>
>  description = "Chrome OS kernel image with one or more FDT blobs";
>
> but the boot process forces a reboot into recovery.
>
> If I use:
>
> description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE IMAGE
> STARTS AT THE RIGHT OFFSET";
> Produces a blank screen with the exact u-boot.bin
>
> I hope someone can confirm nyan can chainboot u-boot and possibly post
what
> the used for their FIT its config.  Thanks for all the help and guided
> responses.

I hope to be able to try this later in the week.

- Simon

>
> On Tue, May 2, 2017 at 11:34 AM, Matthew Gorski <matt.gorski@gmail.com>
> wrote:
>>
>>
>>
>> On Tue, May 2, 2017 at 9:25 AM, Matthew Gorski <matt.gorski@gmail.com>
>> wrote:
>>>
>>>
>>>
>>> On Tue, May 2, 2017 at 2:54 AM, Sjoerd Simons
>>> <sjoerd.simons@collabora.co.uk> wrote:
>>>>
>>>> On Tue, 2017-05-02 at 08:42 +0200, Tomeu Vizoso wrote:
>>>> > On 2 May 2017 at 08:40, Tomeu Vizoso <tomeu@tomeuvizoso.net> wrote:
>>>> > > On 2 May 2017 at 03:19, Matthew Gorski <matt.gorski@gmail.com>
>>>> > > wrote:
>>>> > > > Seems if you change the FIT description from anything but
>>>> > > >
>>>> > > > "description = "Chrome OS kernel image with one or more FDT
>>>> > > > blobs";"
>>>> > > >
>>>> > > > the kernel wont load. So this issue has to be in the kernel-
>>>> > > > big.its
>>>> > > > <https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel
>>>> > > > -big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923>
>>>> > > >
>>>> > > > https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/kernel-
>>>> > > > big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923
>>>> > > >
>>>> > > > We may just need a proper working .its for nyan
>>>> > >
>>>> > > Hi Matthew,
>>>> > >
>>>> > > it has been quite a while, but I remember that if we only tried
>>>> > > chainloading U-Boot was because the goal was to integrate these
>>>> > > machines in our LAVA lab, which to date doesn't support Depthcharge
>>>> > > (though I hope this will change once I get back some time).
>>>> > >
>>>> > > I cannot remember how the correct position of the kernel within the
>>>> > > FIT image was calculated, but it definitely involved looking at the
>>>> > > depthcharge sources.
>>>> >
>>>> > Actually, I have grepped my IRC logs and turns out that we need for
>>>> > the start of U-Boot's code to be aligned to 64kB.
>>>>
>>>> Yup, U-boot both needs to be properly aligned and know its text base
>>>> address.
>>>>
>>>> So the calculation we did was basically look at depthcharge where in
>>>> memory the FIT image gets loaded, determine a suitable load address
>>>> after that (e.g fit load + 64k), configure that in u-boot and then add
>>>> enough padding in the fit image itself such that the u-boot code starts
>>>> at the determined address in memory by putting in just the right amount
>>>> of padding ;).
>>>>
>>>> It is rather ugly, but it does allow running u-boot without the need to
>>>> change the firmware in flash.
>>>
>>>
>>> Thank You Tomeu, Sjoerd and Simon for taking the time to chime in on an
>>> old but interesting topic.
>>>
>>> I believe I have enough info from you all to get this figured out now.
>>>
>>> Since depthcharch loads the FIT image at 0x81000000
>>> https://chromium.googlesource.com/chromiumos/platform/
depthcharge/+/master/board/nyan_big/defconfig#11
>>>
>>> I need to determine a suitable load address e.g fit load + 64k
>>>
>>> So 81000000 + 64k.
>>>
>>> One thing I am not certain about is adding the padding to the FIT .its
>>> config. How is this done?
>>>
>>> description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE
IMAGE
>>> STARTS AT THE RIGHT OFFSET";
>>
>>
>> Seems if I use the description "description = "U-Boot + FDT ---------
THIS
>> PADDING IS NEEDED SO THE IMAGE STARTS AT THE RIGHT OFFSET"; "
>>
>> I get a blank display that shows no signs of loading uboot BUT if I use:
>>
>> description = "Chrome OS kernel image with one or more FDT blobs";
>>
>> Nyan tries to load something because the display flashes like a normal
>> bootup but immediately reboots into chromeos usb/sdcard recovery.
>>
>> So the hack in the the collabora uboot kernel-big.its doesnt seem to work
>> anymore unless the padding is messing with the load address.
>>
>> I am using mainline uboot with CONFIG_SYS_TEXT_BASE 0x81000100 should
this
>> be changed?
>>
>> Also i am trying to figure out how padding is calculated in a fit image
>> and this is confusing.  Is the padding the actual description length?
>>>
>>>
>>>>
>>>> > Thus the padding.
>>>> >
>>>> > Regards,
>>>> >
>>>> > Tomeu
>>>> >
>>>> > > But I do think to remember that it was only an issue once U-Boot
>>>> > > tried
>>>> > > to relocate itself.
>>>> > >
>>>> > > I don't see any reason why my old branch wouldn't work today on
>>>> > > your
>>>> > > machine, other than maybe your hw is a different revision with a
>>>> > > memory chip that wasn't supported back then? I also don't see why
>>>> > > mainline wouldn't work, provided you have that hack in the ITS.
>>>> > >
>>>> > > I'm adding Sjoerd to CC in case he remembers.
>>>> > >
>>>> > > Good luck,
>>>> > >
>>>> > > Tomeu
>>>> > >
>>>> > > > On Mon, May 1, 2017 at 7:45 PM, Matthew Gorski <matt.gorski@gmail
>>>> > > > .com>
>>>> > > > wrote:
>>>> > > >
>>>> > > > >
>>>> > > > >
>>>> > > > > On Mon, May 1, 2017 at 7:34 PM, Simon Glass <sjg@chromium.org>
>>>> > > > > wrote:
>>>> > > > >
>>>> > > > > > Hi Matthew,
>>>> > > > > >
>>>> > > > > > On 1 May 2017 at 17:27, Matthew Gorski <matt.gorski@gmail.com
>>>> > > > > > > wrote:
>>>> > > > > > >
>>>> > > > > > >
>>>> > > > > > > On Mon, May 1, 2017 at 6:02 PM, Simon Glass <sjg@chromium.o
>>>> > > > > > > rg> wrote:
>>>> > > > > > > >
>>>> > > > > > > > Hi Matthew,
>>>> > > > > > > >
>>>> > > > > > > > On 1 May 2017 at 14:30, Matthew Gorski <matt.gorski@gmail
>>>> > > > > > > > .com> wrote:
>>>> > > > > > > > >
>>>> > > > > > > > >
>>>> > > > > > > > > On Mon, May 1, 2017 at 2:36 PM, Simon Glass <sjg@chromi
>>>> > > > > > > > > um.org>
>>>> > > > > >
>>>> > > > > > wrote:
>>>> > > > > > > > > >
>>>> > > > > > > > > > Hi Matthew,
>>>> > > > > > > > > >
>>>> > > > > > > > > > On 1 May 2017 at 11:26, Matthew Gorski <matt.gorski@g
>>>> > > > > > > > > > mail.com>
>>>> > > > > >
>>>> > > > > > wrote:
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > On Mon, May 1, 2017 at 1:03 PM, Simon Glass <sjg@ch
>>>> > > > > > > > > > > romium.org>
>>>> > > > > >
>>>> > > > > > wrote:
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > > > Hi Matthew,
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > > > On 1 May 2017 at 10:40, Matthew Gorski <matt.gors
>>>> > > > > > > > > > > > ki at gmail.com>
>>>> > > > > > > > > > > > wrote:
>>>> > > > > > > > > > > > > Let me repost this to the bottom.  New to the
>>>> > > > > > > > > > > > > mailing list ;)
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > I am using chained boot to test uboot as a FIT
>>>> > > > > > > > > > > > > image so I I
>>>> > > > > >
>>>> > > > > > don't
>>>> > > > > > > > > > > > > have to
>>>> > > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
>>>> > > > > > > > > > > > > need to be
>>>> > > > > >
>>>> > > > > > adjusted
>>>> > > > > > > > > > > > > for
>>>> > > > > > > > > > > > > chained boot?
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > I am using instructions to boot Linux for Tegra
>>>> > > > > > > > > > > > > from
>>>> > > > > >
>>>> > > > > > sdcard/USB in
>>>> > > > > > > > > > > > > developer
>>>> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > What mainline branch should I try?
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > > > There's only one mainline, here:
>>>> > > > > > > > > > > > http://git.denx.de/?p=u-boot.git;a=summary
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > > > There are various custodian branches but I don't
>>>> > > > > > > > > > > > believe the
>>>> > > > > >
>>>> > > > > > tegra
>>>> > > > > > > > > > > > one
>>>> > > > > > > > > > > > has anything different from mainline at present.
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > > > - Simon
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > I will give mainline a try with:
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > CONFIG_SYS_TEXT_BASE 0x8010E000
>>>> > > > > > > > > > > and
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > CONFIG_SPL_TEXT_BASE 0x80108000
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > I know I will also need:
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > CONFIG_DISPLAY_PORT=y
>>>> > > > > > > > > >
>>>> > > > > > > > > > Do you mean CONFIG_DISPLAY? If so, it is already
>>>> > > > > > > > > > defined.
>>>> > > > > > > > > >
>>>> > > > > > > > > > > CONFIG_VIDEO_TEGRA124=y
>>>> > > > > > > > > >
>>>> > > > > > > > > > That is defined in mainline
>>>> > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > for the console to display command prompt.
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > The FIT config I am using is from
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > here:https://git.collabora.com/cgit/user/tomeu/u-bo
>>>> > > > > > > > > > > ot.git/
>>>> > > > > >
>>>> > > > > > commit/?h=nyan-big
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > Do I need to adjust:
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >             load = <0>;
>>>> > > > > > > > > > >             entry = <0>;
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > /dts-v1/;
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > / {
>>>> > > > > > > > > > >     description = "U-Boot + FDT --------- THIS
>>>> > > > > > > > > > > PADDING IS NEEDED
>>>> > > > > >
>>>> > > > > > SO
>>>> > > > > > > > > > > THE
>>>> > > > > > > > > > > IMAGE STARTS AT THE RIGHT OFFSET";
>>>> > > > > > > > > >
>>>> > > > > > > > > > Perhaps you need to adjust this? How was the length
>>>> > > > > > > > > > of it
>>>> > > > > >
>>>> > > > > > calcualted?
>>>> > > > > > > > >
>>>> > > > > > > > >
>>>> > > > > > > > > I am really not sure how the padding was calculated.  I
>>>> > > > > > > > > just assumed
>>>> > > > > > > > > this
>>>> > > > > > > > > kernel-big.its FIT config was correct for nyan_big.  I
>>>> > > > > > > > > will try
>>>> > > > > >
>>>> > > > > > using my
>>>> > > > > > > > > working linux kernel fit config.
>>>> > > > > > > > > >
>>>> > > > > > > > > >
>>>> > > > > > > > > > >     #address-cells = <1>;
>>>> > > > > > > > > > >     images {
>>>> > > > > > > > > > >         kernel at 1{
>>>> > > > > > > > > > >             description = "kernel";
>>>> > > > > > > > > > >             data = /incbin/("u-boot-dtb.bin");
>>>> > > > > > > > > > >             type = "kernel_noload";
>>>> > > > > > > > > > >             arch = "arm";
>>>> > > > > > > > > > >             os = "linux";
>>>> > > > > > > > > > >             compression = "none";
>>>> > > > > > > > > > >             load = <0>;
>>>> > > > > > > > > > >             entry = <0>;
>>>> > > > > > > > > > >         };
>>>> > > > > > > > > > >         fdt at 1{
>>>> > > > > > > > > > >             description = "tegra124-nyan-big.dtb";
>>>> > > > > > > > > > >             data = /incbin/("dts/dt.dtb");
>>>> > > > > > > > > > >             type = "flat_dt";
>>>> > > > > > > > > > >             arch = "arm";
>>>> > > > > > > > > > >             compression = "none";
>>>> > > > > > > > > > >             hash at 1{
>>>> > > > > > > > > > >                 algo = "sha1";
>>>> > > > > > > > > > >             };
>>>> > > > > > > > > > >         };
>>>> > > > > > > > > > >     };
>>>> > > > > > > > > > >     configurations {
>>>> > > > > > > > > > >         default = "conf at 1";
>>>> > > > > > > > > > >         conf at 1{
>>>> > > > > > > > > > >             kernel = "kernel at 1";
>>>> > > > > > > > > > >             fdt = "fdt at 1";
>>>> > > > > > > > > > >         };
>>>> > > > > > > > > > >     };
>>>> > > > > > > > > > > };
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > please let me know if I should also adjust the SPL
>>>> > > > > > > > > > > CONFIG even
>>>> > > > > >
>>>> > > > > > though
>>>> > > > > > > > > > > I
>>>> > > > > > > > > > > am chainbooting uboot:
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > > https://www.chromium.org/chromium-os/firmware-porti
>>>> > > > > > > > > > > ng-guide/
>>>> > > > > >
>>>> > > > > > using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-Installing
>>>> > > > > > -nv-U-Boot-chained-U-Boot-method-
>>>> > > > > > > > > >
>>>> > > > > > > > > > This is exynos, where we booted directly into U-Boot.
>>>> > > > > > > > > > Actually I'm
>>>> > > > > > > > > > wondering we should boot directly into U-Boot
>>>> > > > > > > > > > (instead of SPL) on
>>>> > > > > >
>>>> > > > > > nyan
>>>> > > > > > > > > > also. Perhaps someone at collabora would know? Did
>>>> > > > > > > > > > you search the
>>>> > > > > > > > > > mailing list?
>>>> > > > > > > > > >
>>>> > > > > > > > > > Regards,
>>>> > > > > > > > > > Simon
>>>> > > > > > > > >
>>>> > > > > > > > >
>>>> > > > > > > > > I have not searched the mailing list.  What should I
>>>> > > > > > > > > search for?
>>>> > > > > > > > > Booting
>>>> > > > > > > > > nyan to u-boot directly bypassing SPL?
>>>> > > > > > > >
>>>> > > > > > > > Here are two subjects to search for:
>>>> > > > > > > >
>>>> > > > > > > > Veyron-speedy u-boot
>>>> > > > > > > > [PATCH 0/20] tegra: Expand Nyan-big support
>>>> > > > > > > >
>>>> > > > > > > > Regards,
>>>> > > > > > > > Simon
>>>> > > > > > >
>>>> > > > > > >
>>>> > > > > > > Very odd if I do not use "#address-cells = <1>;" the
>>>> > > > > > > display flashes and
>>>> > > > > > > reboots into recovery but if I do use #address-cells = <1>;
>>>> > > > > > > in my FIT
>>>> > > > > >
>>>> > > > > > config
>>>> > > > > > > I get a blank screen
>>>> > > > > > > so something is working when not using the padding.
>>>> > > > > >
>>>> > > > > > If you figure out where u-boot-dtb.bin needs to start by
>>>> > > > > > looking at
>>>> > > > > > depthcharge or where the kernel starts, then you can figure
>>>> > > > > > out how
>>>> > > > > > long the padding needs to be at the start of the FIT. Rather
>>>> > > > > > than
>>>> > > > > > guessing...!
>>>> > > > > >
>>>> > > > > > - Simon
>>>> > > > > >
>>>> > > > > >  Okay so depthcharge starts at 0x81000000 from here:
>>>> > > > >
>>>> > > > > https://chromium.googlesource.com/chromiumos/platform/
>>>> > > > > depthcharge/+/master/board/nyan_big/defconfig#11
>>>> > > > >
>>>> > > > > In my System.map for u-boot after building says the start is:
>>>> > > > > 81000100 T __image_copy_start
>>>> > > > > 81000100 T _start
>>>> > > > >
>>>> > > > > Hence the define CONFIG_SYS_TEXT_BASE 0x81000100
>>>> > > > >
>>>> > > > > So you say use 0x81000000 as the CONFIG_SYS_TEXT_BASE and not
>>>> > > > > 0x81000100
>>>> > > > > correct?
>>>> > > > >
>>>> > > > > > >
>>>> > > > > > > /dts-v1/;
>>>> > > > > > >
>>>> > > > > > > / {
>>>> > > > > > >     description = "Chrome OS nyan u-boot chain boot
>>>> > > > > > > method";
>>>> > > > > > >     #address-cells = <1>;
>>>> > > > > > >     images {
>>>> > > > > > >         kernel at 1{
>>>> > > > > > >
>>>> > > > > > > >
>>>> > > > > > > > > >
>>>> > > > > > > > > >
>>>> > > > > > > > > > > >
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > On May 1, 2017 12:11 PM, "Matthew Gorski" <
>>>> > > > > >
>>>> > > > > > matt.gorski at gmail.com>
>>>> > > > > > > > > > > > > wrote:
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > On May 1, 2017 11:45 AM, "Simon Glass" <sjg@chr
>>>> > > > > > > > > > > > > omium.org>
>>>> > > > > >
>>>> > > > > > wrote:
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > Hi Matthew,
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > On 1 May 2017 at 09:37, Matthew Gorski <matt.go
>>>> > > > > > > > > > > > > rski at gmail.com>
>>>> > > > > > > > > > > > > wrote:
>>>> > > > > > > > > > > > > > Thanks for the reply Simon.
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > I have been trying to find the System.map for
>>>> > > > > > > > > > > > > > depthcharge to
>>>> > > > > >
>>>> > > > > > see
>>>> > > > > > > > > > > > > > the
>>>> > > > > > > > > > > > > > kernel
>>>> > > > > > > > > > > > > > load address but I am unable to find
>>>> > > > > > > > > > > > > > anything.  I have tried
>>>> > > > > > > > > > > > > > multiple
>>>> > > > > > > > > > > > > > CONFIG_SYS_TEXT_BASE settings with no luck.
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > How did you choose what to use? Also note that
>>>> > > > > > > > > > > > > Tegra uses SPL
>>>> > > > > >
>>>> > > > > > to
>>>> > > > > > > > > > > > > start, so you may need to adjust
>>>> > > > > > > > > > > > > CONFIG_SPL_TEXT_BASE instead.
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > I am creating my sdcard with a standard linux
>>>> > > > > > > > > > > > > > (Linux for
>>>> > > > > >
>>>> > > > > > Tegra)
>>>> > > > > > > > > > > > > > rootfs:
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > Did these instructions come from a web site
>>>> > > > > > > > > > > > > somewhere?
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > Partition an SD card
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > sudo cgpt create <MMC BLOCK DEVICE>
>>>> > > > > > > > > > > > > > sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t
>>>> > > > > > > > > > > > > > kernel <MMC BLOCK
>>>> > > > > > > > > > > > > > DEVICE>
>>>> > > > > > > > > > > > > > # 16
>>>> > > > > > > > > > > > > > MB
>>>> > > > > > > > > > > > > > kernel image partition
>>>> > > > > > > > > > > > > > sudo cgpt add -b 32802 -s <ROOT PARTITION
>>>> > > > > > > > > > > > > > SIZE in 512B
>>>> > > > > >
>>>> > > > > > sectors>
>>>> > > > > > > > > > > > > > -t
>>>> > > > > > > > > > > > > > rootfs
>>>> > > > > > > > > > > > > > <MMC BLOCK DEVICE>
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > cgpt doesn't seem to create a protective MBR.
>>>> > > > > > > > > > > > > > If one is not
>>>> > > > > > > > > > > > > > already
>>>> > > > > > > > > > > > > > in
>>>> > > > > > > > > > > > > > place, it can be created with:
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > sudo gdisk <MMC BLOCK DEVICE> # and enter
>>>> > > > > > > > > > > > > > command w
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > Copy data to the SD card
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > sudo dd if=./kernelpart.bin of=<MMC BLOCK
>>>> > > > > > > > > > > > > > DEVICE>p1
>>>> > > > > > > > > > > > > > sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>>>> > > > > > > > > > > > > > sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > How are you actually making it boot? Is this in
>>>> > > > > > > > > > > > > dev mode with
>>>> > > > > >
>>>> > > > > > USB
>>>> > > > > > > > > > > > > boot
>>>> > > > > > > > > > > > > enabled and pressing Ctrl-U?
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > Also, as this is a mailing list, please avoid
>>>> > > > > > > > > > > > > top-posting.
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > - Simon
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > I am using chained boot to test uboot as a FIT
>>>> > > > > > > > > > > > > image so I I
>>>> > > > > >
>>>> > > > > > don't
>>>> > > > > > > > > > > > > have to
>>>> > > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
>>>> > > > > > > > > > > > > need to be
>>>> > > > > >
>>>> > > > > > adjusted
>>>> > > > > > > > > > > > > for
>>>> > > > > > > > > > > > > chained boot?
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > I am using instructions to boot Linux for Tegra
>>>> > > > > > > > > > > > > from
>>>> > > > > >
>>>> > > > > > sdcard/USB in
>>>> > > > > > > > > > > > > developer
>>>> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > What mainline branch should I try?
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > On Mon, May 1, 2017 at 11:14 AM, Simon Glass
>>>> > > > > > > > > > > > > > <
>>>> > > > > >
>>>> > > > > > sjg at chromium.org>
>>>> > > > > > > > > > > > > > wrote:
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > Hi Matthew,
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > On 1 May 2017 at 08:43, Matthew Gorski <
>>>> > > > > >
>>>> > > > > > matt.gorski at gmail.com>
>>>> > > > > > > > > > > > > > > wrote:
>>>> > > > > > > > > > > > > > > > I am porting u-boot to nyan_big and need
>>>> > > > > > > > > > > > > > > > some input.  I
>>>> > > > > >
>>>> > > > > > have
>>>> > > > > > > > > > > > > > > > been
>>>> > > > > > > > > > > > > > > > searching
>>>> > > > > > > > > > > > > > > > high and low and found this thread here:
>>>> > > > > > > > > > > > > > > > [U-Boot] [PATCH
>>>> > > > > >
>>>> > > > > > 0/20]
>>>> > > > > > > > > > > > > > > > tegra:
>>>> > > > > > > > > > > > > > > > Expand
>>>> > > > > > > > > > > > > > > > Nyan-big support
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >  https://lists.denx.de/pipermail/u-boot/2
>>>> > > > > > > > > > > > > > > > 015-March/209530.
>>>> > > > > >
>>>> > > > > > html
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > I have tried to build u-boot with the
>>>> > > > > > > > > > > > > > > > branch here:
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > https://git.collabora.com/cgit
>>>> > > > > >
>>>> > > > > > /user/tomeu/u-boot.git/commit/?h=nyan-big
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > and also the official chromium next
>>>> > > > > > > > > > > > > > > > branch
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > Have you tried mainline U-Boot? It already
>>>> > > > > > > > > > > > > > > supports nyan-big.
>>>> > > > > > > > > > > > > > > I'm
>>>> > > > > > > > > > > > > > > not
>>>> > > > > > > > > > > > > > > sure about the situation with the
>>>> > > > > > > > > > > > > > > downstream trees.
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > I followed building instructions here:
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > https://www.chromium.org/chrom
>>>> > > > > >
>>>> > > > > > ium-os/firmware-porting-guide/using-nv-u-boot-on-the-samsung
>>>> > > > > > -arm-chromebook
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > I build with these commands:
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > mkimage -e 0x81000100 -a 0x81000100 -f
>>>> > > > > > > > > > > > > > > > kernel-big.its
>>>> > > > > > > > > > > > > > > > kernel-u-boot
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > (with and without the load address
>>>> > > > > > > > > > > > > > > > setting)
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > vbutil_kernel --arch arm --pack
>>>> > > > > > > > > > > > > > > > kernel.bin --keyblock
>>>> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kernel.keyblock
>>>> > > > > > > > > > > > > > > > --signprivate
>>>> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kernel_data_key.
>>>> > > > > > > > > > > > > > > > vbprivk
>>>> > > > > >
>>>> > > > > > --version 1
>>>> > > > > > > > > > > > > > > > --config
>>>> > > > > > > > > > > > > > > > dummy.txt --vmlinuz kernel-u-boot --
>>>> > > > > > > > > > > > > > > > bootloader dummy.txt
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > I have had numerous failed attempts to
>>>> > > > > > > > > > > > > > > > boot uboot from
>>>> > > > > >
>>>> > > > > > sdcard
>>>> > > > > > > > > > > > > > > > mmcblk1p1
>>>> > > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > > Any help is appreciated I have only
>>>> > > > > > > > > > > > > > > > gotten a blank screen
>>>> > > > > > > > > > > > > > > > after
>>>> > > > > > > > > > > > > > > > weeks
>>>> > > > > > > > > > > > > > > > of
>>>> > > > > > > > > > > > > > > > flashing.  I can boot custom v3.10
>>>> > > > > > > > > > > > > > > > kernels so I assume I am
>>>> > > > > > > > > > > > > > > > using
>>>> > > > > > > > > > > > > > > > the
>>>> > > > > > > > > > > > > > > > correct building procedure.  Thanks in
>>>> > > > > > > > > > > > > > > > advance for help
>>>> > > > > >
>>>> > > > > > from
>>>> > > > > > > > > > > > > > > > the
>>>> > > > > > > > > > > > > > > > u-boot
>>>> > > > > > > > > > > > > > > > community.
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > It is possible that it needs a particular
>>>> > > > > > > > > > > > > > > address due to
>>>> > > > > > > > > > > > > > > limitations
>>>> > > > > > > > > > > > > > > in the FIT support on Nyan. I'm not sure
>>>> > > > > > > > > > > > > > > what it is but
>>>> > > > > >
>>>> > > > > > might be
>>>> > > > > > > > > > > > > > > able
>>>> > > > > > > > > > > > > > > to take a look at some point.
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > How are you building your SD card? Are you
>>>> > > > > > > > > > > > > > > following some
>>>> > > > > > > > > > > > > > > instructions
>>>> > > > > > > > > > > > > > > from somewhere?
>>>> > > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > > > Regards,
>>>> > > > > > > > > > > > > > > Simon
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > > >
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > > > >
>>>> > > > > > > > >
>>>> > > > > > > > >
>>>> > > > > > >
>>>> > > > > > >
>>>> > > > >
>>>> > > > >
>>>> > > >
>>>> > > > _______________________________________________
>>>> > > > U-Boot mailing list
>>>> > > > U-Boot at lists.denx.de
>>>> > > > https://lists.denx.de/listinfo/u-boot
>>>>
>>>> --
>>>> Sjoerd Simons
>>>> Collabora Ltd.
>>>
>>>
>>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Thomas Hoff]

Hey Matthew,

Did you have any luck with this? I was attempting to do this a while back
with no success.

Cheers,

Thomas

On Wed, May 3, 2017 at 5:02 AM, Matthew Gorski <matt.gorski@gmail.com>
wrote:

> Great Simon!  That would be very appreciated!  I look forward to your​
> results.  Thanks for all the guidance.  If I have a servo board with serial
> I'm sure I could see what's going on behind the scenes ;)
>
> On May 2, 2017 10:40 PM, "Simon Glass" <sjg@chromium.org> wrote:
>
> Hi Matthew,
>
> On 2 May 2017 at 18:51, Matthew Gorski <matt.gorski@gmail.com> wrote:
> > I have yet to produce a u-boot command prompt.  I can get the display to
> > flash using u-boot mainline with 0x81000100 as the SYS_TEXT_BASE and
> using:
> >
> >  description = "Chrome OS kernel image with one or more FDT blobs";
> >
> > but the boot process forces a reboot into recovery.
> >
> > If I use:
> >
> > description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE IMAGE
> > STARTS AT THE RIGHT OFFSET";
> > Produces a blank screen with the exact u-boot.bin
> >
> > I hope someone can confirm nyan can chainboot u-boot and possibly post
> what
> > the used for their FIT its config.  Thanks for all the help and guided
> > responses.
>
> I hope to be able to try this later in the week.
>
> - Simon
>
> >
> > On Tue, May 2, 2017 at 11:34 AM, Matthew Gorski <matt.gorski@gmail.com>
> > wrote:
> >>
> >>
> >>
> >> On Tue, May 2, 2017 at 9:25 AM, Matthew Gorski <matt.gorski@gmail.com>
> >> wrote:
> >>>
> >>>
> >>>
> >>> On Tue, May 2, 2017 at 2:54 AM, Sjoerd Simons
> >>> <sjoerd.simons@collabora.co.uk> wrote:
> >>>>
> >>>> On Tue, 2017-05-02 at 08:42 +0200, Tomeu Vizoso wrote:
> >>>> > On 2 May 2017 at 08:40, Tomeu Vizoso <tomeu@tomeuvizoso.net> wrote:
> >>>> > > On 2 May 2017 at 03:19, Matthew Gorski <matt.gorski@gmail.com>
> >>>> > > wrote:
> >>>> > > > Seems if you change the FIT description from anything but
> >>>> > > >
> >>>> > > > "description = "Chrome OS kernel image with one or more FDT
> >>>> > > > blobs";"
> >>>> > > >
> >>>> > > > the kernel wont load. So this issue has to be in the kernel-
> >>>> > > > big.its
> >>>> > > > <https://git.collabora.com/cgit/user/tomeu/u-boot.git/
> tree/kernel
> >>>> > > > -big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467e
> e75ed06923>
> >>>> > > >
> >>>> > > > https://git.collabora.com/cgit/user/tomeu/u-boot.git/
> tree/kernel-
> >>>> > > > big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923
> >>>> > > >
> >>>> > > > We may just need a proper working .its for nyan
> >>>> > >
> >>>> > > Hi Matthew,
> >>>> > >
> >>>> > > it has been quite a while, but I remember that if we only tried
> >>>> > > chainloading U-Boot was because the goal was to integrate these
> >>>> > > machines in our LAVA lab, which to date doesn't support
> Depthcharge
> >>>> > > (though I hope this will change once I get back some time).
> >>>> > >
> >>>> > > I cannot remember how the correct position of the kernel within
> the
> >>>> > > FIT image was calculated, but it definitely involved looking at
> the
> >>>> > > depthcharge sources.
> >>>> >
> >>>> > Actually, I have grepped my IRC logs and turns out that we need for
> >>>> > the start of U-Boot's code to be aligned to 64kB.
> >>>>
> >>>> Yup, U-boot both needs to be properly aligned and know its text base
> >>>> address.
> >>>>
> >>>> So the calculation we did was basically look at depthcharge where in
> >>>> memory the FIT image gets loaded, determine a suitable load address
> >>>> after that (e.g fit load + 64k), configure that in u-boot and then add
> >>>> enough padding in the fit image itself such that the u-boot code
> starts
> >>>> at the determined address in memory by putting in just the right
> amount
> >>>> of padding ;).
> >>>>
> >>>> It is rather ugly, but it does allow running u-boot without the need
> to
> >>>> change the firmware in flash.
> >>>
> >>>
> >>> Thank You Tomeu, Sjoerd and Simon for taking the time to chime in on an
> >>> old but interesting topic.
> >>>
> >>> I believe I have enough info from you all to get this figured out now.
> >>>
> >>> Since depthcharch loads the FIT image at 0x81000000
> >>> https://chromium.googlesource.com/chromiumos/platform/
> depthcharge/+/master/board/nyan_big/defconfig#11
> >>>
> >>> I need to determine a suitable load address e.g fit load + 64k
> >>>
> >>> So 81000000 + 64k.
> >>>
> >>> One thing I am not certain about is adding the padding to the FIT .its
> >>> config. How is this done?
> >>>
> >>> description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE
> IMAGE
> >>> STARTS AT THE RIGHT OFFSET";
> >>
> >>
> >> Seems if I use the description "description = "U-Boot + FDT ---------
> THIS
> >> PADDING IS NEEDED SO THE IMAGE STARTS AT THE RIGHT OFFSET"; "
> >>
> >> I get a blank display that shows no signs of loading uboot BUT if I use:
> >>
> >> description = "Chrome OS kernel image with one or more FDT blobs";
> >>
> >> Nyan tries to load something because the display flashes like a normal
> >> bootup but immediately reboots into chromeos usb/sdcard recovery.
> >>
> >> So the hack in the the collabora uboot kernel-big.its doesnt seem to
> work
> >> anymore unless the padding is messing with the load address.
> >>
> >> I am using mainline uboot with CONFIG_SYS_TEXT_BASE 0x81000100 should
> this
> >> be changed?
> >>
> >> Also i am trying to figure out how padding is calculated in a fit image
> >> and this is confusing.  Is the padding the actual description length?
> >>>
> >>>
> >>>>
> >>>> > Thus the padding.
> >>>> >
> >>>> > Regards,
> >>>> >
> >>>> > Tomeu
> >>>> >
> >>>> > > But I do think to remember that it was only an issue once U-Boot
> >>>> > > tried
> >>>> > > to relocate itself.
> >>>> > >
> >>>> > > I don't see any reason why my old branch wouldn't work today on
> >>>> > > your
> >>>> > > machine, other than maybe your hw is a different revision with a
> >>>> > > memory chip that wasn't supported back then? I also don't see why
> >>>> > > mainline wouldn't work, provided you have that hack in the ITS.
> >>>> > >
> >>>> > > I'm adding Sjoerd to CC in case he remembers.
> >>>> > >
> >>>> > > Good luck,
> >>>> > >
> >>>> > > Tomeu
> >>>> > >
> >>>> > > > On Mon, May 1, 2017 at 7:45 PM, Matthew Gorski
> <matt.gorski@gmail
> >>>> > > > .com>
> >>>> > > > wrote:
> >>>> > > >
> >>>> > > > >
> >>>> > > > >
> >>>> > > > > On Mon, May 1, 2017 at 7:34 PM, Simon Glass <sjg@chromium.org
> >
> >>>> > > > > wrote:
> >>>> > > > >
> >>>> > > > > > Hi Matthew,
> >>>> > > > > >
> >>>> > > > > > On 1 May 2017 at 17:27, Matthew Gorski <
> matt.gorski at gmail.com
> >>>> > > > > > > wrote:
> >>>> > > > > > >
> >>>> > > > > > >
> >>>> > > > > > > On Mon, May 1, 2017 at 6:02 PM, Simon Glass
> <sjg@chromium.o
> >>>> > > > > > > rg> wrote:
> >>>> > > > > > > >
> >>>> > > > > > > > Hi Matthew,
> >>>> > > > > > > >
> >>>> > > > > > > > On 1 May 2017 at 14:30, Matthew Gorski
> <matt.gorski@gmail
> >>>> > > > > > > > .com> wrote:
> >>>> > > > > > > > >
> >>>> > > > > > > > >
> >>>> > > > > > > > > On Mon, May 1, 2017 at 2:36 PM, Simon Glass
> <sjg@chromi
> >>>> > > > > > > > > um.org>
> >>>> > > > > >
> >>>> > > > > > wrote:
> >>>> > > > > > > > > >
> >>>> > > > > > > > > > Hi Matthew,
> >>>> > > > > > > > > >
> >>>> > > > > > > > > > On 1 May 2017 at 11:26, Matthew Gorski
> <matt.gorski@g
> >>>> > > > > > > > > > mail.com>
> >>>> > > > > >
> >>>> > > > > > wrote:
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > On Mon, May 1, 2017 at 1:03 PM, Simon Glass
> <sjg@ch
> >>>> > > > > > > > > > > romium.org>
> >>>> > > > > >
> >>>> > > > > > wrote:
> >>>> > > > > > > > > > > >
> >>>> > > > > > > > > > > > Hi Matthew,
> >>>> > > > > > > > > > > >
> >>>> > > > > > > > > > > > On 1 May 2017 at 10:40, Matthew Gorski
> <matt.gors
> >>>> > > > > > > > > > > > ki at gmail.com>
> >>>> > > > > > > > > > > > wrote:
> >>>> > > > > > > > > > > > > Let me repost this to the bottom.  New to the
> >>>> > > > > > > > > > > > > mailing list ;)
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > I am using chained boot to test uboot as a FIT
> >>>> > > > > > > > > > > > > image so I I
> >>>> > > > > >
> >>>> > > > > > don't
> >>>> > > > > > > > > > > > > have to
> >>>> > > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
> >>>> > > > > > > > > > > > > need to be
> >>>> > > > > >
> >>>> > > > > > adjusted
> >>>> > > > > > > > > > > > > for
> >>>> > > > > > > > > > > > > chained boot?
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > I am using instructions to boot Linux for
> Tegra
> >>>> > > > > > > > > > > > > from
> >>>> > > > > >
> >>>> > > > > > sdcard/USB in
> >>>> > > > > > > > > > > > > developer
> >>>> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > What mainline branch should I try?
> >>>> > > > > > > > > > > >
> >>>> > > > > > > > > > > > There's only one mainline, here:
> >>>> > > > > > > > > > > > http://git.denx.de/?p=u-boot.git;a=summary
> >>>> > > > > > > > > > > >
> >>>> > > > > > > > > > > > There are various custodian branches but I don't
> >>>> > > > > > > > > > > > believe the
> >>>> > > > > >
> >>>> > > > > > tegra
> >>>> > > > > > > > > > > > one
> >>>> > > > > > > > > > > > has anything different from mainline at present.
> >>>> > > > > > > > > > > >
> >>>> > > > > > > > > > > > - Simon
> >>>> > > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > I will give mainline a try with:
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > CONFIG_SYS_TEXT_BASE 0x8010E000
> >>>> > > > > > > > > > > and
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > CONFIG_SPL_TEXT_BASE 0x80108000
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > I know I will also need:
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > CONFIG_DISPLAY_PORT=y
> >>>> > > > > > > > > >
> >>>> > > > > > > > > > Do you mean CONFIG_DISPLAY? If so, it is already
> >>>> > > > > > > > > > defined.
> >>>> > > > > > > > > >
> >>>> > > > > > > > > > > CONFIG_VIDEO_TEGRA124=y
> >>>> > > > > > > > > >
> >>>> > > > > > > > > > That is defined in mainline
> >>>> > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > for the console to display command prompt.
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > The FIT config I am using is from
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > here:https://git.collabora.
> com/cgit/user/tomeu/u-bo
> >>>> > > > > > > > > > > ot.git/
> >>>> > > > > >
> >>>> > > > > > commit/?h=nyan-big
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > Do I need to adjust:
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >             load = <0>;
> >>>> > > > > > > > > > >             entry = <0>;
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > /dts-v1/;
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > / {
> >>>> > > > > > > > > > >     description = "U-Boot + FDT --------- THIS
> >>>> > > > > > > > > > > PADDING IS NEEDED
> >>>> > > > > >
> >>>> > > > > > SO
> >>>> > > > > > > > > > > THE
> >>>> > > > > > > > > > > IMAGE STARTS AT THE RIGHT OFFSET";
> >>>> > > > > > > > > >
> >>>> > > > > > > > > > Perhaps you need to adjust this? How was the length
> >>>> > > > > > > > > > of it
> >>>> > > > > >
> >>>> > > > > > calcualted?
> >>>> > > > > > > > >
> >>>> > > > > > > > >
> >>>> > > > > > > > > I am really not sure how the padding was calculated.
> I
> >>>> > > > > > > > > just assumed
> >>>> > > > > > > > > this
> >>>> > > > > > > > > kernel-big.its FIT config was correct for nyan_big.  I
> >>>> > > > > > > > > will try
> >>>> > > > > >
> >>>> > > > > > using my
> >>>> > > > > > > > > working linux kernel fit config.
> >>>> > > > > > > > > >
> >>>> > > > > > > > > >
> >>>> > > > > > > > > > >     #address-cells = <1>;
> >>>> > > > > > > > > > >     images {
> >>>> > > > > > > > > > >         kernel at 1{
> >>>> > > > > > > > > > >             description = "kernel";
> >>>> > > > > > > > > > >             data = /incbin/("u-boot-dtb.bin");
> >>>> > > > > > > > > > >             type = "kernel_noload";
> >>>> > > > > > > > > > >             arch = "arm";
> >>>> > > > > > > > > > >             os = "linux";
> >>>> > > > > > > > > > >             compression = "none";
> >>>> > > > > > > > > > >             load = <0>;
> >>>> > > > > > > > > > >             entry = <0>;
> >>>> > > > > > > > > > >         };
> >>>> > > > > > > > > > >         fdt at 1{
> >>>> > > > > > > > > > >             description = "tegra124-nyan-big.dtb";
> >>>> > > > > > > > > > >             data = /incbin/("dts/dt.dtb");
> >>>> > > > > > > > > > >             type = "flat_dt";
> >>>> > > > > > > > > > >             arch = "arm";
> >>>> > > > > > > > > > >             compression = "none";
> >>>> > > > > > > > > > >             hash at 1{
> >>>> > > > > > > > > > >                 algo = "sha1";
> >>>> > > > > > > > > > >             };
> >>>> > > > > > > > > > >         };
> >>>> > > > > > > > > > >     };
> >>>> > > > > > > > > > >     configurations {
> >>>> > > > > > > > > > >         default = "conf at 1";
> >>>> > > > > > > > > > >         conf at 1{
> >>>> > > > > > > > > > >             kernel = "kernel at 1";
> >>>> > > > > > > > > > >             fdt = "fdt at 1";
> >>>> > > > > > > > > > >         };
> >>>> > > > > > > > > > >     };
> >>>> > > > > > > > > > > };
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > please let me know if I should also adjust the SPL
> >>>> > > > > > > > > > > CONFIG even
> >>>> > > > > >
> >>>> > > > > > though
> >>>> > > > > > > > > > > I
> >>>> > > > > > > > > > > am chainbooting uboot:
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > > https://www.chromium.org/
> chromium-os/firmware-porti
> >>>> > > > > > > > > > > ng-guide/
> >>>> > > > > >
> >>>> > > > > > using-nv-u-boot-on-the-samsung-arm-chromebook#TOC-
> Installing
> >>>> > > > > > -nv-U-Boot-chained-U-Boot-method-
> >>>> > > > > > > > > >
> >>>> > > > > > > > > > This is exynos, where we booted directly into
> U-Boot.
> >>>> > > > > > > > > > Actually I'm
> >>>> > > > > > > > > > wondering we should boot directly into U-Boot
> >>>> > > > > > > > > > (instead of SPL) on
> >>>> > > > > >
> >>>> > > > > > nyan
> >>>> > > > > > > > > > also. Perhaps someone at collabora would know? Did
> >>>> > > > > > > > > > you search the
> >>>> > > > > > > > > > mailing list?
> >>>> > > > > > > > > >
> >>>> > > > > > > > > > Regards,
> >>>> > > > > > > > > > Simon
> >>>> > > > > > > > >
> >>>> > > > > > > > >
> >>>> > > > > > > > > I have not searched the mailing list.  What should I
> >>>> > > > > > > > > search for?
> >>>> > > > > > > > > Booting
> >>>> > > > > > > > > nyan to u-boot directly bypassing SPL?
> >>>> > > > > > > >
> >>>> > > > > > > > Here are two subjects to search for:
> >>>> > > > > > > >
> >>>> > > > > > > > Veyron-speedy u-boot
> >>>> > > > > > > > [PATCH 0/20] tegra: Expand Nyan-big support
> >>>> > > > > > > >
> >>>> > > > > > > > Regards,
> >>>> > > > > > > > Simon
> >>>> > > > > > >
> >>>> > > > > > >
> >>>> > > > > > > Very odd if I do not use "#address-cells = <1>;" the
> >>>> > > > > > > display flashes and
> >>>> > > > > > > reboots into recovery but if I do use #address-cells =
> <1>;
> >>>> > > > > > > in my FIT
> >>>> > > > > >
> >>>> > > > > > config
> >>>> > > > > > > I get a blank screen
> >>>> > > > > > > so something is working when not using the padding.
> >>>> > > > > >
> >>>> > > > > > If you figure out where u-boot-dtb.bin needs to start by
> >>>> > > > > > looking at
> >>>> > > > > > depthcharge or where the kernel starts, then you can figure
> >>>> > > > > > out how
> >>>> > > > > > long the padding needs to be at the start of the FIT. Rather
> >>>> > > > > > than
> >>>> > > > > > guessing...!
> >>>> > > > > >
> >>>> > > > > > - Simon
> >>>> > > > > >
> >>>> > > > > >  Okay so depthcharge starts at 0x81000000 from here:
> >>>> > > > >
> >>>> > > > > https://chromium.googlesource.com/chromiumos/platform/
> >>>> > > > > depthcharge/+/master/board/nyan_big/defconfig#11
> >>>> > > > >
> >>>> > > > > In my System.map for u-boot after building says the start is:
> >>>> > > > > 81000100 T __image_copy_start
> >>>> > > > > 81000100 T _start
> >>>> > > > >
> >>>> > > > > Hence the define CONFIG_SYS_TEXT_BASE 0x81000100
> >>>> > > > >
> >>>> > > > > So you say use 0x81000000 as the CONFIG_SYS_TEXT_BASE and not
> >>>> > > > > 0x81000100
> >>>> > > > > correct?
> >>>> > > > >
> >>>> > > > > > >
> >>>> > > > > > > /dts-v1/;
> >>>> > > > > > >
> >>>> > > > > > > / {
> >>>> > > > > > >     description = "Chrome OS nyan u-boot chain boot
> >>>> > > > > > > method";
> >>>> > > > > > >     #address-cells = <1>;
> >>>> > > > > > >     images {
> >>>> > > > > > >         kernel at 1{
> >>>> > > > > > >
> >>>> > > > > > > >
> >>>> > > > > > > > > >
> >>>> > > > > > > > > >
> >>>> > > > > > > > > > > >
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > On May 1, 2017 12:11 PM, "Matthew Gorski" <
> >>>> > > > > >
> >>>> > > > > > matt.gorski at gmail.com>
> >>>> > > > > > > > > > > > > wrote:
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > On May 1, 2017 11:45 AM, "Simon Glass"
> <sjg@chr
> >>>> > > > > > > > > > > > > omium.org>
> >>>> > > > > >
> >>>> > > > > > wrote:
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > Hi Matthew,
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > On 1 May 2017 at 09:37, Matthew Gorski
> <matt.go
> >>>> > > > > > > > > > > > > rski at gmail.com>
> >>>> > > > > > > > > > > > > wrote:
> >>>> > > > > > > > > > > > > > Thanks for the reply Simon.
> >>>> > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > I have been trying to find the System.map
> for
> >>>> > > > > > > > > > > > > > depthcharge to
> >>>> > > > > >
> >>>> > > > > > see
> >>>> > > > > > > > > > > > > > the
> >>>> > > > > > > > > > > > > > kernel
> >>>> > > > > > > > > > > > > > load address but I am unable to find
> >>>> > > > > > > > > > > > > > anything.  I have tried
> >>>> > > > > > > > > > > > > > multiple
> >>>> > > > > > > > > > > > > > CONFIG_SYS_TEXT_BASE settings with no luck.
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > How did you choose what to use? Also note that
> >>>> > > > > > > > > > > > > Tegra uses SPL
> >>>> > > > > >
> >>>> > > > > > to
> >>>> > > > > > > > > > > > > start, so you may need to adjust
> >>>> > > > > > > > > > > > > CONFIG_SPL_TEXT_BASE instead.
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > I am creating my sdcard with a standard
> linux
> >>>> > > > > > > > > > > > > > (Linux for
> >>>> > > > > >
> >>>> > > > > > Tegra)
> >>>> > > > > > > > > > > > > > rootfs:
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > Did these instructions come from a web site
> >>>> > > > > > > > > > > > > somewhere?
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > Partition an SD card
> >>>> > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > sudo cgpt create <MMC BLOCK DEVICE>
> >>>> > > > > > > > > > > > > > sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t
> >>>> > > > > > > > > > > > > > kernel <MMC BLOCK
> >>>> > > > > > > > > > > > > > DEVICE>
> >>>> > > > > > > > > > > > > > # 16
> >>>> > > > > > > > > > > > > > MB
> >>>> > > > > > > > > > > > > > kernel image partition
> >>>> > > > > > > > > > > > > > sudo cgpt add -b 32802 -s <ROOT PARTITION
> >>>> > > > > > > > > > > > > > SIZE in 512B
> >>>> > > > > >
> >>>> > > > > > sectors>
> >>>> > > > > > > > > > > > > > -t
> >>>> > > > > > > > > > > > > > rootfs
> >>>> > > > > > > > > > > > > > <MMC BLOCK DEVICE>
> >>>> > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > cgpt doesn't seem to create a protective
> MBR.
> >>>> > > > > > > > > > > > > > If one is not
> >>>> > > > > > > > > > > > > > already
> >>>> > > > > > > > > > > > > > in
> >>>> > > > > > > > > > > > > > place, it can be created with:
> >>>> > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > sudo gdisk <MMC BLOCK DEVICE> # and enter
> >>>> > > > > > > > > > > > > > command w
> >>>> > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > Copy data to the SD card
> >>>> > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > sudo dd if=./kernelpart.bin of=<MMC BLOCK
> >>>> > > > > > > > > > > > > > DEVICE>p1
> >>>> > > > > > > > > > > > > > sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
> >>>> > > > > > > > > > > > > > sudo mount <MMC BLOCK DEVICE>p2 /mnt/
> >>>> > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > How are you actually making it boot? Is this
> in
> >>>> > > > > > > > > > > > > dev mode with
> >>>> > > > > >
> >>>> > > > > > USB
> >>>> > > > > > > > > > > > > boot
> >>>> > > > > > > > > > > > > enabled and pressing Ctrl-U?
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > Also, as this is a mailing list, please avoid
> >>>> > > > > > > > > > > > > top-posting.
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > - Simon
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > I am using chained boot to test uboot as a FIT
> >>>> > > > > > > > > > > > > image so I I
> >>>> > > > > >
> >>>> > > > > > don't
> >>>> > > > > > > > > > > > > have to
> >>>> > > > > > > > > > > > > flash to spl flash.  Does CONFIG_SPL_TEXT_BASE
> >>>> > > > > > > > > > > > > need to be
> >>>> > > > > >
> >>>> > > > > > adjusted
> >>>> > > > > > > > > > > > > for
> >>>> > > > > > > > > > > > > chained boot?
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > I am using instructions to boot Linux for
> Tegra
> >>>> > > > > > > > > > > > > from
> >>>> > > > > >
> >>>> > > > > > sdcard/USB in
> >>>> > > > > > > > > > > > > developer
> >>>> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > What mainline branch should I try?
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > On Mon, May 1, 2017 at 11:14 AM, Simon Glass
> >>>> > > > > > > > > > > > > > <
> >>>> > > > > >
> >>>> > > > > > sjg at chromium.org>
> >>>> > > > > > > > > > > > > > wrote:
> >>>> > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > Hi Matthew,
> >>>> > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > On 1 May 2017 at 08:43, Matthew Gorski <
> >>>> > > > > >
> >>>> > > > > > matt.gorski at gmail.com>
> >>>> > > > > > > > > > > > > > > wrote:
> >>>> > > > > > > > > > > > > > > > I am porting u-boot to nyan_big and need
> >>>> > > > > > > > > > > > > > > > some input.  I
> >>>> > > > > >
> >>>> > > > > > have
> >>>> > > > > > > > > > > > > > > > been
> >>>> > > > > > > > > > > > > > > > searching
> >>>> > > > > > > > > > > > > > > > high and low and found this thread here:
> >>>> > > > > > > > > > > > > > > > [U-Boot] [PATCH
> >>>> > > > > >
> >>>> > > > > > 0/20]
> >>>> > > > > > > > > > > > > > > > tegra:
> >>>> > > > > > > > > > > > > > > > Expand
> >>>> > > > > > > > > > > > > > > > Nyan-big support
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > >  https://lists.denx.de/
> pipermail/u-boot/2
> >>>> > > > > > > > > > > > > > > > 015-March/209530.
> >>>> > > > > >
> >>>> > > > > > html
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > > I have tried to build u-boot with the
> >>>> > > > > > > > > > > > > > > > branch here:
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > > https://git.collabora.com/cgit
> >>>> > > > > >
> >>>> > > > > > /user/tomeu/u-boot.git/commit/?h=nyan-big
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > > and also the official chromium next
> >>>> > > > > > > > > > > > > > > > branch
> >>>> > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > Have you tried mainline U-Boot? It already
> >>>> > > > > > > > > > > > > > > supports nyan-big.
> >>>> > > > > > > > > > > > > > > I'm
> >>>> > > > > > > > > > > > > > > not
> >>>> > > > > > > > > > > > > > > sure about the situation with the
> >>>> > > > > > > > > > > > > > > downstream trees.
> >>>> > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > > I followed building instructions here:
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > > https://www.chromium.org/chrom
> >>>> > > > > >
> >>>> > > > > > ium-os/firmware-porting-guide/
> using-nv-u-boot-on-the-samsung
> >>>> > > > > > -arm-chromebook
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > > I build with these commands:
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > > mkimage -e 0x81000100 -a 0x81000100 -f
> >>>> > > > > > > > > > > > > > > > kernel-big.its
> >>>> > > > > > > > > > > > > > > > kernel-u-boot
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > > (with and without the load address
> >>>> > > > > > > > > > > > > > > > setting)
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > > vbutil_kernel --arch arm --pack
> >>>> > > > > > > > > > > > > > > > kernel.bin --keyblock
> >>>> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/
> kernel.keyblock
> >>>> > > > > > > > > > > > > > > > --signprivate
> >>>> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/
> kernel_data_key.
> >>>> > > > > > > > > > > > > > > > vbprivk
> >>>> > > > > >
> >>>> > > > > > --version 1
> >>>> > > > > > > > > > > > > > > > --config
> >>>> > > > > > > > > > > > > > > > dummy.txt --vmlinuz kernel-u-boot --
> >>>> > > > > > > > > > > > > > > > bootloader dummy.txt
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > > I have had numerous failed attempts to
> >>>> > > > > > > > > > > > > > > > boot uboot from
> >>>> > > > > >
> >>>> > > > > > sdcard
> >>>> > > > > > > > > > > > > > > > mmcblk1p1
> >>>> > > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > > Any help is appreciated I have only
> >>>> > > > > > > > > > > > > > > > gotten a blank screen
> >>>> > > > > > > > > > > > > > > > after
> >>>> > > > > > > > > > > > > > > > weeks
> >>>> > > > > > > > > > > > > > > > of
> >>>> > > > > > > > > > > > > > > > flashing.  I can boot custom v3.10
> >>>> > > > > > > > > > > > > > > > kernels so I assume I am
> >>>> > > > > > > > > > > > > > > > using
> >>>> > > > > > > > > > > > > > > > the
> >>>> > > > > > > > > > > > > > > > correct building procedure.  Thanks in
> >>>> > > > > > > > > > > > > > > > advance for help
> >>>> > > > > >
> >>>> > > > > > from
> >>>> > > > > > > > > > > > > > > > the
> >>>> > > > > > > > > > > > > > > > u-boot
> >>>> > > > > > > > > > > > > > > > community.
> >>>> > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > It is possible that it needs a particular
> >>>> > > > > > > > > > > > > > > address due to
> >>>> > > > > > > > > > > > > > > limitations
> >>>> > > > > > > > > > > > > > > in the FIT support on Nyan. I'm not sure
> >>>> > > > > > > > > > > > > > > what it is but
> >>>> > > > > >
> >>>> > > > > > might be
> >>>> > > > > > > > > > > > > > > able
> >>>> > > > > > > > > > > > > > > to take a look at some point.
> >>>> > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > How are you building your SD card? Are you
> >>>> > > > > > > > > > > > > > > following some
> >>>> > > > > > > > > > > > > > > instructions
> >>>> > > > > > > > > > > > > > > from somewhere?
> >>>> > > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > > > Regards,
> >>>> > > > > > > > > > > > > > > Simon
> >>>> > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > > >
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > > > >
> >>>> > > > > > > > >
> >>>> > > > > > > > >
> >>>> > > > > > >
> >>>> > > > > > >
> >>>> > > > >
> >>>> > > > >
> >>>> > > >
> >>>> > > > _______________________________________________
> >>>> > > > U-Boot mailing list
> >>>> > > > U-Boot at lists.denx.de
> >>>> > > > https://lists.denx.de/listinfo/u-boot
> >>>>
> >>>> --
> >>>> Sjoerd Simons
> >>>> Collabora Ltd.
> >>>
> >>>
> >>
> >
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Matthew Gorski]

On Fri, May 5, 2017 at 1:54 PM, Thomas Hoff <thomashoffltd@gmail.com> wrote:

> Hey Matthew,
>
> Did you have any luck with this? I was attempting to do this a while back
> with no success.
>
> Cheers,
>
> Thomas
>

No unfortunately not.  Simon was going to try himself at some point.  I
have a few u-boot forks im dying to chain-boot on nyan so I hope there is
some progress.  I think we need to see whats going on behind the scenes
with a servo board and serial output because I can get u-boot to boot (i
think) but it reboots immediately into recovery (no console on lcd display).

Let hope Simon gets some time in the near future ;)

>
> On Wed, May 3, 2017 at 5:02 AM, Matthew Gorski <matt.gorski@gmail.com>
> wrote:
>
>> Great Simon!  That would be very appreciated!  I look forward to your​
>> results.  Thanks for all the guidance.  If I have a servo board with
>> serial
>> I'm sure I could see what's going on behind the scenes ;)
>>
>> On May 2, 2017 10:40 PM, "Simon Glass" <sjg@chromium.org> wrote:
>>
>> Hi Matthew,
>>
>> On 2 May 2017 at 18:51, Matthew Gorski <matt.gorski@gmail.com> wrote:
>> > I have yet to produce a u-boot command prompt.  I can get the display to
>> > flash using u-boot mainline with 0x81000100 as the SYS_TEXT_BASE and
>> using:
>> >
>> >  description = "Chrome OS kernel image with one or more FDT blobs";
>> >
>> > but the boot process forces a reboot into recovery.
>> >
>> > If I use:
>> >
>> > description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE
>> IMAGE
>> > STARTS AT THE RIGHT OFFSET";
>> > Produces a blank screen with the exact u-boot.bin
>> >
>> > I hope someone can confirm nyan can chainboot u-boot and possibly post
>> what
>> > the used for their FIT its config.  Thanks for all the help and guided
>> > responses.
>>
>> I hope to be able to try this later in the week.
>>
>> - Simon
>>
>> >
>> > On Tue, May 2, 2017 at 11:34 AM, Matthew Gorski <matt.gorski@gmail.com>
>> > wrote:
>> >>
>> >>
>> >>
>> >> On Tue, May 2, 2017 at 9:25 AM, Matthew Gorski <matt.gorski@gmail.com>
>> >> wrote:
>> >>>
>> >>>
>> >>>
>> >>> On Tue, May 2, 2017 at 2:54 AM, Sjoerd Simons
>> >>> <sjoerd.simons@collabora.co.uk> wrote:
>> >>>>
>> >>>> On Tue, 2017-05-02 at 08:42 +0200, Tomeu Vizoso wrote:
>> >>>> > On 2 May 2017 at 08:40, Tomeu Vizoso <tomeu@tomeuvizoso.net>
>> wrote:
>> >>>> > > On 2 May 2017 at 03:19, Matthew Gorski <matt.gorski@gmail.com>
>> >>>> > > wrote:
>> >>>> > > > Seems if you change the FIT description from anything but
>> >>>> > > >
>> >>>> > > > "description = "Chrome OS kernel image with one or more FDT
>> >>>> > > > blobs";"
>> >>>> > > >
>> >>>> > > > the kernel wont load. So this issue has to be in the kernel-
>> >>>> > > > big.its
>> >>>> > > > <https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/
>> kernel
>> >>>> > > > -big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06
>> 923>
>> >>>> > > >
>> >>>> > > > https://git.collabora.com/cgit/user/tomeu/u-boot.git/tree/
>> kernel-
>> >>>> > > > big.its?h=nyan-big&id=35bcb399c0d78ba6a050cc775d467ee75ed06923
>> >>>> > > >
>> >>>> > > > We may just need a proper working .its for nyan
>> >>>> > >
>> >>>> > > Hi Matthew,
>> >>>> > >
>> >>>> > > it has been quite a while, but I remember that if we only tried
>> >>>> > > chainloading U-Boot was because the goal was to integrate these
>> >>>> > > machines in our LAVA lab, which to date doesn't support
>> Depthcharge
>> >>>> > > (though I hope this will change once I get back some time).
>> >>>> > >
>> >>>> > > I cannot remember how the correct position of the kernel within
>> the
>> >>>> > > FIT image was calculated, but it definitely involved looking at
>> the
>> >>>> > > depthcharge sources.
>> >>>> >
>> >>>> > Actually, I have grepped my IRC logs and turns out that we need for
>> >>>> > the start of U-Boot's code to be aligned to 64kB.
>> >>>>
>> >>>> Yup, U-boot both needs to be properly aligned and know its text base
>> >>>> address.
>> >>>>
>> >>>> So the calculation we did was basically look at depthcharge where in
>> >>>> memory the FIT image gets loaded, determine a suitable load address
>> >>>> after that (e.g fit load + 64k), configure that in u-boot and then
>> add
>> >>>> enough padding in the fit image itself such that the u-boot code
>> starts
>> >>>> at the determined address in memory by putting in just the right
>> amount
>> >>>> of padding ;).
>> >>>>
>> >>>> It is rather ugly, but it does allow running u-boot without the need
>> to
>> >>>> change the firmware in flash.
>> >>>
>> >>>
>> >>> Thank You Tomeu, Sjoerd and Simon for taking the time to chime in on
>> an
>> >>> old but interesting topic.
>> >>>
>> >>> I believe I have enough info from you all to get this figured out now.
>> >>>
>> >>> Since depthcharch loads the FIT image at 0x81000000
>> >>> https://chromium.googlesource.com/chromiumos/platform/
>> depthcharge/+/master/board/nyan_big/defconfig#11
>> >>>
>> >>> I need to determine a suitable load address e.g fit load + 64k
>> >>>
>> >>> So 81000000 + 64k.
>> >>>
>> >>> One thing I am not certain about is adding the padding to the FIT .its
>> >>> config. How is this done?
>> >>>
>> >>> description = "U-Boot + FDT --------- THIS PADDING IS NEEDED SO THE
>> IMAGE
>> >>> STARTS AT THE RIGHT OFFSET";
>> >>
>> >>
>> >> Seems if I use the description "description = "U-Boot + FDT ---------
>> THIS
>> >> PADDING IS NEEDED SO THE IMAGE STARTS AT THE RIGHT OFFSET"; "
>> >>
>> >> I get a blank display that shows no signs of loading uboot BUT if I
>> use:
>> >>
>> >> description = "Chrome OS kernel image with one or more FDT blobs";
>> >>
>> >> Nyan tries to load something because the display flashes like a normal
>> >> bootup but immediately reboots into chromeos usb/sdcard recovery.
>> >>
>> >> So the hack in the the collabora uboot kernel-big.its doesnt seem to
>> work
>> >> anymore unless the padding is messing with the load address.
>> >>
>> >> I am using mainline uboot with CONFIG_SYS_TEXT_BASE 0x81000100 should
>> this
>> >> be changed?
>> >>
>> >> Also i am trying to figure out how padding is calculated in a fit image
>> >> and this is confusing.  Is the padding the actual description length?
>> >>>
>> >>>
>> >>>>
>> >>>> > Thus the padding.
>> >>>> >
>> >>>> > Regards,
>> >>>> >
>> >>>> > Tomeu
>> >>>> >
>> >>>> > > But I do think to remember that it was only an issue once U-Boot
>> >>>> > > tried
>> >>>> > > to relocate itself.
>> >>>> > >
>> >>>> > > I don't see any reason why my old branch wouldn't work today on
>> >>>> > > your
>> >>>> > > machine, other than maybe your hw is a different revision with a
>> >>>> > > memory chip that wasn't supported back then? I also don't see why
>> >>>> > > mainline wouldn't work, provided you have that hack in the ITS.
>> >>>> > >
>> >>>> > > I'm adding Sjoerd to CC in case he remembers.
>> >>>> > >
>> >>>> > > Good luck,
>> >>>> > >
>> >>>> > > Tomeu
>> >>>> > >
>> >>>> > > > On Mon, May 1, 2017 at 7:45 PM, Matthew Gorski
>> <matt.gorski@gmail
>> >>>> > > > .com>
>> >>>> > > > wrote:
>> >>>> > > >
>> >>>> > > > >
>> >>>> > > > >
>> >>>> > > > > On Mon, May 1, 2017 at 7:34 PM, Simon Glass <
>> sjg at chromium.org>
>> >>>> > > > > wrote:
>> >>>> > > > >
>> >>>> > > > > > Hi Matthew,
>> >>>> > > > > >
>> >>>> > > > > > On 1 May 2017 at 17:27, Matthew Gorski <
>> matt.gorski at gmail.com
>> >>>> > > > > > > wrote:
>> >>>> > > > > > >
>> >>>> > > > > > >
>> >>>> > > > > > > On Mon, May 1, 2017 at 6:02 PM, Simon Glass
>> <sjg@chromium.o
>> >>>> > > > > > > rg> wrote:
>> >>>> > > > > > > >
>> >>>> > > > > > > > Hi Matthew,
>> >>>> > > > > > > >
>> >>>> > > > > > > > On 1 May 2017 at 14:30, Matthew Gorski
>> <matt.gorski@gmail
>> >>>> > > > > > > > .com> wrote:
>> >>>> > > > > > > > >
>> >>>> > > > > > > > >
>> >>>> > > > > > > > > On Mon, May 1, 2017 at 2:36 PM, Simon Glass
>> <sjg@chromi
>> >>>> > > > > > > > > um.org>
>> >>>> > > > > >
>> >>>> > > > > > wrote:
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > > Hi Matthew,
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > > On 1 May 2017 at 11:26, Matthew Gorski
>> <matt.gorski@g
>> >>>> > > > > > > > > > mail.com>
>> >>>> > > > > >
>> >>>> > > > > > wrote:
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > On Mon, May 1, 2017 at 1:03 PM, Simon Glass
>> <sjg@ch
>> >>>> > > > > > > > > > > romium.org>
>> >>>> > > > > >
>> >>>> > > > > > wrote:
>> >>>> > > > > > > > > > > >
>> >>>> > > > > > > > > > > > Hi Matthew,
>> >>>> > > > > > > > > > > >
>> >>>> > > > > > > > > > > > On 1 May 2017 at 10:40, Matthew Gorski
>> <matt.gors
>> >>>> > > > > > > > > > > > ki at gmail.com>
>> >>>> > > > > > > > > > > > wrote:
>> >>>> > > > > > > > > > > > > Let me repost this to the bottom.  New to the
>> >>>> > > > > > > > > > > > > mailing list ;)
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > I am using chained boot to test uboot as a
>> FIT
>> >>>> > > > > > > > > > > > > image so I I
>> >>>> > > > > >
>> >>>> > > > > > don't
>> >>>> > > > > > > > > > > > > have to
>> >>>> > > > > > > > > > > > > flash to spl flash.  Does
>> CONFIG_SPL_TEXT_BASE
>> >>>> > > > > > > > > > > > > need to be
>> >>>> > > > > >
>> >>>> > > > > > adjusted
>> >>>> > > > > > > > > > > > > for
>> >>>> > > > > > > > > > > > > chained boot?
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > I am using instructions to boot Linux for
>> Tegra
>> >>>> > > > > > > > > > > > > from
>> >>>> > > > > >
>> >>>> > > > > > sdcard/USB in
>> >>>> > > > > > > > > > > > > developer
>> >>>> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > What mainline branch should I try?
>> >>>> > > > > > > > > > > >
>> >>>> > > > > > > > > > > > There's only one mainline, here:
>> >>>> > > > > > > > > > > > http://git.denx.de/?p=u-boot.git;a=summary
>> >>>> > > > > > > > > > > >
>> >>>> > > > > > > > > > > > There are various custodian branches but I
>> don't
>> >>>> > > > > > > > > > > > believe the
>> >>>> > > > > >
>> >>>> > > > > > tegra
>> >>>> > > > > > > > > > > > one
>> >>>> > > > > > > > > > > > has anything different from mainline at
>> present.
>> >>>> > > > > > > > > > > >
>> >>>> > > > > > > > > > > > - Simon
>> >>>> > > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > I will give mainline a try with:
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > CONFIG_SYS_TEXT_BASE 0x8010E000
>> >>>> > > > > > > > > > > and
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > CONFIG_SPL_TEXT_BASE 0x80108000
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > I know I will also need:
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > CONFIG_DISPLAY_PORT=y
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > > Do you mean CONFIG_DISPLAY? If so, it is already
>> >>>> > > > > > > > > > defined.
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > > > CONFIG_VIDEO_TEGRA124=y
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > > That is defined in mainline
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > for the console to display command prompt.
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > The FIT config I am using is from
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > here:https://git.collabora.com
>> /cgit/user/tomeu/u-bo
>> >>>> > > > > > > > > > > ot.git/
>> >>>> > > > > >
>> >>>> > > > > > commit/?h=nyan-big
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > Do I need to adjust:
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >             load = <0>;
>> >>>> > > > > > > > > > >             entry = <0>;
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > /dts-v1/;
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > / {
>> >>>> > > > > > > > > > >     description = "U-Boot + FDT --------- THIS
>> >>>> > > > > > > > > > > PADDING IS NEEDED
>> >>>> > > > > >
>> >>>> > > > > > SO
>> >>>> > > > > > > > > > > THE
>> >>>> > > > > > > > > > > IMAGE STARTS AT THE RIGHT OFFSET";
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > > Perhaps you need to adjust this? How was the length
>> >>>> > > > > > > > > > of it
>> >>>> > > > > >
>> >>>> > > > > > calcualted?
>> >>>> > > > > > > > >
>> >>>> > > > > > > > >
>> >>>> > > > > > > > > I am really not sure how the padding was
>> calculated.  I
>> >>>> > > > > > > > > just assumed
>> >>>> > > > > > > > > this
>> >>>> > > > > > > > > kernel-big.its FIT config was correct for nyan_big.
>> I
>> >>>> > > > > > > > > will try
>> >>>> > > > > >
>> >>>> > > > > > using my
>> >>>> > > > > > > > > working linux kernel fit config.
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > > >     #address-cells = <1>;
>> >>>> > > > > > > > > > >     images {
>> >>>> > > > > > > > > > >         kernel at 1{
>> >>>> > > > > > > > > > >             description = "kernel";
>> >>>> > > > > > > > > > >             data = /incbin/("u-boot-dtb.bin");
>> >>>> > > > > > > > > > >             type = "kernel_noload";
>> >>>> > > > > > > > > > >             arch = "arm";
>> >>>> > > > > > > > > > >             os = "linux";
>> >>>> > > > > > > > > > >             compression = "none";
>> >>>> > > > > > > > > > >             load = <0>;
>> >>>> > > > > > > > > > >             entry = <0>;
>> >>>> > > > > > > > > > >         };
>> >>>> > > > > > > > > > >         fdt at 1{
>> >>>> > > > > > > > > > >             description =
>> "tegra124-nyan-big.dtb";
>> >>>> > > > > > > > > > >             data = /incbin/("dts/dt.dtb");
>> >>>> > > > > > > > > > >             type = "flat_dt";
>> >>>> > > > > > > > > > >             arch = "arm";
>> >>>> > > > > > > > > > >             compression = "none";
>> >>>> > > > > > > > > > >             hash at 1{
>> >>>> > > > > > > > > > >                 algo = "sha1";
>> >>>> > > > > > > > > > >             };
>> >>>> > > > > > > > > > >         };
>> >>>> > > > > > > > > > >     };
>> >>>> > > > > > > > > > >     configurations {
>> >>>> > > > > > > > > > >         default = "conf at 1";
>> >>>> > > > > > > > > > >         conf at 1{
>> >>>> > > > > > > > > > >             kernel = "kernel at 1";
>> >>>> > > > > > > > > > >             fdt = "fdt at 1";
>> >>>> > > > > > > > > > >         };
>> >>>> > > > > > > > > > >     };
>> >>>> > > > > > > > > > > };
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > please let me know if I should also adjust the
>> SPL
>> >>>> > > > > > > > > > > CONFIG even
>> >>>> > > > > >
>> >>>> > > > > > though
>> >>>> > > > > > > > > > > I
>> >>>> > > > > > > > > > > am chainbooting uboot:
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > > https://www.chromium.org/chrom
>> ium-os/firmware-porti
>> >>>> > > > > > > > > > > ng-guide/
>> >>>> > > > > >
>> >>>> > > > > > using-nv-u-boot-on-the-samsung
>> -arm-chromebook#TOC-Installing
>> >>>> > > > > > -nv-U-Boot-chained-U-Boot-method-
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > > This is exynos, where we booted directly into
>> U-Boot.
>> >>>> > > > > > > > > > Actually I'm
>> >>>> > > > > > > > > > wondering we should boot directly into U-Boot
>> >>>> > > > > > > > > > (instead of SPL) on
>> >>>> > > > > >
>> >>>> > > > > > nyan
>> >>>> > > > > > > > > > also. Perhaps someone at collabora would know? Did
>> >>>> > > > > > > > > > you search the
>> >>>> > > > > > > > > > mailing list?
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > > Regards,
>> >>>> > > > > > > > > > Simon
>> >>>> > > > > > > > >
>> >>>> > > > > > > > >
>> >>>> > > > > > > > > I have not searched the mailing list.  What should I
>> >>>> > > > > > > > > search for?
>> >>>> > > > > > > > > Booting
>> >>>> > > > > > > > > nyan to u-boot directly bypassing SPL?
>> >>>> > > > > > > >
>> >>>> > > > > > > > Here are two subjects to search for:
>> >>>> > > > > > > >
>> >>>> > > > > > > > Veyron-speedy u-boot
>> >>>> > > > > > > > [PATCH 0/20] tegra: Expand Nyan-big support
>> >>>> > > > > > > >
>> >>>> > > > > > > > Regards,
>> >>>> > > > > > > > Simon
>> >>>> > > > > > >
>> >>>> > > > > > >
>> >>>> > > > > > > Very odd if I do not use "#address-cells = <1>;" the
>> >>>> > > > > > > display flashes and
>> >>>> > > > > > > reboots into recovery but if I do use #address-cells =
>> <1>;
>> >>>> > > > > > > in my FIT
>> >>>> > > > > >
>> >>>> > > > > > config
>> >>>> > > > > > > I get a blank screen
>> >>>> > > > > > > so something is working when not using the padding.
>> >>>> > > > > >
>> >>>> > > > > > If you figure out where u-boot-dtb.bin needs to start by
>> >>>> > > > > > looking at
>> >>>> > > > > > depthcharge or where the kernel starts, then you can figure
>> >>>> > > > > > out how
>> >>>> > > > > > long the padding needs to be at the start of the FIT.
>> Rather
>> >>>> > > > > > than
>> >>>> > > > > > guessing...!
>> >>>> > > > > >
>> >>>> > > > > > - Simon
>> >>>> > > > > >
>> >>>> > > > > >  Okay so depthcharge starts at 0x81000000 from here:
>> >>>> > > > >
>> >>>> > > > > https://chromium.googlesource.com/chromiumos/platform/
>> >>>> > > > > depthcharge/+/master/board/nyan_big/defconfig#11
>> >>>> > > > >
>> >>>> > > > > In my System.map for u-boot after building says the start is:
>> >>>> > > > > 81000100 T __image_copy_start
>> >>>> > > > > 81000100 T _start
>> >>>> > > > >
>> >>>> > > > > Hence the define CONFIG_SYS_TEXT_BASE 0x81000100
>> >>>> > > > >
>> >>>> > > > > So you say use 0x81000000 as the CONFIG_SYS_TEXT_BASE and not
>> >>>> > > > > 0x81000100
>> >>>> > > > > correct?
>> >>>> > > > >
>> >>>> > > > > > >
>> >>>> > > > > > > /dts-v1/;
>> >>>> > > > > > >
>> >>>> > > > > > > / {
>> >>>> > > > > > >     description = "Chrome OS nyan u-boot chain boot
>> >>>> > > > > > > method";
>> >>>> > > > > > >     #address-cells = <1>;
>> >>>> > > > > > >     images {
>> >>>> > > > > > >         kernel at 1{
>> >>>> > > > > > >
>> >>>> > > > > > > >
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > >
>> >>>> > > > > > > > > > > >
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > On May 1, 2017 12:11 PM, "Matthew Gorski" <
>> >>>> > > > > >
>> >>>> > > > > > matt.gorski at gmail.com>
>> >>>> > > > > > > > > > > > > wrote:
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > On May 1, 2017 11:45 AM, "Simon Glass"
>> <sjg@chr
>> >>>> > > > > > > > > > > > > omium.org>
>> >>>> > > > > >
>> >>>> > > > > > wrote:
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > Hi Matthew,
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > On 1 May 2017 at 09:37, Matthew Gorski
>> <matt.go
>> >>>> > > > > > > > > > > > > rski at gmail.com>
>> >>>> > > > > > > > > > > > > wrote:
>> >>>> > > > > > > > > > > > > > Thanks for the reply Simon.
>> >>>> > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > I have been trying to find the System.map
>> for
>> >>>> > > > > > > > > > > > > > depthcharge to
>> >>>> > > > > >
>> >>>> > > > > > see
>> >>>> > > > > > > > > > > > > > the
>> >>>> > > > > > > > > > > > > > kernel
>> >>>> > > > > > > > > > > > > > load address but I am unable to find
>> >>>> > > > > > > > > > > > > > anything.  I have tried
>> >>>> > > > > > > > > > > > > > multiple
>> >>>> > > > > > > > > > > > > > CONFIG_SYS_TEXT_BASE settings with no luck.
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > How did you choose what to use? Also note
>> that
>> >>>> > > > > > > > > > > > > Tegra uses SPL
>> >>>> > > > > >
>> >>>> > > > > > to
>> >>>> > > > > > > > > > > > > start, so you may need to adjust
>> >>>> > > > > > > > > > > > > CONFIG_SPL_TEXT_BASE instead.
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > I am creating my sdcard with a standard
>> linux
>> >>>> > > > > > > > > > > > > > (Linux for
>> >>>> > > > > >
>> >>>> > > > > > Tegra)
>> >>>> > > > > > > > > > > > > > rootfs:
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > Did these instructions come from a web site
>> >>>> > > > > > > > > > > > > somewhere?
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > Partition an SD card
>> >>>> > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > sudo cgpt create <MMC BLOCK DEVICE>
>> >>>> > > > > > > > > > > > > > sudo cgpt add -b 34 -s 32768 -P 1 -S 1 -t
>> >>>> > > > > > > > > > > > > > kernel <MMC BLOCK
>> >>>> > > > > > > > > > > > > > DEVICE>
>> >>>> > > > > > > > > > > > > > # 16
>> >>>> > > > > > > > > > > > > > MB
>> >>>> > > > > > > > > > > > > > kernel image partition
>> >>>> > > > > > > > > > > > > > sudo cgpt add -b 32802 -s <ROOT PARTITION
>> >>>> > > > > > > > > > > > > > SIZE in 512B
>> >>>> > > > > >
>> >>>> > > > > > sectors>
>> >>>> > > > > > > > > > > > > > -t
>> >>>> > > > > > > > > > > > > > rootfs
>> >>>> > > > > > > > > > > > > > <MMC BLOCK DEVICE>
>> >>>> > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > cgpt doesn't seem to create a protective
>> MBR.
>> >>>> > > > > > > > > > > > > > If one is not
>> >>>> > > > > > > > > > > > > > already
>> >>>> > > > > > > > > > > > > > in
>> >>>> > > > > > > > > > > > > > place, it can be created with:
>> >>>> > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > sudo gdisk <MMC BLOCK DEVICE> # and enter
>> >>>> > > > > > > > > > > > > > command w
>> >>>> > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > Copy data to the SD card
>> >>>> > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > sudo dd if=./kernelpart.bin of=<MMC BLOCK
>> >>>> > > > > > > > > > > > > > DEVICE>p1
>> >>>> > > > > > > > > > > > > > sudo mkfs.ext4 <MMC BLOCK DEVICE>p2
>> >>>> > > > > > > > > > > > > > sudo mount <MMC BLOCK DEVICE>p2 /mnt/
>> >>>> > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > How are you actually making it boot? Is this
>> in
>> >>>> > > > > > > > > > > > > dev mode with
>> >>>> > > > > >
>> >>>> > > > > > USB
>> >>>> > > > > > > > > > > > > boot
>> >>>> > > > > > > > > > > > > enabled and pressing Ctrl-U?
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > Also, as this is a mailing list, please avoid
>> >>>> > > > > > > > > > > > > top-posting.
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > - Simon
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > I am using chained boot to test uboot as a
>> FIT
>> >>>> > > > > > > > > > > > > image so I I
>> >>>> > > > > >
>> >>>> > > > > > don't
>> >>>> > > > > > > > > > > > > have to
>> >>>> > > > > > > > > > > > > flash to spl flash.  Does
>> CONFIG_SPL_TEXT_BASE
>> >>>> > > > > > > > > > > > > need to be
>> >>>> > > > > >
>> >>>> > > > > > adjusted
>> >>>> > > > > > > > > > > > > for
>> >>>> > > > > > > > > > > > > chained boot?
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > I am using instructions to boot Linux for
>> Tegra
>> >>>> > > > > > > > > > > > > from
>> >>>> > > > > >
>> >>>> > > > > > sdcard/USB in
>> >>>> > > > > > > > > > > > > developer
>> >>>> > > > > > > > > > > > > mode.  I can boot L4T fine with kernel v3.10.
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > What mainline branch should I try?
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > On Mon, May 1, 2017 at 11:14 AM, Simon
>> Glass
>> >>>> > > > > > > > > > > > > > <
>> >>>> > > > > >
>> >>>> > > > > > sjg at chromium.org>
>> >>>> > > > > > > > > > > > > > wrote:
>> >>>> > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > Hi Matthew,
>> >>>> > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > On 1 May 2017 at 08:43, Matthew Gorski <
>> >>>> > > > > >
>> >>>> > > > > > matt.gorski at gmail.com>
>> >>>> > > > > > > > > > > > > > > wrote:
>> >>>> > > > > > > > > > > > > > > > I am porting u-boot to nyan_big and
>> need
>> >>>> > > > > > > > > > > > > > > > some input.  I
>> >>>> > > > > >
>> >>>> > > > > > have
>> >>>> > > > > > > > > > > > > > > > been
>> >>>> > > > > > > > > > > > > > > > searching
>> >>>> > > > > > > > > > > > > > > > high and low and found this thread
>> here:
>> >>>> > > > > > > > > > > > > > > > [U-Boot] [PATCH
>> >>>> > > > > >
>> >>>> > > > > > 0/20]
>> >>>> > > > > > > > > > > > > > > > tegra:
>> >>>> > > > > > > > > > > > > > > > Expand
>> >>>> > > > > > > > > > > > > > > > Nyan-big support
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > >  https://lists.denx.de/pipermai
>> l/u-boot/2
>> >>>> > > > > > > > > > > > > > > > 015-March/209530.
>> >>>> > > > > >
>> >>>> > > > > > html
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > > I have tried to build u-boot with the
>> >>>> > > > > > > > > > > > > > > > branch here:
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > > https://git.collabora.com/cgit
>> >>>> > > > > >
>> >>>> > > > > > /user/tomeu/u-boot.git/commit/?h=nyan-big
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > > and also the official chromium next
>> >>>> > > > > > > > > > > > > > > > branch
>> >>>> > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > Have you tried mainline U-Boot? It
>> already
>> >>>> > > > > > > > > > > > > > > supports nyan-big.
>> >>>> > > > > > > > > > > > > > > I'm
>> >>>> > > > > > > > > > > > > > > not
>> >>>> > > > > > > > > > > > > > > sure about the situation with the
>> >>>> > > > > > > > > > > > > > > downstream trees.
>> >>>> > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > > I followed building instructions here:
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > > https://www.chromium.org/chrom
>> >>>> > > > > >
>> >>>> > > > > > ium-os/firmware-porting-guide/
>> using-nv-u-boot-on-the-samsung
>> >>>> > > > > > -arm-chromebook
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > > I build with these commands:
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > > mkimage -e 0x81000100 -a 0x81000100 -f
>> >>>> > > > > > > > > > > > > > > > kernel-big.its
>> >>>> > > > > > > > > > > > > > > > kernel-u-boot
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > > (with and without the load address
>> >>>> > > > > > > > > > > > > > > > setting)
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > > vbutil_kernel --arch arm --pack
>> >>>> > > > > > > > > > > > > > > > kernel.bin --keyblock
>> >>>> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kerne
>> l.keyblock
>> >>>> > > > > > > > > > > > > > > > --signprivate
>> >>>> > > > > > > > > > > > > > > > /usr/share/vboot/devkeys/kerne
>> l_data_key.
>> >>>> > > > > > > > > > > > > > > > vbprivk
>> >>>> > > > > >
>> >>>> > > > > > --version 1
>> >>>> > > > > > > > > > > > > > > > --config
>> >>>> > > > > > > > > > > > > > > > dummy.txt --vmlinuz kernel-u-boot --
>> >>>> > > > > > > > > > > > > > > > bootloader dummy.txt
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > > I have had numerous failed attempts to
>> >>>> > > > > > > > > > > > > > > > boot uboot from
>> >>>> > > > > >
>> >>>> > > > > > sdcard
>> >>>> > > > > > > > > > > > > > > > mmcblk1p1
>> >>>> > > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > > Any help is appreciated I have only
>> >>>> > > > > > > > > > > > > > > > gotten a blank screen
>> >>>> > > > > > > > > > > > > > > > after
>> >>>> > > > > > > > > > > > > > > > weeks
>> >>>> > > > > > > > > > > > > > > > of
>> >>>> > > > > > > > > > > > > > > > flashing.  I can boot custom v3.10
>> >>>> > > > > > > > > > > > > > > > kernels so I assume I am
>> >>>> > > > > > > > > > > > > > > > using
>> >>>> > > > > > > > > > > > > > > > the
>> >>>> > > > > > > > > > > > > > > > correct building procedure.  Thanks in
>> >>>> > > > > > > > > > > > > > > > advance for help
>> >>>> > > > > >
>> >>>> > > > > > from
>> >>>> > > > > > > > > > > > > > > > the
>> >>>> > > > > > > > > > > > > > > > u-boot
>> >>>> > > > > > > > > > > > > > > > community.
>> >>>> > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > It is possible that it needs a particular
>> >>>> > > > > > > > > > > > > > > address due to
>> >>>> > > > > > > > > > > > > > > limitations
>> >>>> > > > > > > > > > > > > > > in the FIT support on Nyan. I'm not sure
>> >>>> > > > > > > > > > > > > > > what it is but
>> >>>> > > > > >
>> >>>> > > > > > might be
>> >>>> > > > > > > > > > > > > > > able
>> >>>> > > > > > > > > > > > > > > to take a look at some point.
>> >>>> > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > How are you building your SD card? Are
>> you
>> >>>> > > > > > > > > > > > > > > following some
>> >>>> > > > > > > > > > > > > > > instructions
>> >>>> > > > > > > > > > > > > > > from somewhere?
>> >>>> > > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > > > Regards,
>> >>>> > > > > > > > > > > > > > > Simon
>> >>>> > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > > > >
>> >>>> > > > > > > > >
>> >>>> > > > > > > > >
>> >>>> > > > > > >
>> >>>> > > > > > >
>> >>>> > > > >
>> >>>> > > > >
>> >>>> > > >
>> >>>> > > > _______________________________________________
>> >>>> > > > U-Boot mailing list
>> >>>> > > > U-Boot at lists.denx.de
>> >>>> > > > https://lists.denx.de/listinfo/u-boot
>> >>>>
>> >>>> --
>> >>>> Sjoerd Simons
>> >>>> Collabora Ltd.
>> >>>
>> >>>
>> >>
>> >
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> https://lists.denx.de/listinfo/u-boot
>>
>
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Simon Glass]

Hi,

On 5 May 2017 at 12:02, Matthew Gorski <matt.gorski@gmail.com> wrote:
>
>
>
> On Fri, May 5, 2017 at 1:54 PM, Thomas Hoff <thomashoffltd@gmail.com> wrote:
>>
>> Hey Matthew,
>>
>> Did you have any luck with this? I was attempting to do this a while back with no success.
>>
>> Cheers,
>>
>> Thomas
>
>
> No unfortunately not.  Simon was going to try himself at some point.  I have a few u-boot forks im dying to chain-boot on nyan so I hope there is some progress.  I think we need to see whats going on behind the scenes with a servo board and serial output because I can get u-boot to boot (i think) but it reboots immediately into recovery (no console on lcd display).
>
> Let hope Simon gets some time in the near future ;)

Just to follow up on this thread I sent a series to enable chain
booting on nyan-big.

Regards,
Simon

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Thomas Hoff]

Awesome! Thanks Simon.

Hey Matthew, you get any further with this?

Cheers,

Thomas

On Mon, Jun 5, 2017 at 12:59 PM, Simon Glass <sjg@chromium.org> wrote:

> Hi,
>
> On 5 May 2017 at 12:02, Matthew Gorski <matt.gorski@gmail.com> wrote:
> >
> >
> >
> > On Fri, May 5, 2017 at 1:54 PM, Thomas Hoff <thomashoffltd@gmail.com>
> wrote:
> >>
> >> Hey Matthew,
> >>
> >> Did you have any luck with this? I was attempting to do this a while
> back with no success.
> >>
> >> Cheers,
> >>
> >> Thomas
> >
> >
> > No unfortunately not.  Simon was going to try himself at some point.  I
> have a few u-boot forks im dying to chain-boot on nyan so I hope there is
> some progress.  I think we need to see whats going on behind the scenes
> with a servo board and serial output because I can get u-boot to boot (i
> think) but it reboots immediately into recovery (no console on lcd display).
> >
> > Let hope Simon gets some time in the near future ;)
>
> Just to follow up on this thread I sent a series to enable chain
> booting on nyan-big.
>
> Regards,
> Simon
>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Davide Baldo]

> Hi Sjoerd,
> On 25 February 2015 at 17:12, Sjoerd Simons
<<sjoerd.simons@collabora.co.uk
<http://lists.denx.de/mailman/listinfo/u-boot>> wrote:
>>* Hey Simon,
*>>>>* Incidentally i got acces to a Nyan big and wanted to start testing
*>>* u-boot on it. Unfortunately putting a uImage in a vboot signed blob to
*>>* chainload it from the primary bootloader like on the exynos based
*>>* chromebooks seemed not to work.
*>>>>* Do you have any good pointers how to use u-boot on nyan? (Ideally
*>>* without having to re-flash coreboot, as i would like to create images
*>>* people can easily test on a vanilla chromebook)
*
> No I don't sorry. I suppose in dev mode it should boot a signed image
> so if you put U-Boot in a FIT as with snow/pit it should work. But I
> don't have instructions...if you figure it out it would be good to put
> this info somewhere.

> Regards,
> Simon

Hi i'm trying to chain u-boot from an sdcard in a byan-big based
chromebook without having to overwrite the main boot, has someone
managed to do it?

Regards,Davide

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Simon Glass]

Hi Sjoerd,

On 30 March 2015 at 02:14, Sjoerd Simons <sjoerd.simons@collabora.co.uk> wrote:
> On Fri, 2015-02-27 at 22:11 -0700, Simon Glass wrote:
>> Hi Sjoerd,
>>
>> On 25 February 2015 at 17:12, Sjoerd Simons
>> <sjoerd.simons@collabora.co.uk> wrote:
>> > Hey Simon,
>> >
>> > Incidentally i got acces to a Nyan big and wanted to start testing
>> > u-boot on it. Unfortunately putting a uImage in a vboot signed blob to
>> > chainload it from the primary bootloader like on the exynos based
>> > chromebooks seemed not to work.
>> >
>> > Do you have any good pointers how to use u-boot on nyan? (Ideally
>> > without having to re-flash coreboot, as i would like to create images
>> > people can easily test on a vanilla chromebook)
>>
>> No I don't sorry. I suppose in dev mode it should boot a signed image
>> so if you put U-Boot in a FIT as with snow/pit it should work. But I
>> don't have instructions...if you figure it out it would be good to put
>> this info somewhere.
>
> Finally got time to play a bit with this. On the snow/peach boards the
> approach is to put u-boot in a legacy u-boot image (not a FIT image),
> which has the nice side-effect of re-locating u-boot before jumping to
> it.
>
> Unfortunately the depthcharge on the nyan boards appears not to support
> legacy images, only FIT images, which don't get relocated before jumping
> into the kernel blob. Long story short, on the nyan boards the FIT image
> gets loaded at 0x81000000 and the FIT images i created put the u-boot
> blob at an offset of 0xCC. After re-configuring CONFIG_SYS_TEXT_BASE to
> match i got u-boot starting \o/ ;)
>
> Unfortunately the board seems to hard hang when it tries to enable/use
> the data cache. Enabling CONFIG_SYS_DCACHE_OFF makes it get to the
> u-boot prompt. Unfortunately neither MMC (didn't detect card) nor USB
> (failed to get descriptor from my usb network dongle) worked so i
> couldn't try booting a kernel just, but it's start.
>
> Simon, does data cache/MMC/USB work properly when booting u-boot
> "natively" rather then chainloading from coreboot or does it have
> similar issues?
>
> Fwiw, I've attached the output of u-boot running onthe board (with
> CONFIG_SYS_DCACHE_OFF enabled).
>

Nice work!

I have the data cache enabled. USB does not work. MMC works OK (I can
boot a kernel from the internal eMMC).

I'm not sure about the cache, it seems odd. I wonder if there is
something broken in the cache set, and U-Boot needs to fix it?

Regards,
Simon

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Sjoerd Simons]

On Fri, 2015-02-27 at 22:11 -0700, Simon Glass wrote:
> Hi Sjoerd,
> 
> On 25 February 2015 at 17:12, Sjoerd Simons
> <sjoerd.simons@collabora.co.uk> wrote:
> > Hey Simon,
> >
> > Incidentally i got acces to a Nyan big and wanted to start testing
> > u-boot on it. Unfortunately putting a uImage in a vboot signed blob to
> > chainload it from the primary bootloader like on the exynos based
> > chromebooks seemed not to work.
> >
> > Do you have any good pointers how to use u-boot on nyan? (Ideally
> > without having to re-flash coreboot, as i would like to create images
> > people can easily test on a vanilla chromebook)
> 
> No I don't sorry. I suppose in dev mode it should boot a signed image
> so if you put U-Boot in a FIT as with snow/pit it should work. But I
> don't have instructions...if you figure it out it would be good to put
> this info somewhere.

Finally got time to play a bit with this. On the snow/peach boards the
approach is to put u-boot in a legacy u-boot image (not a FIT image),
which has the nice side-effect of re-locating u-boot before jumping to
it. 

Unfortunately the depthcharge on the nyan boards appears not to support
legacy images, only FIT images, which don't get relocated before jumping
into the kernel blob. Long story short, on the nyan boards the FIT image
gets loaded at 0x81000000 and the FIT images i created put the u-boot
blob at an offset of 0xCC. After re-configuring CONFIG_SYS_TEXT_BASE to
match i got u-boot starting \o/ ;)

Unfortunately the board seems to hard hang when it tries to enable/use
the data cache. Enabling CONFIG_SYS_DCACHE_OFF makes it get to the
u-boot prompt. Unfortunately neither MMC (didn't detect card) nor USB
(failed to get descriptor from my usb network dongle) worked so i
couldn't try booting a kernel just, but it's start.

Simon, does data cache/MMC/USB work properly when booting u-boot
"natively" rather then chainloading from coreboot or does it have
similar issues?

Fwiw, I've attached the output of u-boot running onthe board (with
CONFIG_SYS_DCACHE_OFF enabled).



-- 
Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Collabora Ltd.
-------------- next part --------------

U-Boot 2015.04-rc4-00125-g662e2ac-dirty (Mar 30 2015 - 00:17:30)


TEGRA124

Model: Acer Chromebook 13 CB5-311

DRAM:  2 GiB

MMC:   Tegra SD/MMC: 0, Tegra SD/MMC: 1, Tegra SD/MMC: 2

Card did not respond to voltage select!

MMC init failed

Using default environment


In:    serial

Out:   serial

Err:   serial

Net:   Net Initialization Skipped

No ethernet found.

Hit any key to stop autoboot:  2 \b\b\b 1 \b\b\b 0 

MMC: no card present

Card did not respond to voltage select!

starting USB...

USB0:   USB EHCI 1.10

scanning bus 0 for devices... EHCI timed out on TD - token=0x80008c80

EHCI timed out on TD - token=0x80008d80

EHCI timed out on TD - token=0x80008c80

EHCI timed out on TD - token=0x80008c80

usb_get_configuration_no: failed to get descriptor - too long: 65460

usb_new_device: Cannot read configuration, skipping device 58f4:fffa

1 USB Device(s) found

USB1:   USB EHCI 1.10

scanning bus 1 for devices... 1 USB Device(s) found

       scanning usb for storage devices... 0 Storage Device(s) found

       scanning usb for ethernet devices... 0 Ethernet Device(s) found


USB device 0: unknown device

No ethernet found.

missing environment variable: pxeuuid

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/00000000

No ethernet found.

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/0000000

No ethernet found.

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/000000

No ethernet found.

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/00000

No ethernet found.

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/0000

No ethernet found.

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/000

No ethernet found.

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/00

No ethernet found.

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/0

No ethernet found.

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/default-arm-tegra124

No ethernet found.

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/default-arm

No ethernet found.

missing environment variable: bootfile

Retrieving file: pxelinux.cfg/default

No ethernet found.

Config file not found

No ethernet found.

Tegra124 (Nyan-big) # 

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Simon Glass]

Hi Sjoerd,

On 25 February 2015 at 17:12, Sjoerd Simons
<sjoerd.simons@collabora.co.uk> wrote:
> Hey Simon,
>
> Incidentally i got acces to a Nyan big and wanted to start testing
> u-boot on it. Unfortunately putting a uImage in a vboot signed blob to
> chainload it from the primary bootloader like on the exynos based
> chromebooks seemed not to work.
>
> Do you have any good pointers how to use u-boot on nyan? (Ideally
> without having to re-flash coreboot, as i would like to create images
> people can easily test on a vanilla chromebook)

No I don't sorry. I suppose in dev mode it should boot a signed image
so if you put U-Boot in a FIT as with snow/pit it should work. But I
don't have instructions...if you figure it out it would be good to put
this info somewhere.

Regards,
Simon

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Sjoerd Simons]

Hey Simon,

Incidentally i got acces to a Nyan big and wanted to start testing
u-boot on it. Unfortunately putting a uImage in a vboot signed blob to
chainload it from the primary bootloader like on the exynos based
chromebooks seemed not to work. 

Do you have any good pointers how to use u-boot on nyan? (Ideally
without having to re-flash coreboot, as i would like to create images
people can easily test on a vanilla chromebook)

On Tue, 2015-02-17 at 15:29 -0700, Simon Glass wrote:
> This series expands Nyan-big support:
> 
> - Enable Chrome OS EC, so that the keyboard works
> - Add some extra clock and pre-kernel init required for reliable operation
> - Add Chrome OS environment variables, including 'run nvboot' to allow
> booting Chrome OS more easily
> 
> Still missing are audio and USB.
> 
> 
> Doug Anderson (1):
>   Add Chrome OS config header
> 
> Simon Glass (19):
>   dm: spi: Avoid setting the speed with every transfer
>   cros_ec: Show the protocol version in the debug message
>   cros_ec: Handle the single duplex requirement in cros_ec
>   tegra: Provide more accurate microsecond time
>   tegra: cros_ec: Add tegra support for Chrome OS EC
>   tegra: spi: Drop the claim_bus() method to correct delays
>   dm: tegra: cros_ec: Enable Chrome OS EC on Nyan-big
>   dm: gpio: Add an implementation for gpio_get_number()
>   tegra: spi: Support slow SPI rates
>   tegra: clock: Support enabling external clocks
>   tegra: clock: Adjust PLL access to avoid a warning
>   tegra: Introduce SRAM repair on tegra124
>   tegra: Add missing tegra124 peripherals
>   tegra: Increase maximum arguments to 32
>   tegra: lcd: Tidy up clock init
>   tegra: Allow board-specific init
>   tegra: nyan-big: Add additional clock and kernel init
>   tegra: config: Allow Chrome OS environment settings to be included
>   tegra: config: nyan-big: Add options required by Chrome OS boot
> 
>  arch/arm/cpu/tegra-common/Makefile                |   1 +
>  arch/arm/cpu/tegra-common/clock.c                 |  24 +-
>  arch/arm/cpu/tegra-common/powergate.c             |  20 +-
>  arch/arm/cpu/tegra-common/timer.c                 |  87 ++++
>  arch/arm/cpu/tegra124-common/clock.c              |   2 +-
>  arch/arm/dts/tegra124-nyan-big.dts                |   6 +-
>  arch/arm/include/asm/arch-tegra/clock.h           |   8 +
>  arch/arm/include/asm/arch-tegra/sys_proto.h       |   7 +
>  arch/arm/include/asm/arch-tegra124/clock-tables.h |  12 +-
>  arch/arm/include/asm/arch-tegra124/flow.h         |  12 +
>  board/nvidia/common/board.c                       |   8 +-
>  board/nvidia/nyan-big/nyan-big.c                  |  76 ++++
>  configs/nyan-big_defconfig                        |   5 +
>  drivers/gpio/gpio-uclass.c                        |  12 +
>  drivers/misc/cros_ec.c                            |   3 +-
>  drivers/misc/cros_ec_spi.c                        |  23 +-
>  drivers/spi/spi-uclass.c                          |   9 +-
>  drivers/spi/tegra114_spi.c                        |  51 +--
>  drivers/video/tegra124/tegra124-lcd.c             |   4 +-
>  include/configs/chromeos.h                        | 464 ++++++++++++++++++++++
>  include/configs/nyan-big.h                        |   8 +
>  include/configs/tegra-common-post.h               |  15 +-
>  include/configs/tegra-common.h                    |   2 +-
>  include/spi.h                                     |   3 +
>  24 files changed, 804 insertions(+), 58 deletions(-)
>  create mode 100644 arch/arm/cpu/tegra-common/timer.c
>  create mode 100644 include/configs/chromeos.h
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6170 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150226/2aad3b4a/attachment.bin>

[U-Boot] [PATCH 0/20] tegra: Expand Nyan-big support

[Simon Glass]

This series expands Nyan-big support:

- Enable Chrome OS EC, so that the keyboard works
- Add some extra clock and pre-kernel init required for reliable operation
- Add Chrome OS environment variables, including 'run nvboot' to allow
booting Chrome OS more easily

Still missing are audio and USB.


Doug Anderson (1):
  Add Chrome OS config header

Simon Glass (19):
  dm: spi: Avoid setting the speed with every transfer
  cros_ec: Show the protocol version in the debug message
  cros_ec: Handle the single duplex requirement in cros_ec
  tegra: Provide more accurate microsecond time
  tegra: cros_ec: Add tegra support for Chrome OS EC
  tegra: spi: Drop the claim_bus() method to correct delays
  dm: tegra: cros_ec: Enable Chrome OS EC on Nyan-big
  dm: gpio: Add an implementation for gpio_get_number()
  tegra: spi: Support slow SPI rates
  tegra: clock: Support enabling external clocks
  tegra: clock: Adjust PLL access to avoid a warning
  tegra: Introduce SRAM repair on tegra124
  tegra: Add missing tegra124 peripherals
  tegra: Increase maximum arguments to 32
  tegra: lcd: Tidy up clock init
  tegra: Allow board-specific init
  tegra: nyan-big: Add additional clock and kernel init
  tegra: config: Allow Chrome OS environment settings to be included
  tegra: config: nyan-big: Add options required by Chrome OS boot

 arch/arm/cpu/tegra-common/Makefile                |   1 +
 arch/arm/cpu/tegra-common/clock.c                 |  24 +-
 arch/arm/cpu/tegra-common/powergate.c             |  20 +-
 arch/arm/cpu/tegra-common/timer.c                 |  87 ++++
 arch/arm/cpu/tegra124-common/clock.c              |   2 +-
 arch/arm/dts/tegra124-nyan-big.dts                |   6 +-
 arch/arm/include/asm/arch-tegra/clock.h           |   8 +
 arch/arm/include/asm/arch-tegra/sys_proto.h       |   7 +
 arch/arm/include/asm/arch-tegra124/clock-tables.h |  12 +-
 arch/arm/include/asm/arch-tegra124/flow.h         |  12 +
 board/nvidia/common/board.c                       |   8 +-
 board/nvidia/nyan-big/nyan-big.c                  |  76 ++++
 configs/nyan-big_defconfig                        |   5 +
 drivers/gpio/gpio-uclass.c                        |  12 +
 drivers/misc/cros_ec.c                            |   3 +-
 drivers/misc/cros_ec_spi.c                        |  23 +-
 drivers/spi/spi-uclass.c                          |   9 +-
 drivers/spi/tegra114_spi.c                        |  51 +--
 drivers/video/tegra124/tegra124-lcd.c             |   4 +-
 include/configs/chromeos.h                        | 464 ++++++++++++++++++++++
 include/configs/nyan-big.h                        |   8 +
 include/configs/tegra-common-post.h               |  15 +-
 include/configs/tegra-common.h                    |   2 +-
 include/spi.h                                     |   3 +
 24 files changed, 804 insertions(+), 58 deletions(-)
 create mode 100644 arch/arm/cpu/tegra-common/timer.c
 create mode 100644 include/configs/chromeos.h

-- 
2.2.0.rc0.207.ga3a616c