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"
Posted by je_ruud: Wed. Nov 13, 2019 - 06:16 AM(Reply to #304)
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".
Posted by DevelopPetuh: Mon. Nov 18, 2019 - 04:03 AM
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.
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.
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.
... 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.
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
Posted by gchapman: Wed. May 20, 2020 - 06:25 PM(Reply to #322)
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.
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.
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?
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.
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...
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.
·IDE Scripting: Improved user scripting (autoload.py).
·MISRA Checking available: MISRA checking now available for use on your application code, with the latest CPPchecker installed with MPLAB X IDE.
·Compatible-device selection in downloadable projects: A selection of compatible devices is provided for selected projects.
·Data breakpoints for AVR: Data breakpoints are now available for some AVR devices.
·MPLAB Code Coverage: Command line tools support. See MPLAB Code Coverage release notes.
·MPLAB XC Compiler Changes: All PRO compilers will require annual HPA renewal to keep PRO optimizations; otherwise optimizations revert to Free. Free optimizations for all MPLAB XC compilers are -O0, -O1, -O2. PRO optimizations are -O0, -O1, -O2, -O3, -Os, -mpa.
14 Repairs and Enhancements in v5.45
...
MPLABX-5500
A valid communication (such as 0.125 MHz or 1/4 of the device clock speed) must be entered when selecting the ISP communication protocol.
ATmega328P, AVRs with ISP + dW communication protocols
MPLABX-5003
BOOTSIZE and CODESIZE fuses for AVR-DA are missing in MPLAB X IDE v5.30.
MPLABX-4901
If the configuration bit RSTPINCFG in an UPDI interface is configured as GPIO or as RST, the debug tool will have to be configured to simple high voltage mode to be able to read/program the device again. On the first try a "PDI enable failed (27)" message may be observed. Try a second time and the operation will succeed.
AVR
...
MPLABX-3894
AVR STS instruction displayed incorrectly in multiple MPLAB X IDE displays:
·Program memory view
·Disassembly listing view
Trace
AVR
...
17.10 Device Feature Support Issues
...
AVR mapped program memory is not viewable on ATmega4808, ATmega4809 devices (MPLABXE-1813)
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-5516
Dashboard display does not include the data section of Flash usage in the total for AVR devices
AVR devices
...
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-3991
Const declared variables display incorrect addresses in the watch window for AVR devices
atmega324pb
...
MPLABX-3840
BOOTEND and APPEND configuration values are not in the configuration window
ATmega4809
MPLABX-3839
Error in disassembly of rcall/call AVR instructions
AVR 4809
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-3725
LDS instruction generated has wrong operands in Disassembly view.
ATmega324pb
...
MPLABX-3615
The AVR-GCC installed with the Arduino IDE does not work with MPLAB X IDE
AVR devices
MPLABX-3595
Memory notification not occurring when notification happens on a config mem change for AVR devices.
This release of the Microchip MPLAB® XC8 C compiler is a minor update that contains a bug fix.
[page 8]
5. Fixed Issues
...
5.1. Version 2.31
Unexplained compiler failures (XC8-2367) When running on Windows platforms that had the system temporary directory set to a path that included a dot ' ' character, the compiler may have failed to execute.
#5 "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."
#5 "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."
This video introduces a new addition to Microchip’s development tool portfolio: the MPLAB® XC8 PIC® Assembler. This tool lets you create projects that are written entirely in assembly code for any 8-bit PIC device and is recommended for all new assembly projects, as the MPASM™ assembler is no longer being developed.
due to
via https://www.microchip.com/RSS/recent-software.xml
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopThanks 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.
- Log in or register to post comments
TopI 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"
- Log in or register to post comments
Top"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopThose people in Canberra never do things right.
John Samperi
Ampertronics Pty. Ltd.
https://www.ampertronics.com.au
* Electronic Design * Custom Products * Contract Assembly
- Log in or register to post comments
TopThanks 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.
- Log in or register to post comments
TopWhat 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".
- Log in or register to post comments
TopGenerally, the IDEs will automagically upgrade firmware if they have a newer version.
I don't suppose that the necessary firmware will be offered for download/install separately from waiting for the next MPLABX?
- Log in or register to post comments
TopHello 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.
- Log in or register to post comments
TopBuilding :
Building a Project Outside of MPLAB® X IDE - Developer Help
Syntax then semantics - invoke MPLAB XC8 from within your preferred editor.
https://www.avrfreaks.net/forum/come-join-us-mplab-now-supports-avrs?page=5#comment-2746851
https://www.avrfreaks.net/forum/avr-studio-going-be-phased-out-favor-mplab#comment-2796681
https://www.avrfreaks.net/forum/microchip-trying-wean-people-arduino-atmel-studio#comment-2791116
"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
TopHi 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'
- Log in or register to post comments
Topvia
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topvia MPLAB Code Configurator | Microchip Technology (Current Download tab)
"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
TopMicrochip 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
- Log in or register to post comments
TopMPLAB Code Coverage - Microchip Technology | Mouser
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopWhere can we ask questions on MPLAB X. Been testing it on the SAMA5D22....
- Log in or register to post comments
TopI guess at Microchip forum??
John Samperi
Ampertronics Pty. Ltd.
https://www.ampertronics.com.au
* Electronic Design * Custom Products * Contract Assembly
- Log in or register to post comments
Topthough not yet on the web page
MPLAB- XC Compilers | Microchip Technology ('Compiler Downloads' tab)
due to
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopIntroduction to Device Family Packs (DFPs) - Developer Help
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top(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?
- Log in or register to post comments
TopI guess you are not using the latest DFP then.
- Log in or register to post comments
Top- 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
Tophttp://ww1.microchip.com/downloads/Secure/en/DeviceDoc/XC8_v2.30_AVR_Sources.zip
edit :
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top??!! "Not as expected"?? So use a non-standard option instead?
- Log in or register to post comments
Topno 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.
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topupdated yesterday
MPLAB- XC Compilers | Microchip Technology (mid-page, Compiler Downloads tab)
edit :
MPLAB XC8 v2.30 Released | Microchip
Using Hexmate On the Command Line - Developer Help
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopOh! that's nice.
Apparently MPLABX has working Simulation for ARM.
- Log in or register to post comments
Top- Log in or register to post comments
TopDo(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
Neil Barnes
www.nailed-barnacle.co.uk
- Log in or register to post comments
Topvia ISO/IEC JTC1/SC22/WG14 - C: Approved standards
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Toparm CPU
Apparently most of PIC32 have peripheral simulation.
Device Support | MPLAB X IDE v5.40
"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
TopTable 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
- Log in or register to post comments
Topedit :
Device Support | MPLAB X IDE v5.45
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopSometimes the pace of improvement is more encouraging than the quality of the product...
- Log in or register to post comments
TopMPLAB XC8-AVR v2.31 GCC Source
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopMPLAB X v5.45 Released | Microchip
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopEA Series? Have I missed something?
#1 Hardware Problem? https://www.avrfreaks.net/forum/...
#2 Hardware Problem? Read AVR042.
#3 All grounds are not created equal
#4 Have you proved your chip is running at xxMHz?
#5 "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."
- Log in or register to post comments
TopThat is this.
http://ww1.microchip.com/downloa...
- Log in or register to post comments
TopWe're going to need a crib sheet to compare the different Dx/Ex families and see what makes them different.
#1 Hardware Problem? https://www.avrfreaks.net/forum/...
#2 Hardware Problem? Read AVR042.
#3 All grounds are not created equal
#4 Have you proved your chip is running at xxMHz?
#5 "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."
- Log in or register to post comments
TopSo far, we have DA, DB, DD and EA I think.
- Log in or register to post comments
Tophttps://www.avrfreaks.net/forum/what-are-avr28da128-avr32da128-avr48da128-avr64da128?page=2#comment-2988166
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topfyi, in the PIC side of the "house" is a second assembler (multi-platform); maybe AVR is next.
edit :
AVR Assembler - Developer Help
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopRelease of Microchip Studio 7.0.2542 | AVR Freaks
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topedit : 24-Nov'20
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopPages