public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Bug#897671: u-boot does not work on sheevaplug
Date: Sat, 05 May 2018 16:04:08 -0700	[thread overview]
Message-ID: <87a7tdpuvr.fsf@aikidev.net> (raw)
In-Reply-To: <3ef09240-8cbe-3ad1-e070-9c4afd4cb1c0@web.de>

Hello U-Boot.

Markus Krebs discovered that the sheevaplug target has again grown and
installation overlaps where the u-boot env is saved since u-boot
~2017.09. Running saveenv overwrites u-boot, and installing u-boot
overwrites any prior environment settings.

More detail on the bug report in Debian:

  https://bugs.debian.org/897671

We don't carry any patches for the sheevaplug u-boot target in Debian,
so this is likely also an issue upstream. Who are the current
maintainers for sheevaplug in u-boot upstream?

A brief summary of the current findings:

On 2018-05-05, Markus Krebs wrote:
> Am 05.05.2018 um 20:36 schrieb Markus Krebs:
>> Am 05.05.2018 um 20:35 schrieb Martin Michlmayr:
>>> * Markus Krebs <Markus.Krebs@web.de> [2018-05-05 20:32]:
>>>> I got it. Indeed it has to to with the size of u-boot.
>>>
>>> Does it boot?
>>>
>> 
>> Yes it does.
>
> ... and no longer so, when I "saveenv" :-(
>
> I downloaded u-boot via git; I guess that the config for u-boot for 
> sheevaplug is already broken upstream (in sheevaplug.h):
>
>    #define CONFIG_ENV_SIZE                 0x20000 /* 128k */
>    #define CONFIG_ENV_ADDR                 0x80000
>    #define CONFIG_ENV_OFFSET               0x80000 /* env starts here */
>
> but the environment shouldn't start at 0x80000 when u-boot.kwb > 524 KB; 
> in this case 'saveenv' overwrites u-boot (?).
> Changing 0x80000 to 0xa0000 helps ; I compiled a u-boot.kwb from the 
> so-modified sources, and now I can start Debian fine.

It looks like it was bumped from 0x60000 to 0x80000 in 2014:

  http://git.denx.de/?p=u-boot.git;a=commit;h=4dfb0e4d3e75763d6fbe8788316bea9ba23e8e01

If 0x80000 isn't enough, there might be some features in the config to
experiment with removing, or it may need to be bumped again.

Not sure what the best coarse of action is.


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180505/ce18391a/attachment.sig>

       reply	other threads:[~2018-05-05 23:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180504104336.2n53z6or65rrjzrw@jirafa.cyrius.com>
     [not found] ` <87muxfpgyq.fsf@aikidev.net>
     [not found]   ` <20180504171113.rsc4dzcnfnuesall@jirafa.cyrius.com>
     [not found]     ` <5411eb5c-e400-5bea-80bc-e231560ca76d@web.de>
     [not found]       ` <73c25c9a-faba-a7ea-4d3d-7e1fe932eda6@web.de>
     [not found]         ` <352dbeca-a872-de5f-60bf-d7a409cbecb8@web.de>
     [not found]           ` <20180505091354.abo3khggep6sa7jm@jirafa.cyrius.com>
     [not found]             ` <8afc29d1-8ae3-18e3-8bb9-22d13814efe4@web.de>
     [not found]               ` <84c2c623-5d6d-e6fa-bc2b-b4082dca5dc2@web.de>
     [not found]                 ` <20180505183529.auxstq2qilg43ttm@jirafa.cyrius.com>
     [not found]                   ` <57d24e3c-aff7-ab81-c08a-a1362bc42ce2@web.de>
     [not found]                     ` <152540843251.13599.4428160353240912722.reportbug@server2.notar-krebs.de>
     [not found]                       ` <3ef09240-8cbe-3ad1-e070-9c4afd4cb1c0@web.de>
2018-05-05 23:04                         ` Vagrant Cascadian [this message]
2018-05-06  0:13                           ` [U-Boot] Bug#897671: u-boot does not work on sheevaplug Tom Rini
2018-05-06  7:00                             ` drEagle
2018-05-08 20:22                             ` Vagrant Cascadian
2018-05-08 20:54                               ` Vagrant Cascadian
2018-05-09  8:19                                 ` Markus Krebs
2018-05-09 12:33                                   ` klaus.goger at theobroma-systems.com
2018-05-09 15:35                                     ` Markus Krebs
2018-05-10 18:10                                       ` Vagrant Cascadian
2018-05-10 19:05                                         ` Markus Krebs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a7tdpuvr.fsf@aikidev.net \
    --to=vagrant@debian.org \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox