public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andre Schwarz <andre.schwarz@matrix-vision.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] data alignment problem with redundant env
Date: Wed, 06 Apr 2011 11:05:45 +0200	[thread overview]
Message-ID: <4D9C2CE9.4050703@matrix-vision.de> (raw)
In-Reply-To: <20110331160119.DB1D9F03208@gemini.denx.de>

Wolfgang,

>>> Which board would that be?  I don't see this on any board I tested.
>> it is mvblm7 (=MPC8343) and a new MPC8377 based one waiting for
>> the merge window to open.
>>
>>
>> I'm using a gcc-4.3.3 from OpenEmbedded/Angstrom ... if this matters at all.
> Can you please try and use anothe rtool chain, say good ole ELDK 4.2
> for a test?
ok - that's it.

Compiling with ELDK 4.2 gives an environment as expected.

4 bytes crc32 + 1 byte redundancy flags + data :

mvBL-M7> md ff800000 10
ff800000: 56900c81 01626175 64726174 653d3131    V....baudrate=11
ff800010: 35323030 00626f6f 74617267 733d726f    5200.bootargs=ro

Using OpenEmbedded's (Angstrom) gcc 4.3.3 produces a corrupted
layout with data having a 16-Bit alignment leading to a 1 byte offset when
redundancy is used.


Will stick to ELDK 4.2 for U-Boot.

Problem solved, but I'm still irritated how easily things can be broken 
nowadays ...


Regards,
Andr?


MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner

      parent reply	other threads:[~2011-04-06  9:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 15:30 [U-Boot] data alignment problem with redundant env Andre Schwarz
2011-03-31 15:39 ` Wolfgang Denk
2011-03-31 15:48   ` Andre Schwarz
2011-03-31 16:01     ` Wolfgang Denk
2011-03-31 16:41       ` Andre Schwarz
2011-04-06  9:05       ` Andre Schwarz [this message]

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=4D9C2CE9.4050703@matrix-vision.de \
    --to=andre.schwarz@matrix-vision.de \
    --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