This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Hardfault on call to pm_init, with R2 set to CAFEBABE

As the title says, I'm getting a hardfault on a call to pm_init() in a BLE peripheral HRS trial application. This is on a micro:bit v2 board, which has an nRF52833 Cortex-M4 MCU.

<info> app_timer: RTC: initialized.
<error> hardfault: HARD FAULT at 0x00000000
<error> hardfault: R0: 0x000000E8 R1: 0x00000000 R2: 0xCAFEBABE R3: 0xCAFEBABE
<error> hardfault: R12: 0x00000000 LR: 0xFFFFFFF9 PSR: 0x200F003A
<error> hardfault: Cause: The processor has attempted to execute an instruction that makes illegal use of the EPSR.

Anyone have any clues as to what the 'CAFEBABE' hex codes indicate?

Parents
  • Hi,  

    Anyone have any clues as to what the 'CAFEBABE' hex codes indicate?

    See the explanation in this post.  

    Please replace the startup and system files as this post indicated or use the example for PCA10100 configuration. PCA10100 is the board name for the nRF52833 DK, which means the project has been configured with the correct startup files, etc for the nRF52833 chip.

    Notice that we are entering the Christmas and New Year holidays and will have reduced staff, please expect delayed responses until after January 4th. Sorry for the inconvenience.

    -Amanda H.

Reply
  • Hi,  

    Anyone have any clues as to what the 'CAFEBABE' hex codes indicate?

    See the explanation in this post.  

    Please replace the startup and system files as this post indicated or use the example for PCA10100 configuration. PCA10100 is the board name for the nRF52833 DK, which means the project has been configured with the correct startup files, etc for the nRF52833 chip.

    Notice that we are entering the Christmas and New Year holidays and will have reduced staff, please expect delayed responses until after January 4th. Sorry for the inconvenience.

    -Amanda H.

Children
No Data
Related