ahhh got it working, I had the wrong connections on my nucleo board - thanks for the tutorial

Which tables ? Please mention the time

@ControllersTech Oh, you replied, I did not expect that! Yes, sorry, I am a bit new to embedded Programming. I meant the last table you showed in the Video around 6:40. The one with the TEX, C, B, Memory Type, etc... I understand how it is connected with the topic of your next video, and I assume that the C, B, and Shareable flags are probably similar/the same in most mC/cache/memory/mpu systems. I still don't understand how i would know the TEX number. I also assume that this information you presented in the table here is provided (in some way or another) from the manufacturer. I use the same Board as you in your example videos, but was not able to find it in the Reference Sheet, or the "Basic user sheet". In the Reference sheet I only found something like the table at 1:52. I would like to know how you got/created the table, so i could be prepared when I am using a different Board. Sorry for the long comment, i hope i got across, what I meant! And in general thank you for your Videos, they are a huge help for me to get into Embedded systems!

These tables are provided by ST itself. I put them together by reading different docs provided by ST. They are not present in the reference manual or datasheet. You can find them on the ST's website where they explain about the MPU. These tables remains the same for all the MCUs.

@@ControllersTech That means I have to be aware of more than just the Manuals; It's also good to know that they are the same for all the ST-Provided MCU's. Thanks for the Pointers, that helped clear things up a lot!

Well you can't capture a 100% and 0% duty. You have to implement some other method for it. For example, create a variable and increment it in the systick handler. Also Reset the variable in the input capture callback. Now in the while loop, check if the variable value has exceeded some partiular time. Here for example, if the frequency of the signal is 100 hz, the interrupt will take place every 10ms. So we will check if variable's values is more than 20, if it is that means the interrupt did not trigger last 2 times and it would mean the duty is either 100 or 0.

Just look for the SPI pins. The rest will remain the same.

There are 3 separate links for each of them.

Of course not. That is a completely different thing. Once the power is reset, the entire code runs from the start, so this setup will also reset. If you want to preserve the values, store them in the flash memory.

@@ControllersTech Thank you for the info. I wanted to update/ store values every time the value is changed. Cycling through many numbers this might be huge amount of writes over time. What would you recommend storage type for continued values stored?

If you do want to retain the value through the power cycle, flash storage is a good option. Instead of writing every value, why not setup a timer to generate interrupt every 2 or 3 seconds. In the interrupt handler, you can store the current value.

Go to project properties -> C/C++ build -> Settings -> MCU/MPU Settings and check the printf_float.

You means at 12:00 ? HAL_UART_Transmit takes the pointer to the variable as the parameter. Therefore we need to pas the address of the variable.

Glad you are enjoying the tutorials! Keep practicing and you will master it.

Did the code flashed successfully? You Probably have the cloned mcu.

@@ControllersTech working correctly, I checked and had misconfigured my external clock frequency, I corrected it and now it works perfect, tested and working on STM32WB55 WeAct board

the maximum frequency measured was 12.8MHz as the board only runs up to 64Mhz and this was the maximum stable pwm frequency I could achieve

This is just what I was looking for, since I want to develop a low-cost and high-performance oscilloscope, I know I need a microcontroller with a higher frequency, but while I investigate I am learning the methods

Now, with the comparator embedded in the board we could try to use the same method with a sine signal to transform it into PWM pulses, and thus calculate its frequency, although with this method we could calculate the frequency but we could not visualize beyond the sample rate of the adc, anyway it would be a great advance and then an external adc of 50Msps could be implemented, But that would be another stage

Did the previoud parts worked ?

Sure! I might make one in the future.

What do you mean "pwm signal was 0"?

I am setting it in the program. The scan mode is automatically enabled when you choose multiple channels. Anyway it doesn't matter if we are using rank 1, so no harm.

There is no advantage. Some people prefer not to use it, so this video is for them.

the 3.5" TFT LCD shield has the same pin and layout with 2.4" "