2008-04-24 11:54:24     USB Console - unable to open an initial console

2008-04-24 11:54:24     USB Console - unable to open an initial console

Richard Aldrich (UNITED KINGDOM)

Message: 54876    I am using a USB to Serial adapter and trying to get the console to work over USB.

I've set console=ttyUSB0 in the boot args. It writes some of the output out to the usb, but when it's get to the point where it would normally say "Welcome to uClinux" (etc) it prints out "Warning: unable to open an initial console". It then won't take any input from the USB console.

I know the driver is working correctly - when I boot normally to the serial console (ttyBF0) i can ECHO commands to ttyUSB0 and they come through correctly with another console window attached to the USB-Serial adapter. I can also CAT ttyUSB0 and read back from the other USB Console.

Any ideas?

QuoteReplyEditDelete

2008-04-24 13:26:06     Re: USB Console - unable to open an initial console

Robin Getz (UNITED STATES)

Message: 54878    Richard:

Just so I understand - your USB/serial device is plugging USB into the Blackfin? or is plugging USB into your host PC, and serial into the Blackfin?

-Robin

QuoteReplyEditDelete

2008-04-24 15:43:38     Re: USB Console - unable to open an initial console

Mike Frysinger (UNITED STATES)

Message: 54891    if you read the kernel to see where that warning is coming from (init/main.c), you'll see that your root filesystem needs to have /dev/console.  if it doesnt, then the kernel will be unable to automatically open it for you and it's up to your userspace to recover.

QuoteReplyEditDelete

2008-04-28 07:31:17     Re: USB Console - unable to open an initial console

Richard Aldrich (UNITED KINGDOM)

Message: 55120    Yes, I have the USB/Serial converter on the Blackfin side, it uses the PL2303 driver.

When I boot with console=ttyBF0, the /dev/console is created correctly. However, if I use /dev/ttyUSB0 it does not create the /dev/console device. Why is this, and how can I change it so it does?

QuoteReplyEditDelete

2008-04-28 08:12:48     Re: USB Console - unable to open an initial console

Robin Getz (UNITED STATES)

Message: 55123    Richard:

Can you post the full boot message from the kernel?

I just want to make sure that the USB driver is being loaded properly during boot.

-Robin

QuoteReplyEditDelete

2008-04-28 08:34:18     Re: USB Console - unable to open an initial console

Richard Aldrich (UNITED KINGDOM)

