Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Viktorin <viktorin@rehivetech.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patch: new board Socrates Cyclone 5
Date: Tue, 1 Aug 2017 13:07:11 +0200	[thread overview]
Message-ID: <20170801130711.16efdcf0.viktorin@rehivetech.com> (raw)
In-Reply-To: <20170801100248.smfxvyhxk624nnwq@ed>

On Tue, 1 Aug 2017 12:02:48 +0200
Lionel Flandrin <lionel@svkt.org> wrote:

> On Tue, Aug 01, 2017 at 10:53:03AM +0200, Thomas Petazzoni wrote:
> > Hello,
> > 
> > On Tue, 1 Aug 2017 09:54:56 +0200, Lionel Flandrin wrote:
> >   
> > > Can I access this preloader.bin somewhere? I could check if there's
> > > anything obviously special about it.  
> > 
> > The preloader.bin is part of the patch that Micha? sent:
> > 
> >   https://patchwork.ozlabs.org/patch/795350/  
> 
> Ah, I missed that, thank you for pointing it out.
> 
> It's definitely a mkpimage file. A simple way to validate that is to
> check offset 0x40:
> 
> @0x40: [41 53 30 31]     Magic ("AS01")
> @0x44: [00]              Version (v0 for Cyclone V)
> @0x45: [00]              Flags
> @0x46: [48 25]           Program length in words, so 38176B
> @0x48: [00 00]           Not used ("spare")
> @0x4a: [62 01]           Header checksum
> 
> Then at the end of the file you have a 4 byte CRC which I haven't
> bothered to validate.
> 
> So nothing out of the ordinary as far as I can tell. In particular I
> can't see anything ressembling a cryptographic signature at the
> beginning or end of the file. Looks like a regular u-boot SPL to me.
> 
> I can't really say more about it, I don't have a Cyclone V board at
> the moment. My advice would be to validate that the SPL generated by

Hi, I've got a Socrates Cyclone V available and so I am able to test.
If there are any patches to test, I can probably help.

Regards
Jan

[...]

> 
> > And the very reason why I opened up this thread is because it's not
> > great to have pre-built bootloader images in the Buildroot tree.  
> 
> I agree completely.
> 
> > Best regards,
> > 
> > Thomas  
> 



-- 
   Jan Viktorin                  E-mail: Viktorin at RehiveTech.com
   System Architect              Web:    www.RehiveTech.com
   RehiveTech
   Brno, Czech Republic

  reply	other threads:[~2017-08-01 11:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-30 12:51 [Buildroot] Patch: new board Socrates Cyclone 5 Michał Łyszczek
2017-07-30 13:15 ` Thomas Petazzoni
2017-08-01  7:54   ` Lionel Flandrin
2017-08-01  8:53     ` Thomas Petazzoni
2017-08-01 10:02       ` Lionel Flandrin
2017-08-01 11:07         ` Jan Viktorin [this message]
2017-08-01 11:21           ` Thomas Petazzoni
2017-08-01 18:08             ` Michał Łyszczek
2017-08-01 18:45               ` Michał Łyszczek
2017-08-01 19:32                 ` Thomas Petazzoni

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=20170801130711.16efdcf0.viktorin@rehivetech.com \
    --to=viktorin@rehivetech.com \
    --cc=buildroot@busybox.net \
    /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