Is IAR C-SPY needed?

Go To Last Post
5 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello fellow freaks!

Our developer wants to switch from GCC to IAR and I’m wondering which version is most suitable of IAR. Basically we are choosing between Standard which is everything included and Limited which lacks MISRA C checker and C-SPY Debugger. The MISRA part we can be without but what about C-SPY debugger? Normally all development is done in AVR Studio, is C-SPY really needed then?

All feedback welcome! (Except comments regarding why we switch from GCC to IAR.)

Björn

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

If you use Studio (and presumably a JTAG?) then you'd have no need for C-Spy

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I used IAR and C-SPY back in college, and I remember C-SPY had a code profiler. It told the execution time spent in each function, in percent of total processing time. Useful for finding bottlenecks in the code.

So, if you need to squeeze the performance to the maximum, that is useful.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Our developer wants to switch from GCC to IAR
On the topic of switching to IAR, I was wondering if there is a good reference that gives details of all of the changes required to move an existing code base from AVR GCC to IAR.

I've seen some overviews, but nothing that for instance, gives details about which #defines are equivalent between the two or what #include files are equivalent.

I have a size limited version of IAR but gave up in disgust trying to move my existing code base.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks for all good replies!

clawson: Yes, we use AVR Studio with JTAG.

Thomas Strand: Very good functions you mention.

I've been missing the finding bottlenecks functions that can be found in C-SPY, so we'll by Standard version with C-SPY.

/Bjorn