MPLAB snap to atmega328pb program and debugWIRE

Go To Last Post
116 posts / 0 new

Pages

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

No kidding, having two full versions of MPLABX on my machine takes quite a bit of space

Then just uninstall the previous one, and select to not delete the user folders. Those wille be picked up by a newer version and migrated over...

 

Yeah I noticed that it picked up on GCC from Studio about an hour after I wrote that OP.  BUT, if MPLABX detects GCC in Studio and installs from that I should be good to go then correct

Jupp, as long as you keep Studio... cheeky

:: Morten

 

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

Last Edited: Sat. Feb 23, 2019 - 11:07 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Thanks, I bought 2 Snaps, so I will mod one of them with a 1k resistor, it will be dedicated for UPDI. It seems to be working fine, but I'm not convinced the transmission speed setting is actually doing anything... needs more testing.

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

Morten,

Always good to know that you are still stalking the AVRFreaks site!

 

So I hijacked this Thread on post #7, and now on Post #54 I am still no closer to having a definitive answer to my question / problem.

 

It still isn't clear to me if the Error I listed above is "Just" a Windows 10 / USB error, or if it also reflects the fact that the M328P and M328PB are "Yellow", and not yet supported, and that when they are supported the error will likely disappear and MPLab X IPE will then connect to the chip.  (i.e. At what level is this error actually generated, Win10  to MPLab, or when the SNAP attempts to connect to the chip and answer back to the MPLab program?).

 

Follow on question, do you have any idea how rapidly support for AVR chips is being added to MPLab X?

Do I have to be a mega-quantity orderer to get the chips above added, or are they already on someone's To Do list?

(My wish list would be: M328P, M328PB, and the Xmega E series.)

 

Finally, two comments in case you didn't read the full Thread:

 

I've not had a good Out-of-the-Box experience after purchasing several SNAP's.

I've spent, literally, several 4 hour time blocks on this and haven't yet flashed an LED.

That includes 3 MPLab X downloads on two separate Win 10 computers.

 

The MC Forum, also, hasn't been user friendly, but perhaps I'm spoiled by the AVRFreaks site.

It took 2 days to have my log on approved, as my Freaks logon didn't cross over.

And I think I'm on day 3 awaiting a MC Moderator to approve my first question / post on the MC Forum.

I guess none of the moderator's over there work weekends, again pointing out how fortunate we are on the AVRFreaks site.

 

The marketing promo's for the SNAP on the MC web site are clearly very mis-leading...

They clearly state that MPLab now supports AVR's...

It isn't until one delves deeper that one learns that the actual support is currently minimalistic at best.

 

I'm glad to hear that the AVR Flash, (Edit: Should be Atmel Ice, my mistake), programmer works with MPLab X.

But if I wanted to use my Flash programmer I wouldn't have purchased the SNAPs...

 

If I was a professional developer and I'd lost a week's time on this, as a newbee to MicroChip, I'd be looking elsewhere.

 

Sorry I'm not able to report success and a great experience, but I have to tell it as I see it from the end customer perspective.

 

Jay Carter

Last Edited: Sun. Feb 24, 2019 - 11:57 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

But did you try to set the protocol to something other than AVR, then back to AVR? It worked for my tiny1616.

At first, I was getting the same error you mentioned in #23.

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

It looks as if El Tangas and ajc are the only "users" so far!    The SNAP has been on the market for 6 months !

 

I don't see a pullup as being a deal breaker for UPDI.    I could just add a jumper to my home made adapter.

 

Has anyone managed to run an IDE or IPE session with a SNAP with JTAG, PDI, ISP, TPI, ... yet?

Has anyone managed with PIC18, PIC24, PIC32, ... yet?

 

I am intrigued.    Perhaps I will buy a SNAP to see for myself.

 

@Jay,

Atmel tools were "unusable" for several periods in the life of AS6 and crap USB drivers.

At least AS7 seems to be operational.

 

David.

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

It still isn't clear to me if the Error I listed above is "Just" a Windows 10 / USB error,

It is a USB error... 

 

or if it also reflects the fact that the M328P and M328PB are "Yellow", and not yet supported,

