[meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Otavio Salvador]

This patchset adds support for Nitrogen6X using the deployment used by
Boundary Devices. The generated sdcard should just work in the board.

The patches are untested as I don't own a Nitrogen6X and would be good
if someone could test those before we apply them.

Otavio Salvador (3):
  u-boot-boundary: Add U-Boot recipe for Boundary Devices version
  u-boot-script-boundary: Add recipe to deploy the boot scripts
  nitrogen6x: Add machine definition

 conf/machine/nitrogen6x.conf                     |   28 ++++++++++++++++
 recipes-bsp/u-boot/u-boot-boundary_git.bb        |   16 ++++++++++
 recipes-bsp/u-boot/u-boot-script-boundary_git.bb |   37 ++++++++++++++++++++++
 3 files changed, 81 insertions(+)
 create mode 100644 conf/machine/nitrogen6x.conf
 create mode 100644 recipes-bsp/u-boot/u-boot-boundary_git.bb
 create mode 100644 recipes-bsp/u-boot/u-boot-script-boundary_git.bb

-- 
1.7.10.4

[meta-fsl-arm-extra][PATCH 1/3] u-boot-boundary: Add U-Boot recipe for Boundary Devices version

[Otavio Salvador]

Change-Id: I6503266d8299aeb82e8e295b2167bb1a65ed076b
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---
 recipes-bsp/u-boot/u-boot-boundary_git.bb |   16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 recipes-bsp/u-boot/u-boot-boundary_git.bb

diff --git a/recipes-bsp/u-boot/u-boot-boundary_git.bb b/recipes-bsp/u-boot/u-boot-boundary_git.bb
new file mode 100644
index 0000000..02c8d2b
--- /dev/null
+++ b/recipes-bsp/u-boot/u-boot-boundary_git.bb
@@ -0,0 +1,16 @@
+require recipes-bsp/u-boot/u-boot.inc
+
+LICENSE = "GPLv2+"
+LIC_FILES_CHKSUM = "file://COPYING;md5=1707d6db1d42237583f50183a5651ecb"
+COMPATIBLE_MACHINE = "(imx6qsabrelite|nitrogen6x)"
+
+PROVIDES = "u-boot"
+
+PV = "v2013.01+git${SRCPV}"
+
+SRCREV = "d6b05d35b8b29392e71fdd8fa43d5cb8bd4fe276"
+SRC_URI = "git://github.com/boundarydevices/u-boot-imx6.git"
+
+S = "${WORKDIR}/git"
+
+PACKAGE_ARCH = "${MACHINE_ARCH}"
-- 
1.7.10.4

[meta-fsl-arm-extra][PATCH 2/3] u-boot-script-boundary: Add recipe to deploy the boot scripts

[Otavio Salvador]

The recipe deploys the scripts used by Boundary Devices to detect and
choose video output, load kernel and etc...

Change-Id: Ic4685c60ba1470a1548629e294ea8aa48473cd0e
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---
 recipes-bsp/u-boot/u-boot-script-boundary_git.bb |   37 ++++++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 recipes-bsp/u-boot/u-boot-script-boundary_git.bb

diff --git a/recipes-bsp/u-boot/u-boot-script-boundary_git.bb b/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
new file mode 100644
index 0000000..6b2591a
--- /dev/null
+++ b/recipes-bsp/u-boot/u-boot-script-boundary_git.bb
@@ -0,0 +1,37 @@
+LICENSE = "GPLv2+"
+LIC_FILES_CHKSUM = "file://COPYING;md5=1707d6db1d42237583f50183a5651ecb"
+COMPATIBLE_MACHINE = "(imx6qsabrelite|nitrogen6x)"
+
+PV = "v2013.01+git${SRCPV}"
+
+SRCREV = "d6b05d35b8b29392e71fdd8fa43d5cb8bd4fe276"
+SRC_URI = "git://github.com/boundarydevices/u-boot-imx6.git"
+
+S = "${WORKDIR}/git"
+
+inherit deploy
+
+do_compile () {
+	:
+}
+
+do_install () {
+	:
+}
+
+do_deploy () {
+    install -d ${DEPLOYDIR}
+    install ${S}/board/boundary/nitrogen6x/6x_bootscript.txt \
+            ${DEPLOYDIR}/6x_bootscript-${MACHINE}-${PV}-${PR}.txt
+    install ${S}/board/boundary/nitrogen6x/6x_upgrade.txt \
+            ${DEPLOYDIR}/6x_upgrade-${MACHINE}-${PV}-${PR}.txt
+
+    cd ${DEPLOYDIR}
+    rm -f 6x_bootscript-${MACHINE}.txt 6x_upgrade-${MACHINE}.txt
+    ln -sf 6x_bootscript-${MACHINE}-${PV}-${PR}.txt 6x_bootscript-${MACHINE}.txt
+    ln -sf 6x_upgrade-${MACHINE}-${PV}-${PR}.txt 6x_upgrade-${MACHINE}.txt
+}
+
+addtask deploy before do_build after do_compile
+
+PACKAGE_ARCH = "${MACHINE_ARCH}"
-- 
1.7.10.4

