Hi,
The latest baseline specifies GNSS use based on the hardware configuration. For CHESTER-U1 devices, GNSS is automatically enabled through the LTE v2 module, while CHESTER-M devices use the SAM-M8Q module. However, some legacy applications on CHESTER-U1 still rely on the SAM-M8Q, developed before the LTE v2 GNSS subsystem was available. To ensure backward compatibility, the following code in ctr_gnss.c
must be updated to allow CHESTER-U1 applications to select either the LTE v2 modem GNSS or the SAM-M8Q module.
#if defined(CONFIG_CTR_GNSS_M8)
if (product_family == CTR_INFO_PRODUCT_FAMILY_CHESTER_M) {
ctr_gnss_m8_set_handler(m_user_cb, m_user_data);
return ctr_gnss_m8_start();
}
#endif
#if defined(CONFIG_CTR_LTE_V2_GNSS)
if (product_family == CTR_INFO_PRODUCT_FAMILY_CHESTER_U1) {
ctr_lte_v2_gnss_set_handler(lte_v2_gnss_handler, NULL);
return ctr_lte_v2_gnss_set_enable(true);
}
#endif
For example, we could simply remove the product_family
verification:
#if defined(CONFIG_CTR_GNSS_M8)
ctr_gnss_m8_set_handler(m_user_cb, m_user_data);
return ctr_gnss_m8_start();
#endif
#if defined(CONFIG_CTR_LTE_V2_GNSS)
ctr_lte_v2_gnss_set_handler(lte_v2_gnss_handler, NULL);
return ctr_lte_v2_gnss_set_enable(true);
#endif
Best,
David