A101 - Image not being programmed or loaded at the correct memory address.
  Before going any further please check if the flash/memory location is working properly. Perform a few writes and reads from the memory location, use MMH for 16bit, MMB for 8 bit, and MMD for 64 bit flash. MM 0xff000000 0x12345678MD 0xff000000

A201 - Why is the ICEBreaker access check failing from the reset command?
    1.) Please Check the JTAGSEL line on the ARM chip and make sure that it is pulled high rather than low. 2.) The default JTAGCLOCK speed has been changed with newer firmware to 16Mhz. If this is too high for your ARM chip then try to change the JTAGCLOCK back to 8Mhz.  

A301 - How do I configure the BDI2000 to catch all exception vectors on an ARM964E cpu?
When using the bdiGDBfirmware, add/modify the lines in the config file[TARGET]..STARTUP..... RESET VECTOR .......CATCH..... 0xff The problem is that with STARTUP RUN, the ARM964E vector catch register is not set via the BDI. Use STARTUP RESET then enter "go" at the telnet prompt.

A401 - I can't connect to the BDI, it keeps saying "cannot connect to BDI loader"
The BDI setup utility has been run on countless Windows and Linux systems and has been known to work. There are no known issues with the setup utility that may cause the connection to be refused. If you are having problems connecting you should check and see if your environment is setup correctly.

A402 - The BDI mode LED keeps blinking or stays on, what does it mean?
When the BDI mode (Red) led is blinking once a second it means that you have no firmware loaded on your BDI2000. If it blinks at a faster rate of about 3 times a second, it means the init Jumper (see manual page 16) is in the init position and is set to clear the firmware logic in the BDI. A solid mode led indicates that the power supply is malfunctioning; it is not at the right power level.

C101 - Can the BDI program NAND flash?
The BDI can only be used to program NOR flash.

C201 - I am having trouble connecting to my MCF 5272 target board. I keep getting BDM communication failed messages or the target is constantly in reset.
The BDI has trouble working with the MCF5272 chip. The problem arises from the fact that the BDI needs to synchronize with PSTCLK that runs at 66Mhz, the same speed as the ARM core in the BDI.

C301 - 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.

C401 - How do I make a config File?
Generating a proper config file is the most difficult part of starting out with the BDI. The config file is used to initialize your board up to the point where SDRAM and FLASH are usable.

L101 - Can the BDI program NAND flash?
The BDI can only be used to program NOR flash.

L201 - How do I setup a tftp server on RedHat Linux 8/9?
To setup a tftp server first make sure you have the tftp Server package installed.

L307 - When I debug a Linux application should I turn off the MMU?
The BDI2000 cannot be used to debug Linux application running in user-space.

L401 - How do I setup a tftp server on RedHat Linux 8/9?
To setup a tftp server first make sure you have the tftp Server package installed. Finding the proper package from installation menus of most Linux distributions can be tricky.

P101 - Flash Programming Failed
After programming the first 512 bytes into flash the BDI2000 gives an error and stops programming. Same thing happens when we run a verify. When we read back the flash it appears to be programmed correctly.

P201 - Our 7xx, 74xx processor has entered “check stop state”, what does this mean?
If for some reason memory access fails on the 7xx, 74xx during startup, the processor enters check stop state and all the clocks are stopped.

P301 - How do I Configure the BDI2000 to target a PowerPC in little endian mode?
The BDI2000 does not support little endian mode in PowerPC's at all at this point. Currently there are not any plans to add it.

P401 - How do I make a config File?
Generating a proper config file is the most difficult part of starting out with the BDI2000. The config file is used to initialize your board up to the point where SDRAM and FLASH are usable.

X101 - How to program an Intel Strata Flash using an Intel ipxd2800 in big endian mode?
Instead of using STRATA8 or 16 as the programming algorithm in the BDI2000 config file, use I28BX8 or 16. This will allow you to program flash in big endian mode now.

X201 - 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.

X401 - I can't connect to the BDI, it keeps saying "cannot connect to BDI loader"
The BDI setup utility has been run on countless windows and Linux systems and has been known to work. There are no known issues with the setup utility that may cause the connection to be refused.

A102 - I keep getting the message "Flash Programming Failed" in the BDI2000. How do I setup my Flash Programming?
There are several reasons that flash programming could be failing. The most common one is that the config file is not setup correctly for flash programming.

A202 - 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.

