Bugs in ble_app_hrs_freertos example?

[samsam]

Some bugs in ble_app_hrs_freertos example from the SDK when handling buttons:
(at the end of this listing are same tests but with ble_app_hrs (no rtos) and buttons are handled as expected)
Tests were made with pca10040 / SDK 16.0.0 and SES 4.30b

Could you point where is the problem, please, because I've used some parts of this code as base for one my app and it handles buttons Ok in Release mode, but in Debug mode first pass through the button handler passes, but then the app stalls without reporting any error :(
Thanks
---------------------------------

ble_app_hrs_freertos_pca10040_s132

Turn On the PCA10040 board:
<info> app: HRS FreeRTOS example started.
<info> app: Fast advertising.

Press Btn1: ->Sleep
Press Btn1 or Btn2 or Btn3 or Btn4:
<info> app: HRS FreeRTOS example started.
<info> app: Fast advertising.

While advertising:
Press Btn2:
<error> hardfault: HARD FAULT at 0x00000004
<error> hardfault: R0: 0x200067E4 R1: 0x20006738 R2: 0x200072E0 R3: 0x200072E0
<error> hardfault: R12: 0x20007138 LR: 0x00000004 PSR: 0x6000000E
<error> hardfault: Cause: The processor has attempted to execute an instruction that makes illegal use of the EPSR.
<info> app: HRS FreeRTOS example started.
<info> app: Fast advertising.

Press Btn3 or Btn4:
<error> hardfault: HARD FAULT at 0x00000002
<error> hardfault: R0: 0x20007098 R1: 0x20006FF8 R2: 0x200072E0 R3: 0x200072E0
<error> hardfault: R12: 0x200065D4 LR: 0x00000002 PSR: 0x6000000E
<error> hardfault: Cause: The processor has attempted to execute an instruction that makes illegal use of the EPSR.
<info> app: HRS FreeRTOS example started.
<info> app: Fast advertising.

While Connected (not paired):
<info> app: Connected

Press Btn2:
<error> hardfault: HARD FAULT at 0x00000004
<error> hardfault: R0: 0x200067E4 R1: 0x20006738 R2: 0x200072E0 R3: 0x200072E0
<error> hardfault: R12: 0x20007138 LR: 0x00000004 PSR: 0x6000000E
<error> hardfault: Cause: The processor has attempted to execute an instruction that makes illegal use of the EPSR.
<info> app: HRS FreeRTOS example started.
<info> app: Fast advertising.

<info> app: Connected
Press Btn3 or Btn4:
<error> hardfault: HARD FAULT at 0x00000002
<error> hardfault: R0: 0x20007098 R1: 0x20006FF8 R2: 0x200072E0 R3: 0x200072E0
<error> hardfault: R12: 0x20007138 LR: 0x00000002 PSR: 0x6000000E
<error> hardfault: Cause: The processor has attempted to execute an instruction that makes illegal use of the EPSR.
<info> app: HRS FreeRTOS example started.
<info> app: Fast advertising.

--- When Paired:
restart:
<info> app: HRS FreeRTOS example started.
<info> app: Fast advertising.

Connect:
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change
<info> app: Connected
<info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Encryption
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Local database, action: Update

Press Btn1 Or Btn2 or Btn3 or Btn4:
For Btn1 and 2 (with some minor diffs in the values):
<error> hardfault: HARD FAULT at 0x00000004
<error> hardfault: R0: 0x200067E4 R1: 0x20006738 R2: 0x200072E0 R3: 0x200072E0
<error> hardfault: R12: 0x20007138 LR: 0x00000004 PSR: 0x6000000E
<error> hardfault: Cause: The processor has attempted to execute an instruction that makes illegal use of the EPSR.
<info> app: HRS FreeRTOS example started.
<info> app: Fast advertising.

For Btn3 and 3 (with some minor diffs in the values):
<error> hardfault: HARD FAULT at 0x00000002
<error> hardfault: R0: 0x20007098 R1: 0x20006FF8 R2: 0x200072E0 R3: 0x200072E0
<error> hardfault: R12: 0x20007138 LR: 0x00000002 PSR: 0x6000000E
<error> hardfault: Cause: The processor has attempted to execute an instruction that makes illegal use of the EPSR.
<info> app: HRS FreeRTOS example started.
<info> app: Fast advertising.

==============================================================================
ble_app_hrs_pca10040_s132: (here everything works Ok so far)

Press Btn1: ->Sleep
Press Btn1:
<info> app_timer: RTC: initialized.
<info> app: Heart Rate Sensor example started.
<info> app: Fast advertising.

Long press Btn2:
<info> app: Fast advertising.

Press Btn1: ->Sleep
Press Btn2:
<info> app_timer: RTC: initialized.
<info> app: Heart Rate Sensor example started.
<info> app: Erase bonds!
<info> peer_manager_handler: All peers deleted.
<info> app: Fast advertising.

Pressing Btn2,Btn3, Btn4 while advertising or connected - no any effect

[bjorn-spockeli]

Hi Samsam,

this is likely a stack overflow issue, see https://devzone.nordicsemi.com/f/nordic-q-a/51621/hardfault-ble_nus_send_data. Try to enable the Stack overflow trigger and adding the appropriate hook function to confirm this as stated here https://devzone.nordicsemi.com/f/nordic-q-a/52048/ble_app_hrs_freertos-increassing-mtu-fatal-error/223867#223867

So likely you will have to increase the stack size of the threat that is handling the button press. 

Best regards

Bjørn

[samsam]

The problems I posted are from the very original NOT modified anyhow ble_app_hrs_freertos example supplied with SDK16.0.0

[bjorn-spockeli]

Hi samsam, 

I am not seeing any issues running the ble_app_hrs_freertos_pca10040_s132 from SDK 16.0.0 in the Debug configuration. Which logging backend are you using RTT or UART?

[samsam]

Hi bjorn-spockeli,
If I compile the example with Debug config setting, I dont see the error messages neither, but the messages appears always when compiled in Release config (this I think was the initial setting the way how was the example provided).
In both modes waking up from sleep mode with Btn2 doesn't work (as supposed to - with clear bonding) and this problem I still didn't trace root cause, else the problem with the other errors that I've posted before - you were right - have to increase timer task stack to somewhere 130 minimum and errors disappear (but if I set 180 - some other crashes start - didnt trace where was the problem yet though)
I used UART for the result I posted last time - not sure the RTT was enabled, because on the other example I tried before was not enabled and I had to enabled it myself)
Thank you and best regards

[bjorn-spockeli]

I am not seeing any Hardfaults or similar when using the Release configuration. I have been using the UART backend for logging as well. 

According to the Heart Rate Application documentation, its Button 1 that is used to wake up the chip from System OFF, not Button 2.