From: Abel Vesa <abel.vesa@nxp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 00/22] mx6sabre: Add DM and SPL FIT support
Date: Thu, 31 Jan 2019 15:13:51 +0000 [thread overview]
Message-ID: <20190131151350.spmazsiwpnve5hnu@fsr-ub1664-175> (raw)
In-Reply-To: <20190131144111.GW30838@bill-the-cat>
On 19-01-31 09:41:11, Tom Rini wrote:
> On Thu, Jan 31, 2019 at 12:59:19PM +0000, Abel Vesa wrote:
> > On 19-01-30 13:58:19, Tom Rini wrote:
> > > On Wed, Jan 30, 2019 at 01:39:50PM +0000, Abel Vesa wrote:
> > >
> > > > The second version is here:
> > > > https://lists.denx.de/pipermail/u-boot/2019-January/356557.html
> > > >
> > > > Changes since v2:
> > > > * Removed the unecessary SYS_MALLOC_F_LEN from both defocnfig
> > > > * Fixed the copyright for all the *u-boot.dtsi files
> > >
> > > OK, but you didn't answer why you need to specify your own its file when
> > > the TI examples show how to have mkimage generate this for you, thanks!
> > >
> >
> > I might be wrong here but TI is doing this for MLO, which AFAIU, it's for
> > SPL. The fit_spl.its I'm adding here is actually for u-boot proper.
> >
> > SPL expects descriptions in the configurations and that can't be done
> > without its file, again, AFAIK.
> >
> > Please let me know what exactly am I missing here.
>
> The flag to mkimage is not about SPL but rather "create a single
> configurations its file on the fly". This should also be fine for the
> its file in patch 10/22 (of v2, don't have v3 in front of me in
> patchwork).
>
Well, I tried something like this (manually):
$ ./tools/mkimage -f auto -C none -A ARM -T standalone -a 0x17800000 -e 0x17800000 -d u-boot-fit-dtb.bin -n "U-Boot" u-boot.itb -E
and the output was:
FIT description: Standalone Program image with one or more FDT blobs
Created: Thu Jan 31 13:58:01 2019
Image 0 (standalone-1)
Description: U-Boot
Created: Thu Jan 31 13:58:01 2019
Type: Standalone Program
Compression: uncompressed
Data Size: 646400 Bytes = 631.25 KiB = 0.62 MiB
Architecture: ARM
Load Address: 0x17800000
Entry Point: 0x17800000
Default Configuration: 'conf-1'
Configuration 0 (conf-1)
Description: unavailable
Kernel: unavailable
And then the SPL complains about the configuration description:
U-Boot SPL 2019.01-00374-gbe79a83 (Jan 31 2019 - 13:56:01 +0200)
Trying to boot from MMC1
fit_find_config_node: Missing FDT description in DTB
No matching DT out of these options:
Firmware image with one or more FDT blobs
fit_find_config_node: Missing FDT description in DTB
No matching DT out of these options:
Firmware image with one or more FDT blobs
fit_find_config_node: Missing FDT description in DTB
No matching DT out of these options:
Firmware image with one or more FDT blobs
mmc_load_image_raw_sector: mmc block read error
spl: no partition table found
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
But with the fit_spl.its file I added I have this and works:
FIT description: Image for u-boot proper (with dtb appended)
Created: Thu Jan 31 13:57:02 2019
Image 0 (uboot at 1)
Description: U-Boot
Created: Thu Jan 31 13:57:02 2019
Type: Standalone Program
Compression: uncompressed
Data Size: 646400 Bytes = 631.25 KiB = 0.62 MiB
Architecture: ARM
Load Address: 0x17800000
Entry Point: unavailable
Default Configuration: 'conf at 1'
Configuration 0 (conf at 1)
Description: i.MX armv7
Kernel: unavailable
Loadables: uboot at 1
So the differences between this and the one generated with mkimage+flags
are the loadables and the description in the configuration 0.
Can I specify those through flags ?
> --
> Tom
next prev parent reply other threads:[~2019-01-31 15:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 13:39 [U-Boot] [PATCH v3 00/22] mx6sabre: Add DM and SPL FIT support Abel Vesa
2019-01-30 13:39 ` [U-Boot] [PATCH v3 01/22] usb: Rename SPL_USB_SUPPORT to SPL_USB_STORAGE Abel Vesa
2019-01-30 13:39 ` [U-Boot] [PATCH v3 02/22] usb: ehci-mx6: Make regulator DM_REGULATOR dependent Abel Vesa
2019-01-30 13:39 ` [U-Boot] [PATCH v3 03/22] configs: imx6sabreauto: Add DM_MMC support Abel Vesa
2019-01-30 13:39 ` [U-Boot] [PATCH v3 04/22] configs: imx6sabreauto: Add DM_USB support Abel Vesa
2019-01-30 13:39 ` [U-Boot] [PATCH v3 05/22] mmc: fsl_esdhc: Fix DM_REGULATOR ifdefs for SPL builds Abel Vesa
2019-01-30 13:39 ` [U-Boot] [PATCH v3 06/22] board: mx6sabresd: Add board_fit_config_name_match to support FIT in SPL Abel Vesa
2019-01-30 13:39 ` [U-Boot] [PATCH v3 07/22] board: mx6sabreauto: " Abel Vesa
2019-01-30 13:39 ` [U-Boot] [PATCH v3 08/22] arm: dts: Add all the imx6[q|qp|dl] sabre[auto|sd] u-boot dts[i] files Abel Vesa
2019-01-30 13:39 ` [U-Boot] [PATCH v3 09/22] arm: dts: Update all the dts[i] files for imx6[q|qp|dl] sabre[auto|sd] Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 10/22] arm: imx: Add FIT SPL its Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 11/22] configs: mx6sabreauto: Add SPL FIT and DM support Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 12/22] configs: mx6sabresd: " Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 13/22] mx6sabreauto: Add DM_GPIO support Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 14/22] mx6sabresd: " Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 15/22] configs: mx6sabreauto: Add DM_SPI_FLASH necessary configs Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 16/22] configs: mx6sabresd: " Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 17/22] board: mx6sabreauto: Remove the non-DM code Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 18/22] board: mx6sabresd: Remove " Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 19/22] board: mx6sabresd: Remove the enet reset gpio handling Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 20/22] configs: mx6sabresd: Reduce size for SPL by disabling SPL_DOS and SPL_EFI Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 21/22] board: mx6sabreauto: Update README with the SPL DM FIT info Abel Vesa
2019-01-30 13:40 ` [U-Boot] [PATCH v3 22/22] board: mx6sabresd: " Abel Vesa
2019-01-30 18:58 ` [U-Boot] [PATCH v3 00/22] mx6sabre: Add DM and SPL FIT support Tom Rini
2019-01-31 12:59 ` Abel Vesa
2019-01-31 14:41 ` Tom Rini
2019-01-31 15:13 ` Abel Vesa [this message]
2019-01-31 15:45 ` Tom Rini
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=20190131151350.spmazsiwpnve5hnu@fsr-ub1664-175 \
--to=abel.vesa@nxp.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 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.