[meta-fsl-arm-extra][PATCH 3/3] nitrogen6x: Add machine definition

[Otavio Salvador]

This adds the machine definition to Nitrogen6x from Boundary Devices.
More information at:

http://boundarydevices.com/products/nitrogen6x-board-imx6-arm-cortex-a9-sbc/

In order to take advance of same code used for imx6qsabrelite (on
linux-imx, u-boot, imx-firmaware), we use a MACHINEOVERRIDES trick, so
imx6qsabrelite is taken as a fallback for nitrogen6x machine.

Change-Id: I8bd0b80d2ad8e8741391ec178c10abd75218542e
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---
 conf/machine/nitrogen6x.conf |   28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 conf/machine/nitrogen6x.conf

diff --git a/conf/machine/nitrogen6x.conf b/conf/machine/nitrogen6x.conf
new file mode 100644
index 0000000..2c0a6a0
--- /dev/null
+++ b/conf/machine/nitrogen6x.conf
@@ -0,0 +1,28 @@
+#@TYPE: Machine
+#@NAME: Nitrogen6X
+#@DESCRIPTION: Machine configuration for Boundary Devices Nitrogen6X
+
+# We need to override the default before everything
+MACHINEOVERRIDES = "${MACHINE}:imx6qsabrelite"
+
+include conf/machine/include/imx-base.inc
+include conf/machine/include/tune-cortexa9.inc
+
+SOC_FAMILY = "mx6q:mx6"
+
+PREFERRED_PROVIDER_u-boot = "u-boot-boundary"
+
+# Use SPI NOR U-Boot by default
+IMAGE_BOOTLOADER ?= ""
+
+# Boot scripts to install
+BOOT_SCRIPTS = "6x_bootscript-${MACHINE}.txt:6x_bootscript.txt \
+                6x_upgrade-${MACHINE}.txt:6x_upgrade.txt"
+
+UBOOT_MACHINE = "nitrogen6X_config"
+
+SERIAL_CONSOLE = "115200 ttymxc1"
+
+MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-wl12xx"
+
+MACHINE_FEATURES += " pci wifi bluetooth"
-- 
1.7.10.4

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Otavio Salvador]

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

On Mon, Dec 10, 2012 at 2:06 PM, Otavio Salvador <otavio@ossystems.com.br>wrote:

> This patchset adds support for Nitrogen6X using the deployment used by
> Boundary Devices. The generated sdcard should just work in the board.
>
> The patches are untested as I don't own a Nitrogen6X and would be good
> if someone could test those before we apply them.
>
> Otavio Salvador (3):
>   u-boot-boundary: Add U-Boot recipe for Boundary Devices version
>   u-boot-script-boundary: Add recipe to deploy the boot scripts
>   nitrogen6x: Add machine definition
>
>  conf/machine/nitrogen6x.conf                     |   28 ++++++++++++++++
>  recipes-bsp/u-boot/u-boot-boundary_git.bb        |   16 ++++++++++
>  recipes-bsp/u-boot/u-boot-script-boundary_git.bb |   37
> ++++++++++++++++++++++
>  3 files changed, 81 insertions(+)
>  create mode 100644 conf/machine/nitrogen6x.conf
>  create mode 100644 recipes-bsp/u-boot/u-boot-boundary_git.bb
>  create mode 100644 recipes-bsp/u-boot/u-boot-script-boundary_git.bb


Eric and Troy,

Please give this patchset a try as I don't own the board to try it myself.

Please bear on mind that this patchset depends on the "[PATCH 0/2]
Flexibilize sdcard generation" patchset to proper work.

Regards,

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

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

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Eric Nelson]

