Getting Started - Best Tools, techniques and such

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

Hi All,

 

I am new to the forum.  Did a project using an AVR... a long time ago.  It went very well.  And now there is a chance to design in an AVR again.

 

There are now a wide array of tools and devices... WOW!

 

What do people prefer?

 

 

1) What CPU?  For the current project there is a need for a lot of GPIO, USB (or similar) and that is about it.

 

    design calls for GPIO(44): reset, trigger, quadrature decoder, five 8-bit buses, TWI and some communicatoin path - USB (or equiv)

    It looks like most of the CPU devices are suitable.

    The Atxmega384c3 seems to be a descent candidate (the AVR32 was the first choice, but the 8-bit device looks cleaner).

    What do people think of this device for a new design?

    Anything more prefered to suggest?

 

2) What IDE is prefered?  I have downloaded studio 6 and 32.  The former seems fine.  Any comments?

 

3) Debug tools?  What hardware do people prefer? The Atxmega384c3 does not have JTAG.  How do people physically connect to the device?

 

4) Bring-up?  What procedure is needed to bring up a freshly minted CPU?

    There are a lot of refrences to the boot loader, but the details on first bring-up are unclear.

    There are references to mEDBG, but it is unclear what it is.

    It seems that the program and debug interface (PDI) is the way to go, but how is unclear.

 

Any pointers, comments or references are greatly appreciated.

Last Edited: Sun. Mar 8, 2015 - 04:49 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Trivet wrote:

1) ...

    design calls for GPIO(44): reset, trigger, quadrature decoder, five 8-bit buses, TWI and some communicatoin path - USB (or equiv)

...

    The Atxmega384c3 seems to be a descent candidate ...

    What do people think of this device for a new design?

    Anything more prefered to suggest?

A C3 (3 series is 64pin) XMEGA looks to be "tight" (on signal count) for the requirements.

An A1U (1 series is 100pin) XMEGA would be a better fit; XMEGA A1U XPlained Pro has an EDBG (Embedded Debugger) and a 512kB external SRAM.

There are a few to several XMEGA A1U third party boards.

Trivet wrote:
3) Debug tools?  What hardware do people prefer?
Atmel-ICE is popular.

Trivet wrote:
The Atxmega384c3 does not have JTAG.  How do people physically connect to the device?
Program and Debug Interface (PDI).

Trivet wrote:
There are references to mEDBG, but it is unclear what it is.
mEDBG is only on the Xplained Mini boards; it's the mini version of EDBG.


Atmel Corporation

XMEGA A1U Xplained Pro Evaluation Kit (ATXMEGAA1U-XPRO)

http://store.atmel.com/PartDetail.aspx?q=p:10500399#tc:description

http://www.findchips.com/search/ATXMEGAA1U-XPRO 

Atmel Corporation

Home > Products > Microcontrollers > AVR 8- and 32-bit MCUs > AVR XMEGA MCUs

Atmel-ICE

http://www.atmel.com/tools/ATATMEL-ICE.aspx

XMEGA384C3 and PDI :

https://www.avrfreaks.net/comment/1383551#comment-1383551

in

https://www.avrfreaks.net/forum/xmega-handheld-programmer

Atmel Logo

Atmel EDBG-based Tools Protocols
Introduction

EDBG interface overview

http://www.atmel.com/webdoc/protocoldocs/ch01s01.html

...

mEDBG is a scaled-down EDBG implementation and does not support the DGI.

DGI is Data Gateway Interface.

 Atmel Logo

Atmel EDBG-based Tools Protocols
Introduction

Atmel EDBG-based tool implementations

http://www.atmel.com/webdoc/protocoldocs/ch01s02.html

...

EDBG implementations are very limited subsets os this protocol which support the particular Atmel controller mounted on that board.

"Dare to be naïve." - Buckminster Fuller

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

Hi gchapman ,

 

Thanks for the insights!

 

> more RAM

 

