I have downloaded and compiled DA14580 Dialog Beacons 3.40.2 project in Keil uVision 4.73.0.0 and I am able to compile and run the project on the Murata module, part number LBCA2HNZYZ, on a custom board. The programmer I am using is the Keil ULINK2.
I have not changed anything in the provided project and I can see the advertisement in the Android Bluetooth LE Scanner App and 2 other Apple BLE Scanning apps, but unfortunately, none show the Device Name in the advertisement.
This is the information I get from the Android Bluetooth Scanner app:
Device Name:
Device Address: 98:F1:70:67:2D:AE
Device Class: Unknown
Bonding State: Unbonded
SCAN RECORD
[02, 01, 04, 1A, FF D2, 00, 02, 15, 58, 5C,
DE, 93, 1B, 01, 42, CC, 9A, 13, 25, 00, 9B,
ED, C6, 00, 00, 00, C5, 00, 00, 00, 00, 00,
00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00,
00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00,
00, 00, 00, 00, 00, 00, 00]
Raw AD Records
#1 Flags
As Array: '[04]'
#255 Manufacturer Specific Data
As Array: '[D2, 00, 02, 15, 58, ...
Any idea as to why the device info is not showing? There were absolutely no code changes to project DA14580 Dialog Beacons 3.40.2 and I can see all that information in const struct nvds_data_struct nvds_data_storage __attribute__((section("nvds_data_storage_area"))). This is my one and only development board at this time. My steps to run the project were as follows?
1. Download and unzip DA14580 Dialog Beacons 3.40.2
2.去Flash |配置Flash工具:
2a. In Device tab, set to Dialog Semiconductor DA14580
2b. In Debug tab, set to Use: ULINK2/ME Cortex Debugger
2c. In ULINK2/ME Cortex Debugger Settings, set Port to SW
3. In Utilities tab, check Use Target Driver for Flash Programming and select ULINK2/ME Cortex Debugger in drop down menu.
4. Start/stop debugging twice
Please help. Forgive me if I have missed a step. I have read thru the FAQ's page, Beacon Reference and software architecture PDF's as well as the murata first step guide, but could not find anything wrong.
Thanks in advance.
Hi JD,
Beacons do not necessarily advertise a device name. The sample beacon implmentations from Dialog does not advertise the name, so everything you report indicates that your setup is working as expected.
Please look thru the routine "app_adv_func", in file "app_dialog_beacon_proj.c". This is where the advertisement message is assembled. As you can see we pick up the data from "NVDS_TAG_APP_BLE_ADV_DATA". This is defined in nvds.c as
.NVDS_TAG_APP_BLE_ADV_DATA = "\x1A\xFF\xD2\x00\x02\x15\x58\x5C\xDE\x93\x1B\x01\x42\xCC\x9A\x13\x25\x00\x9B\xED\xC6\x5E\x00\x00\x00\x00\xC5",
This is what you see over the air.
MHv_Dialog & TR_Dialog,
Thank you so much for confirming. Last question, any idea where the Device Address (98:F1:70:67:2D:AE ) is located in the example project (DA14580 Dialog Beacons 3.40.2)??
The reason I ask is because in the example project, the MAC address, .NVDS_TAG_BD_ADDRESS = {0x01, 0x23, 0x45, 0x55, 0x89, 0x11},
is not the same as what is being advertised/scanned: 98:F1:70:67:2D:AE
y在哪里ou see the Device Address (98:F1:70:67:2D:AE ) ? I guess it is from a sniffer.
If that is the case, the BD address is most likely coming from the OTP header. You can confirm that by using Smart Snippets. If you read the OTP header, look at the 6 bytes starting at offset 0x7FD4.
The BD address in OTP header supersedes the BD address in .NVDS_TAG_BD_ADDRESS. The later will be used only if the BD address in OTP header is all zero. You can find the corresponding code in file nvds.c.