From: Joris Offouga <offougajoris@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC 0/9] Convert Pico-Pi i.MX7D to DM
Date: Sat, 16 Feb 2019 14:02:34 +0100 [thread overview]
Message-ID: <2ca63ebd-98db-5152-1063-c9cf9681687e@gmail.com> (raw)
In-Reply-To: <CAOMZO5A0jN4DZSuF=X3gjGwOzF3roQMoBYQkdKoeVEzShkD9GQ@mail.gmail.com>
Le 16/02/2019 à 13:46, Fabio Estevam a écrit :
> On Sat, Feb 16, 2019 at 10:34 AM Joris Offouga <offougajoris@gmail.com> wrote:
>>
>> Le 16/02/2019 à 13:17, Fabio Estevam a écrit :
>>> Hi Joris,
>>>
>>> On Sat, Feb 16, 2019 at 9:06 AM Offouga Joris <offougajoris@gmail.com> wrote:
>>>
>>>> Hi Fabio
>>>>
>>>> I followed Lukasz's advice and I increased the size of the U-Boot in the dfu_alt_info and there is no more error. However, once the SPL and U-Boot are changed and the board reboots with the jumper in Boot from emmc, the SPL can not load the U-Boot.
>>> What is the U-Boot size you used in the dfu_alt_info?
>> "u-boot raw 0x8a 0x1000"
> The original setting was correct:
> u-boot-dtb.img needs to be flashed at the position 69kB of the eMMC.
>
> Originally we had:
>
> u-boot raw 0x8a 0x400;
>
> which means: 0x8a = 138 * 0x400 = 138 * 1024 = 138 sectors. Each
> sector is 512 bytes, so 138*0.5k = 69kB
>
> Could you also try:
>
> u-boot raw 0x45 0x800
>
> Does it make any difference?
Yes , download with dfu it's okay but after rebooting the SPL does not
load.
For u-boot, dm-spl, this does not work only if the SPL is converted to
DM too, because the add-on in the uscdh3 node did not change the problem
of loading the U-Boot
next prev parent reply other threads:[~2019-02-16 13:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 22:38 [U-Boot] [RFC 0/9] Convert Pico-Pi i.MX7D to DM Joris Offouga
2019-01-22 9:47 ` Lukasz Majewski
2019-01-23 21:01 ` Joris Offouga
2019-02-15 11:22 ` Fabio Estevam
2019-02-15 11:50 ` Lukasz Majewski
2019-02-16 11:06 ` Offouga Joris
2019-02-16 12:17 ` Fabio Estevam
2019-02-16 12:33 ` Fabio Estevam
2019-02-16 12:33 ` Joris Offouga
2019-02-16 12:46 ` Fabio Estevam
2019-02-16 13:02 ` Joris Offouga [this message]
2019-02-16 13:58 ` Fabio Estevam
2019-02-16 14:38 ` Joris Offouga
2019-02-16 14:42 ` Fabio Estevam
2019-02-16 14:52 ` Joris Offouga
2019-02-16 14:54 ` Fabio Estevam
2019-02-16 15:14 ` Joris Offouga
2019-02-16 15:25 ` Fabio Estevam
2019-02-16 15:41 ` Joris Offouga
2019-02-16 15:43 ` Fabio Estevam
2019-02-19 19:24 ` Offouga Joris
2019-02-19 20:22 ` Fabio Estevam
2019-02-28 20:38 ` Fabio Estevam
2019-02-28 22:06 ` Offouga Joris
2019-03-09 22:21 ` Offouga Joris
2019-03-10 14:24 ` Fabio Estevam
2019-03-10 18:35 ` Joris Offouga
[not found] <1548019059-10918-1-git-send-email-offougajoris@gmail.com>
2019-02-14 12:27 ` Fabio Estevam
-- strict thread matches above, loose matches on Subject: below --
2019-01-20 21:18 Joris Offouga
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=2ca63ebd-98db-5152-1063-c9cf9681687e@gmail.com \
--to=offougajoris@gmail.com \
--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