Using I2C with two devices on App Timer gets Hardfaulthttps://devzone.nordicsemi.com/f/nordic-q-a/21190/using-i2c-with-two-devices-on-app-timer-gets-hardfaultHello, I have two devices sharing an I2C bus. These devices are the MAX86150 and the MLX90614. DMA is being used. I2C is running at 100 KHz. After initializing both devices, the application timer is configured to interrupt every 10 ms. A processen-USTelligent Community 13Thu, 20 Apr 2017 14:12:19 GMTRE: Using I2C with two devices on App Timer gets Hardfaulthttps://devzone.nordicsemi.com/thread/82923?ContentTypeID=1Thu, 20 Apr 2017 14:12:19 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5e7fe009-c9de-46ad-814f-fe6e3f7b043bStian R&#248;ed Hafskjold<p>If you put a break point in the hardfault_handler in the arm_startup_xxx.s file you should be able to see the call stack when it hits the hardfault handler, and which instruction that caused this. And also compile with the -O0 optimization flag.</p><div style="clear:both;"></div>RE: Using I2C with two devices on App Timer gets Hardfaulthttps://devzone.nordicsemi.com/thread/82922?ContentTypeID=1Fri, 07 Apr 2017 07:36:59 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6f0a6b76-c588-45d1-8684-27eafb0b7d9cAlex<p>You can check registers and one of them can tell you the address where it happened <a href="http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0553a/Babcefea.html">link text</a>. May be <a href="http://www.keil.com/appnotes/files/apnt209.pdf">this document</a> help you as well.</p><div style="clear:both;"></div>RE: Using I2C with two devices on App Timer gets Hardfaulthttps://devzone.nordicsemi.com/thread/82921?ContentTypeID=1Thu, 06 Apr 2017 17:21:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5123ee45-b284-44f0-8db2-495990c239d0Noah<p>Also, this doesn&#39;t always hardfault. Sometimes the code jumps to address 0x0001AFF4. Any thoughts?</p><div style="clear:both;"></div>