From: Schrempf Frieder <frieder.schrempf@kontron.de>
To: u-boot@lists.denx.de
Subject: iMX8MM USB support?
Date: Thu, 9 Apr 2020 10:02:09 +0000 [thread overview]
Message-ID: <9d7f8b3a-6e54-9b3b-c820-06678b2c225c@kontron.de> (raw)
In-Reply-To: <CAJ+vNU0T41RJ7M1QqK3gUnWhvvo_SSOX7eSimP-HLBXffe9F-g@mail.gmail.com>
On 08.04.20 17:31, Tim Harvey wrote:
[...]
>>
>> In my case I'm loading a FIT image, so things are a bit different.
>> Where are you loading the image to?
>>
>> I have the following line in mx8mm_usb_sdp_spl.conf to load my FIT image
>> to DDR and jump to it:
>>
>> /path/to/image/u-boot.itb:load 0x40200000, jump_direct 0x40200000
>>
>
> Frieder,
>
> I was trying to load u-boot.img
>
> The SPL boots fine:
> U-Boot SPL 2020.01-00029-g5ad7797 (Apr 08 2020 - 08:16:53 -0700)
> read error from device: 9310b8 register: x!Normal Boot
> Trying to boot from USB SDP
> SDP: initialize...
> SDP: handle requests..
>
> But when I 'imx_usb u-boot.img' it complains there is no header on
> u-boot.img. I enabled FIT generation and attempted to 'imx_usb
> u-boot.itb' but imx_usb still complains about no header found.
>
> My mx8mm_usb_sdp_spl.conf loooks like this:
> mx8mm_spl_sdp
> #hid/bulk,[old_header,]max packet size, {ram start, ram size}(repeat
> valid ram areas)
> #In SPL, we typically load u-boot.img which has a U-boot header...
> hid,1024,0x910000,0x40000000,1G,0x00900000,0x40000
>
> #0x60000 - 0x8400 = 0x57c00, +0x3000=5ac00 (FIT image)
> ../u-boot-imx6/u-boot.bin:load 0x40200000
> ../u-boot-imx6/bl31-iMX8MM.bin:load 0x00920000,jump 0x920000
>
> What does your mx8mm_usb_sdp_spl.conf look like? I must admit I don't
> really understand how these are configured.
It looks just like yours except that I have a single instruction as
already stated above:
/path/to/image/u-boot.itb:load 0x40200000, jump_direct 0x40200000
and I'm loading the FIT image by running './imx_usb' without arguments.
As imx_usb_loader can't parse FIT image headers, I use 'jump_direct' to
jump to the raw image entry point and let SPL parse the FIT. I think in
that case imx_usb_loader shouldn't complain about a missing header.
next prev parent reply other threads:[~2020-04-09 10:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 17:55 iMX8MM USB support? Tim Harvey
2020-04-01 21:34 ` Igor Opaniuk
2020-04-02 1:02 ` Sherry Sun
2020-04-06 9:43 ` Schrempf Frieder
2020-04-07 17:06 ` Tim Harvey
2020-04-08 7:35 ` Schrempf Frieder
2020-04-08 15:31 ` Tim Harvey
2020-04-09 10:02 ` Schrempf Frieder [this message]
2020-04-09 21:45 ` Tim Harvey
2020-04-10 18:37 ` Tim Harvey
2021-07-01 23:15 ` Fabio Estevam
2021-07-01 23:58 ` Tim Harvey
2021-07-02 0:36 ` Fabio Estevam
2021-07-02 0:49 ` Tim Harvey
2021-07-02 0:56 ` Fabio Estevam
2021-07-02 1:13 ` Fabio Estevam
2021-07-02 1:36 ` Fabio Estevam
2021-07-02 14:50 ` Fabio Estevam
2021-07-02 21:12 ` Tim Harvey
2021-07-02 21:32 ` Fabio Estevam
2022-03-09 10:52 ` Michael Nazzareno Trimarchi
2022-03-09 11:06 ` Tommaso Merciai
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=9d7f8b3a-6e54-9b3b-c820-06678b2c225c@kontron.de \
--to=frieder.schrempf@kontron.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.