Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

FormerMember — Wed, 16 May 2018 07:43:55 GMT

The SDK and the application will be one "unit" so it will not be possible to distinguish them .

If setting NRF_POWER->RAMON, RAM data in the specified blocks will be kept in SYSTEM OFF.

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

nagaraj — Thu, 10 May 2018 12:25:34 GMT

Hi,

please reply for previous posted comment, Application and SDK RAM usage in our project.

how to distinguish the call-stack address for SDK and our Application.

Thanks,

Nagaraj

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

FormerMember — Wed, 25 Apr 2018 08:28:43 GMT

The debugging continues in this thread.

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

nagaraj — Mon, 23 Apr 2018 10:25:47 GMT

Hi,

Waiting for your reply, please respond to above mentioned issue.

Thanks,

Nagaraj

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

nagaraj — Tue, 17 Apr 2018 05:22:58 GMT

Hi,

we are using SDK v8.1.0, didn't use APP_TWI_INIT function to initialize the i2c, we have written the drivers for i2c initialization.

We have set CSTACK size to 3k and Heap Size to 0, As per S110 SDS_v2 Document CSTACK has to start from address 0x20003fff to 0x20003402, but in our Application Cstack address starts from 0x20002e96 to 0x20002298.

Our Application RAM usage:

Application RAM address starts from 0x20002000 to 0x20002295, followed by CSTACK address 0x20002e96 to 0x20002298, followed by Application RAM address starts from 0x20002e98 to 0x20003c5f, but it has to be readwrite,Heap,CSTACk in this order as per S110 SDS_v2 . why it is so?

After Application hangs, when we check call stack contains [NRF_POWER_RAMONx_RAMxON_ONMODE_Msk + 0x6ad] in debug mode, what this indicate?

devzone.nordicsemi.com/.../1425.i2c.c devzone.nordicsemi.com/.../i2c_5F00_0.c

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

FormerMember — Mon, 16 Apr 2018 18:36:44 GMT

Which version of the SDK do you use?

Could you have a look at this thread, could the problem be similar to the one in that thread?

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

nagaraj — Mon, 16 Apr 2018 10:13:39 GMT

Hi,

We are using S110 v8.1.0, As per soft-device S110_SDS_V2 priority levels up to 0 - 3 available in Code. devzone.nordicsemi.com/.../app_5F00_util_5F00_platform.h

After Application hangs, when we check CSTACK address of 0x20002E34 holds value of 0xFFFFFFF9, What is 0xFFFFFFF9 indicates. Is this causing any issue.

Thanks,

Nagaraj

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

FormerMember — Mon, 16 Apr 2018 09:24:25 GMT

Okay, I see. By priority level, does the priority levels correspond to these priority levels?

#define _PRIO_SD_HIGH       0
#define _PRIO_SD_MID        1
#define _PRIO_APP_HIGH      2
#define _PRIO_APP_MID       3
#define _PRIO_SD_LOW        4
#define _PRIO_SD_LOWEST     5
#define _PRIO_APP_LOW       6
#define _PRIO_APP_LOWEST    7
#define _PRIO_THREAD        15

typedef enum
{
#ifndef SOFTDEVICE_PRESENT
    APP_IRQ_PRIORITY_HIGHEST = _PRIO_SD_HIGH,
#else
    APP_IRQ_PRIORITY_HIGHEST = _PRIO_APP_HIGH,
#endif
    APP_IRQ_PRIORITY_HIGH    = _PRIO_APP_HIGH,
#ifndef SOFTDEVICE_PRESENT
    APP_IRQ_PRIORITY_MID     = _PRIO_SD_LOW,
#else
    APP_IRQ_PRIORITY_MID     = _PRIO_APP_MID,
#endif
    APP_IRQ_PRIORITY_LOW     = _PRIO_APP_LOW,
    APP_IRQ_PRIORITY_LOWEST  = _PRIO_APP_LOWEST,
    APP_IRQ_PRIORITY_THREAD  = _PRIO_THREAD     /**< "Interrupt level" when running in Thread Mode. */
} app_irq_priority_t;

What happens if you set the priority of I2C0, UART0, TIMER2 , GPIOTE to APP_IRQ_PRIORITY_LOWEST and the softdevice to APP_IRQ_PRIORITY_LOW? So that the softdevice and the softdevice events always will have higher priority?

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

nagaraj — Thu, 12 Apr 2018 10:36:16 GMT

Hi,

As per Company policy we cannot share the source code, Application will run sometimes more than hour or sometimes hangs after 5-10 mintues. Application will work without softdevice .

We using the I2C0, UART0, TIMER2 ,GPIOTE which are interrupt based, In Application every 2sec we reading registers through i2c.

We tried different priority level with I2C0, UART0, TIMER2 , GPIOTE, results in same control hardfault loop, when we check debug mode in call stack after hardfault sometimes control stuck in i2c read function.

I2C Priority Level: 1, UART Priority Level: 3, TIMER2 Priority Level: 3, GPIOTE Priority Level: 3
I2C Priority Level: 1, UART Priority Level: 3, TIMER2 Priority Level: 1, GPIOTE Priority Level: 3
I2C Priority Level: 3, UART Priority Level: 3, TIMER2 Priority Level: 3, GPIOTE Priority Level: 3
I2C Priority Level: 1, UART Priority Level: 1, TIMER2 Priority Level: 1, GPIOTE Priority Level: 1

Thanks,

Nagaraj

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

FormerMember — Tue, 10 Apr 2018 11:42:41 GMT

The addresses 0x6b0 and 0x640 are addresses of a hardfault.

In your code, do you check all error codes?

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

FormerMember — Tue, 10 Apr 2018 10:52:29 GMT

Could you upload the code here? (If you want to keep the code confidential, you can switch the case to a private case.)

Is there any difference in running the application when the chip has newly been fully erased, and when it has not? (In terms of how much time it takes before the application crash.)

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

nagaraj — Tue, 10 Apr 2018 05:27:06 GMT

Hi,

Waiting for your reply, Application hangs in control hard-fault and sometimes in soft-device lower address, This is happening not while Bluetooth stack initialization.

Thanks,

Nagaraj

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

nagaraj — Thu, 05 Apr 2018 08:07:27 GMT

Hi Kristin,

Our Application will send battery status to central Device (Mobile app), able to communicate with central device but sometimes hangs in Soft-Device address.

We have tried with increasing the C-stack size up to 3 Kb for Soft-device and Application. When we comment the advertising part the code didn't hang in this case.

We are not able to exactly locate the cause for the issue as sometimes the code will not hang for hours, but sometimes the code will hang immediately as soon as we reset the board.

This problem occurred in Debug mode as well as in release mode also.

Let me know if you want more details.

Thanks,

Nagaraj

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

FormerMember — Wed, 04 Apr 2018 14:03:02 GMT

What does the application do before it starts hanging? Which functions are being called?

If you use logging over UART/RTT what is going on before the application hangs?

Does this problem only occur in debug mode?

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

nagaraj — Tue, 03 Apr 2018 04:38:29 GMT

Hi,

Please reply for above issue, Due to this issue project not moving forward.

Thanks,

Nagaraj

RE: Control Stuck at Soft device region 0 address at 0x6b0(sometimes at 0x640)

nagaraj — Fri, 30 Mar 2018 09:37:39 GMT

Hi,

Please respond to above mentioned issue, I am waiting for your reply.

This is .map memory details after building the project:

38 122 bytes of read-only code memory
1 428 bytes of read-only data memory
7 322 bytes of read-write data memory

Thanks,

Nagaraj