Come Join Us (MPLAB Now Supports AVRs)

Go To Last Post
311 posts / 0 new

Pages

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

YouTube

Unboxing the New MPLAB® PICKit™ 4 In Circuit Debugger

Published on Feb 27, 2018

https://www.youtube.com/watch?v=Ahfrpo_NW_Y (1m41s)

via https://plus.google.com/+MicrochipTech/posts/A5fNnaJ2aPu

 

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

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

YouTube

Getting Started with the NEW MPLAB® PICkit™ 4 In-Circuit Debugger

Microchip Technology

Published on Mar 1, 2018

https://www.youtube.com/watch?v=oUZ9bV82xgU (6m18s)

via https://plus.google.com/+MicrochipTech/posts/FAGFecSzkfv

 

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

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

A new arrival at

Mouser Electronics  - Electronic Components Distributor

Mouser Electronics

MPLAB® PICkit™ 4 In-Circuit Debugger/Programmer

https://www.mouser.com/new/microchip/microchip-mplab-pickit-4/

 

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

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

Are you thinking about taking advantage of the great discount on the MPLAB® ICD 4 ...

https://plus.google.com/+MicrochipTech/posts/25p5eHQa3XY

Currently out-of-stock at microchipDIRECT though with an ETA of 02-Apr'18.

IIRC, the sales price on an invoice is honored on restock.

 

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

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

I wish they would lower the AtmelICE prices back down to the same level.

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

jgmdesign wrote:
I did not see anything about AVR support.
MPLAB X 4.20 (6/5/2018)

From a quick read, the changes from 4.15 to 4.20 :

  • Compilers - removal of AVR GNU
  • SAM E70 and SAM S70

Readme for MPLAB X IDE.htm

...

 

11 What's New in v4.20

...

Support for SAM E70 using MPLAB ICD 4 or MPLAB PICkit 4 (using AC102015) - Selected SAM devices supported. No support for EDBG, e.g. Xplained boards not supported.

...

Device Support.htm

...

ATSAMS70Q21B

ATSAMS70Q20B

ATSAMS70N21B

ATSAMS70N20B

ATSAMS70J21B

ATSAMS70J20B

ATSAME70Q21B

ATSAME70Q20B

ATSAME70N21B

ATSAME70N20B

ATSAME70J21B

ATSAME70J20B

...

http://www.microchip.com/mplab/mplab-x-ide

http://www.microchip.com/development-tools/pic-and-dspic-downloads-archive

http://www.microchip.com/design-centers/32-bit/sam-32-bit-mcus/sam-e-mcus

http://www.microchip.com/design-centers/32-bit/sam-32-bit-mcus/sam-s-mcus

http://www.microchip.com/developmenttools/ProductDetails/PartNO/DV164045 (MPLAB ICD 4)

http://www.microchip.com/developmenttools/ProductDetails/PartNO/PG164140 (MPLAB PICkit 4)

 

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

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

gchapman wrote:
Compilers - removal of AVR GNU

So that didn't last long, then!

 

frown

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

