First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 86697
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Embedded Team <dev-embedded@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Sandro Bonazzola (RETIRED) <sanchan@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
avarice-2.3.ebuild Proposed ebuild for avarice 2.3 text/plain Sandro Bonazzola (RETIRED) 2005-03-25 13:05 0000 868 bytes Details
metadata.xml Metadata for avarice text/plain Sandro Bonazzola (RETIRED) 2005-03-25 13:05 0000 352 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 86697 depends on: 98660 Show dependency tree
Bug 86697 blocks: 78908
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2005-03-25 13:04 0000
New ebuild for dev-embedded.

In recent times, GCC added support for the AVR series of microcontrollers. This has been quite the boon for those of us who write embedded applications for processors with "leaner" architectures. Recently, Atmel announced the availability of a JTAG box for the AVR. Until now, there was no way to interface to this device with GDB.

AVaRICE runs on a POSIX machine and connects to gdb via a TCP socket and communicates via gdb's "serial debug protocol". This protocol allows gdb to send commands like "set/remove breakpoint" and "read/write memory".

AVaRICE translates these commands into the Atmel protocol used to control the AVR JTAG ICE. Connection to the AVR JTAG ICE is via a serial port on the POSIX machine.

Because the GDB <---> AVaRICE connection is via a TCP socket, the two programs do not need to run on the same machine. In an office environment, this allows a developer to debug a target in the lab from the comfort of their cube (or even better, their home!)

------- Comment #1 From Sandro Bonazzola (RETIRED) 2005-03-25 13:05:14 0000 -------
Created an attachment (id=54470) [edit]
Proposed ebuild dor avarice 2.3

------- Comment #2 From Sandro Bonazzola (RETIRED) 2005-03-25 13:05:56 0000 -------
Created an attachment (id=54471) [edit]
Metadata for avarice

------- Comment #3 From Scott Price 2005-04-06 08:21:37 0000 -------
I submitted an ebuild for gdb (Bug #88169) that would allow it to be built for
different targets.  When that is put into portage I will submit a patch to
crossdev so that gdb can also be built with the rest of the avr toolchain.

------- Comment #4 From Sandro Bonazzola (RETIRED) 2005-04-06 11:48:04 0000 -------
Well done.

------- Comment #5 From Henrik Brix Andersen 2005-07-28 12:12:02 0000 -------
sys-devel/crossdev-0.9.8 supports building avr-gdb, as required by AVaRICE.

------- Comment #6 From Sandro Bonazzola (RETIRED) 2005-07-28 12:37:23 0000 -------
Well done.

------- Comment #7 From SpanKY 2005-07-28 13:24:06 0000 -------
Scott: can you review this ebuild ?

------- Comment #8 From Sandro Bonazzola (RETIRED) 2005-07-28 13:47:18 0000 -------
the ebuild should be modified to RDEPEND on the new cross-avr/gdb.
It seems that no special tool are required in DEPEND, standard system tools
should be enough. Maybe DEPEND can be set on sys-devel/gcc.

------- Comment #9 From Scott Price 2005-07-28 14:37:53 0000 -------
I am out of town until Sunday.  I will check it when I get back.

Sorry for the delay.

Scott  =)

------- Comment #10 From Scott Price 2005-09-05 18:57:17 0000 -------
Woops.  It seems I dropped the ball here.  I will look at this tomorrow.

Sorry.

Scott  =)

------- Comment #11 From Scott Price 2005-09-07 09:02:47 0000 -------
The ebuild builds fine on my x86 and amd64 machines.  The only thing I had to
change was add ~amd64 to the keywords.  I don't have a good way to test whether
avarice itself works, but it does run.  It just complains that it can't find the
jtag emulator.

Scott  =)

------- Comment #12 From SpanKY 2005-09-07 18:56:41 0000 -------
thanks, now in portage

First Last Prev Next    No search results available      Search page      Enter new bug