2013-09-16 11:19 AM
http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF259090
http://www.st.com/st-web-ui/static/active/en/resource/technical/document/data_brief/DM00094498.pdf
http://www.digikey.com/product-detail/en/STM32F429I-DISCO/497-13898-ND/4310131
2013-12-16 08:50 PM
I agree with Clive1 , someone needs to look into the issue with the lcd. Mine also arrived with lcd out of the metal frame. I tried to get it lock back in to no avail. Finally go out the hot glue. A little hacked for a brand new board. Also could not get any of my flash drives to work with the demo. I have 5 sandisk from 1 to 16 gb. I could use my 1 and 2 GB on the stm32f407 discovery . The touch screen seem to lag on the demo as well , not very sensitive, even using my best stylus. Still will like to see how useful it will be with the external ram.
2014-12-21 06:02 AM
I know this is an old post. I'm trying to build this SDRAM example code with gcc arm embedded toolchain. The none-eabi linker is give me an error that .ARM.exidx overlaps .DATA section. I can't find .ARM.exidx section in stm32f429i.ld?
It build some .bin and .hex but no .elf I still did not try to run the binaries. I hope someone can still reply on this post.2014-12-21 07:46 AM
And you're doing this with what version of the GNU/GCC tools, on what platform?
I provided a MAKEFILE which works fine with GNU/GCC 4.7.2 under Yagarto2014-12-21 08:32 AM
I'm cross-compiling on a Win8 machine. I'm building the executable with make under cygwin env.
The toolchain is gcc-arm-embedded and the compiler version is 4.9.3.2014-12-21 11:12 AM
Suggest you review the linker scripts (.LD) they use, and adapt those to reflect the memory map described in mine.
2014-12-21 12:15 PM
I don't know if I'm in the right corner here to ask. If I use libc I get the linker error. Is libc compatible with stm32f429i.ld?
2014-12-21 03:01 PM
gcc-arm-embedded includes the red hat newlib libc 2.1.0
I try to figure out with the libc manual.2014-12-23 03:07 AM
The least resisant path was indeed to use the supplied ld script from gcc-arm-embedded toolchain and morph it to the map of stm32f429i.ld
In fact libgcc use the .ARM.exidx section.The stdio functionality. I conclude the newlib lib in YAGARTO is different build then the gcc-arm-embedded newlib.