Hope this isn't old news to everyone else, but it is new to me....US$47.95

http://www.microchip.com/developmen...ontent=Development+Tools&utm_campaign=Article

http://ww1.microchip.com/downloads/en/Market_Communication/MicroSolutions_May_June_2018.pdf

 

Looking forward to the latest Dave Jones rant!!
Max.

 

Yeah, got email from microchip today.
Like Max, I can not wait for Dave to take it apart.

 

+1 for Dave, guy's an animal.
Whoever comes across it first should link it to this thread so we can all share the Aussie excellence.

 

I particularly liked the Microchip Utube response in their 'The Office' take off skit reply.
Max.

 

Yeah that was also excellent.

 

Well, I ordered one today. They have a 20% off deal going on and I am tired of messing around with my finicky pickit3 (clone?).

 

I guess it is bye bye for using MPLAB-IDE with it, too bad they don't make thier stuff downward compatible.
As the video by Dave outlined.
Max.

 

I have been using MPLAB X IDE for a while and I actually like it quite a bit (v5.10). I have started to focus on pic32 (using XC32 v2.10). This is not a trivial effort, at least to me. If you think that going through an 8 bit data sheet is daunting (not saying that you do) try a much larger family data sheet and then another 15-20 very large and specific data sheets for all of the functions/categories.

I reached a decision that I would do what they (Microchip) want because, in my view it is easiest and best until I get to a point where I can see otherwise. IOW I am trying to look forward.

That also means deciding not to use any legacy peripheral libraries. They even issue a warning that they will likely be dropped in future xc32 versions. That means getting into the Harmony libraries. That does not mean, however, getting into Harmony projects. I wanted to stick to the CCI (Common C Interface) but I simply can't adhere to the no no sub-directories rule in the header specification. Once I am far along in my understanding and familiarity, I will go back and simply use correct paths. But, right now, I run into so many dependencies the paths get too funky. Again, give me some time.

Of course I am not happy about the price for an optimized xc32, but it is only a hope that it becomes a problem some day. In fact, taken together, all the compilers, the IDE, the assemblers...all free, it's pretty awesome.

Anyways, that's my story and I am sticking to it

 

I have been using MPLAB X IDE for a while and I actually like it quite a bit (v5.10). I have started to focus on pic32 (using XC32 v2.10). This is not a trivial effort, at least to me. If you think that going through an 8 bit data sheet is daunting (not saying that you do) try a much larger family data sheet and then another 15-20 very large and specific data sheets for all of the functions/categories.

I reached a decision that I would do what they (Microchip) want because, in my view it is easiest and best until I get to a point where I can see otherwise. IOW I am trying to look forward.

That also means deciding not to use any legacy peripheral libraries. They even issue a warning that they will likely be dropped in future xc32 versions. That means getting into the Harmony libraries. That does not mean, however, getting into Harmony projects. I wanted to stick to the CCI (Common C Interface) but I simply can't adhere to the no no sub-directories rule in the header specification. Once I am far along in my understanding and familiarity, I will go back and simply use correct paths. But, right now, I run into so many dependencies the paths get too funky. Again, give me some time.

Of course I am not happy about the price for an optimized xc32, but it is only a hope that it becomes a problem some day. In fact, taken together, all the compilers, the IDE, the assemblers...all free, it's pretty awesome.

Anyways, that's my story and I am sticking to it

When you get to the point where you can see otherwise there is always the MIPS toolchain if you want 'Bare Metal'.

https://evosyn.com/pic32img.html

This guide is for those who don't want to use XC32 or would like unrestricted optimisation options without paying out for the non-free Microchip compiler.

Since the PIC32 has a MIPS core, the Imagination Technologies (Who own MIPS) toolchain can be used to generate object code. Most programs should be able to be ported with a little effort.

"Codescape GNU Tools for MIPS - MTI".

 

Looking forward to the latest Dave Jones rant!!
Max.

Since there have been some recent posts/threads about a sale on the PICkit 3 (even though the 4 has been out for more than a year), I went to search for a Dave video and I can't find any. He mentions it in this video, but it is not a review. There are, of course, a few video reviews of the 4.

 

Not sure if he has one on the ver4 yet, but I was also alluding to the later one Dave did on the 3 regarding the MPLAB IPE which Microchip brought out due to the feedback they got.

Max.