Merge Eddystone beacon and DFU buttonless application

RE: Merge Eddystone beacon and DFU buttonless application

Gabriel Jiro — Thu, 14 Jan 2021 11:40:01 GMT

Hi,

that configuration is ok:

Yes, I tried without the bootloader and it worked. I will look to that debug guide and try to debug...

Thanks

RE: Merge Eddystone beacon and DFU buttonless application

Hung Bui — Thu, 14 Jan 2021 08:54:59 GMT

Hi,
Please double check with a fresh copy of the SDK. The ble_app_eddystone has the following configuration:

When something doesn't work as it should, please try to debug.
Have you tried to test without the bootloader and step into the code to see if anything assert ? You may want to follow the debug guide here.

RE: Merge Eddystone beacon and DFU buttonless application

Gabriel Jiro — Wed, 13 Jan 2021 16:14:57 GMT

I did the DFU update with a simple application (buttonless application example from the nRF52 SDK) and it worked.

I also tested my Eddystone beacon application and it worked too.

Now, I am trying to merge both applications (buttonless application and eddystone beacon application), but it doesn't work. The device doesn't advertise....

I still think that the problem is related to the memory address.... Do you know why the beacon eddystone application example (from nRF52 SDK) use the 0x76000 - 0x7F007 address? How can I change it?

Thanks for helping

RE: Merge Eddystone beacon and DFU buttonless application

Hung Bui — Wed, 13 Jan 2021 14:53:45 GMT

Please try to do DFU update on simple application first before you move to more complex one. Also please try to test and make sure your application works without bootloader ( you may temporary turn off the buttonless feature)

RE: Merge Eddystone beacon and DFU buttonless application

Gabriel Jiro — Wed, 13 Jan 2021 12:19:43 GMT

Hi Hung,

Your blog is very useful. I updated the application using the bootloader and the nRF Connect app. However, after that, my device doesn't advertise...

I still think that it is a problem related to the memory address that the eddystone uses. I will try to change it.

Thanks

RE: Merge Eddystone beacon and DFU buttonless application

Hung Bui — Tue, 12 Jan 2021 18:25:31 GMT

Hi Gabriel,

When you testing with the bootloader, you would need to update the application using the bootloader. Please try to get familiar with the bootloader.
If you want to flash the application using the programming interface, you would need to create a bootloader setting to tell the bootloader that you have a valid application.
Please have a look at my blog here.

RE: Merge Eddystone beacon and DFU buttonless application

Gabriel Jiro — Tue, 12 Jan 2021 17:25:52 GMT

Hi, Hung
Thanks for your reply.

No, the device doesn't enter the application. It just stays in the bootloader, so it advertise the DFU information.

I think I found one of the problems:

It looks like the eddystone application uses the bootloader address....

I don't know why the beacon eddystone application uses the 0x7F000-0x76007... Any idea about how can I change this?

Gabriel

RE: Merge Eddystone beacon and DFU buttonless application

Hung Bui — Tue, 12 Jan 2021 16:55:50 GMT

Hi,

Could you check if your application can advertise any data, using nRF Connect app ?

If not, please try to debug. You need to find where it get assert and look for the error code.