All code working now in all the UART devices. Checked several times, as it is usual, some pin confusion.
This events information is very usefull but it was really a pain to find it, it would be nice to have an example like this documented somewhere else, but for the mean time this will do.
Today I come here because I used event for SERIAL Driver input a long time and now with the new functions I was testing its functionality as seen in this post: http://forum.chibios.org/phpbb/viewtopic.php?f=2&t=872 .
Giovanni: My CPU doesn't get stuck anywhere, the execution is run normally. barthess: The function successfully returns and status==RDY_OK and errors==0. Indeed it returns 0, but instead other data should be returned. Is weird that the eagletree page is ...
With a little shame I come here asking for assistance. I was trying to read Altimeter V3 and Airspeed V3[1] sensors from Eagletree, which have a I2C bus to acquire its raw data. Eagletree provides information on how to use this sensors, the I2C addresses and pseudocode to access it[2 ...
It was indeed a DMA channels problem, I updated my trunk, changed I2C1 DMA channel and problem solved. Once I fixed it, I tried reading and writing to a BaseChannel in a SerialDrive, but for a high amount of iterations, it seems to create a system lock, so UART driver ...
Ok, found the posible DMA ids in the hal_lld.h file, but when changing STM32_I2C1_TX_DMA_MSK from (STM32_DMA_STREAM_ID_MSK(1, 6)) to STM32_DMA_STREAM_ID_MSK(1, 7)), the system stops working (I tried this in the discovery F4 demo).
Could this be a DMA related issue? the debugging hasn't been ...
Greetings, I am using various available serial protocols in stm32f4 discovery board. I am using the USART driver and Serial Driver.
When I use SD4 in pins PINA1 and PINA0 with USART3 in pins PINB10 and PINB11, everything works fine, but when I add Serial Port 2 (with Serial Driver or USART driver ...