public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Re-introducing support for OLD hardware
Date: Mon, 16 Apr 2018 13:10:34 +0200	[thread overview]
Message-ID: <20180416131034.5eaeb409@jawa> (raw)
In-Reply-To: <CAL+A2ONkJZ-Ggk4xvGHtx096d7TbpvQaBhHWZpfnh+erXTb3GQ@mail.gmail.com>

On Thu, 12 Apr 2018 09:04:20 +0200
Jason Mitchell <jason@sparkatm.co.za> wrote:

> Good day all
> 
> I am currently faced with a task of having to run new software on
> ageing hardware. We have currently about 1000 units in the field of a
> machine that runs Windows CE using the Samsung S3C6410.
> 
> Because these are considerable assets its not a simple case of
> replacing them with new, more modern hardware.
> 
> The goal is to be able to get these existing boards to run Ubuntu so
> that we can run GoLang applications, so we need the GUI with just a
> relatively recent browser.
> 
> The board in question is a near perfect clone of the SMDK6410, which
> was supported fully in U-boot in the past, indeed I can select
> SMDK6410 and compile a working U-boot using 1.3.4 sources
> 
> After much effort I managed to get a tailored (tailored as in having
> changed the memory configuration to match the hardware) U-boot V1.3.4
> compiled and running for this chip, the problem now, obviously we
> have a fairly recent Linux kernel compiled and it won't boot because
> the Device Tree Blob doesn't exist on such an old version of U-boot.
> 
> So my questions are:
> 
> - Has anyone perhaps created a branch or fork of the current or nearly
> current version of U-boot and patched in this support. I see a lot of
> Chinese websites where they seem to have done this but the language
> barrier is a big problem. Also a lot of dead links are another
> problem.
> 
> - If there isn't something out there, would it be possible to run
> through the steps with me to add support for this CPU again. I don't
> mind doing the work, the main issue is I have no clue how U-boot
> actually works internally.
> 
> I have FULL JTAG access to this board, with a perfectly functional
> OpenOCD setup. This is how we are able to program versions of U-boot
> into the FLASH.
> 
> Hoping someone can assist

If this helps - I do have some code (including OpenOCD
restoration/debricking files) to add support for smdk6410 based on
v2013.04 u-boot.

As fair as I remember this code was booting till prompt, but was NOT in
a shape allowing mainlining.

Unfortunately, I don't have smdk6410 dev board anymore, so I cannot
help with testing/tunning the HW.

> 
> Kindest Regards,
> Jason Mitchell
> Software Developer
> Spark ATM Systems (PTY) LTD
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180416/cd4d33a8/attachment.sig>

      parent reply	other threads:[~2018-04-16 11:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12  7:04 [U-Boot] Re-introducing support for OLD hardware Jason Mitchell
2018-04-12 14:01 ` Tom Rini
2018-04-16  6:03   ` Jason Mitchell
2018-05-04  7:27   ` Jason Mitchell
2018-04-16 11:10 ` Lukasz Majewski [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=20180416131034.5eaeb409@jawa \
    --to=lukma@denx.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