Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 05 Sep 2016 22:41:37 +0200
From:      "Ronald Klop" <ronald-lists@klop.ws>
To:        "Russell Haley" <russ.haley@gmail.com>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: Fwd: Paid Support for iMX6 Port
Message-ID:  <op.ynb3rn1kkndu52@d93fd8ae.cm-21.dynamic.ziggo.nl>
In-Reply-To: <CABx9NuSJ0m06J=a7M=vLksbGLH_4n7fAfvLhQYybZO_HqRNwRQ@mail.gmail.com>
References:  <SN1PR0201MB15343313B83CCDFFEC52F1C798050@SN1PR0201MB1534.namprd02.prod.outlook.com> <CABx9NuQMRdP%2BmMeuf3Zum3onME8qEXL0ty6yQp1tZHuU=ockiw@mail.gmail.com> <SN1PR0201MB153446C48ADBB666C021AB3098050@SN1PR0201MB1534.namprd02.prod.outlook.com> <CABx9NuSF2K427XKMj_2gGDW1OyaXodF6PukQS%2BufAv5Z_ZSZMQ@mail.gmail.com> <CABx9NuSR6MSkHFROjc7HkjCBS6NTScD=rfpi65qYWJwA0gpmQQ@mail.gmail.com> <op.ylmk7wqokndu52@53555a16.cm-6-6b.dynamic.ziggo.nl> <CABx9NuSJ0m06J=a7M=vLksbGLH_4n7fAfvLhQYybZO_HqRNwRQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 05 Aug 2016 22:25:09 +0200, Russell Haley <russ.haley@gmail.com>  
wrote:

> On Wed, Aug 3, 2016 at 8:27 AM, Ronald Klop <ronald-lists@klop.ws> wrote:
>> On Wed, 03 Aug 2016 00:16:55 +0200, Russell Haley <russ.haley@gmail.com>
>> wrote:
>>
>>> Sorry, reply instead of reply all...
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Russell Haley <russ.haley@gmail.com>
>>> Date: Tue, Aug 2, 2016 at 3:16 PM
>>> Subject: Re: Paid Support for iMX6 Port
>>> To: Michel Kohanim <michel@universal-devices.com>
>>>
>>>
>>> On Tue, Aug 2, 2016 at 2:39 PM, Michel Kohanim
>>> <michel@universal-devices.com> wrote:
>>>>
>>>> Hi Russell,
>>>>
>>>> Thanks so very much for getting in touch. Hopefully the experienced  
>>>> iMX6
>>>> developer will chime in. Again, I am willing to pay for services and  
>>>> then
>>>> share the results with the community.
>>>>
>>>> 1. Would love to read your notes on Hummingboard. I am using Wandboard
>>>> and Wandboard Dual for testing purposes and have been able to get  
>>>> FreeBSD
>>>> binary image (from the website) loaded and functioning albeit it's  
>>>> way too
>>>> slow even for rudimentary tasks such as vi (on the Solo). I suspect  
>>>> 512MB is
>>>> not sufficient. Ultimately, I would like to be able to make a smaller  
>>>> image
>>>> ourselves but have been having a hell of a time with Crochet
>>>
>>>
>>> Give me a few days, I just got back from vacation and kids don't sleep
>>> well during summer hours so I have very limited time right now, but I
>>> will get you what I have so far.
>>>
>>> <snip>
>>>
>>>> 6. NAND flash/eMMC ... our main goal is that - at the minimum - the
>>>> kernel should be on a flash chip of some sort so that boot up does NOT
>>>> require an SD Card. Are you aware of any flash chip that can be used  
>>>> by
>>>> uboot to boot FreeBSD?
>>>
>>> It's possible to run u-boot from NAND and then run ubldr/kernel from a
>>> different source. It may even be possible to manually load ubldr from
>>> NAND (or even manually load the kernel from NAND in u-boot) but you
>>> would need to find an alternative for the kernel and rootfs,
>>> especially if you want to update your kernel ever. Not what I would
>>> call desirable, but I have *heard* of production systems running like
>>> this.
>>
>>
>>
>> My Sheevaplug loads the kernel from NAND which mounts the rootfs from
>> USB-stick. And does this for a couple of years already. I used to have a
>> rootfs on nandfs(5) also, but nandfs is not stable enough.
>>
>> # nandtool erase dev=/dev/gnand0s.fbsd-boot
>> # dd if=/tmp/kernel.bin of=/dev/gnand0s.fbsd-boot bs=2k conv=sync
>
> Hi Ronald,
>
> So does this mean you used an freebsd slice for nandfs on the entire
> nand unit and placed u-boot and the kernel within the nandfs slice
> (I'll look at nandfs documentation when I get a chance)? It's probably
> implementation specific, but I wonder if  the partition table and
> nandfs would affect the "hardware boot loaders" ability to find the
> u-boot binary (I don't understand the pre-u-boot boot process yet)?
> Also, are you saying that nandfs is "stable enough" to be used in a
> write-rarely/read-often scheme?
>
> Russ

Hi,

I was on holiday, so a late response. I use this layout.

A little bit adjusted version of: sys/boot/fdt/dts/arm/sheevaplug.dts

                 nand@0,0 {
                         #address-cells = <1>;
                         #size-cells = <1>;
                         compatible = "mrvl,nfc";
                         reg = <0x0 0x0 0x00100000>;
                         bank-width = <2>;
                         device-width = <1>;

                         slice@0 {
                                 reg = <0x0 0x200000>;
                                 label = "u-boot";
                                 read-only;
                         };

                         slice@200000 {
                                 reg = <0x200000 0x600000>;
                                 label = "fbsd-boot";
                         };

                         slice@800000 {
                                 reg = <0x800000 0x1f800000>;
                                 label = "root";
                         };
                 };

Never touched the u-boot part. Added the fbsd-boot part which is written  
by dd as mentioned before (so no fs on it). The 'root' part was nandfs,  
but that did not run very well (it slowly filled up if I remember  
correctly) and is unused now.

Regards,
Ronald.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.ynb3rn1kkndu52>