On 12/10/2012 09:11 AM, Otavio Salvador wrote:
> On Mon, Dec 10, 2012 at 2:06 PM, Otavio Salvador <otavio@ossystems.com.br>wrote:
>
>> This patchset adds support for Nitrogen6X using the deployment used by
>> Boundary Devices. The generated sdcard should just work in the board.
>>
>> The patches are untested as I don't own a Nitrogen6X and would be good
>> if someone could test those before we apply them.
>>
>> Otavio Salvador (3):
>>    u-boot-boundary: Add U-Boot recipe for Boundary Devices version
>>    u-boot-script-boundary: Add recipe to deploy the boot scripts
>>    nitrogen6x: Add machine definition
>>
>>   conf/machine/nitrogen6x.conf                     |   28 ++++++++++++++++
>>   recipes-bsp/u-boot/u-boot-boundary_git.bb        |   16 ++++++++++
>>   recipes-bsp/u-boot/u-boot-script-boundary_git.bb |   37
>> ++++++++++++++++++++++
>>   3 files changed, 81 insertions(+)
>>   create mode 100644 conf/machine/nitrogen6x.conf
>>   create mode 100644 recipes-bsp/u-boot/u-boot-boundary_git.bb
>>   create mode 100644 recipes-bsp/u-boot/u-boot-script-boundary_git.bb
>
>
> Eric and Troy,
>
> Please give this patchset a try as I don't own the board to try it myself.
>
> Please bear on mind that this patchset depends on the "[PATCH 0/2]
> Flexibilize sdcard generation" patchset to proper work.
>
> Regards,
>

Will do.

The patches all apply cleanly to meta-fsl-arm and I'm building now.

Understanding will likely take a while ;)

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Otavio Salvador]

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

On Mon, Dec 10, 2012 at 5:47 PM, Eric Nelson <
eric.nelson@boundarydevices.com> wrote:

> On 12/10/2012 09:11 AM, Otavio Salvador wrote:
>
>> On Mon, Dec 10, 2012 at 2:06 PM, Otavio Salvador <otavio@ossystems.com.br
>> >**wrote:
>>
>>  This patchset adds support for Nitrogen6X using the deployment used by
>>> Boundary Devices. The generated sdcard should just work in the board.
>>>
>>> The patches are untested as I don't own a Nitrogen6X and would be good
>>> if someone could test those before we apply them.
>>>
>>> Otavio Salvador (3):
>>>    u-boot-boundary: Add U-Boot recipe for Boundary Devices version
>>>    u-boot-script-boundary: Add recipe to deploy the boot scripts
>>>    nitrogen6x: Add machine definition
>>>
>>>   conf/machine/nitrogen6x.conf                     |   28
>>> ++++++++++++++++
>>>   recipes-bsp/u-boot/u-boot-**boundary_git.bb<http://u-boot-boundary_git.bb>       |   16 ++++++++++
>>>   recipes-bsp/u-boot/u-boot-**script-boundary_git.bb<http://u-boot-script-boundary_git.bb>|   37
>>> ++++++++++++++++++++++
>>>   3 files changed, 81 insertions(+)
>>>   create mode 100644 conf/machine/nitrogen6x.conf
>>>   create mode 100644 recipes-bsp/u-boot/u-boot-**boundary_git.bb<http://u-boot-boundary_git.bb>
>>>   create mode 100644 recipes-bsp/u-boot/u-boot-**script-boundary_git.bb<http://u-boot-script-boundary_git.bb>
>>>
>>
>>
>> Eric and Troy,
>>
>> Please give this patchset a try as I don't own the board to try it myself.
>>
>> Please bear on mind that this patchset depends on the "[PATCH 0/2]
>> Flexibilize sdcard generation" patchset to proper work.
>>
>> Regards,
>>
>>
> Will do.
>
> The patches all apply cleanly to meta-fsl-arm and I'm building now.
>
> Understanding will likely take a while ;)
>

I bet that in two weeks you'll be proposing major changes and improvements
;-)

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

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

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Eric Nelson]

On 12/10/2012 12:50 PM, Otavio Salvador wrote:
> On Mon, Dec 10, 2012 at 5:47 PM, Eric Nelson <
> eric.nelson@boundarydevices.com> wrote:
>
>> On 12/10/2012 09:11 AM, Otavio Salvador wrote:
>>
>>>
>>> Eric and Troy,
>>>
>>> Please give this patchset a try as I don't own the board to try it myself.
>>>
>>> Please bear on mind that this patchset depends on the "[PATCH 0/2]
>>> Flexibilize sdcard generation" patchset to proper work.
>>>
>>> Regards,
>>>
>>>
>> Will do.
>>
>> The patches all apply cleanly to meta-fsl-arm and I'm building now.
>>
>> Understanding will likely take a while ;)
>>
>
> I bet that in two weeks you'll be proposing major changes and improvements
> ;-)
>
Thanks Otavio,

If so, it will feel like Christmas!

After pulling all kinda N00b stuff, I finally got a build to complete
for 'nitrogen6x', but it failed with the following errors

