While upgrading the compiler would allow me to program the current PICS, I don't actually need a new 'feature' or 'peripheral', the 46k22 has done everything for me.Īs for power consumption, anything less than 1ma is 'micropower' to me. I'm kinda stuck using the 18F46K22, the 'Swiss Army Knife' of PICs, though I suppose that's 'obsolete' to many. I'm with the 'Prince' as well ! OK, I'm a 'dinosaur', still using MPLAB 8v92 (last version ?), a real PICkit3 and an early 5 version of compiler. On a scale of 1.10, I rate it as a low '2' as a developmentĮnvironment, when MPLAB, was perhaps a 7 or 8. It is now close to being useable sometimes,īut is still very unreliable, and does not provide features that the older MPLAB Have to agree wholeheartedly with PrinceNai. It looks as if the changes in 5.50, require the compiler to be the current However key difference for both him and me, is that we are running 5.105. I then tested programming with a PicKit 4, and Now, like Daniel, I just compiled a real test program, and it Like Forrest Gump said, MPLABX is like a box of chocolade, you never know what you'll get. Very unlike MPLABX, where every new version is just much bigger and also much worse.
#Mplab xc8 make error 1 full#
I don't need 39 different sleep modes or to work in FemtoWatt range when in full speed. So from my perspective, I'd always choose a PIC supported by MPLAB 8.92 for any project, unless there is a peripheral or a footprint I just need to use and I can't find it on older micros. Right now it is only this forum, my laziness and the fact that I can still use the old IDE for older micros that keeps me working with PIC's and not switching to way cheaper and faster ARM's (with their IDE's as complicated as MPLABX). The deciding factor, 20 years ago to use PIC was the user friendliness of their IDE.
#Mplab xc8 make error 1 upgrade#
For me the Microchip's move from MPLAB to MPLABX is by far the worst upgrade ever. I've run into this kind of problem with MPLABX before. Which forces me to compile in 5.45, export to the IPE of 5.50. The version 5.50 Pickit 4 has support for the PIC, however it does not compile with ccs. The version 5.45 when connected to Pickit 4 does not support this PIC. Good afternoon Daniel, the problem is not compiling, the problem is programing.
Make: Leaving directory 'C:/Users/eng2/Dropbox/Vitaltech/Transf/teste_18F57Q84.X' I'm having to compile on mplabx 5.45, and program the PIC on IPE 5.50. My problem is that version 5.45 doesn't support the PIC I'm using. Use CCS IDE or return version 5.45 of IDE MPLABX. Apparently version 5.50 is not compatible with the CCS plugin (makefile issues). I tried to create projects with 16F and 18F pics and had the same problem. Last edited by adilsongutierres_ on Thu 10:02 am edited 1 time in total Nbproject/Makefile-impl.mk:39: recipe for target '.build-impl' failedīUILD FAILED (exit value 2, total time: 71ms) Make: Leaving directory 'C:/Users/Gutierres/18F57K42_SIMULADOR_PUC.X' Make: Entering directory 'C:/Users/Gutierres/18F57K42_SIMULADOR_PUC.X' Make -f nbproject/Makefile-default.mk SUBPROJECTS=. Make: *** No rule to make target '.build-conf'.
It's only supported on mplabX 5.50 for my burning tool, a pickit4. It's only supported on mplabX 5.50 for my burning tool a pickit4. My Mplab X 5.50 does not work with ccs 5.103 SOLVEDĭear friends, mplabx 5.50 does not work with ccs 5.103. Send them to Mplab X 5.50 does not work with ccs 5.103 SOLVED
Please do not post bug Reports on this forum. Include nbproject/Makefile-local-default.CCS :: View topic - My Mplab X 5.50 does not work with ccs 5.103 SOLVEDįAQ Forum Help Official CCS Support Search Register Profile Log in to check your private messages Log inĬCS does not monitor this forum on a regular basis. Ifeq "$(wildcard nbproject/Makefile-local-default.mk)" "nbproject/Makefile-local-default.mk" # Include makefile containing local settings User is passing all local related variables already # This makefile implements configuration specific macros and targets. # has a -pre and a -post target defined where you can add customized code. # Edit the Makefile in the project folder instead (./Makefile).
0 kommentar(er)
