[U-Boot] Tegra board problems

[Simon Glass]

Hi Stephen,

On 25 November 2014 at 09:25, Stephen Warren <swarren at wwwdotorg.org> wrote:
>
> On 11/25/2014 09:16 AM, Simon Glass wrote:
>>
>> Hi Stephen,
>>
>> On 25 November 2014 at 09:11, Stephen Warren <swarren at wwwdotorg.org> wrote:
>>>
>>> On 11/24/2014 09:03 PM, Simon Glass wrote:
>>>>
>>>>
>>>> Hi,
>>>>
>>>> I'm a bit messed up with my testing now.
>>>
>>>
>>> ...
>>>>
>>>>
>>>> 2. beaver: I cannot get mainline U-Boot to boot a kernel. In fact
>>>> 'part list mmc 0' just prints an error:
>>>>
>>>> ## Unknown partition table
>>>>
>>>> It is getting a partition ID of 0. Is there something wrong with
>>>> Beaver's mmc support in mainline?
>>>
>>>
>>>
>>> I just built commit 2a82ec77d27e "Prepare v2015.01-rc2" and both eMMC and SD
>>> appear to work.
>>>
>>> Do you have a valid partition table on the eMMC? If you installed L4T there
>>> rather than partitioning it yourself, note that L4T uses a non-standard
>>> "tegra PT" partition table format. Some newer versions of L4T also include a
>>> backup GPT that makes some of the partitions available in a more standard
>>> way, but IIUC there's never a primary GPT. I don't recall if the version of
>>> L4T for Beaver was new enough to do even that though. Your best bet is to
>>> use standard tools to install a complete GPT and then install a Linux distro
>>> on top of that.
>>>
>>> Tegra30 (Beaver) # part list mmc 0
>>>
>>> Partition Map for MMC device 0  --   Partition Type: EFI
>>>
>>> Part    Start LBA       End LBA         Name
>>>          Attributes
>>>          Type GUID
>>>          Partition GUID
>>>    1     0x00000800      0x01da97ff      ""
>>>          attrs:  0x0000000000000000
>>>          type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
>>>          guid:   ac3c736e-a29b-43d4-9819-4cf4fd84c3b0
>>>
>>> Tegra30 (Beaver) # part list mmc 1
>>>
>>> Partition Map for MMC device 1  --   Partition Type: EFI
>>>
>>> Part    Start LBA       End LBA         Name
>>>          Attributes
>>>          Type GUID
>>>          Partition GUID
>>>    1     0x00000022      0x003b9132      ""
>>>          attrs:  0x0000000000000000
>>>          type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
>>>          guid:   b2f82cda-2535-4779-b467-094a210fbae7
>>>
>>
>> OK thank you, that could be my problem. I'll try installing a new GPT.
>>
>> Will try out the Jetson and see if I can get it running again. So does
>> that mean as shipped it runs an Android boot loader and then jumps to
>> U-Boot?
>
>
> It probably depends on which L4T release you have.
>
> I think the following is accurate:
>
> The first L4T releases for Jetson may have only supported the Android boot loader.
>
> A later release certainly supported either the Android boot loader or U-Boot. You had to choose which to install at flashing time. The Android boot loader is/was the default, and is/was what is installed at the factory. In either case, there's no chain-loading of boot loaders, simply a choice of which to put into flash.
>
> I believe the latest release only contains U-Boot, or perhaps supports both with U-Boot as the default, but I haven't validated that, nor whether it's actually shipped yet.

Thanks for the info, very helpful.

Regards,
Simon