-----------------------------------------------------------------------------
| Creating journal inode: done
| This filesystem will be automatically checked every 20 mounts or
| 0 days, whichever comes first.  Use tune2fs -c or -i to override.
| 0+0 records in
| 0+0 records out
| 0 bytes (0 B) copied, 1.098e-05 s, 0.0 kB/s
| Model:  (file)
| Disk 
/home/ericn/yocto/build/tmp/deploy/images/fsl-image-test-nitrogen6x-20121211024022.rootfs.sdcard: 
390MB
| Sector size (logical/physical): 512B/512B
| Partition Table: msdos
| Disk Flags:
|
| Number  Start   End     Size    Type     File system  Flags
|  1      4194kB  12.6MB  8389kB  primary
|  2      12.6MB  386MB   373MB   primary
|
| mkfs.vfat 2.11 (12 Mar 2005)
| 6x_bootscript-nitrogen6x.txt: No such file or directory
| ERROR: Function failed: do_rootfs (see 
/home/ericn/yocto/build/tmp/work/nitrogen6x-poky-linux-gnueabi/fsl-image-test-1.0-r0/temp/log.do_rootfs.3886 
for further information)
ERROR: Task 7 
(/home/ericn/yocto/sources/meta-fsl-demos/recipes-fsl/images/fsl-image-test.bb, 
do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3983 tasks of which 2321 didn't need to 
be rerun and 1 failed.
No currently running tasks (3983 of 3984)

Summary: 1 task failed:
 
/home/ericn/yocto/sources/meta-fsl-demos/recipes-fsl/images/fsl-image-test.bb, 
do_rootfs
Summary: There were 2 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
------------------------------------------------------------------------

This brings up a couple of questions.

What boot script? I think I saw a reference to one that we placed
in our U-Boot tree in one of your patches, but I'll need to spend some
more time with that.

Why two partitions? It seems that unless a RAM disk is used, a
single partition should suffice. The same is true of SABRE Lite,
but I just noticed that the Freescale default environment only
supports FAT for some reason :(.

It's been a long day. I'll look at this some more tomorrow.

Regards,


Eric

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Eric Bénard]

Hi Eric,

Le Mon, 10 Dec 2012 20:58:22 -0700,
Eric Nelson <eric.nelson@boundarydevices.com> a écrit :
> | 6x_bootscript-nitrogen6x.txt: No such file or directory

Does that work if you do bibake u-boot-script-boundary before building
the image ?

Eric

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Eric Nelson]

On 12/11/2012 01:23 AM, Eric Bénard wrote:
> Hi Eric,
>
> Le Mon, 10 Dec 2012 20:58:22 -0700,
> Eric Nelson <eric.nelson@boundarydevices.com> a écrit :
>> | 6x_bootscript-nitrogen6x.txt: No such file or directory
>
> Does that work if you do bibake u-boot-script-boundary before building
> the image ?
>

Thanks Eric,

That allows things to work, so it seems we have a missing dependency.

We still have an issue though. The generic boot script in our git
repository has a couple of references that presume a single
partition:

	https://github.com/boundarydevices/u-boot-imx6/blob/production/board/boundary/nitrogen6x/6x_bootscript.txt#L56

In particular, the 'root=/dev/mmcblk0p1' clause and the 1 in the
command:
	${fs}load mmc ${disk}:1

The SD card created by bitbake is configured for two:

	~/yocto/build$ fdisk -l 
tmp/deploy/images/fsl-image-test-nitrogen6x-20121211024022.rootfs.sdcard
	...
	Device Boot      Start         End      Blocks   Id  System
      ...sdcard1            8192       24575        8192   83  Linux
      ...sdcard2           24576      753663      364544   83  Linux

It trivially easy to create a boot script specifically for Yocto
images, but this should probably be discussed.

Why should we use two partitions? It seems that unless we're loading
a RAM disk, there's no benefit in having multiple partitions.

I suspect that there's a way to create a RAM disk in Yocto, but
I'm not sure where to start besides Googling the MLs and grepping
the sources.

If we decide to use a single partition, it also seems that the
.sdcard target is a bit of overkill, and a tar-ball of the RFS
is sufficient.

Regards,


Eric

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Otavio Salvador]

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

On Tue, Dec 11, 2012 at 12:09 PM, Eric Nelson <
eric.nelson@boundarydevices.com> wrote:

