Come Join Us (MPLAB Now Supports AVRs)

Go To Last Post
316 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

Pages