2011-07-11 10:39:36     gdbproxy and gdb

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

2011-07-11 10:39:36     gdbproxy and gdb

Adam Whiting (UNITED KINGDOM)

Message: 102320   

 

I'm having trouble trying to connect to a custom board using a BF524 processor. firstly i try to run gdbproxy

 

Z:\>bfin-gdbproxy --debug bfin --reset

 

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 ()

Found USB cable: gnICE+

Connected to libftdi driver.

IR length: 5

Chain length: 5

Device Id: 00110010011111001000000011001011 (0x327C80CB)

Manufacturer: Analog Devices, Inc. (0x0CB)

Part(0): BF537 (0x27C8)

Stepping: 3

Filename: c:\program files\analog devices\gnu toolchain\2010r1\elf\bin\../

share/urjtag/analog/bf537/bf537

Device Id: 11111111111111111111111111111111 (0xFFFFFFFF)

Unknown manufacturer! (11111111111) (c:\program files\analog devices\gnu toolc

hain\2010r1\elf\bin\../share/urjtag/MANUFACTURERS)

Device Id: 11111111111111111111111111111111 (0xFFFFFFFF)

Unknown manufacturer! (11111111111) (c:\program files\analog devices\gnu toolc

hain\2010r1\elf\bin\../share/urjtag/MANUFACTURERS)

Device Id: 11111111111111111111111111111111 (0xFFFFFFFF)

Unknown manufacturer! (11111111111) (c:\program files\analog devices\gnu toolc

hain\2010r1\elf\bin\../share/urjtag/MANUFACTURERS)

Device Id: 11111111111111111111111111111111 (0xFFFFFFFF)

Unknown manufacturer! (11111111111) (c:\program files\analog devices\gnu toolc

hain\2010r1\elf\bin\../share/urjtag/MANUFACTURERS)

warning: bfin: no board selected, 5 cores are detected

warning: bfin: cores: [BF537]

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

 

 

notice: bfin-gdbproxy: connected

debug: bfin: bfin_connect ()

debug: bfin: emulation_enable ()

debug: [0] DBGSTAT [0x0000]: cause:emuexcpt <before>

debug: [0] DBGSTAT [0x0000]: cause:emuexcpt <after>

debug: [0] DBGCTL [0x00a3]: emudatsz_40 emuirsz_32 emfen empwr <emulation_en

able>

debug: bfin: emulation_trigger ()

debug: [0] DBGSTAT [0x0000]: cause:emuexcpt <before>

debug: [0] DBGSTAT [0x0000]: cause:emuexcpt <after>

debug: Reset EMUPC

debug: [0] EMUPC [0x00000000] <before>

debug: [0] EMUPC [0x00000000] <after>

info: [0] emulator not ready: DBGSTAT [0x0000]

info: Resetting ...

debug: Reset core(s)

Assertion failed: in_reset, file /usr/src/packages/BUILD/blackfin-toolchain-2010

R1/urjtag/src/bfin/bfin.c, line 611

 

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.

 

 

 

 

when i try to connect to the target using

 

target remote :2000 i get the above and gdbproxy disconnects.

 

I have a seperate development board which has a BF526 on it and that works fine. Does anyone have any ideas.

 

This is all run under window XP toolchain 2010R1

QuoteReplyEditDelete

 

 

2011-07-11 10:54:31     Re: gdbproxy and gdb

Jie Zhang (UNITED STATES)

Message: 102321   

 

The other four unknown parts are expected? Do they conform to the JTAG standard?

QuoteReplyEditDelete

 

 

2011-07-11 11:02:38     Re: gdbproxy and gdb

Adam Whiting (UNITED KINGDOM)

Message: 102322   

 

thats also another issue that i reports back 5 items in the jtag chain but there is only one DSP connected.

 

Sometimes it does only report one device in the chain but this still doesn't stop it from not connecting to the debugger.

QuoteReplyEditDelete

 

 

2011-07-11 11:09:27     Re: gdbproxy and gdb

Jie Zhang (UNITED STATES)

Message: 102323   

 

Is the DSP in the JTAG scan chain?

 

Try a lower frequency to see if it helps, for example "--frequency=1000000".

QuoteReplyEditDelete

 

 

2011-07-11 11:20:08     Re: gdbproxy and gdb

Adam Whiting (UNITED KINGDOM)

Message: 102324   

 

I tried some frequencies and anything less than 10MHz "--frequency=1000000" it comes up with

 

detecting parts failed

 

Couldn't connect to suitable USB device.

 

However a 10MHz it still doesn't work properly. I did do a bit of reading is posibly something to do with how the DSP is configured to boot up?

QuoteReplyEditDelete

 

 

2011-07-11 11:34:22     Re: gdbproxy and gdb

Jie Zhang (UNITED STATES)

Message: 102325   

 

Try "--frequency=1000000 --wait-clocks=0"

QuoteReplyEditDelete

 

 

2011-07-12 02:49:11     Re: gdbproxy and gdb

Adam Whiting (UNITED KINGDOM)

Message: 102334   

 

I tried this and it still comes up with

 

detecting parts failed

 

Couldn't connect to suitable USB device.

 

However i tried the same thing on my other development board which uses a BF526 and that worked fine.

QuoteReplyEditDelete

 

 

2011-07-12 02:52:16     Re: gdbproxy and gdb

Adam Whiting (UNITED KINGDOM)

Message: 102335   

 

It looks as though it's something to do with when the processor is reset when gdb tries to connect it.

QuoteReplyEditDelete

 

 

2011-07-12 08:56:43     Re: gdbproxy and gdb

Jie Zhang (UNITED STATES)

Message: 102363   

 

From your first post, I also saw that the blackfin processor was detected wrong:

 

Device Id: 00110010011111001000000011001011 (0x327C80CB)

Manufacturer: Analog Devices, Inc. (0x0CB)

Part(0): BF537 (0x27C8)

Stepping: 3

 

I don't know what's the next step to try. Maybe you should ask people who designed the hardware board.

QuoteReplyEditDelete

 

 

2011-07-12 09:00:07     Re: gdbproxy and gdb

Adam Whiting (UNITED KINGDOM)

Message: 102364   

 

It all seems to be fixed now. I rewired the programming hardware and it works fine now. I think it may of been the cable length between the gnIce and the DSP.

QuoteReplyEditDelete

Attachments

    Outcomes