BDI 3000 with BEAGLE

[Sairam S]

Hi ,

 

We are trying to use the BDI3000 to  debug software on  Beagle board . But we are not able to debug the board .

We have used b30allgd.108 firmware file and Omap35xx.cfg and Reg3500.def files for configuration of BDI .

 

But the error we are getting is

 -TARGET:BDI executes scan chain init string  -TARGET:Bypasscheck

0x0000001->0xffffffff  -TARGET:JTAG exists check failed #

-TARGET:resetting target failed # JTAG:Communication with target failed .

 

We have also modified the cable connecting from BDI (TARGET A ) to Beagle board , w.r.t to the connections of TI and BDI documentation .Thew configuration used is atatched here .

It worked for  a while when we changed the WAKEUP delay to 8000, but could not get connected every time we power on .

The connection details are as follows .

 

BDI         BEAGLE      JTAG SIGNALS

9           5           VCC

7           2           TRST

8           3           TDI

6           1           TMS

4           11          TCK

10          7           TDO

3,5         4,8         GND

 

Kindly let us know where we are going wrong .

 

 

Thanks & regards ,

Sairam.S

[Gerald Coley]

As I don't have the BDI product, I won't be able to help you. Maybe someone in the community has experience with this device. I would think your best bet is to contact BDI for OMAP34xx or OMAP35xx support.

 

Gerald

 

; with the BDI needs to be modified.
;
; To halt the core as soon as possible after power-up,
; select EMU1=1,EMU0=0 (Wait In Reset mode WIR).
;
; Commands supported in the SCANINIT and SCANPOST strings:
;
;  I<n>=<...b2b1b0>   write IR, b0 is first scanned
;  D<n>=<...b2b1b0>   write DR, b0 is first scanned
;                       n  : the number of bits 1..256
;                       bx : a data byte, two hex digits
;  W<n>               wait for n (decimal) micro seconds
;  T1                 assert TRST
;  T0                 release TRST
;  R1                 assert RESET
;  R0                 release RESET
;  CH<n>              clock TCK n (decimal) times with TMS high
;  CL<n>              clock TCK n (decimal) times with TMS low
;
;
[INIT]
;WGPR    11          0x40200020  ;set frame pointer to free RAM
;WM32    0x40200020  0x40200028 ;dummy stack frame
;

[TARGET]
CPUTYPE     OMAP3500
CLOCK       2                   ;JTAG clock
POWERUP     2000                ;power-up delay
TRST        PUSHPULL            ;TRST driver type (OPENDRAIN | PUSHPULL)
RESET       NONE                ;Reset signal is not routed to the debug connector
STARTUP     HALT
;STARTUP     STOP  10000         ;let boot code setup the system
ENDIAN      LITTLE              ;memory model (LITTLE | BIG)
WAKEUP      2000
MEMACCESS   CORE  10            ;memory access via core (80 TCK's access delay)
;MEMACCESS   AHB   8             ;memory access via AHB  (64 TCK's access delay)
;DCC         7                   ;DCC I/O via TCP port 7

SCANPRED    1 6                 ;count for ICEPick TAP
SCANSUCC    0 0                 ;no device after Cortex-A8

; Configure ICEPick module to make Cortex-A8 DAP-TAP visible
SCANINIT    t1:w1000:t0:w1000:  ;toggle TRST,
SCANINIT    ch10:w1000:         ;clock TCK with TMS high and wait
SCANINIT    i6=07:d8=89:i6=02:  ;connect and select router
SCANINIT    d32=81000080:       ;IP control: KeepPowered
SCANINIT    d32=a3002048:       ;TAP3: DebugConnect, ForcePower, ForceActive
SCANINIT    d32=81000081:       ;IP control: KeepPowered, SysReset
SCANINIT    d32=a3002148:       ;enable TAP3
SCANINIT    cl10:i10=ffff       ;clock 10 times in RTI, scan bypass
;


[HOST]
IP          151.120.25.112
FILE        E:/temp/dump1024k.bin
FORMAT      BIN 0x80000000
PROMPT      OMAP35xx>

[FLASH]
; only to test helper code execution
WORKSPACE   0x80001000          ;workspace at 0x1000
CHIPTYPE    AM29BX16
CHIPSIZE    0x400000
BUSWIDTH    16
FILE        E:/temp/dump1024k.bin
FORMAT      BIN 0x80300000

[REGS]
FILE    $regOMAP3500.def

[deepak khungar]

Hi,

I am facing the same issue with MIPS64. Did you happen find the way to resolve this issue, if yes please share the way?

[deepak khungar]

Hi Sairam,

I am facing this same issue with MIPS64. Did you happen get way to resolve the issue, if yes please share the way?

On Friday, September 26, 2008 at 10:55:01 PM UTC+5:30, Sairam S wrote: