[3rdparty][PATCH v2] imx7d-pico: Add machine configuration

[3rdparty][PATCH v2] imx7d-pico: Add machine configuration

[Vanessa Maegima]

Add machine definition for imx7d-pico board.

For more information about this reference design, please visit:

https://www.wandboard.org/products/android-things/PICO-PI-IMX7/

The machine configuration file used to include Yocto Project support to the
board is a consolidation work only.

It only reflects the work done in Linux kernel, U-Boot and FSL Community BSP,
where the hard work is actually done.

Signed-off-by: Vanessa Maegima <vanessa.maegima@nxp.com>
---
Changes since v1:
- Remove unnecessary overriding
- Add wic support
- Remove unnecessary line COMPATIBLE_MACHINE_imx7d-pico

 conf/machine/imx7d-pico.conf | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 conf/machine/imx7d-pico.conf

diff --git a/conf/machine/imx7d-pico.conf b/conf/machine/imx7d-pico.conf
new file mode 100644
index 0000000..80aea98
--- /dev/null
+++ b/conf/machine/imx7d-pico.conf
@@ -0,0 +1,27 @@
+#@TYPE: Machine
+#@NAME: IMX7D-PICO
+#@SOC: i.MX7D
+#@DESCRIPTION: Machine configuration for IMX7D-PICO board.
+#@MAINTAINER: Vanessa Maegima <vanessa.maegima@nxp.com>
+
+MACHINEOVERRIDES =. "use-mainline-bsp:mx7:mx7d:"
+
+require conf/machine/include/imx-base.inc
+require conf/machine/include/tune-cortexa7.inc
+
+SERIAL_CONSOLE = "115200 ttymxc4"
+
+KERNEL_DEVICETREE = "imx7d-pico.dtb"
+
+UBOOT_MACHINE = "pico-imx7d_defconfig"
+
+MACHINE_ESSENTIAL_EXTRA_RDEPENDS += " \
+    kernel-image \
+    kernel-devicetree \
+    u-boot-fslc \
+"
+
+WKS_FILES ?= "imx-uboot.wks"
+WKS_FILE_DEPENDS ?= ""
+
+IMAGE_FSTYPES = "tar.bz2 ext4 wic.gz"
-- 
2.7.4

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration

[Fabio Berton]

[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]

Hi Vanessa,

If you intend to use only wic image you don't need to add tar.bz2 ext4 to
IMAGE_FSTYPES, adding only wic.gz is enough.

On Thu, Sep 14, 2017 at 3:28 PM, Vanessa Maegima <vanessa.maegima@nxp.com>
wrote:

> Add machine definition for imx7d-pico board.
>
> For more information about this reference design, please visit:
>
> https://www.wandboard.org/products/android-things/PICO-PI-IMX7/
>
> The machine configuration file used to include Yocto Project support to the
> board is a consolidation work only.
>
> It only reflects the work done in Linux kernel, U-Boot and FSL Community
> BSP,
> where the hard work is actually done.
>
> Signed-off-by: Vanessa Maegima <vanessa.maegima@nxp.com>
> ---
> Changes since v1:
> - Remove unnecessary overriding
> - Add wic support
> - Remove unnecessary line COMPATIBLE_MACHINE_imx7d-pico
>
>  conf/machine/imx7d-pico.conf | 27 +++++++++++++++++++++++++++
>  1 file changed, 27 insertions(+)
>  create mode 100644 conf/machine/imx7d-pico.conf
>
> diff --git a/conf/machine/imx7d-pico.conf b/conf/machine/imx7d-pico.conf
> new file mode 100644
> index 0000000..80aea98
> --- /dev/null
> +++ b/conf/machine/imx7d-pico.conf
> @@ -0,0 +1,27 @@
> +#@TYPE: Machine
> +#@NAME: IMX7D-PICO
> +#@SOC: i.MX7D
> +#@DESCRIPTION: Machine configuration for IMX7D-PICO board.
> +#@MAINTAINER: Vanessa Maegima <vanessa.maegima@nxp.com>
> +
> +MACHINEOVERRIDES =. "use-mainline-bsp:mx7:mx7d:"
> +
> +require conf/machine/include/imx-base.inc
> +require conf/machine/include/tune-cortexa7.inc
> +
> +SERIAL_CONSOLE = "115200 ttymxc4"
> +
> +KERNEL_DEVICETREE = "imx7d-pico.dtb"
> +
> +UBOOT_MACHINE = "pico-imx7d_defconfig"
> +
> +MACHINE_ESSENTIAL_EXTRA_RDEPENDS += " \
> +    kernel-image \
> +    kernel-devicetree \
> +    u-boot-fslc \
> +"
> +
> +WKS_FILES ?= "imx-uboot.wks"
> +WKS_FILE_DEPENDS ?= ""
> +
> +IMAGE_FSTYPES = "tar.bz2 ext4 wic.gz"
> --
> 2.7.4
>
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>

