Problem To Discover DA14580 by DSPS

Hi kaoutar,

The host project can't be discovered, its a scanner, it role is to scan and discover other devices (devices that act as peripherals and advertise), you wont be able to discover a central from another central.

Thanks MT_dialog

Hi kaoutar,

Yes, Tera Term is a terminal you can use with the DSPS in order to check the transfered data, please check the instructions in the DSPS application note in order to correctly setup the demo and check your connections. Make sure that you use the correct setup (HW/SW flow control at your PC on the Tera Term in order to properly display the data). In order to change the character settings its a matter of your terminal and has nothing to do with keil, the terminal is going to translate the data that you are sending either as ascii or hexadecimal data.

Thanks MT_dialog

Hi shuixiu,

When you invoke the app_start_scanning() your device will start to scan in all 3 advertising channels continuously, when your device gets an advertising string from a peripheral the app_adv_report_ind_func will be called in order to inform your application that an advertising string is traced.

Thanks MT_dialog

Hi shuixiu,

Please check your other post for the answerhttp://support.dialog-semiconductor.com/current-start-scanning-event.

Thanks MT_dialog

Hi kaoutar,

Lets take the displaying of the advertising data as an example, you can enable the UART2 feature in order to print out data and use the arch_printf in order to push the data on a terminal. In the da1458x_config_basic.h define the CFG_PRINTF in order to enable the uart2 functionallity (also include the uart2.c if not allready included in the project) configure your pins properly and replace the the code indicated below with following snippet in the schedule_while_ble_on():

////////////////////////////////////code in the SDK//////////////////////////////////////

if (!app_asynch_trm())
break;

//SDKIMPROVEMENTS Needs testing!! We can add the following condition and move
// it out of the loop
// we may consider putting it in before the app_asynch_trm
//if (GetBits16(CLK_CTRL_REG, RUNNING_AT_XTAL16M))

// execute the printf process
arch_printf_process();

////////////////////////////replace the code above with the code below/////////////////////////////////////
if (app_asynch_trm())
{
continue; // so that rwip_schedule() is called again
}
else
{
arch_printf_process();
break;
}
}

After you ve done that, you can place in the user_on_adv_report_ind() (the callback that will be issued whenever you have an advertising message) the following snippet.

arch_printf("Connect with %02x %02x %02x %02x %02x %02x",
param->report.adv_addr.addr[5],
param->report.adv_addr.addr[4],
param->report.adv_addr.addr[3],
param->report.adv_addr.addr[2],
param->report.adv_addr.addr[1],
param->report.adv_addr.addr[0]);

In order to print out the bd address of the device that was advertising.

Thanks MT_dialog

Hi kaoutar,

The instructions i mentioned above is in order to print the data in your UART port. If you just want to check the variable's values in keil you should reduce the optimization level from keil (just hit the options for target button, select the C/C++ tab, and change your optimization level to -O0 or -O1). Regarding where to look, when your host finds an advertising string, the user_on_adv_report() callback will be invoked, and the advertising string that your device tracked will be indicated in the param pointer. That pointer points to a gapm_adv_report_ind struct and the tracked bd address will be located in the param->report.adv_addr.addr member. Regarding the fact that it doesn't work, the printing functionallity in DSPS uses UART2 module and the UART2 module is mapped on different pins on DSPS since UART1 module is used for the application. With only the above implementation and the CFG_PRINTF definition in the da1458x_config_basic.h (without placing the printf commands, since the user_on_adv_report() has allready the specified commands) you will be able to print the bd address of the scanned device.

Thanks MT_dialog