Hi,
I am writing a custom i2c driver for an evaluation, when I ran the same i was getting exception:
[00:00:00.422,149] <err> os: ***** BUS FAULT ***** [00:00:00.422,180] <err> os: Precise data bus error [00:00:00.422,180] <err> os: BFAR Address: 0x0 [00:00:00.422,180] <err> os: r0/a1: 0x00010734 r1/a2: 0x0001073c r2/a3: 0x00000000 [00:00:00.422,210] <err> os: r3/a4: 0x0000000c r12/ip: 0x00000042 r14/lr: 0x0000f911 [00:00:00.422,210] <err> os: xpsr: 0x81000000 [00:00:00.422,210] <err> os: Faulting instruction address (r15/pc): 0x0000b372 [00:00:00.422,241] <err> os: >>> ZEPHYR FATAL ERROR 25: Unknown error on CPU 0 [00:00:00.422,271] <err> os: Current thread: 0x20008720 (unknown) [00:00:00.494,689] <err> os: Halting system
during troubleshooting i scraped the entire custom driver and found that the issue was still persistent.
Then I just disabled CONFIG_I2C=n and the issue disappeared.
Now somehow even blinky sample program throws the very same exception when i enable CONFIG_I2C=y.
I fail to understand what is happening here.
Kindly suggest.
