[meta-freescale] Advantech UBC-200
cyclist2918 at gmail.com
Tue Feb 24 08:37:11 PST 2015
On Tue, Feb 24, 2015 at 10:16 AM, Daiane Angolini <daiane.list at gmail.com>
> On Tue, Feb 24, 2015 at 11:22 AM, Dan Gundlach <cyclist2918 at gmail.com>
> > On Tue, Feb 24, 2015 at 5:51 AM, Daiane Angolini <daiane.list at gmail.com>
> > wrote:
> >> On Mon, Feb 23, 2015 at 10:09 PM, Dan Gundlach <cyclist2918 at gmail.com>
> >> wrote:
> >> > I'm trying to install dizzy to an Advantech UBC-200. It's basically a
> >> > Sabre
> >> > SD.
> >> >
> >> > I tried building various images, but none of them would boot unless I
> >> > used
> >> > the stock kernel (3.0.35) configuration, which I built using the
> >> > based BSP from Advantech. I had to make a change to the kernel
> >> > configuration for udev-182, and was able to get it to start. I had to
> >> > manually create the sdcard using the scripts from the BSP. I'm using
> >> > the
> >> > core-image-full-cmdline recipe.
> >> >
> >> > It looks like everything is starting except for the network. I'm not
> >> > getting a kernel message recognizing the network adapter. I'm not
> >> > getting an ip address on the lo device. The new kernel works
> >> > when
> >> > installed on the rescue image that I made using the BSP, so I'm
> >> > as
> >> > to what the problem is.
> >> For me, it looks like you have a kernel problem.
> >> Using the same rootfs, you get different result when changing the
> >> kernel, so for me the problem is the kernel.
> > What I'm trying to do is build a Yocto system wrapped around a known
> > kernel and u-boot, since the image built using Yocto was not even
> > by the machine.
> > I guess that I wasn't clear in explaining my problem. The modified
> > works with the original rootfs on an SD card, while I'm getting a failure
> > with the Yocto rootfs. I'm pretty sure that I'm missing something in my
> > kernel configuration that some package (udev?) in Yocto needs. The only
> > difference between the original kernel and the one I built is support for
> > devtmpfs. I've pasted the kernel configuration below.
> Take a look here:
> Maybe, it can help you with some patch.
Thanks for that info. I was unsuccessful in finding a workable Yocto
3.0.35 kernel in my searches.
> And another important point, if you need GPU support it's not that simple.
Fortunately, that's not applicable here.
> > The u-boot installed on the system is 2009.08. Could that be why the
> > I built completely using bitbake wouldn't boot? The system completely
> > ignored the SD card when I used the image I built using bitbake, so I
> > created the image using the tools provided by Advantech. There's only
> > partition on the card, and it's offset so that u-boot and the kernel
> can be
> > written to the card with dd.
> u-boot 2009.08 and 2014.X are hugely different.
> I remember a different set of variable was needed to use u-boot
> 2009.08 in yocto.
> So, yes, maybe it was copied wrongly to the sdcard and nothing happens.
> However, if you are working only with the pieces, I'm sure you can get
> your u-boot to mount the system, depending on the way you configure
> the sdcard and bootenv.
The Yocto rootfs is mounting and starting processes, but it's not setting
up the network, which unfortunately is the only way I'm able to get a shell
(through telnet or ssh). I'm having it write the output of "dmesg", "ps
ax", and "ifconfig" to a file during startup, and the only one not working
The only connector that I can see on the board for any type of serial
output is a usb port. The kernel is reporting a bootconsole on
/dev/ttymxc0. Would I connect to that through the usb port? The kernel is
reporting 5 UARTs. The board is inside a case, which I opened to see if
there are any other connectors for serial communications. I didn't see any.
Am I correct in assuming that it's udev that finds the network interface,
even though the kernel is monolithic? Running dmesg on the stock
configuration shows the ethernet PHY reported after udevd starts.
> I assume you mean the .ext3 rootfs when you say yocto rootfs (and not
> the .sdcard image)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the meta-freescale