Debugging-zephyr-assert-header
From Wiki at Neela Nurseries
2022-08-09 Tuesday
Which of these assert.h files need we include in our RP2040 explorations project?
ted@localhost:~/projects-sandbox/workspace-for-rpi$ find . -name assert.h ./zephyr/lib/libc/minimal/include/assert.h ./modules/lib/chre/platform/include/chre/platform/assert.h ./modules/lib/chre/util/include/chre/util/nanoapp/assert.h ./modules/lib/chre/std_overrides/include/assert.h ./modules/hal/libmetal/libmetal/lib/assert.h ./modules/hal/libmetal/libmetal/lib/system/freertos/assert.h ./modules/hal/libmetal/libmetal/lib/system/zephyr/assert.h ./modules/hal/libmetal/libmetal/lib/system/nuttx/assert.h ./modules/hal/libmetal/libmetal/lib/system/generic/assert.h ./modules/hal/libmetal/libmetal/lib/system/linux/assert.h ./modules/hal/rpi_pico/src/common/pico_base/include/pico/assert.h ./modules/hal/espressif/components/newlib/platform_include/assert.h
Reviewing latest committed Zephyr RTOS sources for ~/zephyr/include/zephyr/drivers/reset.h find that there is a name conflict addressed here between drivers/reset/reset_rpi_pico.c and newlibc assert() definition or name:
^ Search for missing bus data member
Possible sensor API data structure change, member 'bus' no such member in Zephyr 3.2.0 . . .
ted@localhost1:~/projects-sandbox/workspace-out-of-tree/kionix-driver-demo/build$ grep -nr '\->bus' ./*
./zephyr/zephyr.lst:2164: status = i2c_write_read(device_data_ptr->bus,
./zephyr/zephyr.lst:11454: iis2dh->bus = device_get_binding(cfg->bus_name);
./zephyr/zephyr.lst:11458: if (!iis2dh->bus) {
./zephyr/zephyr.lst:19409: return i2c_burst_write(data->bus, iis2dh_i2c_slave_addr,
./zephyr/zephyr.lst:19424: return i2c_burst_write(data->bus, iis2dh_i2c_slave_addr,
./zephyr/zephyr.lst:19452: return i2c_burst_read(data->bus, iis2dh_i2c_slave_addr,
./zephyr/zephyr.lst:19462: return i2c_burst_read(data->bus, iis2dh_i2c_slave_addr,
ted@localhost1:~/projects-sandbox/workspace-out-of-tree/kionix-driver-demo/build$
