2011-01-05 03:18 AM
Moving from AVR to STM32 -- starter questions
2011-05-17 05:20 AM
About EEPROM, it seems I've found app note:
AN2594 EEPROM emulation in STM32F10x microcontrollers
2011-05-17 05:20 AM
About EEPROM emulation, see:
[DEAD LINK /public/STe2ecommunities/mcu/Lists/ARM%20CortexM3%20STM32/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/ARM CortexM3 STM32/hi,&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000626BE2B829C32145B9EB5739142DC17E]https://my.st.com/public/STe2ecommunities/mcu/Lists/ARM%20CortexM3%20STM32/Flat.aspx?RootFolder=%2fpublic%2fSTe2ecommunities%2fmcu%2fLists%2fARM%20CortexM3%20STM32%2fhi%2c&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000626BE2B829C32145B9EB5739142DC17E2011-05-17 05:20 AM
Thanks for the response! What about other items, what IDE\compiler do you use?
2011-05-17 05:20 AM
I bought ST-LINK at DigiKey and it didn't work at all. Just lost my money.
2011-05-17 05:20 AM
2011-05-17 05:20 AM
Thanks for the response! What about other items, what IDE\compiler do you use?
It's probably not GCC, and your original question seems to be artificially constrained. I think RIDE, ROWLEY and ATOLLIC use GCC, but it's hardly what I'd call an ''embedded'' compiler. Of those I would choose Rowley, or just use WinARM or Yagarto. I'm also not sure what ''community choice'' is. Is it code for free or cheap, or runs under Linux? Development environment choice is typically personal (what you like/prefer), or corporately driven (what the vendor/customer uses). The aggregated opinion of the forum is unlikely to result in a single clear answer, everyone will have their own preference, usually a strong one. The Keil or IAR demo/eval versions would be my suggestions. Atollic Lite is so broken/crippled/slow as to be unusable, and the buy-in prices for the TrueStudio could get you equivalent Keil tools with a lot more mileage.2011-05-17 05:20 AM
BTW. You will need a JTAG Programmer Ulink oder IAR-Link. RS232 Serial programming is a pain in the...
He's using a VL Discovery board, with the built in ST-LINK. Notwithstanding that programming with the serial port is *not* that hard and readily implemented on a production line, for debugging you do indeed need a decent JTAG or trace tool.2011-05-17 05:20 AM
''I can't speak to it's effectiveness for debugging''
I use Keil, but it seems to me that by far the biggest problem with all of the free GCC-based things is getting debug working! With Keil (and IAR), you get a complete kit that ''just works''; with the free GCC-based things, you get the compiler from here, the debugger from there, a patch from somewhere else, pull together a few forum threads to configure it, etc, etc, etc,... Well, that's the way it looks to me, anyhow!
2011-05-17 05:20 AM
Thank you for the responses, you are absolutely correct about ''It's probably not GCC, and your original question seems to be artificially constrained'', I just have last hope that something like WinAVR exists for STM32. It seems IAR is the way to go for me (at least it seems to be the most popular).
Some other questions left: - Will ST-Link part of STM32VL-Discovery work with other STM32 controllers, for example F103 line? I assume the answer is ''yes''?