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

Eric Nelson eric.nelson at boundarydevices.com
Mon Dec 10 19:58:22 PST 2012

On 12/10/2012 12:50 PM, Otavio Salvador wrote:
> On Mon, Dec 10, 2012 at 5:47 PM, Eric Nelson <
> eric.nelson at 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 
| 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 
for further information)
ERROR: Task 7 
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:
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.



More information about the meta-freescale mailing list