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

ChibiOS public support forum for all topics not covered by a specific support forum.

Moderators: utzig, lbednarz, tfAteba, barthess, RoccoMarco

sntnjrg
Posts: 65
Joined: Mon Jul 22, 2019 2:19 pm
Has thanked: 18 times
Been thanked: 3 times

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

Postby sntnjrg » Wed Aug 26, 2020 11:58 am

Hi,

I compile the demo with last version and it is working. The only difference I see is the chconf.h file. If I add these changes to this file, the demo will generate the same compilation error:

Code: Select all

  *          of ticks that is safe to specify in a timeout directive.
  *          The value one is not valid, timeouts are rounded up to
  *          this value.
  */
 #if !defined(CH_CFG_ST_TIMEDELTA)
-/*
 #define CH_CFG_ST_TIMEDELTA                 2
-*/
-#define CH_CFG_ST_TIMEDELTA                 0
 #endif
 
 /** @} */
 
 /*===========================================================================*/
@@ -318,14 +315,11 @@
  * @note    The default is @p TRUE.
  * @note    Requires @p CH_CFG_USE_WAITEXIT.
  * @note    Requires @p CH_CFG_USE_HEAP and/or @p CH_CFG_USE_MEMPOOLS.
  */
 #if !defined(CH_CFG_USE_DYNAMIC)
-/*
 #define CH_CFG_USE_DYNAMIC                  TRUE
-*/
-#define CH_CFG_USE_DYNAMIC                  FALSE
 #endif
 
 /** @} */
 
 /*===========================================================================*/
@@ -537,42 +531,33 @@
  * @brief   Debug option, kernel statistics.
  *
  * @note    The default is @p FALSE.
  */
 #if !defined(CH_DBG_STATISTICS)
-/*
 #define CH_DBG_STATISTICS                   FALSE
-*/
-#define CH_DBG_STATISTICS                   TRUE
 #endif
 
 /**
  * @brief   Debug option, system state check.
  * @details If enabled the correct call protocol for system APIs is checked
  *          at runtime.
  *
  * @note    The default is @p FALSE.
  */
 #if !defined(CH_DBG_SYSTEM_STATE_CHECK)
-/*
 #define CH_DBG_SYSTEM_STATE_CHECK           FALSE
-*/
-#define CH_DBG_SYSTEM_STATE_CHECK           TRUE
 #endif
 
 /**
  * @brief   Debug option, parameters checks.
  * @details If enabled then the checks on the API functions input
  *          parameters are activated.
  *
  * @note    The default is @p FALSE.
  */
 #if !defined(CH_DBG_ENABLE_CHECKS)
-/*
 #define CH_DBG_ENABLE_CHECKS                FALSE
-*/
-#define CH_DBG_ENABLE_CHECKS                TRUE
 #endif
 
 /**
  * @brief   Debug option, consistency checks.
  * @details If enabled then all the assertions in the kernel code are
@@ -580,14 +565,11 @@
  *          runtime anomalies and port-defined checks.
  *
  * @note    The default is @p FALSE.
  */
 #if !defined(CH_DBG_ENABLE_ASSERTS)
-/*
 #define CH_DBG_ENABLE_ASSERTS               FALSE
-*/
-#define CH_DBG_ENABLE_ASSERTS               TRUE
 #endif
 
 /**
  * @brief   Debug option, trace buffer.
  * @details If enabled then the trace buffer is activated.
@@ -628,14 +610,11 @@
  *          runtime measurement of the used stack.
  *
  * @note    The default is @p FALSE.
  */
 #if !defined(CH_DBG_FILL_THREADS)
-/*
 #define CH_DBG_FILL_THREADS                 FALSE
-*/
-#define CH_DBG_FILL_THREADS                 TRUE
 #endif
 
 /**
  * @brief   Debug option, threads profiling.
  * @details If enabled then a field is added to the @p thread_t structure that
@@ -644,14 +623,11 @@
  * @note    The default is @p FALSE.
  * @note    This debug option is not currently compatible with the
  *          tickless mode.
  */
 #if !defined(CH_DBG_THREADS_PROFILING)
-/*
 #define CH_DBG_THREADS_PROFILING            FALSE
-*/
-#define CH_DBG_THREADS_PROFILING            TRUE
 #endif
 
 /** @} */
 
 /*===========================================================================*/

User avatar
Giovanni
Site Admin
Posts: 13527
Joined: Wed May 27, 2009 8:48 am
Location: Salerno, Italy
Has thanked: 861 times
Been thanked: 743 times
Contact:

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

Postby Giovanni » Wed Aug 26, 2020 1:38 pm

Do you have a custom linker script in your project? if so then start from one in the new version, some symbol names changed.

Giovanni


Return to “General Support”

Who is online

Users browsing this forum: No registered users and 3 guests