Yellow means beta. For AVRs, that means that everything should work, but we haven't done in-house testing to verify that specific part yet. For instance we fixed a bug relating to devices that has a different ISP page size than its real page size between 5.10 and 5.15. Also one issue with PDI on XMEGAs with large page sizes hung the PK4 firmware in 5.10 which is fixed in 5.15.

Follow on question, do you have any idea how rapidly support for AVR chips is being added to MPLab X

Per now, every AVR in Studio is supported by MPLAB. There are some issues with HW, like the pull up needed for Snap for UPDI, and some TPI stuff on Snap, but for the most part all the Atmel tools (Atmel-ICE, EDBG, mEDBG, Power Debugger) are working.

 

I've not had a good Out-of-the-Box experience after purchasing several SNAP's.

I've spent, literally, several 4 hour time blocks on this and haven't yet flashed an LED.

That includes 3 MPLab X downloads on two separate Win 10 computers

I can't really explain that. The error is a USB error returned by the USB stack in MPLAB.

 

They clearly state that MPLab now supports AVR's...

It does...

 

 

:: Morten

 

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

Last Edited: Sun. Feb 24, 2019 - 08:52 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Same hassle everytime when update the firmware under Linux. Needs multiple runs of mplab_ipe to succeed. But when done, simple debugging with v5.15 and snap works. Target is a Tiny1614. But a 1k pullup to overwrite a 4k7 pulldown isnt very elegant. I built an adaptor with a current-source based on a BCV62 on it. When modifying my snap, i would replace the pulldown by a pullup.

Attachment(s): 

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

El Tangas

Yes, I saw that approach mentioned above and gave it a try, unfortunately without success.

 

David,

I actually bought three of them, in total.

I was looking for a simple Windows user interface, and programmer, to give to someone for a project I'm over-seeing.

(The AVR Flash connector is very fragile, and I hate to give away my ARV ISP mkII, it is my workhorse!  The SNAP seemed like a good solution.) 

I'd gladly drop one in the mail to you, but I expect the postage would be more than you picking one up locally.

 

Morton,

Thank you for the update.

Perhaps I'm being overly perturbed and cynical, if the MPLab X and SNAP actually work for AVR's for most people, and I'm an isolated problem case.

That said, I'm just reporting my experience, and looking for a working solution.

 

My primary system is a Dell desktop with an Intel i7, 920, 2.67 GHz, with 8 cores, running Windows 10 Home, (V1803 OS Build 17134.590).
Device Manager with the SNAP plugged in:

Microchip Tools

Microchip WinUSB Device

This device is working properly.

Driver:

Microchip Technology, Inc.

Driver Date: 3/20/2018

Driver Version: 1.0.0.8

Digital Signer: Microchip Technology, Inc.

Driver Management concluded the process to install driver mchpwinusbdevice.inf_amd64_875121ba87e95050 for Device Instance ID USB\VID_04D8&PID_9018\BUR183075981 with the following status: 0x0.

 

As I mentioned above, the MPLab X IPE fills the tool box with SNAP and the boards serial number.

So, again as questioned above, either the USB connection worked and MPLab queried the SNAP and (correctly) received a reply over the USB link, or MPLab simply read it from a Windows USB device table, and then failed to make the connection, in spite of Windows thinking it installed the driver without a problem. 

 

On a side note my AVR Flash, (Edit: Should be Atmel ICE, my mistake), and AVR ISP mkII both work fine under Studio7....

 

Morton, know that I certainly don't expect you to troubleshoot the above.

But I've provided it here in case others are reviewing the Thread, particularly if they experience a similar problem, or perhaps can report success with a different USB driver.

I've also provided it so that if you elected to do so you could pass a link to the Thread, or copy/paste the above, to whomever troubleshoots such issues.

It likely isn't all the info needed for problem identification, but is perhaps a start.

 

NetOger,

Sorry, I'm not running Linux, so no comments or experience in that regard.

 

JC

 

Last Edited: Sun. Feb 24, 2019 - 11:57 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

So, again as questioned above, either the USB connection worked and MPLab queried the SNAP and (correctly) received a reply over the USB link, or MPLab simply read it from a Windows USB device table
.
We do the latter... So your error comes the first time we actually connect...

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

