DA14585 DK Pro SDK6.0.12 prox_reporter Eclipse/GCC problem

Learn MoreFAQsTutorials

6 posts / 0 new
Last post
dsteury
Offline
Last seen:5 months 1 week ago
Joined:2016-09-28 16:05
DA14585 DK Pro SDK6.0.12 prox_reporter Eclipse/GCC problem

Hello,

I downloaded SDK6.0.12 and I'm using a DK14585 Pro development board. I noticed in the Getting Started with SDK6 tuturoal, Dialog Semiconductor offers some level of support for GCC and references:

The SDK contains a sample application which supports GCC. This project can be found in the following folder:/projects/target_apps/ble_examples/prox_reporter/Eclipse

I successfully imported the project, but I got a warning:

Invalid project path: Include path not found (C:\SDK\6.0.12.1020.2\sdk\platform\driver\spi_hci).

When I build, selecting DA14585, I don't get any errors (just the warning above), but when I debug, selecing RAM_DA14585, I hit a breakpoint in hardfault_handler, and looks like it's being triggered from GPIO_init() in system_init().

When I open arch_system.c is see two more warnings:

Unused declaration of function 'rf_recalibration'
Unused declaration of function 'set_system_clocks'

I realize this is actually meant to be used with the DA14531, but I don't have that setup (at least not yet). My question is, should this work with the setup I'm using? If so, can you shed any light on what I might be doing wrong?

Thanks

Device:
PM_Dialog
Offline
Last seen:3 days 23 hours ago
Staff
Joined:2018-02-08 11:03
Hi dsteury,

Hi dsteury,

The Eclipse based project of the SDK6.0.12 should work out of the box, as provided by the SDK. I tested in my side using the DA14585 Pro-DK, I can compile it and download the firmware into System-RAM. The device starts advertising and I can connect from a BL E mobile application. Please make sure that you are following the correct steps:

  1. Download and install the latest version (v2.0.10) of SmartSnippets Studio (SSS).
  2. Open the tool and select the workspace directory. It is recommend to follow the steps in a clean SDK workspace without the .metadata folder.
  3. Open the “Eclipse IDE” and import the pxp_reporter project.
  4. Right-click on the pxp_reporter from the “Project Explorer” window and select “Properties”. Please check the attached image and un-click the “Generate errors instead of warnings” option.
  5. DA14585构建项目。顶部的GUI you will find a “hammer” – you will need to select the second option from the drop-down menu.
  6. When the build is finished, select the DA14585 out folder and start a debug procedure for DA14585.
  7. Press the “Start” button and the device should start advertising.

Please follow the steps above and let me know if you have any other issue.

Thanks, PM_Dialog

Attachment:
dsteury
Offline
Last seen:5 months 1 week ago
Joined:2016-09-28 16:05
Thanks for quick reply and

Thanks for quick reply and for the steps and screenshots.

I thought I might have screwed up my PC somehow; so, I went to my son's machine (which never had any of the tools installed) and started from scratch. I downloaded and installed all of the tools, followed all of the steps and got to the same place you describe in step 7. I took a screenshot of my step_7 (please see attached), but when I hit start (see screenshot I'm calling step_8) I still have the same problem.

I'm wondering if maybe I have a hardware problem. I included a picture of my development kit. It it possible I have jumpers set in a way that might cause this problem. Could this be the issue?

Thanks, David

Attachment:
PM_Dialog
Offline
Last seen:3 days 23 hours ago
Staff
Joined:2018-02-08 11:03
Hi dsteury,

Hi dsteury,

Can you please set the jumpers in J5 header in the “SPI position” ?

Thanks, PM_Dialog

dsteury
Offline
Last seen:5 months 1 week ago
Joined:2016-09-28 16:05
Hello,

Hello,

I tried setting jumpers per your suggestion. I still have the same problem. I'm not sure what the problem is.

Attachment:
dsteury
Offline
Last seen:5 months 1 week ago
Joined:2016-09-28 16:05
So, I happen to have a

So, I happen to have a DA14585 IoT Multi-Sensor Development Kit and interface board. I decided to try and run this on that platform and it runs fine. There must be something wrong with my DK Pro. Consider this case closed.

Topic locked