你好,
We have customised target board which has da14580-01.
I have flashed proximity code using keil , in this BLE board.
But, i am not able to discover this device in my android device. i mean the device is not getting scanned .
Tue, 2015-01-27 10:48
#1
Not able to scan the da14580 device
Hello Shivanagouda,
Are you running proximity monitor or reporter application ? and was this 'as is ' out of the SDK ?
Which app did you use to check whether the device is advertising ? BlueLoupe is a very good app - i find that some apps don't always scan working devices that are known to be advertising, but blueloupe has been found to be very reliable.
BR JE_Dialog
Hello JE,
I am running proximity reporter application. and yes it is "as is " of the SDK.
Below are steps fallowed ,
after having done the connection , device got detected .
then , started the debug session, then RUN execution / STOP execution , and come out of debug session.
the application used is , nrf-master-control-panel , and some other BLE applications from playstroe.
Hello,
From your description, the 16M crystal oscillator may not be properly tuned and leading to the RF carrier off the nominal frequency.
Please follow "AN-B-020_v1.3_End product testing and programming guidelines" document to verify and tune the crystal frequency firstly.
BR, WI_Dialog.
Hello,
1. We are using a crystal of 12MHz across XTAL16Mm and XTAL16Mp , will this effect the performance of the BLE.
2. While we are copying the CODE directly into SRAM using keil , how to confirm that CODE has been copied properly ?
3. How to confirm that code has been properly flashed to the board .?
Hello shivanagouda,
thankyou Vesa...
Shivamagouda, the 16MHz XTAL is fundamental need : you cannot use a lower or higher value since all the intenral PLL are aligned to this frequency as well as the main MCU clocking architecture.
BR JE_Dialog