Sysprogs forums › Forums › VisualGDB › Errors compiling nRF52 ADC project
- This topic has 7 replies, 2 voices, and was last updated 6 years, 8 months ago by support.
-
AuthorPosts
-
August 3, 2017 at 11:55 #11891AFParticipant
I am trying to compile an nRF52 example project for ADC. The compilation fails with the following errors
AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.nordic.nrf5x\nRF5x\components\drivers_nrf\power\nrf_drv_power.c(181,27): error : ‘NRF_POWER_THRESHOLD_V21’ undeclared (first use in this function)thr = NRF_POWER_THRESHOLD_V21;
AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.nordic.nrf5x\nRF5x\components\drivers_nrf\power\nrf_drv_power.c(184,27): error : ‘NRF_POWER_THRESHOLD_V23’ undeclared (first use in this function)thr = NRF_POWER_THRESHOLD_V23;
AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.nordic.nrf5x\nRF5x\components\drivers_nrf\power\nrf_drv_power.c(187,27): error : ‘NRF_POWER_THRESHOLD_V25’ undeclared (first use in this function)thr = NRF_POWER_THRESHOLD_V25;
AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.nordic.nrf5x\nRF5x\components\drivers_nrf\power\nrf_drv_power.c(190,27): error : ‘NRF_POWER_THRESHOLD_V27’ undeclared (first use in this function)thr = NRF_POWER_THRESHOLD_V27;
AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.nordic.nrf5x\nRF5x\components\drivers_nrf\power\nrf_drv_power.c(196,13): warning : implicit declaration of function ‘sd_power_pof_threshold_set’ [-Wimplicit-function-declaration]sd_power_pof_threshold_set(thr);
AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.nordic.nrf5x\nRF5x\components\drivers_nrf\power\nrf_drv_power.c(406,19): error : ‘NRF_EVT_POWER_FAILURE_WARNING’ undeclared (first use in this function)if (evt_id == NRF_EVT_POWER_FAILURE_WARNING)
AppData\Local\VisualGDB\EmbeddedBSPs\arm-eabi\com.sysprogs.arm.nordic.nrf5x\nRF5x\components\drivers_nrf\power\nrf_drv_power.c(429,49): error : ‘CLOCK_CONFIG_IRQ_PRIORITY’ undeclared (first use in this function)nrf_drv_common_irq_enable(POWER_CLOCK_IRQn, CLOCK_CONFIG_IRQ_PRIORITY);Need help to compile the project successfully
August 3, 2017 at 19:32 #11901supportKeymasterHi,
Please try searching the header files in the Nordic SDK directory for the definitions of NRF_POWER_THRESHOLD_V25. E.g. in SDK 13.0 it is defined in nrf_soc.h, but only if SOFTDEVICE_PRESENT is defined as well. Hence you would need to ensure that the softdevice is enabled for your project.
August 4, 2017 at 08:15 #11910AFParticipantHi,
The SOFTDEVICE_PRESENT is defined in the project and the option to include the soft device is also chosen when creating the project. I think there is a bug in VisualGDB and how it generates a project.
I tried compiling the same example in nRF SDK v13 (installed separately) using command line and it just compiled without any errors or warning.
I am currently running VisualGDB in trial mode. If it cannot even generate and build a sample program, then is it worth buying??
August 4, 2017 at 17:21 #11924supportKeymasterHi,
We are sorry about your experience. We have just retested this by creating a new project for Nordic nRF528232 with the SDK 13.0 and manually enabling the power module and could not get any error. The line mentioning NRF_POWER_THRESHOLD_V23 compile successfully and IntelliSense is able to find the definition correctly.
Perhaps you have imported the project in a way that lets a 3rd-party Makefile control the build and the Makefile itself contains errors? We would be happy to help you if you could let us know how exactly have you created the project so that we could reproduce this on our side.
August 4, 2017 at 23:44 #11926AFParticipantFind attached screen shots and the output of the build.
Attachments:
You must be logged in to view attached files.August 6, 2017 at 05:19 #11937supportKeymasterHi,
Thanks for the detailed description. We have rechecked this and can confirm that it is a bug in the latest VisualGDB version. The behavior we got was different, although the error you observed could be caused by the same problem. Some samples from the Nordic SDK like SAADC can only be compiled with the softdevice disabled and VisualGDB did not properly override the softdevice setting manually selected on the MCU selection page. We have fixed this in the upcoming v5.3 Preview 5. As a workaround please try disabling the softdevice manually via VisualGDB Project Properties.
Please also update your nRF5x BSP to the latest version (13.0r3) as previous BSP versions might handle this incorrectly.
August 7, 2017 at 02:32 #11955AFParticipantHi,
Thanks for the reply.
Can I update my copy of VisualGDB to v5.3 Preview 5?
Cheers
August 7, 2017 at 07:25 #11958supportKeymasterHi,
Sure, we have just released it: http://visualgdb.com/download/ (use the “try preview” button).
After installing we recommend updating the debug packages via Tools->VisualGDB->Manage VisualGDB Packages. This will install updates that significantly improve the OpenOCD and Segger J-Link debug experience.
-
AuthorPosts
- You must be logged in to reply to this topic.