Your Microstick may support some of the small PIC32 as well. Look at the docs.
If you program in C, it won't be much different. 32-bit MCUs typically require more setup, but the compiler/IDE will absorb most of it.
Wanna the most flexible device on 32 bit?
http://www.cypress.com/documentation/development-kitsboards/cy8ckit-043-psoc-4-m-series-prototyping-kit
https://www.youtube.com/user/CypressSemi/videos
Your Microstick may support some of the small PIC32 as well. Look at the docs.
If you program in C, it won't be much different. 32-bit MCUs typically require more setup, but the compiler/IDE will absorb most of it.Unfortunatly not, my Microstick is this one: http://www.microchip.com/Developmenttools/ProductDetails.aspx?PartNO=DM240013-2
So I'd have to get another dev-board like the Microstick II.
And yes, I program in C.Wanna the most flexible device on 32 bit?
http://www.cypress.com/documentation/development-kitsboards/cy8ckit-043-psoc-4-m-series-prototyping-kit
https://www.youtube.com/user/CypressSemi/videos
I thought about PSoC also. But would it be the best bet to learn about MCUs and their peripherals?
Their IDE, being mostly graphical, seems to make everything too simple (?). And if I needed to work with another MCU, at work/school, I would have to learn everything again.
That's only my opinion and I may be wrong.
Also, I'd like to know if there are any good tutorials/books about these MCUs (the ones I mentioned in my first post).
look at the ST NUCLEO stuff = specially the 144 series.
you can get a 200MHz+ F746 for about 25Euro's with 144pins and ethernet and USB-OTG complete with a USB ST-LINK programmer on the board.
i dont think that can be bettered!
http://www.carminenoviello.com/2016/01/22/getting-started-stm32-nucleo-f746zg/
You setup the logic and analog peripherals in a graphical manner, but you still have to actually write code and program the ARM portion. That's the same as any other ARM MCU.
You don't even need to use Cypress' software to do that, if you don't want to; you can download any ARM toolchain and IDE you want, in fact PSoC Creator is using gcc-arm-eabi-none as the backend compiler, which is pretty much the standard. Also, their IDE is pretty good in and of itself.
Basically the "Schematic Editor" portion of PSoC Creator is used to setup and wire together the flexible analog (op-amps, ADCs, DACs, filters, etc.), logic (and/or/xor/not/flip-flops, etc.), communication blocks (SPI, UART, I2C, etc.), clocks and I/O pins.
Once everything is wired together you write code, program and debug in the same software, outside of the Schematic Editor mode. So in that regard it's just like any other IDE and compiler.
So yes, setting up and wiring together the peripherals is easier than most MCUs, but code is code.
Also, every MCU has a different set of peripherals anyway. A Cortex M4 part from ST will have a completely different memory map and set of registers than one from TI with the same CM4 core. (TI, NXP, Cypress, ST, etc. all buy the same IP from ARM, that is the MCU core itself, then they add their own set of peripherals; that's what makes each part from each vendor unique.)
So you'll always have to learn new stuff when moving between vendors; that knowledge is never portable.
when you say "ease of programming", do you mean writing the code, or uploading to the device?
http://electronut.in/stm32-start/
look at the ST NUCLEO stuff = specially the 144 series.
you can get a 200MHz+ F746 for about 25Euro's with 144pins and ethernet and USB-OTG complete with a USB ST-LINK programmer on the board.
i dont think that can be bettered!
http://www.carminenoviello.com/2016/01/22/getting-started-stm32-nucleo-f746zg/
Yes, I've looked at the STM Nucleo boards, especially at the smaller ones, that you can put on a breadboard. I don't really need the power of a Cortex M7, a M0+ would really be enough for what I do right now.
But STM has me somewhat devided. The parts are cheap (so are the dev-boards) but for what I have read, they are less straight forward to program.
Does anyone know how does STM compare to NXP or Atmel SAM in terms of ease of programming?You setup the logic and analog peripherals in a graphical manner, but you still have to actually write code and program the ARM portion. That's the same as any other ARM MCU.
You don't even need to use Cypress' software to do that, if you don't want to; you can download any ARM toolchain and IDE you want, in fact PSoC Creator is using gcc-arm-eabi-none as the backend compiler, which is pretty much the standard. Also, their IDE is pretty good in and of itself.
Basically the "Schematic Editor" portion of PSoC Creator is used to setup and wire together the flexible analog (op-amps, ADCs, DACs, filters, etc.), logic (and/or/xor/not/flip-flops, etc.), communication blocks (SPI, UART, I2C, etc.), clocks and I/O pins.
Once everything is wired together you write code, program and debug in the same software, outside of the Schematic Editor mode. So in that regard it's just like any other IDE and compiler.
So yes, setting up and wiring together the peripherals is easier than most MCUs, but code is code.
Also, every MCU has a different set of peripherals anyway. A Cortex M4 part from ST will have a completely different memory map and set of registers than one from TI with the same CM4 core. (TI, NXP, Cypress, ST, etc. all buy the same IP from ARM, that is the MCU core itself, then they add their own set of peripherals; that's what makes each part from each vendor unique.)
So you'll always have to learn new stuff when moving between vendors; that knowledge is never portable.
OK, I think I understand you.
So what would you recomend to a "beginner"?
Check these out:
https://www.youtube.com/playlist?list=PLPW8O6W-1chwyTzI3BHwBLbGQoPFxPAPM
Videos use the TI Stellaris/TivaC Launch Pad board with ARM Cortex M4F. The videos are very informative.
The PSoC is a good place to start for any skill level I think. Their driver library is very easy to use and all the components have full documentation (on PDF no less) showing you what all the code functions do along with how to setup the components themselves in the schematic view.
I'd recommend picking up the $10 PSoC 5LP kit to start with. It's their high end chip, which can plug right into a breadboard and includes a little USB programming dongle. It might just be the best deal going right now, in terms of dev kits.
I can also recommend TI's LaunchPad line of boards as a very good value; their hardware is very easy to use, too. Look at the Tiva C LaunchPad if you want speed (it's a Cortex-M4) and the MSP432 for low power (it's a CM0).
If you're already using MPLABX and the PIC24, then the PIC32 would be the easiest. You already have the tools and know how to use them; at most you'd just need to download the PIC32 compiler.
I have not found the PIC32 to be harder to get started with (at the blinking LED level) than the other PIC's. Of course the PIC32 has tons of complex features but learning to use those is not obligatory and is just a matter of studying the data sheets and programming guide.
Microchip has a nice selection of inexpensive PIC32 dev boards on their MicrochipDirect online store. If you are a student with an .edu email you can get 25% off last time I checked.
Thank you for your opinion! I have to search a bit about the several PIC32 series (MX, MZ, MM, MK).
and the MSP432 for low power (it's a CM0).
MZ is a performance chip. Can run at 250 MHz. It has FPU, DSP and core which can use MicroMips. But, IMHO, the CPU runs faster than periphery can handle. It still has very nice performance features such as 3 MHz ADCs, high speed USB etc.
All those multi 100 mhz chip runs much faster than the peripherals, the high speed is just there to crunch numbers.
Re: new parts It's been about a year but "soon" 32MZ DA with display controller should come out. that is going to be interesting. Anyway, page is up and everything. still no datasheet
Also, there is the pic32wk (which is inside microchip's wifi modules) you can find a datasheet but no product page
MK is for industrial stuff (which is great!!) even though i could see myself use one for our automotive modules (4x CAN and a crapton of timers, IC and PWM, which our current dspics of choice lacks)
in this case i am thankful that the core speed is that higher than the peripherals so that everything can be in order before the next operation
Sadly, no high speed (sub ns resolution) pwm like in one of the aforementioned dspic (this is an if-only moment, just like if only the mx had 12 bit adc)
datasheet is there http://www.microchip.com/design-centers/32-bit/architecture/pic32mk-family
yeah, seems like the peripherals are better,
pic24 : pic32mx = dspic : pic32mz/mk
Keep in mind that these high speed mcus also have caches, which may give unexpected results in first projects.
then i suggest you set up your projects + clock tree with harmony so that you have the startup code ready and then give it the middle finger and access the peripherals directly if you can
this at least is what i'm doing, because i'm not expert enough in pic32 to write my own startup code yet (i've only played with them so far, nothing for work)
unfortunately these new cores are very pricey, i don't know how much it's worth it to use them instead of arm counterparts
though arms with all those peripherals, M4F/M7 core are not being sold for peanuts either
Sorry for answering so late.
So, I've decided to go for PIC32...
Just have to choose the line. All of them have curiosity boards except for MK...
Which one would you go for?