MPLAB Snap

Go To Last Post
72 posts / 0 new

Pages

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

Gotta laugh, or cry, not sure which.

 

Meslomp, that is my thread on the MC Forum.

It is a SHORT version of my Thread about my difficulties with the SNAP.

None of the replies addressed the specific issue I have, namely the inability to download a pre-compiled .hex file to a Nano, and not also totally trash the Fuses.

 

The LONG version of difficulties with the SANP are detailed on a Freaks Thread that I hijacked, HERE.

 

Morton asked for some screen shots, so I provided a few.

I haven't hear anything back.

 

MC Support finally got back to me about my difficulty in getting my (first) Thread posted on the MC Forum.

That was a lengthy process.

 

I still can't download a pre-compiled .hex file into a Nano.

 

I gave up and moved on.

I use my AVR ISP mkII and my Atmel ICE.

 

My Stupid Non-working Avr Programmer, (SNAP for short) is just as non-functional today as it was when I purchased it.

 

I see that Cliff received some meaningful support from MC in another recent Thread of his.

Perhaps there is yet hope.

 

Perhaps not.

 

JC

 

Edit: Typo

I had a few other "S" works in mind, but this is a "G" rated Forum...

Last Edited: Fri. May 10, 2019 - 04:32 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Hello,

 

With such cheap price I couldn't resist to order one!

I had to remove the R48 as described on the snap page http://ww1.microchip.com/downloads/en/DeviceDoc/ETN36_MPLAB%20Snap%20AVR%20Interface%20Modification.pdf

I also made a small adapter to plug into UPDI pins.

With MPLAB X it works great, reading, writing (5V).

 

 

 

picture MPLAB SNAP + adapter 

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

fgras78 wrote:
With MPLAB X it works great, reading, writing (5V).

 

I bet you are using default fuses. This is no big deal for the UPDI chips, because the clock frequency is (mostly) set by software (the fuses only select 16 or 20MHz base clock). But for classic AVRs, you will quickly come across the problem that DocJC has been complaining about (to no avail so far). That is, the fuses are always auto-reset to factory default each time you upload a program.

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

I haven't removed R48 yet. Looks like that's next. Your SPI adapter is lots neater than mine. I'll check mine with an ohm meter again as it's easy to get the even and odd pins wrong when you're an autistic with spacial problems. 

 

My thread has never appeared on Microchip's forum. Perhaps shoes are required?

The largest known prime number: 282589933-1

It's easy to stop breaking the 10th commandment! Break the 8th instead. 

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

My thread has never appeared on Microchip's forum. Perhaps shoes are required?

 

Your account and first post as a newbie has to be Moderator approved.

 

For my SNAP post, (first post), it took almost a week before my post was approved.

Apparently their Moderators don't spend as much time on their Forum as our (outstanding!) Freaks Moderators do.

 

That delay is real helpful when one is trying to solve a problem...

 

Back in the day I seem to recall being told that MC/AVR was working on automatically making our Freaks log ins work on the MC site.

That, apparently, never happened.

 

JC

 

Edit.  typo and attitude...

Last Edited: Sat. May 11, 2019 - 06:32 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I decided it was about to SNAP my patience & put it aside, until I need a new dose of aggravation. 

When in the dark remember-the future looks brighter than ever.   I look forward to being able to predict the future!

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

To help deal with that aggravation, I just ordered a new Atmel-Ice.

 

"The Freaks" are probably the main reason I have stayed with AVR so long. If the new overloards wished, I would help "freak" their site.

 

Oh, yes. Here is what MPLAB says when I try to program a 4313 on the pc. Haven't tried it on the mac yet.

 

 

The largest known prime number: 282589933-1

It's easy to stop breaking the 10th commandment! Break the 8th instead. 

Last Edited: Sun. May 12, 2019 - 01:56 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0


Torby,

 

I was more thinking about this:

 

it is a post by this guy:

 

It was a rather long post were he seemed to have a couple of more tips/tricks.

I stopped reading at the first quote and did a quick scan on the rest.

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

You know. I think I saw that... I'll (forget to) try it tonight.

The largest known prime number: 282589933-1

It's easy to stop breaking the 10th commandment! Break the 8th instead. 

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

MPLAB Snap

...

50% Off - Use Coupon Code : TP1973        Expires : 30-Sep-2019

...

via Dev Tool Deals | Microchip Technology

current stock is 10895

2 week lead-time

 

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

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

Release Notes for MPLAB® Snap
In-Circuit Debugger & Device (Non-Production) Programmer

MPLAB® X IDE v5.25

__firmware__

 

August 2, 2019

 

...

 

1        Device Support

[MPLAB Snap is all beta for AVR in MPLAB X v5.25; tested (not beta) for a significant subset of PIC, PIC24, dsPIC, PIC32, and SAMS70Q19]

 

...

 

