2010-11-19 05:54:37     jtag connection to bf537-stamp

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

2010-11-19 05:54:37     jtag connection to bf537-stamp

Henning Hörentrup (GERMANY)

Message: 96001   

 

Hello ,

 

I’m trying to get my jtag-connection to work properly in order to port the working u-boot to our custom hardware, which will be based on bf537. I read thru the “how-to’s” on http://docs.blackfin.uclinux.org , especially the pages regarding flashing via jtag ( http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:loading ) and jtagconsole ( http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:jtagconsole ) , because our custom board will just have a jtag- and an Ethernet-interface.

 

Unfortunately, I ran into some problems:

 

1)       I followed the instructions described here: http://docs.blackfin.uclinux.org/doku.php?id=toolchain:debug:gdbproxy

 

    But I’m only getting the libftdi support with no async mode ( see attachment jtag configure), which is maybe the cause for my second problem.

 

2)       If I connect my host to my target via jtag command, detection of the target hardware doesn’t succeed regularly (see attachment jtag detect)

 

3)       If I’m trying to start jtagconsole I get the error message: line38: nc: command not found.

 

 

 

And finally my questions:

 

1)       What do I have to do, to activate the async mode correctly? And is it even important?

 

2)       Why does the detection of the bf537-stamp-board doesn’t work properly? Maybe because of problem one?

 

3)       I think, the nc command redefines stdin, stdout and stderr, am I right? At least this it does when I changed the stdin, stdout and stderr from serial to Ethernet. Were do I have to define it?

 

 

 

On the positive side, gdbproxy and bfin-uclinux-gdb are working just fine, I think. But the goal is to flash the uboot via jtag and to monitor the early booting process of uboot via jtagconsole.

 

Hopefully you can help me solving my problems or can provide some hints. It’s the first time I’m doing stuff like that.

 

Henning

 

jtag detect.txt

jtag configure.txt

QuoteReplyEditDelete

 

 

2010-11-19 06:08:35     Re: jtag connection to bf537-stamp

Mike Frysinger (UNITED STATES)

Message: 96005   

 

building jtag stuff from scratch doesnt really make sense anymore.  use the precompiled binaries that come with 2009R1.1 and newer releases.

QuoteReplyEditDelete

 

 

2010-11-25 04:09:34     Re: jtag connection to bf537-stamp

Henning Hörentrup (GERMANY)

Message: 96210   

 

Allright, using the precompiled binaries was the solution to get a stable connection via bfin-jtag and I succeeded in flashing a bootable image. Thanks for that, Mike.

 

Right now I'm trying to connect my gnICE+ via bfin-gdbproxy, but it doesn't work:

 

# bfin-gdbproxy --debug 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.

 

debug: bfin: bfin_open ()

Connected to libftdi driver.

device not found: No such file or directory

Error: Cable initialization failed!

error: bfin: cable initialization failed

 

 

 

If I'm using gdbproxy the initialization works:

 

#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: gnICE+

Connected to libftdi driver.

IR length: 5

Chain length: 1

Device Id: 00110010011111001000000011001011 (0x327C80CB)

  Manufacturer: Analog Devices, Inc. (0x0CB)

  Part(0):      BF537 (0x27C8)

  Stepping:     3

  Filename:     /usr/local/share/urjtag/analog/bf537/bf537

Error: Unable to detect JTAG chain end!

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:    gdbproxy: waiting on TCP port 2002

 

 

 

I think something is wrong with my files or path, because of the red marked part device not found: No such file or directory.  But I don't know how to fix it. Not really an uboot question, more a noob question, but I hope you can help me.

QuoteReplyEditDelete

 

 

2010-11-25 05:20:27     Re: jtag connection to bf537-stamp

Aaron Wu (CHINA)

Message: 96212   

 

Could you start a new thread since it's another topic?  BTW it's working on my side, my tool chain version is 2010R1 RC4

Attachments

Outcomes