2016-10-26 11:34 PM
I have the evaluation board for stm32f429. But almost all the support is given to discovery board. Many codes which is useful is done in the discovery board. How can i convert that code to fit in the evalaution board? What all changes I have to make? Can anyone tell hoe I can convert that same program to fit my MCU board?
2016-10-27 01:44 AM
Hi sunny.dixon_p,
Only the board specific features need to be ported or simply comment related code. Then the same application should run successfully.If you start from a Cube example, you should find similar examples for discovery and eval board (not for all cases for sure).If it is your own application, you may refer to the template projects.-MaylaTo give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2016-10-27 09:03 AM
You'd start with an appreciation of the schematics for both boards, and the pin utilization for the assorted peripherals and external hardware. You'd then use that and the Data Sheets and Reference Manual to adapt code from one board to another.
Not sure there's an App Note for it, as it's a frequent task for an embedded software engineer.2016-10-27 11:34 PM
2016-10-27 11:37 PM
2016-10-28 12:40 PM
Ok, but at some point you're going to need to get an appreciation for what a limited set of pins is going to afford you in terms of escaping peripherals. You will need to review the Data Sheet for the pin functionality
http://www.st.com/en/evaluation-tools/stm32429i-eval.html
If you feel the DISCO has more examples of what you need, then get one of them, they cost a fraction of the EVAL board. Cube has examples for all the boardsDirectory of C:\...\STM32Cube_FW_F4_V1.9.0\Projects
10/12/2015 05:13 PM <
DIR
> .
10/12/2015 05:13 PM <
DIR
> ..
10/12/2015 05:11 PM <
DIR
> STM32446E-Nucleo
10/12/2015 05:12 PM <
DIR
> STM32446E_EVAL
10/12/2015 05:08 PM <
DIR
> STM32469I-Discovery
10/12/2015 05:09 PM <
DIR
> STM32469I_EVAL
10/12/2015 05:11 PM <
DIR
> STM324x9I_EVAL
10/12/2015 05:13 PM <
DIR
> STM324xG_EVAL
08/14/2015 08:18 PM 143,540 STM32CubeProjectsList.html
10/12/2015 05:13 PM <
DIR
> STM32F4-Discovery
10/12/2015 05:13 PM <
DIR
> STM32F401-Discovery
10/12/2015 05:11 PM <
DIR
> STM32F401RE-Nucleo
10/12/2015 05:13 PM <
DIR
> STM32F410xx-Nucleo
10/12/2015 05:11 PM <
DIR
> STM32F411RE-Nucleo
10/12/2015 05:10 PM <
DIR
> STM32F429I-Discovery
10/12/2015 05:13 PM <
DIR
> WIN32
What examples are you specifically trying to evaluate or port to your platform?
There isn't some magic answer here that's going to avoid some effort and due diligence on your part.
Perhaps you might want to talk with others in your project group, or within your company, with more experience porting code between platforms or chips.