DocJC wrote:
David, I actually bought three of them, in total. I was looking for a simple Windows user interface, and programmer, to give to someone for a project I'm over-seeing. (The AVR Flash connector is very fragile, and I hate to give away my ARV ISP mkII, it is my workhorse! The SNAP seemed like a good solution.) I'd gladly drop one in the mail to you, but I expect the postage would be more than you picking one up locally.

It is too late for me to order a SNAP from Farnell this evening and get it on Monday.

 

If the topic remains "interesting" I will order at 18.00 on Monday.    Receive it on Tuesday morning.

 

What is "AVR Flash"?   I presume you mean ATMEL-ICE

 

David.

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

My mistake, yes, I meant Atmel Ice.

 

JC

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

All of this sounds so complicated.  I thought my $20 AVRISP MKii from China, and my $50 ICE from Atmel would keep me happy with my Windows 7 machine and Atmel Studio 7 for the rest of my life.  Someone pointed out some of those may not last the rest of my life, and right away I dropped the AVRISP and it stopped working, so I ordered another one from China for $13.  In the meantime, my ICE is flawless.  I just like to use the AVRISP to save wear and tear on my ICE.

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

I bought these Snap things because they are cheap and can program and debug almost everything from microchip (PIC/AVR/ARM). Maybe too good to be true?

They have several glitches but are usable to me, so given the price I really have no complaints.

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

