Posted by 12oclocker: Tue. Jan 12, 2021 - 02:07 AM
1
2
3
4
5
Total votes: 0
In linux I have been using command line for avr development for years now. Any text editor, xed or geany, is fine for writing C or asm files. Once you get used to it, it is surprisingly quicker to develop in than sluggish GUI stuff. If mplab has avr simulation that may be worth checking out. Linux command line simulation is lacking.
This release of the Microchip MPLAB® XC8 C compiler is a minor update that contains a bug fix.
[page 4]
3. What's New
...
3.1. Version 2.32
Stack Guidance Available with a PRO compiler license, the compiler's stack guidance feature can be used to estimate the maximum depth of any stack used by a program. It constructs and analyzes the call graph of a program, determines the stack usage of each function, and produces a report, from which the depth of stacks used by the program can be inferred. This feature is enabled through the command-line option. A summary of stack usage is printed after execution. A detailed stack report is available in the map file, which can be requested in the usual way.
New device support Support is available for the following AVR parts: ATTINY427, ATTINY424, ATTINY426, ATTINY827, ATTINY824, ATTINY826, AVR32DB32, AVR64DB48, AVR64DB64, AVR64DB28, AVR32DB28, AVR64DB32, and AVR32DB48.
Retracted device support Support is no longer available for the following AVR parts: AVR16DA28, AVR16DA32 and, AVR16DA48.
[page 8]
5. Fixed Issues
...
5.1. Version 2.32
Second access of library fails (XC8-2381) Invoking the Windows version of the library archiver a second time to access an existing library archive may have failed with an error message.
Posted by gchapman: Thu. May 13, 2021 - 08:39 PM(Reply to #343)
1
2
3
4
5
Total votes: 0
Note : Advance information as the web page is to be updated.
MPLAB X updated on 14-May'21
MPLAB X IDE can be in a virtual machine other than for remote (if I correctly read)
Almost totally AVR-complete other than simulated I/O
Release Notes for MPLAB® X IDE
MPLAB X IDE v5.50
May 8, 2021
...
2.5 Unsupported Configurations
Virtual Machines.
Remote USB Plug-in using Virtual Machines is not supported
Apple ARM Core
...
6.1 Compilers & Assemblers
[MPLAB XC8 v2.05 and sub., Microchip AVR GCC 3.4.3 and sub., AVRASM2 2.2.6 and subsequent from Microchip Studio]
It is recommended that you install compilers in the same location as MPLAB XC compilers so MPLAB X IDE can find them.
...
7.1 Web Documentation – Internet Access Required
...
Register Help: For some AVR devices, you can access on-line data sheets, user’s guides and other support documentation from a Kit Window. In an IO View or Editor window, you can select a register and then click on the PDF icon to open the on-line help for that register.
Configuration Bits Help: For some AVR devices, you can select a fuse in the Configuration Bits window and then click on the PDF icon to open the on-line help for that fuse.
...
13. What's New in v5.50
·AVR device debug improvements: Support for Boot memory, blank check, and live connect. Easier access to erase function.
...
·MPLAB Data Visualizer included in install: The MPLAB DV is now bundled with MPLAB X IDE. New support for Power Debugging.
AVR ATmega4808 and ATmega4809 devices support a feature for efficient access of data used by the application which resides in the flash program space. Currently, MPLAB X IDE will not identify this space as a separate viewable memory.
Workaround: The data is viewable where the data begins in the program memory space.
ATTINY3217 Curiosity Nano certain firmware version does not function correctly and no firmware update was triggered in MPLAB X IDE. After an automatic update on a PC running Microchip Studio, the boards function correctly under MPLAB X IDE.
...
MPLABX-5516
Dashboard display does not include the data section of Flash usage in the total for AVR devices
...
MPLABX-5139
MPLAB X IDE failed to program/debug ATA8210 with STK600
...
MPLABX-4008
AVR-GCC Toolchain on a mounted drive in Linux does not get discovered with correct version information in MPLAB X IDE.
MPLABX-3991
Const declared variables display incorrect addresses in the watch window for AVR devices
...
MPLABX-3840
BOOTEND and APPEND configuration values are not in the configuration window
ATmega4809
MPLABX-3839
Error in disassembly of rcall/callAVR instructions
ATmega4809
MPLABX-3836
When launching a Debug Wire debug session and the device signature is wrong, the launch is aborted. However, a dialog pops up asking if you want to disable Debug Wire even though you never entered a Debug Wire session.
...
MPLABX-3615
The AVR-GCC installed with the Arduino IDE does not work with MPLAB X IDE
MPLABX-3595
Memory notification not occurring when notification happens on a config mem change for AVR devices.
The modules are supported by the MCC Melody in both offline MPLAB® X and online MPLAB® Xpress.
Refer to the Supported Families, Devices and Peripherals section for complete list of newly supported devices and peripherals. [tinyAVR 2-series, AVR DA, AVR DB; missing EVSYS]
Wow "MPLAB Xpress"? They've kept that pretty quiet! (or maybe PIC users having been using it for years?). Looks like more AVR fun (my first project)...
(thinks: does the URL really have to contain your email address unencoded I wonder ??)
New platform combines configuration and collaboration tools with knowledge-based search to modernize the embedded development workflow
[beginning of third paragraph]
The enhanced MPLAB Xpress IDE delivers a powerful, scalable cloud infrastructure for development and debug along with community collaboration tools using secure GitHubrepository interface controls. Designers have the option to download MPLAB Xpress projects to continue development in MPLAB X IDE.
For MPLAB X IDE v6.00, the PDF files “MPLAB X IDE User's Guide”, “MPLAB IPE User's Guide”, and “MDB User’s Guide” have been removed from the build and are linked to their web locations. “Device Support.htm” has also been removed from the build as this file is now updated on new pack releases. All these documents may be found on the MPLAB X IDE Webpage under the Documentation tab.
7.1 Web Documentation – Internet Access Required
...
Register Help: For some AVR devices, you can access on-line data sheets, user’s guides and other support documentation from a Kit Window. In an IO View or Editor window, you can select a register and then click on the PDF icon to open the on-line help for that register.
Configuration Bits Help: For some AVR devices, you can select a fuse in the Configuration Bits window and then click on the PDF icon to open the on-line help for that fuse.
·MPLAB ICE 4 support: Support for the new Microchip in-circuit emulator. See MPLAB ICE 4 documentation.
·Compiler Advisor: MPLAB XC C compiler feature to visually compare memory usage with different optimizations. See MPLAB X IDE documentation, Analysis section.
·CI/CD Wizard: Generate project files for use in CI/CD applications – Docker with Jenkins or alone – using this wizard. See MPLAB X IDE documentation, Automation section.
·MPLAB Data Visualizer: Touch application features: dashboard with widgets, variable groups, and auto config. See Data Visualizer documentation.
·MyMicrochip sharing: Share data in MPLAB X IDE with your MyMicrochip account when logged in. See MPLAB X IDE documentation, Before You Begin>Install MPLAB X IDE section.
AVR ATmega4808 and ATmega4809 devices support a feature for efficient access of data used by the application which resides in the flash program space. Currently, MPLAB X IDE will not identify this space as a separate viewable memory.
Workaround: The data is viewable where the data begins in the program memory space.
...
17.12 IDE Specific Issues
...
MPLABX-6089
ATTINY3217 Curiosity Nano certain firmware version does not function correctly and no firmware update was triggered in MPLAB X IDE. After an automatic update on a PC running Microchip Studio, the boards function correctly under MPLAB X IDE.
ATTiny3217
...
MPLABX-5516
Dashboard display does not include the data section of Flash usage in the total for AVR devices
AVR devices
...
MPLABX-5139
MPLAB X IDE failed to program/debug ATA8210 with STK600
ATA8210
...
MPLABX-4008
AVR-GCC Toolchain on a mounted drive in Linux does not get discovered with correct version information in MPLAB X IDE.
AVR MCUs
...
MPLABX-3836
When launching a Debug Wire debug session and the device signature is wrong, the launch is aborted. However, a dialog pops up asking if you want to disable Debug Wire even though you never entered a Debug Wire session.
ATmega328PB, other AVR debugWIRE devices
...
MPLABX-3595
Memory notification not occurring when notification happens on a config mem change for AVR devices.
The official release date of this compiler version is the 6 December 2021.
...
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.
[page 4, middle]
2.1. smart-io-format Option
...
To reduce code size, the compiler customizes library code associated with the print and scan families of smart IO functions, based on the conversion specifications present in the format strings collated across all calls to these functions.
...
2.3. Amendment to Section 4.14.2 Changing and Linking the Allocated Section
Note that contrary to information contained in this section of the User's guide, changes made to the compiler in this release now mean that custom sections can be linked using the option and without having to modify the linker script.
3. What's New
3.1. Version 2.35
New device support Support is available for the following AVR parts: ATTINY3224, ATTINY3226, ATTINY3227, AVR64DD14, AVR64DD20, AVR64DD28, and AVR64DD32.
Improved context switching The new option changes how interrupt functions save registers on entry and how those registers are restored when the interrupt routine terminates. It works in a similar way to the option, but only affects interrupt functions (ISRs).
Even more improved context switching The new option controls the context switch code generated for small interrupt service routines. When enabled, this feature will have the assembler scan the ISR for register usage and only save these used registers if required.
Configurable flash mapping Some devices in the AVR DA and AVR DB family have an SFR (e.g. FLMAP) that specifies which 32k section of program memory will be mapped into the data memory. The new option can be used to have the linker place all - qualified data in one 32k section and automatically initialize the relevant SFR register to ensure that this data is mapped into the data memory space, where it will be accessed more effectively.
Microchip Unified Standard Libraries All MPLAB XC compilers will share a Microchip Unified Standard Library, which is now available with this release of MPLAB XC8. The MPLAB® XC8 C Compiler User!s Guide for AVR® MCU no longer includes the documentation for these standard functions. This information can now be found in the Microchip Unified Standard Library Reference Guide. Note that some functionality previously defined by avr-libc is no longer available. (See Library functionality.)
Smart IO As part of the new unified libraries, IO functions in the printf and scanf families are now customgenerated on each build, based on how these functions are used in the program. This can substantially reduce the resources used by a program.
Smart IO assistance option When analyzing calls to smart IO functions (such as or ), the compiler cannot always determine from the format string or infer from the arguments those conversion specifiers required by the call. Previously, the compiler would always make no assumptions and ensure that fully functional IO functions were linked into the final program image. A new option has been added so that the compiler can instead be informed by the user of the conversion specifiers used by smart IO functions whose usage is ambiguous, preventing excessively long IO routines from being linked. (See smart-io-format Option for more details.)
Placing custom sections Previously, the option only placed the specified section at the requested address when the linker script defined an output section with the same name. When that was not the case, the section was placed at an address chosen by the linker and the option was essentially ignored. Now the option will be honoured for all custom sections, even if the linker script does not define the section. Note, however, that for standard sections, such , or , the best fit allocator will still have complete control over their placement, and the option will have no effect. Use the option, as described in the user's guide.
[page 9, middle]
4. Migration Issues
...
4.1. Version 2.35
Inappropriate speed optimizations
[difference due to -O3]
Library functionality
[Microchip Unified Standard Library isn't avr-libc]
[page 10, bottom]
5. Fixed Issues
...
5.1. Version 2.35
Contiguous allocation using __at (XC8-2653) Contiguous allocation of multiple objects places in a section with the same name and using did not work correctly. For example: const char arr1[] __attribute__((section(".mysec"))) __at (0x500) = {0xAB, 0xCD}; const char arr2[] __attribute__((section(".mysec"))) = {0xEF, 0xFE}; should have placed immediately after .
Specifying section start addresses (XC8-2650) The option was silently failing to place sections at the nominated start address. This issue has been fixed for any custom-named sections; however, it will not work for any standard sections, such as or , which must be placed using a option.
Linker crashes when relaxing (XC8-2647) When the optimization was enabled and there were code or data sections that did not fit into the available memory, the linker crashed. Now, in such a circumstance, error messages are issued instead.
No no-falling-back (XC8-2646) The option was not correctly implemented, nor documented. This can now be selected to ensure that the compiler will not fall back to a lower optimization setting if the compiler is unlicensed, and will instead issue an error.
Inappropriate speed optimizations (XC8-2637) Procedural abstraction optimizations were being enabled when selecting level 3 optimizations ( ). These optimizations reduce code size at the expense of code speed, so should not have been performed.
Bad EEPROM access (XC8-2629) The routine did not work correctly on Xmega devices when the option was enabled (which is the default state), resulting in EEPROM memory not being read correctly.
Invalid memory allocation (XC8-2593, XC8-2651) When the or linker option (for example passed through using a driver option) is specified, the corresponding text/data region origin was updated; however, the end address was not adjusted accordingly, which could have led to the region exceeding the target device's memory range.
Crash with over-attributed function (XC8-2580) The compiler crashed if a function was declared using more than one of the interrupt, signal or nmi attributes, e.g., .
Invalid ATtiny interrupt code (XC8-2465) When building for ATtiny devices and the optimizations were disabled ( ), interrupt functions may have triggered assembler messages.
Options not being passed through (XC8-2452) When using the option with multiple, comma-separated linker options, not all of the linker options were being passed to the linker.
Error indirectly reading program memory (XC8-2450) In some instances, the compiler produced an internal error ( ) when reading a two byte value from a pointer to program memory
[page 14]
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
Incorrect initialization (XC8-2679) There is a discrepancy between where the initial values for some global/static byte-sized objects are placed in data memory and where the variables will be accessed at runtime.
strtod incorrectly sets endptr (XC8-2652) In instances where a subject string for conversion by contains what appears to be a floating-point number in exponential format and there is an unexpected character after an character, then the address, if provided, will point to the character after the and not the itself. For example: strtod("100exy", endptr); will result in pointing to the character.
Bad indirect function calls (XC8-2628) In some instances, function calls made via a function pointer stored as part of a structure might fail.
strtof returns zero for hexadecimal floats (XC8-2626) The library functions et al and et al, will always convert a hexadecimal floating-point number that does not specify an exponent to zero. For example: strtof("0x1", &endptr); will return the value 0, not 1.
Inaccurate stack advisor messaging (XC8-2542, XC8-2541) In some instances, the stack advisor warning regarding recursion or indeterminate stack used (possibly through the use of alloca()) is not emitted.
Failure with duplicate interrupt code (XC8-2421) Where more than one interrupt function has the same body, the compiler might have the output for one interrupt function call the other. This will result in all call-clobbered registers being saved unnecessarily, and the interrupts will be enabled even before the epilogue of the current interrupt handler has run, which could lead to code failure.
Const objects not in program memory (XC8-2408) For avrxmega3 and avrtiny projects unitialized objects are placed into data memory, even though a warning suggests that they have been placed in program memory. This will not affect devices that do not have program memory mapped into the data memory space, nor will it affect any object that is initialized.
Bad output with invalid DFP path (XC8-2376) If the compiler is invoked with an invalid DFP path and a 'spec' file exists for the selected device, the compiler is not reporting the missing device family pack and instead selecting the 'spec' file, which might then lead to an invalid output. The 'spec' files might not be up to date with the distributed DFPs and were intended for use with internal compiler testing only.
Memory overlap undetected (XC8-1966) The compiler is not detecting the memory overlap of objects made absolute at an address (via ) and other objects using the 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 address space might fail. Note that library routines are called from some C operators, so, for example, the following code is affected:
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 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.
Time zones The library functions assume GMT and do not support local time zones, thus will return the same time as , for example.
Added Button, Slider Wheel sensor support for newly supported devices (Check Supported Devices and Families).
Added support for two-way Data Streamer protocol through UART communication for both supported AVR and PIC devices (Note: Update to the latest MPLAB touch Plugin v1.0.1).
Added example .c and .h files during generation of touch files.
This release of the Microchip MPLAB® XC8 C compiler implements minor bug fixes and installer changes.
[page 11 bottom and page 12 top]
5. Fixed Issues
...
5.1. Version 2.36
Error when delaying (XC8-2774) Minor changes in the default Free mode optimizations prevented constant folding of operand expressions to the delay built-in functions, resulting in them being treated as nonconstants and triggering the error: .
I recently finished a project using MPLAB / MCC for the ATtiny817, and it never crossed my mind that there was anything strange about compiling for an AVR processor in MPLAB.
To be fair, I've done a lot of work in MPLAB (and previously in Atmel Studio and Eclipse and...), and I'd be hard pressed to say that any one IDE is really better than another: they all have their warts.
This release of the Microchip MPLAB® XC8 C compiler is a functional safety compiler, based on the v2.36 release of this compiler and which now supports the Network Server License.
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopSimulator Model | MPLAB X Simulator Help
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopIn linux I have been using command line for avr development for years now. Any text editor, xed or geany, is fine for writing C or asm files. Once you get used to it, it is surprisingly quicker to develop in than sluggish GUI stuff. If mplab has avr simulation that may be worth checking out. Linux command line simulation is lacking.
- Log in or register to post comments
TopHave you looked at this: https://github.com/avrsimulator/... ? Linux models (.so) are available in the DFPs at http://packs.download.atmel.com/.
- Log in or register to post comments
TopDevice Support | MPLAB X IDE v5.45 (AVR begin mid-page 41)
Working Outside of MPLAB® X IDE - Developer Help
UltraEdit / UltraStudio as an alternative to MPLAB-X? | Microchip
UltraEdit | The world's best text editor
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopGetting Started with the MCC AVR® and PIC16/18 IEC60730 Class B Diagnostic Libraries
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopMPLAB XC8-AVR v2.32 GCC Source
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopLinux :
Assembler for the AVR128DB28? | AVR Freaks
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopRevision F (May 2021) | MPLAB® X IDE User’s Guide
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopNote : Advance information as the web page is to be updated.MPLAB X updated on 14-May'21
MPLAB® X IDE | Microchip Technology (near bottom)
copied from https://www.microchip.com/RSS/recent-software.xml
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Toppublished yesterday
Data Streamer Driver User Guide
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopWow "MPLAB Xpress"? They've kept that pretty quiet! (or maybe PIC users having been using it for years?). Looks like more AVR fun (my first project)...
(thinks: does the URL really have to contain your email address unencoded I wonder ??)
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topedit : web doc
Revision History | MPLAB® Data Visualizer User's Guide
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Toppublished 18-Dec'21
new are TWI drivers
MPLAB® Code Configurator Melody 8-bit AVR MCU Modules Release Notes
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopMPLAB® X IDE | Microchip Technology
https://ww1.microchip.com/downloads/en/DeviceDoc/mplabx-ide-release-notes-v6.00.zip
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopMPLAB® ICE 4 | AVR Freaks
Compiler Advisor in MPLAB X IDE User's Guide
edit :
MDB User's Guide
edit2 :
Compiler Advisor - Developer Help
CI/CD Wizard - Developer Help
edit3 :
CI/CD Wizard in MPLAB X IDE User's Guide
edit4 : web doc
CI/CD Wizard in MPLAB X IDE User's Guide
edit5 :
GitHub - MicrochipTech/cicd-assistant: Contains support scripts for setting up continuous integration / continuous deployment (CICD) systems.
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopWith thanks to W4GNS.
MPLABX v6.00 Release | Microchip
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopIt's always a good idea to wait and see, after MC releases a IDE or compiler.
Don't be the Alpha tester
- Log in or register to post comments
Toplinter (MISRA® C 2012) and Code Coverage :
MPLAB® Analysis Tool Suite
https://www.microchipdirect.com/product/search/all/SW006027
edit :
MPLAB Analysis Tool Suite Workstation License | Microchip Technology
MPLAB Analysis Tool Suite User's Guide
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopMPLAB® XC Compilers | Microchip Technology
(MPLAB XC8 still at v2.32)edit : the above strikethru
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopMicrochip Unified Standard Library Reference Guide
edit : web doc
Microchip Unified Standard Library Reference Guide
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopNumerous changes in two and a half years.
MPLAB X IDE User’s Guide
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopLooks like the major addition to MPLabX 6.0 is support of the $1800 Ice4 debugger
MPLAB X IDE v6.00 features
==========================
- Support for MPLAB ICE4
- Compiler advisor
- MISRA checker
- CI/CD assistant
- Bug fixes
https://www.microchip.com/forums...
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topwww.tokopedia.com/madagang .Buy and Donated cheap electronics and manuscripts.
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopMPLAB® Code Configurator Melody 8-bit AVR MCU Modules Release NotesMPLAB® Code Configurator Melody 8-bit AVR MCU Modules Release NotesMCC Melody Release Notes for AVR MCU Family Support
What are the AVR28DA128 AVR32DA128 AVR48DA128 AVR64DA128 ?? | AVR Freaks
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopMPLABX IDE 6.00 support AVRdude basically https://www.avrfreaks.net/forum/... and PIC Serial bootloader.
www.tokopedia.com/madagang .Buy and Donated cheap electronics and manuscripts.
- Log in or register to post comments
Topre AVRDUDE, more :
Using AVRDUDE from within MPLAB X (Mac OS X) | Microchip
Using AVRISP MK2 with MPLAB X IDE | AVR Freaks
Configure MPLAB for AVRISP Mk2 | AVR Freaks
Microchip Gallery | App Launcher Plugin 1.2.0
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topwww.tokopedia.com/madagang .Buy and Donated cheap electronics and manuscripts.
- Log in or register to post comments
TopAVRxt TWI drivers are described in section 3.
MCC Melody API Reference for AVR MCU FamiliesMCC Melody API Reference for AVR MCU Families
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topand it should be a lot easier to use with one of these
John Samperi
Ampertronics Pty. Ltd.
https://www.ampertronics.com.au
* Electronic Design * Custom Products * Contract Assembly
- Log in or register to post comments
TopFixed that for you...
The perfect cap for MPLABX users...
- Log in or register to post comments
Topwww.tokopedia.com/madagang .Buy and Donated cheap electronics and manuscripts.
- Log in or register to post comments
TopJeckson I have edited your signature and removed the "military" bits, please keep it that way if you want to maintain a good standing here.
John Samperi
Ampertronics Pty. Ltd.
https://www.ampertronics.com.au
* Electronic Design * Custom Products * Contract Assembly
- Log in or register to post comments
TopI recently finished a project using MPLAB / MCC for the ATtiny817, and it never crossed my mind that there was anything strange about compiling for an AVR processor in MPLAB.
To be fair, I've done a lot of work in MPLAB (and previously in Atmel Studio and Eclipse and...), and I'd be hard pressed to say that any one IDE is really better than another: they all have their warts.
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopPages