[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 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

>
> 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 at chromium.org> wrote:
>
> Hi Matthew,
>
> On 1 May 2017 at 09:37, Matthew Gorski <matt.gorski 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/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
>>
>>
>
>
>