Programming 32-bit Microcontrollers in C: Exploring the PIC32 (Embedded Technology)

I almost never give out five star ratings to anything, but I gave this one five stars because it is worth it.

Key thing to keep in mind if you do purchase the book, is that it expects you to already know the C programming language. No wasted space on trying to spoon feed C to newbies. So if you are new to C or have only used assembler in the past, it's time to get serious and learn C - download any of the free C compiler's from Microchip's Dev Tools web site, and then sit down and get ready to program a screaming fast machine.

A good book, nothing else out there like it on programming PIC32 in C. You should come to this with some experience in C, but it isn't absolutely necessary. I'm learning to program in C at the same time I'm going through this book. I'd give this five stars except it is sometimes lacking in explanations of new concepts.

I'd give it 4. The chapter sample code on the CD isn't well commented. On the other hand, if you copy the chapter sample code to your hard drive to use it, you can comment it yourself as you learn.

This is a must have for anyone building sophisticated applications for DsPic or Pic I found that most of what I wanted to learn was covered, and in a manner that was to the point coding wise and very easy to understand. I have programmed with Assembly and Basic for most of my Pic projects and yet jumping back into C was very easy with this book. I would highly recommend this to anyone interested in the 16 and 32 bit micros, even if you have limited C programming experience or limited understanding of the new PIC architectures. This is by far the best out of the top 3 books I have purchased since when I got involved with industrial controls using micro-controllers.

It's clear, concise and to the point. DiJasio does not ramble or go off on tangents as most books in this area do, and makes it very easy to just dive right in and start coding your own custom application based on his ideas. We will send you an SMS containing a verification code. Please double check your mobile number and click on "Send Verification Code".

Editorial Reviews

Enter the code below and hit Verify. Free Shipping All orders of Don't have an account? It does have some fun projects though and a web site with code examples used in each chapter. If you have more questions let me know, I have the book handy. I agree with the previous poster. I bought the book very shortly after it came out, you know, when there was no Kindle or iPad.

There wasn't really a huge amount I learned from it, but I congratulate the author on some pretty creative projects that really demonstrate what can be achieved if you have such direct hardware access. And that's the problem: This is a perennial problem.

At the time that the book was released, there was also a peripheral library for the PIC32 that made a half-assed attempt at unifying he peripheral set, but half the time you ended up hacking the hardware registers directly. The Microchip hardware abstraction layer guys can never make their minds up about what constitutes the right HAL or API or abstraction. Sometimes you used macros, sometimes function calls, sometimes either. In the end, end user firmware almost always ended up with a combination of direct register hacking together with API calls when they worked and were fit for purpose.

Harmony was meant to take us all away from that. But right now it's as much a barrier as it is an enabler, although the balance is very slowly going in the right direction. Regrettably, well before we get close to a reasonable solution, some CS guy with a shiny new MBA who's never seen a soldering iron or oscilloscope will step into the Microchip development tools chief honcho's shoes and tell us that system level programming in C is the wrong direction and Python with Hadoop is the way forward for resource limited low power devices, in much the same way as a bunch of Linux kernel "experts" came up with Harmony,.

I will never be able to understand why Microchip was never able to put together a HAL for the 32s. I can refactor it and expand it and be transparent to all the programs I've used it in. Also, being in charge of the compiler they could optimize specifically for the tradeoffs made such that latency or space used are minimized. Maybe too many teams working on the same thing without a clear direction? I've seen it plenty of times. On the other hand it seems they are getting better at cleaning the header files: I do like the code configurator and the Harmony as ideas but never used them.

• Programming bit Microcontrollers in C - Exploring the PIC32 mit Leseprobe von Lucio Di Jasio.
• The Role of Data at the Semantics-Pragmatics Interface (Mouton Series in Pragmatics [MSP]).
• Microcontrollers - Vyhledávání na theranchhands.com.
• Legend of Promise.

I think the implementation is not great. Also don't release it until is mature enough With I am assuming only MX It would be nice to have a reference of the core. It can help me avoid answering question on non existent registers. Data sheets are always hit and miss on core details.

Any discussion of Harmony will be out of date.