What to do if network processes do not function on Abatron BDI2000?
If network processes aren't functioning after a successful firmware load for your Abatron Computer Accessories, ensure the BDI2000 is properly connected to the network via LAN cable or media converter. Also, verify that the IP address entered in the BDI2000 configuration is correct.
What to do if Abatron Computer Accessories are not working with the target system?
If you're unable to work with the target system after successfully loading the firmware on your Abatron Computer Accessories, consider these potential causes: * Check the pin assignment (BDM/JTAG connector) of the target system. * Ensure correct target system initialization by entering an appropriate target initialization list. * Verify that the IP address entered is correct (BDI2000 configuration). * Inspect the BDM/JTAG signals from the target system for any short-circuits or breaks. * Consider the possibility of damage to the target system.
General| Supported Protocols | JTAG, SWD |
|---|---|
| Target Interface | JTAG, SWD |
| Interface | Ethernet |
| Operating System Compatibility | Windows, Linux |
| Host Interface | Ethernet, USB |
| Supported Architectures/Devices | ARM, MIPS, PowerPC, ColdFire, XScale |
| Connection | Ethernet, USB |
| Debugging Features | Breakpoints, Memory access, Register access |
| Operating System Support | Windows, Linux |
Overview of the BDI2000, its function as the main part of the bdiGDB system, and its firmware/logic update capabilities.
Details on initial setup, IP address, host IP, and configuration file storage within BDI2000 flash memory.
Instructions for connecting the BDI2000 to the target system using a 16-pin ribbon cable, including pin assignments and cable length limits.
Guidance on connecting the BDI2000 to a 5V power supply, specifying voltage limits and connection sequences for reliable operation.
Explanation of the built-in LED states (OFF, ON, BLINK) and their corresponding BDI status indicators.
Details on establishing host connection via serial line (RS232) for initial configuration and Ethernet communication.
Steps for configuring the bdiGDB system, including software/firmware loading and initial parameter transmission via diskette or BOOTP.
Procedure for configuring the BDI2000 on Linux/Unix systems, involving building a setup tool, checking serial connection, and loading firmware.
Steps to configure the BDI2000 on Windows using the Update/Setup dialog box, including firmware/logic updates and parameter settings.
Procedure to recover the BDI2000 if firmware loading fails, involving jumper settings and power cycling.
Method to test the communication between the host and BDI2000 using Telnet after initial setup.
Description of the provided TFTP server (tftpsrv.exe) for Windows, used for configuration file access and program loading.
Explanation of how the BDI firmware handles GDB requests, accesses target memory/registers via JTAG, and the power-up sequence.
Details on the syntax and structure of the configuration file, including comments, part names, and identifier/parameter entries.
Defines commands executed upon target reset to prepare it for program loading, including register writes and delays.
Specifies target-specific values like CPUTYPE, JTAGCLOCK, BDIMODE, STARTUP mode, and BOOTADDR for debugging.
Defines host-specific values such as IP address, default filename, image format, load mode, and start address.
Covers flash programming and erasing, defining chip type, size, bus width, filename, format, and erase commands.
Explains how to define registers in a definition file for easier access via Telnet, including register types and SWAP options.
Details on debugging with GDB, including target setup, connecting to the remote target, and handling application suspension.
Describes breakpoint modes (SOFT/HARD) and how GDB versions handle breakpoints, including hardware breakpoint setup.
Explains the use of the GDB 'monitor' command to execute Telnet commands and switch BDI breakpoint modes from GDB.
How to connect target serial I/O to BDI's RS232 port for access via TCP/IP, enabling Telnet sessions for UART output.
Details on supporting Linux kernel debugging with MMU enabled, including PTBASE configuration for page table translation.
Overview of the integrated Telnet server for error messages, information, and basic debug commands like memory modification and register display.
Guidance on concurrent debugging of MPC8641D dual-core processors, including configuration and startup modes for each core.
Common problems encountered during firmware loading, target system operation, and network connectivity, with possible reasons and solutions.
Instructions for cleaning the housing, replacing the fuse, and reassembling the unit, including ESD precautions.
Statement that all trademarks are the property of their respective holders.
To Next Page
