| Author |
Message |
|
|
Posted: Aug 10, 2011 - 05:02 AM |
|

Joined: Jul 04, 2010
Posts: 161
|
|
|
aussieavr wrote:
Hi saaadhu,
This is fantastic and has helped to restore my faith in the new AS5.
Thanks. Glad you found it useful.
Quote:
static const gpio_map_t USART_GPIO_MAP =
{
{EXAMPLE_USART_RX_PIN, EXAMPLE_USART_RX_FUNCTION},
{EXAMPLE_USART_TX_PIN, EXAMPLE_USART_TX_FUNCTION}
};
and
Disable_global_interrupt();
The project compiles file with no errors or warnings.
What am I missing (a #include perhaps?)
No, you found a bug. One of the header files included before gpio.h (which has the struct's definition) had GCC and/or C99 specific extensions, and Clang stopped processing the file when it hit those errors. I tried turning on C99 and GNU specific extensions/keywords, and I don't get errors now. I'll update this thread once I upload a new build later in the day.
Quote:
Also did you say you are a member of the AS5 team? If so are they planning on introducing support for programming of USB DFU Boot Loaders via JTAG ICE MKII like one could in AVR32 Studio?
It's in our todo list is all I can say  |
_________________ Regards
Senthil
|
| |
|
|
|
|
|
Posted: Aug 27, 2011 - 09:04 AM |
|

Joined: Jan 25, 2008
Posts: 13
|
|
Any hint of when a new version is due saaadhu  |
|
|
| |
|
|
|
|
|
Posted: Sep 01, 2011 - 09:32 PM |
|

Joined: Jul 04, 2010
Posts: 161
|
|
Sorry, couldn't find time to work on this. I uploaded a new build though at https://github.com/downloads/saaadhu/na ... 0v0.2.vsix .
Naggy can now show warnings (green squiggly) and errors (red squiggly) separately, and it also handles a lot more GCC specific stuff without barfing up. Unfortunately, builtin directives unknown to Clang (Enable_global_interrupt uses __builtin_csrf)x still show up as errors, but that'll have to wait for the next build. |
_________________ Regards
Senthil
|
| |
|
|
|
|
|
Posted: Sep 02, 2011 - 10:37 AM |
|

Joined: Jan 25, 2008
Posts: 13
|
|
| Thanks saaadhu, trying out now. |
|
|
| |
|
|
|
|
|
Posted: Jan 11, 2012 - 01:31 AM |
|


Joined: Mar 27, 2009
Posts: 125
Location: Hellas
|
|
| Senthil i think the latest ver of naggy (0.2.4) does not work in AS 5.1 Beta 148. |
|
|
| |
|
|
|
|
|
Posted: Jan 13, 2012 - 09:27 PM |
|


Joined: Mar 27, 2009
Posts: 125
Location: Hellas
|
|
| Could someone check it to make it sure that its a Bug? |
|
|
| |
|
|
|
|
|
Posted: Jan 14, 2012 - 09:40 AM |
|

Joined: Jul 04, 2010
Posts: 161
|
|
|
DieCore wrote:
Could someone check it to make it sure that its a Bug?
Yes, it appears to be a bug. I don't have a proper 5.1 beta build with me at the moment, but based on the description and after some debugging with a dev build, I have a build of Naggy that I think works around the problem. Can you try installing Naggy from https://github.com/downloads/saaadhu/naggy/Naggy%20v0.2.4%20for%205.1.vsix (after uninstalling the previous version)? |
_________________ Regards
Senthil
|
| |
|
|
|
|
|
Posted: Jan 14, 2012 - 02:36 PM |
|


Joined: Mar 27, 2009
Posts: 125
Location: Hellas
|
|
|
saaadhu wrote:
DieCore wrote:
Could someone check it to make it sure that its a Bug?
Yes, it appears to be a bug. I don't have a proper 5.1 beta build with me at the moment, but based on the description and after some debugging with a dev build, I have a build of Naggy that I think works around the problem. Can you try installing Naggy from https://github.com/downloads/saaadhu/naggy/Naggy%20v0.2.4%20for%205.1.vsix (after uninstalling the previous version)?
Ok
I installed the .vsix that you provided for the AS5.1.
I tried and only the lowlighting of excluded code works.
Its saying again that error, it cant find the first header file... |
|
|
| |
|
|
|
|
|
Posted: Jan 15, 2012 - 08:36 AM |
|

Joined: Jul 04, 2010
Posts: 161
|
|
Ok, I have another build of Naggy out. I tested this on the beta build, and it appears to work fine - it works around the problem by hardcoding the default include paths for toolchains. Looks like AS 5.1 broke an API contract.
Anyway, you can try it again from the same link https://github.com/downloads/saaadhu/naggy/Naggy%20v0.2.4%20for%205.1.vsix. Do let me know if it works. |
_________________ Regards
Senthil
|
| |
|
|
|
|
|
Posted: Jan 15, 2012 - 09:50 AM |
|


Joined: Jan 23, 2004
Posts: 9832
Location: Trondheim, Norway
|
|
|
Quote:
Ok, I have another build of Naggy out. I tested this on the beta build, and it appears to work fine - it works around the problem by hardcoding the default include paths for toolchains. Looks like AS 5.1 broke an API contract.
AS5.l have moved the toolchain out of the root install and into a VS extension itself - could that be the issue? Making the toolchain and ASF modules extensions would/will allow for upgrades to be made to the IDE or the modules without affecting the other components.
- Dean  |
_________________ Atmel Studio 6.1 is now released, grab it here.
Report AS6/ASF bugs here.
|
| |
|
|
|
|
|
Posted: Jan 15, 2012 - 04:36 PM |
|


Joined: Mar 27, 2009
Posts: 125
Location: Hellas
|
|
|
saaadhu wrote:
Ok, I have another build of Naggy out. I tested this on the beta build, and it appears to work fine - it works around the problem by hardcoding the default include paths for toolchains. Looks like AS 5.1 broke an API contract.
Anyway, you can try it again from the same link https://github.com/downloads/saaadhu/naggy/Naggy%20v0.2.4%20for%205.1.vsix. Do let me know if it works.
This WORKS for the 8bit toochain ONLY in a CUSTOM simple project with #include <avr/io.h> but it can't find a path for instance (C:\Users\Administrator\Documents\AVRStudio 5.1\TC_SIMULATOR_EXAMPLE_xmega\TC_SIMULATOR_EXAMPLE_xmega\src\config\conf_example.h) (Win7 SP1 x64)
for the tc_example for xmega simulator (write simulator in the example projects menu and you find it fast)
SECONDLY it doesn't work for the avr32 toolchain at all i think,
tested with the first simulator gpio example project
it cant find the #include "gpio.h" (C:\Users\Administrator\Documents\AVRStudio 5.1\GPIO_SIMULATOR_EXAMPLE\GPIO_SIMULATOR_EXAMPLE\src\asf\avr32\drivers\gpio\gpio.h)
I also tried other example avr32 & projects with the #include <asf.h> as a first line in the main.c file fo the project with the same issue it cant find the path.
I think you need to hardcode the avr32 toolchain like what you did for the avr8 but also the main project path.I also noticed a strange thing, at the xmega project if i change the <asf.h> to "asf.h" it fixed the path unknown issue (i comment with // the previous headers to let naggy check the asf.h file first).A conversion of <> to "" doesn't help in avr32 projects.
Thanks for the Help! Its really a useful program extension specially for C dummies like me.I think its useful even for the OLD experts...  |
|
|
| |
|
|
|
|
|
Posted: Jan 17, 2012 - 10:27 AM |
|

Joined: Jul 04, 2010
Posts: 161
|
|
|
|
|
|
|
Posted: Jan 18, 2012 - 08:19 AM |
|


Joined: Mar 27, 2009
Posts: 125
Location: Hellas
|
|
|
|
|
|
|
Posted: Mar 28, 2012 - 10:58 PM |
|

Joined: May 09, 2009
Posts: 113
|
|
| Is Naggy compatible with AVR Studio 6? |
|
|
| |
|
|
|
|
|
Posted: Apr 03, 2012 - 04:50 PM |
|

Joined: Jul 04, 2010
Posts: 161
|
|
|
|
|
|
|
Posted: Apr 17, 2012 - 01:41 PM |
|


Joined: Jan 23, 2004
Posts: 9832
Location: Trondheim, Norway
|
|
Senthil,
What's the likelyhood of this becoming a standard AS6 extension available through the online gallery, or included in the installer?
- Dean  |
_________________ Atmel Studio 6.1 is now released, grab it here.
Report AS6/ASF bugs here.
|
| |
|
|
|
|
|
Posted: Apr 17, 2012 - 06:10 PM |
|


Joined: Mar 27, 2009
Posts: 125
Location: Hellas
|
|
| That's a very good idea Dean! I prefer to be available through the online gallery to be easier for the future updates! |
|
|
| |
|
|
|
|
|
Posted: May 10, 2012 - 08:35 PM |
|


Joined: Mar 27, 2009
Posts: 125
Location: Hellas
|
|
Hi Senthil
Please rebuild Naggy for the AS 6.0 Final which just released.The latest naggy for AS6 doesnt work for the AS 6.0 Final i think because the paths are changed again
Is it possible to extend naggy and make it compatible on Visual Studio 2010? I don't know if there is any gcc x86 toolchain for VS2010 as first step |
|
|
| |
|
|
|
|
|
Posted: May 13, 2012 - 03:54 PM |
|

Joined: Jul 04, 2010
Posts: 161
|
|
|
|
|
|
|
Posted: May 23, 2012 - 04:27 PM |
|


Joined: Mar 27, 2009
Posts: 125
Location: Hellas
|
|
I think there is a bug in Naggy for AS6 RTM
It works fine when i make a new C project for Atmega32 but it doesnt work for instance with this bigger project and its showing errors because it cant find/recognise the io.h header.
I also use Productinity Power Tools and Ultra Find as third party extensions and i am not sure if there are any compatibility issues.
Does anyone else has similar issues?
I tried to build myself naggy on VS2010 SP1 it opens the main solution file (Naggy.sln)but it showing an error that it can't open the naggy c# project (Naggy.csproj) |
|
|
| |
|
|
|
|
|