[-- Attachment #2: Type: text/html, Size: 3402 bytes --]

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration

[Philippe Desrochers]

[-- Attachment #1: Type: text/plain, Size: 2335 bytes --]

Hello,

Does anybody know if the Wifi module is enable with this configuration for
the PICO-PI-IMX7 ?

How can I write the built image (kernel/rootfs) to the eMMC ?
Do I have to use the NXP manufacturing tool from here:
https://www.nxp.com/products/microcontrollers-and-processors/arm-based-processors-and-mcus/i.mx-applications-processors/developer-resources/iot-development-platforms-based-on-i.mx-6ul-7dual-processor-and-android-things-os:IOT-DEV-PLATFORMS-i.MX6UL?tab=Design_Tools_Tab

Thanks




2017-09-14 14:28 GMT-04:00 Vanessa Maegima <vanessa.maegima@nxp.com>:

> Add machine definition for imx7d-pico board.
>
> For more information about this reference design, please visit:
>
> https://www.wandboard.org/products/android-things/PICO-PI-IMX7/
>
> The machine configuration file used to include Yocto Project support to the
> board is a consolidation work only.
>
> It only reflects the work done in Linux kernel, U-Boot and FSL Community
> BSP,
> where the hard work is actually done.
>
> Signed-off-by: Vanessa Maegima <vanessa.maegima@nxp.com>
> ---
> Changes since v1:
> - Remove unnecessary overriding
> - Add wic support
> - Remove unnecessary line COMPATIBLE_MACHINE_imx7d-pico
>
>  conf/machine/imx7d-pico.conf | 27 +++++++++++++++++++++++++++
>  1 file changed, 27 insertions(+)
>  create mode 100644 conf/machine/imx7d-pico.conf
>
> diff --git a/conf/machine/imx7d-pico.conf b/conf/machine/imx7d-pico.conf
> new file mode 100644
> index 0000000..80aea98
> --- /dev/null
> +++ b/conf/machine/imx7d-pico.conf
> @@ -0,0 +1,27 @@
> +#@TYPE: Machine
> +#@NAME: IMX7D-PICO
> +#@SOC: i.MX7D
> +#@DESCRIPTION: Machine configuration for IMX7D-PICO board.
> +#@MAINTAINER: Vanessa Maegima <vanessa.maegima@nxp.com>
> +
> +MACHINEOVERRIDES =. "use-mainline-bsp:mx7:mx7d:"
> +
> +require conf/machine/include/imx-base.inc
> +require conf/machine/include/tune-cortexa7.inc
> +
> +SERIAL_CONSOLE = "115200 ttymxc4"
> +
> +KERNEL_DEVICETREE = "imx7d-pico.dtb"
> +
> +UBOOT_MACHINE = "pico-imx7d_defconfig"
> +
> +MACHINE_ESSENTIAL_EXTRA_RDEPENDS += " \
> +    kernel-image \
> +    kernel-devicetree \
> +    u-boot-fslc \
> +"
> +
> +WKS_FILES ?= "imx-uboot.wks"
> +WKS_FILE_DEPENDS ?= ""
> +
> +IMAGE_FSTYPES = "tar.bz2 ext4 wic.gz"
> --
> 2.7.4
>
>

[-- Attachment #2: Type: text/html, Size: 3521 bytes --]

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration

[Otavio Salvador]

Hello Philippe,

On Wed, Sep 27, 2017 at 8:29 PM, Philippe Desrochers
<desrochers.philippe@gmail.com> wrote:
> Does anybody know if the Wifi module is enable with this configuration for
> the PICO-PI-IMX7 ?

I don't know; but it is likely.

> How can I write the built image (kernel/rootfs) to the eMMC ?
> Do I have to use the NXP manufacturing tool from here:
> https://www.nxp.com/products/microcontrollers-and-processors/arm-based-processors-and-mcus/i.mx-applications-processors/developer-resources/iot-development-platforms-based-on-i.mx-6ul-7dual-processor-and-android-things-os:IOT-DEV-PLATFORMS-i.MX6UL?tab=Design_Tools_Tab

You can use U-Boot ums or gzwrite for it.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration

[Vanessa Maegima]

Hi Philippe,

On Qua, 2017-09-27 at 20:57 -0300, Otavio Salvador wrote:
> Hello Philippe,
> 
> On Wed, Sep 27, 2017 at 8:29 PM, Philippe Desrochers
> <desrochers.philippe@gmail.com> wrote:
> > 
> > Does anybody know if the Wifi module is enable with this
> > configuration for
> > the PICO-PI-IMX7 ?
> I don't know; but it is likely.
> 

Wifi is not enabled in this configuration yet. It uses kernel 4.13 and
the Wifi module is enabled in kernel 4.14. You can try to update the
kernel and add the firmware files yourself.

I didn't add the firmware in this configuration because I was facing
some issues trying to get Wifi working in this board. I'm still trying
to debug this. If you could make it functional please let us know.

> > 
> > How can I write the built image (kernel/rootfs) to the eMMC ?
> > Do I have to use the NXP manufacturing tool from here:
> > https://www.nxp.com/products/microcontrollers-and-processors/arm-ba
> > sed-processors-and-mcus/i.mx-applications-processors/developer-
> > resources/iot-development-platforms-based-on-i.mx-6ul-7dual-
> > processor-and-android-things-os:IOT-DEV-PLATFORMS-
> > i.MX6UL?tab=Design_Tools_Tab
> You can use U-Boot ums or gzwrite for it.
> 

Best,
Vanessa

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration

[Otavio Salvador]

On Thu, Sep 28, 2017 at 10:00 AM, Vanessa Maegima
<vanessa.maegima@nxp.com> wrote:
> On Qua, 2017-09-27 at 20:57 -0300, Otavio Salvador wrote:
>> On Wed, Sep 27, 2017 at 8:29 PM, Philippe Desrochers
>> <desrochers.philippe@gmail.com> wrote:
>> >
>> > Does anybody know if the Wifi module is enable with this
>> > configuration for
>> > the PICO-PI-IMX7 ?
>> I don't know; but it is likely.
>>
>
> Wifi is not enabled in this configuration yet. It uses kernel 4.13 and
> the Wifi module is enabled in kernel 4.14. You can try to update the
> kernel and add the firmware files yourself.

Send the patches for our 4.13 kernel.

> I didn't add the firmware in this configuration because I was facing
> some issues trying to get Wifi working in this board. I'm still trying
> to debug this. If you could make it functional please let us know.

There was a bump of linux-firmware these days, it might help.


-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration

[Vanessa Maegima]

Hi Otavio,

On Qui, 2017-09-28 at 10:12 -0300, Otavio Salvador wrote:
> On Thu, Sep 28, 2017 at 10:00 AM, Vanessa Maegima
> <vanessa.maegima@nxp.com> wrote:
> > 
> > On Qua, 2017-09-27 at 20:57 -0300, Otavio Salvador wrote:
> > > 
> > > On Wed, Sep 27, 2017 at 8:29 PM, Philippe Desrochers
> > > <desrochers.philippe@gmail.com> wrote:
> > > > 
> > > > 
> > > > Does anybody know if the Wifi module is enable with this
> > > > configuration for
> > > > the PICO-PI-IMX7 ?
> > > I don't know; but it is likely.
> > > 
> > Wifi is not enabled in this configuration yet. It uses kernel 4.13
> > and
> > the Wifi module is enabled in kernel 4.14. You can try to update
> > the
> > kernel and add the firmware files yourself.
> Send the patches for our 4.13 kernel.
> 

I've sent the pull request for 4.13 kernel.

> > 
> > I didn't add the firmware in this configuration because I was
> > facing
> > some issues trying to get Wifi working in this board. I'm still
> > trying
> > to debug this. If you could make it functional please let us know.
> There was a bump of linux-firmware these days, it might help.
> 
> 

Thanks, I will test it again.

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration

[Takashi Matsuzawa]

[-- Attachment #1: Type: text/plain, Size: 2692 bytes --]

Hello.

I have one question regard this change.

There is another board called PICO-PI-IMX6UL and the same image from below can also be used on PICO-PI-IMX6UL, or maybe configuration change is needed?

________________________________
From: Fabio Berton <fabio.berton@ossystems.com.br>
Sent: Friday, September 15, 2017 4:40 AM
To: Vanessa Maegima
Cc: meta-freescale Mailing List; Takashi Matsuzawa; desrochers.philippe@gmail.com
Subject: Re: [meta-freescale] [3rdparty][PATCH v2] imx7d-pico: Add machine configuration

Hi Vanessa,

If you intend to use only wic image you don't need to add tar.bz2 ext4 to IMAGE_FSTYPES, adding only wic.gz is enough.

On Thu, Sep 14, 2017 at 3:28 PM, Vanessa Maegima <vanessa.maegima@nxp.com<mailto:vanessa.maegima@nxp.com>> wrote:
Add machine definition for imx7d-pico board.

For more information about this reference design, please visit:

https://www.wandboard.org/products/android-things/PICO-PI-IMX7/

The machine configuration file used to include Yocto Project support to the
board is a consolidation work only.

It only reflects the work done in Linux kernel, U-Boot and FSL Community BSP,
where the hard work is actually done.

Signed-off-by: Vanessa Maegima <vanessa.maegima@nxp.com<mailto:vanessa.maegima@nxp.com>>
---
Changes since v1:
- Remove unnecessary overriding
- Add wic support
- Remove unnecessary line COMPATIBLE_MACHINE_imx7d-pico

 conf/machine/imx7d-pico.conf | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 conf/machine/imx7d-pico.conf

diff --git a/conf/machine/imx7d-pico.conf b/conf/machine/imx7d-pico.conf
new file mode 100644
index 0000000..80aea98
--- /dev/null
+++ b/conf/machine/imx7d-pico.conf
@@ -0,0 +1,27 @@
+#@TYPE: Machine
+#@NAME: IMX7D-PICO
+#@SOC: i.MX7D
+#@DESCRIPTION: Machine configuration for IMX7D-PICO board.
+#@MAINTAINER: Vanessa Maegima <vanessa.maegima@nxp.com<mailto:vanessa.maegima@nxp.com>>
+
+MACHINEOVERRIDES =. "use-mainline-bsp:mx7:mx7d:"
+
+require conf/machine/include/imx-base.inc
+require conf/machine/include/tune-cortexa7.inc
+
+SERIAL_CONSOLE = "115200 ttymxc4"
+
+KERNEL_DEVICETREE = "imx7d-pico.dtb"
+
+UBOOT_MACHINE = "pico-imx7d_defconfig"
+
+MACHINE_ESSENTIAL_EXTRA_RDEPENDS += " \
+    kernel-image \
+    kernel-devicetree \
+    u-boot-fslc \
+"
+
+WKS_FILES ?= "imx-uboot.wks"
+WKS_FILE_DEPENDS ?= ""
+
+IMAGE_FSTYPES = "tar.bz2 ext4 wic.gz"
--
2.7.4

--
_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.org<mailto:meta-freescale@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/meta-freescale


[-- Attachment #2: Type: text/html, Size: 4937 bytes --]

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration

[Fabio Estevam]

On Fri, Sep 29, 2017 at 5:06 AM, Takashi Matsuzawa <tmatsuzawa@xevo.com> wrote:
> Hello.
>
> I have one question regard this change.
>
> There is another board called PICO-PI-IMX6UL and the same image from below
> can also be used on PICO-PI-IMX6UL, or maybe configuration change is needed?

imx6ul-pico has its own machine entry at: conf/machine/imx6ul-pico-hobbit.conf

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration

[Fabio Estevam]

Hi Takashi,

On Fri, Sep 29, 2017 at 8:54 AM, Fabio Estevam <festevam@gmail.com> wrote:
> On Fri, Sep 29, 2017 at 5:06 AM, Takashi Matsuzawa <tmatsuzawa@xevo.com> wrote:
>> Hello.
>>
>> I have one question regard this change.
>>
>> There is another board called PICO-PI-IMX6UL and the same image from below
>> can also be used on PICO-PI-IMX6UL, or maybe configuration change is needed?
>
> imx6ul-pico has its own machine entry at: conf/machine/imx6ul-pico-hobbit.conf

Sorry for the confusion, this machine entry does not support the pi version.

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)

[Takashi Matsuzawa]

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

Hello.
I am now trying this with my board and want to make sure if what I am doing is correct.

>Add machine definition for imx7d-pico board.
>
>For more information about this reference design, please visit:
>
>https://www.wandboard.org/products/android-things/PICO-PI-IMX7/

My local build creates wic.gz file (core-image-minimal-imx7d-pico.wic.gz).

1) This is expected to be a one-partition disk image with an ext4 partition in it?

(I can see no fat partition for #1, only one ext4 partition.  Is this expected?)

2) In serial download mode, I could boot the board using u-boot (using imx_usb loader tool, by pushing u-boot.imx data to the board).

3) However, I am failing to boot it from eMMC.

I have written u-boot data to 1K offset on the eMMC (/dev/sdc as it is mounted on the host).
So, at least it should boot into u-boot, but it does not.

Though looking into hardware manuals for PICP-PI-IMX7, I am seeing conflicing information on which is the eMMC boot mode setting on the J1/J2 jumpers,
I tried them but non worked.

The board as deliverd booted into the default Linux (provided by technexsion), so the problem is not hardware.
(Unfortunately, I did not take not of the default jumper setting or data of pre-installed boot loader)


[-- Attachment #2: Type: text/html, Size: 2088 bytes --]

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)

[Takashi Matsuzawa]

[-- Attachment #1: Type: text/plain, Size: 2066 bytes --]

Hello.
By the way, I found I could boot successfully using this wic image (only one ext4 partition) by the following.
So, it might have to do something with the boot code  - but I still not sure what being wrong.

1) Connect power (USB-C cable)
2) sudo imx_usb u-boot.imx

Then, the linux successfull boot into the logon prompt.
This seems to work regardless of the J1 jumper setting (so eMMC boot setting is not working and always being serial download mode?)

________________________________
From: Takashi Matsuzawa
Sent: Tuesday, October 3, 2017 6:47 PM
To: Vanessa Maegima; meta-freescale@yoctoproject.org
Cc: desrochers.philippe@gmail.com; festevam@gmail.com; van.ayumi@gmail.com
Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)


