i *really* want a bootable OE image for my pdlogic am1808 experimenter kit

i *really* want a bootable OE image for my pdlogic am1808 experimenter kit

[Robert P. J. Day]

  as i've mentioned recently, i've just come into possession of one of
these:

  http://www.logicpd.com/products/system-on-modules/zoom-am1808/

and i very badly would like to use OE + meta-ti to build a *very*
simple bootable image -- no graphics, no clutter, just a simple system
that i can populate with some HW/flash tools.

  so the short question is: is there a verified recipe for building
such a thing for precisely that board?  because i haven't been having
a lot of luck.

  assuming the machine choice for that board is the am180x-evm, i
first tried building the ti-hw-bringup-image, but that's broken for a
couple systemd-related reasons so i finally gave up on it.

  i *did* get a successful build for OE's core-image-minimal, but it
won't boot fully so i'm kind of stuck there, and here's where i'm
stuck.  the SD card that comes with the kit boots nicely, and here's
the tail end of the boot to establish a baseline to show what works:

===== boot output =====
... snip ...
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 148K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
udev: starting version 141
Remounting root file system...
Caching udev devnodes
Populating dev cachekjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p3): using internal journal
EXT3-fs (mmcblk0p3): recovery complete
EXT3-fs (mmcblk0p3): mounted filesystem with writeback data mode
mv: cannot rename '/tmp/devices': No such file or directory
NET: Registered protocol family 10
logger: mount: mount point /proc/bus/usb does not exist
ALSA: Restoring mixer settings...
/usr/sbin/alsactl: load_state:1625: No soundcards found...
Configuring network interfaces... eth0: attached PHY driver [SMSC
LAN8710/LAN8720] (mii_bus:phy_addr=1:00, id=7c0f1)
ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.13.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
done.
Setting up IP spoofing protection: rp_filter.
Fri Apr 15 04:54:00 UTC 2011
INIT: Entering runlevel: 5
Starting system message bus: dbus.
Starting Dropbear SSH server: dropbear.
Starting telnet daemon.
Starting syslogd/klogd: done
Starting thttpd.
Starting Matrix GUI application.

 _____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

Arago Project http://arago-project.org am180x-evm ttyS2

Arago 2011.02 am180x-evm ttyS2

am180x-evm login:

===== end of boot output =====

  so, clearly, it can be done.  and here's what happens when i replace
the uImage and root filesystem on that SD card with what came from the
core-image-minimal build:

===== start =====
... snip ...
INIT: version 2.88 booting
Starting udev
Starting Bootlog daemon: bootlogd.
Configuring network interfaces... davinci_mdio davinci_mdio.0:
resetting idled conr
net eth0: attached PHY driver [SMSC LAN8710/LAN8720]
(mii_bus:phy_addr=0:00, id=7c)
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
hwclock: can't open '/dev/misc/rtc': No such file or directory
Thu Jan 31 16:02:00 UTC 2013
hwclock: can't open '/dev/misc/rtc': No such file or directory

   (hangs)

  so the kernel boots, mounts the root filesystem, makes it partway in
and hangs right after that attempted access of the real-time clock.

  i had a few minutes to look further and the device_table file in the
root filesystem refers to /dev/rtc, not to /dev/misc/rtc but i don't
know enough to know if that would be enough to cause the boot to hang,
or if it's something happening right after that.

  in short, i would dearly love a recipe that would give me a bootable
kernel and rootfs for this board.  should i be selecting a different
output image?  thoughts?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: i *really* want a bootable OE image for my pdlogic am1808 experimenter kit

[Javier Martinez Canillas]

> hwclock: can't open '/dev/misc/rtc': No such file or directory
> Thu Jan 31 16:02:00 UTC 2013
> hwclock: can't open '/dev/misc/rtc': No such file or directory
>
>    (hangs)
>

Hi Robert,

I don't have your board but I've seen a similar issue before caused by
using a recent udev and not having enabled CONFIG_DEVTMPFS=y on your
kernel config.

