Choose a category on the left to view all FAQ's by section.

You may also search articles to find answers!

 

 

Find out more about our Support Program  

Frequently Asked Questions

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

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.

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.

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

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.

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.

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.

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.

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.