250USD minus 75USD (Jul'18 dev tool sale)

Microchip Technology Inc

Microchip Technology

DV164045 - MPLAB ICD 4 In-Circuit Debugger

http://www.microchip.com/Developmenttools/ProductDetails/DV164045

...

$75 off - Use Coupon Code : TP1913        Expires : 31-Jul-2018

...

via

Microchip Direct Logo

microchipDIRECT

DEVELOPMENT TOOL DEALS

https://www.microchipdirect.com/product/DevToolDeals

 

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

Last Edited: Wed. Jan 23, 2019 - 01:30 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil wrote:

gchapman wrote:
Compilers - removal of AVR GNU

So that didn't last long, then!

 

frown

Maybe wait for MPLAB X 5.0?

http://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB_XC8_C_Compiler_User_Guide_for_AVR.pdf

http://ww1.microchip.com/downloads/en/DeviceDoc/Readme_XC8_for_AVR.pdf

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

Either wow or oh no ... at least the current XC8 pro is on sale so a reasonable price may be reached.

Compiler invocations per http://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB_XC8_C_Compiler_User_Guide_for_AVR.pdf :

  • legacy is avr-gcc
  • free (zero price) or pro is xc8-gcc

Atmel did not compete with second parties; Microchip will compete with IAR, HP InfoTech, and Imagecraft Creations.

 


Microchip Technology Inc

Microchip

MPLAB XC8 Compiler PRO Dongle License

http://www.microchip.com/Developmenttools/ProductDetails/SW006021-DGL

...

40% off - Use Coupon Code : TP1914        Expires : 31-Jul-2018

(0.6 * 1495USD = 897USD)

...

via  https://www.microchipdirect.com/product/DevToolDeals

 

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

Last Edited: Wed. Jan 23, 2019 - 01:30 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

So what does all this mean?  That instead of the free Atmel Studio Suite that works with ALL Atmel components.....and that many complain about, we are going to be forced to PURCHASE compilers for each device family we want to work with?  And maintenance fees as well?

 

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

So what does all this mean?

For me it means to just use chips supported by whatever the latest free version of AS7  (or even AS4??) is. But I'm in a fortunate position I guess.

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

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

Last Edited: Thu. Jul 5, 2018 - 02:58 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

jgmdesign wrote:
So what does all this mean?
<WAG>

  • EOL of Microchip builds of AVR GCC (iow Microchip AVR GCC is legacy)
  • therefore, WinAVR is dead ... long live WinAVR wink
  • the rise of LLVM AVR? (a FOSS attempt to compete against proprietary XC8 AVR Pro)
  • Near-eventual EOL of Atmel Studio
  • therefore, third parties enter the void (Visual Studio extension?, Visual Studio Code extension?, etc)

</WAG>

It's the end of an epoch ... it's the beginning of the next epoch.

jgmdesign wrote:
... we are going to be forced to PURCHASE compilers for each device family we want to work with?
No for free version, yes for pro version (Microchip's take on AVR GCC)

jgmdesign wrote:
And maintenance fees as well?
Depends on the instance of XC8; dongle instance is perpetual.

 


Microchip

MPLAB® XC8 C Compiler User’s Guide for AVR® MCU

http://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB_XC8_C_Compiler_User_Guide_for_AVR.pdf

(page 13)

...

If you are building a legacy project or would prefer to use the old command-line driver you may instead run the avr-gcc driver application and use appropriate command-line options for that driver. Those options may differ to those described in this guide.

...

http://llvm.org/docs/ReleaseNotes.html#changes-to-the-avr-target (AVR LLVM 7)

http://releases.llvm.org/6.0.0/LICENSE.TXT (7's ETA is 2018-Sep-05)

Microchip Technology Inc

Microchip Technology

MPLAB- XC Compilers

http://www.microchip.com/mplab/compilers

(expand License Types, near bottom)

Dongle License

...

  • Includes unlimited updates to new compiler versions without the need for HPA (perpetual license)

...

 

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

Last Edited: Wed. Jan 23, 2019 - 01:31 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

gchapman wrote:
EOL of Microchip builds of AVR GCC (iow Microchip AVR GCC is legacy)

Hmmm - so what will that mean for Arduino ... ?

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

What was that thing about Microchip never discontinuing a product while you're still using it ... ?

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil wrote:

What was that thing about Microchip never discontinuing a product while you're still using it ... ?

 

They won't discontinue Studio; they might stop future development on it though which is a different thing.

 

Although, how much of Studio is their's?

#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

Presumably they PAY Microsoft for the core of Studio? Perhaps someone at Mchip has been asked to sign a cheque and was surprised to see how big it was?

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

awneil wrote:
Hmmm - so what will that mean for Arduino ... ?
Possibly no major effect on Arduino though when AVR GCC patches arrive may change.

FSF AVR GCC is complete "enough".

xc8-gcc may have a dual license (GPL, commercial); another GCC contributor has dual licensing with GCC patches once per year.

 

Edit:

XC8-GCC release periods may be similar to XC16.

 

XC16 version, source code date

1.31, 2017-Feb-20

1.32B, 2017-Aug-23

1.33, 2017-Oct-18

1.34, 2018-Apr-02

1.35, 2018-Jun-12

 

current XC16 is 1.35 (6/20/18)

 


Microchip Technology Inc

Microchip Technology

PIC and dsPIC Downloads Archive

http://www.microchip.com/development-tools/pic-and-dspic-downloads-archive

(near bottom)

Source Archives

http://www.microchip.com/mplab/compilers (Downloads tab)

 

Edit1 : XC16 : 1.34, 1.35

 

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

Last Edited: Wed. Jan 23, 2019 - 01:31 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

One or an entity joins the Visual Studio Partner Program at some level.

Microsoft

Microsoft

VSP

Visual Studio Isolated and Integrated Shells

https://vspartner.com/pages/vsshells

(right side)

Get the Benefits

 

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

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

with thanks to Greg_Muth and his https://www.avrfreaks.net/forum/hint-thing-come#comment-2516531

Microchip Technology Inc

Microchip Technology

MPLAB- X IDE

http://www.microchip.com/mplab/mplab-x-ide

...

MPLAB X IDE v5.0 Now Provides Beta Support For AVR® MCUs

...

Getting started with AVR in MPLAB X IDE

...

(Downloads tab, Release Notes, unzip, Readme for MPLAB X IDE.htm)

11 What's New in v5.00

·         New Project format – Projects created in or updated to v5.00 are not backward compatible! However, there is a plugin you can use to revert projects (Tools>Plugins>Available Plugins>Save As v4.xx Project).
MPLAB X IDE projects now support packs, found under <MPLAB X IDE install directory>\v5.00\packs. Packs contain versioned device information.

·         Support for AVR devices using Atmel-ICE (EDBG) or PICkit 4 (UPDI) – Selected AVR devices supported only on stated tools.

·         Support for Atmel-ICE (EDBG) – Atmel embedded debugger (EDBG) support using Atmel-ICE.

·         MPLAB XC8 AVR support – Support for AVR devices in MPLAB XC8 v2.00.

·         AVR Language tool support – Support for AVR GCC and AVRASM2.

·         Support for some Dual Core Devices – Support added for some dual core (dsPIC33C) devices.

 


http://www.microchip.com/mplab/compilers

 

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

Last Edited: Wed. Jan 23, 2019 - 01:32 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0
  • Compilers - removal of AVR GNU

restored in MPLAB X v5.00

http://www.microchip.com/mplab/mplab-x-ide

(Downloads tab, Release Notes, unzip, Readme for MPLAB X IDE.htm)

5.3 Compilers

...

Atmel Compiler (1)

Toolchain

Versions

ARM GNU

ARM GNU

5.3.1 and later

AVR GNU

AVR GNU

3.4.3 and later

...

  1. Install this compiler in the same location as MPLAB XC compilers so MPLAB X IDE can find them, e.g.;
    C:\Program Files\microchip\ARM_GCC

...

 

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

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

I've cut down the device support list to just show AVR parts...

 

PK4 is the Microchip Pickit4

ICD4 is the Microchip ICD4

AICE is the Atmel ICE

 

P means program

D means debug

 

 

[EDIT]

Formatting in PDF tidied.

 

 

 

 

Attachment(s): 

#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

Very useful chart. Hope you are able to maintain it until there is something comparable from "the front office".

 

Jim

Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net

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

@Brian Fairchild wrote:

 

I've cut down the device support list to just show AVR parts...

The device support provided by Microchip appears to be inaccurate.  A number of "Alternate Tools" are available:

 

 

 

And I just programmed a MEGA328PB X-Mini through its mEDBG:

 

Greg Muth

Portland, OR, US

Xplained/Pro/Mini Boards mostly

 

Make Xmega Great Again!

 

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

Greg_Muth wrote:
And I just programmed a MEGA328PB X-Mini through its mEDBG:

How painful was that?

 

Did you use debugWIRE or ISP?   How big an executable?

A 30kB executable file takes over two minutes on AS7 over debugWIRE with XMINI-328PA   (and times out).

 

I would assume that any debugging session is going to involve exactly the same traffic over mEDBG on both IDEs.

Fortunately the new UPDI works very nicely with EDBG on its XPRO.    And my Tiny817-XMINI works reasonably fast on its mEDBG.

 

It will be interesting to see how MPLAB compares with AS7.

 

David.

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

MPLAB is (currently) lumping Power Debugger, EDBG, mEDBG and Atmel-ICE into the same 'device support matrix', i.e the same device support level applies to all...

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

@david.prentice wrote:

How painful was that?

 

Did you use debugWIRE or ISP?   How big an executable?

 

AFAIK I used debugWIRE.  At the end of programming a dialog box pops up and asks whether to keep debugWIRE enabled or revert to ISP (program-only) mode.  The file was small, about 2.5kB.  I didn't time it, but it seemed similar to AS7.   

 

EDIT: forgot to answer the first question:

 

Not painful at all.  I imported an AS7 project into MPLABX and, while the three configurations were imported, the symbols defined in Project -> Properties -> Toolchain were lost.  But after correcting that the project built without incident.

Greg Muth

Portland, OR, US

Xplained/Pro/Mini Boards mostly

 

Make Xmega Great Again!

 

Last Edited: Sun. Jul 22, 2018 - 09:54 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

There's trouble in (beta) paradise.  Seems as likes to crash:

 

as: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
avr-gcc: internal compiler error: Aborted (program as)

 

I opened a support ticket.

 

Should I be posting this in the Microchip MPLABX forum rather than here..?

 

 

Greg Muth

Portland, OR, US

Xplained/Pro/Mini Boards mostly

 

Make Xmega Great Again!

 

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

Greg_Muth wrote:
I opened a support ticket.
I think Joey Morin started a thread about this LOCALE thing elsewhere. Clearly something has crept into later avr-gcc that has maybe only been tested in one locale.

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

Hints about future programming/debugging hardware are starting to appear.

 

AC102015

Microchip Technology ICD4 RJ45 Debugger Adapter Board
Microchip ICD4 RJ45 Debugger Adapter Board is designed for debugging SAM Xplained and legacy AVR® demonstration boards with MPLAB ICD4 and PICkit 4 debuggers. This debugger adapter board supports SWD, JTAG, and ICSP protocols in various connector formats. The debugger adapter board is compatible with MPLAB PICkit 4 ICSP, SEGGER J-link JTAG SWD, SEGGER J-link EJTAG, Atmel-ICE, and power debugger JTAG SWD/AVR JTAG.

FEATURES
Debugs legacy AVR and SAM Xplained demonstration boards
Protocols supported:
JTAG
SWD
ICSP
Compatible with:
MPLAB ICD 4 ICSP/JTAG
MPLAB PICkit 4 ICSP
SEGGER J-link JTAG SWD
SEGGER J-link EJTAG
Atmel-ICE and Power Debugger JTAG SWD
Atmel-ICE and Power Debugger AVR JTAG

#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

clawson wrote:

Greg_Muth wrote:
I opened a support ticket.
I think Joey Morin started a thread about this LOCALE thing elsewhere. Clearly something has crept into later avr-gcc that has maybe only been tested in one locale.

https://www.avrfreaks.net/forum/ubuntu-mate-1804-lts-issue-atmel-toolchains

 

Not sure the issue lies with the Atmel Toolchain, although that is certainly possible, perhaps even likely.

 

 

"Experience is what enables you to recognise a mistake the second time you make it."

"Good judgement comes from experience.  Experience comes from bad judgement."

"Wisdom is always wont to arrive late, and to be a little approximate on first possession."

"When you hear hoofbeats, think horses, not unicorns."

"Fast.  Cheap.  Good.  Pick two."

"We see a lot of arses on handlebars around here." - [J Ekdahl]

 

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

Yes and no... See my response over there for a quick workaround.

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

 

See my response over there for a quick workaround.

How about a quick workaround for MPLABX?  I've the following pre-build commands:

  • export/set/<nothing> LC_LANG=XYZZY 
  • export/set/<nothing> LC_LANG=C 
  • export/set/<nothing> LANG=C 

 

None of those worked.  If I prepend the actual compiler commands from the build output with LANG=C, they compile:

LANG=C  "/opt/microchip/xc8/v2.00/bin/xc8-cc"  -mcpu=ATmega328PB -c  -x c -D__ATmega328PB__ ...

Is there a way to tell MPLABX to do that?

 

Greg Muth

Portland, OR, US

Xplained/Pro/Mini Boards mostly

 

Make Xmega Great Again!

 

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

For mplab it should be enough to export that before launching mplab_ide from the same shell ( so that mplab inherits that variable)

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

 

For mplab it should be enough to export that before launching mplab_ide from the same shell ( so that mplab inherits that variable)

I thought I had tried that, but apparently I did not, because it just worked. 

 

Thanks!

Greg Muth

Portland, OR, US

Xplained/Pro/Mini Boards mostly

 

Make Xmega Great Again!

 

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

Anybody figured out how to wire up the Pickit 4 to an AVR ICSP header?

 

I tried that ICD4/PICkit 4 Target Adapter Board with an Atmel-ICE adapter cable and traced back the pins, somethin' aint right. Target voltage was a No-Connect, and MOSI was shorted to SCK. Also, MISO was a no connect.  

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

Which header on the adapter board did you use? It should be the bottom one one top side (the ICSP one is on the bottom side)

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

The one furthest from the PICkit on the top side. 

 

So, I should be able to ring out the circuit on the bottom header to figure out how to bring this out to the AVR 100mil 2x3 header? 

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

Joining for updates; I'd like to know if and how the PICKIT 4 can interface with AVRs.

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

Microchip

Developer Help

PICkit™ 4 Setup Instructions

http://microchipdeveloper.com/pickit4:setup

(Step 4)

...

For SAM or AVR devices, you will need the AC102015 Debugger Adapter Board for demo board connectivity.

 

...

Microchip Technology Inc

Microchip

Debugger Adapter Board

http://www.microchip.com/Developmenttools/ProductDetails/PartNo/AC102015

PICKit4 debugger adapter board, two cables for SEGGER J-Link, Microchip RJ-11 cable, Atmel-ICE cable

(Features tab)

...

 • 2 x 5 – 50 mil (compatible with Atmel-ICE and Power Debugger AVR JTAG)

...

 

Edit : PNG
 

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

Last Edited: Wed. Jan 23, 2019 - 01:33 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

I guess I should have been more specific... does this "debugger adapter board" have any logic of its own, or is it simply re-routing contacts? If the latter, then I can just design a header on my PCBs, so that the PICKIT 4 can work directly with the AVR or SAM, without "adapters" in between.

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

Thank you for the link. 

 

I have that adapter board. 

 

I'm wondering what to do with it. 

 

From what I've experienced there is zero documentation on the pinout of that AVR ICSP header. I know pin 2 is VTarg, pin 3 is Ground... After that I'm at a loss. I don't actually need that adapter board, I can squid cable with the best of them, just looking for support on the pinout. 

 

gchapman wrote:
PICkit™ 4 Setup Instructions http://microchipdeveloper.com/pi...

 

 

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

igendel wrote:

I guess I should have been more specific... does this "debugger adapter board" have any logic of its own, or is it simply re-routing contacts? If the latter, then I can just design a header on my PCBs, so that the PICKIT 4 can work directly with the AVR or SAM, without "adapters" in between.

 

It's just a pinout adapter/rerouter, gives convenience factor for having an ICD4 adapter and Pickit 4 adapter, especially if your targets have 50mil headers. 

 

If you have 0.1" headers making a quick harness/adapter is easy, if you know the specifics on your guzintas and gozoutas. 

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

dshay wrote:

If you have 0.1" headers making a quick harness/adapter is easy, if you know the specifics on your guzintas and gozoutas. 

 

That is exactly what I want to know... smiley

 

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

Greg_Muth wrote:
The device support provided by Microchip appears to be inaccurate.

Digi-Key Electronics - Electronic Components Distributor

DigiKey

Microchip’s MPLAB® X IDE Beta Support for AVRs!

by Kristof Berg

7/27/2018

https://www.digikey.com/en/blog/microchips-mplab-x-ide-now-features-beta-support-for-avrs

...

 

(mid-page)

Selected popular parts have been added to the IDE, and the IDE features the ability to request support for parts not currently featured within the IDE.

 

...

 

One other development, Microchip’s newly released, low-cost PICkit™ 4 In-Circuit programming and debugging development tool also currently provides Beta support for AVRs.

[MPLAB PICkit 4 picture]

...

via https://plus.google.com/u/0/+digikey/posts/iQcJokqiBHu

 

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

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

gchapman wrote:

Greg_Muth wrote:
The device support provided by Microchip appears to be inaccurate.

The thread that this is quoting has been edited. It appears they were working with MPLAB X 4.2 at the time. 

 

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

I wrote:

I imported an AS7 project into MPLABX and, while the three configurations were imported, the symbols defined in Project -> Properties -> Toolchain were lost.  But after correcting that the project built without incident.

 

Turns out this was user error, not an issue with MPLABX.

 

Greg Muth

Portland, OR, US

Xplained/Pro/Mini Boards mostly

 

Make Xmega Great Again!

 

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

david.prentice wrote:
It will be interesting to see how MPLAB compares with AS7.

Microchip

Developer Help

Migrating to MPLAB® X IDE from Atmel Studio IDE

http://microchipdeveloper.com/mplabx:migration-atstudio

due to https://plus.google.com/+MicrochipTech/posts/htrPiHywn8w

 

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

Pages