Hi,

On Aug 2, 2012, at 10:09, Khem Raj <raj.k...@gmail.com> wrote:

> 
> On Aug 1, 2012, at 7:44 PM, Elvis Dowson <elvis.dow...@gmail.com> wrote:
> 
>> Hi Khem,
>> 
>> On Aug 2, 2012, at 2:37 AM, Khem Raj wrote:
>> 
>>> On Aug 1, 2012, at 9:18 AM, Elvis Dowson <elvis.dow...@gmail.com> wrote:
>>> 
>>>> Hi,
>>>>    Perhaps the reason none of my root file system binaries are not working 
>>>> or running is because there is no
>>>> 
>>>> GLIBCTARGETOS ?= "linux-gnueabi"
>>>> 
>>>> in my machine/virtex5.conf or local.conf file? 
>>> 
>>> you don't need to set it. it should be automatically computed based on libc 
>>> and arch
>>> your problem seems more like console related. Probably you don't have 
>>> console params
>>> set correctly or securetty does not know about your console device.
>> 
>> You're right. After rebuilding it, with that variable set, it made no 
>> difference in the generated
>> binaries, (e.g. generate a tool chain powerpc-poky-linux-gnueabi-gcc) nor 
>> did it 
>> change the situation with my having no console login or bash prompt.
>> 
>> The serial port that I am using is ttyS0. There is an entry for ttyS0 under 
>> /dev in my ramdisk
>> , and my /etc/device_table also has an entry for ttyS. 
>> 
>> I have also checked that my securetty has an entry for ttyS0.
>> 
>> I have tried all possible option, e.g. try to get inittab running first with 
>> 
>> S:2345:respawn:/sbin/getty 9600 ttyS0
>> 
>> then with
>> 
>> S:2345:respawn:/bin/sh 9600 ttyS0
> 
> well. When I look into virtext configuration then I see
> 
> SERIAL_CONSOLE ?= "115200 ttyUL0"
> 
> I wonder if you have tried that configuration for serial console.
> 
> 

I'm working with my local repo so, I have made the changes locally to ttyS0. As 
soon as I get something working, I send it to Adrian to commit to the repo.

The problem I have with ttyS0 also happens with ttyUL0. I've tried with both.

Elvis
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to