AnsweredAssumed Answered

When moving to less pins/spec then MCU in dev kit

Question asked by new guy on Apr 10, 2013
Latest reply on Apr 10, 2013 by Clive One
Hey,

I would be grateful for some help - first time moving from dev kit to own board.

I have a software design based on the stm32 f4 G-Eval kit, developed using the g-eval libraries as the foundation. I am using Keil uVision 4 as my development environemnt.

1. In production, I will not need so many pins on the MCU as per the MCU in the G-eval dev board. Could you please outline what changes have to be made when you use an MCU with a lower number of pins? For example, for I2C1 do you simply select a lower MCU partnumber in the project settings and use the pins marked as I2C1 on the datasheet of that new MCU, or is there more to it? Are code changes to the library required or example?

 2. Likewise, when using a chip with a lower amount of flash memory etc than the kit, do you have to make any changes in code, or is it again simply a matter of changing the MCU partnumber in project settings?

Thanks

Outcomes