After power turn off and on. Chip is not working

RE: After power turn off and on. Chip is not working

Seng ju Han — Mon, 04 Nov 2019 06:59:41 GMT

Hi, Simon

I found a error. but I don`t know why don`t work the sensor.

I write the delay 1ms after mpu_init. (Code of mpu_setup)

It works. :)

I think that sending sensor values need more time after the sensor initialized.

Thank you for your help. Simon.

Best regards,
Han

RE: After power turn off and on. Chip is not working

Simonr — Thu, 31 Oct 2019 11:56:21 GMT

[quote user="Seng ju Han"][/quote]

I tested the board.

I turn off the board.

The nRF connect on my cell phone has disappeared advertising.

This makes it seem like your application works when the DK is running, which suggests that it is the DK running the application and not the module. Can you please specify, as I'm not sure I understand what you mean.

Best regards,

Simon

RE: After power turn off and on. Chip is not working

Seng ju Han — Thu, 31 Oct 2019 08:29:49 GMT

Hi Simon.

I tested the board.

I turn off the board.

The nRF connect on my cell phone has disappeared advertising.

I don't think it's a matter of communication.

Maybe...

If you happen to solve the problem, I'll leave a reply.

First. Let me check the layout again to see if there are any problems with the hardware.

Of course, it's more likely that there's no problem with the circuit. 😞

Have you ever thought about any other possibilities?

Best Regards,

Han

RE: After power turn off and on. Chip is not working

Simonr — Wed, 30 Oct 2019 08:51:43 GMT

Hi Han

Thank you, the advertising_init() and advertising_start() functions were what I wanted to see. I don't see any issues with your advertising, so that's not it. Could it be that the reason it works while you debug is that the DK is the board that is advertising, and not the module? Can you check if you see the advertisement when powering the board and not the module? It should be easy to determine if the DK is the one advertising by checking the RSSI value of it in the nRFConnect app when you bring it closer to/further away from the phone.

Best regards,

Simon

RE: After power turn off and on. Chip is not working

Seng ju Han — Wed, 30 Oct 2019 00:25:34 GMT

First, I'm sorry for using the expression "it doesn`t matter" to exclude the answer to check the connection of the mpu6050 from my custom board.
The sensor is working. I succeeded in getting data through the line in the sensor of the custom board in Arduino.

I don`t know how to "Also, if you could post a snippet showing the advertising initialization that would be great!"

If it is related to "advertising_init" and "advertising_star"

uint32_t ble_advertising_init(ble_advertising_t * const p_advertising,
ble_advertising_init_t const * const p_init)
   {
uint32_t ret;
if ((p_init == NULL) || (p_advertising == NULL))
   {
        return NRF_ERROR_NULL;
   }

p_advertising->initialized = true;
p_advertising->adv_mode_current = BLE_ADV_MODE_IDLE;
p_advertising->adv_modes_config = p_init->config;
p_advertising->conn_cfg_tag = BLE_CONN_CFG_TAG_DEFAULT;
p_advertising->evt_handler = p_init->evt_handler;
p_advertising->error_handler = p_init->error_handler;
p_advertising->current_slave_link_conn_handle = BLE_CONN_HANDLE_INVALID;

memset(&p_advertising->peer_address, 0, sizeof(p_advertising->peer_address));
memset(&p_advertising->advdata, 0, sizeof(p_advertising->advdata));

// Copy advertising data.
p_advertising->advdata.name_type = p_init->advdata.name_type;
p_advertising->advdata.include_appearance = p_init->advdata.include_appearance;
p_advertising->advdata.flags = p_init->advdata.flags;
p_advertising->advdata.short_name_len = p_init->advdata.short_name_len;

p_advertising->advdata.uuids_complete = p_init->advdata.uuids_complete;
p_advertising->advdata.uuids_more_available = p_init->advdata.uuids_more_available;
p_advertising->advdata.uuids_solicited = p_init->advdata.uuids_solicited;
p_advertising->advdata.include_ble_device_addr = p_init->advdata.include_ble_device_addr;

if (p_init->advdata.p_manuf_specific_data != NULL)
{
p_advertising->advdata.p_manuf_specific_data = &(p_advertising->manuf_specific_data);
p_advertising->manuf_specific_data.data.p_data = p_advertising->manuf_data_array;
p_advertising->advdata.p_manuf_specific_data->company_identifier =
p_init->advdata.p_manuf_specific_data->company_identifier;
p_advertising->advdata.p_manuf_specific_data->data.size = p_init->advdata.p_manuf_specific_data->data.size;

for (uint32_t i = 0; i < p_advertising->advdata.p_manuf_specific_data->data.size; i++)
{
p_advertising->manuf_data_array[i] = p_init->advdata.p_manuf_specific_data->data.p_data[i];
}
}

if (p_init->advdata.p_service_data_array != NULL)
{
p_advertising->service_data.data.p_data = p_advertising->service_data_array;
p_advertising->advdata.p_service_data_array = &(p_advertising->service_data);
p_advertising->advdata.p_service_data_array->data.p_data = p_advertising->service_data_array;
p_advertising->advdata.p_service_data_array->data.size = p_init->advdata.p_service_data_array->data.size;
p_advertising->advdata.p_service_data_array->service_uuid = p_init->advdata.p_service_data_array->service_uuid;

for (uint32_t i = 0; i < p_advertising->advdata.p_service_data_array->data.size; i++)
{
p_advertising->service_data_array[i] = p_init->advdata.p_service_data_array->data.p_data[i];
}

p_advertising->advdata.service_data_count = p_init->advdata.service_data_count;
}

if (p_init->advdata.p_slave_conn_int != NULL)
{
p_advertising->advdata.p_slave_conn_int = &(p_advertising->slave_conn_int);
p_advertising->advdata.p_slave_conn_int->max_conn_interval = p_init->advdata.p_slave_conn_int->max_conn_interval;
p_advertising->advdata.p_slave_conn_int->min_conn_interval = p_init->advdata.p_slave_conn_int->min_conn_interval;
}

if (p_init->advdata.p_tx_power_level != NULL)
{
p_advertising->advdata.p_tx_power_level = p_init->advdata.p_tx_power_level;
}

#if (NRF_SD_BLE_API_VERSION <= 2)
for (int i = 0; i <BLE_GAP_WHITELIST_ADDR_MAX_COUNT ; i++)
{
p_advertising->whitelist.pp_addrs[i] = &p_advertising->whitelist_addrs[i];
}

for (int i = 0; i <BLE_GAP_WHITELIST_IRK_MAX_COUNT ; i++)
{
p_advertising->whitelist.pp_irks[i] = &p_advertising->whitelist_irks[i];
}
#endif
ret = ble_advdata_set(&(p_advertising->advdata), &(p_init->srdata));
return ret;
}


uint32_t ble_advertising_start(ble_advertising_t * const p_advertising,
ble_adv_mode_t advertising_mode)
{
uint32_t ret;
ble_gap_adv_params_t adv_params;

if (p_advertising->initialized == false)
{
return NRF_ERROR_INVALID_STATE;
}

p_advertising->adv_mode_current = advertising_mode;

// Delay starting advertising until the flash operations are complete.
if (flash_access_in_progress())
{
p_advertising->advertising_start_pending = true;
return NRF_SUCCESS;
}

memset(&p_advertising->peer_address, 0, sizeof(p_advertising->peer_address));

if ( ((p_advertising->adv_modes_config.ble_adv_directed_enabled) && (p_advertising->adv_mode_current == BLE_ADV_MODE_DIRECTED))
||((p_advertising->adv_modes_config.ble_adv_directed_slow_enabled) && (p_advertising->adv_mode_current == BLE_ADV_MODE_DIRECTED))
||((p_advertising->adv_modes_config.ble_adv_directed_slow_enabled) && (p_advertising->adv_mode_current == BLE_ADV_MODE_DIRECTED_SLOW))
)
{
if (p_advertising->evt_handler != NULL)
{
p_advertising->peer_addr_reply_expected = true;
p_advertising->evt_handler(BLE_ADV_EVT_PEER_ADDR_REQUEST);
}
else
{
p_advertising->peer_addr_reply_expected = false;
}
}

p_advertising->adv_mode_current = adv_mode_next_avail_get(p_advertising, advertising_mode);

// Fetch the whitelist.
if ((p_advertising->evt_handler != NULL) &&
(p_advertising->adv_mode_current == BLE_ADV_MODE_FAST || p_advertising->adv_mode_current == BLE_ADV_MODE_SLOW) &&
(p_advertising->adv_modes_config.ble_adv_whitelist_enabled) &&
(!p_advertising->whitelist_temporarily_disabled))
{
#if (NRF_SD_BLE_API_VERSION >= 3)
p_advertising->whitelist_in_use = false;
#endif
p_advertising->whitelist_reply_expected = true;
p_advertising->evt_handler(BLE_ADV_EVT_WHITELIST_REQUEST);
}
else
{
p_advertising->whitelist_reply_expected = false;
}

// Initialize advertising parameters with default values.
memset(&adv_params, 0, sizeof(adv_params));

adv_params.type = BLE_GAP_ADV_TYPE_ADV_IND;
adv_params.fp = BLE_GAP_ADV_FP_ANY;

// Set advertising parameters and events according to selected advertising mode.
switch (p_advertising->adv_mode_current)
{
case BLE_ADV_MODE_DIRECTED:
ret = set_adv_mode_directed(p_advertising, &adv_params);
break;

case BLE_ADV_MODE_DIRECTED_SLOW:
ret = set_adv_mode_directed_slow(p_advertising, &adv_params);
break;

case BLE_ADV_MODE_FAST:
ret = set_adv_mode_fast(p_advertising, &adv_params);
break;

case BLE_ADV_MODE_SLOW:
ret = set_adv_mode_slow(p_advertising, &adv_params);
break;

case BLE_ADV_MODE_IDLE:
p_advertising->adv_evt = BLE_ADV_EVT_IDLE;
break;

default:
break;
}

if (p_advertising->adv_mode_current != BLE_ADV_MODE_IDLE)
{
ret = sd_ble_gap_adv_start(&adv_params, p_advertising->conn_cfg_tag);
if (ret != NRF_SUCCESS)
{
return ret;
}
}

if (p_advertising->evt_handler != NULL)
{
p_advertising->evt_handler(p_advertising->adv_evt);
}

return NRF_SUCCESS;
}

OR?

static void advertising_init(void)
{
    ret_code_t             err_code;
    ble_advertising_init_t init;

    memset(&init, 0, sizeof(init));

    init.advdata.name_type               = BLE_ADVDATA_FULL_NAME;
    init.advdata.include_appearance      = true;
    init.advdata.flags                   = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
    init.advdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
    init.advdata.uuids_complete.p_uuids  = m_adv_uuids;

    init.config.ble_adv_fast_enabled  = true;
    init.config.ble_adv_fast_interval = APP_ADV_INTERVAL;
    init.config.ble_adv_fast_timeout  = APP_ADV_TIMEOUT_IN_SECONDS;

    init.evt_handler = on_adv_evt;

    err_code = ble_advertising_init(&m_advertising, &init);
    APP_ERROR_CHECK(err_code);

    ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
    
    
    
    
static void advertising_start(bool erase_bonds)
{
    if (erase_bonds == true)
    {
        delete_bonds();
        // Advertising is started by PM_EVT_PEERS_DELETED_SUCEEDED evetnt
    }
    else
    {
        ret_code_t err_code = ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST);

        APP_ERROR_CHECK(err_code);
    }
}
}

I`m right?

I hope that's the answer you want.

Today as well, Thank you for reply.

Best regards,

Han

RE: After power turn off and on. Chip is not working

Simonr — Tue, 29 Oct 2019 14:19:49 GMT

[quote user="Seng ju Han"]However, when debugging, it doesn't matter.[/quote]

What do you mean that it "doesn't matter"? Does the application skip it, or what. Please clarify. Also, if you could post a snippet showing the advertising initialization that would be great!

Best regards,

Simon

RE: After power turn off and on. Chip is not working

Seng ju Han — Tue, 29 Oct 2019 11:58:16 GMT

int main(void)
{
bool erase_bonds;

// Initialize.

timers_init();

ble_stack_init();
gap_params_init();
gatt_init();
advertising_init();
services_init();
conn_params_init();
peer_manager_init();
mpu_setup();


advertising_start(erase_bonds);

sum_values_t sum_values;

// Enter main loop.
for (;;)
  {
      if (NRF_LOG_PROCESS() == false)
         {
              power_manage();
              if(start_accel_update_flag == true)
                  {

                      mpu_read_sum(&sum_values);
                      ble_mpu_update(&m_mpu, &sum_values);


                start_accel_update_flag = false;

                  }
             }
   }
}

In the middle, there is a part that initializes mpu6050. However, when debugging, it doesn't matter.

RE: After power turn off and on. Chip is not working

Simonr — Mon, 28 Oct 2019 07:22:38 GMT

Okay, so there's definitely your project code that is causing this. Can you upload a snippet of where in your code you do advertising initialization and where you start advertising?

Best regards,

Simon

RE: After power turn off and on. Chip is not working

Seng ju Han — Fri, 25 Oct 2019 09:10:35 GMT

I used this power supply.

I tested 52DK board. (sdk v15.3 ble_app_blink_pca_s132)

after Debug -> It is works.

and dk board turn off and connect p21 to power supply. -> it is works.

but my code .... I tested 52Dk board.

after Debug -> it is works.

board turn off and connect p21 to power supply -> it is not working

I think my code is wrong...

The last changes code is data structure.

It doesn't mean much.

typedef
{
int16_t accel_x;
int16_t accel_y;
int16_t accel_z;
int16_t gyro_x;
int16_t gyro_y;
int16_t gyro_z;

}sum_value_t

-> change

typedef
{
int16_t gyro_z;
int16_t gyro_y;
int16_t gyro_x;
int16_t accel_z;
int16_t accel_y;
int16_t accel_x;
}sum_value_t

I connected custom board ->

ps. I disconnected with computer to Dk board for photo.

Best regard,

Han

RE: After power turn off and on. Chip is not working

Simonr — Fri, 25 Oct 2019 06:15:25 GMT

These settings seem correct. What were the last changes you made to your application code? There must have been something that causes the devices to not work with the power supply. Also, what exactly is this power supply, and how do you connect it to the custom boards? Are you able to power your DK with this power supply using the External supply pins on header P21?

Best regards,

Simon

RE: After power turn off and on. Chip is not working

Seng ju Han — Thu, 24 Oct 2019 11:41:24 GMT

Hi Simon,

#define CLOCK_CONFIG_LF_SRC 0

I've already done it.

but

The following is a difference in configuration.

Debug configuration

"BOARD_PCA10040;CONFIG_GPIO_AS_PINRESET;FLOAT_ABI_HARD;INITIALIZE_USER_SECTIONS;NO_VTOR_CONFIG;NRF52;NRF52832_XXAA;NRF52_PAN_74;NRF_SD_BLE_API_VERSION=5;S132;SOFTDEVICE_PRESENT;MPU_USES_TWI;MPU60x0" from project in Common configuration
"DEBUG; DEBUG_NRF" from solution in Debug configuration

Release configuration

and

Debugging level

Debug configuration- > Debugging level 3

Release configuration- > Debugging level None

and

Optimization level

Debug configuration- > None

Release configuration- > Optimize For Size

How should I change it?

and I don`t understand pre-processor flags.. I cann`t find it .

I was really frustrated, but I'm glad I could talk about this.

Thank you for leaving me a reply.

Best regards,

Han

RE: After power turn off and on. Chip is not working

Simonr — Thu, 24 Oct 2019 09:03:20 GMT

For SDK v.14.2, please change #define CLOCK_CONFIG_LF_SRC to 0 in your sdk_config.h file and see if that helps. You can also try comparing the Release and Debug configuration in SES to see if there are any differences apart from optimization level and pre-processor flags, also, check if the flash_placement.xml file is the same for Release and Debug.

Best regards,

Simon

RE: After power turn off and on. Chip is not working

Seng ju Han — Thu, 24 Oct 2019 00:01:22 GMT

Hi Simon.

I used SDK v.14.2 . When I use version 15.3, I will consider your advice.

Thank you Simon. But I haven't solved it yet.

Best regards,

Han

RE: After power turn off and on. Chip is not working

Simonr — Wed, 23 Oct 2019 08:41:02 GMT

What SDK version are you using? Assuming you're using SDK v.15.3.0, please change the following defines in your sdk_config file to the following:

#define NRFX_CLOCK_CONFIG_LF_SRC 0

#define CLOCK_CONFIG_LF_SRC 0

#define CLOCK_CONFIG_LF_CAL_ENABLED 1

Best regards,

Simon