mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: Carlos Leyva Guerrero <carlos.leyva@idener.es>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Compilation for ARM926ej-s --> S3c2451
Date: Thu, 4 Dec 2014 10:02:47 +0100	[thread overview]
Message-ID: <CABDcavbLHhPZ_p0UqEqu_66a12TM6obktyZssGxwxMAH8PS7cg@mail.gmail.com> (raw)
In-Reply-To: <CAB6LMXnf8-zYthFTPVmvOGXm0QyZH4zY_FgiV=7L=KvxojvppA@mail.gmail.com>

2014-12-03 18:00 GMT+01:00 Carlos Leyva Guerrero <carlos.leyva@idener.es>:
[...]
>>> If I provide you the patch and config file I did for the kernel 3.6,
>>> would you mind testing if you are able to compile and boot with it?
>>
>>
>> Sure, I can do that, but it will probably be 2-3 weeks before I can try
>> it. I have some high priority stuff to take care off before that (this is
>> also why I had to put my ongoing work on barebox in standby).
>>
>> I can also send you my kernelconfig and platformconfig files if you think
>> this would be helpful.
>
> Please send them so I can run some additional checks, see diferences in
> kernels that could explain the non-booting issue.

Let me dig these (I want to make sure to send the correct files) and I
will send them to you.

[...]
>> I will try this but I dont't think this will work. The NAND locking is not
>> accidental -- it is done explicitly by superboot through the "tight lock"
>> bit in the S3C2451 NAND controller. So I expect they would also do the same
>> in USB mode.
>
>
> I am in contact with the original manufacturer of the boards, and I have
> talked with them several time about uboot, I will contact them and will ask
> if they in fact block the nand in all modes.

Please let me know if you get any feedback on this.

>>> Remember to use a good quality mini-usb cables, If you have problems
>>> detecting the board, messages like "data not accepted by the board", it is
>>> due to bad quality wires.
>>>
>>> - You have to fuse the bootloader into the SD card or the nand, process
>>> similar to the one used to get uboot working in our boards (there are boards
>>> in china with uboot working with 2451, and there is some documentation from
>>> samsung (I can provide it to you if you want).
>>>
>>> If first stage bootloader lock nand in any situation, there is no other
>>> solution than using the SD fused bootloader option.
>>
>>
>> Yes. This one will work for sure. Actually I am waiting for some boards
>> with u-boot preloaded, this will help me proceed without worrying about
>> superboot for the time being :)
>
>
> This statement is the most surprising!. Pre-loaded uboot? can I ask which
> provider will serve this boards to you (you can answer by private if you
> can't share it openly)? I have identify other providers with same chip
> (s3c2451) but different boards and unless USA FA distributor AAH ships the
> boards with uboot, I have missed a new distributor!.

Maybe I was too fast in my reply. The boards I am getting (from
Boardcon) are not actually based on the s3c2451; they are based on the
s3c2416 instead. However these are very similar (they even use the
same chip ID) except for some extra onboard peripherals in the
S3C2451.

http://armbest.com/Tiny2451_CPU%20Compare.html

Guillermo

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-12-04  9:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03  9:25 Carlos Leyva Guerrero
2014-12-03 10:02 ` Guillermo Rodriguez Garcia
2014-12-03 10:58   ` Carlos Leyva Guerrero
2014-12-03 11:24     ` Guillermo Rodriguez Garcia
2014-12-03 16:01       ` Carlos Leyva Guerrero
2014-12-03 16:47         ` Guillermo Rodriguez Garcia
2014-12-03 17:00           ` Carlos Leyva Guerrero
2014-12-04  9:02             ` Guillermo Rodriguez Garcia [this message]
2014-12-05 16:46               ` Guillermo Rodriguez Garcia
2014-12-18 18:41                 ` Guillermo Rodriguez Garcia
2014-12-18 22:43                   ` Carlos Leyva Guerrero

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=CABDcavbLHhPZ_p0UqEqu_66a12TM6obktyZssGxwxMAH8PS7cg@mail.gmail.com \
    --to=guille.rodriguez@gmail.com \
    --cc=carlos.leyva@idener.es \
    --cc=ptxdist@pengutronix.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