Data visualiser

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

Heloo all,

 

Can the data visualiser work only with Xplained pro boards? I have a Atmega which is a regular chip type and works with ATMEL ICE DEBUGGER.  The problem I face is ,I cannot read the data that I have sent or received on Atmega,with the DEBUGGER. I just want to print the values received on my SPI.

 

Since the UART program is not -s-o easy , I found about the Data Visualiser. Can this be used with all type of Atmega boards.?

 

Thanks

Last Edited: Fri. Apr 13, 2018 - 11:55 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

This is a general Atmel Studio question - not specific to AVR.

 

ISTR that the Data Visualiser protocol is published somewhere - so you could implement it yourself.

 

I think that more recent versions of Atmel-ICE support the Data Visualiser?

 

 

EDIT

 

Microchip wrote:
The Data Visualizer is a program to process and visualize data. The Data Visualizer is capable of receiving data from various sources such as the Embedded Debugger Data Gateway Interface (DGI) and COM ports

 

https://www.microchip.com/avr-support/data-visualizer

 

Documentation for the Atmel Data Protocol:

 

https://www.microchip.com/webdoc...

 

The Atmel Data Protocol (ADP) is a content independent protocol intended for transferring data from a target MCU to a host PC through an EDBG based debugger (EDBG, Atmel-ICE, Power Debugger) using the Data Gateway Interface (DGI, see Embedded Debugger's Data Gateway Interface) or directly to the host computer using a serial port. ADP is content independent and the transfer through the debugger is transparent, meaning that the content is not interpreted by the debugger.

 

 

EDIT 2

 

Or perhaps it should be under 'In-System Debuggers and Programmers' ? 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
Last Edited: Fri. Apr 13, 2018 - 10:50 PM