Don't know what happened, using atmel ice debug wire and after install of codevision full version and licence
when I press the green debug arrow that uploads the code it wont step through the C code anymore.
What do I do?
Go on. ZIP up your AS7.0 project and attach it.
Are you using Debug or Release?
Using Debug Here is the .zip
Its actually the rudimentary pulse oximeter code, I have to relearn everything, been a long time since I have done this stuff.
Thanks for the ZIP.
Sure enough, it shows ASM code when I debug with the Simulator.
I built a new CV project in AS7 using your C file.
It built fine. It debugged fine with the C source. It even reports to Output Window for the Conditional Breakpoint.
I am not sure what is going wrong with your CPROJ.
The obvious fix is to just create a new project and copy your C file.
I will have a look at your "build" later today.
Did you create your project before getting your CV licence?
I have never used the Evaluation version. Your project is very small (920B). I would guess that the Evaluation gives a full Debug experience in AS7.0 (for projects < 4kB )
Your Line breakpoints are not recognised. Delete your existing Breakpoints. Then add fresh Breakpoints as near as possible.
I often have multiple projects in one Solution. So it is not uncommon that the Debugger can't evaluate every Breakpoint physical address from the Source line.
I have not experienced your behaviour !!
I found it odd as well in the Dependency folder there was a mega3xx.bit.h and then when i thought Dropbox was causing problems
because my code is in a dropbox folder I copied the folder to my hard drive and double clicked on the solution file,
then there was a different megaxxx.bit.h file in dependency folder. When debugging that there was still references to sysop\dropbox
in the disassembly code (in red type)
Perhaps I need to do a CLEAN and rebuild
I know I had problems working in Visual Studio with C# and another programmer sharing code
because files in the debug folder would not be refreshed to my computers folder structure.
One more thing, my studio 7 for a while after the install of codeview would not run the tool background and just hung with a message wait for a min or cancel
after rebooting it loads the tool background again.
When I get home i will create new project and paste in the code.
I think its good you had the same problem was not looking forward to reinstalling everything.
I did try making a new project with just a main and loop, but on debugging using the same atmel ice and dbugwire it complained about the debug wire
when I re loaded the mega48blinky program it uploaded fine and started debugging, both tool settings were the same but the new main only one did not have
any cpu clock settings (generated n the other code by codevision).
One more thing, red squiggly lines on #defines from .h files keep are back, if I open the .h file then go back to my .C code they go away.
I can understand AS7.0 having difficulties when associating a real-life Flash address with a line in source code.
I suggest that you delete all breakpoints after a substantial edit. Then start Debug session and re-apply the Breakpoints.
When you are in Debug session AS7.0 shows breakpoint success or failure.
Sometimes it is worth going to the ASM view if you want fine control of the breakpoint address.
Incidentally, you will find CV generated code is a lot easier to debug than GCC code.
I use to use Code Vision IDE all the time , Perhaps I should just switch to Code Vision to write / compile / build I don't even know
can i debug in code vision IDE stand alone with no atmel studio, I was confused as this new version (from the one i used a long time ago)
ties in with AS7 , I am also thinking I should move to a JTAG device instead of the mega48 (just happen to have a bunch of them left over from the old days)
Looking for a list of JTAG atmel chips that work with AVR-ICE programmer, I did read about older JTAG systems and limited list of AVR's
You can build and debug CV from AS7.0
The AS7.0 IDE is not as pleasant as CV IDE but perfectly usable.
debugWIRE is ok for debugging. JTAG, PDI, UPDI, ... are faster and less prone to foot-shooting.
Choose whichever board is most convenient for developing your project. Generally this is a chip with plenty of legs, memory etc.
When you have finished developing, rebuild and test on the smallest, cheapest chip e.g. mega48.
Ordering these chips, Are there any others with JTAG I should try?
Looking for a list of JTAG atmel chips that work with AVR-ICE programmer, ...
Atmel Studio 7.0.2389 may have switched to version 2 device packs :
Microchip Packs Repository
AVR and SAM Downloads Archive | Microchip Technology
Atmel Studio 7 | Microchip Technology (7.0.2389)
"Dare to be naïve." - Buckminster Fuller
Thank's now if I can get rid of the kink in my neck from reading them sideways.....
© 2019 Microchip Technology Inc.