2010-06-16 15:37:01 Trying to make JTAG console work
Peter Naulls (UNITED STATES)
Message: 90342
c.f:
docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:jtagconsole
I'm trying to make the JTAG console work with BF548-EZKIT. I have seen several bug reports with details similar to below, but no conclusion. I have both the gnICE and gnICE+ adapters. With gnICE+ I get:
sudo bfin-gdbproxy -q bfin
Connected to libftdi driver.
device not found: Inappropriate ioctl for device
Error: Cable initialization failed!
error: bfin: cable initialization failed
With gnICE, more luck:
Connected to libftdi driver.
IR length: 5
Chain length: 1
Device Id: 00100010011111011110000011001011 (0x00000000227DE0CB)
Manufacturer: Analog Devices
Part(0): BF548
Stepping: 2
Filename: /home/peter/projects/fish/SDK/scripts/../toolchain/bfin-uclinux/bin/../share/urjtag/analog/bf548/bf548
warning: bfin: no board selected, BF548 is detected
notice: bfin: jc: waiting on TCP port 2001
notice: bfin-gdbproxy: waiting on TCP port 2000
And then the jtag settings typed into u-boot from serial console.
Telnet/nc to port 2001 connects, but there's no output to anything typed.
I have tried with 2009 toolchain and also with a more recent trunk toolchain. I also upgraded u-boot to 2010.03 from 2009.11.1
What am I missing?
Cheers.
QuoteReplyEditDelete
2010-06-16 16:04:09 Re: Trying to make JTAG console work
Mike Frysinger (UNITED STATES)
Message: 90343
if you want to use a non-default cable, you have to specify it yourself with --connect. this is in the blackfin-specific help output.
you really should use the helper tools to connect to the jtag console instead of typing your own commands:
docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:jtagconsole
you dont have to set both stdin and stdout with u-boot to the console. so to make debugging easier, it is often easier to set just the stdout to jtag while keeping stdin with the serial port.