Hi
When I use I2C library without Keil RTX to communicate with I2C EEPROM the program works fine, but when I start the RTX the program stuck at:
while(!Status) Status=I2C_CheckEvent(I2C1, I2C_EVENT_MASTER_TRANSMITTER_MODE_SELECTED); // Test on EV6 and clear it
Somebody know how to fix this?
Ps: uVision3 V3.63 , MDK-ARM V3.24 , RL-ARM V3.40
Unfortunately did not work. Im using the STM32 in the MCBSTR32. I used the I2C1 and I2C2, but both present the same problem. I created a program only to test the I2C with RTX. This program have a function that write and read 10 address of a EEPROM. In program I configured the Clocks and I2C inside main function and after I called the os_sys_init function. If I call the test function of I2C before the os_sys_init function, the function runs perfectly. But if I call the test function of I2C after the os_sys_init function (inside a task) the problem occurs.
Just wondering if you had fixed this problem. If you haven't, I've gotten the I2C to work on the MCBSTR9. I saw that the code is using I2C1. There are two I2Cs on the STR912. If you really want to use I2C1, then one of the I2C1 is tied to the Ethernet. You must reconfigure it via a jumper on the board. That is documented on the setup board (check the on-line manual).
Let me know if you need some help with this.
Tom
then you probably fail to configure i2c correctly. are you shutting down the hardware timer used by RTX, or something? check your RTX_Config.c file to which one is used.
The program stuck at I2C routine like with task_lock().
remove "task_lock()"...what happens?
I lock RTOS (task_lock()) before use the I2C routines.
The I2C routines do not use interrupts, I'm using polling method.
There's just two interrupts on use (USART1_RX and USART2_RX).
I did a "bare OS with only one task" but still not working.
Ps: ARM CORTEX - M3 (STM32F103RBT6)
I can say that I2C works well with RTX (using NXP though)
I'd suggest that you walk two steps away and try to look at the problem from a different viewpoint.
What might get changed by the presence of a RTX ? Typically interrupts. Timer usage.. ? Does that Lib need Interrupts? (I guess..) Do you see a single IRQ ? Any ports mis-set ? Are the priorities of the tasks set correctly ?
I would start with a bare OS with only one task (your program) set to a high prio and let it run. Be arware that the OS wants one timer and its interrupt. And that'S it. Nothing else. Does your task alone (without I2C code) run well?
So just try to get closer to the problem. good luck ! Uli
View all questions in Keil forum