[#6286] characters is not shown correctly in u-boot jtag console test

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

[#6286] characters is not shown correctly in u-boot jtag console test

Submitted By: Vivi Li

Open Date

2010-10-09 07:08:46     Close Date

2010-10-15 03:56:14

Priority:

Medium     Assignee:

Mike Frysinger

Vivi Li

Category:

N/A     Fixed In Release:

N/A

Found In Release:

N/A     Status:

Closed

Board:

N/A     Processor:

BF537

Silicon Revision:

    Resolution:

Assigned (Not Start)

Is the bug repeatable?:

N/A     

Summary: characters is not shown correctly in u-boot jtag console test

Details:

 

In u-boot jtag console test, run command "echo test", it shows "echo test\n\rtest\n\rbfin>".

For jtag test in kernel, run the same command, it shows "echo test\r\ntest\r\nbfin>". Usually I get "\r\n" at the end of a line in log file, not "\n\r".

 

--

uboot34-bf537stamp:/home/test/work/cruise/checkouts/u-boot/u-boot_test_script #  bfin-gdbproxy bfin

 

Remote proxy for GDB, v0.7.2, Copyright (C) 1999 Quality Quorum Inc.

MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood

Blackfin adaption Copyright (C) 2008 Analog Devices, Inc.

 

GDBproxy comes with ABSOLUTELY NO WARRANTY; for details

use `--warranty' option. This is Open Source software. You are

welcome to redistribute it under certain conditions. Use the

'--copying' option for details.

 

Found USB cable: gnICE

Connected to libftdi driver.

IR length: 5

Chain length: 1

Device Id: 00100010011111001000000011001011 (0x227C80CB)

  Manufacturer: Analog Devices, Inc. (0x0CB)

  Part(0):      BF537 (0x27C8)

  Stepping:     2

  Filename:     /opt/uClinux/bfin-uclinux/bin/../share/urjtag/analog/bf537/bf537

warning:   bfin: no board selected, BF537 is detected

notice:    bfin: jc: waiting on TCP port 2001

notice:    bfin: jc:  (you must connect GDB before using jtag console)

notice:    bfin-gdbproxy: waiting on TCP port 2000

 

*****************************

STEP 6: gdb_spawn_id: run bfin-uclinux-gdb

 

test@uboot34-bf537stamp:~/work/cruise/checkouts/u-boot/u-boot_test_script> expor t PATH=/opt/uClinux/bfin-uclinux/bin:/opt/uClinux/bfin-elf/bin:/opt/uClinux/bfin -linux-uclibc/bin:$PATH

test@uboot34-bf537stamp:~/work/cruise/checkouts/u-boot/u-boot_test_script> bfin- uclinux-gdb

GNU gdb 6.6

Copyright (C) 2006 Free Software Foundation, Inc.

GDB is free software, covered by the GNU General Public License, and you are

welcome to change it and/or distribute copies of it under certain conditions.

Type "show copying" to see the conditions.

There is absolutely no warranty for GDB.  Type "show warranty" for details.

This GDB was configured as "--host=i686-pc-linux-gnu --target=bfin-uclinux".

(gdb) target remote :2000

Remote debugging using :2000

0x03f80b0e in ?? ()

(gdb)

*****************************

STEP 7: netcat_spawn_id: run netcat as jtag console window

 

test@uboot34-bf537stamp:~/work/cruise/checkouts/u-boot/u-boot_test_script> /home /test/work/cruise/checkouts/u-boot//tools/jtagconsole

NOTE: the interrupt signal (normally ^C) has been remapped to ^T

 

*****************************

STEP 8: gdb_spawn_id: Continue to run uboot

 

 

(gdb) c

Continuing.

 

*****************************

STEP 9: kermit_spawn_id: set env for jtag console

 

 

bfin> set stdout jtag; set stderr jtag; set stdin jtag

 

*****************************

STEP 10: netcat_spawn_id: testing jtag console

 

bfin>

bfin> echo test

test

bfin> FAIL:testing jtag console!

--

 

Follow-ups

 

--- Sonic Zhang                                              2010-10-12 06:13:13

I think both "\n\r" and "\r\n" are valid next line mark in

console. Vivi is better to change the test script to accept both.

 

--- Vivi Li                                                  2010-10-15 03:56:14

OK, test script is updated in branch 2010r1 and trunk.

Close now.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes