Breakpoint issue while project starting to execute

Hello,

When you get the "Failed to set automatic breakpoint at main" error message, it is nothing to do with building the project. If the internal IDDE function that sets breakpoints fails for any reason, this error is returned to the IDDE. There is an option to "Load executable after build" available under "Settings: Preferences: General". When the build has completed, the tools will then load the DXE to the target. Once the DXE has been loaded, the IDDE will attempt to set breakpoints at each of the relevant addresses for breakpoints listed under 'Settings: Breakpoints'.

These automatic breakpoints include main, __lib_prog_term and __stack_overflowed, and the error message "Failed to set automatic breakpoint at <symbol>" indicates that the IDDE is unable to access the processor's memory in order to write the Emulator Trap instructions at these addresses.

The most common reason this occurs is that the location of the breakpoint in question is in external memory, and the external memory interface is not correctly configured. The IDDE, by default, only takes steps to configure the external memory interface of a target for a debug session where that target matches an EZ-KIT Lite (e.g. for a 21371 or 21369 target, but not for a 21368 target as there is no 21368 EZ-KIT Lite).

If you are using custom hardware, we would recommend you to use a Custom Board Support File to configure these registers to values suitable for your target.

For more information on this behavior and Custom Board Support Files, I recommend reading the following FAQ on our Engineer Zone, and the relevant documentation:

https://ez.analog.com/dsp/software-and-development-tools/hardware-tools/w/documents/6752/faq-my-application-behaves-incorrectly-when-using-sdram

Please try and let us know how you are getting on

Regards,
Santha kumari.K

Hello,

Could you please let us know the above mentioned issue has been resolved in your side

Best regards,

Santha kumari.K

Hello,

Could you please let us know the above mentioned issue has been resolved in your side

Best regards,

Santha kumari.K

Hi Santha,

No,we are still facing this issue, but we find the actual issue. my project is not able to read the custom support file.

and I don't know how to give the path in Visualdsp++ for custom support file.

Regards 

Asim Aslam

Hello Asim,

You can configure a debug session to read a particular custom board support file. This file is read after the Analog Devices processor definition file.

To read a custom board support file :

The following procedure assumes that a custom board support file has already been created.

1.From the Settings menu, choose Session. The Session Settings dialog box appears. At present, the dialog box has only one page, General.

2.Select Enable customizations.

3.In Custom board support filename, type the path and name of the custom board support file, or click the ... (browse) button to navigate to the file. Custom board support files have an .xml extension.

The custom board support files may be written to a directory of your choosing. Analog Devices recommends that you store custom board .XML files in the standard area for user documents:
Document and Settings/<username>/My Documents

By default, clicking "Browse" in the Session Settings dialog box opens to this directory.

4.Click OK.

5.Disconnect and then reconnect to the target, or restart the IDDE.You must take this action for your changes to take effect.

You can find further details in the VisualDSP++ Help. Simply navigate to: 'Help' - 'Contents' - 'Graphical Environment' - 'Custom Board Support'.

As we said previously, There's an FAQ on the EngineerZone called  "My application behaves incorrectly when using SDRAM". This discusses the use and setup of Custom Board Support files, you can access the FAQ here:

ez.analog.com/.../faq-my-application-behaves-incorrectly-when-using-sdram

Regards,
Santha kumari.K