[#7305] bfin-jtag.exe and bfin-gdbproxy.exe do not work on Windows

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

[#7305] bfin-jtag.exe and bfin-gdbproxy.exe do not work on Windows

Submitted By: Andrew McLachlan

Open Date

2012-09-03 03:39:40     Close Date

2012-09-28 12:25:54

Priority:

High     Assignee:

Jie Zhang

Board:

N/A     Silicon Revision:

Resolution:

Rejected     Fixed In Release:

N/A

Processor:

ALL     

Host Operating System:

Windows

toolchain rev.:

    kernel rev.:

State:

Closed     Found In Release:

2012R1

Is this bug repeatable?:

N/A     

Summary: bfin-jtag.exe and bfin-gdbproxy.exe do not work on Windows

Details:

 

Trying to connect to ADSP-BF609 rev 1.2 with ICE-100B

(firmware version is 2.0.7)

 

http://docs.blackfin.uclinux.org/doku.php?id=hw:jtag:ice100b says

that the firmware must be >= 1.0.7

 

-- GNU tools running under Cygwin on Windows 7 64bit --

 

$ bfin-jtag.exe

cable probe

Found USB cable: ICE-100B

 

(no more output)

 

$ bfin-gdbproxy.exe

 

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: ICE-100B

error:     bfin: cable initialization failed

 

 

-- Ubuntu running through Virtualbox --

 

$ sudo ./bfin-gdbproxy

 

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: ICE-100B

ICE-100B firmware version is 2.0.7

IR length: 5

Chain length: 1

Device Id: 00000010100000000100000011001011 (0x028040CB)

  Manufacturer: Analog Devices, Inc. (0x0CB)

  Part(0):      SDU (0x2804)

  Stepping:     0

  Filename:     ./../share/urjtag/analog/sdu/sdu

warning:   bfin: no board selected, 3 parts are detected

warning:   bfin:   parts: [BF609 BF609] SDU

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

 

$ sudo ./bfin-gdbproxy

 

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: ICE-100B

ICE-100B firmware version is 2.0.7

IR length: 5

Chain length: 1

Device Id: 00000010100000000100000011001011 (0x028040CB)

  Manufacturer: Analog Devices, Inc. (0x0CB)

  Part(0):      SDU (0x2804)

  Stepping:     0

  Filename:     ./../share/urjtag/analog/sdu/sdu

warning:   bfin: no board selected, 3 parts are detected

warning:   bfin:   parts: [BF609 BF609] SDU

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

 

Follow-ups

 

--- Andrew McLachlan                                         2012-09-03 04:44:28

 

running under CMD (run As Administrator), I get similar results to Cygwin:

 

bfin-jtag:

jtag> cable probe

Found USB cable: ICE-100B

error: libusb error: libusb_open() failed: -12

 

bfin-gdbproxy:

 

Found USB cable: ICE-100B

error:     bfin: cable initialization failed

 

--- Mike Frysinger                                           2012-09-05 15:11:37

this is expected behavior documented in the wiki:

http://docs.blackfin.uclinux.org/doku.php?id=hw:jtag:ice100b#use_different_usb_pids_for_visualdsp_and_urjtag_gdbproxy

 

--- Andrew McLachlan                                         2012-09-06 08:12:22

 

I now understand the set-up. Sadly, this means that it isn't very straight-

forward to debug a CCES project and then swap to debugging a GNU project

without messing with drivers and jumpers.

 

--- Jie Zhang                                                2012-09-06 11:04:50

Not a bug.

 

--- Mike Frysinger                                           2012-09-06 13:26:14

yes, as long as the VDSP windows drivers use their own usb stack (rather than

the usermode usb driver), there's not much the open source side can do.  once

(if?) they convert to the usermode usb driver, then things will "just

work" with urjtag.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes