[tanevitt]

At least one problem solved:

I was able to locate my linker script by doing the following:

Right click VisualGBD Project -> VisualGBD Project Properties -> MSBuild settings

There I was able to find the path for my linker script.

[tanevitt]

Hello,

Thank you for your response. I was pulled to another project for the past couple weeks, but now I am getting back to this.

Regarding your first suggestion of checking sizes/alignment in Embedded Memory Explorer, I’m able to open Embedded Memory Explorer and see the flash progress of various sections of my code (see attached screenshot, embedded_explorer.png) but I’m unable to locate my linker script to adjust the alignment. Where can I find my linker script to begin editing it?

Regarding your second suggestion of using Segger J-Link instead of OpenOCD, I was able to download J-Link and I can select it in my DeBug settings. It even autodetects the correct debugging device, however, when I click the “Test” button with Segger J-Link selected, I get the message that “No emulators connected via USB”. See attached sceen shot, “J_link.png” Some googling around suggested that perhaps this could be an issue with the default USB drivers not being compatible with J-Link, but another coworker suggested that J-Link may not work without using a physical J-Link debugging probe, such as the J-Link Pro. To get Segger J-link to work in this situation, is it a matter of changing my USB drivers around to work, or perhaps re-flashing ST-LINK onboard to work with J-Link? Or do I need to buy a J-Link Pro?

Thank you, and please let me know if you need any additional clarifying information.

-Zander

Attachments:

You must be logged in to view attached files.

[Author]

Posts