DocJC wrote:
(The AVR Flash connector is very fragile, ...
Tag-Connect has Atmel-ICE product that will pitch convert with strain relief on the end that gets worked a lot; otherwise, the pitch converters in several threads here.

DocJC wrote:
... and I hate to give away my ARV ISP mkII, it is my workhorse!
Ain't Atmel AVRISP mkII great?

Apparently twice the drive of an Atmel-ICE.

IIRC, the ones at Waveshare make the AVRISP2 clone.

Dean's LUFA AVRISP2 has several manufacturers.

STK500v2-compatibles are many.

If for a unified memory AVR (UPDI) then there's the few very low price alternatives to programming by Atmel-ICE.

 


http://www.tag-connect.com/search/node/Atmel-ICE

 

OSH Park ~ AtmelICE Adapter

50-100mil Adapter allows you to connect a mikroProg for STM32 programmer and hardware debugger to a Cortex debug connector

PinBoard 1.27mm to 2.54mm Cable Converter for Zigbee Bluetooth Emulator Download | eBay

Proto Advantage - Dual Row 1.27mm Pitch 10-Pin to Dual Row 2.54mm Pitch Adapter

Proto Advantage - Dual Row 1.27mm Pitch 10-Pin Male Header to DIP-10 Adapter

Atmel ICE header adapter

most of the above are due to posts here :

Atmel ICE custom cable part numbers for you. | AVR Freaks

https://www.avrfreaks.net/forum/ice-header-adapters#comment-1877541

https://www.avrfreaks.net/forum/atmelice-rats#comment-2026396

https://www.avrfreaks.net/forum/avr-dragon-vs-avr-ice#comment-2095001

https://www.avrfreaks.net/forum/does-mega1284p-xplained-board-work-atmel-icess#comment-2485006

https://www.avrfreaks.net/forum/atmel-ice-pin-out#comment-2523716

 

USB AVRISP XPII - Waveshare Wiki

WaveShare | eBay Stores - AVR - Programmers/Debuggers

 

Four Walled Cubicle - AVRISP-MKII Clone (function-like; Waveshare may have the compatible USB bridge that was what EOL'd Atmel AVRISP mkII)

 

Pololu USB AVR Programmer v2.1

 

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

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

MarkThomas wrote:
I thought my $20 AVRISP MKii from China, ...
I'm so glad (scary?) you have that mind connection with the ones of China. cheeky

MarkThomas wrote:
... and right away I dropped the AVRISP and it stopped working, ...
Sorry about that.

MarkThomas wrote:
... so I ordered another one from China for $13.
surprise (to continue that price flow, by UPDI would be very inexpensive)

 

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

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

MarkThomas wrote:
I just like to use the AVRISP to save wear and tear on my ICE.

 

What about anlank2's little programmers?  They work great!

 

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

 

I have several of them and they are certainly easy to use.

 

Jim

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

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

westfw wrote:
(I'd recommend an Xplained Mini.)
arrived 21-Feb'19 :

MPLAB® X IDE - Debugging with debugWIRE for AVR® MCUs - Developer Help

 

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

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

Does the SNAP work with Atmel Studio, or only MPLab?  I am resistant to changing away from AS.

 

The ICE does seem to have a weak USB connector.  As other folks have done, I have my ICE mounted on a piece of foam core with the USB cable zip tied down to remove stresses on the USB connector.  I love the ICE, and it works perfectly for all the mega's I use.  It was only $50 when I bought it from Digi-Key.

 

I looked at Xplained Mini, and they come in various flavors of ATmega's, but not the ATmega1284P, which I use a bunch of.  Will any Xplained Mini work as a general purpose programmer/debugger for any mega?

 

jgmdesign wrote:
What about anlank2's little programmers?  They work great!

What is all the EEPROM for?

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

18.00 arrived.   I have ordered a SNAP from Farnell.   I will report back when it arrives.

 

You can make a programmer out of almost anything.    e.g. Uno, Nano, Pro Micro, ...

Or you can program different firmware into a USBASP.

 

It all comes down to something that is convenient and easy to use.    For example,   programming PICs with a HEX that is stored in the PICklit memory.

Alank's can program from stored HEX.

The AVR Butterfly could program from different HEXs stored on the DataFlash chip. 

 

The PICkit mates nicely with a 8x1 or 7x1 male header on a PIC target pcb.

AVR targets tend to use 3x2 or 5x2 which need a ribbon cable. 

 

What you end up using the most is the best programmer for you.

 

David.

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

david.prentice wrote:
What you end up using the most is the best programmer for you.

Too true, David.  I'm hooked on the AVRISP mkII and the ICE.  It would be easier to solder 8x1 or 7x1 headers than the 3x2's I use on my boards, but I am getting pretty good at it.

 

I'm wondering how long the new Chinese AVRISP will last.  All the vendors on AliExpress have a different version from what they used to look like.  There is a 10 to 6 adaptor that plugs into the 10 pin connector to use with the usual 3x2 programming header.  It says it works with AS7.  We will see.

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

Does it appear as an AVRISP-2 e.g. abcminiuser's firmware

Or does it appear a STK500 on a COM port?

 

The AVRISP-2 clone should support ISP, PDI, TPI, ...

The STK500 clone probably only supports ISP.

 

It really comes down to a pleasant looking case,   robust USB connectors,    robust 3x2 or 5x2 ribbon connectors.

But if you do break it,   you can create your own with Uno, ...

and buy a replacement for your favourite.

 

David.

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

david.prentice wrote:
Does it appear as an AVRISP-2 e.g. abcminiuser's firmware

When I plug it in a new menu item called Atmel appears in the device manager, and when I expand it it shows an AVRISP mkII.

 

To top things off, I opened the case and wiggled the ribbon connector and now it works fine.  So I guess I will have a spare when the new one comes from China.  Seeing as how i will have two, this one will probably last forever.  O well.  I like the things for programming, and I use the ICE for debugging.  The two Chinese versions I bought were together still cheaper than the original Atmel item I got from Digi-Key years ago.

 

It looks like only enterprise users with sufficiently deep pockets will be able to get the Windows 7 updates for another 3 years after next January.  Us little users will be forced to upgrade to Win 10, or go offline.  Since I use Dropbox for backup, I will need to get external storage for my Win7 machines where I do my software development if I go offline.

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

I ordered at 18.00 on Monday.  The SNAP arrived at my door at 11.00 on Tuesday.

 

I have wasted several hours.   I have not been able to get the SNAP to work at all.   The USB comms fails.

 

PICkit4 and ATMEL-ICE work just fine.    Whether JTAG, ISP, debugWIRE, ...

Surely the USB comms is exactly the same for PICkit4 or SNAP.   One works and the other fails.

Tried with Win10-64 Desktop PC and Win7-32 Laptop PC.

 

David.

Last Edited: Tue. Feb 26, 2019 - 09:59 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You are getting the "Error code -10121" thing, too? I'm not sure why, but one of my Snaps started working eventually (the other one, I didn't power it up yet). At first, I thought it was because of me changing targets between AVR/PIC/ARM, but probably just a coincidence.

Last Edited: Tue. Feb 26, 2019 - 10:15 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

El Tangas wrote:

Error code -10121

 

Does it help to know that -10121 in hex is 0xD877?

 

--Mike

 

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

Yes,  I got lots of "Error code -10121"

 

I tried changing targets and interface protocol with no effect.

 

I am sure that the solution is trivial.    After all,  the SNAP has been on the market for 6 months.

It behaves the same in MPLABX 5.10 too.

 

Likewise,   I am sure that when it is working in MPLABX support for SNAP could be added to AS7.

 

David.

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

Hi David,

 

Thank you for giving it a try.

It makes me fell better to know I'm not just doing something crazy stupid.

 

El Tangas,

Did you get it working under Windows, (or Linux, or Mac)?

By got it working, do you mean you have successfully downloaded a .Hex file to an AVR chip while connected to a Windows 10 PC?

 

I have my first post on the MC Forum, SNAP Sub-Forum, still awaiting a Moderator's approval to post it...

I submitted a  Support Ticket for getting my MC SNAP Sub-Forum Post approved yesterday, or the day before, I don't recall.

Needless to say that, also, has fallen on deaf ears.

Of course I am not a Fortune 500 company.

 

Not sure if Morton or any other Microchip employees are perusing this Thread or not, but I'll just mention again that one can only hope other users have / have had a better experience, mine has been depressingly dreadful... <sigh>.

 

SNAP doesn't work under Windows.

MC SNAP Forum, can't post as a new user, and can't seem to get my post authorized for posting.

MC Corporate Support, no reply there, either.

 

One week into this as a "new" MC user and still haven't flashed an LED, or made any measurable steps in the right direction.

 

On the up side, however, Morten dropped in so perhaps something good is happening behind the scenes.

And The AVR Freaks stepped in to provide assistance, (as is always appreciated!!).

 

Jay Carter

 

 

 

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

DocJC wrote:

El Tangas,

Did you get it working under Windows, (or Linux, or Mac)?

By got it working, do you mean you have successfully downloaded a .Hex file to an AVR chip while connected to a Windows 10 PC?

 

I'm using Win7 64. Yes, I flashed Hex files using both the IPE and the IDE. I was also able to use the debug feature.

I don't know why it started working, at first I was getting the same USB error. First, I tried all the USB cables I could find, then monitored the data lines on the programming header looking for any signs of life...

It started working while I was messing around with the IPE, testing all kinds of settings, etc.

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

Not sure if Morton or any other Microchip employees are perusing this Thread or not, but I'll just mention again that one can only hope other users have / have had a better experience, mine has been depressingly dreadful... <sigh>.

 

Anyone with issues should create a support case so that it can be routed to the correct people... 

 

Not sure if Morton or any other

If you keep calling me that I might just start actively ignoring instead cheeky

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

Ok, I powered up my Snap #2, and out-of-the-box, "Error code -10121". Snap #1 is still working.

 

I reproduced the way snap #1 started working:

 

1) select ATSAMC20E1A

2) press Apply

3) press Connect. Some firmware activity takes place. Some Win drivers are installed.

4) select ATtiny1616

5) press Apply

6) press Connect. Some firmware activity takes place. Some Win drivers are installed. This message should appear:

 

*****************************************************

...

Currently loaded versions:
Boot version...................1.0.0

Now Downloading new Firmware for target device: ATtiny1616
Updating firmware application...

From here on, the Snap is "cured". Worked on my 2 Snaps.

 

edit: forgot to say - this is using the IPE software.

Last Edited: Wed. Feb 27, 2019 - 12:16 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Woo-hoo.   I have just run MPLABX v5.10 and SNAP is working with JTAG and working with debugWIRE !!

 

Then tried v5.15 with the debugWIRE project.   And that is working now.

However v5.15 with the JTAG project gives:

The VDD voltage desired is out of range. It is below the minimum voltage of 1.5V.
Connection Failed.

 

I wish that I knew what was happening.   My bedtime.

 

David.

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

Well, I ordered a SNAP to try out.  I guess it should be here in a day or two.

I has essentially assumed that the SNAP was a PICKit4 with no fancy package and "limited" software, but my PICKit4 seems to work fine...

(at least I'll have a "known good" adapter/target setup to try out!)

 

 

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

Well, I'm making progress.

 

I followed El Tangas's procedure from Post #81 and MPLab X IPE v5.15 WILL now communicate with a Nano, (Using the Win 10 interface).

 

It isn't quite all correct, yet.

 

I have to Disconnect and then Re-Connect to the chip between Programming episodes.

 

MPLab sets my Nano (M328P) in Internal RC Osc at 8 MHz with with Div by 8 Fuse set, (active), so my micro runs at 1 MHz.

 

I have been through the Advanced Settings and I can SEE the "Configuration Bits", (Fuses), but I can't change them.

A pop-up says:  Editing the configuration bit setting is disabled for AVR devices"

 

WHAT?

 

MPLab RESET the Fuses, (the Clock in particular), and I don't yet see that it will let me reset it back to use the external 16 MHz Xtal!!!

 

Perhaps I just need more time with the interface, but I've played with it for an hour now.

 

I disconnected the SNAP, loaded Studio 7, and used my AVR ISP mkII to reset my Nano's clock back to the 16 MHz External Xtal.

That all worked fine, and the LED flashes @ 1 Hz like it is suppose to.

 

Now disconnect the mkII and close out of Studio 7.

 

Connect the SNAP, and re-Program the same LED Flasher .Hex file and it AGAIN RESETS THE CLOCK TO 1 MHz.

 

<><><><><><><><>

 

So, the SNAP is partially working, with El Tangas's work-around MPLab X IPE v5.15 will now talk to the AVR.

 

I'm still looking around to figurate out why it wants to reset the Fuses, and how to either disable that, or better yet tell it what I want the Fuses to be.

 

Thus far, it still isn't a working programmer for me.

I can't have MPLab defining my Clock and other Fuse settings!

 

The above testing was in ISP Mode.

I'll have to switch boards to test DW Mode, and truth be known I don't have much experience with that mode.

But perhaps it will let me set the Fuses myself???

 

El Tangas,

Nice Job on tracking down a procedure to get the MPLab X IPE to communicate with the SNAP.

 

JC 

 

Edit:

Morten, 

Sorry, I apologize.

I used to work with a Morton, and I just typed it without giving it a second thought.

 

Last Edited: Wed. Feb 27, 2019 - 03:41 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

hmmm I wonder if the next 2 cheap debuggers and programmers will be Crackle and Pop, already have Snap.....

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I have been through the Advanced Settings and I can SEE the "Configuration Bits", (Fuses), but I can't change them.

Historically, PICs set the config bits from inside the binary, using appropriate compiler/assembler directives.

You could try that with the AVR features that were added (relatively recently?)  https://www.microchip.com/webdoc/AVRLibcReferenceManual/group__avr__fuse.html

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

The IPE tool pops up this warning when you try to edit fuses:

 

Editing the Configuration Bit settings is disabled for AVR devices.

 

So it's disabled on purpose! 

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

MPLAB X v5.15, file 'Readme for MPLAB IPE.htm' 

Release Notes for MPLAB® IPE
Integrated Programming Environment

MPLAB® X IDE v5.15

 

February 20, 2019

...

(bottom)

7.14 Programming Configuration Bits of AVR and SAM Devices in MPLAB IPE

To program the configuration bits of AVR and SAM devices in MPLAB IPE, they need to be part of the hex file only. This differs from the MPLAB X IDE, where they can be programmed separately via the configuration bits memory window.

For PIC devices, however, the configuration bits can be programmed separately using MPLAB X IDE and MPLAB IPE.

 

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

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

It's here!

Mine doesn't work either:

Data transmission failed. Error code -150 returned while trying to receive USB data.

A communication error with the debug tool has occurred. The tool will be reset and should re-enumerate shortly.
Connection Failed.

This is on a Mac, using MPLAB IDE or IPE, with an ATmega328p as target, using the same setup that works fine with a PICkit4.

Sigh.

 

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

To program the configuration bits of AVR and SAM devices in MPLAB IPE, they need to be part of the hex file only. This differs from the MPLAB X IDE, where they can be programmed separately via the configuration bits memory window.

Gchapman, thank you for that post. 

I have no idea why MC thinks the SNAP is suitable for programming AVR's with its IPE.

Even with the workaround above to get it to connect USB-wise, it automatically sets the clock to 1 MHz...

 

Well, I'm still terribly disappointed.

 

The SNAP is useless when it automatically sets my board's clock to 1 MHz when using the IPE interface.

The IPE seemed to be a lot easier to navigate than the IDE, but I'll grant you I've not used the MPLab IDE before. 

 

So I spent a little while working with the MPLab IDE, and giving it a pre-generated .Hex file from another compiler, (which is my intended purpose to begin with), and I could not make it let me adjust the Fuse bits.

I kept getting some messages about ISP and DW modes, and I had great difficulty trying to get into ISP mode, which the MPLab pop up told me was necessary in order to change the Fuse bits.

 

The best solution, in my mind, would be for MC to:

1) Fix the Windows 10 to SNAP USB connectivity problem.

