Trimslice with 1GB of RAM and DTB now working

[Brendan Conoboy]

Hi folks,

The people at Compulab sent me a pointer for how to fix the problem with 
the trimslice not booting using the latest kernel.  It's as simple as 
setting a couple new uboot environment variables.  See:

http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#U-Boo...

This works for me!  My trimslice is now running 
3.8.5-201.fc18.armv7hl.tegra with 1GB of memory.

-- 
Brendan Conoboy / Red Hat, Inc. / blc(a)redhat.com

[d.marlin]

On 04/15/2013 10:04 AM, Brendan Conoboy wrote:
>  Hi folks,
>
>  The people at Compulab sent me a pointer for how to fix the problem 
>  with the trimslice not booting using the latest kernel. It's as simple 
>  as setting a couple new uboot environment variables.  See:
>
>
> http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#U-Boo...
>
>
>
>  This works for me!  My trimslice is now running 
>  3.8.5-201.fc18.armv7hl.tegra with 1GB of memory. 
Since this "work-around" was noted for v2010.09-1.01, but v2010.09-1.03 
is the latest (that I see on their website), has this been addressed in 
the newer versions (variables pre-defined in the firmware release)?  If 
not, will it be addressed in the next release?  If these settings are 
"required", there should be no need for every user to add them manually.


d.marlin

[Brendan Conoboy]

On 04/15/2013 11:50 AM, David A. Marlin wrote:
>  Since this "work-around" was noted for v2010.09-1.01, but
> v2010.09-1.03
>  is the latest (that I see on their website), has this been addressed in
>  the newer versions (variables pre-defined in the firmware release)?  If
>  not, will it be addressed in the next release?  If these settings are
>  "required", there should be no need for every user to add them manually.
Yes, I would hope they will issue an updated uboot, but do not know 
their plans.  We shouldn't count on them doing this, though.  If 
somebody else will confirm this fixes it for them as well I will update 
the wiki with the advice (gru-boot will use it as well).

-- 
Brendan Conoboy / Red Hat, Inc. / blc(a)redhat.com

[Peter Robinson]

On Mon, Apr 15, 2013 at 7:50 PM, David A. Marlin <dmarlin(a)redhat.com&gt; wrote:
>  On 04/15/2013 10:04 AM, Brendan Conoboy wrote:
> >
> > Hi folks,
> >
> > The people at Compulab sent me a pointer for how to fix the problem with
> > the trimslice not booting using the latest kernel. It's as simple as setting
> > a couple new uboot environment variables.  See:
> >
> >
> >
> http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#U-Boo...
> >
> > This works for me!  My trimslice is now running
> > 3.8.5-201.fc18.armv7hl.tegra with 1GB of memory.
>
>
>  Since this "work-around" was noted for v2010.09-1.01, but v2010.09-1.03 is
>  the latest (that I see on their website), has this been addressed in the
>  newer versions (variables pre-defined in the firmware release)?  If not,
>  will it be addressed in the next release?  If these settings are "required",
>  there should be no need for every user to add them manually. 
You're looking at the non DTS versions, this issue doesn't affect
those. This is for the 2012* DTS releases the latest of which is
v2012.04-1.02

www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#U-Boot_envir...

Peter

[d.marlin]

On 04/15/2013 01:58 PM, Peter Robinson wrote:
>  On Mon, Apr 15, 2013 at 7:50 PM, David A. Marlin
> <dmarlin(a)redhat.com&gt; wrote:
> > On 04/15/2013 10:04 AM, Brendan Conoboy wrote:
> >> Hi folks,
> >>
> >> The people at Compulab sent me a pointer for how to fix the problem with
> >> the trimslice not booting using the latest kernel. It's as simple as setting
> >> a couple new uboot environment variables.  See:
> >>
> >>
> >>
> http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#U-Boo...
> >>
> >> This works for me!  My trimslice is now running
> >> 3.8.5-201.fc18.armv7hl.tegra with 1GB of memory.
> >
> > Since this "work-around" was noted for v2010.09-1.01, but v2010.09-1.03 is
> > the latest (that I see on their website), has this been addressed in the
> > newer versions (variables pre-defined in the firmware release)?  If not,
> > will it be addressed in the next release?  If these settings are
> "required",
> > there should be no need for every user to add them manually.
>  You're looking at the non DTS versions, this issue doesn't affect
>  those. This is for the 2012* DTS releases the latest of which is
>  v2012.04-1.02
>
>  www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#U-Boot_envir...
>
>  Peter 
You are correct, so v2012.04-1.02 is the latest and it has the issue.  
Again, hopefully they will fix this in the next release (soon).


d.marlin
========

[Hans de Goede]

Hi,

>  On 04/15/2013 10:04 AM, Brendan Conoboy wrote:
> >
> > Hi folks,
> >
> > The people at Compulab sent me a pointer for how to fix the problem with
> > the trimslice not booting using the latest kernel. It's as simple as setting
> > a couple new uboot environment variables.  See:
> >
> >
> >
> http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#U-Boo...
> >
> > This works for me!  My trimslice is now running
> > 3.8.5-201.fc18.armv7hl.tegra with 1GB of memory.
>  
Oh, interesting, so I've finally made the jump on my trimslice from
the stock kernel to 3.8.7-201.fc18.armv7hl.tegra

I've got things working, but this was not a smooth ride. The wiki
is wrong wrt the instructions for putting the dtb in place, it says:

###

ln -s /boot/dtb-<kernel-version> /boot/dtbs

For example for 'kernel-tegra-3.7.5-202.fc18.armv7hl'

ln -s /boot/dtb-3.7.5-202.fc18.armv7hl.tegra /boot/dtbs

###

But in uboot /boot is / so it should be a relative symlink
to work in both environments!

I know it is a wiki, so I've already updated it :) I just wanted to
make sure others reading this thread are aware of this too.

Regards,

Hans

[Peter Robinson]

On Mon, Apr 15, 2013 at 4:04 PM, Brendan Conoboy <blc(a)redhat.com&gt; wrote:
>  Hi folks,
>
>  The people at Compulab sent me a pointer for how to fix the problem with the
>  trimslice not booting using the latest kernel.  It's as simple as setting a
>  couple new uboot environment variables.  See:
>
>
> http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#U-Boo...
>
>  This works for me!  My trimslice is now running 3.8.5-201.fc18.armv7hl.tegra
>  with 1GB of memory. 
Is it a persistent setting or one that needs to be set in the boot.cmd
on each boot?

Peter

[Brendan Conoboy]

On 04/15/2013 11:53 AM, Peter Robinson wrote:
>  On Mon, Apr 15, 2013 at 4:04 PM, Brendan Conoboy
> <blc(a)redhat.com&gt; wrote:
> > Hi folks,
> >
> > The people at Compulab sent me a pointer for how to fix the problem with the
> > trimslice not booting using the latest kernel.  It's as simple as setting a
> > couple new uboot environment variables.  See:
> >
> >
> http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater#U-Boo...
> >
> > This works for me!  My trimslice is now running 3.8.5-201.fc18.armv7hl.tegra
> > with 1GB of memory.
>
>  Is it a persistent setting or one that needs to be set in the boot.cmd
>  on each boot? 
If you run saveenv as they suggest it will be persistent.  I'm adding 
the setting to gru-boot to ensure it's always there.

-- 
Brendan Conoboy / Red Hat, Inc. / blc(a)redhat.com