DGI not working on SAML21 XPro

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

 

Atmel Studio 7.0.2397 on Win7-Pro;

same (mis-)behaviour in Microchip Studio 7.0.2542 on Win10-Pro.

 

The SAML21 XPlained-Pro is seen:

 

but when I press 'Connect', nothing happens. The button goes down when I click it, but just comes up again immediately when I release - still saying 'Connect'

 

The 'Status' LED on the board blinks a couple of times, then goes steady-on.

 

With an ATmega4809 XPlained Pro, the button immediately changes to 'Disconnect', and is greyed-out while "searching for protocols":

 

(while 'searching', the 'Status' LED is flashing fast)

 

and then:

 

(LED steady-on)

 

 

So why doesn't this work with the L21 board?

 

I couldn't see anything on the L21 XPlained-Pro page about firmware updates or anything:

 

https://www.microchip.com/developmenttools/ProductDetails/PartNO/ATSAML21-XPRO-B

 

The info panel suggests these interfaces should be present:

 

 

 

Cross-reference: https://www.avrfreaks.net/forum/...

 

This topic has a solution.

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. May 14, 2021 - 07:25 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0


The L21 board behaves the same whether or not I check 'Autodetect protocols'.

 

On the AVR board, there also doesn't seem to be any difference:

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...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

 

 

Some progress:

 

It seems the EDBG firmware was out of date.

 

Use View -> Available Atmel Tools to see the list of tools:

 

Right-click the 'EDBG' entry:

 

'Upgradee':

 

No idea why it hadn't automatically prompted me before?

 

After the update, the board appears as a USB Mass Storage device (in addition to the COM port):

 

and as 'EDBG MSD' in the Tools list:

 

Right-click now has an extra  'Communication mode' option

 

Which gives:

 

This needs to be changed to 'DGI':

 

then the 'Available Tools' entry changes back to just 'EDBG':

 

and then it was able to connect and did recognise the DGI interfaces:

 

I haven't seen anything in any documentation anywhere - for the board, or the EDBG, or DGI, or the Data Visualisation, or the Power Debugger - that mentions this setting.

 

angry

 

But now I can connect and see a power data trace:

 

However, as soon as I try to save the data to a file, Studio crashes.

 

I did try the standalone visualiser - but it doesn't show the Power:

 

 

So we're making progress - but not quite there yet ...

 

 

EDIT

 

I don't know what's happened to all (but one) of the screenshots: https://www.avrfreaks.net/forum/where-have-all-my-pictures-gone

 

frown

 

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. May 14, 2021 - 08:15 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0


Hmm ... just noticed that my Device Manager screenshot showed COM140:

 

but the standalone Data Visualiser showed COM138:

 

 

This is correct - it seems that the change from plain 'EDBG' mode to 'EDBG MSD' causes the VCP to be seen as a different COM port number.

 

frown

 

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...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil wrote:
as soon as I try to save the data to a file, Studio crashes.

Apparently this is known:

 

Microchip Support wrote:
logging the measurement data to a file is not supported in the Data Visualizer. The data from the Power interface is a bit different from the other DGI streams. So, the Data Visualizer crashes because the data logger is not able to parse the incoming data

 

frown

 

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...
This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

So the solution to the initial problem of DGI not working at all was two things:

 

  1. Update the board firmware
  2. With the new firmware, the board needs to be in 'EDBG' mode - not 'EDBG MSD'

 

See #3 for full details.

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...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil wrote:
Apparently this is known

Latest from Support:

Microchip wrote:
Microchip Studio's Data visuzlier will not be updated in the future.

Can you please try out the Data visualizer tool in MPLAB X IDE?

This is the next-gen data visualizer tool and there is a lot of work going on currently.

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...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

in #3, I wrote:
I did try the standalone visualiser - but it doesn't show the Power:

 

 

in #6, I wrote:
Microchip wrote:

This [in MPLAB] is the next-gen data visualizer tool and there is a lot of work going on currently.

Can you please try out the Data visualizer tool in MPLAB X IDE?

Awaiting their response on the Standalone version ...

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: Wed. Jun 2, 2021 - 09:10 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil wrote:
Awaiting their response on the Standalone version

Never got a response, but there is now a version of the Standalone MPLAB Data Visualiser  which does do the power analysis, and can save data to file:

 

https://www.avrfreaks.net/commen...

 

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...