ATTINY416-XNANO mEDBG

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

Hello, 
I'm back again with my problems.

I dare quote: "The onboard debugger can be completely disconnected from the ATtiny416 microcontroller and it can be used to program other UPDI devices."
Sounds good, but something is wrong.
The drop-down list contains only ATtiny416. I can change "Device" to ATtiny412 by keying, but this attempt does not lead to success, and when programming I get the error message:
"Cannot execute empty custom programming tool command. Please provide a command to execute and try again."

 

 

 

 

This topic has a solution.

The truth is more important than the facts.

Last Edited: Wed. May 27, 2020 - 04:35 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

what is the ATpack version you are using ?

 

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

 

 

The thread title says "attiny416-xNano"

 

Are we saying that this is an Xnano board that claims to be 416 but has been built with a 412 (as identified by UPDI read) then ?

 

EDIT: now confused further. 416 datasheet says:

 

 

Yet your picture shows:

 

 

so 1E 92 23 does indeed look like it is not a 416 ?!?

 

 

Last Edited: Tue. May 26, 2020 - 02:26 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Moe123 wrote:

what is the ATpack version you are using ?

 

Sorry, where can I find this information?

 

 

 

Atmel Studio 7, installed last week.

 

The truth is more important than the facts.

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


See my previous EDITs in #3 and also:

 

 

So if UPDI has read 1E 92 23 as the picture seems to indicate it does appear to have found an ATTiny412 not an ATTiny416 !

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

poftamunk wrote:
"The onboard debugger can be completely disconnected from the ATtiny416 microcontroller

So have you done that?

 

it can be used to program other UPDI devices

But only after you have done the previous step!

 

EDIT

 

Thread from a while back on using an onboard mEDBG for off-board debugging:

https://www.avrfreaks.net/forum/low-cost-debugger-xplained-kits

 

 

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: Tue. May 26, 2020 - 02:34 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:

So if UPDI has read 1E 92 23 as the picture seems to indicate it does appear to have found an ATTiny412 not an ATTiny416 !

 

ATtiny412 is identified as ATtiny412. Is it not OK?

The truth is more important than the facts.

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

poftamunk wrote:
ATtiny412 is identified as ATtiny412. Is it not OK?
Yes but your thread title lead me to believe you were trying to use an Attiny416 XNano. I would kind of hope an ATtiny416 Xnano might have an ATtiny416 CPU on it, not an ATtiny412. YMMV.

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


I remember what brought me here to freaks the first time was the issue with AS7 detecting the wrong device and it was the same problem with tiny412.

 

so I suspect its the same problem if you have an old AT pack.

 

@OP: please check this thread

https://www.avrfreaks.net/forum/...

 

You should be able to update your pack here:

 

if you want to do it manually, you can find the latest packs here:

http://packs.download.atmel.com/

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

I suspect you have an older version with the wrong device signature bug,

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

clawson wrote:
Yes but your thread title lead me to believe you were trying to use an Attiny416 XNano.

Yes, but I think he's trying to use it to program a separate target - which is not a '416 ?

 

EDIT

 

So, if he's still getting the signature of the 416, that could be because he's still talking to the on-board 416 - not the off-board 412 ... ?

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: Tue. May 26, 2020 - 03:20 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
 Yes but your thread title lead me to believe you were trying to use an Attiny416 XNano.

Indeed, the title is too brief. Sorry.
It has to do with the mEDBG of the XNANO, not with the ATtiny416.

 

 

Moe123 wrote:

You should be able to update your pack here:

 

 

What I have to do?

 

 

The truth is more important than the facts.

Last Edited: Wed. May 27, 2020 - 04:31 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

poftamunk wrote:
What I have to do?
Click the [Install] button to the right of the top line. That will install Tiny pack 1.4.310

 

BTW when you look down that list doesn't the comment against 1.3.229 look interesting? !

 

(EDIT: oh, wait a minute, it's saying that is the one you currently use !)

Last Edited: Tue. May 26, 2020 - 03:49 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
 Click the [Install] button to the right of the top line. That will install Tiny pack 1.4.310

OK.

 

 

 

There is still only ATtiny416 to select.

 

What's next?
 

 

 

 

The truth is more important than the facts.

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

poftamunk wrote:
What's next?

Are there any more detailed instructions in the User Guide ?

 

 

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: 1

Hello,

 

try to go in that menu in Atmel Studio : 

 

Tools (Main Menu) -> Options ... -> Tools -> Hide Unsupported Device -> False

 

then you will be able to choose another device in the progamming interface, than the one initially configured in the xnano board.

 

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

Ah, yes - previously, on AVRFreaks:

 

https://www.avrfreaks.net/commen... - and following posts.

 

 

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

fgras78 wrote:
Hello,

 

try to go in that menu in Atmel Studio : 

 

Tools (Main Menu) -> Options ... -> Tools -> Hide Unsupported Device -> False

 

then you will be able to choose another device in the progamming interface, than the one initially configured in the xnano board.

 

That's more like it. Now the MCU is automatically identified:

 

 

 

But programming doesn't succeed:

 

 

 

The truth is more important than the facts.

This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 2

In your project, you have chosen to execute a custom command instead of using the Tool... It's under Tool in your project properties.

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

meolsen wrote:
In your project, you have chosen to execute a custom command instead of using the Tool... It's under Tool in your project properties.

 

Salvation!

 

 

 

 

The truth is more important than the facts.

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

congrats!