Come Join Us (MPLAB Now Supports AVRs)

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

Pages