About BCrow.1

BCrow.1 · 2020-02-03

I have tried using the HAL_I2C_Master_Transmit_DMA and HAL_I2C_Master_Receive_DMA functions to access an external I2C slave but I find that this takes a fair amount of processing time. I am using a STM32L476R M4 core device. Using a GPIO I measure th...

BCrow.1 · 2020-01-30

I am doing a DMA based I2C transmit using HAL_I2C_Master_Transmit_DMA and am seeing an issue with the state of the I2C. The transfer completes as expected as confirmed using an oscilloscope on the pins. However, the state of the I2C gets switched to ...

BCrow.1 · 2020-01-07

I am able to open an example project and debug that without issues. I have tried regenerating my project, generating a new project, and even reinstalling the tool and generating a new project, but I still get the same error on debugging. I can still ...

BCrow.1 · 2020-01-06

BCrow.1 · 2020-10-15

If I remember correctly it was the I2C event interrupt. You need the DMA interrupts enabled as well to manage the data with the callback function for those, but if the event interrupt isn't enabled you'll get stuck in the busy state. I am using the S...

BCrow.1 · 2020-02-03

Thanks for the state machine thought. That might be something to look into for my system. It's not the I2C bus time itself that I am worried about. I was hoping that the DMA mode of operation would allow me to set up an access and then just go off an...

BCrow.1 · 2020-01-30

I found my own answer. I had an interrupt issue as they were not properly enabled.

BCrow.1 · 2020-01-07

Just as suddenly that this stopped working for me it seems to have started again. I put a delay call in the while loop of main and it now no longer gives me the above error. I commented out the delay call and it still works???

BCrow.1 · 2020-01-07

Thanks for the help in pointing that out. The documentation points toward the website for examples, which confuses the issue somewhat. Thanks for clearing it up for me.

User statistics

User Activity

What is the least CPU intensive way to access the I2C bus?

Why does the I2C state remain in HAL_I2C_STATE_BUSY_TX when an access is completed.

I am using the STM CubeIDE with a Nucleo L476RG dev board. When I first generated a project I was able to download it to the card and debug. then for some reason I started getting an error saying the arm-none-eabi-gdb.exe has stopped working.

I am just starting to use a Nucleo-L476RG demo board that comes with code that flashes the LED at fixed rates selected by the switch. Where can I find the source code for that application?

Re: Why does the I2C state remain in HAL_I2C_STATE_BUSY_TX when an access is completed.

Re: What is the least CPU intensive way to access the I2C bus?

Re: Why does the I2C state remain in HAL_I2C_STATE_BUSY_TX when an access is completed.

Re: I am using the STM CubeIDE with a Nucleo L476RG dev board. When I first generated a project I was able to download it to the card and debug. then for some reason I started getting an error saying the arm-none-eabi-gdb.exe has stopped working.

Re: I am just starting to use a Nucleo-L476RG demo board that comes with code that flashes the LED at fixed rates selected by the switch. Where can I find the source code for that application?