nRF5340 audio application ZEPHYR FATAL ERROR in NCS v2.7.0

Hello,

I'm using nRF5340 audio application with nRF Connect SDK v2.7.0 on nrf5340 Audio DK.

I didn't change anything in the sample code but only modifying the NRF5340_AUDIO_TRANSPORT_MODE to change it to bis headset. 

When I burned the code, the error always occurred.

Here is the error log.

*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
HL [00:00:00.267,181] <inf> board_version: Compatible board/HW version found: 1.0.0
HL [00:00:00.291,992] <inf> fw_info: 
	 nRHL [00:00:00.292,022] <inf> fw_info: ------- DEBUG BUILD -------
HL [00:00:00.292,022] <inf> fw_info: HEADSET left device
HL [00:00:00.319,580] <wrn> bt_hci_core: opcode 0x203a status 0x01
HL [00:00:00.319,580] <wrn> bt_hci_core: Controller does not support 'LE_READ_MAX_ADV_DATA_LEN'. Assuming maximum length is 31 bytes.
HL [00:00:00.356,719] <inf> bt_mgmt_ctlr_cfg: Controller: SoftDevice: Version 5.4 (0x0d), Revision 8699
HL [00:00:00.356,903] <inf> bt_mgmt: Local identity addr: FE:F4:EA:7D:D7:B9 (random)
HL [00:00:00.386,047] <wrn> bt_hci_core: opcode 0x2041 status 0x01
HL [00:00:00.386,077] <err> main: Failed to start scanning
HL [00:00:00.386,077] <err> main: ERR_CHK Err_code: [-5] @ line: 481	
HL [00:00:00.386,077] <err> os: r0/a1:  0x00000003  r1/a2:  0x00000009  r2/a3:  0x00000008
HL [00:00:00.386,108] <err> os: r3/a4:  0x00000003 r12/ip:  0x20002848 r14/lr:  0x000530ad
HL [00:00:00.386,108] <err> os:  xpsr:  0x09100000
HL [00:00:00.386,108] <err> os: s[ 0]:  0x20001048  s[ 1]:  0x00053281  s[ 2]:  0x2001c828  s[ 3]:  0x00000004
HL [00:00:00.386,138] <err> os: s[ 4]:  0x2001c830  s[ 5]:  0xfffffffb  s[ 6]:  0x2001c828  s[ 7]:  0x2001c858
HL [00:00:00.386,138] <err> os: s[ 8]:  0x2001c830  s[ 9]:  0xffffffff  s[10]:  0xffffffff  s[11]:  0x000532c5
HL [00:00:00.386,138] <err> os: s[12]:  0x20004570  s[13]:  0x00063240  s[14]:  0xfffffffb  s[15]:  0x000001e1
HL [00:00:00.386,138] <err> os: fpscr:  0x01000003
HL [00:00:00.386,138] <err> os: Faulting instruction address (r15/pc): 0x00003dc8
HL [00:00:00.386,169] <err> os: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
HL [00:00:00.386,199] <err> os: Current thread: 0x20004570 (main)
HL [00:00:00.386,199] <err> error_handler: Caught system error -- reason 3. Entering infinite loop

I have not encountered this problem when using either NCS v2.6.0 or NCS v2.2.0.

Is there anything else I need to modify in NCS v2.7.0?

Parents
  • Hello,

    I have a few initial thoughts just to find out where to start with possible debugging.

    I didn't change anything in the sample code but only modifying the NRF5340_AUDIO_TRANSPORT_MODE to change it to bis headset. 

    Did you modify NRF5340_AUDIO_TRANSPORT_MODE by setting CONFIG_TRANSPORT_BIS=y in prj.conf?

    I have not encountered this problem when using either NCS v2.6.0 or NCS v2.2.0.

    Is there anything else I need to modify in NCS v2.7.0?

    HL [00:00:00.319,580] [1;33m<wrn> bt_hci_core: Controller does not support 'LE_READ_MAX_ADV_DATA_LEN'. Assuming maximum length is 31 bytes.[0m

    The default controller was changed in NCS v2.6.0. The hci warning indicates some mismatch between the application and network core.

    Did you build (and flash) the application in NCS v2.7.0 for both cores?

    I will return to this next week.

    Best regards,

    Maria

  • Did you modify NRF5340_AUDIO_TRANSPORT_MODE by setting CONFIG_TRANSPORT_BIS=y in prj.conf?

    Yes, I modified NRF5340_AUDIO_TRANSPORT_MODE by settings CONFIG_TRANSPORT_BIS=y in prj.conf.

    Did you build (and flash) the application in NCS v2.7.0 for both cores?

    I executed Pristine build in NCS v2.7.0 environment, and then used Programmer Tool to burn merged_domains.hex.

  • I now know how this error occurs.

    I did not check "Use sysbuild" when editing build configuration.

    After I checked Use sybuild and rebuilt, I didn't encounter ZEPHYR FATAL ERROR again.

Reply Children
Related