A302 - Is ARM SEMI-HOSTING fully supported by the BDI2000?
BDIGDB uses the standard GDB remote protocol. There is no semi-hosting possible with it. BDIRDI Supports Semihosting.

A403 - How do I make a config File?
Generating a proper config file is the most difficult part of starting out with the BDI2000. The config file is used to initialize your board up to the point where SDRAM and FLASH are usable. After this you can put an initial boot agent onto the board or replace the existing boot agent

C302 - Why does the Program counter seem to jump around in my code? It does not follow the code execution
This is not uncommon and is due to instruction reorganization and rescheduling.

C402 - I can't connect to the BDI, it keeps saying "cannot connect to BDI loader"
 The BDI setup utility has been run on countless Windows and Linux systems and has been known to work. There are no known issues with the setup utility that may cause the connection to be refused.

L301 - Warning: unknown architecture file may be incompatible with i386 target
I am trying to get the BDI2000 up and running. The basic configuration appears to be fine. I can telnet and also connect via GDB. These are the steps I used:detachtarget remote bdi:2001file armbootThen I get the warning message above.

L402 - I can't connect to the BDI, it keeps saying "cannot connect to BDI loader"
The BDI setup utility has been run on countless Windows and Linux systems and has been known to work. There are no known issues with the setup utility that may cause the connection to be refused. If you are having problems connecting you should check and see if your environment is setup correctly.

P102 - Can I load the ppcboot to the flash on the Sandpoint board (Motorola) and use the flash map in the sp8240.cfg?
Only after you have modified it for use with the Sandpoint. Remember, the SP8240.cfg is only a generic example file for a generic 8240 target.

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.

P302 - Having problems booting Linux or application with BDI attached on MPC8xx. Getting a kernel panic with BDI attached.
The debug registers cannot be written by software when the BDI2000 is hooked up. Take a look at the MPC8xx manual and you will see that the debug registers, like ICTRL, cannot be written when a hardware debugger is attached.

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.

X102 - Image not being programmed or loaded at the correct memory address. Doing a load or prog into memory results in the image being put at the wrong memory location
Before going any further please check if the flash/memory location is working properly. Perform a few writes and reads from the memory location, use MMH for 16bit, MMB for 8 bit and MMD for 64 bit flash. MM 0xff000000 0x12345678MD 0xff000000

X202 - Why does our Target board keep resetting? It says "Target reset detected, restarting target"
There are several reasons that the target can get stuck into constant resetting pattern.

X301 - Having problems booting Linux with BDI attached on Xscale
Having problems booting Linux with BDI attached on Xscale. BDI telnet prompt shows it entered debug mode, doing "info" at the prompt reveals: Core number : 0 Core state : debug mode (ARM) Debug entry cause : Vector Trap (PREFETCH ABORT)Current PC : 0xffff0840 Current CPSR : 0x600000d2 (IRQ)

A103 - Can the BDI program NAND flash?
    The BDI can only be used to program NOR flash.

A203 - Why does our Target board keep resetting? It says "Target reset detected, restarting target"
There are several reasons that the target can get stuck into constant resetting pattern.

A303 - Why are we getting “writing to workspace failed” at the BDI2000 prompt when we have disabled the workspace by writing 0xffffffff to it?
Disable the vector catch and this error message will go away.

A404 - Cannot open file on host
You will get this error when the BDI tries to access a file on the TFTP server and the file either does not exist or it cannot communicate with the TFTP server.

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.

C403 - The BDI mode LED keeps blinking or stays on, what does it mean?
When the BDI mode (Red) led is blinking once a second it means that you have no firmware loaded on your BDI2000. If it blinks at a faster rate of about 3 times a second, it means the init Jumper (see manual page 16) is in the init position and is set to clear the firmware logic in the BDI. A solid mode led indicates that the power supply is malfunctioning; it is not at the right power level.

L302 - How can I use the BDI2000 and GDB to debug other applications other than the Linux kernel?
The BDI2000 cannot be used to debug Linux applications. It is designed so that it can access kernel space memory but has no information about user space memory.

L403 - The BDI mode LED keeps blinking or stays on, what does it mean?
When the BDI mode (Red) led is blinking once a second it means that you have no firmware loaded on your BDI2000.

P103 - My Flash configuration has the bits reversed; can I still program flash using the BDI2000 and the bdiGDB firmware?
Flash memory is usually connected so that the MSB of the processor is connected to the MSB of the FLASH.

P203 - The BDI is displaying the wrong PVR value for my board
It should be 0x80811014: > - JTAG exits check passed > - Target PVR is 0x80911014 > - COP status is 0x01

P303 - When I am debugging my 405GPR kernel I get a kernel panic.
This is a known issue for the PPC405GPR.

P403 - I get this target server error when I try and connect to the BDI2000 using a PPC405 - "Cannot determine target architecture for CPU 112"
Unfortunately,WindRiver has changed the CPU type for 405 from 112 to 2001.

X103 - I keep getting the message "Flash Programming Failed" in the BDI2000. How do I setup my Flash Programming?
There are several reasons that flash programming could be failing. The most common one is that the config file is not setup correctly for flash programming.

X203 - I get the following output from the BDI Telnet prompt while starting up my Target
I get the following output from the BDI Telnet prompt while starting up my Target  

X302 - Why can't I hit breakpoints in my Kernel, Uboot or program?
Breakpoints are not immediately set when you put a "bi" command in the BDI or a "break" in GDB. They are set as soon as you hit "go" and are cleared as soon as you stop.

A304 - Why can't I hit breakpoints in my Kernel, Uboot or program?
Breakpoints are not immediately set when you put a "bi" command in the BDI or a "break" in GDB. They are set as soon as you hit "go" and are cleared as soon as you stop. This way they do not influence debugging. You will never see the breakpoints in the DBCR0 or DBCR1 registers. For debugging Linux kernels, set the initial breakpoint after Uboot has booted up and before the kernel is loaded. This way Uboot will not clear the kernel breakpoint during its startup.

A405 - I cannot ping the BDI on our network. It seems like it is dead.
First of all please check the BDI error codes to see if your BDI is working properly, (see related article below - A402).

C304 - GDB will not single step
When I connect GDB to the BDI everything seems fine but the PC does not seem to single step, I get an error from GDB. Everything else like registers, memory, breakpoints and continue seem to be working. Doing an “n” from gdb results in a memory access error.

C404 - Cannot open file on host
You will get this error when the BDI tries to access a file on the TFTP server and the file either does not exist or it cannot communicate with the TFTP server.

L303 - What is the meaning of defining target/workspace?
If a workspace is defined, the BDI uses a faster download mode.

L404 - How do I make a config File?
Generating a proper config file is the most difficult part of starting out with the BDI2000. The config file is used to initialize your board up to the point where SDRAM and FLASH are usable.

P104 - I keep getting the message "Flash Programming Failed" in the BDI2000. How do I setup my Flash Programming?
There are several reasons that flash programming could be failing. The most common one is that the config file is not setup correctly for flash programming.

P204 - On startup we get this error message saying "Target not supported" or "PVR not supported". Known TQM8260 issue.
Please contact your Ultimate Solutions FAE to confirm that the processor is supported by the current firmware you are using.

P304 - Why can't I hit breakpoints in my Kernel, Uboot or program?
Breakpoints are not immediately set when you put a "bi" command in the BDI or a "break" in GDB. They are set as soon as you hit "go" and are cleared as soon as you stop. This way they do not influence debugging.

P404 - I can't connect to the BDI, it keeps saying "cannot connect to BDI loader"
The BDI setup utility has been run on countless windows and Linux systems and has been known to work. There are no known issues with the setup utility that may cause the connection to be refused. If you are having problems connecting you should check and see if your environment is setup correctly.

X104 - Can the BDI program NAND flash?
The BDI can only be used to program NOR flash.

X204 - BDI says "Communication with Debug Handler Failed"
Normally this error occurs during target startup. First of all make sure that the Debug Handler is located in the Mini IC. Be sure to add the line DBGHANDLER into the [TARGET] section of the config file and point it to the Mini IC. Pointing it to an invalid location will result is this error.

X303 - How can I use the BDI2000 and GDB to debug other applications other than the Linux kernel?
The BDI2000 cannot be used to debug Linux applications; it is designed so that it can access kernel space memory but has no information about user space memory.

A305 - How can I use the BDI2000 and GDB to debug other applications other than the Linux kernel?
The BDI2000 cannot be used to debug Linux applications. It is designed so that it can access kernel space memory but has no information about user space memory.

A406 - Where can I get config files for the BDI2000?
The BDI2000 gets shipped with a few config files that were used during the firmware development of the BDI and are located in the firmware directory.

C405 - I cannot ping the BDI on our network. It seems like it is dead
First of all please check the BDI error codes to see if your BDI is working properly, (see related article below, A402).

L304 - If I define the WORKSPACE in TARGET of the config file I cannot load file to the memory
If I do not define the WORKSPACE in TARGET of the config file I can load the file to memory, but there is a repeat of every 4th word.

L405 - Cannot open file on host
You will get this error when the BDI tries to access a file on the TFTP server and the file either does not exist or it cannot communicate with the TFTP server.

P105 - How can I use the Physical Address of my flash memory to program it?
Remove the MMU XLAT option from the config file. With that off you should be able to program flash using the physical address.

P205 - Our MPC83xx seems to start up correctly but doing an info shows that the debug entry is cause is unknown and the Program counter location seems to be junk. Accessing IMMBAR or memory results in a SAP error. The BDI will not single step.
Target CPU : MPC83xx (ledZeppo)Target state : debug modeDebug entry cause : <reserved 0>Current PC : 0xfffffffcCurrent CR : 0xf8000fffCurrent MSR : 0xf8000fffCurrent LR : 0xf8000fff This normally implies that something has gone wrong in the processor startup.

P305 - I keep getting the error message in GDB saying Program Received SIGSTOP
If the program being debugged has stopped responding then GDB comes back and displays this message. It is not uncommon to receive this message in GDB while debugging a Linux kernel and normally points to a problem in your Page Table entries

P405 - The BDI mode LED keeps blinking or stays on, what does it mean?
When the BDI mode (Red) led is blinking once a second it means that you have no firmware loaded on your BDI2000.

X205 - During debugging the BDI displays a message saying “step time out detected”. I cannot single step anymore.
The reason for this is that at some point during your board bring up the Debug Handler gets over written by your code.

X304 - 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.

A306 - 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.

A407 - 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).

C406 - Where can I get config files for the BDI2000?
The BDI2000 gets shipped with a few config files that were used during the firmware development of the BDI and are located in the firmware directory.

L305 - ***CONFIG: cannot open sp8240.cfg
Once I installed the BDI firmware and Telnet to the BDI2000, I always receive the above message.

L406 - I cannot ping the BDI on our network. It seems like it is dead
First of all please check the BDI error codes to see if your BDI is working properly, (see related article below, A402).

P106 - Image not being programmed or loaded at the correct memory address. Doing a load or prog into memory results in the image being put at the wrong memory location.
Before going any further please check if the flash/memory location is working properly. Perform a few writes and reads from the memory location, use MMH for 16bit MMB for 8 bit and MMD for 64 bit flash.

P206 - PPC Core timeout waiting for freeze
If you are using a PPC82xx processor and are getting this error during the BDI startup sequence then possibly TRST and HRESET are wired together in some manner causing some unknown behavior resulting in a timeout. Please check the JTAG circuitry and make sure TRST and HRESET are not tied together.

P306 - How can I use the BDI2000 and GDB to debug other applications other than the Linux kernel?
The BDI2000 cannot be used to debug Linux applications. It is designed so that it can access kernel space memory but has no information about user space memory.

P406 - Download speeds for my PPC platform seem slow - what can I do to fix this?
I assume we talk about downloading via TFTP and not about the GDB "load" command. I suspect that you have enabled the PPC caches. The download speed decreases dramatically because the BDI has to do cache coherent writes.

X206 - Why does my IXP465 Intel development board keep resetting itself?
Users of the IXP456 board may get the following repeating output from the BDI:

X305 - Why does the Program counter seem to jump around in my code? It does not follow the code execution
This is not uncommon and is due to instruction reorganization and rescheduling.

A307 - Why does the Program counter seem to jump around in my code? It does not follow the code execution
This is not uncommon and is due to instruction reorganization and rescheduling. To stop the compiler from rescheduling instructions please add the following compiler flags to the CFLAGS line in your make file:-fno-schedule-insns -fno-schedule-insns2

A408 - Can I write scripts to perform BDI operations?
The easiest way to script with the BDI is to write GDB Scripts. All BDI telnet commands are available thru GDB via the “mon” keyword.

C407 - 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).

L407 - Where can I get config files for the BDI2000?
The BDI2000 gets shipped with a few config files that were used during the firmware development of the BDI and are located in the firmware directory.

P107 - Can I program my flash with bdiPro when I have the flash bus bits reversed?
bdiPro does not support non-standard flash memory configurations. bdiPro can only program flash chips tied to the PPC bus MSB to MSB.

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.

P307 - The kernel/application stops booting and the BDI says the target has stopped. Doing "info", I get the message in the BDI saying "debug entry cause : system call or that the system has encountered and exception.
The debug registers cannot be written by software when the BDI2000 is hooked up. Take a look at the MPC8xx manual and you will see that the debug registers, like DER, cannot be written through software when a hardware debugger is attached.

P407 - How do I set the HRCW on my MPC82xx?
To set the HRCW pull up the RSTCONF pin on the MPC82xx from its default low.

X306 - 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.

A308 - 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.

A409 - I want to move the BDI to and from a secure lab, but need to know the internal memory configuration of the BDI to make sure that indicviduals are not able to take data in and out of the lab using the BDI.
The BDI has 512 KB unbuffered SRAM and 1MB Flash. The flash and the RAM used for the processor running in the BDI2000 are not isolated.

C408 - Can I write scripts to perform BDI operations?
The easiest way to script with the BDI is to write GDB Scripts. All BDI telnet commands are available thru GDB via the “mon” keyword.

L306 - The {HOST} info in the config file does not match my host computer, the telnet of BDI2000 does not give any warning
The file supplied with the BDI2000 is an example. You must change it so it makes sense and works in your environment. This statement applies not only to the HOST section, but to the target initialization as well.

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

P108 - Can the BDI program NAND flash?
The BDI can only be used to program NOR flash.

P208 - Why does our Target board keep resetting? It says "Target reset detected, restarting target"
There are several reasons that the target can get stuck into constant resetting pattern.

P308 - When using MPC85xx, how do I set up the Linux kernel so that I can hit breakpoints with the BDI2000?
Start out by reading related article below, P304, as that is a good guide to hitting breakpoints.

P408 - Cannot open file on host
You will get this error when the BDI tries to access a file on the TFTP server and the file either does not exist or it cannot communicate with the TFTP server.

X307 - GDB will not single step
When I connect GDB to the BDI everything seems fine but the PC does not seem to single step, I get an error from GDB.  Everything else like registers, memory, breakpoints and continue seem to be working. Doing an “n” from gdb results in a memory access error.

A309 - GDB will not single step
When I connect GDB to the BDI everything seems fine but the PC does not seem to single step, I get an error from GDB. Everything else like registers, memory, breakpoints and continue seem to be working. Doing an “n” from gdb results in a memory access error.

C409 - I want to move the BDI to and from a secure lab, but need to know the internal memory configuration of the BDI to make sure that indicviduals are not able to take data in and out of the lab using the BDI
The BDI has 512 KB unbuffered SRAM and 1MB Flash. The flash and the RAM used for the processor running in the BDI2000 are not isolated.

A410 - Trying to connect my BDI probe to a board by Logic Product Development. Is there a library of config files for this board?
I am trying to connect my BDI probe to a board designed and manufactured by Logic Product Development and I can't find a .cfg file that will allow me to connect to my target board.  Where can I get access to a library of these files?

L409 - Can I write scripts to perform BDI operations?
The easiest way to script with the BDI is to write GDB Scripts. All BDI telnet commands are available thru GDB via the “mon” keyword.

P209 - BDI prompts gives this error message during startup: "Check LSRL length failed", eventually saying that the target is not supported.
Please contact Ultimate Solutions and confirm that the processor is supported.

P309 - When I try and single step using the BDI2000's "ti" command the PC increments once then stops incrementing and the processor is hosed.
This points to the TLB's not being setup incorrectly. In the 440 CPU's a valid TLB entry needs to exist before memory can be accessed. Make sure the TLB entry for the boot space is correct in your BDI config file.

P409 - I cannot ping the BDI on our network. It seems like it is dead
First of all please check the BDI error codes to see if your BDI is working properly, (see related article below, A402).

X308 - During debugging the BDI displays a message saying “step time out detected”. I cannot single step anymore.
The reason for this is that at some point during your board bring up the Debug Handler gets over written by your code.

L410 - I want to move the BDI to and from a secure lab, but need to know the internal memory configuration of the BDI to make sure that indicviduals are not able to take data in and out of the lab using the BDI
The BDI has 512 KB unbuffered SRAM and 1MB Flash. The flash and the RAM used for the processor running in the BDI2000 are not isolated.

P210 - 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.

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.

P410 - Where can I get config files for the BDI2000?
The BDI2000 gets shipped with a few config files that were used during the firmware development of the BDI and are located in the firmware directory.

X402 - The BDI mode LED keeps blinking or stays on, what does it mean?
When the BDI mode (Red) led is blinking once a second it means that you have no firmware loaded on your BDI2000.

