Setting up WiSE Studio for BlueNRG evaluation board

[cxiong]

Hey,

So, I've been spoon fed on starting up a project but this is my first time figuring it out. I've been reading/skimming a few of manuals, a few example programs, and still don't know what to do. When I create a new program, I go to new-> C/C++ Project-> C++ Managed Build -> (selected WiSE Project and WiSE Toolchain) -> default configuration -> Series (BlueNRG-LP), Board (steval-idb011v1), import sources from BlueNRG Development Kit. (I linked it to the BlueNRG-LP DK 1.1.0 folder location) -> Finish.

I thought that would ease my library problems but when I go to build a turning on a LED code with just including BlueNRG_LP.h and stdio.h:

GPIOB->MODER = (GPIO_MODER_MODE8);

GPIOB->OTYPER = (GPIO_OTYPER_OT8);

I got 13 errors:

...

Building file: ../Middlewares/cryptolib/aes_hw.c

Invoking: GCC C Compiler

Invoking: GCC C Compiler

../src/BLE_User_main.c:28:10: fatal error: bluenrg_lp_it.h: No such file or directory

  28 | #include "bluenrg_lp_it.h"

   |     ^~~~~~~~~~~~~~~~~

compilation terminated.

src/subdir.mk:24: recipe for target 'src/BLE_User_main.o' failed

make: *** [src/BLE_User_main.o] Error 1

make: *** Waiting for unfinished jobs....

C:\Users\xxxxx\WiSE-Studio\workspace\TEST\Debug

../src/User.c:20:10: fatal error: bluenrg_lp_it.h: No such file or directory

  20 | #include "bluenrg_lp_it.h"

   |     ^~~~~~~~~~~~~~~~~

compilation terminated.

make: *** [src/User.o] Error 1

src/subdir.mk:24: recipe for target 'src/User.o' failed

arm-none-eabi-gcc -mcpu=cortex-m0plus -mthumb -mfloat-abi=soft -O0 -g3 -DSTEVAL_IDB011V1 -DCONFIG_DEVICE_BLUENRG_LP -DCONFIG_HW_SMPS_10uH -DCONFIG_HW_HSE_TUNE=32 -DCONFIG_HW_LS_XTAL -DUSE_FULL_LL_DRIVER -DUSER_BUTTON=BSP_PUSH1 -DBLE_STACK_FULL_CONF -I../../../Inc -I../../../../../../Drivers/Peripherals_Drivers/Inc -I../../../../../../Drivers/CMSIS/Device/ST/BlueNRG_LP/Include -I../../../../../../Middlewares/ST/hal/Inc -I../../../../../../Middlewares/ST/PKAMGR/Inc -I../../../../../../Middlewares/ST/RNGMGR/Inc -I../../../../../../Middlewares/ST/AESMGR/Inc -I../../../../../../Middlewares/ST/BLECNTR/Inc -I../../../../../../Middlewares/ST/NVMDB/Inc -I../../../../../../Drivers/CMSIS/Include -I../../../../../../Drivers/BSP/STEVAL-IDB011V1/Inc -I../../../../../../Drivers/BSP/Common/Inc -I../../../../../../Drivers/BSP/Components/lps22hh_STdC/driver -I../../../../../../Drivers/BSP/Components/lsm6dsox_STdC/driver -I../../../../../../Middlewares/ST/BLE_Application/layers_inc -I../../../../../../Middlewares/ST/BLE_Application/OTA/inc -I../../../../../../Middlewares/ST/Bluetooth_LE/Inc -I../../../../../../Middlewares/ST/NVMDB/Inc -I../../../../../../Middlewares/ST/BLE_Application/Profiles/Inc -I../../../../../../Middlewares/ST/cryptolib/inc -I../../../../../../Middlewares/ST/cryptolib/inc/Common -I../../../../../../Middlewares/ST/cryptolib/inc/AES -MMD -MP -MF"src/bluenrg_lp_it.d" -MT"src/bluenrg_lp_it.o" -c -o "src/bluenrg_lp_it.o" "../src/bluenrg_lp_it.c"

C:\Users\xxxx\WiSE-Studio\workspace\TEST\Debug

