[#3949] cat through ttyBF0 would have one more empty line for each line

Document created by Aaronwu Employee on Aug 28, 2013
Version 1Show Document
  • View in full screen mode

[#3949] cat through ttyBF0 would have one more empty line for each line

Submitted By: Mingquan Pan

Open Date

2008-03-03 00:17:03     Close Date

2008-05-26 06:57:28

Priority:

Low     Assignee:

Sonic Zhang

Status:

Closed     Fixed In Release:

N/A

Found In Release:

N/A     Release:

Category:

N/A     Board:

N/A

Processor:

N/A     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

N/A

Uboot version or rev.:

    Toolchain version or rev.:

08r1-8

App binary format:

N/A     

Summary: cat through ttyBF0 would have one more empty line for each line

Details:

 

cat through ttyBF0 on bf561-ezkit would have one more empty line for each line.

 

On host,do:

 

cat /dev/ttyS0 > aaa

 

telnet to target board:

 

cat /etc/boa.conf > /dev/ttyBF0

 

Aftering finishing, ctl+c on host ,see aaa like:

 

# Boa v0.94 configuration file

 

# File format has changed little from 0.92

 

# version changes are noted in the comments

 

#

 

# The Boa configuration file is parsed with a lex/yacc or flex/bison

 

# generated parser.  If it reports an error, the line number will be

 

# provided; it should be easy to spot.  The syntax of each of these

 

# rules is very simple, and they can occur in any order.  Where possible

 

# these directives mimic those of NCSA httpd 1.3; I saw no reason to

 

# introduce gratuitous differences.

 

 

# The "ServerRoot" is not in this configuration file.  It can be compiled

 

# into the server (see defines.h) or specified on the command line with

 

# the -c option, for example:

 

#

 

# boa -c /usr

 

 

the original one is:

 

# Boa v0.94 configuration file

# File format has changed little from 0.92

# version changes are noted in the comments

#

# The Boa configuration file is parsed with a lex/yacc or flex/bison

# generated parser.  If it reports an error, the line number will be

# provided; it should be easy to spot.  The syntax of each of these

# rules is very simple, and they can occur in any order.  Where possible

# these directives mimic those of NCSA httpd 1.3; I saw no reason to

# introduce gratuitous differences.

 

# The "ServerRoot" is not in this configuration file.  It can be compiled

# into the server (see defines.h) or specified on the command line with

# the -c option, for example:

#

# boa -c /usr

 

 

 

 

Follow-ups

 

--- Mingquan Pan                                             2008-04-09 22:58:26

These days frequently see this bug also happens on bf537 stamp and bf533

stamp,which makes the serial test case fail on trunk.

 

 

bfin> bootelf

Loading .text @ 0x00001000 (1047280 bytes)

Loading .exit.text.refok @ 0x00100af0 (296 bytes)

Loading .rodata @ 0x00100c20 (249652 bytes)

Loading __ksymtab @ 0x0013db54 (14880 bytes)

Loading __ksymtab_gpl @ 0x00141574 (4168 bytes)

Loading __ksymtab_strings @ 0x001425bc (45828 bytes)

Loading __param @ 0x0014d8c0 (300 bytes)

Clearing .bss @ 0x0014da00 (55556 bytes)

Loading .data @ 0x0015b304 (77052 bytes)

Loading .init.text @ 0x0016e000 (97964 bytes)

Loading .init.data @ 0x00185eac (13176 bytes)

Loading .init.setup @ 0x00189224 (612 bytes)

Loading .initcall.init @ 0x00189488 (448 bytes)

Loading .con_initcall.init @ 0x00189648 (4 bytes)

Loading .init.ramfs @ 0x0018964c (3585515 bytes)

Loading .text_l1 @ 0xffa00000 (6984 bytes)

sh_addr: FFA00000, p_paddr: 004F4C37

Loading from: 024E8000 to 004F4C37, size: 6984

Loading .data_l1 @ 0xff800000 (192 bytes)

sh_addr: FF800000, p_paddr: 004F677F

Loading from: 024EA000 to 004F677F, size: 192

## Starting application at 0x0016e000 ...

Linux version 2.6.24.4-ADI-2008R2-pre-svn4569 (test@uclinux50-cf-cdrom) (gcc

version 4.1.2 (ADI svn)) #5 Wed Apr 9 19:01:09 CST 2008

console [early_BFuart0] enabled

early printk enabled on early_BFuart0

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

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  fixedcode = 0x00000400-0x00000490

  text      = 0x00001000-0x00100af0

  rodata    = 0x00100c20-0x0014d9ec

  bss       = 0x0014da00-0x0015b304

  data      = 0x0015b304-0x0016e000

    stack   = 0x0016c000-0x0016e000

  init      = 0x0016e000-0x004f7000

  available = 0x004f7000-0x037ff000

  DMA Zone  = 0x03f00000-0x04000000

Hardware Trace Active and Enabled

Reset caused by Software reset

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

Compiled for ADSP-BF537 Rev 0.2

Blackfin Linux support by   blackfin.uclinux.org/

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

NOMPU: setting up cplb tables for global access

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 14224

Kernel command line: root=/dev/mtdblock0 rw earlyprintk=serial,uart0,57600

console=/dev/null ip=10.100.4.50

Configuring Blackfin Priority Driven Interrupts

PID hash table entries: 256 (order: 8, 1024 bytes)

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

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

Memory available: 51676k/65536k RAM, (3620k init code, 1022k kernel code, 438k

data, 1024k dma, 7756k reserved)

Blackfin Scratchpad data SRAM: 4 KB

Blackfin Data A SRAM: 16 KB (15 KB free)

Blackfin Data B SRAM: 16 KB (16 KB free)

Blackfin Instruction SRAM: 48 KB (41 KB free)

Security Framework initialized

Mount-cache hash table entries: 512

net_namespace: 64 bytes

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

stamp_init(): registering device resources

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 2048 (order: 2, 16384 bytes)

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

TCP: Hash tables configured (established 2048 bind 2048)

TCP reno registered

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

Serial: Blackfin serial driver

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

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

bfin_mac_mdio: probed

bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1,

mdc_clk=2500000Hz(mdc_div=19)@sclk=100MHz)

bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Controller Driver, Version 1.0,

regs_base@ffc00500, dma channel@7

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

bfin-wdt: initialized: timeout=20 sec (nowayout=0)

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

turn off boot console early_BFuart0

 

(Back at uclinux50-cf-cdrom.analog.com)

----------------------------------------------------

(/home/test/work/cruise/checkouts/uclinux-dist/testsuites/serial/)

C-Kermit>q

Closing /dev/ttyS0...OK

sh-3.00$ telnet 10.100.4.50

Trying 10.100.4.50...

Connected to 10.100.4.50.

Escape character is '^]'.

 

 

BusyBox v1.10.0 (2008-04-09 17:52:13 CST) built-in shell (msh)

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

 

root:/> stty -F /dev/ttyBF0 ispeed 57600 ospeed 57600

root:/> cat /dev/ttyBF0

sh-3.00$  echo abcdefghijklmnopqrstuvwxyz0123456789 > /dev/ttyS0

sh-3.00$

abcdefghijklmnopqrstuvwxyz0123456789

 

Case 8 ...PASS

 

Case 8 ...PASS

 

root:/> Echoed char get on host .stty -F /dev/ttyBF0 ispeed 57600 ospeed

57600

root:/> ls

build_serial_kernel.exp  build_serial_uart1_kernel.exp  serial_test.exp

serial_uart1_test.exp

build_serial_kernel_log  build_sport_uart_kernel.exp    serial_test_log

sport_uart_test.exp

sh-3.00$ cat /dev/ttyS0 > aaa

cat /etc/boa.conf > /dev/ttyBF0

root:/>

sh-3.00$ cat aaa

# Boa v0.94 configuration file

 

# File format has changed little from 0.92

 

# version changes are noted in the comments

 

#

 

# The Boa configuration file is parsed with a lex/yacc or flex/bison

 

# generated parser.  If it reports an error, the line number will be

 

# provided; it should be easy to spot.  The syntax of each of these

 

# rules is very simple, and they can occur in any order.  Where possible

 

# these directives mimic those of NCSA httpd 1.3; I saw no reason to

 

# introduce gratuitous differences.

 

 

...

 

#Auth /etc /etc/passwd

 

dos2unix aaa

sh-3.00$ dos2unix aaa

dos2unix: converting file aaa to UNIX format ...

sh-3.00$ rcp root@10.100.4.50:/etc/boa.conf .

sh-3.00$ diff -u aaa boa.conf

--- aaa 2008-04-09 19:05:23.000000000 +0800

+++ boa.conf    2008-04-09 19:05:27.000000000 +0800

@@ -1,354 +1,177 @@

# Boa v0.94 configuration file

-

# File format has changed little from 0.92

-

# version changes are noted in the comments

-

#

-

# The Boa configuration file is parsed with a lex/yacc or flex/bison

-

# generated parser.  If it reports an error, the line number will be

-

# provided; it should be easy to spot.  The syntax of each of these

-

# rules is very simple, and they can occur in any order.  Where possible

-

# these directives mimic those of NCSA httpd 1.3; I saw no reason to

-

# introduce gratuitous differences.

 

Case 9 ...FAIL

 

--- Sonic Zhang                                              2008-05-26 05:09:13

Looks like a tty configuration issue. Please run stty -F /dev/ttyS0 on your host

and set proper control flags before start testing.

 

--- Mingquan Pan                                             2008-05-26 06:57:28

Yes,use stty -F /dev/ttyS0 -icrnl can eliminate this issue.Close.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes