Author Topic: Guidance needed for embedded processor JTAG debugging  (Read 4496 times)

Offline ChuckH

  • Single posting newcomer
  • *
  • Posts: 3
Guidance needed for embedded processor JTAG debugging
« on: March 18, 2011, 12:03:34 am »
I have been using Code::Blocks with the WinAVR (gcc) compiler for 2 or 3 months now for embedded development (Atmel AVR ATMega32) but I have been using AVRStudio for debugging.  I'd like to transition to debugging with Code::Blocks.  I tried a couple of times but I was never able to connect (using GDB etc.) with my serial connected JTAG device (ECROS Technology AVR "ICE-Cube").

Can someone point me to an on-line tutorial on how to set this up?

Thanks,

Chuck Hackett

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7785
    • My Best Post
Re: Guidance needed for embedded processor JTAG debugging
« Reply #1 on: March 18, 2011, 01:04:41 am »
Please post this type of topic in this sub-forum next time.
No need to post this post again; I do suggest you read the other sub-forum for info like this.

http://forums.codeblocks.org/index.php/board,22.0.html
C Programmer working to learn more about C++ and Git.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline scarphin

  • Lives here!
  • ****
  • Posts: 640
Re: Guidance needed for embedded processor JTAG debugging
« Reply #2 on: March 18, 2011, 09:00:44 am »
AVR Studio connects directly to target hardware without the need for any server. GDB needs a server in order to drive the target hardware and make the connection to it. To use GDB u have to setup a server first which is named 'avarice' then adjust GDB to connect to that server. CodeBlocks doesn't fire up a server automatically, it just launches GDB so u will have start the server manually. There is some info for ur hardware on the following link:
http://www.ecrostech.com/AtmelAvr/AvrIceCube/Using.htm
Check the section 'Debugging with AVaRICE and AVR Insight'. It suggests to use the command line 'avarice --jtag /dev/com1 :4242' to run the server before debugging but u might be needing some extra options. Check the 'avarice' manual for that.