Come Join Us (MPLAB Now Supports AVRs)

Go To Last Post
339 posts / 0 new

Pages

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

Release Notes for MPLAB® Code Configurator 8-bit AVR MCUs library v2.0.2

July 31st, 2019

[bottom of page 3]

10 Appendix: Supported Devices The MCC avr8bit Library supports the following 20 Devices.

[tinyAVR 1-series except tiny3217, tiny3216]

[megaAVR 0-series]

due to

Release Notes for MPLAB® Code Configurator’s Foundation Services Library v0.2.0

Oct 28, 2019

...

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

 

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

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

Thanks for posting this. Still didn't get it to recognize the stdint-gcc.h in the IDE, but that's not as important as the avr header.

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

westfw wrote:

The necessary FW upgrade for PICkit4 was not included in the release.

"oops."

In general, or just for MacOS?  (I can imagine both the "of course the same ancillary files are used for all OSes!" AND "The content for each OS is customized for that OS" scenarios.)
MPIPE *did* update my firmware to 1.6.87

Edit: and alas, after installing 5.30 on a PC as well, it did not offer to upgrade the firmware any further.  :-(

 

 

I bought a PICkit4 and installed MPLABX on my Ubuntu 18.02 GNU/Linux box.  I don't see any option to upgrade the firmware.   There was option to use a firmware file.

 

Also, on my system with Hi DPI screen, the text size is good but the space allocated for text is too small in many areas.

 

For other linux users, MPLABX complained that I did not have libcanberra-gtk-module (solution: sudo apt install libcanberra-gtk-module):

    Gtk-Message: 10:24:23.141: Failed to load module "canberra-gtk-module"

 

 

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

MattRW wrote:
Also, on my system with Hi DPI screen, the text size is good but the space allocated for text is too small in many areas.
Changing dpiaware might be enough (via '3       Monitor Support' in MPLAB X v5.30 'Readme for MPLAB X IDE.htm')

 

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

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

Failed to load module "canberra-gtk-module"

Those people in Canberra never do things right.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

gchapman wrote:

MattRW wrote:
Also, on my system with Hi DPI screen, the text size is good but the space allocated for text is too small in many areas.
Changing dpiaware might be enough (via '3       Monitor Support' in MPLAB X v5.30 'Readme for MPLAB X IDE.htm')

 

 

Thanks for that.  I did look and made some changes (e.g., default fontsize from 11 to 10).   I didn't notice any improvement right away but will see.  

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

What FW version to use on the tool is a part of the project configuration. In you dashboard (window down in the left corner) you have a small wrench-icon on the left side. That will open Project Properties. Select your tool in the Categories tree. Then you select Firmware in the "Options categories"-pulldown menu. There is your "Firmware Update Options". You can either "use latest", "select a file" or "Do not change the firmware".

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

Generally, the IDEs will automagically upgrade firmware if they have a newer version.

 

The necessary FW upgrade for PICkit4 was not included in the release.

I don't suppose that the necessary firmware will be offered for download/install separately from waiting for the next MPLABX?

 

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

Hello guys, i want to ask.

 

Seems what MPLABX is totally outdated buggy-laggy shit, is there any experiments to connect XC8 with MVS or AS7? Not for debug but for building\syntax checking.

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

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

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

MPLAB® XC8 C Compiler Version 2.19 Release Notes for AVR® MCU

...

1.1. Introduction

This release of the Microchip MPLAB® XC8 C compiler is a functional safety compiler, based on the v2.10 release of this compiler.

1.2. Release Date

The official release date of this compiler version is the 30 September 2019.

...

 

[page 2]

1.4. Component Licenses and Versions

...

[GPL]

...

Support code provided for the header files, linker scripts, and runtime libraries are proprietary code and not covered under the GPL.

This compiler is an implementation of GCC version 5.4.0, binutils version 2.26, and uses avr-libc version 2.0.0.

...

1.7. Editions and License Upgrades

The MPLAB XC8 Functional Safety Compiler must be activated with a functional safety license purchased from Microchip. The compiler will not operate without this license. Once activated, you can select any optimization level and use all the compiler features.

...

 

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

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

Hi All, 

 

I am currently working on 2 MPLAB X plugins, A Debugger and an Importer, that might be relevant for Arduino or ATmega328p users in general.

 

For the importer I have been tweaking the Arduino Importer plugin work to actually make it work - the one that ships with MPLAB 5.3 just doesn't work.

https://github.com/chipKIT32/chi...

 

So I manage to get the importer to worksand actually I can now use it with the Debugger plugin I am developing but I have a question which AVR experts might be able to just snap your fingers and tell me what's missing. 

 

Basically, the importer has a 'Sketch' in it's source and prebuilds the Arduino Libraries into a '.a' library file.

 

When I debug the application using the simulator, it works fine for the 'Sketch' source file but the Arduino library cores in the '.a' library seem not to be correctly linked for debugging so for example if I step into and an Arduino library function such as digitalWrite it doesn't find the source code so it can't step the source.

 

The makefile for the library uses the -g option but I am ashamed how little I know about gcc and can't figure out how to make this work for.

 

I know it's possible because I used the Arduino importer in the Atmel Studio and the projects imported that way ( which end up with a separate core library project in MPLAB ) can be source code debugged in the Arduino core level.

 

I tried to compare the linking settings between the two project types and I couldn't see why one could debug the Arduino libraries and the other not.

 

Hopefully it is just a special flag of that allows '.a' libraries to be linked as source code debuggable or it's some optimisation setting.

 

Help would be MUCH appreciated.

 

Thanks.

 

James

 

 

 

Attachment(s): 

Virtual Breadboard
www.virtualbreadboard.com
'A playground for your microcontroller'

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

MPLAB® Data Visualizer - Developer Help

[second paragraph]

MDV is capable of receiving data from various sources such as the Embedded Debugger Data Gateway Interface (DGI) and COM ports.

...

via

What's New? - Developer Help

9 Jan 2020 

 

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

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

Release Notes for MPLAB® Code Configurator 8-bit AVR MCUs library v2.1.0

Jan 16th, 2020

...

 

2 What’s New

• AVR128DAxx device family support

• tinyAVR 0-series device family support

• ATtiny3216/7 devices support

• Contextual help

 

...

 

[page 4/4]

10 Appendix: Supported Devices The MCC avr8bit Library supports the following 37 Devices. Devices shown in bold are new to this release (17 Devices)

...

via MPLAB Code Configurator | Microchip Technology (Current Download tab)

 

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

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

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

...

<item>

<title>MPLAB XC8-AVR v2.19 GCC Source</title>

<description>MPLAB XC8-AVR v2.19 GCC Source</description>

<link>

http://ww1.microchip.com/downloa...

</link>

<pubDate>1/17/2020 10:20:47 PM</pubDate>

</item>

...

 

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

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

Microchip Simplifies Functional Safety Requirements with MPLAB TÜV SÜD-certified Tools | Microchip Technology

Chandler, Arizona

January 15, 2020

...

... TÜV SÜD certification of its MPLAB® XC compilers for functional safety, significantly simplifying the functional safety qualification process for Microchip’s PIC®, AVR® and SAM microcontrollers (MCUs) and dsPIC® Digital Signal Controllers (DSCs). To further simplify testing and diagnostics, Microchip also introduced MPLAB Code Coverage license, which determines parts of software that have or have not been executed with minimal impact to the application.   

...

...  Microchip also offers many PIC, AVR, dsPIC and SAM MCUs that are Functional Safety Ready. For all Functional Safety Ready microcontrollers, Microchip provides Failure Mode Effect and Diagnostics Analysis (FMEDA) reports and safety manuals targeting ISO 26262 [automotive safety] up to ASIL-B safety levels, with some products achieving ASIL-D.

...

 

Pricing and Availability

MPLAB X IDE version 5.25 is available for free on Microchip’s website. The MPLAB Code Coverage workstation license is available today for $799. The MPLAB XC8, XC16 and XC32++ functional safety workstation licenses are available today for $2,995 each.

...

 

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

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

Microchip Gallery | MPLAB-Data-Visualizer-Plugin 1.0.675

2019-12-20

Last published

 

...

•Visualize data streamed from a running embedded target via serial port (CDC)or the Data Gateway Interface (DGI)

...

•Decode data fields at runtime using the Data Stream Protocol format

MPLAB Data Visualizer comes as a stand-alone application and as a plug-in toMPLAB X.

 

 

...

 

 

The MPLAB Data Visualizer plug-in must be installed in MPLAB X version 5.30or later for correct operation.

 

 

...

 

 

Documentation is shipped with the product and can be opened from the DataVisualizer User Interface once started.

 

...

 

Release Notes

Known Issues

...

 

DV-835 Cannot connect to ttyACM0 for streaming data. Workaround: add your user to the dialoutgroup and log out, then log back in. 
Linux

 

...

Microchip Gallery | MPLAB-Data-Visualizer-Standalone(Windows) 1.0.675

Microchip Gallery | MPLAB-Data-Visualizer-Standalone(macOS) 1.0.675

Microchip Gallery | MPLAB-Data-Visualizer-Standalone(Linux) 1.0.675

 

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

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

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

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

Where can we ask questions on MPLAB X.  Been testing it on the SAMA5D22....

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

I guess at Microchip forum??

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

MPLAB® XC8 C Compiler Version 2.20 Release Notes for AVR® MCU

...

1.2. Release Date

The official release date of this compiler version is the 8 April 2020.

 

1.3. Previous Version The previous MPLAB XC8 C compiler version was 2.10, released 28 July 2019. The previous Atmel AVR 8-bit GNU Toolchain version was 3.6.1, released Sept 2017.

 

...

 

3. What's New

...

3.1. Version 2.20

New device support Support is available for the following AVR parts: ATTINY1624, ATTINY1626, and ATTINY1627.

Better best fit allocation The best fit allocator (BFA) in the compiler has been improved so that sections are allocated in an order permitting better optimization. The BFA now supports named address spaces and better handles data initialization.

Improved procedural abstraction The procedural abstraction optimizations are now performed on more code sequences. Previous situations where this optimization might have increased code size have been addressed by making the optimization code aware of the linker's garbage collection process.

Absence of AVR Assembler The AVR Assembler is no longer included with this distribution

 

...

 

4.1. Version 2.20

Changed DFP layout The compiler now assumes a different layout used by DFPs (Device Family Packs). This will mean that an older DFP might no work with this release, and older compilers will not be able to use the latest DFPs.

 

...

 

[corrected defects]

5.1. Version 2.20

Error with long commands (XC8-1983) When using an AVR target, the compiler may have stopped with a file not found error, if the command line was extremely large and contained special characters such a quotes, backslashes, etc.

Unassigned rodata section (XC8-1920) The AVR linker failed to assign memory for custom rodata sections when building for avrxmega3 and avrtiny architectures, potentially producing memory overlap errors

...

 

though not yet on the web page

MPLAB- XC Compilers | Microchip Technology ('Compiler Downloads' tab)

 


due to

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

...

<item>

<title>MPLAB XC8-AVR v2.20 GCC Source</title>

<description>MPLAB XC8-AVR v2.20 GCC Source</description>

<link>

http://ww1.microchip.com/downloa...

</link>

<pubDate>4/29/2020 4:45:49 PM</pubDate>

</item>

...

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

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

4.1. Version 2.20

Changed DFP layout The compiler now assumes a different layout used by DFPs (Device Family Packs). This will mean that an older DFP might no work with this release, and older compilers will not be able to use the latest DFPs.

Introduction to Device Family Packs (DFPs) - Developer Help

 

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

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

(MPLAB Now Supports AVRs)

That's funny.

I bought a SNAP some time ago. Doing some recent work with an avr again, an ATmega164, I was curious to see it at work.

Studio recognized it, but then was giving no supported chips... useless.

atprogram.exe giving some error too.

So, I downloaded and installed gigs of MPLABX. 

No success either. ???

I made the factory reset procedure for SNAP, and then loaded the latest firmware for it.

And then.... the only difference is atprogram.exe, which suddenly started to work.

And it works quite great, usefull for production programming.

Studio, still doesn't work.

MPLABX IPE, the same. It doesn't work with ATmega164p. Period.

Isn't it just funny?

 

Last Edited: Thu. May 21, 2020 - 07:34 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

rammon wrote:
Studio recognized it, but then was giving no supported chips... useless.

I guess you are not using the latest DFP then.

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

mraardvark wrote:

rammon wrote:
Studio recognized it, but then was giving no supported chips... useless.

I guess you are not using the latest DFP then.

I use the latest DFP for mega chips. That's what was interested me anyway.

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

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

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

Release Notes for MPLAB® Code Configurator 8-bit AVR MCUs library v2.4.0

Aug 19, 2020

...

 

2 What’s New

• AVR64DAxx and AVR32DAxx devices support

• Bug fixes and improvements

• Updated for compatibility with MCC v4.0.0

 

...

 

5 Repairs and Enhancements

[tiny202, tiny406, tinyAVR 1-series, mega1608, AVR128DAxx]

 

...

 

10 Appendix: Supported Devices The MCC avr8bit Library supports the following 50 Devices. Devices shown in bold are new to this release. • ATtiny3216 • ATtiny3217 • ATtiny1614 • ATtiny1616 • ATtiny1617 • ATtiny814 • ATtiny816 • ATtiny817 • ATtiny412 • ATtiny414 • ATtiny416 • ATtiny417 • ATtiny212 • ATtiny214 • ATtiny1604 • ATtiny1606 • ATtiny1607 • ATtiny202 • ATtiny204 • ATtiny402 • ATtiny404 • ATtiny406 • ATtiny804 • ATtiny806 • ATtiny807 • ATtiny1627 • ATtiny1626 • ATtiny1624 • ATmega4808 • ATmega4809 • ATmega1609 • ATmega1608 • ATmega3208 • ATmega3209 • ATmega808 • ATmega809 • ATmega328 • ATmega328P • ATmega328PB • AVR128DA28 • AVR128DA32 • AVR128DA48 • AVR128DA64 • AVR64DA64 • AVR64DA48 • AVR64DA32 • AVR64DA28 • AVR32DA48 • AVR32DA32 • AVR32DA28

 

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

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

MPLAB® XC8 C Compiler Version 2.30 Release Notes for AVR® MCU

...

 

1.2. Release Date

The official release date of this compiler version is the 25 August 2020.

 

1.3. Previous Version

The previous MPLAB XC8 C compiler version was 2.29, a functional safety compiler, released 19 August 2020.

 

...

 

1.5. Component Licenses and Versions

...

This compiler is an implementation of GCC version 5.4.0, binutils version 2.26, and uses avr-libc version 2.0.0.

 

...

 

3. What's New

...

3.1. Version 2.30

New option to prevent data initialisation

A new driver option prevents the initialisation of data and the clearing of bss sections. It works by suppressing the output of the and symbols in assembly files, which will in turn prevent the inclusion of those routines by the linker.

Enhanced optimizations

A number of optimization improvements have been made, including the removal of redundant return instructions, the removal of some jumps following a skip-if-bit-is instruction, and improved procedural abstraction and the ability to iterate this process. Additional options are now available to control some of these optimizations, specifically , which allows access of objects to be performed relative to one symbol; , which allows the number of procedural abstraction iterations to be changed from the default of 2; and, , which performs more aggressive procedural abstraction, in the hope that the linker can relax long calls. This last option can increase code size if the underlying assumptions are not realised.

New device support

Support is available for the following AVR parts: AVR16DA28, AVR16DA32, AVR16DA48, AVR32DA28, AVR32DA32, AVR32DA48, AVR64DA28, AVR64DA32, AVR64DA48, AVR64DA64, AVR128DB28, AVR128DB32, AVR128DB48, and AVR128DB64.

Retracted device Support

Support is no longer available for the following AVR parts: [multiple mostly EOL automotive AVR with, IIRC, LIN basis]

...

 

3.2. Version 2.29 (Functional Safety Release)

Header file for compiler built-ins

To ensure that the compiler can conform to language specifications such as MISRA, the header file, which is automatically included by , has been updated. This header contains the prototypes for all in-built functions, such as and . Some built-ins may not be MISRA compliant; these can be omitted by adding the define to the compiler command line. The built-ins and their declarations have been updated to use fixed-width types.

...

 

5. Fixed Issues

...

5.1. Version 2.30

Global labels misplaced after outlining (XC8-2299)

Hand-written assembly code that places global labels within assembly sequences that are factored out by procedural abstraction might not have been correctly repositioned.

A relaxing crash (XC8-2287)

Using the -mrelax option might have caused the linker to crash when tail jump relaxation optimizations attempted to remove ret instruction that were not at the end of a section.

Crash when optimizing labels as values (XC8-2282)

Code using the "Labels as values" GNU C language extension might have caused the procedural abstraction optimizations to crash, with an error.

Not so const (XC8-2271)

The prototypes for and other functions from no longer specify the non-standard qualifier on returned string pointers when the feature is disabled. Note that with avrxmega3 and avrtiny devices, this feature is permanently enabled.

Lost initializers (XC8-2269)

When more than one variable in a translation unit was placed in a section (using or ), and the first such variable was zero initialized or did not have an initializer, initializers for other variables in the same translation unit that were placed in the same section were lost.

 

5.1. Version 2.29 (Functional Safety Release)

None.

...

 

6. Known Issues

...

6.1. MPLAB X IDE Integration

MPLAB IDE integration

If Compiler is to be used from MPLAB IDE, then you must install MPLAB IDE prior to installing Compiler.

6.2. Code Generation

(XC8-1966) The compiler is not detecting the memory overlap of objects made absolute at an address (via __at()) and other objects using the __section() specifier and that are linked to the same address.

Failure with library functions and __memx (XC8-1763)

Called libgcc float functions with an argument in the __memx address space might fail. Note that library routines are called from some C operators, so, for example, the following code is affected:

Broken linker option (XC8-1755)

The --section-start linker option, used to place a section at a user-defined address, does not work as expected. It is recommended that the __at() construct be used to place objects at an known address.

Data initialization

The option, which is mentioned in the user's guide, has not yet been implemented.

Limited libgcc implementation (AVRTC-731)

For the ATTiny4/5/9/10/20/40 products, the standard C / Math library implementation in libgcc is very limited or not present.

Program memory limitations (AVRTC-732)

Program memory images beyond 128 kb are supported by the toolchain; however, there are known instances of linker aborts without relaxation and without a helpful error message rather than generating the required function stubs when the -mrelax option is used.

Name space limitations (AVRTC-733)

Named address spaces are supported by the toolchain, subject to the limitations mentioned in the user's guide section Special Type Qualifiers.

http://ww1.microchip.com/downloads/Secure/en/DeviceDoc/XC8_v2.30_AVR_Sources.zip

 

edit :

MPLAB® XC8 C Compiler Version 2.30 Release Notes for AVR® MCU

9/6/20, 2:30 PM

...

 

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

Last Edited: Wed. Sep 9, 2020 - 03:16 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Broken linker option (XC8-1755)

The --section-start linker option, used to place a section at a user-defined address, does not work as expected. It is recommended that the __at() construct be used to place objects at an known address.

??!!  "Not as expected"??  So use a non-standard option instead?

 

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

no answers ... only responses

akin to what's in armcc "Compiler-specific Features"

__attribute__((at(address))) variable attribute | ARM Compiler v5.06 for µVision armcc User Guide

 

P.S.

similar in Ada :

At Clauses | Ada 95

 

edit : Embedded C has addressmod with an optional address for memory spaces.

Project status and milestones | ISO/IEC JTC1/SC22/WG14 - C: Approved standards

[mid-page]

TR 18037: Embedded C

 

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

Last Edited: Thu. Sep 3, 2020 - 07:50 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

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

Last Edited: Thu. Sep 3, 2020 - 11:32 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Oh!  that's nice.

Apparently MPLABX has working Simulation for ARM.

 

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

gchapman wrote:
New option to prevent data initialisation
You've got to wonder why?! I once worked with a TI compiler that did not clear BSS and it caused all kinds of problems as a lot of code is simply written with the assumption that BSS vars will hold 0 as default.

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

Do(es) the standard(s) say whether BSS should be cleared to zero? Safe programming would indicate that one should never read a variable without having first written it...

 

Neil

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

ISO/IEC 9899:201x

[page 572]

Annex J

(informative)

Portability issues

J.1 Unspecified behavior

1 The following are unspecified:

— The manner and timing of static initialization (5.1.2).

...

via ISO/IEC JTC1/SC22/WG14 - C: Approved standards

https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html

-fno-zero-initialized-in-bss

If the target supports a BSS section, GCC by default puts variables that are initialized to zero into BSS. This can save space in the resulting code.

This option turns off this behavior because some programs explicitly rely on variables going to the data section—e.g., so that the resulting executable can find the beginning of that section and/or make assumptions based on that.

The default is -fzero-initialized-in-bss.

 

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

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

arm CPU

Apparently most of PIC32 have peripheral simulation.

Device Support | MPLAB X IDE v5.40

 

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

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

Release Notes for MPLAB® Code Configurator 8-bit AVR MCUs library v2.5.0

Sep 17, 2020

...

 

2 What’s New

 AVR128DBxx devices support

 Added links to Mindi Schematics in AVR128DBxx Operational Amplifier module

 Bug fixes and improvements

 

...

 

10 Appendix: Supported Devices

The MCC avr8bit Library supports the following 50 Devices. Devices shown in bold are new to this release.

ATtiny Device Family: [tinyAVR 0, 1, and 2-series]

ATmega Device: [megaAVR 0-series], mega328, mega328P, mega328PB

AVRDx Device Family: [AVR DA], [AVR128DB]

 

...

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

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

MPLAB PICkit4 In-Circuit Debugger User's Guide (PDF)

[bottom of page 61]

12.6 Revision F (October 2020)

• Added Tool Pack Selection option (10.2.8 Tool Pack Selection), replacing the Firmware option, in the Debugger Function Summary.

• Changed dW to debugWIRE for clarification in Table 11-5

• Added clarification for TX and RX interfaces and notes in Table 11-6

Table 11-6 is DMCI and DGI.

 

currently up to revision E :

MPLAB® PICkit™ 4 In-Circuit Debugger User's Guide (web)

 

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

Pages