![]() * setup uart port */ dev_uart_add ( & dbg_uart ) /* set callback for uart rx */ dbg_uart. So, let’s have a look in the main() function to explain what is going on there. You can use this as a cmake template to build your own stuff on top of it. This template is quite simple, just a blinking LED and a USART port baud-rate. You can download the source code from here: And it seems that is working just fine, at least both of my boards worked fine with the overclock. Neat.Īnd yes… In this project you’ll get an stm32f303k8 overclocked up to 128MHz (if you’re lucky). But… I needed also to do something stupid on top, so I’ve decided to add in my template a way to overclock the stm32f303. So after loosing 30 mins from my life, I’ve decided to make one of my standard cmake templates. This is not a professional tool and Hobbyists have much better tools like the various Whateverduinos. Sorry ARM, but I really can’t understand who’s using this thing. I mean, who the heck is going to develop on an online IDE and compiler and do development on libs that can’t have access to fix bugs or hack? What a mess. I’ve tried mbed before, but that was a lot of years ago when it started and it was meh, but I didn’t expect it to be still so much. ARM elevates that domain to a very high standard, which is difficult to compete. So, after spending ~30mins I found out that I’m not the only one that does stupid things. Then I’ve seen this ARM mbed enabled thing on the case and although I was sure that it would be something silly, I wanted to try it. I’ve plugged the USB cable, the leds were flickering, cool. ProjectĪfter the initial sock, I said to myself, ok let’s do something simple and stupid at least, just to see that it works. Enough goodies for my happiness meter not to drop that much. But, it still has all the other goodies like 2x DACs, opamp, ADCs, I2C, SPI e.t.c. ![]() I’ve also realized that the stm32f303 was the small brother of the family, so no USB anyways, no much RAM and several other things. After reading the manual (always RTFM), I’ve realized that the USB port is not connected on the stm32f303 and the stm32f103 was the on board st-link and I’ve also realized the reason that the board was a bit more expensive than I expected (though Arrow had a lower price compared to others). Of course, I’ve spontaneously forgiven myself, so I can repeat the same mistake the next time. Oh, wait… Oh, nooo… And then I’ve realized all the reasons why you should always read the text around the pictures before you buy something. ![]() So, I got home and opened the packaging and BOOM! WTF is this?!? Why does it have 2 mcus? Where is the connector with the SWDIO and SWCLK pins to flash it with my st-link? Why there’s also an stm32f103c8t6 on the back side of the PCB? What’s going on here? It shipped faster and I don’t have to do any soldering. Therefore, as a proper engineer, I’ve order two boards (one is never enough) without even read the details and after a couple of days these boards arrived.ĭouble win I thought. And before do those changes, then one day BOOM! I’ve seen this NUCLEO-F303K8board, that looks like the blue-pill and said, ok, lets order this and screw the custom board, who cares. In the meantime, I’ve delayed the PCB order because I wanted to do some changes, like use 0603 components and remove the extra pad areas for hand-soldering. The difference is that I’ve used the stm32f373c8t6. Note: because I had to recover the db and there wasn’t a backup of this post, the oscilloscope screenshots and the comments were lost □įew weeks ago I’ve done a stupid project herein which I’ve designed a small deb board that is similar to the blue pill board (which uses the stm32f103c8t6).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |