[jasonkelly214]

I found it. It’s not a JLinkGDBServerCL window. It’s the VisualGDB Output window, you select JLinkGDBServerCL at the top of the window.

 

I can’t get the data to show properly though. It works in the j-lnk swo viewer software. but here the hex values aren’t even correct. Is there a setting I’m issing?

Attachments:

You must be logged in to view attached files.

[jasonkelly214]

https://sysprogs.com/w/forums/topic/undefined-reference-to-end-_sbrk/#post-32248

 

Can you review this post for which I just posted a full walkthrough of setup procedure?

[jasonkelly214]

I cannot say if it’s not working per the tutorial. The tutorial doesn’t show how to activate the window. Is the jlinkDGBservercl window already installed? Should it be present when I start a visualgdb project? Is it supported in Visual Studio 2022?

[jasonkelly214]

Ok I see.

Even with a default project it doesn’t pull in the ASF files; I still had to follow your step of including them from the project properties.

 

I went back and forth on using AFS because I find it cumbersome to navigate and often full of bugs, especially relating to setting the clocks. I thought that by importing the atmel start sdk the various makefile settings would be included such that I could create my project with whatever was needed for the project. I didn’t understand sbrk or that it wasn’t a hardware mapping but was a “utility”.

It seems sufficient to pull in utils_syscalls.c from the asf files.

I have it working now, thanks!

[jasonkelly214]

I know you said to upload the original, but I’m not sure what all was in it. I just generated a new atmel start sdk  from start.atmel.com and created a new visualgdb project with the same steps I did above and I got the same results.

I noticed the warning “manually-specified variables were not used by the project: LOCALAPPDATA”. I suspect that could be relevant since that is the location of the Atmel start file?

Shared files location: C:\Users\jason\AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.atstart.ATSAME51J18A

Here is the .atzip from the start configurator: https://www.dropbox.com/s/iwasymqxcnljno8/My%20Project4.atzip?dl=0

 

I know there were some settings in the advanced section about path mapping, none of which I changed. But in the error output it shows a path using both a forward and back slash; I assumed this was ok. Screenshot attached.

 

 

Attachments:

You must be logged in to view attached files.

[jasonkelly214]

I’m still in my evaluation period and this is my first project with visualgdb. I don’t think I selected anything that would cause this error but please do let me know.

Attachments:

You must be logged in to view attached files.

[jasonkelly214]

Launch visual studio, click “continue without code”.

File -> New -> VisualGDB Project

Embedded Project Wizard. Click Add

Embedded application, Advanced CMKake, C99

NEXT

Select ARM in C:\SysGCC\arm-eabi

ATSAME51J18A

Execute from FLASH, library default, Implementations for _sbrk(), etc “minimal (no semihosting)”

NEXT

Empty project

NEXT

OpenOCD, CMIS-DAP SWD programmer, target/atsame5x.cfg, SWD, Program FLASH memory always, reset before programming.

FINISH

 

Add new C file to project named main.c with main() function.

 

Project builds successfully.

Include <string.h>, add snprintf() function, error undefined reference to “end”. “could not open project\build\VisualGDB\Debug\sbrk.c, that file path might have been parsed incorrectly”.

Attachments:

You must be logged in to view attached files.

[Author]

Posts