4        What's New in v5.25

·Support for AVR-mode CDC implementation on MPLAB PICkit 4 and MPLAB Snap. See Virtual COM Port for more information.

 

5        Repairs and Enhancements Made in v5.25

·SNAP-21:Verify failure on some older revs of PIC16(L)F182x/193x.

 

6        USB Port Setup

When MPLAB X IDE (v5.05 or greater) is installed the MPLAB Snap In-Circuit Debugger will automatically update any necessary device drivers upon connecting to USB.

 

7        Powering the Debugger and Target Board

The MPLAB Snap debugger derives power via a cable connected to the Micro-B USB connector and the computer. The target board must be powered from its own supply.

 

8        Setting Up the Debugger and Target Board in MPLAB X IDE

To set up the MPLAB X IDE:

1.      Launch MPLAB X IDE.

2.      In MPLAB X IDE, create or open a project with the debugger selected as the Hardware tool. The debugger will automatically connect when code is executed. (To always be connected, see Tools>OptionsEmbedded,Generic Settings, “Maintain active connection to hardware tool”.) Also, the debugger can automatically detect if it has been disconnected/reconnected and if the target has been disconnected/reconnected.

3.      The debugger will now be ready for use.

 

9        Virtual COM Port for AVR Devices

The Virtual COM Port is a general-purpose USB serial bridge between a host PC and a target AVR device.

The AVR-mode CDC implementation on the MPLAB PICkit4/SNAP Virtual COM port supports:

·Baud rates in the range 1200 bps to 500kbps

·Only 8-bit character format

·No hardware flow control

·One or two stop-bits

IMPORTANT NOTE: Connecting to the Virtual COM port from a terminal emulator will enable pins 7 and 8 on the MPLAB PICkit4/Snap header as TX and RX pins. This functionality is independent of the debugger functionality. You must ensure that you do not use CDC at the same time as a debug interface which also needs those pins, for example JTAG or SWD.

 

10    Known Problems

The following is a list of known problems. For information on common problems, error messages and limitations please see Troubleshooting in the on-line help file for the MPLAB Snap debugger.

10.1   Communications

Use a full-featured Micro-B USB cable (data and power), no longer than 1.5 meter, to connect to a computer (for example, the Microchip Part Number ATUSBMICROCABLE-XPRO). Ensure that the cables you use are USB 2.0 compliant. If you are using a hub, it must also be High Speed USB 2.0 compliant.

10.2   Tool SSRs (System Service Requests)

SNAP-48

Using MPLAB X IDE/IPE v5.25 the MPLAB PICkit 4 and MPLAB Snap ICD tools cannot program/debug the specific devices at the Vdd minimum voltage of 1.8 V (with respect to Vss). Workaround: Raise the Vdd voltage supplied to the part to 2V or higher.

AVR64DA128, AVR48DA128, AVR32DA128, AVR28DA128

 

...

 

10.3   Other Tool SSRs (System Service Requests)

The following is a list of issues that are being tracked for other tools but are related to this tool.

PK4-31

The firmware update will fail with either the MPLAB PICkit 4 or the MPLAB Snap ICD tool, when using:

- USB Full-speed port 
- USB Full-speed hub 
- USB Full-speed isolator

Workaround:

The tool would have to be plugged into a USB Full-speed or USB SuperSpeed USB port/hub/isolator to allow the firmware update process to complete successfully.

After the firmware update completes, the tool can then be plugged back into a USB Full-speed port/hub/isolator.

 

...

 

10.4   Engineering Technical Notes (ETNs)

The following ETNs are related to the MPLAB Snap in-circuit debugger. Please see the product webpage for details.

·Engineering Technical Note #36 MPLAB Snap AVR UPDI/PDI/TPI Interface Modification

 

11    Important Notes

...

 

11.2   AVR UPDI/PDI/TPI Support

A 1K ohm pull-up resistor must be installed between the MPLAB Snap ICD ICSP connector's (PCB reference designator J4) pin 4 (PGD) and pin 2 (VDD) to allow proper programming/debugging support for AVR parts that support the UPDI/PDI/TPI interface.

Note: If this 1K ohm pull-up resistor is not installed a 'PDI physical timed out. (25)' message will be issued for various operations in the MPLAB X IDE or MPLAB X IPE GUI.

 

...

 


MPLAB Snap (on sale at 50% thru 30-Sep'19, get two so one has ETN 36, get three if simultaneous debugging and USB CDC ACM)

ETN36_MPLAB Snap AVR Interface Modification

MPLAB® SNAP AVR UPDI/PDI/TPI Interface Modification

https://www.microchipdirect.com/product/Other?keywords=ATUSBMICROCABLE-XPRO

 

edit :

MPLAB X IDE | Microchip Technology

 

edit2 :

MPLAB® Snap Additional Items Needed - Developer Help

 

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

Last Edited: Tue. Aug 6, 2019 - 10:42 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Question about VTG: I'll only be using a SNAP for the new 0- and 1- series tinyAVRs (402/817 etc) over UPDI. For my PICs, the PICkits could supply 5V to the target and things were easy, but the AVRs require external power. Since the SNAP PCB is exposed, can I simply connect the VTG pin on the connector with the 5V line coming from the microUSB port so that the target AVR gets powered by the USB bus? I understand that the SNAP will always read and get a target voltage whenever it checks, but are there any other issues which would make this not work (or do something worse)?

-Sam

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

VTG is a level sensing input. It's so the programmer/debugger can adapt its other signals to either 3.3V, 5V or other Vcc levels.

 

Just build your circuit with it's normal power supply and power as the eventual device will then attach the debugger to that and it will adapt.

 

To power it I guess you could just run a cable from a second USB port on the PC and use the two outer lines which are 0V and 5V. Just don't try to pull more than 100mA.

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

Thanks clawson. I understand the VTG pin function, however my boards will only be 5V circuits, so I could do without the whole level shifting shebang. I'm sure there are better ways to get my target powered (like the USB thing you suggested), but do you think there is a problem if I feed the target power from the microUSB 5V via the VTG connector pin? In my (admittedly limited) knowledge, it would just be the same as powering it externally through another USB port, except that the SNAP would always sense 5V on the VTG pin, even when there is no target connected. Would that cause any issues with programming? 

-Sam

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

I don't see how that can be a problem, it would be like VTG is permanently connected to the target's VDD. It shouldn't cause any damage.

 

Edit: in fact the snap has mounting holes marked 5V0 and a 3V3 it should be easy to wire to VTG.

Last Edited: Tue. Aug 13, 2019 - 03:22 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I've done something similar on my dragon debugger, wiring the vcc to vtg pin, works fine, however there is always the danger of connecting it the first time to an unknown board that has a vcc/gnd short somewhere and either damaging the snap or worse the USB port in your PC!!!   You have been warned. 

 

Jim

 

Click Link: Get Free Stock: Retire early! PM for strategy

share.robinhood.com/jamesc3274
stack gold/silver https://www.onegold.com/join/713...

 

 

 

 

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

Jim, good to know you've done it and it works. Your warning is good advice, I guess that's a chance I'll have to take. (I also usually test a board's power supply before connecting a programmer). Plus most computers I've had this issue with have shut the USB port down as soon as an overcurrent was detected.

-Sam

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

Friday Free Board Quiz – Week #92 prize is USB isolator | olimex

[picture then first paragraph]

USB-ISO is galvano isolator of your PC USB port with 1000VDC isolation. It’s must have device if you deal with Arduino prototype boards as in case you wired something wrong you can burn your PC or laptop USB port. USB-ISO will protect it. Also lot of people use USB-ISO for Audio DAC ground loop isolation.

via https://olimex.wordpress.com/?s=USB-ISO

 

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

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

samay wrote:
Plus most computers I've had this issue with have shut the USB port down as soon as an overcurrent was detected.
That can literally be blown through; one way is by mis-wire.

Protect Equipment with USB Isolators - B&B Electronics

... and its leads [hot, neutral, or ground] had been reversed to keep it [machine] from tripping a GFI switch. As the laptop and the connected device now had different ground potentials, the USB cable became the path to a lower ground state. It was an expensive lesson.

...

Southwire Southwire 120V AC Receptacle Tester at Lowes.com

 

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

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

Good morning,

 

I've bought the Snap recently and modified it a bit, shorting the USB 5V to VTG. 

But for one project i need a programmer with HV-UPDI, so i've started another project to make an adapter:

 

 

The component values are yet temporary, probably will need some tweaking to work properly.

My idea was to measure the UPDI signal from Snap, and when the programming starts, send a generated 12V to target.

The generator is a simple voltage multiplier with 5V and 12V zener diodes for protection.

The attiny5 generates alternating signals to the generator.

My plan was to NOT remove the updi pull-down resistor and instead add a 1k pull-up, then measure the levels with adc.

From what i've probed the updi line sits a bit under 4V idle and rises to over 4.5V for about 2.5ms, so after detecting a 1ms of over 4.5V the attiny5 will open the 12V output for about 1ms.

It would be simpler by just removing the pull-down, but i didn't want to modify the Snap too much. 

 

 

I've also added a jumper to connect the generated 12V directly to RST for HV-TPI programming.

Removing the jumper disconnects the 12V output. 

 

Now i wonder, does this circuit make sense so far? 

Should i change or add something?

 

Thank you.

 

edit: Updated the bottom layer.

Last Edited: Fri. Aug 16, 2019 - 11:18 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well, maybe it will work, depends on how much time you have from when the snap sends the UPDI enable signal until it sends the first programming signals.

Seems a good idea to me.

 

Pages