• State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 22 subscribers
  • Views 2813 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Migrating from PIC18, getting started with Cortex M3

Sam Byte

Hi All,
I've been eyeing on Cortex M3, namely STM32F207ZG to get started with ARM, simply because there's a cheap development Board at eBay. I can be considered as a pro with Microchip PIC, mainly using Mid Range 8-bit PICs, Microchip ASM and Hi-Tech C. But I need guide from all of you guys to jump start. Keil was recommended by the eBay seller and so I'm here. What is the recommended debugger/programmer? What are JTAG/SWD? As for PIC I'm using PICKit2, MPLab ICD2, ICD3.

Thanks
Sam

Parents
  • 0 in reply to Sam Byte

    Two biggest differences:

    1) lower-end PICs don't have vectored interrupt. This makes modular programming a little bit difficult.

    2) the clocking options are generally much more on the CMx chips than on the PICs. This can be challenging to new programmers. Luminary does a great job of having code example C code that shows how to set up a peripheral, to get a new user going.

    Other than that, they are fairly transparent, as long as you code in a high level language.

Reply
  • 0 in reply to Sam Byte

    Two biggest differences:

    1) lower-end PICs don't have vectored interrupt. This makes modular programming a little bit difficult.

    2) the clocking options are generally much more on the CMx chips than on the PICs. This can be challenging to new programmers. Luminary does a great job of having code example C code that shows how to set up a peripheral, to get a new user going.

    Other than that, they are fairly transparent, as long as you code in a high level language.

Children
No data