384 KBytes FLASH, 8 KBytes boot section, 4 KBytes EEPROM, 32 KBytes internal SRAM

 

The applicaiton is largely stateless, so there is little need for RAM.

Data is colelcted (about 256 bytes) every 100 ms and directly shipped over the USB.

There is a little analytics to do, but that requires very little memory.
Most of the RAM will go for USB buffers and management, libraries, stack, heap and such.
I doubt there is 1 KB of applicaion data, including all of the OS services (e.g. stack, timers, counters, et cetera).

 

The code is not that rangey... it could be tens of pages... maybe unrolling loops could get larger, but relative to the FLASH, tiny.

 

> more pins

 

The Atxmega384c3 is tight on pins, actually an exact match.

But there is a way to steel pins, so there are options if there are unexpected issues.

 

> ATMEL ICE

 

It looks like that is the way to go, for access to the PD bus.

 

It seems that a USB dongle could be programmed to talk PD/TWI...

 

> XMEGA eval boards

 

Thanks for the pointers.

 

> first bring-up

 

I assume that the Studio 6 over PDI can configure the boot block and there is boot code available - somewhere.

 

Is the PD bus comparable to the functionality of the JTAG?

 

Many Thanks!

Last Edited: Tue. Jan 30, 2018 - 06:51 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yes PDI offers pretty much the same as JTAG just using a different form of signalling. 

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

Trivet wrote:
It seems that a USB dongle could be programmed to talk PD/TWI...

 

> XMEGA eval boards

 

Thanks for the pointers.  I have been looking at them for clues.

MattairTech has a USB dongle-sized PDI/mulitool, and, multiple XMEGA boards.

Trivet wrote:
> first bring-up

 

I assume that the Studio 6 over PDI can configure the boot block and there is boot code avaialble - somewhere.

Atmel Studio, and, yes the bootloader is "somewhere" in Atmel Gallery (one possible bootloader there), ASF, or in one (or more) Atmel Studio projects for an Atmel board.

The Mattairtech XMEGA C3 board's web page contains a URL for a DFU bootloader and a URL to the Atmel app note.

Atmel has several XMEGA bootloaders (application notes with code).


MattairTech LLC

  • Home /
  • Development Boards /
  • ZeptoProg II USB AVR Programmer and Multitool (AVRISP mkII compatible, ISP/PDI/TPI)

https://www.mattairtech.com/index.php/development-boards/zeptoprog-ii.html

"Dare to be naïve." - Buckminster Fuller

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

Got into the EVK1100 and found the preloaded demo working,

the USB storage drive and web applicaiton work fine.

 

Studio 6 does not see a debugger over USB or Ethernet.

Is there a debug target that comes with the kit?

If so, what is involved with getting it going?

 

Thanks!

Last Edited: Fri. Aug 11, 2017 - 09:33 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Trivet wrote:
Is there a debug target that comes with the kit?
No.

Trivet wrote:
If so, what is involved with getting it going?
JTAGICE3 or, IIRC, the complete Atmel-ICE kit (will need the 10pin capability; newest debugger); JTAGICE mkII would work though more expensive and/or more difficult to find in-stock (it's essentially replaced).

If you need NanoTrace then that should do it; if you need buffered or streamed trace then AVR ONE! instead, thru the NEXUS connector, and IAR EWAVR32 instead of Atmel Studio.

fyi, UC3A is an older revision UC3; UC3C and UC3L are the current revision UC3.

Ideally the UC3A0 has a pre-installed USB DFU bootloader so Atmel FLIP or dfu-programmer should work for ISP though not for debugging.


Atmel Logo

EVK1100
Microcontroller's interfaces

JTAG

http://www.atmel.com/webdoc/evk1100/evk1100._jtag.html

 Atmel Logo

Atmel Studio
Supported Devices

AVR UC3

http://www.atmel.com/webdoc/atmelstudio/supported.devices.AVR.UC3.html

"Dare to be naïve." - Buckminster Fuller