Hello.
I am now trying this with my board and want to make sure if what I am doing is correct.

>Add machine definition for imx7d-pico board.
>
>For more information about this reference design, please visit:
>
>https://www.wandboard.org/products/android-things/PICO-PI-IMX7/

My local build creates wic.gz file (core-image-minimal-imx7d-pico.wic.gz).

1) This is expected to be a one-partition disk image with an ext4 partition in it?

(I can see no fat partition for #1, only one ext4 partition.  Is this expected?)

2) In serial download mode, I could boot the board using u-boot (using imx_usb loader tool, by pushing u-boot.imx data to the board).

3) However, I am failing to boot it from eMMC.

I have written u-boot data to 1K offset on the eMMC (/dev/sdc as it is mounted on the host).
So, at least it should boot into u-boot, but it does not.

Though looking into hardware manuals for PICP-PI-IMX7, I am seeing conflicing information on which is the eMMC boot mode setting on the J1/J2 jumpers,
I tried them but non worked.

The board as deliverd booted into the default Linux (provided by technexsion), so the problem is not hardware.
(Unfortunately, I did not take not of the default jumper setting or data of pre-installed boot loader)


[-- Attachment #2: Type: text/html, Size: 3413 bytes --]

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)

[Vanessa Ayumi Maegima]

