Top
Senior Member
Offline
Posts: 339
Thank You
-Given: 52
-Receive: 1719
|
|
« on: March 29, 2012, 12:08:30 00:08 » |
|
Fix for MPLAB® XC Compilershttp://www.microchip.com/pagehandler/en_us/promo/mplabxc/Windows, Linux & Mac OS X 13-Aug-2012; Updated for v1.10 compilers. 14-Aug-2012; MPLAB XC32 C++ license activated. 01-Jan-2013; License info update. 12-Jun-2014; Updated for v1.32 compilers. 19-Jun-2014; Fixed issue with XC32 compilers.
|
|
« Last Edit: June 20, 2014, 11:00:49 23:00 by Top »
|
Logged
|
|
|
|
LithiumOverdosE
Senior Member
Offline
Posts: 361
Thank You
-Given: 383
-Receive: 587
|
|
« Reply #1 on: June 04, 2012, 04:14:50 16:14 » |
|
XC8 is based on HiTech PICC + PICC18 with compatibility mode for C18. XC16 is ex-C30. XC32 is ex-C32.
Since MPLABX 1.20 all XCx tool chains are present.
However, now my Proteus tool chain disappeared but that's hardly a problem for the moment.
|
|
|
Logged
|
|
|
|
MichelM
Newbie
Offline
Posts: 23
Thank You
-Given: 31
-Receive: 95
|
|
« Reply #2 on: June 16, 2012, 10:28:08 10:28 » |
|
|
|
|
Logged
|
|
|
|
Top
Senior Member
Offline
Posts: 339
Thank You
-Given: 52
-Receive: 1719
|
|
« Reply #3 on: August 01, 2012, 01:21:24 13:21 » |
|
The link in dl.txt is not working any more.
Original post updated; new links in dl.txt.
|
|
|
Logged
|
|
|
|
LithiumOverdosE
Senior Member
Offline
Posts: 361
Thank You
-Given: 383
-Receive: 587
|
|
« Reply #4 on: August 11, 2012, 12:11:37 12:11 » |
|
I just tried this fix with XC8 1.10 and the compiler stays in Free mode.
With XC8 1.00 and 1.01 everything is fine.
|
|
|
Logged
|
|
|
|
Top
Senior Member
Offline
Posts: 339
Thank You
-Given: 52
-Receive: 1719
|
|
« Reply #5 on: August 11, 2012, 12:50:39 12:50 » |
|
I just tried this fix with XC8 1.10 and the compiler stays in Free mode.
Try replacing xclm.exe in C:\Program Files\Microchip\xc8\v1.10\bin folder.
|
|
|
Logged
|
|
|
|
LithiumOverdosE
Senior Member
Offline
Posts: 361
Thank You
-Given: 383
-Receive: 587
|
|
« Reply #6 on: August 11, 2012, 01:05:56 13:05 » |
|
Ah, so that was the trick. In previous versions it was enough to replace it in C:\Program Files\Microchip\xclm directory.
|
|
|
Logged
|
|
|
|
marcodassi
Junior Member
Warned
Offline
Posts: 40
Thank You
-Given: 73
-Receive: 26
|
|
« Reply #7 on: August 12, 2012, 11:09:13 11:09 » |
|
Just downloaded XC8, XC16 and XC32 1.10; tested with current fix; results: - XC8 1.10 - fine, works in Pro mode with all optimizations; - XC16 1.10 - fine, works in Pro mode with all optimizations; - XC32 1.10 - DOESN'T WORK - the compiler stays in Free mode, no optimizations allowed I've tried to copy xclm.exe in the "\Program Files\Microchip\xc32\v1.10\bin" folder too, with no luck. Please fix it, if possibile Thank you very much in advance!
|
|
|
Logged
|
|
|
|
cranor
Newbie
Offline
Posts: 18
Thank You
-Given: 10
-Receive: 10
|
|
« Reply #8 on: September 13, 2012, 03:23:12 15:23 » |
|
The version v1.41 of MPLAB® X IDE is available from here : http://www.microchip.com/mplabx-ide-windows-installerIt solves some of compilation and compiler detection issues with XC compilers but introduces new problems too..
|
|
|
Logged
|
|
|
|
SpaleKG
Junior Member
Offline
Posts: 36
Thank You
-Given: 19
-Receive: 18
|
|
« Reply #9 on: October 07, 2012, 11:44:27 23:44 » |
|
Just to confirm that current fix works fine on Mac OSX on all XC compilers.
I have one question about MPLAB X IDE. How to configure project when using bootloader in PIC. For example bootloader uses first 200 bytes of FLASH memory, so how to tell compiler to generate hex to start after that ?
|
|
|
Logged
|
|
|
|
jukinch
Inactive
Offline
Posts: 5
Thank You
-Given: 5
-Receive: 2
|
|
« Reply #10 on: October 07, 2012, 11:54:45 23:54 » |
|
SpaleKG: you can use a project specific "linker script" to start after that memory location. Jukinch
|
|
|
Logged
|
|
|
|
odessa
Newbie
Offline
Posts: 22
Thank You
-Given: 101
-Receive: 16
|
|
« Reply #11 on: October 08, 2012, 09:47:22 09:47 » |
|
You can set a code offset from within MPlab X. If you right click your project - select properties - then click linker - Choose additional options from the drop down menu on the right you'll see a code offset option.
|
|
|
Logged
|
|
|
|
SpaleKG
Junior Member
Offline
Posts: 36
Thank You
-Given: 19
-Receive: 18
|
|
« Reply #12 on: October 13, 2012, 12:33:34 12:33 » |
|
You can set a code offset from within MPlab X. If you right click your project - select properties - then click linker - Choose additional options from the drop down menu on the right you'll see a code offset option.
Does this move interrupt vector adresses too or I need to do that somehow?
|
|
|
Logged
|
|
|
|
Gallymimu
Hero Member
Offline
Posts: 704
Thank You
-Given: 152
-Receive: 214
|
|
« Reply #13 on: October 13, 2012, 05:36:53 17:36 » |
|
Does this move interrupt vector adresses too or I need to do that somehow?
I'm pretty sure you can't move the interrupt vector addresses. Some of the PIC processors have alternate interrupt vector tables which follow directly in memory after the primary interrupt vectors but that doesn't help you much with typical bootloader related issues. You can however point the interrupt vectors to a jump table that resides in your application memory space that can then be overwritten when you load a new firmware. That way you can update interrupt function locations without overwriting the first segments of memory.
|
|
« Last Edit: October 13, 2012, 05:39:41 17:39 by Gallymimu »
|
Logged
|
|
|
|
RedAlert
Active Member
Offline
Posts: 161
Thank You
-Given: 168
-Receive: 302
|
|
« Reply #14 on: October 30, 2012, 08:11:07 20:11 » |
|
|
|
« Last Edit: October 30, 2012, 08:30:26 20:30 by RedAlert »
|
Logged
|
"Life would be easier if we had its source code"
|
|
|
marcodassi
Junior Member
Warned
Offline
Posts: 40
Thank You
-Given: 73
-Receive: 26
|
|
« Reply #15 on: October 31, 2012, 11:50:05 23:50 » |
|
|
|
|
Logged
|
|
|
|
j2mb
Inactive
Offline
Posts: 4
Thank You
-Given: 6
-Receive: 2
|
|
« Reply #16 on: November 28, 2012, 03:48:26 03:48 » |
|
|
|
|
Logged
|
|
|
|
metal
Global Moderator
Hero Member
Offline
Posts: 2420
Thank You
-Given: 862
-Receive: 678
Top Topic Starter
|
|
« Reply #17 on: November 28, 2012, 03:50:55 03:50 » |
|
u'r kidding me!?
|
|
|
Logged
|
|
|
|
TucoRamirez
Senior Member
Offline
Posts: 307
Thank You
-Given: 257
-Receive: 115
Tuco ... dead or Alive
|
|
« Reply #18 on: November 28, 2012, 08:31:47 08:31 » |
|
the thing that confuses me about mplabX is that even if my code is ok, mplab show me "!" signs ... (even with XC demos or the application libraries -that compile 100/100 ok ) ... anyway, the config tool inside is quite nice but, mplabx is crappy slow on my eeepc netbook (1G Ram ... ) ...but in a 4GB elitebook hp runs ok ...
|
|
|
Logged
|
Whoever double crosses me and leaves me alive... he understands nothing about Tuco.
|
|
|
LithiumOverdosE
Senior Member
Offline
Posts: 361
Thank You
-Given: 383
-Receive: 587
|
|
« Reply #19 on: November 28, 2012, 11:06:14 11:06 » |
|
Well, same here on Win7 x64.
|
|
|
Logged
|
|
|
|
Gallymimu
Hero Member
Offline
Posts: 704
Thank You
-Given: 152
-Receive: 214
|
|
« Reply #20 on: November 28, 2012, 03:26:02 15:26 » |
|
the thing that confuses me about mplabX is that even if my code is ok, mplab show me "!" signs ... (even with XC demos or the application libraries -that compile 100/100 ok ) ... anyway, the config tool inside is quite nice but, mplabx is crappy slow on my eeepc netbook (1G Ram ... ) ...but in a 4GB elitebook hp runs ok ... I have a lot of problems with this as well. They don't have the parsing working quite right yet. It's especially bad in XC8
|
|
|
Logged
|
|
|
|
gamegurus
Newbie
Muted
Offline
Posts: 23
Thank You
-Given: 14
-Receive: 64
Oh what a wonderful morning!!!
|
|
« Reply #21 on: December 03, 2012, 09:04:41 09:04 » |
|
After install, How to check, if XC compiler is free or PRO versions? I tried all ways 1) cmd 2) compile test and see output in MPLABX but didnt find any such info.
|
|
|
Logged
|
Indian Gaming Guru
|
|
|
TucoRamirez
Senior Member
Offline
Posts: 307
Thank You
-Given: 257
-Receive: 115
Tuco ... dead or Alive
|
|
« Reply #22 on: December 03, 2012, 01:07:32 13:07 » |
|
check the project properties, in the part of compiler tou will see the options of optimisation
|
|
|
Logged
|
Whoever double crosses me and leaves me alive... he understands nothing about Tuco.
|
|
|
Gallymimu
Hero Member
Offline
Posts: 704
Thank You
-Given: 152
-Receive: 214
|
|
« Reply #23 on: December 03, 2012, 04:22:27 16:22 » |
|
check the project properties, in the part of compiler tou will see the options of optimisation
I don't think that tells you, all options always show in the properties. You need to run the compiler and look at the output. It should say it is running in free mode and omniscient code generation is disabled if it is in free mode.
|
|
|
Logged
|
|
|
|
ximo
Inactive
Offline
Posts: 1
Thank You
-Given: 26
-Receive: 1
|
|
« Reply #24 on: December 24, 2012, 09:37:32 09:37 » |
|
XC8 v1.12 is working ok with this fix. Tested on Ubuntu 12.04. Regards
|
|
|
Logged
|
|
|
|
|