Message: 55126    Linux version 2.6.19.3-ADI-2007R1.1-svn (root@linux-8q19) (gcc version 4.1.1 (A8

Warning: limiting memory to 19MB due to hardware anomaly 05000263

Blackfin support (C) 2004-2007 Analog Devices, Inc.

Compiled for ADSP-BF537 Rev 0.2

Blackfin Linux support by http://blackfin.uclinux.org/

Processor Speed: 500 MHz core clock and 100 Mhz System Clock

Board Memory: 32MB

Kernel Managed Memory: 32MB

Memory map:

  text      = 0x00001000-0x00167964

  init      = 0x00168000-0x00178838

  data      = 0x0017a9bc-0x001bdb80

  stack     = 0x0017c000-0x0017e000

  bss       = 0x001bdb80-0x001cce80

  available = 0x001cce80-0x01300000

  rootfs    = 0x01300000-0x01f00000

  DMA Zone  = 0x01f00000-0x02000000

Instruction Cache Enabled

Data Cache Enabled (write-through)

Hardware Trace Enabled

Built 1 zonelists.  Total pages: 4826

Kernel command line: root=/dev/mtdblock0 rw console=ttyUSB0 ip=192.168.0.2:192.f

Configuring Blackfin Priority Driven Interrupts

PID hash table entries: 128 (ousbcore: registered new interface driver pl2303

drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver

rtc-bfin rtc-bfin: rtc intf: sysfs

rtc-bfin rtc-bfin: rtc intf: proc

rtc-bfin rtc-bfin: rtc intf: dev (254:0)

rtc-bfin rtc-bfin: IP-Config: Complete:

      device=eth0, addr=192.168.0.2, mask=255.255.255.0, gw=192.168.0.1,

     host=BF537, domain=, nis-domain=(none),

     bootserver=192.168.0.28, rootserver=192.168.0.28, rootpath=

VFS: Mounted root (ext2 filesystem).

Freeing unused kernel memory: 64k freed (0x168000 - 0x177000)

Warning: unable to open an initial console.

ISA-BlackFin-CAN CAN Driver 3.4_AD_BLACKFIN (c) Apr 21 2008

H.J. Oertel (oe@port.de)

QuoteReplyEditDelete

2008-04-28 10:50:25     Re: USB Console - unable to open an initial console

Robin Getz (UNITED STATES)

Message: 55141    Richard:

Is that the entire bootmsg? I need to see it all.

Where is the portion that is the USB chip getting initialized?

-Robin

QuoteReplyEditDelete

2008-04-28 11:05:03     Re: USB Console - unable to open an initial console

Mike Frysinger (UNITED STATES)

Message: 55147    the /dev/console device node always exist irregardless of the console= specified

QuoteReplyEditDelete

2008-04-28 11:25:17     Re: USB Console - unable to open an initial console

Richard Aldrich (UNITED KINGDOM)

Message: 55153    Thats all that is shown when I boot with the console=ttyUSB0. The following is when I boot with ttyBF0 console..

## Starting application at 0x00001000 ...

Linux version 2.6.19.3-ADI-2007R1.1-svn (root@linux-8q19) (gcc version 4.1.1 (A8

Warning: limiting memory to 19MB due to hardware anomaly 05000263

Blackfin support (C) 2004-2007 Analog Devices, Inc.

Compiled for ADSP-BF537 Rev 0.2

Blackfin Linux support by http://blackfin.uclinux.org/

Processor Speed: 500 MHz core clock and 100 Mhz System Clock

Board Memory: 32MB

Kernel Managed Memory: 32MB

Memory map:

  text      = 0x00001000-0x00167964

  init      = 0x00168000-0x00178838

  data      = 0x0017a9bc-0x001bdb80

  stack     = 0x0017c000-0x0017e000

  bss       = 0x001bdb80-0x001cce80

  available = 0x001cce80-0x01300000

  rootfs    = 0x01300000-0x01f00000

  DMA Zone  = 0x01f00000-0x02000000

Instruction Cache Enabled

Data Cache Enabled (write-through)

Hardware Trace Enabled

Built 1 zonelists.  Total pages: 4826

Kernel command line: root=/dev/mtdblock0 rw console=ttyBF0,57600 ip=192.168.0.2f

Configuring Blackfin Priority Driven Interrupts

PID hash table entries: 128 (order: 7, 512 bytes)

Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)

Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)

Physical pages: 1300

Memory available: 17316k/31253k RAM, (66k init code, 1434k kernel code, 60k dat)

Blackfin Scratchpad data SRAM: 4 KB

Blackfin DATA_A SRAM: 16 KB

Blackfin DATA_B SRAM: 16 KB

Blackfin Instruction SRAM: 48 KB

Security Framework v1.0.0 initialized

Capability LSM initialized

Mount-cache hash table entries: 512

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

stamp_init(): registering device resources

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

NET: Registered protocol family 2

IP route cache hash table entries: 256 (order: -2, 1024 bytes)

TCP established hash table entries: 1024 (order: 0, 4096 bytes)

TCP bind hash table entries: 512 (order: -1, 2048 bytes)

TCP: Hash tables configured (established 1024 bind 512)

TCP reno registered

JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

pfx: pfbits driver for bf5xx

Dynamic Power Management Controller Driver v0.1: major=10, minor = 254

Blackfin Watchdog Timer: 0.01 initialized. wd_action_code=0 cnt_sec=20 sec (now)

Serial: Blackfin serial driver

bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART

bfin-uart.1: ttyBF1 at MMIO 0xffc02000 (irq = 20) is a BFIN-UART

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

PPP generic driver version 2.4.2

Blackfin mac net device registered

uclinux[mtd]: RAM probe address=0x1300000 size=0xc00000

Creating 1 MTD partitions on "RAM":

0x00000000-0x00c00000 : "ROMfs"

uclinux[mtd]: set ROMfs:EXT2  to be root filesystem

m25p80 spi1.1: m25p64 (8192 Kbytes)

Creating 3 MTD partitions on "m25p80":

0x00000000-0x00020000 : "bootloader"

0x00100000-0x00500000 : "file system"

0x00400000-0x00700000 : "kernel"

usbmon: debugfs is not available

driver isp1362-hcd, 2005-04-04

isp1362-hcd isp1362-hcd.0: ISP1362 Host Controller

isp1362-hcd isp1362-hcd.0: new USB bus registered, assigned bus number 1

isp1362_hc_reset:

isp1362-hcd isp1362-hcd.0: irq 54, io mem 0x20360000

isp1362_hc_start:

isp1362-hcd isp1362-hcd.0: ISP1362 Memory usage:

isp1362-hcd isp1362-hcd.0:   ISTL:    2 *  256:      512 @ $0000:$0100

isp1362-hcd isp1362-hcd.0:   INTL:   16 * ( 64+8):  1152 @ $0200

isp1362-hcd isp1362-hcd.0:   ATL :   32 * ( 64+8):  2304 @ $0680

isp1362-hcd isp1362-hcd.0:   USED/FREE:   3968       128

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 2 ports detected

ISP1362 Host Controller, irq 54

Initializing USB Mass Storage driver...

usb 1-2: new full speed USB device using isp1362-hcd and address 2

usb 1-2: configuration #1 chosen from 1 choice

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usbcore: registered new interface driver usbserial

drivers/usb/serial/usb-serial.c: USB Serial Driver core

drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303

pl2303 1-2:1.0: pl2303 converter detected

usb 1-2: pl2303 converter now attached to ttyUSB0

usbcore: registered new interface driver pl2303

drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver

rtc-bfin rtc-bfin: rtc intf: sysfs

rtc-bfin rtc-bfin: rtc intf: proc

rtc-bfin rtc-bfin: rtc intf: dev (254:0)

rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting the system clock to 1970-01-01 04:28:00 (16080)

IP-Config: Complete:

      device=eth0, addr=192.168.0.2, mask=255.255.255.0, gw=192.168.0.1,

     host=BF537, domain=, nis-domain=(none),

     bootserver=192.168.0.28, rootserver=192.168.0.28, rootpath=

VFS: Mounted root (ext2 filesystem).

Freeing unused kernel memory: 64k freed (0x168000 - 0x177000)

Welcome to:

       ____ _  _

      /  __| ||_|             _  _

_   _| |  | | _ ____  _   _ \ \/ /

| | | | |  | || |  _ \| | | | \  /

| |_| | |__| || | | | | |_| | /  \

|  ___\____|_||_|_| |_|\____|/_/\_\

|_|

For further information see:

http://www.uclinux.org/

http://blackfin.uclinux.org/

ISA-BlackFin-CAN CAN Driver 3.4_AD_BLACKFIN (c) Apr 21 2008

H.J. Oertel (oe@port.de)

BusyBox v1.4.1 (2008-04-21 14:43:33 BST) Built-in shell (msh)

Enter 'help' for a list of built-in commands.

root:~>

QuoteReplyEditDelete

2008-04-29 09:01:01     Re: USB Console - unable to open an initial console

Richard Aldrich (UNITED KINGDOM)

Message: 55222    You say it always exists, but it is definitely different when I specify console=ttyUSB0 to when it's console=ttyBF0.

The simple test i'm using is: echo "help me!" > /dev/console

If it fails to open the device with that then it can't be initialised correctly somewhere.

QuoteReplyEditDelete

2008-04-30 16:58:44     Re: USB Console - unable to open an initial console

Mike Frysinger (UNITED STATES)

Message: 55318    how are you testing it if you dont have a serial console ?

i imagine the USB serial console may be more finicky during boot because it requires so much more beneath it (USB subsystem fully initialized) before things will start coming out ... i think i have a pl2303 laying around that i can test with

it would probably be useful to test the USB console on your desktop system ...

QuoteReplyEditDelete

2008-05-01 07:05:48     Re: USB Console - unable to open an initial console

Richard Aldrich (UNITED KINGDOM)

Message: 55339   

>> "how are you testing it if you dont have a serial console ?"

I am able to test it through Telnet over ethernet.