Hi Takashi,

On Tue, Oct 3, 2017 at 7:35 AM, Takashi Matsuzawa <tmatsuzawa@xevo.com> wrote:
> Hello.
> By the way, I found I could boot successfully using this wic image (only one
> ext4 partition) by the following.
> So, it might have to do something with the boot code  - but I still not sure
> what being wrong.
>
> 1) Connect power (USB-C cable)
> 2) sudo imx_usb u-boot.imx
>
> Then, the linux successfull boot into the logon prompt.
> This seems to work regardless of the J1 jumper setting (so eMMC boot setting
> is not working and always being serial download mode?)
>
>
> ________________________________
> From: Takashi Matsuzawa
> Sent: Tuesday, October 3, 2017 6:47 PM
> To: Vanessa Maegima; meta-freescale@yoctoproject.org
> Cc: desrochers.philippe@gmail.com; festevam@gmail.com; van.ayumi@gmail.com
> Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration
> (booting)
>
>
> Hello.
> I am now trying this with my board and want to make sure if what I am doing
> is correct.
>
>>Add machine definition for imx7d-pico board.
>>
>>For more information about this reference design, please visit:
>>
>>https://www.wandboard.org/products/android-things/PICO-PI-IMX7/
>
> My local build creates wic.gz file (core-image-minimal-imx7d-pico.wic.gz).
>
> 1) This is expected to be a one-partition disk image with an ext4 partition
> in it?
>
> (I can see no fat partition for #1, only one ext4 partition.  Is this
> expected?)
>
> 2) In serial download mode, I could boot the board using u-boot (using
> imx_usb loader tool, by pushing u-boot.imx data to the board).
>
> 3) However, I am failing to boot it from eMMC.
>
> I have written u-boot data to 1K offset on the eMMC (/dev/sdc as it is
> mounted on the host).
> So, at least it should boot into u-boot, but it does not.
>
> Though looking into hardware manuals for PICP-PI-IMX7, I am seeing
> conflicing information on which is the eMMC boot mode setting on the J1/J2
> jumpers,
> I tried them but non worked.
>
> The board as deliverd booted into the default Linux (provided by
> technexsion), so the problem is not hardware.
> (Unfortunately, I did not take not of the default jumper setting or data of
> pre-installed boot loader)
>

This machine configuration generates the wic image only. This image
includes u-boot.imx, dtb, zImage and rootfs and generates only the
ext4 partition. The kernel files can be found at /boot.

I've created a tutorial on how to build and flash this image, please see
it here:

https://imxdev.gitlab.io/announcement/The_imx7d-pico_board_is_now_supported_in_FSL_Community_BSP/

I faced a similar issue as you are facing now. The problem was that the
default u-boot by TechNexion was locked and I needed to unlock it in
order to flash a new U-Boot.

Please see this tutorial:

https://imxdev.gitlab.io/tutorial/WaRP7_possible_brick_and_solution/

Please try to unlock your user partition and flash u-boot again in serial
downloader mode. You will need to set the right parameters to
mmc partconf (mmc partconf dev [boot_ack boot_partition partition_access])

Best,
Vanessa

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)

[Takashi Matsuzawa]

[-- Attachment #1: Type: text/plain, Size: 5162 bytes --]

Hello.

Thank you for your hints, but I am still unable to boot from eMMC.


1) mmc partconf commands


>mmc partconf 0 1 1 0

>mmc partconf 0 1 0 0


I think partconf flags correcponds to BOOT_ACK, BOOT_PARTITION_ENABLE, PARTITION_ACCCESS.

So, I need to do something like below instead to make sure my u-boot is written to offset 1KB on eMMC?


>mmc partconf 0 1 7 1

>mmc write xxxx 7D0 yyyy

>mmc partconf 0 1 7 0


(Though I have to figure out what xxxx and yyyy are.)

Since I have to write u-boot data to 1KB offset, I need to specify 7 (user partition)?


I could better use dd command from my host, but after I issue:


>mmc partconf 0 1 0 1


"ums 0 mmc 0" command gives me "bad MBR sector signature 0x0000" error (so it does not appear on host as block device), so I think I cannot access it from the host.


2) J1/J2 jumpers


This may be board specific (Technexsion) issue, but I am still confused.


Looking into:


https://www.nxp.com/docs/en/quick-reference-guide/PICO-iMX7D-QSG.pdf


I can see following jumper modes.


i) Download mode

ii) Boot mode


I am still unsure on exactly how these affects the board behavior.

(Also I can see these are different from the one from PICO-PI-IMX6UL document - so it also make me wonder if it is document typo or accurate info.)


________________________________
From: Vanessa Ayumi Maegima <van.ayumi@gmail.com>
Sent: Tuesday, October 3, 2017 9:14 PM
To: Takashi Matsuzawa
Cc: Vanessa Maegima; meta-freescale@yoctoproject.org; desrochers.philippe@gmail.com; festevam@gmail.com
Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)

Hi Takashi,

On Tue, Oct 3, 2017 at 7:35 AM, Takashi Matsuzawa <tmatsuzawa@xevo.com> wrote:
> Hello.
> By the way, I found I could boot successfully using this wic image (only one
> ext4 partition) by the following.
> So, it might have to do something with the boot code  - but I still not sure
> what being wrong.
>
> 1) Connect power (USB-C cable)
> 2) sudo imx_usb u-boot.imx
>
> Then, the linux successfull boot into the logon prompt.
> This seems to work regardless of the J1 jumper setting (so eMMC boot setting
> is not working and always being serial download mode?)
>
>
> ________________________________
> From: Takashi Matsuzawa
> Sent: Tuesday, October 3, 2017 6:47 PM
> To: Vanessa Maegima; meta-freescale@yoctoproject.org
> Cc: desrochers.philippe@gmail.com; festevam@gmail.com; van.ayumi@gmail.com
> Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration
> (booting)
>
>
> Hello.
> I am now trying this with my board and want to make sure if what I am doing
> is correct.
>
>>Add machine definition for imx7d-pico board.
>>
>>For more information about this reference design, please visit:
>>
>>https://www.wandboard.org/products/android-things/PICO-PI-IMX7/
>
> My local build creates wic.gz file (core-image-minimal-imx7d-pico.wic.gz).
>
> 1) This is expected to be a one-partition disk image with an ext4 partition
> in it?
>
> (I can see no fat partition for #1, only one ext4 partition.  Is this
> expected?)
>
> 2) In serial download mode, I could boot the board using u-boot (using
> imx_usb loader tool, by pushing u-boot.imx data to the board).
>
> 3) However, I am failing to boot it from eMMC.
>
> I have written u-boot data to 1K offset on the eMMC (/dev/sdc as it is
> mounted on the host).
> So, at least it should boot into u-boot, but it does not.
>
> Though looking into hardware manuals for PICP-PI-IMX7, I am seeing
> conflicing information on which is the eMMC boot mode setting on the J1/J2
> jumpers,
> I tried them but non worked.
>
> The board as deliverd booted into the default Linux (provided by
> technexsion), so the problem is not hardware.
> (Unfortunately, I did not take not of the default jumper setting or data of
> pre-installed boot loader)
>

This machine configuration generates the wic image only. This image
includes u-boot.imx, dtb, zImage and rootfs and generates only the
ext4 partition. The kernel files can be found at /boot.

I've created a tutorial on how to build and flash this image, please see
it here:

https://imxdev.gitlab.io/announcement/The_imx7d-pico_board_is_now_supported_in_FSL_Community_BSP/
The imx7d-pico board is now supported in FSL Community BSP<https://imxdev.gitlab.io/announcement/The_imx7d-pico_board_is_now_supported_in_FSL_Community_BSP/>
imxdev.gitlab.io
The imx7d-pico is a TechNexion board defined here. It is nowsupported in meta-freescale-3rdparty in the master branch.




I faced a similar issue as you are facing now. The problem was that the
default u-boot by TechNexion was locked and I needed to unlock it in
order to flash a new U-Boot.

Please see this tutorial:

https://imxdev.gitlab.io/tutorial/WaRP7_possible_brick_and_solution/

Please try to unlock your user partition and flash u-boot again in serial
downloader mode. You will need to set the right parameters to
mmc partconf (mmc partconf dev [boot_ack boot_partition partition_access])

Best,
Vanessa

[-- Attachment #2: Type: text/html, Size: 18037 bytes --]

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)

[Takashi Matsuzawa]

[-- Attachment #1: Type: text/plain, Size: 5772 bytes --]

Hello.


>2) J1/J2 jumpers


Well, why I am puzzled is that I can see different (as it seems) info on boot jumpers on the following two documents..


https://www.nxp.com/docs/en/quick-reference-guide/PICO-iMX7D-QSG.pdf
https://www.nxp.com/docs/en/user-guide/PICO-IMX7D-USG.pdf

________________________________
From: Takashi Matsuzawa
Sent: Wednesday, October 4, 2017 1:15 PM
To: Vanessa Ayumi Maegima
Cc: Vanessa Maegima; meta-freescale@yoctoproject.org; desrochers.philippe@gmail.com; festevam@gmail.com
Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)


Hello.

Thank you for your hints, but I am still unable to boot from eMMC.


1) mmc partconf commands


>mmc partconf 0 1 1 0

>mmc partconf 0 1 0 0


I think partconf flags correcponds to BOOT_ACK, BOOT_PARTITION_ENABLE, PARTITION_ACCCESS.

So, I need to do something like below instead to make sure my u-boot is written to offset 1KB on eMMC?


>mmc partconf 0 1 7 1

>mmc write xxxx 7D0 yyyy

>mmc partconf 0 1 7 0


(Though I have to figure out what xxxx and yyyy are.)

Since I have to write u-boot data to 1KB offset, I need to specify 7 (user partition)?


I could better use dd command from my host, but after I issue:


>mmc partconf 0 1 0 1


"ums 0 mmc 0" command gives me "bad MBR sector signature 0x0000" error (so it does not appear on host as block device), so I think I cannot access it from the host.


2) J1/J2 jumpers


This may be board specific (Technexsion) issue, but I am still confused.


Looking into:


https://www.nxp.com/docs/en/quick-reference-guide/PICO-iMX7D-QSG.pdf


I can see following jumper modes.


i) Download mode

ii) Boot mode


I am still unsure on exactly how these affects the board behavior.

(Also I can see these are different from the one from PICO-PI-IMX6UL document - so it also make me wonder if it is document typo or accurate info.)


________________________________
From: Vanessa Ayumi Maegima <van.ayumi@gmail.com>
Sent: Tuesday, October 3, 2017 9:14 PM
To: Takashi Matsuzawa
Cc: Vanessa Maegima; meta-freescale@yoctoproject.org; desrochers.philippe@gmail.com; festevam@gmail.com
Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)

Hi Takashi,

