USI Home | Downloads | Config-Files | Reg Def Files | Tech-Support | ToolFinder | eStore
 
SPRT Home
FAQ
Submit a question
Favorites
Categories
BDI Commands (01-03) (3)
BDI Setup (02-10) (9)
BDM-JTAG Communication (01-02) (2)
Cables & AC Power Supply (4)
Config & Regdef Files (01-06) (6)
Connecting to Target (01-06) (6)
CPU Specific (28)
Flash Memory Programming (01-08) (8)
GCC-GDB (01-04) (4)
Host & Network Communication (01) (1)
Linux Kernel Debugging (01-04) (4)
Linux Module Debugging (01) (1)
LinuxScope (01-03) (3)
Miscellaneous (01-06) (6)
TFTP Server (01-02) (2)
U-Boot (0)
Search Articles
Advanced Search
Frequently Asked Questions
Search our FAQ to find resolutions to common issues.
Main Page
P207 - JTAG Exits Check Failed, JTAG Bypass Check Failed

If you get a JTAG Exits check failed message after a JTAG Bypass check message then it means the JTAG Chain is disabled for some reason. The BDI tries to read the bypass register but can't. The message will appear in this sequence In the BDI Telnet prompt.

> - CONFIG: loading configuration file passed
> - TARGET: processing reset request
> - TARGET: BDI asserts TRST and RESET
> - TARGET: BDI removes TRST
> - TARGET: Bypass check 0x000000001 => 0x00FFFFFF
> - TARGET: JTAG exits check failed

There are several reasons this may be occurring. When you get a message saying Bypass check 0x000000001 => 0xFFFFFFFF, it means that the JTAG is disabled and the BDI cannot find any device on the JTAG chain. A message showing => 0x00000001 or any other number shows the number of devices that were discovered on the JTAG chain.

1) Start out by making sure the correct CPUTYPE is selected in the config file, the location of the bypass register can change with different processors and the BDI might be looking at the wrong location if an incorrect processor type is defined.

2) If the reset from the JTAG connector is delayed for some reason (it might not be directly connected to the processor) then add a wake-up delay to reset line, e.g. "WAKEUP 10000". This does not work if your processor has a watchdog timer (MPC82xx in particular), because the watch dog will trigger before the wakeup time is over. Possibly try and use a smaller wakeup delay.

3) For COP Targets you can try and add a Powerup delay in the target section. "POWERUP 10000". Use this without the WAKEUP delay to see if the exits check passes.

4) If the processor is not the only device on the JTAG Scan chain then you have to tell the BDI2000 the IR values of all the Devices on the Scan chain. USE SCANPRED and SCANSUCC to specify the correct values, see the user manual for more details.

5) Check the JTAG circuit to make sure it is wired correctly on the board. Reference the manual at page 5 and make sure the JTAG connector is wired correctly. Use an oscilloscope to test the logic levels of the signals if need be.

6) A message saying => 0xFFFFFFFF means that the JTAG chain is disabled on your board. Make sure that the JTAG chain is enabled on your board. If there is a mux or jumper on the JTAG chain make sure it is at the correct setting.

7) Please check the power supply to the processor, make sure the power supply is clean and at the recommended level.

8) JTAG is very sensitive to noise and adding resistors sometimes creates slow rising signals that don't meet their time window. For the most part pull-ups of >= 1K are ok with signal lines. The values below should be ok to use with the indicated signals.

Signal Name Resistor Pullup/Pulldown Resistor Value TDI,TDO,TMS, TCK pullup >=2K RESET and TRST pullup 1K-3K TRST pulldown(ARM only) 1K-10K VCC <= 1k

Signal Name Resistor Pullup/pulldown Resistor Value
TDI, TDO, TMS, TCK pullup >=2K
RESET and TRST pullup 1K-3K
TRST pulldown
(ARM only)
1K-10K
VCC <= 1K

Article ID: 10083 Article Created: 05-13-2008 16:03 PM

Print  Email  Save  Notify Me  Add to Favorites 

How well did this article answer your question? 100% 75% 50% 25% 0%

Most Recently Viewed Articles
P310 - When I try and connect GDB to the BDI, I get the error message saying "remote packet too long"
If you try and use the default GDB on your host system to connect to the BDI you will get this error. This is because GDB on your Linux or Cygwin system is trying to read x86 registers from the target, your target is not X86....
03 - On the BDI startup, I keep getting the message "waiting for target stop failed" or “check stopped state failed” and "Break at Boot Vector Failed, Freeze Forced"
During startup the BDI sets a hardware breakpoint at the Boot Vector. If you have a boot monitor on your board try and use STARTUP RUN in your config file and the BDI will not try and set a breakpoint and will bring up your boot monitor. ...
C303 - GDB does not find the source files after I load the symbol file
There are several reasons you could be experiencing this behavior from GDB....
02 - Where can I get config files for the BDI Probe?
The BDI Probe gets shipped with a few config files that were used during the firmware development of the BDI and are located in the firmware directory. ...
01 - When I debug a Linux application should I turn off the MMU?
The BDI Probe cannot be used to debug Linux applications running in user-space....
X407 - Can I use your USB to RS232 cable assembly to access the BDI Telnet Interface?
With bdiGDB (and bdiWind) you can only use Ethernet to access the Telnet interface (command interface)....
P402 - Having problems bringing up my bootmonitor with the BDI2000 attached. Program counter is at an exception vector 0x00000800. TQM8260
Try and change STARTUP mode to RUN to try and bring up the boot monitor by default. An issue has been identified with certain TQM8260 boards (TQM8260-AG) where the HRCW is not set correctly, which causes the bootmonitor to hose while the BDI is connected....
P202 - Error: JTAG instruction stuff overrun
When in debug mode the PPC4xx fetches normal PPC instructions from the JTAG port. The error "# PPC: JTAG instruction stuff overrun" is raised when the processor stops fetching from the JTAG port, possibly because the processor hangs at an un-terminated memory transfer. ...
013 - PC Stepping Backwards
On our PowerPC processor the PC seems to start stepping backwards either during debugging or at system startup?...
008 - How do I Configure the BDI Probe to target a PowerPC in little endian mode?
How do I Configure the BDI Probe to target a PowerPC in little endian mode?...
Powered by Omnistar Kbase