About Breakthecake

Breakthecake · 2022-02-26

Master: STM32L476RG on Nucleo boardSlave: M95M01-A125, 1 Mbit serial SPI bus EEPROMI set up a SPI driver to study details how registers work and the data is out and in transmitted. The data flow works fine looking at the logic analyzer window. In thi...

Breakthecake · 2022-02-09

I am writing a SPI driver for STM32L476RG, which is on a Nucleo board. First use: Communicate with an EEPROM to see how SPI works, logic analyzer records the bits. The slave seems not to react. I found out the /NSS pin is never High. As far as I get ...

Breakthecake · 2022-02-28

Thank you for this valuable information! Now I am curious, where I will find the information "in the toolchain" about registers read, when using (no) breakpoints (in general or whenever). :smiling_face_with_smiling_eyes:

Breakthecake · 2022-02-27

Hi TDK,`> while( !(pSPIx->SPIx_SR & (1 << SPI_SR_TXE)))This is nonsense. Well, I would not agree. You may not imagine the macro standing behind SPI_SR_TXE, which is used in my code. #define SPI_SR_TXE 1and same for your 2nd example#define SPI_CR2_D...

Breakthecake · 2022-02-18

Well TDK,I think there is a misunderstanding. I was commenting on //8 bit transfer ,pTxBuffer = pointer to uint8_t *((uint8_t*)&pSPIx->SPI_DR) = *pTxBuffer;As mentioned, a teacher on a course using the stm32Fxx type did not have to code like thi...

Breakthecake · 2022-02-17

I can confirm that's the way to code it! Funny, the teacher of the online course coded like Tbone in his first quote and it seemed to work fine for the stm32Fxxx µC, but not for the L-type! Of course, this is not documented in the ref man. Dear ST st...

Breakthecake · 2022-02-15

Hi Tbone,maybe we both take part in the same online course ... ;)Why do you choose software slave management and configure the /NSS pin? - By the way, in case you prefer to use the /NSS pin, use an external pull-up resistor or configure the GPIO to u...

User statistics

User Activity

SPI communication using own driver for blocking call: Transmit/receive works fine, but I cannot get the data into the RxData array for later use.

Setting up GPIO and SPI for hardware slave select management. /NSS is never set to HIGH. Is there a bug?

Re: SPI communication using own driver for blocking call: Transmit/receive works fine, but I cannot get the data into the RxData array for later use.

Re: SPI communication using own driver for blocking call: Transmit/receive works fine, but I cannot get the data into the RxData array for later use.

Re: Question on SPI communication

Re: Question on SPI communication

Re: Question on SPI communication