You are welcome! I will try to load the USB bootload and I will prepare a tutorial! Cheers!

cbm80amiga Thanks buddy

Using along with C is better than Arduino IDE

Not exactly because thanks to same API I can easily share same code/libs between ESP8266 and STM32. STM32 is more convenient for prototyping more advanced projects for ESP8266.

Hi - thanks very much for your excellent videos! For using USB: please do not forget to check the resistors on your board, ref here: amitesh-singh.github.io/stm32/2017/05/27/Overcoming-wrong-pullup-in-blue-pill.html All the best, Christine

I'm working on a power wall of my own, do you have details on your BMS?

i tried this STM32F103C8T6 but still noisy unstable adc so i went to STM32F407VET6 with Vref and was just perfect.

I like the ADS1115 i2c ADC, it has a builtin 4.096v reference as well as an adjustable amplifier and 16/15 bit resolution.

ADS1115 i2c still common to fail when switching inductive loads plus much slower response than built in adc mcu. yes for limited simple resistive load slow measurement applications, but still if you add it to the price to the mcu it wont be economical.

I have done so already using Arduino pro minis but their ADC are only 10 bit. You can find it on my channel.

Friendroid HAhahahaha just loved your comment. Really made me laugh.

giveup porn to arduino/stm32 is a wise choice

Be smart be like Friendroid,lol. XD

There is plenty of time in life for both

Lol

the STM32F103C8T6 supports usb communication so there is no need for USB-UART converter. You can upload via usb if you flash usb bootloader. there are tutorials all over the youtube on how to do it.

I have a hard time haring the words but the English captions make perfect sense

Cool! Thanks for sharing!

I started discovering arduino in the last 2-3 weeks and I already hate it. The hardware (choice of the mcu) is horrible, programming via serial is a kind of useless approach (integrated ch340 ic). It has a usb socket but you can not use it as usb device, because it is just an usb-rs232 converter. If the board has a usb socket it should be connected directly to the mcu usb port, and the boot loader should emulate an rs232 port, or other device. STM32 seems to fix this issue. The arduino framework is easy to use for some fap-off projects, but uses horrible implementations for timing-important jobs. The atmel mcu is very slow, and has incredibly small sram. I personally doesn't have any problem of just a few kBytes of ram, if you program in assembly. About 20 years ago i programmed a lot pic and dspic mcus in assembly, it was a pain in the ass to make very complex firmwares (for example rtl8019 dirver, ftp server, ata hdd controller), but because of the asm language i needed to use just a few hundred of bytes of ram. But these boards are meant to program in C++, and only the arduino framework after compiling takes more than ~700 bytes of ram, and more than ~10 kbytes of program memory. Not counting the boot loader. Almost no space for any useful. Declaring an int[1000] array is just a no-no. Accessing the GPIO pins is the slowest i have seen, just after a few days i had to create my own GPIO control library to minimize the access timings with inline asm operands. Arduino is easy to use, but if you are using that framework then forget the arduino hardware. I moved very fast to STM32, and now i can say we are going somewhere. Advice: Use the ST-LinkV2 programmer, Visual Studio Code, and install the PlatformIO extension. When you create a new project just select the board, you can choose from 4 frameworks (stm32, arduino, etc...), it will automatically detect the programmer and you can upload just by one click. It has a built in serial terminal for debugging. Very nice IDE with a minimal effort to set up. Even runs on linux exactly the same. I say if you are doing just some wanky projects like proof-of-concept then arduino hardware and framework is ok, but when you really want to hack-in some timing-critical and optimized code, then go STM32 and don't be scared to override the arduino framework with some own implementations, like inline asm operands. Have fun!

@@resetcoder Hey, cheers for the lengthy coverage. I was keen to use the STM32s and got in quite a few of them as they're so cheap. I still plan on giving them some life, but it was taking too long to set up on Linux. I was able to get the Nucleo boards to work, but they have the debugger built in and using Cube IDE certainly takes care of the most difficult part of setup. I was using STM32 on PlatformIO with ST-Link V2 and the Arduino framework; as you suggested. I got the gdb debugger running, but then wasn't able to upload any code. I searched for some solutions, tried them out, but didn't get the end result I needed at the time. I managed to upload a blinky via serial, but I was over it by that stage. Arduino is perfectly fine for the project that I'm working on as the process parameters aren't time-critical. I'm just creating my own interfaces from sensors to bus and the measurements that I'm dealing with don't change much due to thermal capacity, CO2 which doesn't change too rapidly, pH and some SSRs. I'd like to code the STM32F1s using assembly at some stage, but only so I can get a better understanding of the ubiquitous ARM Cortex architecture. I haven't written assembly for over 20 years now and it certainly seemed less complication on the HC11, 8086 and Heathkit Trainer. It's certainly a valuable exercise once the pain of getting started wears off. Do you know of a good hands-on resource that leaves nothing out from the get-go regarding ARM assembly and open-source/free software? When digging this deep, the idea of scaffolding an application using CubeMX or GNU ARM and then filling in the blanks removes critical steps in getting things going. I'd love to be able to walk through each step of what goes in the linker file, critical config code, jump instruction and whatever else after that. Cheers

@@WayneRiesterer To be honest I don't use debuggers, even though I know they are useful, so I can not recommend anything regarding this topic. I just write the code, upload, test, if something is not working I just send back debug info or "break point marks" via serial, blink leds, or write on display, and I debug myself, usually I don't get stuck so much to need debugger. If platformio can upload the code and it is running then I'm happy. Still much easier than back in the days when we had to build and program the programmers for the mcu's. I'm more familiar with RISC asm than 8086 because I programmed PIC's only in asm (the compiler was shit, it is still shit, and probably will be shit), but now I had to implement some asm code to Atmel mcu, which isn't RISC, so it was a bit different, but the main stuff are the same. I can not recommend any tutorials or books about how to start it from scratch, but if you did already some code in asm, then you don't even need it. I recommend checking useful codes, libraries, how others did an optimized workaround in asm, like xmem for display driving, it is a very very interesting approarch how to fill the holes between Cpp and performance. (This a very interesting library by someone who knows what he is doing: andybrown.me.uk/2012/07/28/interfacing-the-nokia-6300-qvga-tft-to-the-standard-arduino/ and kzfaq.infovideos [sorry for the external links, but it is important info]) I did the same, just you need to search the internet exactly for what you want, and you don't need to learn the complete asm if you need only a few things. Cpp is a very good language for mcu programming, it avoids the struggle that asm makes for you, but sometimes the compiler even with strong automatic optimization can not do the straight job you need with inline asm blocks. Just simply override with your code what is crap in the framework and you won't lose much time with overcomplicated solutions, at the end you may extend or improve the framework or create an own. I sometimes use VSCode+PlatformIO on linux, sometimes on Windows, depending on where or what I'm working on, but to be honest I didn't try the STLink under linux, probably only a driver is needed to make it work, but in the worst case you still can upload your code via serial. I'm not saying arduino is useless, but it is like having a 4 floor house with the 3. and 4. floor having a wall to make you unable to access them. A lot of people saying "it is enough for me", but then why not just having a 2 floor house? Actually the atm328 with its 8 or 16mhz and (if I remember right) 2kB of sram is actually capable to do a lot, if you write pure asm code and forget the framework. But for very simple things it is OK, I can get over of the "overkill" because the arduino framework eat up the rest of the mcu. I don't say I will never use them, actually still having a project on a Nano board, but I'm pretty sure I will move to STM8/32 mcu's everywhere it is possible. They are not more expensive, but much better. The point of what I'm saying: Debugging is a secondary priority, first have a good IDE (like vscode), a programmer (like serial or stlink), and a debug info channel (like serial), if the setup works, you are almost ready to do anything you think of.

@@resetcoder Thanks again for all the info. I'll be continuing with the project as is for now, but in my spare time I'll certainly be trying to get my head around the Arm-based technology. I like the idea of learning an architecture that is very similar across device families with varying capabilities. It smooths out the learning curve a bit because the knowledge gained is transferable. As far as the tooling setup issues go, I've just purchased a license for Windows 10 and will set up a dual-booter some time next week. There's heaps of videos that show how easy it is to get started on STM32 using Windows. Incidentally, I found that the Arm courses are quite affordable. They also sent me a free one month trial offer, but it seems most of the training uses Keil; which is super-expensive for an enthusiast. Still, the knowledge and skills will at least in part be transferable and useful in developing with the GNU Arm Toolchain. So much to learn and so little time and money.

@@WayneRiesterer Good luck to your plans! Btw I sometimes when I need mixed environment (which happens very often) then I just run linux or windows in virtual machine, no need the hassle of the dual boot. But it is always depending on the needs, sometimes it is better to boot to another os, or have multiple computers around you.

Thanks for that! Things have changed since I published the video...

@@Educ8s welcome and Thanks for your videos. Can you please make video of stm32 with ili9341 tft touch screen , i have problem with the arduino ide library and no one in youtube explains this

@@eng.salahawwad I will note it down to try it.

@@Educ8s thanks, appreciated

I use System Workbench to program Blue Pill in C. Also STM32CubeMX to set up the clocks, pins and peripherals and create the project for System Workbench. Works perfectly. I've been using ST-Link as the programming interface. Top tip: in STM32CubeMX make sure to enable the Serial Wire Debug under System Core>SYS, to avoid bricking the programming interface. :-)

Yes, it sounds great! I will try it!

I will try to test different display with this board and I will post my findings. So far the ST7335 and the Nokia 5110 work great with this board!

I am glad it was helpful! Cheers!