On Tue, Oct 3, 2017 at 7:35 AM, Takashi Matsuzawa <tmatsuzawa@xevo.com> wrote:
> Hello.
> By the way, I found I could boot successfully using this wic image (only one
> ext4 partition) by the following.
> So, it might have to do something with the boot code  - but I still not sure
> what being wrong.
>
> 1) Connect power (USB-C cable)
> 2) sudo imx_usb u-boot.imx
>
> Then, the linux successfull boot into the logon prompt.
> This seems to work regardless of the J1 jumper setting (so eMMC boot setting
> is not working and always being serial download mode?)
>
>
> ________________________________
> From: Takashi Matsuzawa
> Sent: Tuesday, October 3, 2017 6:47 PM
> To: Vanessa Maegima; meta-freescale@yoctoproject.org
> Cc: desrochers.philippe@gmail.com; festevam@gmail.com; van.ayumi@gmail.com
> Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration
> (booting)
>
>
> Hello.
> I am now trying this with my board and want to make sure if what I am doing
> is correct.
>
>>Add machine definition for imx7d-pico board.
>>
>>For more information about this reference design, please visit:
>>
>>https://www.wandboard.org/products/android-things/PICO-PI-IMX7/
>
> My local build creates wic.gz file (core-image-minimal-imx7d-pico.wic.gz).
>
> 1) This is expected to be a one-partition disk image with an ext4 partition
> in it?
>
> (I can see no fat partition for #1, only one ext4 partition.  Is this
> expected?)
>
> 2) In serial download mode, I could boot the board using u-boot (using
> imx_usb loader tool, by pushing u-boot.imx data to the board).
>
> 3) However, I am failing to boot it from eMMC.
>
> I have written u-boot data to 1K offset on the eMMC (/dev/sdc as it is
> mounted on the host).
> So, at least it should boot into u-boot, but it does not.
>
> Though looking into hardware manuals for PICP-PI-IMX7, I am seeing
> conflicing information on which is the eMMC boot mode setting on the J1/J2
> jumpers,
> I tried them but non worked.
>
> The board as deliverd booted into the default Linux (provided by
> technexsion), so the problem is not hardware.
> (Unfortunately, I did not take not of the default jumper setting or data of
> pre-installed boot loader)
>

This machine configuration generates the wic image only. This image
includes u-boot.imx, dtb, zImage and rootfs and generates only the
ext4 partition. The kernel files can be found at /boot.

I've created a tutorial on how to build and flash this image, please see
it here:

https://imxdev.gitlab.io/announcement/The_imx7d-pico_board_is_now_supported_in_FSL_Community_BSP/
The imx7d-pico board is now supported in FSL Community BSP<https://imxdev.gitlab.io/announcement/The_imx7d-pico_board_is_now_supported_in_FSL_Community_BSP/>
imxdev.gitlab.io
The imx7d-pico is a TechNexion board defined here. It is nowsupported in meta-freescale-3rdparty in the master branch.




I faced a similar issue as you are facing now. The problem was that the
default u-boot by TechNexion was locked and I needed to unlock it in
order to flash a new U-Boot.

Please see this tutorial:

https://imxdev.gitlab.io/tutorial/WaRP7_possible_brick_and_solution/

Please try to unlock your user partition and flash u-boot again in serial
downloader mode. You will need to set the right parameters to
mmc partconf (mmc partconf dev [boot_ack boot_partition partition_access])

Best,
Vanessa

[-- Attachment #2: Type: text/html, Size: 20021 bytes --]

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)

[Takashi Matsuzawa]

[-- Attachment #1: Type: text/plain, Size: 6855 bytes --]

Hello.
It seems I could finally boot from eMMC.

I am not sure this is OK.
In particullar, how jumper settings and mmc partconf BOOT_PARTITION_ENABLE/PARTITION_ACCESS flags affecting this?

(Steps)
- Set jumper to "boot mode" according to PICO-IMX7D-QSG.pdf
- Side load u-boot by imx_usb loader.

- at u-boot console:

- env default -a f (I am not sure if this is needed)
- saveenv
- mmc partconf 0 1 7 0
- ums 0 mmc 0

- then on host:

- /dev/sdc appears on the host
- Then dd if=xxxx.wic of=/dev/sdc
- disconnect USB-C (power off)
- reconnect USB-C (power on)
- the board boots from eMMC.

(Now I hesitate to try this again from scratch for while since I have only one PICO-IMX7 at hand until next time I burn image to the board.)


________________________________
From: Takashi Matsuzawa
Sent: Wednesday, October 4, 2017 1:52 PM
To: Vanessa Ayumi Maegima
Cc: Vanessa Maegima; meta-freescale@yoctoproject.org; desrochers.philippe@gmail.com; festevam@gmail.com
Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)


Hello.


>2) J1/J2 jumpers


Well, why I am puzzled is that I can see different (as it seems) info on boot jumpers on the following two documents..


https://www.nxp.com/docs/en/quick-reference-guide/PICO-iMX7D-QSG.pdf
https://www.nxp.com/docs/en/user-guide/PICO-IMX7D-USG.pdf

________________________________
From: Takashi Matsuzawa
Sent: Wednesday, October 4, 2017 1:15 PM
To: Vanessa Ayumi Maegima
Cc: Vanessa Maegima; meta-freescale@yoctoproject.org; desrochers.philippe@gmail.com; festevam@gmail.com
Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)


Hello.

Thank you for your hints, but I am still unable to boot from eMMC.


1) mmc partconf commands


>mmc partconf 0 1 1 0

>mmc partconf 0 1 0 0


I think partconf flags correcponds to BOOT_ACK, BOOT_PARTITION_ENABLE, PARTITION_ACCCESS.

So, I need to do something like below instead to make sure my u-boot is written to offset 1KB on eMMC?


>mmc partconf 0 1 7 1

>mmc write xxxx 7D0 yyyy

>mmc partconf 0 1 7 0


(Though I have to figure out what xxxx and yyyy are.)

Since I have to write u-boot data to 1KB offset, I need to specify 7 (user partition)?


I could better use dd command from my host, but after I issue:


>mmc partconf 0 1 0 1


"ums 0 mmc 0" command gives me "bad MBR sector signature 0x0000" error (so it does not appear on host as block device), so I think I cannot access it from the host.


2) J1/J2 jumpers


This may be board specific (Technexsion) issue, but I am still confused.


Looking into:


https://www.nxp.com/docs/en/quick-reference-guide/PICO-iMX7D-QSG.pdf


I can see following jumper modes.


i) Download mode

ii) Boot mode


I am still unsure on exactly how these affects the board behavior.

(Also I can see these are different from the one from PICO-PI-IMX6UL document - so it also make me wonder if it is document typo or accurate info.)


________________________________
From: Vanessa Ayumi Maegima <van.ayumi@gmail.com>
Sent: Tuesday, October 3, 2017 9:14 PM
To: Takashi Matsuzawa
Cc: Vanessa Maegima; meta-freescale@yoctoproject.org; desrochers.philippe@gmail.com; festevam@gmail.com
Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)

Hi Takashi,