arm-none-eabi-gcc -mcpu=cortex-m0plus -mthumb -mfloat-abi=soft -O0 -g3 -DSTEVAL_IDB011V1 -DCONFIG_DEVICE_BLUENRG_LP -DCONFIG_HW_SMPS_10uH -DCONFIG_HW_HSE_TUNE=32 -DCONFIG_HW_LS_XTAL -DUSE_FULL_LL_DRIVER -DUSER_BUTTON=BSP_PUSH1 -DBLE_STACK_FULL_CONF -I../../../Inc -I../../../../../../Drivers/Peripherals_Drivers/Inc -I../../../../../../Drivers/CMSIS/Device/ST/BlueNRG_LP/Include -I../../../../../../Middlewares/ST/hal/Inc -I../../../../../../Middlewares/ST/PKAMGR/Inc -I../../../../../../Middlewares/ST/RNGMGR/Inc -I../../../../../../Middlewares/ST/AESMGR/Inc -I../../../../../../Middlewares/ST/BLECNTR/Inc -I../../../../../../Middlewares/ST/NVMDB/Inc -I../../../../../../Drivers/CMSIS/Include -I../../../../../../Drivers/BSP/STEVAL-IDB011V1/Inc -I../../../../../../Drivers/BSP/Common/Inc -I../../../../../../Drivers/BSP/Components/lps22hh_STdC/driver -I../../../../../../Drivers/BSP/Components/lsm6dsox_STdC/driver -I../../../../../../Middlewares/ST/BLE_Application/layers_inc -I../../../../../../Middlewares/ST/BLE_Application/OTA/inc -I../../../../../../Middlewares/ST/Bluetooth_LE/Inc -I../../../../../../Middlewares/ST/NVMDB/Inc -I../../../../../../Middlewares/ST/BLE_Application/Profiles/Inc -I../../../../../../Middlewares/ST/cryptolib/inc -I../../../../../../Middlewares/ST/cryptolib/inc/Common -I../../../../../../Middlewares/ST/cryptolib/inc/AES -MMD -MP -MF"Middlewares/cryptolib/aes_hw.d" -MT"Middlewares/cryptolib/aes_hw.o" -c -o "Middlewares/cryptolib/aes_hw.o" "../Middlewares/cryptolib/aes_hw.c"

../src/bluenrg_lp_it.c:25:10: fatal error: bluenrg_lp_it.h: No such file or directory

src/subdir.mk:24: recipe for target 'src/bluenrg_lp_it.o' failed

  25 | #include "bluenrg_lp_it.h"

   |     ^~~~~~~~~~~~~~~~~

compilation terminated.

make: *** [src/bluenrg_lp_it.o] Error 1

../Middlewares/cryptolib/aes_hw.c:13:10: fatal error: crypto.h: No such file or directory

  13 | #include "crypto.h"

   |     ^~~~~~~~~~

compilation terminated.

make: *** [Middlewares/cryptolib/aes_hw.o] Error 1

Middlewares/cryptolib/subdir.mk:18: recipe for target 'Middlewares/cryptolib/aes_hw.o' failed

"make -j8 all" terminated with exit code 2. Build might be incomplete.

[Sebastien DENOUAL]

Hi @cxiong​ 

I could advise tostart from an existing SDK code example at first.

You need first to install BlueNRG-LP SDK ; I suppose you already did it.

Then open one of BLE_Project from Wise Studio : "File->Import-> General -> Existing Project into workspace" and select the one most suitable for your application.

Edit : All project from SDK are already configured by default for STEVAL-IDB001V1

Regards,

Sebastien.

[Danny0007]

Hi Sebastien,

I want to further the question:
As you mentioned: "open one of BLE_Project from Wise Studio : "File->Import-> General -> Existing Project into workspace" and select the one most suitable for your application."

It´s ok, if user just wanna to view the example codes. But if user makes some changes in the Drivers and Middlewares, it will also affect other examples, because they share these codes.

My question: How to import a example project and its related Drivers and Middlewares into the workspace, so user can compile the code locally standalone, not affect other projects. As you can see if user tries to import the project into the workspace, the compiler still tries to look for the files as it´s set before.