The problem is that since udev-182, udev no longer creates device
nodes under /dev and this has to be managed by the kernel devtmpfs
filesystem.

 This means that a kernel built without devtmpfs config will not boot
since there won't be any device files on /dev.

Hope it helps,
Javier

Re: i *really* want a bootable OE image for my pdlogic am1808 experimenter kit

[Robert P. J. Day]

On Fri, 1 Feb 2013, Javier Martinez Canillas wrote:

> > hwclock: can't open '/dev/misc/rtc': No such file or directory
> > Thu Jan 31 16:02:00 UTC 2013
> > hwclock: can't open '/dev/misc/rtc': No such file or directory
> >
> >    (hangs)
> >
>
> Hi Robert,
>
> I don't have your board but I've seen a similar issue before caused
> by using a recent udev and not having enabled CONFIG_DEVTMPFS=y on
> your kernel config.
>
> The problem is that since udev-182, udev no longer creates device
> nodes under /dev and this has to be managed by the kernel devtmpfs
> filesystem.
>
> This means that a kernel built without devtmpfs config will not
> boot since there won't be any device files on /dev.

  that sounds vaguely familiar, i remember reading that once upon a
time.  which brings me back to my plaintive lament -- is there a
recipe i can use to build a bootable system for this board?

  the SD card that came with it has "arago" splashed all over it so
i'm going to check out the meta-arago layer(s) to see what i get.  but
i would *dearly* love to figure out what it takes to build a working
system for this in the next day or two.

  don't make me beg.  all right, i'm begging ...

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: i *really* want a bootable OE image for my pdlogic am1808 experimenter kit

[Cooper Jr., Franklin]