On Tue, Oct 3, 2017 at 7:35 AM, Takashi Matsuzawa <tmatsuzawa@xevo.com> wrote:
> Hello.
> By the way, I found I could boot successfully using this wic image (only one
> ext4 partition) by the following.
> So, it might have to do something with the boot code  - but I still not sure
> what being wrong.
>
> 1) Connect power (USB-C cable)
> 2) sudo imx_usb u-boot.imx
>
> Then, the linux successfull boot into the logon prompt.
> This seems to work regardless of the J1 jumper setting (so eMMC boot setting
> is not working and always being serial download mode?)
>
>
> ________________________________
> From: Takashi Matsuzawa
> Sent: Tuesday, October 3, 2017 6:47 PM
> To: Vanessa Maegima; meta-freescale@yoctoproject.org
> Cc: desrochers.philippe@gmail.com; festevam@gmail.com; van.ayumi@gmail.com
> Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration
> (booting)
>
>
> Hello.
> I am now trying this with my board and want to make sure if what I am doing
> is correct.
>
>>Add machine definition for imx7d-pico board.
>>
>>For more information about this reference design, please visit:
>>
>>https://www.wandboard.org/products/android-things/PICO-PI-IMX7/
>
> My local build creates wic.gz file (core-image-minimal-imx7d-pico.wic.gz).
>
> 1) This is expected to be a one-partition disk image with an ext4 partition
> in it?
>
> (I can see no fat partition for #1, only one ext4 partition.  Is this
> expected?)
>
> 2) In serial download mode, I could boot the board using u-boot (using
> imx_usb loader tool, by pushing u-boot.imx data to the board).
>
> 3) However, I am failing to boot it from eMMC.
>
> I have written u-boot data to 1K offset on the eMMC (/dev/sdc as it is
> mounted on the host).
> So, at least it should boot into u-boot, but it does not.
>
> Though looking into hardware manuals for PICP-PI-IMX7, I am seeing
> conflicing information on which is the eMMC boot mode setting on the J1/J2
> jumpers,
> I tried them but non worked.
>
> The board as deliverd booted into the default Linux (provided by
> technexsion), so the problem is not hardware.
> (Unfortunately, I did not take not of the default jumper setting or data of
> pre-installed boot loader)
>

This machine configuration generates the wic image only. This image
includes u-boot.imx, dtb, zImage and rootfs and generates only the
ext4 partition. The kernel files can be found at /boot.

I've created a tutorial on how to build and flash this image, please see
it here:

https://imxdev.gitlab.io/announcement/The_imx7d-pico_board_is_now_supported_in_FSL_Community_BSP/
The imx7d-pico board is now supported in FSL Community BSP<https://imxdev.gitlab.io/announcement/The_imx7d-pico_board_is_now_supported_in_FSL_Community_BSP/>
imxdev.gitlab.io
The imx7d-pico is a TechNexion board defined here. It is nowsupported in meta-freescale-3rdparty in the master branch.




I faced a similar issue as you are facing now. The problem was that the
default u-boot by TechNexion was locked and I needed to unlock it in
order to flash a new U-Boot.

Please see this tutorial:

https://imxdev.gitlab.io/tutorial/WaRP7_possible_brick_and_solution/

Please try to unlock your user partition and flash u-boot again in serial
downloader mode. You will need to set the right parameters to
mmc partconf (mmc partconf dev [boot_ack boot_partition partition_access])

Best,
Vanessa

[-- Attachment #2: Type: text/html, Size: 21802 bytes --]

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)

[Takashi Matsuzawa]

[-- Attachment #1: Type: text/plain, Size: 7463 bytes --]

Hello.


>Now I hesitate to try this again


Well, I did again, and just confirmed the image is updated and eMMC boots with new image.


- jumper settings is "boot mode"

- at u-boot console "ums 0 mmc 0"

- dd xxxx.wic to /dev/sdc

- power recycle(detach/attach USB-C)

________________________________
From: Takashi Matsuzawa
Sent: Wednesday, October 4, 2017 4:00 PM
To: Vanessa Ayumi Maegima
Cc: Vanessa Maegima; meta-freescale@yoctoproject.org; desrochers.philippe@gmail.com; festevam@gmail.com
Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)


Hello.
It seems I could finally boot from eMMC.

I am not sure this is OK.
In particullar, how jumper settings and mmc partconf BOOT_PARTITION_ENABLE/PARTITION_ACCESS flags affecting this?

(Steps)
- Set jumper to "boot mode" according to PICO-IMX7D-QSG.pdf
- Side load u-boot by imx_usb loader.

- at u-boot console:

- env default -a f (I am not sure if this is needed)
- saveenv
- mmc partconf 0 1 7 0
- ums 0 mmc 0

- then on host:

- /dev/sdc appears on the host
- Then dd if=xxxx.wic of=/dev/sdc
- disconnect USB-C (power off)
- reconnect USB-C (power on)
- the board boots from eMMC.

(Now I hesitate to try this again from scratch for while since I have only one PICO-IMX7 at hand until next time I burn image to the board.)


________________________________
From: Takashi Matsuzawa
Sent: Wednesday, October 4, 2017 1:52 PM
To: Vanessa Ayumi Maegima
Cc: Vanessa Maegima; meta-freescale@yoctoproject.org; desrochers.philippe@gmail.com; festevam@gmail.com
Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)


Hello.


>2) J1/J2 jumpers


Well, why I am puzzled is that I can see different (as it seems) info on boot jumpers on the following two documents..


https://www.nxp.com/docs/en/quick-reference-guide/PICO-iMX7D-QSG.pdf
https://www.nxp.com/docs/en/user-guide/PICO-IMX7D-USG.pdf

________________________________
From: Takashi Matsuzawa
Sent: Wednesday, October 4, 2017 1:15 PM
To: Vanessa Ayumi Maegima
Cc: Vanessa Maegima; meta-freescale@yoctoproject.org; desrochers.philippe@gmail.com; festevam@gmail.com
Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)


Hello.

Thank you for your hints, but I am still unable to boot from eMMC.


1) mmc partconf commands


>mmc partconf 0 1 1 0

>mmc partconf 0 1 0 0


I think partconf flags correcponds to BOOT_ACK, BOOT_PARTITION_ENABLE, PARTITION_ACCCESS.

So, I need to do something like below instead to make sure my u-boot is written to offset 1KB on eMMC?


>mmc partconf 0 1 7 1

>mmc write xxxx 7D0 yyyy

>mmc partconf 0 1 7 0


(Though I have to figure out what xxxx and yyyy are.)

Since I have to write u-boot data to 1KB offset, I need to specify 7 (user partition)?


I could better use dd command from my host, but after I issue:


>mmc partconf 0 1 0 1


"ums 0 mmc 0" command gives me "bad MBR sector signature 0x0000" error (so it does not appear on host as block device), so I think I cannot access it from the host.


