hi,
I2C I/O settings is as follow:
palSetPadMode(GPIOB, 10, PAL_MODE_ALTERNATE(4) | PAL_STM32_OTYPE_OPENDRAIN); /* SCL */
palSetPadMode(GPIOB, 11, PAL_MODE_ALTERNATE(4) | PAL_STM32_OTYPE_OPENDRAIN); /* SDA */
After some more speed & duty-cycle combination checking, the followings are working ...
Search found 3 matches
- Thu Jul 17, 2014 6:06 am
- Forum: STM32 Support
- Topic: Problem with changing I2C speed or dutycycle
- Replies: 5
- Views: 4420
- Wed Jul 16, 2014 7:29 am
- Forum: STM32 Support
- Topic: Problem with changing I2C speed or dutycycle
- Replies: 5
- Views: 4420
Re: Problem with changing I2C speed or dutycycle
Thanks a lot for your quick reply...
from any reason this is the only configuration that is working for me:
static const I2CConfig i2cfg2 = {
OPMODE_I2C,
400000,
FAST_DUTY_CYCLE_2,
};
any chnge in speed or dutycycle is not working. same resaults on I2CD1 or I2CD2...
while testing I2C with my ...
from any reason this is the only configuration that is working for me:
static const I2CConfig i2cfg2 = {
OPMODE_I2C,
400000,
FAST_DUTY_CYCLE_2,
};
any chnge in speed or dutycycle is not working. same resaults on I2CD1 or I2CD2...
while testing I2C with my ...
- Tue Jul 15, 2014 4:43 pm
- Forum: STM32 Support
- Topic: Problem with changing I2C speed or dutycycle
- Replies: 5
- Views: 4420
Problem with changing I2C speed or dutycycle
hi
I'm testing testhal, I2C example on STM32F4-Discovery.
I've noticed that in this example board.h is NONSTANDARD_STM32F4_BARTHESS1 and not ST_STM32F4_DISCOVERY.
When I've changed board.h to DISCOVERY, I2CD2 was not working. Then I realized that GPIOB_CLK_IN, GPIOB_SDA are connected to (PIN10,PIN9 ...
I'm testing testhal, I2C example on STM32F4-Discovery.
I've noticed that in this example board.h is NONSTANDARD_STM32F4_BARTHESS1 and not ST_STM32F4_DISCOVERY.
When I've changed board.h to DISCOVERY, I2CD2 was not working. Then I realized that GPIOB_CLK_IN, GPIOB_SDA are connected to (PIN10,PIN9 ...