Robert,
I am currently working on porting am180x to the latest Sitara Linux SDK (http://processors.wiki.ti.com/index.php/Sitara_Linux_Software_Developer%E2%80%99s_Guide). Our Sitara SDK is based on the Arago distribution (http://arago-project.org/git/?p=meta-arago.git;a=summary)

Meta-Arago has the following restrictions:
1. We use a prebuilt toolchain for our oe-core builds (http://software-dl.ti.com/sdoemb/sdoemb_public_sw/arago_toolchain/2011_09/index_FDS.html). You probably can use the tool chain built with oe-core but you have to make a tweak to use the "internal" built tool chain instead of the expected "external" tool chain.
2. Meta-Arago master is based on the latest meta-oe, meta-ti, oe-core maintenance branch. This means you will need to use meta-oe, meta-ti and oe-core danny/denzil branches for things to work without a problem. We just started work on transitioning to danny from denzil.
3. My work for am18 hasn't been pushed to meta-arago or meta-ti yet. But you can see my hacks in the Sitara SDK integration branches.

http://arago-project.org/git/projects/?p=meta-arago-amsdk.git;a=summary Branch: amsdk-05.07.00.00-integration
http://arago-project.org/git/projects/?p=meta-ti-amsdk.git;a=summary Branch: amsdk-05.07.00.00-integration

If you build tisdk-rootfs-image (full SDK root filesystem) or arago-base-image (minimal root filesystem) you should get what you need to get the board booted up.

If you have issues we do have a script that configures everything you need to get up and running and building with our Arago distribution in no time.

> -----Original Message-----
> From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-
> bounces@yoctoproject.org] On Behalf Of Robert P. J. Day
> Sent: Friday, February 01, 2013 5:52 PM
> To: Javier Martinez Canillas
> Cc: meta-ti mailing list
> Subject: Re: [meta-ti] i *really* want a bootable OE image for my pdlogic
> am1808 experimenter kit
> 
> On Fri, 1 Feb 2013, Javier Martinez Canillas wrote:
> 
> > > hwclock: can't open '/dev/misc/rtc': No such file or directory Thu
> > > Jan 31 16:02:00 UTC 2013
> > > hwclock: can't open '/dev/misc/rtc': No such file or directory
> > >
> > >    (hangs)
> > >
> >
> > Hi Robert,
> >
> > I don't have your board but I've seen a similar issue before caused by
> > using a recent udev and not having enabled CONFIG_DEVTMPFS=y on your
> > kernel config.
> >
> > The problem is that since udev-182, udev no longer creates device
> > nodes under /dev and this has to be managed by the kernel devtmpfs
> > filesystem.
> >
> > This means that a kernel built without devtmpfs config will not boot
> > since there won't be any device files on /dev.
> 
>   that sounds vaguely familiar, i remember reading that once upon a time.
> which brings me back to my plaintive lament -- is there a recipe i can use to
> build a bootable system for this board?
> 
>   the SD card that came with it has "arago" splashed all over it so i'm going to
> check out the meta-arago layer(s) to see what i get.  but i would *dearly* love
> to figure out what it takes to build a working system for this in the next day or
> two.
> 
>   don't make me beg.  all right, i'm begging ...
> 
> rday
> 
> --
> 
> ================================================================
> ========
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                         http://crashcourse.ca
> 
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ================================================================
> ========
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti

Re: i *really* want a bootable OE image for my pdlogic am1808 experimenter kit

[Robert P. J. Day]

On Tue, 5 Feb 2013, Cooper Jr., Franklin wrote:

> Robert,

> I am currently working on porting am180x to the latest Sitara Linux
> SDK
> (http://processors.wiki.ti.com/index.php/Sitara_Linux_Software_Developer%E2%80%99s_Guide).
> Our Sitara SDK is based on the Arago distribution
> (http://arago-project.org/git/?p=meta-arago.git;a=summary)
>
> Meta-Arago has the following restrictions:
> 1. We use a prebuilt toolchain for our oe-core builds (http://software-dl.ti.com/sdoemb/sdoemb_public_sw/arago_toolchain/2011_09/index_FDS.html). You probably can use the tool chain built with oe-core but you have to make a tweak to use the "internal" built tool chain instead of the expected "external" tool chain.
> 2. Meta-Arago master is based on the latest meta-oe, meta-ti, oe-core maintenance branch. This means you will need to use meta-oe, meta-ti and oe-core danny/denzil branches for things to work without a problem. We just started work on transitioning to danny from denzil.
> 3. My work for am18 hasn't been pushed to meta-arago or meta-ti yet. But you can see my hacks in the Sitara SDK integration branches.
>
> http://arago-project.org/git/projects/?p=meta-arago-amsdk.git;a=summary Branch: amsdk-05.07.00.00-integration
> http://arago-project.org/git/projects/?p=meta-ti-amsdk.git;a=summary Branch: amsdk-05.07.00.00-integration
>
> If you build tisdk-rootfs-image (full SDK root filesystem) or
> arago-base-image (minimal root filesystem) you should get what you
> need to get the board booted up.
>
> If you have issues we do have a script that configures everything
> you need to get up and running and building with our Arago
> distribution in no time.

  cool, i'll give this a shot in the next day or two, i appreciate it.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: i *really* want a bootable OE image for my pdlogic am1808 experimenter kit

[Denys Dmytriyenko]

On Fri, Feb 01, 2013 at 06:51:59PM -0500, Robert P. J. Day wrote:
> On Fri, 1 Feb 2013, Javier Martinez Canillas wrote:
> 
> > > hwclock: can't open '/dev/misc/rtc': No such file or directory
> > > Thu Jan 31 16:02:00 UTC 2013
> > > hwclock: can't open '/dev/misc/rtc': No such file or directory
> > >
> > >    (hangs)
> > >
> >
> > Hi Robert,
> >
> > I don't have your board but I've seen a similar issue before caused
> > by using a recent udev and not having enabled CONFIG_DEVTMPFS=y on
> > your kernel config.
> >
> > The problem is that since udev-182, udev no longer creates device
> > nodes under /dev and this has to be managed by the kernel devtmpfs
> > filesystem.
> >
> > This means that a kernel built without devtmpfs config will not
> > boot since there won't be any device files on /dev.
> 
>   that sounds vaguely familiar, i remember reading that once upon a
> time.  which brings me back to my plaintive lament -- is there a
> recipe i can use to build a bootable system for this board?
> 
>   the SD card that came with it has "arago" splashed all over it so
> i'm going to check out the meta-arago layer(s) to see what i get.  but
> i would *dearly* love to figure out what it takes to build a working
> system for this in the next day or two.

Robert,

Sorry for not replying earlier - I was quite busy last week finishing up my 
work before I went on travel this week...

As of the SD card that you received with the board - it was the old Arago 
(AMSDK) release, based on the Classic OpenEmbedded 2011.03-maintenance 
branch. And it used udev-141.

What you didn't mention in your emails, is which branch of meta-ti you are 
trying to use. Same for oe-core. So, if it's anything latest, like "master" 
branch, then you are probably trying to use udev-182. And as Javier above 
said, you would need to enable DEVTMPFS config option in the defconfig.

For our TI SDK products we usually stay with the stable branch and so it was 
"denzil" for a while and just last week I pushed all the required changes to 
finally switch to "danny". In either of those cases we are using udev-164. 
Hence, DEVTMPFS is not required to be enabled.

So, if you still want to use the latest master of oe-core and meta-ti, you'd 
be forced to use a more recent udev-182 and hence would need to make a simple 
change in the am180x defconfig to enable DEVTMPFS config option. I'll gladly 
accept a patch from you, if that proves to be the (only) culprit.

As of the Arago images - you are more than welcome to look into meta-arago and 
how things are being built there (e.g. tisdk-rootfs-image), but that maybe too 
specialized for your needs, plus make sure to realize that meta-arago "master" 
branch now depends on "danny" of oe-core/meta-ti/meta-oe and was depending on 
even older "denzil" just before the last week. So, you are maybe better off 
using just the core-image-base or core-image-minimal rootfs images from 
oe-core, depending on your needs, especially if what you need at first is to 
bring the board up...

Please let me know if this works for you or you have any other questions.

-- 
Denys

Re: i *really* want a bootable OE image for my pdlogic am1808 experimenter kit

[Denys Dmytriyenko]

Well, not to derail Franklin's enthusiasm, but below suggestion would point 
Robert into the direction of an unfinished work-in-progress "feature" tree, 
that hasn't been reviewed or merged into the main meta-ti or meta-arago. Plus, 
it doesn't really solve Robert's specific problem and from a quick look at 
it, doesn't have the necessary defconfig change, but works because of older 
udev version...


> I am currently working on porting am180x to the latest Sitara Linux SDK 
> (http://processors.wiki.ti.com/index.php/Sitara_Linux_Software_Developer%E2%80%99s_Guide). 

BTW, Sitara SDK = AMSDK in this context. And Franklin is working on updating 
am180x support from Classic OE to OE-Core. Meaning, there's no newer kernel 
version planned for am180x at this point, unfortunately.


> Our Sitara SDK is based on the Arago distribution 
> (http://arago-project.org/git/?p=meta-arago.git;a=summary)
> Meta-Arago has the following restrictions:
> 1. We use a prebuilt toolchain for our oe-core builds 
> (http://software-dl.ti.com/sdoemb/sdoemb_public_sw/arago_toolchain/2011_09/index_FDS.html). 

Actually, the same Arago toolchain was used for older Classic OE builds of 
Arago-based TI SDK products and is quite old by now - it's gcc-4.5, 
binutils-2.20 and eglibc-2.12. That is the one I built all the way back in 
September 2011.


> You probably can use the tool chain built with oe-core but you have to make 
> a tweak to use the "internal" built tool chain instead of the expected 
> "external" tool chain.

Unfortunately, it's not that easy - I never finished the toolchain framework 
in meta-arago to the same level I had it in old Arago and Classic OE. You can 
switch between 2 prebuilt toolchains for now - Arago gcc-4.5 for AMSDK and 
Linaro gcc-4.6 for MCSDK. The easy way of setting TOOLCHAIN_TYPE=internal to 
build your own toolchain still doesn't work, so that would require more 
extensive changes in the configuration. Finishing that is still on my 
extra-long ToDo list...


> 2. Meta-Arago master is based on the latest meta-oe, meta-ti, oe-core 

The proper term here would be "depends", not "based"...


> maintenance branch. This means you will need to use meta-oe, meta-ti and 
> oe-core danny/denzil branches for things to work without a problem. We just 
> started work on transitioning to danny from denzil.

Should be mostly working now - last week I pushed the groundwork for this 
transition to danny and was able to build tisdk-rootfs-image for couple of our 
platforms.


> 3. My work for am18 hasn't been pushed to meta-arago or meta-ti yet. 
> But you can see my hacks in the Sitara SDK integration branches.

As I mentioned above, these are interim work-in-progress branches and are in 
the early stages of porting/development, so please be aware of hacks (thanks 
Franklin for being honest here :) and possible periodic rebases or reverts of 
commits when we go through the review process in the way to the main meta-ti 
and meta-arago trees. But you are free and welcome to look at the interim 
progress, of course. Let us know if you have any questions. Thanks.

-- 
Denys


> http://arago-project.org/git/projects/?p=meta-arago-amsdk.git;a=summary 
> Branch: amsdk-05.07.00.00-integration
> http://arago-project.org/git/projects/?p=meta-ti-amsdk.git;a=summary Branch: 
> amsdk-05.07.00.00-integration
> 
> If you build tisdk-rootfs-image (full SDK root filesystem) or 
> arago-base-image (minimal root filesystem) you should get what you need to 
> get the board booted up.
> 
> If you have issues we do have a script that configures everything you need 
> to get up and running and building with our Arago distribution in no time.
> 
> > -----Original Message-----
> > From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-
> > bounces@yoctoproject.org] On Behalf Of Robert P. J. Day
> > Sent: Friday, February 01, 2013 5:52 PM
> > To: Javier Martinez Canillas
> > Cc: meta-ti mailing list
> > Subject: Re: [meta-ti] i *really* want a bootable OE image for my pdlogic
> > am1808 experimenter kit
> > 
> > On Fri, 1 Feb 2013, Javier Martinez Canillas wrote:
> > 
> > > > hwclock: can't open '/dev/misc/rtc': No such file or directory Thu
> > > > Jan 31 16:02:00 UTC 2013
> > > > hwclock: can't open '/dev/misc/rtc': No such file or directory
> > > >
> > > >    (hangs)
> > > >
> > >
> > > Hi Robert,
> > >
> > > I don't have your board but I've seen a similar issue before caused by
> > > using a recent udev and not having enabled CONFIG_DEVTMPFS=y on your
> > > kernel config.
> > >
> > > The problem is that since udev-182, udev no longer creates device
> > > nodes under /dev and this has to be managed by the kernel devtmpfs
> > > filesystem.
> > >
> > > This means that a kernel built without devtmpfs config will not boot
> > > since there won't be any device files on /dev.
> > 
> >   that sounds vaguely familiar, i remember reading that once upon a time.
> > which brings me back to my plaintive lament -- is there a recipe i can use to
> > build a bootable system for this board?
> > 
> >   the SD card that came with it has "arago" splashed all over it so i'm going to
> > check out the meta-arago layer(s) to see what i get.  but i would *dearly* love
> > to figure out what it takes to build a working system for this in the next day or
> > two.
> > 
> >   don't make me beg.  all right, i'm begging ...
> > 
> > rday
> > 
> > --
> > 
> > ================================================================
> > ========
> > Robert P. J. Day                                 Ottawa, Ontario, CANADA
> >                         http://crashcourse.ca
> > 
> > Twitter:                                       http://twitter.com/rpjday
> > LinkedIn:                               http://ca.linkedin.com/in/rpjday
> > ================================================================
> > ========
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
>