Programming the Attiny1614 with Xplained Mini

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

** Found the solution in this thread :  https://www.avrfreaks.net/forum/medbg-tool-not-appearing-attiny1616-project

 

Hello all,

I am trying to use a Xplained-Mini 817 board to program an ATtiny1614 located in a bareboard, using the UPDI channel. The Atmel Studio 7 did work as charm with the AtTiny817 present in the demo board, so I disconnected the 817 from UPDI line ( that comes from the MEGA32U4) in order to have only one device on it and connected it to the ATtiny1614.

I started a new project selecting the 1614 and it is correctly build. In order to program it in the device I went to the Device Programming window and there my little nightmare started. First, there is only one device I can select (ATtiny817). I found that can write the ATtiny1614 manually (and Apply button) and the window refreshes showing the correct ATTiny1614 device signature, target voltage, etc. I can even see the communicaton at the UPDI line with my scope.

So, the Studio 7 can see my device. But, when I close this window it forgets the device and does not program it. Goes only to simulation.

In the Project Properties, tool tab, there is no mEDBG option for the debugger/programmer.

 

Therefore, I came to you guys to know if there is a way to tell the Atmel Studio 7 that it shall keep the selected device.

 

Thank you,

Augusto

This topic has a solution.
Last Edited: Sun. Aug 25, 2019 - 12:55 AM
This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thank you El Tangas.

After I had posted my question I continued to dig on old threads and found where to configure the Studio 7 to present all other devices in the mEDBG list.

It is unclear why Atmel/Microchip would make so difficult to set some things (not documented things). After all, the sole reason for someone to get/purchase a demo board is to test a design and later program the end device in the user's board. The tool must allow this as easy as possible. 

 

I have now my little 1614 running. It is a real beast for under a $1 and after 10 years away from micros (I was a long runner user of MSP430 and PICs) it is quite fun to squize lots of code in 16KB. In my gold days I wrote a complete PLC with integrated supervisor and comm protocol in 2KB. Now, 16KB seems like infinite memory.

 

Cheers,

Augusto