Dear nRF experts.
We are a module manufacturer and we have designed an nRF45L15 module.
We are doing a series of verifications. When we were doing the connection test, we found that there was a problem with our module. We compiled peripheral_hr and downloaded it to our module. When using a mobile phone to connect to this module, there will be an error message. , shown as follows:
[00:00:24.960,528] <wrn> bt_conn: conn 0x200022f8 failed to establish. RF noise? Disconnected, reason 0x3e Stop blinking LED. Starting Legacy Advertising (connectable and scannable) Start blinking LED... Connected Stop blinking LED. [00:00:27.924,260] <err> mpsl_init: MPSL ASSERT: 1, 1239 [00:00:27.924,273] <err> os: ***** HARD FAULT ***** [00:00:27.924,277] <err> os: Fault escalation (see below) [00:00:27.924,282] <err> os: ARCH_EXCEPT with reason 3 [00:00:27.924,289] <err> os: r0/a1: 0x00000003 r1/a2: 0x00000000 r2/a3: 0x00013313 [00:00:27.924,296] <err> os: r3/a4: 0x00000003 r12/ip: 0x20002348 r14/lr: 0xffffffff [00:00:27.924,300] <err> os: xpsr: 0x010000f5 [00:00:27.924,304] <err> os: Faulting instruction address (r15/pc): 0x0001d14c [00:00:27.924,321] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0 [00:00:27.924,325] <err> os: Fault during interrupt handling [00:00:27.924,347] <err> os: Current thread: 0x20002ea8 (unknown) [00:00:27.999,362] <err> os: Halting system
However, if we use the dk board of nRF54L15 to download this firmware, everything will be normal.
Could this be an issue with our RF?
We have verified that the center frequency point and TX POWER of our radio frequency are close to the DK BOARD.