C410 - Trying to connect my BDI probe to a board by Logic Product Development. Is there a library of config files for this board?
 I am trying to connect my BDI probe to a board designed and manufactured by Logic Product Development and I can't find a .cfg file that will allow me to connect to my target board.  Where can I get access to a library of these files?

L307 - When I debug a Linux application should I turn off the MMU?
The BDI2000 cannot be used to debug Linux aplications running in user-space.

L308 - How do I convert an ELF file to an S-Record or Intel Hex file that I can load into FLASH memory via bdiPRO?
Most development tools provide a method to convert an elf file to an Intel Hex file including users of GNU/GDB and Cygwin by using objcopy.exe.

P211 - Why is my MPC8xx not entering debug mode? BDI says "Target does not enter debug mode". It also says "resetting target failed" depending on it I use STARTUP mode RUN or HALT.
Here is the BDI's startup sequence: - The BDI asserts HRESET (DSCK high to force debug mode) - MPC8xx asserts HRESET and SRESET - The BDI releases HRESET - BDI waits until HRESET and SRESET are inactive - Then it waits for debug mode entry.

P311 - GDB cannot communicate with target System
I am trying to use GDB to debug our PPC85xx system, my connection errors out when I try and connect GDB to the BDI. When I do connect to the BDI the PC is at an incorrect location and single stepping does not work?

P411 - 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).

X403 - How do I make a config File?
Generating a proper config file is the most difficult part of starting out with the BDI2000. The config file is used to initialize your board up to the point where SDRAM and FLASH are usable.

L309 - I received my Abatron bdiGDB firmware for a Linux host and the software is based on a Windows host. How do I run on Linux?
When running on a Windows host, the setup utility "B20XXXGD.exe" is provided to configure the BDI2000. If you are using a Linux host, you must "build" the setup utility from the provided source files "bdisetup.zip".

P212 - What is the reset sequence of a COP target?
Here is the sequence is simple terms of how the Reset Signals are toggled during bring up of the Board: - The BDI asserts HRESET - BDI Toggles TRST and resets the TAP controller - PPC asserts HRESET and SRESET - The BDI releases HRESET - BDI waits until HRESET and SRESET are inactive - Then it waits for debug mode entry

P312 - On our PowerPC processor the PC seems to start stepping backwards either during debugging or at system startup?
Normally this indicates some bigger problem. Start the processor in STARTUP RESET mode and make sure you do not get any startup error messages.

P412 - Can I write scripts to perform BDI operations?
The easiest way to script with the BDI is to write GDB Scripts. All BDI telnet commands are available thru GDB via the “mon” keyword.

X404 - Cannot open file on host
You will get this error when the BDI tries to access a file on the TFTP server and the file either does not exist or it cannot communicate with the TFTP server.

L310 - What are the benefits of using the BDI2000 over a Kgdb stub?
The BDI2000 is a system bring up / system debug tool. It can be used to program your flash, bring up a test board and initialize ram and peripherals. It is a complete development solution.

P313 - Why does the Program counter seem to jump around in my code? It does not follow the code execution.
This is not uncommon and is due to instruction reorganization and rescheduling.

P314 - 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.

P413 - I want to move the BDI to and from a secure lab, but need to know the internal memory configuration of the BDI to make sure that individuals are not able to take data in and out of the lab using the BDI
The BDI has 512 KB unbuffered SRAM and 1MB Flash. The flash and the RAM used for the processor running in the BDI2000 are not isolated.

X405 - I cannot ping the BDI on our network. It seems like it is dead.
First of all please check the BDI error codes to see if your BDI is working properly, (see related article below, A402).

L311 - 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.

P315 - GDB will not single step.
When I connect GDB to the BDI everything seems fine but the PC does not seem to single step, I get an error from GDB. Everything else like registers, memory, breakpoints and continue seem to be working. Doing an “n” from gdb results in a memory access error.

X406 - Where can I get config files for the BDI2000?
The BDI2000 gets shipped with a few config files that were used during the firmware development of the BDI and are located in the firmware directory.

L312 - Why does the Program counter seem to jump around in my code? It does not follow the code execution.
This is not uncommon and is due to instruction reorganization and rescheduling.

P316 - MPC83xx SAP error trying to read dcache. Why do I get this “# SAP: read access failed” error from the BDI?
First of all make sure that your debug entry cause is not <reserved 0> as this would indicate a more serious startup issue. Please check our FAQ repository for the proper FAQ on t