• State Verified Answer
  • Replies 3 replies
  • Subscribers 86 subscribers
  • Views 276 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 353042
Options

nRF54H20DK bump SDK v3.2.0-preview1 to SDK v3.2.0-preview2

Mads Fidder

Hello,

I am currently developing on the nRF54H20DK, which i have previously used v3.2.0-preview1 for.

Everything works fine on v3.2.0-preview1. I have tried bumping to v3.2.0-preview2 and are now faced with:

[00:00:00.402,319] <err> os: ***** BUS FAULT *****
[00:00:00.402,325] <err> os:   Precise data bus error
[00:00:00.402,328] <err> os:   BFAR Address: 0xe1fdfe0
[00:00:00.402,340] <err> os: r0/a1:  0x2f041ef0  r1/a2:  0x0e1fdfe0  r2/a3:  0x0e1fdff0
[00:00:00.402,345] <err> os: r3/a4:  0x2f041eef r12/ip:  0x0000a000 r14/lr:  0x0e0d1edb
[00:00:00.402,348] <err> os:  xpsr:  0x89000000
[00:00:00.402,351] <err> os: Faulting instruction address (r15/pc): 0x0e0d6dc4
[00:00:00.402,368] <err> os: >>> ZEPHYR FATAL ERROR 25: Unknown error on CPU 0
[00:00:00.402,387] <err> os: Current thread: 0x2f007588 (main)
[00:00:00.477,696] <err> os: Halting system

I have made no other changes to my project. Any help will be appreciated

Parents
  • 0

    Hi Mads,

    Seems like the fault is happening in main thread

    If everything in your application is exactly same, then something in the SDK might be using more main stack than it was previously. If the application of yours works fine on v3.2.0-preview1, then it must be using up almost full allocated main stack and the v3.2.0-preview2 might have just pushed it to little over limit. Increase the CONFIG_MAIN_STACK_SIZE in your prj.conf to little higher than what you had before and this might go away. If it does not, then you need to know exactly what code lies at instruction address 0x2f007588 looking at the map file to understand the context of the error.

Reply
  • 0

    Hi Mads,

    Seems like the fault is happening in main thread

    If everything in your application is exactly same, then something in the SDK might be using more main stack than it was previously. If the application of yours works fine on v3.2.0-preview1, then it must be using up almost full allocated main stack and the v3.2.0-preview2 might have just pushed it to little over limit. Increase the CONFIG_MAIN_STACK_SIZE in your prj.conf to little higher than what you had before and this might go away. If it does not, then you need to know exactly what code lies at instruction address 0x2f007588 looking at the map file to understand the context of the error.

Children
  • 0 in reply to Susheel Nuguru

    Hello Susheel,

    Thank you for your quick answer!

    Previously i had my main stack size configured to 5200. I have tried raising it to 16384, but it does not seem to make a difference. 

    Instruction address 0x2f007588  points to ncs/v3.2.0-preview2/zephyr/kernel/init.c:56.

    Which is:

    Which is not very telling, for me at least.

    However, i have noticed that with preview2, sysbuild now also includes a build for "uicr", instead of only the app-core and radio-core. 

    If i don't flash the whole project, and instead only flashes app- and radio-core, it seems to work.

    How can that be?

    I do not know if it relevant but my IronSide is of v23.0.2-live+17

    Thank you in advance.

  • 0 in reply to Mads Fidder

    It was because of a partition issue, which was self made, but didn't cause any damage on preview1.

    Thank you for your time!

Related
Terms of service