2) Add another option in the Advanced Mode to let the user adjust the Configuration Registers, (Fuse Bits), from within the MPLab X IPE.

 

Until then I have three paperweights sitting on my desk.

 

JC

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

Just ordered one of these as my Atmel ICE has died.

 

We'll see what happens

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut. 

Last Edited: Thu. Feb 28, 2019 - 04:23 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Tom,

 

The SNAP seems to work ok for debugWIRE and ISP (on popular AVR models)

It supports some UPDI models.   UPDI requires a hardware mod.  I have not tried UPDI because I have onboard debuggers.

 

It currently does not do JTAG on v5.15 (but ok on v5.10)

It does not do PDI on Xmegas

It does not do TPI on Tiny20/40/5/10

It does not support the PIC18F458 (that I have).    But it does do some PIC18F.

 

It looks as if the Sales and Marketing was done by Donald Trump.

 

Having said that,   I would guess that the hardware is present for JTAG, PDI, TPI, ...

We just need to wait for Microchip to release the appropriate software (and possibly firmware upgrade to SNAP)

 

Think about it.    In the Atmel era announcements would be made.   No hardware appeared for months if not years.

The SNAP appeared in real life.    Microchip have not done the software yet.

 

David.

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

david.prentice wrote:
It looks as if the Sales and Marketing was done by Donald Trump.

 