2) J1/J2 jumpers


This may be board specific (Technexsion) issue, but I am still confused.


Looking into:


https://www.nxp.com/docs/en/quick-reference-guide/PICO-iMX7D-QSG.pdf


I can see following jumper modes.


i) Download mode

ii) Boot mode


I am still unsure on exactly how these affects the board behavior.

(Also I can see these are different from the one from PICO-PI-IMX6UL document - so it also make me wonder if it is document typo or accurate info.)


________________________________
From: Vanessa Ayumi Maegima <van.ayumi@gmail.com>
Sent: Tuesday, October 3, 2017 9:14 PM
To: Takashi Matsuzawa
Cc: Vanessa Maegima; meta-freescale@yoctoproject.org; desrochers.philippe@gmail.com; festevam@gmail.com
Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)

Hi Takashi,

On Tue, Oct 3, 2017 at 7:35 AM, Takashi Matsuzawa <tmatsuzawa@xevo.com> wrote:
> Hello.
> By the way, I found I could boot successfully using this wic image (only one
> ext4 partition) by the following.
> So, it might have to do something with the boot code  - but I still not sure
> what being wrong.
>
> 1) Connect power (USB-C cable)
> 2) sudo imx_usb u-boot.imx
>
> Then, the linux successfull boot into the logon prompt.
> This seems to work regardless of the J1 jumper setting (so eMMC boot setting
> is not working and always being serial download mode?)
>
>
> ________________________________
> From: Takashi Matsuzawa
> Sent: Tuesday, October 3, 2017 6:47 PM
> To: Vanessa Maegima; meta-freescale@yoctoproject.org
> Cc: desrochers.philippe@gmail.com; festevam@gmail.com; van.ayumi@gmail.com
> Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration
> (booting)
>
>
> Hello.
> I am now trying this with my board and want to make sure if what I am doing
> is correct.
>
>>Add machine definition for imx7d-pico board.
>>
>>For more information about this reference design, please visit:
>>
>>https://www.wandboard.org/products/android-things/PICO-PI-IMX7/
>
> My local build creates wic.gz file (core-image-minimal-imx7d-pico.wic.gz).
>
> 1) This is expected to be a one-partition disk image with an ext4 partition
> in it?
>
> (I can see no fat partition for #1, only one ext4 partition.  Is this
> expected?)
>
> 2) In serial download mode, I could boot the board using u-boot (using
> imx_usb loader tool, by pushing u-boot.imx data to the board).
>
> 3) However, I am failing to boot it from eMMC.
>
> I have written u-boot data to 1K offset on the eMMC (/dev/sdc as it is
> mounted on the host).
> So, at least it should boot into u-boot, but it does not.
>
> Though looking into hardware manuals for PICP-PI-IMX7, I am seeing
> conflicing information on which is the eMMC boot mode setting on the J1/J2
> jumpers,
> I tried them but non worked.
>
> The board as deliverd booted into the default Linux (provided by
> technexsion), so the problem is not hardware.
> (Unfortunately, I did not take not of the default jumper setting or data of
> pre-installed boot loader)
>

This machine configuration generates the wic image only. This image
includes u-boot.imx, dtb, zImage and rootfs and generates only the
ext4 partition. The kernel files can be found at /boot.

I've created a tutorial on how to build and flash this image, please see
it here:

https://imxdev.gitlab.io/announcement/The_imx7d-pico_board_is_now_supported_in_FSL_Community_BSP/
The imx7d-pico board is now supported in FSL Community BSP<https://imxdev.gitlab.io/announcement/The_imx7d-pico_board_is_now_supported_in_FSL_Community_BSP/>
imxdev.gitlab.io
The imx7d-pico is a TechNexion board defined here. It is nowsupported in meta-freescale-3rdparty in the master branch.




I faced a similar issue as you are facing now. The problem was that the
default u-boot by TechNexion was locked and I needed to unlock it in
order to flash a new U-Boot.

Please see this tutorial:

https://imxdev.gitlab.io/tutorial/WaRP7_possible_brick_and_solution/

Please try to unlock your user partition and flash u-boot again in serial
downloader mode. You will need to set the right parameters to
mmc partconf (mmc partconf dev [boot_ack boot_partition partition_access])

Best,
Vanessa

[-- Attachment #2: Type: text/html, Size: 23587 bytes --]

Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)

[Vanessa Ayumi Maegima]

Hi Takashi,

On Wed, Oct 4, 2017 at 7:36 AM, Takashi Matsuzawa <tmatsuzawa@xevo.com> wrote:
>
> Hello.
>
>
> >Now I hesitate to try this again
>
>
> Well, I did again, and just confirmed the image is updated and eMMC boots with new image.
>
>
> - jumper settings is "boot mode"
>
> - at u-boot console "ums 0 mmc 0"
>
> - dd xxxx.wic to /dev/sdc
>
> - power recycle(detach/attach USB-C)
>
>
> ________________________________
> From: Takashi Matsuzawa
> Sent: Wednesday, October 4, 2017 4:00 PM
>
> To: Vanessa Ayumi Maegima
> Cc: Vanessa Maegima; meta-freescale@yoctoproject.org; desrochers.philippe@gmail.com; festevam@gmail.com
> Subject: Re: [3rdparty][PATCH v2] imx7d-pico: Add machine configuration (booting)
>
>
> Hello.
> It seems I could finally boot from eMMC.
>
> I am not sure this is OK.
> In particullar, how jumper settings and mmc partconf BOOT_PARTITION_ENABLE/PARTITION_ACCESS flags affecting this?
>
> (Steps)
> - Set jumper to "boot mode" according to PICO-IMX7D-QSG.pdf
> - Side load u-boot by imx_usb loader.
>
> - at u-boot console:
>
> - env default -a f (I am not sure if this is needed)
> - saveenv
> - mmc partconf 0 1 7 0
> - ums 0 mmc 0
>
> - then on host:
>
> - /dev/sdc appears on the host
> - Then dd if=xxxx.wic of=/dev/sdc
> - disconnect USB-C (power off)
> - reconnect USB-C (power on)
> - the board boots from eMMC.
>
> (Now I hesitate to try this again from scratch for while since I have only one PICO-IMX7 at hand until next time I burn image to the board.)
>

Thanks for letting us know!

In fact, I think that's the right procedure, I'm just not sure about
the 7 in the
partconf command, but great that it worked for you.

You should follow the boot pins as described in the PICO-IMX7D-QSG (not
sure why it's different on the PICO-IMX7D-USG).

Best,
Vanessa