I have a Zephyr application running on a NRF9160 using the Golioth SDK. I updated from their SDK from v17 to v18 and started getting undefined reference linker errors. I’ve worked with Golioth and there are no changes in the logging subsystem on their end.
The Golioth SDK update moved from nRF Connect SDK 2.8.0 to 3.0.1 so It has to be some difference in the nRF SDK or the underlying Zephyr versions causing the issue.
I’ve looked through the change lists and can’t identify a change that would affect this. Has anyone seen an issue with an undefined reference to log_dynamic_i2c_nrfx_twim or have any ideas what to try next?
Here's the full error message
FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map /home/jstuewe/prj/golioth18/build/sm-iot-gen5/zephyr/zephyr_pre0.map
/home/jstuewe/zephyr-sdk-0.17.1/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr/drivers/i2c/libdrivers__i2c.a(i2c_nrfx_twim_common.c.obj): in function `nrf_twim_frequency_set':
/home/jstuewe/prj/golioth18/deps/modules/hal/nordic/nrfx/hal/nrf_twim.h:909: undefined reference to `log_dynamic_i2c_nrfx_twim'
/home/jstuewe/zephyr-sdk-0.17.1/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr/drivers/i2c/libdrivers__i2c.a(i2c_nrfx_twim_common.c.obj): in function `i2c_nrfx_twim_msg_transfer':
/home/jstuewe/prj/golioth18/deps/zephyr/drivers/i2c/i2c_nrfx_twim_common.c:84: undefined reference to `log_dynamic_i2c_nrfx_twim'
/home/jstuewe/zephyr-sdk-0.17.1/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr/drivers/i2c/libdrivers__i2c.a(i2c_nrfx_twim_common.c.obj): in function `i2c_nrfx_twim_common_init':
/home/jstuewe/prj/golioth18/deps/zephyr/drivers/i2c/i2c_nrfx_twim_common.c:139: undefined reference to `log_dynamic_i2c_nrfx_twim'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.