Related image

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

Snowflakes, the sky is falling..............................

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

Today in the Microchip forum MPLAB Snap Digisoles reported a solution response in two of his posts.

 

Snap. Failed to get Device ID  https://www.microchip.com/forums/m1081464.aspx

Snap error  https://www.microchip.com/forums/m1089112.aspx

 

Hi,
found the problem, so I'm adding the solution here for those that have the same error and search through this forum:
It was not a connection issue, you must use a USB hub, and all you nightmares will be gone. Smile: Smile

 

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

Interesting, but I don't think that is the real solution to the (multiple) problems.

 

This SNAP should still be able to connect directly to the USB Host chip on the PC mother board, without a hub.

 

The additional killer bug is that the SNAP resets the AVR's clock to  the internal RC clock and enables the Div by 8, so the micro runs a 1 MHz.

If I have to  run Studio and an AVR ISP mkII or Flash programmer to re-set the Fuses for the clock every time I use the SNAP then it defeats the purpose of suing the SNAP, at least for an AVR.

 

That issue, obviously, isn't related to the USB Host to SNAP connectivity issue.

 

JC

 

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

defeats the purpose of suing the SNAP

Yep, just do it....

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Hello mraardvark,

 

I appreciate the update, and it is certainly a step in the right direction.

 

Unfortunately, the SNAP still resets the AVR's Fuses to use the internal RC Osc with Div 8 active.

That makes it worthless, as I have an external Xtal on the board for a reason!

 

JC

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

Are you sure about that? It would be MPLAB that would do that, and by default MPLAB will not wrote fuses at all (unlike how it does for PICs).
.
Do you have fuses in code? Or have you used the configuration bits window? Do you have the message in the output window saying that configuration bits will not be written when you program?
.
What version of MPLAB?

:: Morten

 

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

Last Edited: Mon. Apr 8, 2019 - 12:53 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

At work today, will try to get you some details and screen shots tomorrow.

Yes, I am sure it is resetting the Fuses and the clock, it is extremely frustrating.

I had to fire up Studio and my AVR ISP mkII and reset the Fuses each time I used the SNAP.

 

I was just trying to burn a program file, .hex.

No elf, no bootloader, no fuses, no eeprom.

 

Thank you for the interest.

 

JC

Pages