Forum Replies Created
-
Posts
-
Hi Alberto,
Well, no. It’ depends on your favorite way to use the BITBAND_SRAM() macro
The current macro definition is made so that you can use it in the following way:uint32_t myvar;
…
unit32_t *bbmyvar = BITBAND_SRAM(myvar, 0);If you define the macro in that other way:
#define BITBAND_SRAM(a,b) ((ALIAS_SRAM_BASE + ((uint32_t)&(a)-BITBAND_SRAM_BASE)*32 + (b*4)))
Then you have to use it differently:
…
unit32_t *bbmyvar = BITBAND_SRAM(&myvar, 0);To alias a given variable, which is bound to a given memory address, then you have to know that address.
The difference with BITBAND_PERI() is that the peripheral macros (for example, GPIOA_ODR) are nothing more than an address in the peripheral mapped region.
Hope this clarifies.
Hi,
Well, it’s tough for me to provide help without a more detailed scenario.However, this often happens for two main reasons:
- There is something wrong at SPI level, often a bad configuration of the SPI interface or a wiring issue
- Simply, the SD card doesn’t support the SPI mode. Try with “older” cards with a size of 2-4GB
An SPI protocol analyzer can help a lot in this phase.
Hi,
My book doesn’t cover the HRTIM timer.ST provides a dedicated application note about it:
https://www.st.com/resource/en/application_note/dm00121475-hrtim-cookbook-stmicroelectronics.pdf
Hope it helps.
Hi,
Sorry for late reply (I’ve to move this forum elsewhere since the email notification is totally buggy…..).There are several cheap and really good alternatives nowadays. I suggest you to have a look to Rigol oscilloscope up to 100Mhz. For example the DS1102Z is a best buy in that segment.
Also give a look to oscilloscope from Atten/Siglent: if you buy them directly from China, you can save up to $100.The hardware in your hands is sufficient for almost all book examples. So I think it’s ok to start with it.
So, forget the Arduino and go ahead with the book. If you give you time you should be able to start working with STM32 without problems.Hi,
Sorry for the late reply but email notifications are totally broken and I have to fix them.Well, your question is not trivial to answer. The learning curve of a complex STM32F4 MCU may be too steep if you are new to electronics and embedded programming. It depends a lot on the time you want to dedicate to the learning process. Sometimes you spent a lot of time just understanding the concepts before going into technicalities. I do all my best to keep things simple, but I assume you have a little of experience with embedded programming. You could start by learning simpler architectures (like Arduino) so that you can acquire the very basic concepts. Don’t give up, it’s just a matter of time.
I’m aware of the fact that we the advent of STCubeIDE (formerly Atollic TrueStudio) there is no longer need to use the toolchain described in the book. Few other things may differ.
I’m considering a deep update of the book, but in this period of my life I’ve no sufficient time to work on it.
Tough to believe, but writing a technical book is the most time consuming thing in the lifeI’m aware of the fact that we the advent of STCubeIDE (formerly Atollic TrueStudio) there is no longer need to use the toolchain described in the book. Few other things may differ.
I’m considering a deep update of the book, but in this period of my life I’ve no sufficient time to work on it.
Tough to believe, but writing a technical book is the most time consuming thing in the life 😀Hi,
I’ve in my plans to make a printed edition of the book, but I guess that I’m really far from making it.
In this phase of my life I’m very busy, and I cannot spend the necessary time needed to fix the current book to make a printed (and immutable) edition.The files are available here:
