Combining register access with mbed, what a glorious joke.
Whats complex on such a F0 DISCOVERY board? There's only 64pin MCU with neccessary supply decoupling. (Plus the standalone programmer, which can be easily disconnected). What more minimal would you need? Don't like the programmer? Snap it off the NUCLEO board.
Awww... OSH.. That explains everything. I usually do not do OSH, or support for other OS. I just dont care about apple, and unix people usualy help themselves better, than I possibly could.
What gives NXP for free? Professional design tools specific for the purpose or some huge eclipse/GCC nest? Have you ever tried such a Keil or IAR?
Yes, it also supports HW debuggers, single stepping, breakpoints, register evaluation, expression watching, etc.
I think you didn't understood my question. Your board has no capability of debug on its own, you need $20 + shipping + other turd $$ external programmer. This is only a complication, istead of having a single plug-and-work board for half the price.
I prefer to have the target board separated from the debugger, this is a more realistic scenario for custom PCBs
This makes no sense. On the first side you have a complete development board, on the other the application. What is the real advantage having development board separated in many pieces? Is this some illness from OSH, that every HW must be separated into so called "shields"? And as you said, it is only a preference, not any advantage.
Conclusion: With STM boards, beginner simply takes a board, and can work with it, having the full featured debugger already integrated on board, without the need of investigating how to connect those together.
As for the STM32 bootloader, I've mentioned the UART. If it is not enough, then read this
http://www.st.com/web/en/resource/technical/document/application_note/CD00167594.pdfOn NUCLEO boards with STLINK v2.1, mass storage file-copy programming also works. But as I (tried to) explain you, having no debugger is a crapped way how to begin with ARM. ARM is not an atmega328. It's not as stupid as arduino is, learning it without a debugger is almost impossible to do. (Or if you do, I suspect, the highest achivement is mbed and slaptogether libraries).
As I should remind you,
rwgast_lowlevellogicdesin wants to learn the proper way, from basics, low level. It is simply a waste of time for him, to begin with such things like mbed. It won't help him with anything.
I do and I chose the configuration of the ARM PRO MINI was chosen to be very practical. Suggesting that ST is the only good solution is not serious. Mine went to the trash (literally) because I found something that fit my goals better.
Thats exact. Fits you, not
rwgast_lowlevellogicdesin who I am trying to help, suggesting a solution.
Maybe I am too much affected by professional design, that's why I hate all that mbed and arduino stuff. But I have no problems with OSH. OSH is a really good thing, but must be done properly, so one could even use that to learn something. If I sounded to much offensive, sorry for that, but I really hate mbed and anything related to that. I would really like to help him, because it is a small mirracle, when someone has an interrest to acually learn MCUs properly. So I am defending him from the mbed world, not offending you or your work.
PS: ST offers a set of example codes for each peripheral on each productline of chips. These multiple examples are indeed useful for beginner and/or anyone else.
Y
//EDIT: Summary:
ARM PRO MINI:
- small
- nothing on it
- no debug (except using external tools)
- bootloader code inside
- single install IDE (but not sure if that is an advantage)
ST-DISCOVERY / NUCLEO
- bigger, because it simply uses MCUs with higher count pin packages
- sometimes useful hardware appears directly on the kit, such as: e-Ink display, STN LCD display, sound codec, MEMS microphone, USB OTG, gyro/accel or compass, external RAM, TFT LCD, power conversion stuff,...
- bootloader also inside, including USB, CAN, (ETH*?)
- no ide obtruded with that, free for your choice. (uggesting use of KEIL or IAR.)
- professionally written code examples, no mbed.
- HW debugger onboard, allowing to program&debug MCUs off board.
*not sure how it works, haven't worked with it yet.
Not much diference between those, but the requirement was STM32, so am I glad to help with that.