Re: key steps to get c-file debugging info into AVRStudio 4
From: Richard M. (richard_at_imagecraft.com)
Date: 03/16/05
- Next message: Robertus: "Re: Inexpensive ARM compilers"
- Previous message: mark thomas: "Re: Serial Product to USB i/f"
- In reply to: Joe: "Re: key steps to get c-file debugging info into AVRStudio 4"
- Next in thread: Joe: "Re: key steps to get c-file debugging info into AVRStudio 4"
- Reply: Joe: "Re: key steps to get c-file debugging info into AVRStudio 4"
- Reply: Meindert Sprang: "Re: key steps to get c-file debugging info into AVRStudio 4"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 15 Mar 2005 15:23:12 -0800
Joe wrote:
>yes, it is gcc that I'm using.
>...
>I did load ImageCraft's ICCAVR with a view to porting the existing project
>to this environment, but I got put off by two things:
>
>1. The keyword that you use to indicate Program Memory (flash), is 'const'.
>I got to that while porting and thought it seemed suspect. I.e. I didn't
>imagine that it would always do what I was wanting.
>
>
>
While somewhat unusual, I don't think it breaks ANSI C's definition per
se, except for people who use "const char *" to a function's argument to
mean the function will not change the content, but I can be wrong. In
anyway, AVR is a Harvard architecture so this issue needs to be handled
one way or another...
I *may* add a separate keyword at some future release, but it will have
to be done slowly to support backward compatibility :-(
>2. When I was trying to convert an old gcc 'set bit' instruction, your
>documentation said, "see the Atmel data***". I'm afraid that was the
>deciding factor for me - to stick with GCC for a bit longer to see if I
>could get it to work.
>
>
>
Eh? One problem here is that the old GCC does not generate set bit
instruction so now you have unnecessary extensions to the language in
your program. I am pretty sure the new GCC fixes it, but a set bit is
simply:
unsigned char c;
#define bit(x) (1 << (x))
c |= bit(2);
...
etc.
>When one pays for a product, one does not want to be sent running around
>looking for answers - if a runaround IS necessary, at least and explanation
>of why and a hint of where in the data*** to look would be helpful.
>
>
>
Unless I am wrong, you are only experiencing this because your program
happens to use a non-standard C extensions. This is the prime reason we
avoid extensions as much as possible....
>3. (This was not a deciding factor, but it's a negative factor with your
>product) Whenever I open your html help, I keep getting asked if I want to
>allow such and such a thing to be installed (I don't, so this is very
>annoying) - what does this give me that I can't do without it- I seem to be
>able to browse your help even if it does not load.
>
>
>
Not sure what you mean here. We switched to use HTML Webwork help on V7,
so there may be requirements that I don't know of, but so far, I have
not gotten any such complaints from other people. You need either
Javascript or Java and the Webworks suppose to detect that, but I am not
aware that it needs anything else to be installed.
>What are your comments on these points?
>
>I'm in no way a commited gcc person and would willingly pay to make my life
>easier when it comes to developing this code, so there is still time to
>convert me to ICCAVR.
>
>
>
Well, hope this helps. If you wish, you can email me privately if you
have more questions etc.
-- // richard http://www.imagecraft.com
- Next message: Robertus: "Re: Inexpensive ARM compilers"
- Previous message: mark thomas: "Re: Serial Product to USB i/f"
- In reply to: Joe: "Re: key steps to get c-file debugging info into AVRStudio 4"
- Next in thread: Joe: "Re: key steps to get c-file debugging info into AVRStudio 4"
- Reply: Joe: "Re: key steps to get c-file debugging info into AVRStudio 4"
- Reply: Meindert Sprang: "Re: key steps to get c-file debugging info into AVRStudio 4"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]