[U-Boot] Help needed on Colibri T20 - Iris Board

[Simon Glass]

Hi Stéphane,

On Fri, Jan 13, 2012 at 6:03 AM, Stéphane Carvalho
<carvalho.stephane at gmail.com> wrote:
> Hi guys,
>
> Here's the situation:
>
> We applied the following patches to an original u-boot source code (2011.09
> version):
>
> [U-Boot] [PATCH 1/2] Tegra2: Make XTal speed configurable
> [U-Boot] [PATCH 2/2] Tegra2: Add support for Toradex Colibri T20 board
>
> And we use the antmicro patches for the Colibri T20 available
> on http://antmicro.com/blog.html (category ARM)
> Their patches are used to add the USB drivers for using the USB-to-Ethernet
> port.

OK. There is a USB series on the list also. I can see a tar file on
that web page but didn't look at it. I presume it works for you ok so
that is fine.

>
> Then, we take the following patches:
>
> [U-Boot] [PATCH v2 0/8] Tegra2: Implement SPI flash and saved environment
>
> The problem is that this patch is for the Seaboard. We adapted it for the
> Iris Board but this ain't working. We wonder if this patch is the right one.

Well the series includes the driver support but also turns on the
environment options in seaboard.h. So at the least you would need to
turn these options on in your config file.

Also check that the pinmux is being set in tegra2_spi.c. The final few
patches to do this cleanly for Seaboard were NAKed (NS16550 changes
and buffering) so this might be slightly different on your platform.
It looks like you use UARTA so won't have the SPI/UART conflict, but
you still need to make sure that SPI's pinmux is enabled.

Regards,
Simon
>
>
> 2012/1/11 Simon Glass <sjg at chromium.org>
>>
>> Hi Stéphane,
>>
>> On Wed, Jan 11, 2012 at 1:52 AM, Stéphane Carvalho
>> <carvalho.stephane at gmail.com> wrote:
>> > We are 2 engineering students from Fribourg, Switzerland working on a
>> > embedded systems project.
>> >
>> > The fact is that we're looking to setup U-Boot on a Colibri Iris Board
>> > using
>> > the Colibri T20 module with NVIDIA Tegra 2 processor.
>> >
>> > Since the Iris board is a relatively new board, it is difficult for us
>> > to
>> > find information about it.
>>
>> Sorry I don't know anything about that particular board either.
>>
>> >
>> > We managed to install a recent uboot on the board but it is not very
>> > efficient. The major problem is that we aren't able to run the saveenv
>> > command in order to save the environnement. Does anyone have any ideas
>> > about
>> > the problem? Or patches to recommend us?
>>
>> Where is your environment supposed to be stored? If you are booting
>> from NAND or MMC then you could store it there. There are various
>> CONFIG_ENV_IS_IN_... variables to define depending on where you want
>> the environment. The README file lists each of these and explains how
>> to use them. You also need to define CONFIG_CMD_SAVEENV or perhaps
>> better #include <config_default.h>.
>>
>> >
>> > We don't have much experience in embedded systems so a little help from
>> > you
>> > would be much appreciated.
>>
>> OK, please reply on this thread if you have further questions.
>>
>> >
>> > Thank you in advance
>>
>> Regards,
>> Simon
>
>