I just installed Atmel Studio 7 on my Windows 10 HP laptop. This is my first time working w/ a C compiler since high school, and my first time working with a microcontroller.
I loaded one of their example projects and built it without any errors. However, I am not able to debug since there is no option for a debugging tool (see screenshot). The only option is for 'Custom programming tool', while their tutorial videos all show an option for a SAM-ICE debugger or Simulator (e.g. https://www.youtube.com/watch?v=9QlDSNeuAdY)
I have spent hours trying to find an issue online w/ no luck. Please help!
I have had the same problem. I solved this by unchecking the box Tools->Options->Debugger->Backend Agent-> Start Local Backend Agent and then checking that box again
I'll add this information as I also just spent a fair amount of time trying to determine why no debugging tool was available as an option:
Make sure you have the right device connected.
I know this sounds terribly basic, but in my case I have both SAML21 and SAML22 Xplained Pro boards, and I'd forgotten which one I had targeted for a particular project. If you have a project open that targets one, but the attached device is different, you may have this problem. The only available option becomes "Custom Programming Tool" which isn't helpful.
After connecting the correct board, I had to revisit the Tool menu and change the selected debugger/programmer to the appropriate (only) EDBG • ATML###### option.
If you're not using an Atmel Xplained board, this may not be applicable.
I spend some time about this problem as well and found out that all I had to do was go to Device and Debugging options then go to Build and select All Configurations in the configuration box then the simulator should appear under tools.
In my case it was atbackend.exe which crashed after hibernating my laptop. I had to stop Atmel studio, ensure that no AtmelStudio or atbackend processes exist in system and then start ATmel STudio again. After that Simulator appeared in Tool-Selected debugger/programmer.
Related
Downloaded & Installed/unzipped Eclipse 2020-9 to see if my old version ( Mars ) was broken.
When I do something simple like
Add a Folder
I get two "create folder dialogues"
2 popups
Same when I right click to delete a folder, I get two delete dialogue boxes.
these are just two examples, I'm guessing most actions will have two reactions!
Cannot debug a target get an error ( Stop the first session before staring a new one )
guessing Run->Debug is fired twice too.
I'm a long time eclipse user, so really curious why this is happening
issue started when I got a 'new' win 7 pc, discovering this bug while setting up my environment
any hints are welcome.
Used OpenJDK and Oracles Java 8 same issue ( Tried two versions of eclipse, same issue )
Eclipse is used for C development with ARM MCUs with OpenOCD and Gcc for ARM.
Many thanks for taking time to read this.
Regards
Alan
Solution:
Fixed nVidia graphic driver application software was the culprit, the one that makes enhances the user experience by making windows go transparent when you drag them, good useful stuff like that. Uninstall nVidia desktop enhancing tools and Eclipse (and Notepad++ ) work perfectly Eclipse was never the problem, just the side effect.
I downloaded Visual Studio 2017 Community and installed it on my Windows 10 PC. I downloaded the HomeSeer templates from the VS "marketplace" and installed them. I created a new project from the C# HSPI "A" template and pressed F5 to start the debug; I get 1 error message:
Error The command "powershell -file c:\users\paul\documents\visual studio 2017\Projects\HSPIPluginA1\HSPIPluginA1\fix-output.ps1 -configuration Debug -executionpolicy Unrestricted -NonInteractive" exited with code -196608.
Project: HSPIPluginA1 File: c:\users\paul\documents\visual studio 2017\Projects\HSPIPluginA1\HSPIPluginA1\HSPIPluginA1.csproj Line: 77
Do you have any idea what I did wrong? I'm pretty bad if I can't even get the default, pre-packaged, code to work.
Also, how do I provide an alternate IP Address for the plugin to connect to? My HS3 runs on a remote Linux (Lubuntu 16.04 LTS) machine. Thanks in advance.
I did not mean to imply that I was frustrated with you - it was me I was frustrated with; there just seems to be so much to learn. I know how much time and effort it takes to create/package/edit/document things so other folks can use them, so I certainly don't want to be a "whiner" right at the start. I also really appreciate you made the modifications to the template so quickly.
Thanks for reporting.
I just published an update to the extension that corrects the problem you were having. The corresponding tracking issue is https://github.com/alexdresko/HSPI/issues/62
I haven't finished the documentation yet, but you can see how to change the IP and port by going to https://github.com/alexdresko/HSPI/issues/7#issuecomment-283101463
Please do not expect perfection from this project. It's something I'm working on in my spare time and I am in no way affiliated with HomeSeer.
Now that I think about it, I do not know if this project will work with Linux, as that is something I haven't tested yet. I am very interested to know if it works, so please keep me updated.
Thanks again!
I would like to make a Graphical interface for a home-made program using SFML on Raspberry Pi2. I am using Raspbian. I recompiled the graphical lib
It works fine unsing startx first, then using my application, which wors perfectly fine.
But I can't figure if it is possible or how to launch my application directly after boot without launching startx (just to optimise the cpu of the Raspberry).
Starting my program direcly after boot, I get the following error:
Failed to open X11 display: make sure the DISPLAY environnement variable is set correctly.
Aborted.
I already tested the classic export DISPLAY=:0.0 but without sucess.
I interested myself in x and xinit, but I am not sure that would even do it.
Where should I start looking? I don't need a complete solution, even a hint or an idea would be nice!
I checked to see if it was possible to open a graphical app without the X desktop environment and as that answer states, with Firefox at least, you need the X server which SFML also probably needs in order to create a window.
The answer states:
Basically something like:
$ X
Then you just start Firefox in this X server:
$ DISPLAY=:0 firefox
You can switch from the X server and the framebuffer by using
CTRL+ALT+F1 and CTRL+ALT+F7.
You could try that and see if it helps.
Also, still searching, I found a forum post on the sfml website about what you're trying to accomplish stating somewhere:
SFML requires OpenGL, so as far as I know you need at least X running,
but you probably don't need gnome, KDE or a similar Desktop
Environment on top.
The forum guy asking for help seems to have managed to get X11 and a SFML basic render window to work on Ubuntu server after someone posted a link to xinitrc. I guess, that's the route to go from here.
I'm a rookie at C in general and VS 2013 also. I am trying to use some C code provided by a vendor in VS 2013 express. It compiles and runs without problem using the command line compiler but I would like to use the IDE.
I started a new project, C++ for console app, and I have pasted the code into the IDE and saved it as xyy.c so that it builds successfully. I thought it would be nice to have it in a GUI, so I duplicated the effort with a Win32 app project. It also builds.
The program's job is to connect to a PCI card that has Plx chip as an interface and program an FPGA. The Win32 program succeeds, even though I can't see any of the info printed by the program. The console program fails and I think it is because it fails to find the driver for the Plx chip. I thought I would get a clue by single stepping through the Win32 program to see which driver was supposed to be found.
However, after the first pass through a while loop, I get a pop up that says "Source Not Found" and "stack.cpp not found". Google wasn't any help to me.
I be grateful for any suggestions.
You might have "Enable .NET Framework source stepping" enabled (see http://msdn.microsoft.com/en-us/library/cc667410.aspx). So when you are at Stack... and trying to step into, it will actually try, but you don't have the sources for that. There is also a new experience for using the .NET framework reference source that was announced recently: http://blogs.msdn.com/b/dotnet/archive/2014/02/24/a-new-look-for-net-reference-source.aspx
I faced the same problem. I advise at the moment of receiving the information "stack.cpp not found" to look at the stack trace and check if there is something like this: "RTC".
If there is, you need to change the flag along the path (for example, set the Default or a more convenient configuration for you):
Project Properties -> C/C++ -> Code Generation -> Basic Runtime Checks
More details: https://learn.microsoft.com/en-us/cpp/build/reference/rtc-run-time-error-checks?view=msvc-160
I have been writing and debugging a minifilter on Windows 7 using the IFS Kit for some time now. it finally works, but as I require to add further functionality, I will spend some more days playing with it
what I'm worried about is debugging. until now I have simply built the driver, installed it on a virtual box and tested it by verifying dbg_print statements. I have been using this simple and error prone approach, as I could not find anything about how to debug minifilters more structured and programmatically.
are there any best practice methods to debug minifilters or filters? can visualDDK be used to add (remote) debugging functionality to visual studio for minifilters?
greetings,
curiosity
The Windows DDK includes a copy of windbg which you can use to connect to the VM over a named pipe with the appropriate configuration.
You can do one better by using VirtualKD to get an accelerated channel to talk to the kernel debugger embedded in Windows.
If you want to do debugging using the Visual Studio user interface, you should look at VisualDDK.
Both are powerful tools, but they require a little work to get set up the first time.
I tend to just use WinDBG because it is the easiest thing to set up on random QA machines etc.
But I have used those tools to iterate rapidly during initial development of a project.
Good luck.
Visual Studio does not support debugging in kernel mode. You can use kd or WinDbg, which are both part of the Debugger package included in Windows DDK. This will get you started with debugging:
Configure kernel debugger on VM and attach WinDbg. Instructions are here: http://ndis.com/ndis-debugging/virtual/vmwaresetup.htm.
Build your binaries in debug mode (or in release with full symbols).
Once WinDbg connected, fix up symbols, and source path. Make sure you added location of symbols of your new driver to the symbol path.
Now you can debug similar how you use VS for user mode apps.