ATTiny1616 Pickit4 12V programming does not work

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

I am trying to program an ATtiny1616 with a Pickit4 progammer. In "standard" mode everything works, but I cannot get it to output a 12V programming pulse, see screenshot. The programming sequence on an attached scope looks exactly the same with and without 12v option.

 

What am I doing wrong? Or is my brand new Pickit4 programmer defective?

Attachment(s): 

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


You're best bet is probably Microchip technical support...

 

 

#1 This forum helps those that help themselves

#2 All grounds are not created equal

#3 How have you proved that your chip is running at xxMHz?

#4 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand." - Heater's ex-boss

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

That's an interesting table. Could you post a link? I did not find any compatibilty information on Microchip's website.

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

Download and unzip the release notes for the version of the toolchain you are using. You'll find it in there called "device support.htm"

#1 This forum helps those that help themselves

#2 All grounds are not created equal

#3 How have you proved that your chip is running at xxMHz?

#4 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand." - Heater's ex-boss

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

drei wrote:
Or is my brand new Pickit4 programmer defective?
No (incomplete firmware)

https://www.avrfreaks.net/forum/attiny416-series-1-fuses#comment-2726491

 

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

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

Next question. I have a Power Debugger that I bought end of 2017 but never used. Now when I try to connect it it is recognized by Atmel Studio but nothing works, even the LEDs stay dark. The firmware version displayed is 1.36. According to Microchips's product page the latest version should be 1.45. Where do I get this version and how do I perform an upgrade? Atmel Studio is configured to check firmware, but nothing is offered.

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

If the LEDs on the Power Debugger is dark, then is it actually connected? (I.e is it visible in Studio or in the Device Manager?)

:: Morten

 

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

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

Yes. I get this device information from within Atmel Studio:

 

Power Debugger
Debug host        127.0.0.1
Debug port        57131
Serial number     J51800000176
Connection        com.atmel.avrdbg.connection.cmsis-dap
Firmware Version  1.36
Hardware Version  1

Last Edited: Sun. Aug 4, 2019 - 04:06 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Normally, Studio I will do a upgrade automatically. You can force it by going to view/available tools and right click on the power debugger and select upgrade.

:: Morten

 

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

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

There I get: Power Debugger is up to date, firmware version on tool 1.36, on disk 1.36.

 

I know that I have 1.36 on disk, it is in one of the more or less undocumented Atmel Studio subdirectories. I still do not know where to download the claimed latest version 1.45. No download is offered. This probably is the culprit, there is no download from within Atmel Studio, it only offers the built-in outdated version.

 

This is all very confusing.

 

Edit: just out of curiosity I have started an upgrade process. The "upgrade" is performed in multiple steps, apparently different parts of the debugger are programmed. I finally get the message "debugger firmware successfully upgraded", version is still 1.36, still not working.

Last Edited: Sun. Aug 4, 2019 - 05:41 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Where did you see that there is a 1.45 version?

:: Morten

 

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

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

https://www.microchip.com/webdoc/GUID-EAD481FD-28E6-4CD5-87FB-5165E7687C12/index.html

 

Firmware release history:

 

1.45 29.09.2016

Added support for UPDI interface (tinyX devices)

Made USB endpoint size configurable

General bug fixes

 

According to this list 1.36 should not even support UPDI.

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

Hihi, the table lists decimal versions while Studio uses hexadecimal versions (36 = 54)

:: Morten

 

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

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

But, what issues are you seeing with the Power Debugger?

:: Morten

 

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

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

Ok, so now I have:

 

1. A power debugger with latest firmware that never worked.

2. An ICE debugger with 12V option mentioned in the programming software, but not implemented.

3. A Pickit4, still in beta support state, waiting for an update.

 

Is there any third party solution that supports 12V programming?

 

But, what issues are you seeing with the Power Debugger?

 

As mentioned, all LEDs black, error message when trying to connect to target. Only current and voltage are displayed in Data Visualizer.

Last Edited: Sun. Aug 4, 2019 - 07:21 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What doesn't work with the Power Debugger then?

:: Morten

 

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

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

meolsen wrote:
What doesn't work with the Power Debugger then?

 

Sorry, I have been too slow, see above.

 

Error message when trying to read signature:

 

Failed sending command/receiving response. Command ID 0x10. Failed sending CMSIS command from AtmelDapTransport

Unable to enter programming mode. Verify device selection, interface settings, target power, security bit, and connections to the target device.

 

Details:

 

Timestamp:    2019-08-04 21:25:49.768
Severity:        ERROR
ComponentId:    20100
StatusCode:    1
ModuleName:    TCF (TCF command: Device:startSession failed.)

Failed sending command/receiving response. Command ID 0x10. Failed sending CMSIS command from AtmelDapTransport

 

I have seen other forum entries where Power Debuggers have been bricked after a firmware update. I do not know if my device ever worked, there may have been an initial update that bricked it immediately. I only know that I was never able to establish a communication with the target, and the LEDs always stayed dark.

Last Edited: Sun. Aug 4, 2019 - 07:30 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Mind sharing the errors then? (And did you click the set button after checking use 12v?) Is the updi pin used as a input or output pin? Are you driving it from your application?

:: Morten

 

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

Last Edited: Sun. Aug 4, 2019 - 07:29 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

meolsen wrote:
Mind sharing the errors then? (And did you click the set button after checking use 12v?) Is the updi pin used as a input or output pin? Are you driving it from your application?

 

See above. I have tested with several processors, these are just my experiences with the target I have currently connected. I suppose the programmer is dead and possibly always was. I had the vague idea that a supposedly newer firmware version could help, which is aparently not the case.

 

I will contact Microchip support tomorrow. This weekend the support site is down.

 

Many thanks!

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

Are there any news regarding  Pickit4 and 12V programming for UPDI? It seems that Microchip has released some updates but I cannot find anything about 12V programming.

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

drei wrote:

Are there any news regarding  Pickit4 and 12V programming for UPDI? It seems that Microchip has released some updates but I cannot find anything about 12V programming.

 

I'm looking for it too

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

A placeholder :

https://microchipdeveloper.com/mplabx:avr-updi-high-voltage

 

edit : page was updated yesterday to add content

 

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

Last Edited: Wed. Oct 30, 2019 - 08:30 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

October 21, 2019
I had a chance to borrow a PICkit4, so I played around on the weekend.

 

<MPLAB X IDE V5.25 (IDE & IPE)>
There is no high voltage setting or power supply setting.

 

<Atmel Studio 7.0.2389>
When you start Dvice Programming, the item “Use UPDI high voltage activation” will appear. However, PICkit4 does not output 12V in any setting.

 

If UPDI is disabled, the debugger must also control the power supply to the chip.
Wait for the update.

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

MPLAB X v5.30 is imminent.

12V UPDI for MPLAB PICkit 4.

https://www.microchip.com/RSS/recent-software.xml

<pubDate>10/29/2019 ...

[release notes, macOS, Linux] 

 

edit :

https://www.avrfreaks.net/forum/come-join-us-mplab-now-supports-avrs?page=5#comment-2789921

 

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

Last Edited: Thu. Oct 31, 2019 - 09:20 PM