> On 12/11/2012 01:23 AM, Eric Bénard wrote:
>
>> Hi Eric,
>>
>> Le Mon, 10 Dec 2012 20:58:22 -0700,
>> Eric Nelson <eric.nelson@boundarydevices.**com<eric.nelson@boundarydevices.com>>
>> a écrit :
>>
>>> | 6x_bootscript-nitrogen6x.txt: No such file or directory
>>>
>>
>> Does that work if you do bibake u-boot-script-boundary before building
>> the image ?
>>
>>
> Thanks Eric,
>
> That allows things to work, so it seems we have a missing dependency.
>
> We still have an issue though. The generic boot script in our git
> repository has a couple of references that presume a single
> partition:
>
>         https://github.com/**boundarydevices/u-boot-imx6/**
> blob/production/board/**boundary/nitrogen6x/6x_**bootscript.txt#L56<https://github.com/boundarydevices/u-boot-imx6/blob/production/board/boundary/nitrogen6x/6x_bootscript.txt#L56>
>
> In particular, the 'root=/dev/mmcblk0p1' clause and the 1 in the
> command:
>         ${fs}load mmc ${disk}:1
>
> The SD card created by bitbake is configured for two:
>
>         ~/yocto/build$ fdisk -l tmp/deploy/images/fsl-image-**
> test-nitrogen6x-**20121211024022.rootfs.sdcard
>         ...
>         Device Boot      Start         End      Blocks   Id  System
>      ...sdcard1            8192       24575        8192   83  Linux
>      ...sdcard2           24576      753663      364544   83  Linux
>
> It trivially easy to create a boot script specifically for Yocto
> images, but this should probably be discussed.
>

We can apply a patch in the script for it. Can you please generate a patch
to adapt the script for our environment?


> Why should we use two partitions? It seems that unless we're loading
> a RAM disk, there's no benefit in having multiple partitions.
>
> I suspect that there's a way to create a RAM disk in Yocto, but
> I'm not sure where to start besides Googling the MLs and grepping
> the sources.
>

The real benefit here is to avoid too much complexity in sdcard class. For
accomplish it in a single partition we'd need to flexibilize the class even
more and I am not sure it is worth the effort.


> If we decide to use a single partition, it also seems that the
> .sdcard target is a bit of overkill, and a tar-ball of the RFS
> is sufficient.
>

The idea to provide a sdcard image is to allow for easier test and use of
the build images. It is a matter of dd the fine, directly in the sdcard and
be done with that.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

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

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Eric Nelson]

On 12/11/2012 07:15 AM, Otavio Salvador wrote:
> On Tue, Dec 11, 2012 at 12:09 PM, Eric Nelson <
> eric.nelson@boundarydevices.com> wrote:
>
>> On 12/11/2012 01:23 AM, Eric Bénard wrote:
>>
>>
>> It trivially easy to create a boot script specifically for Yocto
>> images, but this should probably be discussed.
>>
>
> We can apply a patch in the script for it. Can you please generate a patch
> to adapt the script for our environment?
>
Can do.

There's another issue though. The boot scripts need to be wrapped
by 'mkimage' so that U-Boot will 'source' them properly.

e.g.
	mkimage -A arm -O linux -T script -C none -a 0 -e 0 \
		-n "boot script" -d 6x_bootscript.txt 6x_bootscript


I just copied the SD card image and found that the .txt files
were copied, but not compiled.

>> Why should we use two partitions? It seems that unless we're loading
>> a RAM disk, there's no benefit in having multiple partitions.
>>
>> I suspect that there's a way to create a RAM disk in Yocto, but
>> I'm not sure where to start besides Googling the MLs and grepping
>> the sources.
>>
>
> The real benefit here is to avoid too much complexity in sdcard class. For
> accomplish it in a single partition we'd need to flexibilize the class even
> more and I am not sure it is worth the effort.
>
>
>> If we decide to use a single partition, it also seems that the
>> .sdcard target is a bit of overkill, and a tar-ball of the RFS
>> is sufficient.
>>
>
> The idea to provide a sdcard image is to allow for easier test and use of
> the build images. It is a matter of dd the fine, directly in the sdcard and
> be done with that.
>

Okay with me for now. At least this will get us up and bootable.

Regards,


Eric

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Otavio Salvador]

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

On Tue, Dec 11, 2012 at 12:29 PM, Eric Nelson <
eric.nelson@boundarydevices.com> wrote:

> On 12/11/2012 07:15 AM, Otavio Salvador wrote:
>
>> On Tue, Dec 11, 2012 at 12:09 PM, Eric Nelson <
>> eric.nelson@boundarydevices.**com <eric.nelson@boundarydevices.com>>
>> wrote:
>>
>>  On 12/11/2012 01:23 AM, Eric Bénard wrote:
>>>
>>>
>>> It trivially easy to create a boot script specifically for Yocto
>>> images, but this should probably be discussed.
>>>
>>>
>> We can apply a patch in the script for it. Can you please generate a patch
>> to adapt the script for our environment?
>>
>>  Can do.
>
> There's another issue though. The boot scripts need to be wrapped
> by 'mkimage' so that U-Boot will 'source' them properly.
>
> e.g.
>         mkimage -A arm -O linux -T script -C none -a 0 -e 0 \
>                 -n "boot script" -d 6x_bootscript.txt 6x_bootscript
>
>
> I just copied the SD card image and found that the .txt files
> were copied, but not compiled.


Right; so this needs to be done in u-boot-script-boundary. I will take a
look about how to do that.


>  Why should we use two partitions? It seems that unless we're loading
>>> a RAM disk, there's no benefit in having multiple partitions.
>>>
>>> I suspect that there's a way to create a RAM disk in Yocto, but
>>> I'm not sure where to start besides Googling the MLs and grepping
>>> the sources.
>>>
>>>
>> The real benefit here is to avoid too much complexity in sdcard class. For
>> accomplish it in a single partition we'd need to flexibilize the class
>> even
>> more and I am not sure it is worth the effort.
>>
>>
>>  If we decide to use a single partition, it also seems that the
>>> .sdcard target is a bit of overkill, and a tar-ball of the RFS
>>> is sufficient.
>>>
>>>
>> The idea to provide a sdcard image is to allow for easier test and use of
>> the build images. It is a matter of dd the fine, directly in the sdcard
>> and
>> be done with that.
>>
>>
> Okay with me for now. At least this will get us up and bootable.
>

Nice.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

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

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Harmalkar, Subodh S.]

FYI.. my core-image-minimal build failed.

| 0 bytes (0 B) copied, 3.6108e-05 s, 0.0 kB/s
| Model:  (file)
| Disk /home/subodh/fsl-community-bsp/build/tmp/deploy/images/core-image-minimal-nitrogen6x-20121210232351.rootfs.sdcard: 29.4MB
| Sector size (logical/physical): 512B/512B
| Partition Table: msdos
| Disk Flags:
| 
| Number  Start   End     Size    Type     File system  Flags
|  1      4194kB  12.6MB  8389kB  primary
|  2      12.6MB  25.2MB  12.6MB  primary
| 
| mkfs.vfat 2.11 (12 Mar 2005)
| 6x_bootscript-nitrogen6x.txt: No such file or directory
| ERROR: Function failed: do_rootfs (see /home/subodh/fsl-community-bsp/build/tmp/work/nitrogen6x-poky-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.3183 for further information)

Thanks.

Subodh

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Otavio Salvador]

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

On Tue, Dec 11, 2012 at 11:27 AM, Harmalkar, Subodh S. <
Subodh.Harmalkar@jhuapl.edu> wrote:

> FYI.. my core-image-minimal build failed.
>
> | 0 bytes (0 B) copied, 3.6108e-05 s, 0.0 kB/s
> | Model:  (file)
> | Disk
> /home/subodh/fsl-community-bsp/build/tmp/deploy/images/core-image-minimal-nitrogen6x-20121210232351.rootfs.sdcard:
> 29.4MB
> | Sector size (logical/physical): 512B/512B
> | Partition Table: msdos
> | Disk Flags:
> |
> | Number  Start   End     Size    Type     File system  Flags
> |  1      4194kB  12.6MB  8389kB  primary
> |  2      12.6MB  25.2MB  12.6MB  primary
> |
> | mkfs.vfat 2.11 (12 Mar 2005)
> | 6x_bootscript-nitrogen6x.txt: No such file or directory
> | ERROR: Function failed: do_rootfs (see
> /home/subodh/fsl-community-bsp/build/tmp/work/nitrogen6x-poky-linux-gnueabi/core-image-minimal-1.0-r0/temp/log.do_rootfs.3183
> for further information)
>

build u-boot-script-boundary before building the image.

I'll fix it for a v2.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

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

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Otavio Salvador]

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

On Tue, Dec 11, 2012 at 1:58 AM, Eric Nelson <
eric.nelson@boundarydevices.com> wrote:

> On 12/10/2012 12:50 PM, Otavio Salvador wrote:
>
>> On Mon, Dec 10, 2012 at 5:47 PM, Eric Nelson <
>> eric.nelson@boundarydevices.**com <eric.nelson@boundarydevices.com>>
>> wrote:
>>
>>  On 12/10/2012 09:11 AM, Otavio Salvador wrote:
>>>
>>>
>>>> Eric and Troy,
>>>>
>>>> Please give this patchset a try as I don't own the board to try it
>>>> myself.
>>>>
>>>> Please bear on mind that this patchset depends on the "[PATCH 0/2]
>>>> Flexibilize sdcard generation" patchset to proper work.
>>>>
>>>> Regards,
>>>>
>>>>
>>>>  Will do.
>>>
>>> The patches all apply cleanly to meta-fsl-arm and I'm building now.
>>>
>>> Understanding will likely take a while ;)
>>>
>>>
>> I bet that in two weeks you'll be proposing major changes and improvements
>> ;-)
>>
>>  Thanks Otavio,
>
> If so, it will feel like Christmas!
>
> After pulling all kinda N00b stuff, I finally got a build to complete
> for 'nitrogen6x', but it failed with the following errors
>
> ------------------------------**------------------------------**
> -----------------
> | Creating journal inode: done
> | This filesystem will be automatically checked every 20 mounts or
> | 0 days, whichever comes first.  Use tune2fs -c or -i to override.
> | 0+0 records in
> | 0+0 records out
> | 0 bytes (0 B) copied, 1.098e-05 s, 0.0 kB/s
> | Model:  (file)
> | Disk /home/ericn/yocto/build/tmp/**deploy/images/fsl-image-test-**
> nitrogen6x-20121211024022.**rootfs.sdcard: 390MB
> | Sector size (logical/physical): 512B/512B
> | Partition Table: msdos
> | Disk Flags:
> |
> | Number  Start   End     Size    Type     File system  Flags
> |  1      4194kB  12.6MB  8389kB  primary
> |  2      12.6MB  386MB   373MB   primary
> |
> | mkfs.vfat 2.11 (12 Mar 2005)
> | 6x_bootscript-nitrogen6x.txt: No such file or directory
> | ERROR: Function failed: do_rootfs (see /home/ericn/yocto/build/tmp/**
> work/nitrogen6x-poky-linux-**gnueabi/fsl-image-test-1.0-r0/**temp/log.do_rootfs.3886
> for further information)
> ERROR: Task 7 (/home/ericn/yocto/sources/**meta-fsl-demos/recipes-fsl/**
> images/fsl-image-test.bb, do_rootfs) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 3983 tasks of which 2321 didn't need to be
> rerun and 1 failed.
> No currently running tasks (3983 of 3984)
>
> Summary: 1 task failed:
>
> /home/ericn/yocto/sources/**meta-fsl-demos/recipes-fsl/**images/
> fsl-image-test.bb, do_rootfs
> Summary: There were 2 WARNING messages shown.
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> ------------------------------**------------------------------**
> ------------
>
> This brings up a couple of questions.
>
> What boot script? I think I saw a reference to one that we placed
> in our U-Boot tree in one of your patches, but I'll need to spend some
> more time with that.
>

I see; please try to boot u-boot-script-boundary package and try again. It
should work then.


> Why two partitions? It seems that unless a RAM disk is used, a
> single partition should suffice. The same is true of SABRE Lite,
> but I just noticed that the Freescale default environment only
> supports FAT for some reason :(.
>
> It's been a long day. I'll look at this some more tomorrow.
>

The sdcard generation routine works this way and I'd like to do minimal
changes on this, if possible. Currently the change I am doing is to have
the boot script in the first partition. Maybe we'd need to patch the boot
script to be able to load kernel and pass the right root param, but rest
should work fine.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

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

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Eric Nelson]

Hi Otavio,

On 12/11/2012 07:10 AM, Otavio Salvador wrote:
> On Tue, Dec 11, 2012 at 1:58 AM, Eric Nelson <
> eric.nelson@boundarydevices.com> wrote:
>
>>
>> This brings up a couple of questions.
>>
>> What boot script? I think I saw a reference to one that we placed
>> in our U-Boot tree in one of your patches, but I'll need to spend some
>> more time with that.
>>
>
> I see; please try to boot u-boot-script-boundary package and try again. It
> should work then.
>
>
>> Why two partitions? It seems that unless a RAM disk is used, a
>> single partition should suffice. The same is true of SABRE Lite,
>> but I just noticed that the Freescale default environment only
>> supports FAT for some reason :(.
>>
>
> The sdcard generation routine works this way and I'd like to do minimal
> changes on this, if possible. Currently the change I am doing is to have
> the boot script in the first partition. Maybe we'd need to patch the boot
> script to be able to load kernel and pass the right root param, but rest
> should work fine.
>

I have no problem building 6x_bootscript_yocto and adding it to our git
repository. I think this will require a bump in the revision.

Do you want to keep uImage in the root of the first partition, and
format that as FAT?

Please advise,


Eric

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Otavio Salvador]

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

On Tue, Dec 11, 2012 at 12:24 PM, Eric Nelson <
eric.nelson@boundarydevices.com> wrote:

> Hi Otavio,
>
>
> On 12/11/2012 07:10 AM, Otavio Salvador wrote:
>
>> On Tue, Dec 11, 2012 at 1:58 AM, Eric Nelson <
>> eric.nelson@boundarydevices.**com <eric.nelson@boundarydevices.com>>
>> wrote:
>>
>>
>>> This brings up a couple of questions.
>>>
>>> What boot script? I think I saw a reference to one that we placed
>>> in our U-Boot tree in one of your patches, but I'll need to spend some
>>> more time with that.
>>>
>>>
>> I see; please try to boot u-boot-script-boundary package and try again. It
>> should work then.
>>
>>
>>  Why two partitions? It seems that unless a RAM disk is used, a
>>> single partition should suffice. The same is true of SABRE Lite,
>>> but I just noticed that the Freescale default environment only
>>> supports FAT for some reason :(.
>>>
>>>
>> The sdcard generation routine works this way and I'd like to do minimal
>> changes on this, if possible. Currently the change I am doing is to have
>> the boot script in the first partition. Maybe we'd need to patch the boot
>> script to be able to load kernel and pass the right root param, but rest
>> should work fine.
>>
>>
> I have no problem building 6x_bootscript_yocto and adding it to our git
> repository. I think this will require a bump in the revision.
>
> Do you want to keep uImage in the root of the first partition, and
> format that as FAT?
>

At least for now. I'd like to keep the change at minimum. We can refactor
and improve it later.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

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

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Eric Nelson]

Hi Otavio,

On 12/11/2012 07:35 AM, Otavio Salvador wrote:
> On Tue, Dec 11, 2012 at 12:24 PM, Eric Nelson <
> eric.nelson@boundarydevices.com> wrote:
>>
>> On 12/11/2012 07:10 AM, Otavio Salvador wrote:
>>> On Tue, Dec 11, 2012 at 1:58 AM, Eric Nelson <
>>> eric.nelson@boundarydevices.**com <eric.nelson@boundarydevices.com>>
>>> wrote:
>>>
>>>>
>>> The sdcard generation routine works this way and I'd like to do minimal
>>> changes on this, if possible. Currently the change I am doing is to have
>>> the boot script in the first partition. Maybe we'd need to patch the boot
>>> script to be able to load kernel and pass the right root param, but rest
>>> should work fine.
>>>
>> I have no problem building 6x_bootscript_yocto and adding it to our git
>> repository. I think this will require a bump in the revision.
>>
>> Do you want to keep uImage in the root of the first partition, and
>> format that as FAT?
>>
> At least for now. I'd like to keep the change at minimum. We can refactor
> and improve it later.
>

Do you know the context (directory) in which the patch will be applied?

Will it be from the root of the U-Boot tree and patch
	board/boundary/nitrogen6x/6x_bootscript.txt
	board/boundary/nitrogen6x/6x_upgrade.txt

Or will it be applied somewhere in the work directory?

Also, the 6x_upgrade script is useless unless we copy u-boot.imx
into one of the partitions. Should it go into the FAT partition or
the ext3 partition?

Please advise,


Eric

Re: [meta-fsl-arm-extra][PATCH 0/3] Initial support for Nitrogen6X

[Otavio Salvador]

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

On Tue, Dec 11, 2012 at 1:48 PM, Eric Nelson <
eric.nelson@boundarydevices.com> wrote:

> Hi Otavio,
>
>
> On 12/11/2012 07:35 AM, Otavio Salvador wrote:
>
>> On Tue, Dec 11, 2012 at 12:24 PM, Eric Nelson <
>> eric.nelson@boundarydevices.**com <eric.nelson@boundarydevices.com>>
>> wrote:
>>
>>>
>>> On 12/11/2012 07:10 AM, Otavio Salvador wrote:
>>>
>>>> On Tue, Dec 11, 2012 at 1:58 AM, Eric Nelson <
>>>> eric.nelson@boundarydevices.****com <eric.nelson@boundarydevices.**com<eric.nelson@boundarydevices.com>
>>>> >>
>>>>
>>>> wrote:
>>>>
>>>>
>>>>>  The sdcard generation routine works this way and I'd like to do
>>>> minimal
>>>> changes on this, if possible. Currently the change I am doing is to have
>>>> the boot script in the first partition. Maybe we'd need to patch the
>>>> boot
>>>> script to be able to load kernel and pass the right root param, but rest
>>>> should work fine.
>>>>
>>>>  I have no problem building 6x_bootscript_yocto and adding it to our git
>>> repository. I think this will require a bump in the revision.
>>>
>>> Do you want to keep uImage in the root of the first partition, and
>>> format that as FAT?
>>>
>>>  At least for now. I'd like to keep the change at minimum. We can
>> refactor
>> and improve it later.
>>
>>
> Do you know the context (directory) in which the patch will be applied?
>
> Will it be from the root of the U-Boot tree and patch
>         board/boundary/nitrogen6x/6x_**bootscript.txt
>         board/boundary/nitrogen6x/6x_**upgrade.txt
>

Or will it be applied somewhere in the work directory?
>

Applied from root of U-Boot tree.


> Also, the 6x_upgrade script is useless unless we copy u-boot.imx
> into one of the partitions. Should it go into the FAT partition or
> the ext3 partition?
>

I left it in deploy if someone wish to take it. I don't want to install it
as it might put people at risk of breaking their board (even though the
u-boot source has been taken from your production branch).

Let's go for fat, by now.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

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