Microchip Summer Dev Tool Deals:
MPLAB® Snap In-Circuit Debugger/Programmer
Use Coupon Code:
TP1973
$14.95 $7.47
Jim
SNAP on sale - CHEEEEP!
Author
Message
Level: 10k+ Postman
Joined: Tue. Nov 11, 2003
Posts: 10367 View posts
Location: Bartlesville Oklahoma USA
Couldn't seem to make mine work with any chips I had. I bought another Atmel ICE.
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. 
Level: Moderator
Joined: Wed. Mar 28, 2001
Posts: 29976 View posts
Location: Sydney, Australia (Gum trees, Koalas and Kangaroos, No Edelweis, but plenty of Corona beer)
...why do you think they want to get rid of them....
Torby wrote:
Couldn't seem to make mine work with any chips I had. I bought another Atmel ICE.
Same here...
js wrote:
...why do you think they want to get rid of them....
Now Now....
JIm
js wrote:
...why do you think they want to get rid of them....
Instead of unsubstantiated comments, why not post your project? explain your problem. explain which chip.
Then solutions can be shown.
Yes, SNAP was pretty unusable with MPLABX v5.15
v5.20 worked with popular AVR chips.
v5.25 should be better
It would be nice if SNAP worked with AS7.0 but I suppose this means SNAP owners will be obliged to use MPLABX.
SNAP looks pretty good value.
Likewise Curiosity-M4809 is really cheap too.
David.
david.prentice wrote:
why not post your project?
Here, or in the Mchip forums? Post it here and no one seems to have any idea how any of it works. Post in teh Mchip forum(if you can get an account) and they treat you like trash.
david.prentice wrote:
explain your problem.
Biggest problem I have had is having to make adapters and the software/hardware do not like to talk to each other.
david.prentice wrote:
Instead of unsubstantiated comments,
I dunno David, there have been several threads here about snap, and in the end the threads seem to piddle out as usually the OP gives up.
I may start up a new project in a week or so and I'll try a SNAP I have here. I bought 5 of them(at $15.00 each) so I would like to see one of them work. Have PICKIT 4 here too that aI also dont use because of the need to buy more supplies to make adapters.
I guess my issue with all of this is that the evil empire decided to introduce the devices and it seems they deliberately made them incompatible as a drop in replacement for established tools.
I'll try again in a week.
JIm
david.prentice wrote:
... but I suppose this means SNAP owners will be obliged to use MPLABX.
Does Microchip have anything like Atmel's atprogram that could be called from Atmel Studio 7?
Level: Moderator
Joined: Wed. Mar 28, 2001
Posts: 29976 View posts
Location: Sydney, Australia (Gum trees, Koalas and Kangaroos, No Edelweis, but plenty of Corona beer)
why not post your project?
My latest project is cruising the Mediterranean sea in the next few weeks and SNAP doesn't help at all......
explain your problem
Not enough money to do more cruising, can you help please? 
Level: 10k+ Postman
Joined: Tue. Jan 9, 2007
Posts: 13199 View posts
Location: Clay County, Texas, u.S.A.
gchapman wrote:
MDB via mdb.bat
(transparency : I haven't tried this)
That would still require using MPLABX - or is that not so?
I was hoping that Microchip has a program (similar to atprogram.exe)
that AS7 could call to program a uC by using the SNAP board.
This would be similar to how AS7 can be set up to call avrdude.exe to
program an arduino.
Level: 10k+ Postman
Joined: Tue. Jan 9, 2007
Posts: 13199 View posts
Location: Clay County, Texas, u.S.A.
MPLAB X installed, MDB operator data is by standard I/O.
There's EXE for legacy debuggers at Welcome to opensource4pic | opensource4pic
gchapman wrote:
MPLAB X installed, MDB operator data is by standard I/O.
Thanks for the info.
Well, I found a command line utility somewhere in the installation path, called "ipecmd". The documentation is this file: "{install path}\MPLABX\v5.15\docs\Readme for IPECMD.htm"
Does it work with Snap? No idea, I didn't test it yet.
Level: 10k+ Postman
Joined: Tue. Jan 9, 2007
Posts: 13199 View posts
Location: Clay County, Texas, u.S.A.
Release Notes for IPE Command Line Interface
MPLAB® X IDE v5.25
August 2, 2019
...
1 Command Line Utility Defined
MPLAB IPE Command Line Interface (IPECMD) is a 32/64-bit command-line interface to the MPLAB X IDE. This interface is designed for programming devices in a production environment.
The IPECMD provides a common tool for the Microchip programming tools (see section 3). Support for the respective features is based on the programming tool selected.
Possible uses for this interface include:
·Setting up an MPLAB PM3 for stand-alone programming or a PICkit 3 for Programmer-To-Go.
·Cross-platform programming.
·Programming devices without using an IDE.
·SQTP programming.
·Environment support.
...
...
...
El Tangas wrote:
Yes
Does it work with Snap?
Refer to their respective readmes for additional information:
· MPLAB PICkit™ 4 in-circuit debugger/production programmer
· MPLAB Snap in-circuit debugger/development programmer
· PICkit 3 in-circuit debugger/development programmer
· MPLAB ICD 4 in-circuit debugger/production programmer
· MPLAB ICD 3 in-circuit debugger/production programmer
· MPLAB REAL ICE™ in-circuit emulator/production programmer
· MPLAB PM3 production programmer
· PICkit On Board (PKOB) demo boards
· PICkit On Board 4 (PKOB4) demo boards
For legacy purposes, some tool-specific command line interfaces are available:
· RealICECMD_ICD3CMD
· PK3CMD
· PM3CMD
...
10.1 Java Requirements
The IPECMD.jar is written in Java. Therefore, you will need the JRE (Java Runtime Environment) to run your script. In order to avoid conflict, please use the JRE that is distributed with MPLAB X IPE installation. You can set the environment path using the MPLAB X IPE Installation directory:
For Windows “..\sys\java\jrex.xx\java-windows\bin”
For Linux “..\sys\java\jrex.xx\bin”
For Mac “..\sys\java\jrex.xx\bin”10.2 Specifying Options
Each option must be immediately preceded by a switch, which can be either a dash “-’ or a slash “/” and options must be separated by a single space. Example:
>java -jar ipecmd.jar /P16F877 /Fc:\mycode.hex /M
or
>java -jar ipecmd.jar -P16F877 -Fc:\mycode.hex -MNotes:
·For Windows, commands and their parameters are not case-sensitive. For Linux/Mac, the file path must be case-sensitive.
·Commands will be processed according to command order of precedence not the order in which they appear on the command line.
·The program will return an exit code upon completion which will indicate either successful completion or describe the reason for failure.
...
The following IPECMD files are automatically installed in the default locations when the MPLAB X IPE is installed (vx.xx represents the version):
· IPECMD.jar – Command line utility classes (..\Microchip\MPLABX\vx.xx\mplab_platform\mplab_ipe\)
· IPECMD.exe – Application
(..\Microchip\MPLABX\vx.xx\mplab_platform\mplab_ipe\).· ipelibs.jar – Core Library functionalities (..\Microchip\MPLABX\vx.xx\mplab_platform\mplab_ipe\modules\ext\)
...
For Windows-based computers, you can use the java –jar ipecmd.jar command or use the ipecmd.exe to execute the tool.
Notes:
1. When selecting a part using the “P” option, use the following:
·For PIC devices, drop “PIC”, for example, PIC16F877 becomes 16F877
·For dsPIC devices, drop “dsPIC”, for example, dsPIC30F6014 becomes 30F6014
·For rfPIC devices, drop “rfPIC” and appended letters, for example, rfPIC12C509AG becomes 12C509
·For MCS/HCS/MCV/SST devices use as is, for example, MCS3122 stays as MCS3122
2. MPLAB PM3 specific commands are highlighted.
3. Commands are not case-sensitive. The Escape character can be either a dash ‘-’ or a slash ‘/’.
The following commands are available in the command line interface:
...
OR<Setting><Value>
AVR/SAM-related Setting
Type:
I = [Interface type]
[JTAG, SWD, UPDI, DW, ISP, TPI, PDI, HVPP, HVSP]
None
S = Speed in MHz
None
[an example below; ORI, ORS, defaults are 'None']
...
NOTE: IPECMD can be invoked using java –jar on any Windows, Mac, or Linux machine:
>java -jar ipecmd.jar -TPPK3 -P18F4550 -M –F”c:/demo.hex”
Or, if using a Windows-based operating system:
>ipecmd.exe -TPPK3 -P18F4550 -M –F”c:/demo.hex”
...
17.3 Program the Target with a Hex File
> java -jar ipecmd.jar /P16F1938 /FAPPCODE.HEX /M /TPPK3
PICKIT 3 is selected and set to a PIC16F1938. The file APPCODE.HEX is sent to the PICKIT 3. Voltages are set to the device's default values. All of the device's memory is erased and programmed with blank values in the locations not specified by APPCODE.HEX.
17.4 Program the Target without a Hex File
> java -jar ipecmd.jar /P16F1938 /M /TPPM3
MPLAB PM3 is set to a PIC16F1938. The device is erased and programmed with the current contents of the device programmer at the device’s default voltage values.
...
17.49 How to Program AVR device using PICKIT4
> java -jar ipecmd.jar /PATMEGA324PB /FAPPCODE.HEX /ORIJTAG /ORS0.100 /M /TPPK4
In this command, the MPLAB PICKIT 4 is selected and set to ATMEGA324PB. The hex file APPCODE.HEX is sent to the MPLAB PICKIT 4. Voltages are set to the device's default values.
...
18 How to Use IPECMD.EXE in Windows Machines
Note: IPECMD.exe is an executable that works only in Windows machines.
To program using PK3
>ipecmd.exe –TPPK3 –P18F4550 –M –F“c:/demo.hex”
To read target using PK3
>ipecmd.exe –P24FJ256GB106 –TPPK3 –GF“e:/pic24.hex”
To erase target using PK3
>ipecmd.exe –TPPK3 –P18F4550 –E
...
That is good news.
Your HTML is different to the file on my PC:
file:///C:/Program%20Files%20(x86)/Microchip/MPLABX/v5.25/mplab_platform/mplab_ipe/modules/ext/Readme%20for%20IPECMD.htm#_Toc518034360
My HTML does not say Snap.
Anyway, the proof of the pudding depends on trying it with a regular Snap and AVR target.
David.
Level: 10k+ Postman
Joined: Tue. Jan 9, 2007
Posts: 13199 View posts
Location: Clay County, Texas, u.S.A.
david.prentice wrote:
from
Your HTML is different to the file on my PC:
mplabx-ide-v5.25-release-notes-00.zip
Level: 10k+ Postman
Joined: Tue. Nov 11, 2003
Posts: 10367 View posts
Location: Bartlesville Oklahoma USA
js wrote:
...why do you think they want to get rid of them....
Engineers can be so cynical! But then, engineers usually know what they're talking about.
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.
Level: 10k+ Postman
Joined: Tue. Nov 11, 2003
Posts: 10367 View posts
Location: Bartlesville Oklahoma USA
js wrote:
why not post your project?
My latest project is cruising the Mediterranean sea in the next few weeks and SNAP doesn't help at all......
explain your problem
Not enough money to do more cruising, can you help please?
You used an AVR, PIC or ARM for that?
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.
Seems an ARM would be best
El Tangas wrote:
Well, I found a command line utility somewhere in the installation path, called "ipecmd".
Thanks El Tangas.
gchapman wrote:
Release Notes for IPE Command Line Interface
·Programming devices without using an IDE.
Thanks gchapman.
My SNAP seems to be working as well as my PICKit4 (with MPLABX, on a Mac), for talking to my ATmega4809 board, now that I've made the UPDI cable with the 1k pullup resistor...
they both (or perhaps mplab itself) seem to think that the chip only has 1 HW breakpoint, which is sort-of annoying. (the datasheet says 2.) (It's been theorized that the debugger reserves one for use by singlestep? if so, I think the "project dashboard" ought to say so...)
Correct, one hw breakpoint is used internally by the debugger fw and is not available for the user.
gchapman wrote:
Release Notes for IPE Command Line Interface
MPLAB® X IDE v5.25
August 2, 2019
...
1 Command Line Utility Defined
MPLAB IPE Command Line Interface (IPECMD) is a 32/64-bit command-line interface to the MPLAB X IDE. This interface is designed for programming devices in a production environment.
The IPECMD provides a common tool for the Microchip programming tools (see section 3). Support for the respective features is based on the programming tool selected.
...
...
...
17.49 How to Program AVR device using PICKIT4
> java -jar ipecmd.jar /PATMEGA324PB /FAPPCODE.HEX /ORIJTAG /ORS0.100 /M /TPPK4
In this command, the MPLAB PICKIT 4 is selected and set to ATMEGA324PB. The hex file APPCODE.HEX is sent to the MPLAB PICKIT 4. Voltages are set to the device's default values.
Why do they choose such a cryptic, hard to remember, and find, name for a command line interface tool ??
Hi,
I got a snap and an atmel ice to try. I want to build a production programming station for low volume boards programmed by someone else.
I have legacy boards with atmega64c1 and atmega32u2 chips. The avrrispMKII programmers are obsolete. Avr studio is obsolete. The chips seem to be available but verging on obsolete, but I cannot change the hw yet. Sigh.
I wanted to get to a more modern and supported hw/sw. Also some tools that will not be obsoleted soon by microchip as they digest atmel. So I downloaded the MPLAB X IDE/IPE.
The atmel ice worked pretty good, and has a nice protected plastic box - price $130 or so. I thought the snap ($14) might work too. Part of the problem is both atmega processors use the now obsolete(?) debugwire interface.
I could not get the snap to work and everyone seemed to be having problems here and elsewhere via googling. Finally I almost gave up, then used the mplabx ide Debug->Hardware_tool_emergency_boot_.... menu item with the snap. That fixed it and I can now use the snap for programming and debugging on my atmegas.
Steve
Level: Moderator
Joined: Mon. Jul 18, 2005
Posts: 101096 View posts
Location: (using avr-gcc in) Finchingfield, Essex, England
Level: 10k+ Postman
Joined: Tue. Jan 9, 2007
Posts: 13199 View posts
Location: Clay County, Texas, u.S.A.
Steveatzoll wrote:
There's some C# for that.
I want to build a production programming station for low volume boards programmed by someone else.
Steveatzoll wrote:
Waveshare has the AVRISP mkII clone.
The avrrispMKII programmers are obsolete.
Steveatzoll wrote:
An MCU similar to mega64C1 is in the radiation-tolerant Microchip catalog (avionics, LEO)
The chips seem to be available but verging on obsolete, ...
mega32u2 is long-in-tooth in comparison with USB PIC.
Steveatzoll wrote:
Approx 100USD by Waveshare in a metal box.
The atmel ice worked pretty good, and has a nice protected plastic box - price $130 or so.
Steveatzoll wrote:
debugWIRE isn't too slow though UPDI is an excellent follow-on (unified memory AVR, forthcoming AVR DA-series)
Part of the problem is both atmega processors use the now obsolete(?) debugwire interface.
Steveatzoll wrote:
Thank you!
That fixed it and I can now use the snap for programming and debugging on my atmegas.
AN2466 Using Atmel-ICE for AVR® Programming In Mass Production
Can I Get a Genuine Atmel AVRISP MKII? | Blog | Kanda
USB AVRISP XPII - Waveshare Wiki
East :
via Waveshare Development Kit Store - Small Orders Online Store, Hot Selling and more on Aliexpress.com
West :
Waveshare AVR Programmer USB AVRISP XPII for AVR devices with ISP/PDI interface 700646946136 | eBay via WaveShare | eBay Stores
ATmegaS64M1 - Tolerant Devices
ATmegaET64M1 - Tolerant Devices
East :
West :
Atmel-ICE-C Kit for debugging and programming Atmel SAM and AVR microcontroller 614961953789 | eBay
Atmel-ICE | Atmel-ICE Features
What are the AVR28DA128 AVR32DA128 AVR48DA128 AVR64DA128 ?? | AVR Freaks
edit :
Pololu - P-Star Programmable Controllers (USB PIC)
Last Edited: Tue. Sep 3, 2019 - 07:22 PM
gchapman wrote:
Steveatzoll wrote:There's some C# for that.I want to build a production programming station for low volume boards programmed by someone else.
Thanks for your info. The whole point of my post was so someone else trying to use a snap on atmega would know that it will work on debugwire, if you reflash the snap.
What hardware environment does the c# code use to replace the IPE? Does it verify the flash? (IPE doesn't seem to verify).
Regards, Steve
Last Edited: Tue. Sep 3, 2019 - 08:22 PM
Level: 10k+ Postman
Joined: Tue. Jan 9, 2007
Posts: 13199 View posts
Location: Clay County, Texas, u.S.A.
Steveatzoll wrote:
Atmel-ICE and a PC (Microsoft Windows 7 and subsequent, Atmel Studio 7 and its atprogram.exe)
What hardware environment does the c# code use to replace the IPE?
Steveatzoll wrote:
Yes
Does it verify the flash?
Steveatzoll wrote:
(IPE doesn't seem to verify).
Production Mode Settings - Developer Help
[3/4 page]
Allow “Verify Device ID before Program” under the Settings menu
edit : oops
Programming A Device - Developer Help
[step 3]
If the device is programmed successfully, the output window will show the message: Programming/Verify complete, as shown below:
edit2 :
Operate Option View - Developer Help
[last paragraph]
After making changes to the other Production Mode features, click on the Operate option button to perform the Production Mode features, such as Program., Erase, Read, Verify, or Blank Check.
Using Atmel-ICE for AVR Programming In Mass Production
[page 11]
3.1 Prerequisites
[page 12]
3.2 Features
• One button click to start the chiperase. The firmware image will then be programmed and verified, and the fuse lock bit will automatically be written.
Last Edited: Tue. Sep 3, 2019 - 08:57 PM
gchapman wrote:
Steveatzoll wrote:
(IPE doesn't seem to verify).
Production Mode Settings - Developer Help
[3/4 page]
Allow “Verify Device ID before Program” under the Settings menu
IPE v5.25 says this Allow selection is "Applicable only for PM3" and I think this is a special programmer. I want to use ice or snap. If I have it checked anyway the verify button is greyed out. And anyway I don't want to verify the device ID, I want to verify the atmega flash with the selected file.
Level: 10k+ Postman
Joined: Tue. Jan 9, 2007
Posts: 13199 View posts
Location: Clay County, Texas, u.S.A.
maybe via 'Operate Option View'
Steveatzoll wrote:
Hi,
I got a snap and an atmel ice to try. I want to build a production programming station for low volume boards programmed by someone else.
...
Part of the problem is both atmega processors use the now obsolete(?) debugwire interface.
debugWIRE is a debug interface. These parts have a SPI interface for production programming.
mraardvark wrote:
debugWIRE is a debug interface. These parts have a SPI interface for production programming.
Correct, but I and probably others with a new snap card also would like to do debugging. Production using IPE uses only SPI, but since verify is broken in IPE, I tried using IDE to program, it uses debugwire to program. But no luck there, no way to verify from the IDE either.
Steve
Yes, the MPLABX v5.25 IDE works fine.
ZIP up your MPLABX project and attach the Zip to your message.
If you provide a buildable project, we can walk you through the build, debug, manage, ... steps.
Think about it. If we can just unzip "your" project, we can replicate your "problem"
If we have to do a lot of guesswork, it is unlikely that readers will help.
If your Nuclear Bomb project is a top commercial secret, just post a non-sensitive project.
The debugWIRE debugging work fine too. But it is a lot quicker to upload code via regular SPI for production programming.
David.
david.prentice wrote:
Yes, the MPLABX v5.25 IDE works fine.
ZIP up your MPLABX project and attach the Zip to your message.
If you provide a buildable project, we can walk you through the build, debug, manage, ... steps.
Think about it. If we can just unzip "your" project, we can replicate your "problem"
If we have to do a lot of guesswork, it is unlikely that readers will help.
If your Nuclear Bomb project is a top commercial secret, just post a non-sensitive project.
The debugWIRE debugging work fine too. But it is a lot quicker to upload code via regular SPI for production programming.
David.
You misunderstand me. By upgrading my snap in the IDE, I was able to get all the spi and debugwire functions working. I was able to build a project, download it and test it. Great.
My only remaining issue is neither the IPE or the IDE has a way to verify the flashed image with the original files. The IPE has a greyed out verify button and I can find nothing in the mplabx IDE to verify an image (actually all 3 sections, flash, eeprom, configuration). These problems exist with BOTH the snap and an atmel ICE.
Steve
Surely you would use the CommandLine tool for programming, verifying, ... in any production environment.
Or since you appear to be using debugWIRE Megas, there are dozens of Third Party AVR programmers that you might use for production.
With perfectly good commandline software e.g. ATprogram or avrdude.
From memory, the SNAP worked with ATmega328P debugWIRE in MPLABX v5.15, v5.20, v5.25
However the more esoteric chips were not all supported in v5.15, v5.20.
You just needed to ask.
Of course regular AVR SPI programming was always supported by Atmel programmers and software.
David.
david.prentice wrote:
Surely you would use the CommandLine tool for programming, verifying, ... in any production environment.
Yes, I would use a CommandLine tool if the software tool would fully flash and fully verify a pre-flashed device.
What tool do you suggest? Remember this entire message thread is about using the microchip SNAP programmer/debugger.
I don't think snap is supported by avrstudio 7. So would atprogram work via SNAP? And if it does do I have to install an entire avr studio in order to get atprogram?
Regards, Steve
Level: 10k+ Postman
Joined: Tue. Jan 9, 2007
Posts: 13199 View posts
Location: Clay County, Texas, u.S.A.
Steveatzoll wrote:
https://www.avrfreaks.net/forum/snap-sale-cheeeep#comment-2746286
What tool do you suggest?
I would use a CommandLine tool if the software tool would fully flash and fully verify a pre-flashed device.
The manual says:
17.5 Verify a Hex File Against a Target
> java -jar ipecmd.jar /P16F887 /FHEXCODE.HEX /Y /TPPM3
Grr. "We'll just assign commands to the letters A-Z. Some of them might line up with words that are actually descriptive."
Does anyone know if there are any "debugging" commands for the ipecmd tool? I'm having some problems programming binaries with non-continuous code ranges, and I can't tell whether it's the tools, the programmer (PICKit4), or the chip (ATtiny412, at the moment.)
Also, the shell script wrapped that Microchip provides to run ipecmd on MacOS contains an annoying "cd $platform_bin_path" that means that if you want to specify any files (like source or destination .hex files), you need to give them a full absolute pathname. Sigh.
Excellent pointer. I did not read that because it was all about java. However it looks like it is a supported microchip tool, so I will give it a try.
I have the release notes, so will use that. I will later post here if it works ok on snap using atmegas.
Steve
This is a great thread. Just to reiterate, there is a 50% discount on the Snapd debugger, till the end of September.
Looks like folks have been able to use it in difficult AVR Debug wire and UPDI situations so this purchase is no brainer for me.
https://www.microchip.com/Develo...
I think Atmel/Microchip has been needing a product that does this, in this price range, for 10 forevers. Hope they continue to produce/support this ongoing!
R.
Last Edited: Sat. Sep 7, 2019 - 04:28 PM
Steveatzoll wrote:
gchapman wrote:
https://www.avrfreaks.net/forum/snap-sale-cheeeep#comment-2746286
Excellent pointer. I did not read that because it was all about java. However it looks like it is a supported microchip tool, so I will give it a try.
I have the release notes, so will use that. I will later post here if it works ok on snap using atmegas.
Steve
I have not tried programming with ipecmd and a SNAP.
I initially programmed it with this result:
*****************************************************
Connecting to MPLAB Snap...
Currently loaded versions:
Application version............1.2.66
Target voltage detected
*****************************************************
*****************************************************
Erasing...
The following memory area(s) will be programmed:
program memory: start address = 0x0, end address = 0x7fff
Programming/Verify complete
SNAP Program Report
19-Sep-2019, 17:05:29
Device Type:ATmega64C1
Program Succeeded.
Operation Succeeded
*****************************************************
Connecting to MPLAB Snap...
Currently loaded versions:
Application version............1.2.66
Target voltage detected
SNAP Verify Report
19-Sep-2019, 17:15:32
Device Type:ATmega64C1
*****************************************************
The following memory area(s) will be verified:
program memory: start address = 0x0, end address = 0x7fff
IPE:Verify Failed
Has anyone successfully verified using ipecmd on an atmega?
Steve
I tried using ipecmd.exe with SNAP and with ATMEL-ICE on a ATmega328P target.
It seems to program Flash ok. It does not recognise EEPROM programming.
No, the Verify always fails.
Read to hexfile reads all memory blocks
Read to screen can specify a memory type and range
I suspect that the IPECMD tool requires a bit more support for AVR. Perhaps we will see it in next MPLABX release.
You will need a PIC user to comment on the IPECMD behaviour on PIC targets.
David.
david.prentice wrote:
I tried using ipecmd.exe with SNAP and with ATMEL-ICE on a ATmega328P target.
It seems to program Flash ok. It does not recognise EEPROM programming.
No, the Verify always fails.
Read to hexfile reads all memory blocks
Read to screen can specify a memory type and range
I suspect that the IPECMD tool requires a bit more support for AVR. Perhaps we will see it in next MPLABX release.
You will need a PIC user to comment on the IPECMD behaviour on PIC targets.
David.
Yes, ipecmd seems very buggy with atmega. It is frustrating because I can read using IPE and it shows the eeprom at address 810xxx, but I cannot figure out an incantation to get ipecmd to read it. Here is what ipe read:
:02000004008179
:10000000000000000000000031353A30363A353843
:1000100000417567203330203230313900FFFFFF57
etc... to the end.
I can also read the entire chip including the above mystery regions using
java -jar ipecmd.jar -TPSNAP -PATmega64C1 -ORIisp -gfc:\test\test.hex
the 02000004 record says use the next 16 bits 0081 as a "segment address". (good old intel arch). But when I ask ipecmd to read "810000"
using option: -gp810000-8100ff
Invalid Memory region(s) entered for program/verify
There are also regions at 82xxxx and 83xxxx. I am not sure what, I think 82xxxx may be the configuration fuses.
:10FFF000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF11
:02000004008278
:03000000E0DFFA44
:02000004008377
:01000000E01F
:02000004008179
:10000000638837550000000031353A30383A3130D6
Here it shows the very last line of the program flash at 0xfff0,
shows memory at 0x820000 which reads as E0DFFA - 3 bytes
it shows memory at 0x8300000 which is one byte 0x30
Then it shows the eeprom at 810000
The eeprom contains a time/date which apparently came from when I imported an avrstudio project into mplabx. It must be hidden in the ide project somewhere. The built hex file does contain both the configuration and eeprom, but magically has put things there and doesn't seem to let me explicitly read it.
I cannot imagine a programmer that will not verify an image.
Also I find it annoying to have to reverse engineer manufacturer supplied tools.
Steve
Microchip acquired Atmel in July 2016. That is over 3 years ago.
I would have expected IPECMD to support Atmel chips by now.
SNAP was released over 1 year ago.
I would have expected Tools to support it fully by now.
From memory, PIC18 HEX files contain different sections for Flash, EEPROM, CONFIG memory.
It seems logical to treat AVR HEX files in a similar way e.g. Flash, EEPROM, FUSE, LOCK memory.
I only possess two PIC18 boards. It seems wise to experiment with IPECMD on PIC first.
An experienced PIC user would be best placed for testing IPECMD on PIC. e.g. accessing specific memory regions.
Hey-ho. It would be nice if AS7.0 could support SNAP.
But it seems sensible for Microchip to concentrate on MPLABX and IPECMD. e.g. make MPLABX "better" than AS7.0
David.
Edit. Yes, Reading an AVR into a HEX file seems to contain several memory sections:
0x000000 Flash
0x810000 EEPROM
0x820000 Fuses
0x830000 Lock
Last Edited: Fri. Sep 20, 2019 - 11:38 PM
I dug out my PIC18F458 and my PIC18F14K50 boards.
IPECMD recognises SNAP but SNAP does not support either PIC18
IPECMD works fine with PICkit4
IPECMD does not recognise PICkit2
MPLABX-IDE will not accept SNAP for either PIC18
MPLABX-IDE works with PICkit4 and PICkit2
I suspect that the next MPLABX version will provide more SNAP support.
I doubt if IPECMD will ever support PICkit2
Atmel users are accustomed to software and Tools having "features".
I would have expected better from Microchip. Especially with their PIC devices and PIC tools. After all, PIC18 is at least 15 years old and still popular.
I am not able to test SNAP with modern PIC because I only have PIC18F458 and PIC18F14K50.
david.prentice wrote:
Hey-ho. It would be nice if AS7.0 could support SNAP.
But it seems sensible for Microchip to concentrate on MPLABX and IPECMD. e.g. make MPLABX "better" than AS7.0
Try the latest Studio release, 7.0.2389, just out.
Level: 10k+ Postman
Joined: Tue. Jan 9, 2007
Posts: 13199 View posts
Location: Clay County, Texas, u.S.A.
Steveatzoll wrote:
Enable ALL MPLAB® IPE Features - Developer Help
The IPE has a greyed out verify button ...
Many MPLAB® IPE features that are accessible in the Production Mode, by default, are OFF. To make them all fully functional, run the IPE as administrator.
Well, that's pretty windows-centric. Does it turn on features beyond what I see when I change the "Settings" to "advanced mode" and give it a password (on my Mac)?
gchapman wrote:
Steveatzoll wrote:Enable ALL MPLAB® IPE Features - Developer HelpThe IPE has a greyed out verify button ...
It says there:
| Verify | verifies the device against the memory contents of IPE | On |
So even though my user has admin privs I started the IPE as administrator - still greyed out.
IPE really does not like atmega chips. It does not handle the on-chip eeprom for instance. ipecmd however can handle those, but treats eeprom as at a funny address 81xxxx instead of a separate memory like apparently is used on PICs.
The funny addresses are different than those built by avr studio. So no back compatibility for production released hex files. What a pain.
And I am running on windows so scripting is really brain dead - but I can use gawk - so hex files are text and can be handled. ipecmd seems able to read and write via SNAP ok, so I think I can handle all these weirdness-es. Of course if IPE was not broken I would not need to do any of this.
Steve
je_ruud wrote:
Try the latest Studio release, 7.0.2389, just out
Does it support SNAP? (the point of this whole thread).
Steve
ipecmd ... treats eeprom as at a funny address 81xxxx
That's how it works in all AVR .hex files, isn't it?
(Edit: no, apparently not the .hex files. The .elf files, though. All the non-progmem sections are handled as data at "funny addresses.")
Last Edited: Wed. Sep 25, 2019 - 09:48 PM