Search found 277 matches

by FXCoder
Mon Aug 24, 2020 3:56 pm
Forum: General Support
Topic: STM32L4R5ZI-NUCLEO144: How to activate the I2C4 bus on mcuconf.h?
Replies: 11
Views: 173

Re: STM32L4R5ZI-NUCLEO144: How to activate the I2C4 bus on mcuconf.h?

OK. Understand now what you meant.
The I2C4 driver did have a bug but that was fixed a while back.

Bob
by FXCoder
Mon Aug 24, 2020 3:16 pm
Forum: General Support
Topic: STM32L4R5ZI-NUCLEO144: How to activate the I2C4 bus on mcuconf.h?
Replies: 11
Views: 173

Re: STM32L4R5ZI-NUCLEO144: How to activate the I2C4 bus on mcuconf.h?

Hi. You have it pretty much. Below is an I2C setup from a working L4+ project... -- Bob /* * I2C driver system settings. */ #define STM32_I2C_USE_I2C1 TRUE #define STM32_I2C_USE_I2C2 FALSE #define STM32_I2C_USE_I2C3 TRUE #define STM32_I2C_USE_I2C4 TRUE #define STM32_I2C_BUSY_TIMEOUT 50 #define STM32...
by FXCoder
Sun Aug 16, 2020 3:40 pm
Forum: Bug Reports
Topic: CH_CFG_USE_MUTEXES_RECURSIVE - incorrect var name Topic is solved
Replies: 2
Views: 221

CH_CFG_USE_MUTEXES_RECURSIVE - incorrect var name Topic is solved

Hi, Incorrect var name used in recursive mutex code. -- Bob Index: chmtx.c =================================================================== --- chmtx.c (revision 13808) +++ chmtx.c (working copy) @@ -150,7 +150,7 @@ /* If the mutex is already owned by this thread, the counter is increased and the...
by FXCoder
Thu Aug 13, 2020 6:37 am
Forum: Bug Reports
Topic: ICU driver and 32 bits timer
Replies: 17
Views: 1293

Re: ICU driver and 32 bits timer

Hi. Here is the simple change in hal_icu.h to enable ICU scaling by using the overflow callback. The overflow scaling is only available where a callback is set. The callback is not called until edge sync is obtained. If there is concern over legacy behavior a #define could be added (e.g.) #I2C_USE_O...
by FXCoder
Tue Aug 11, 2020 12:23 am
Forum: Bug Reports
Topic: EVENTSOURCE_DATA initializer Topic is solved
Replies: 6
Views: 219

Re: EVENTSOURCE_DATA initializer Topic is solved

Understood. However, the idea was to allow the function to accept NULL from the function call set start a timer. In the case of NULL an internal callback handler is substituted. Thus NULL in the CB field will continue to indicate the timer is not started. Then the use case where all that is required...
by FXCoder
Mon Aug 10, 2020 2:13 pm
Forum: Bug Reports
Topic: EVENTSOURCE_DATA initializer Topic is solved
Replies: 6
Views: 219

Re: EVENTSOURCE_DATA initializer Topic is solved

So add something like this for VT so that the CB can be specified as NULL? (Plus add an initializer.) diff --git a/software/tracker/ChibiOS/os/rt/src/chvt.c b/software/tracker/ChibiOS/os/rt/src/chvt.c index 7366195..374b0e8 100644 --- a/software/tracker/ChibiOS/os/rt/src/chvt.c +++ b/software/tracke...
by FXCoder
Sat Aug 08, 2020 9:59 am
Forum: Bug Reports
Topic: EVENTSOURCE_DATA initializer Topic is solved
Replies: 6
Views: 219

Re: EVENTSOURCE_DATA initializer Topic is solved

Actually one thing in a similar class that would be useful for VTs....
In the case that a VT is used in the "has it expired" mode only then the CB could be pointed at a dummy CB inside the chvt.c that just returns?

Would save writing a few lines :-)
--
Bob
by FXCoder
Sat Aug 08, 2020 9:53 am
Forum: Bug Reports
Topic: EVENTSOURCE_DATA initializer Topic is solved
Replies: 6
Views: 219

EVENTSOURCE_DATA initializer Topic is solved

Hi. should this... /** * @brief Data part of a static event source initializer. * @details This macro should be used when statically initializing an event * source that is part of a bigger structure. * @param name the name of the event source variable */ #define _EVENTSOURCE_DATA(name) {(event_liste...

Go to advanced search