Porting IoT MultiSensor to ISM14585 module

嗨mhv，

I have some more findings.

（1）初始化似乎是正确的，无论引导加载程序都可能做，MS DK还正确配置GPIO。GPIOS和SPI参数配置在set_pad_functions和iot_dk_spi_init中：

void periph_init(void) { // Power up peripherals' power domain SetBits16(PMU_CTRL_REG, PERIPH_SLEEP, 0); while (!(GetWord16(SYS_STAT_REG) & PER_IS_UP)); SetBits16(CLK_16M_REG, XTAL16_BIAS_SH_ENABLE, 1); //rom patch patch_func(); //Init pads set_pad_functions(); // (Re)Initialize peripherals iot_dk_spi_init(ACCEL_CS_PORT, ACCEL_CS_PIN, SPI_XTAL_DIV_2);

（2）我观察MISO，MOSI，CLK，CS与示波器的emcted活动。SPI似乎很好。

（3）我观察到BMI160中断变高（再次显示BMI160似乎通过SPI正确编程），似乎是问题开始。固件对中断没有反应。

Following the observation (3) I have inspected the behavior with Ozone (spoiler: I used it for the first time). A breakpoint in

void si_setup_interrupts(si_list_entity_t *ptr)

in the file sensors_interface.c shows that the interrupt is indeed being configured. A breakpoint in

void si_gpio_irq_cb（uint8_t端口，uint32_t引脚）

then shows that the callback is never executed, although the pin goes HIGH. The pin is correctly configured according to our schematic:

#define accel_drdy_port gpio_port_0 #define accel_drdy_pin gpio_pin_1 [...] gpio_configurepin（Accel_drdy_port，Accel_drdy_pin，input_pulldown，PID_GPIO，FALSE）;

[edit; deleted a part that I now figured is normal and does not help to find the problem]

在您之前的回复中，您表示您希望与我联系，但我没有收到通知或电子邮件。您需要我的联系信息吗？

BR Johannes

edit:

（a）相同是真的，我可以在运动功能上启用唤醒。我可以观察到设备睡眠，中断低。当我移动传感器时，引脚确实变高，但固件对其没有反应。
（b）我已经为这些测试禁用了睡眠模式。

Dear Dialog Support,

I am still urgently waiting for an answer. What could be the reason for the interrupt not to work? How can I further investigate this issue with Ozone?

BR Johannes

Hi PM_Dialog,

considering how much our project has in common with the MultiSensor DK (everything except for: missing env sensors, different magnetometer, different pinout, different flash/PA), I hope that you can understand that I still favor the approach of stripping down/modifying the MultiSensor DK. I hope that you have some ideas how to investigate why I don't see the interrupt.
也许我应该开始使用empty_peripheral_template测试中断功能本身。

BR Johannes

Hi PM_Dialog,

[任何新闻？任何想法如何解决这个问题？臭氧验证说明将是很棒的。]

edit:
在代码中的长期调查之后，我注意到了

void wkup_ad_cb（void）

only registers P1 and P2 are checked. Then I saw tha in UM-B-101 page 20 it is stated:

Currently this module supports interrupts in port 1 and 2. This hardware configuration does not support other ports.

Can you please tell me - urgently - if interrupts on port 0 are not possible? What is the restriction here? SDK6? MultiSensor DK? DA14585?

edit2:
我已经修改了回调函数并刚刚根据端口0的条件添加，似乎没有缺陷的工作。
这是非常不幸的是我找到这一点需要多长时间。当然，它被记录在内......但我永远不会猜到实施是不完整的。我非常好奇地理解原因。

BR Johannes